Posted: Wed 30 Dec 2015, 14:51
My condolences on your NorthBridge Via CN896 and VN896. I don't see anything so far in linux for a driver, although theres plenty of Windows stuff available. Maybe theres something in Ubuntu.
READ-ONLY Archive
https://oldforum.puppylinux.com/
Hello tenbob,tenbob wrote:I am trying to boot from a USB I created with UNetbootin from the ISO. I can see the progress up to "Booting the kernel", then the screen flickers and goes blank.
Code: Select all
puppy modprobe.blacklist=via
Thanks for your efforts, BUT problem remains same -SAD01micko wrote:3G Modem fix up packages for evaluation
If they prove to work I will put a link on the front page and add to the next version. All pets are not essential but are recommended. The main one is wvstreams where the bug was found; usb-modeswitch is upgraded to the latest version. A missing package 'modem-stats' is added.
32 bit
http://distro.ibiblio.org/puppylinux/pe ... -1.0.1.pet
http://distro.ibiblio.org/puppylinux/pe ... 6_s631.pet
http://distro.ibiblio.org/puppylinux/pe ... 6_s631.pet
http://distro.ibiblio.org/puppylinux/pe ... 6_s631.pet
http://distro.ibiblio.org/puppylinux/pe ... 6_s631.pet
64 bit
http://distro.ibiblio.org/puppylinux/pe ... 4_s631.pet
http://distro.ibiblio.org/puppylinux/pe ... 4_s631.pet
http://distro.ibiblio.org/puppylinux/pe ... 4_s630.pet
http://distro.ibiblio.org/puppylinux/pe ... 4_s631.pet
http://distro.ibiblio.org/puppylinux/pe ... 4_s631.pet
------------------------------------------------------
Code: Select all
Dec 31 11:49:55 puppypc2680 daemon.notice pppd[14380]: pppd 2.4.5 started by root, uid 0
Dec 31 11:49:55 puppypc2680 daemon.debug pppd[14380]: using channel 1
Dec 31 11:49:55 puppypc2680 daemon.info pppd[14380]: Using interface ppp0
Dec 31 11:49:55 puppypc2680 daemon.notice pppd[14380]: Connect: ppp0 <--> /dev/ttyUSB0
Dec 31 11:49:55 puppypc2680 daemon.warn pppd[14380]: Warning - secret file /etc/ppp/pap-secrets has world and/or group access
Dec 31 11:49:55 puppypc2680 daemon.debug pppd[14380]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x9a39a019> <pcomp> <accomp>]
Dec 31 11:49:55 puppypc2680 daemon.debug pppd[14380]: rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth chap MD5> <magic 0xf4de31> <pcomp> <accomp>]
Dec 31 11:49:55 puppypc2680 daemon.debug pppd[14380]: sent [LCP ConfAck id=0x0 <asyncmap 0x0> <auth chap MD5> <magic 0xf4de31> <pcomp> <accomp>]
Dec 31 11:49:55 puppypc2680 daemon.debug pppd[14380]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x9a39a019> <pcomp> <accomp>]
Dec 31 11:49:55 puppypc2680 daemon.debug pppd[14380]: rcvd [LCP DiscReq id=0x1 magic=0xf4de31]
Dec 31 11:49:55 puppypc2680 daemon.debug pppd[14380]: rcvd [CHAP Challenge id=0x1 <d0fbfb2732295110fc9967406c90ae51>, name = "UMTS_CHAP_SRVR"]
Dec 31 11:49:55 puppypc2680 daemon.warn pppd[14380]: Warning - secret file /etc/ppp/chap-secrets has world and/or group access
Dec 31 11:49:55 puppypc2680 daemon.debug pppd[14380]: sent [CHAP Response id=0x1 <29de67db3cca54117ca5cccfd3d0b716>, name = "''"]
Dec 31 11:49:55 puppypc2680 daemon.debug pppd[14380]: rcvd [CHAP Success id=0x1 ""]
Dec 31 11:49:55 puppypc2680 daemon.info pppd[14380]: CHAP authentication succeeded
Dec 31 11:49:55 puppypc2680 daemon.notice pppd[14380]: CHAP authentication succeeded
Dec 31 11:49:55 puppypc2680 daemon.warn pppd[14380]: kernel does not support PPP filtering
Jan 1 09:49:55 puppypc2680 user.info kernel: PPP BSD Compression module registered
Dec 31 11:49:55 puppypc2680 daemon.debug pppd[14380]: sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
Dec 31 11:49:55 puppypc2680 daemon.debug pppd[14380]: sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
Jan 1 09:49:55 puppypc2680 user.info kernel: PPP Deflate Compression module registered
Dec 31 11:49:55 puppypc2680 daemon.debug pppd[14380]: rcvd [LCP ProtRej id=0x2 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f]
Dec 31 11:49:55 puppypc2680 daemon.debug pppd[14380]: Protocol-Reject for 'Compression Control Protocol' (0x80fd) received
Dec 31 11:49:56 puppypc2680 daemon.debug pppd[14380]: rcvd [IPCP ConfNak id=0x1 <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
Dec 31 11:49:56 puppypc2680 daemon.debug pppd[14380]: sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
Dec 31 11:49:57 puppypc2680 daemon.debug pppd[14380]: rcvd [IPCP ConfNak id=0x2 <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
Dec 31 11:49:57 puppypc2680 daemon.debug pppd[14380]: sent [IPCP ConfReq id=0x3 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
Dec 31 11:49:58 puppypc2680 daemon.debug pppd[14380]: rcvd [IPCP ConfReq id=0x0]
Dec 31 11:49:58 puppypc2680 daemon.debug pppd[14380]: sent [IPCP ConfNak id=0x0 <addr 0.0.0.0>]
Dec 31 11:49:58 puppypc2680 daemon.debug pppd[14380]: rcvd [IPCP ConfRej id=0x3 <compress VJ 0f 01>]
Dec 31 11:49:58 puppypc2680 daemon.debug pppd[14380]: sent [IPCP ConfReq id=0x4 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
Dec 31 11:49:58 puppypc2680 daemon.debug pppd[14380]: rcvd [IPCP ConfReq id=0x1]
Dec 31 11:49:58 puppypc2680 daemon.debug pppd[14380]: sent [IPCP ConfAck id=0x1]
Dec 31 11:49:58 puppypc2680 daemon.debug pppd[14380]: rcvd [IPCP ConfNak id=0x4 <addr 10.49.124.252> <ms-dns1 193.70.152.25> <ms-dns2 212.52.97.25>]
Dec 31 11:49:58 puppypc2680 daemon.debug pppd[14380]: sent [IPCP ConfReq id=0x5 <addr 10.49.124.252> <ms-dns1 193.70.152.25> <ms-dns2 212.52.97.25>]
Dec 31 11:49:58 puppypc2680 daemon.debug pppd[14380]: rcvd [IPCP ConfAck id=0x5 <addr 10.49.124.252> <ms-dns1 193.70.152.25> <ms-dns2 212.52.97.25>]
Dec 31 11:49:58 puppypc2680 daemon.warn pppd[14380]: Could not determine remote IP address: defaulting to 10.64.64.64
Dec 31 11:49:58 puppypc2680 daemon.notice pppd[14380]: local IP address 10.49.124.252
Dec 31 11:49:58 puppypc2680 daemon.notice pppd[14380]: remote IP address 10.64.64.64
Dec 31 11:49:58 puppypc2680 daemon.notice pppd[14380]: primary DNS address 193.70.152.25
Dec 31 11:49:58 puppypc2680 daemon.notice pppd[14380]: secondary DNS address 212.52.97.25
Jan 1 09:50:24 puppypc2680 user.warn kernel: OUTPUT packet died: IN= OUT=ppp0 SRC=10.49.124.252 DST=193.70.152.25 LEN=69 TOS=0x00 PREC=0x00 TTL=64 ID=229 DF PROTO=UDP SPT=58989 DPT=53 LEN=49
Jan 1 09:50:24 puppypc2680 user.warn kernel: OUTPUT packet died: IN= OUT=ppp0 SRC=10.49.124.252 DST=212.52.97.25 LEN=69 TOS=0x00 PREC=0x00 TTL=64 ID=16633 DF PROTO=UDP SPT=34596 DPT=53 LEN=49
Jan 1 09:50:24 puppypc2680 user.warn kernel: OUTPUT packet died: IN= OUT=ppp0 SRC=10.49.124.252 DST=193.70.152.25 LEN=69 TOS=0x00 PREC=0x00 TTL=64 ID=230 DF PROTO=UDP SPT=57240 DPT=53 LEN=49
Jan 1 09:51:05 puppypc2680 user.warn kernel: Invalid packet: IN=ppp0 OUT= MAC= SRC=184.173.179.49 DST=10.49.124.252 LEN=119 TOS=0x00 PREC=0x00 TTL=53 ID=17133 DF PROTO=TCP SPT=5222 DPT=52164 WINDOW=512 RES=0x00 ACK PSH FIN URGP=0
Jan 1 09:52:08 puppypc2680 user.warn kernel: Invalid packet: IN=ppp0 OUT= MAC= SRC=184.173.179.49 DST=10.49.124.252 LEN=119 TOS=0x00 PREC=0x00 TTL=53 ID=38861 DF PROTO=TCP SPT=5222 DPT=52164 WINDOW=512 RES=0x00 ACK PSH FIN URGP=0
Jan 1 09:53:12 puppypc2680 user.warn kernel: Invalid packet: IN=ppp0 OUT= MAC= SRC=184.173.179.49 DST=10.49.124.252 LEN=119 TOS=0x00 PREC=0x00 TTL=53 ID=22209 DF PROTO=TCP SPT=5222 DPT=52164 WINDOW=512 RES=0x00 ACK PSH FIN URGP=0
Cheers/usr/bin/x264:
libavformat.so.55 => not found
libavcodec.so.55 => not found
libavutil.so.52 => not found
libswscale.so.2 => not found
SOLVED! I turned the firewall off, dialed with pupdial and turned on the firewall again: I'm posting from it now. Many thanks and Happy New Year01micko wrote:@watchdog and AshwaniGaur
Absolutely make sure the firewall is off.
<cut>
Once connected then you can re configure the firewall.
Pretty simple really! Some have criticised this new firewall but I have found it to be very useful (and actually works!) I do need to improve it somewhat, like add some customisation for custom ports and maybe add some more standard ports. It is totally dependent on the network interface and perhaps should be a little more intelligent; like pop a message when the interface has changed or something like that.watchdog wrote:
SOLVED! I turned the firewall off, dialed with pupdial and turned on the firewall again: I'm posting from it now. Many thanks and Happy New Year
Well, Firewall is OFF , StupidMode is Unchecked. still not able to connect to internet, Donot know what wrong i am doing01micko wrote:@watchdog and AshwaniGaur
Absolutely make sure the firewall is off. Also, try unchecking 'Stupid mode'.
take a look (and post if you like) at the contents of /tmp/pupdial.log before closing pupdial.
----
@Dennola4 - filed to 'love letters'
That should be a more complete log.In this case take a look (and post if you like) at the contents of /tmp/pupdial.log before closing pupdial.
Code: Select all
pmodemdiag
Code: Select all
Jan 2 09:39:35 puppypc31083 user.info kernel: wvdial[9755]: segfault at 4 ip b7515d83 sp bfe9bb80 error 4 in libwvbase.so.4.6[b74e0000+7d000]
Yes it crashed, but we know that!Karl Godt wrote:the last line of the var log messages file may say everything :
There is NO newer wvdial version! It is at least 8 years old with various patches. I just built a version with the slackware patches, works the same for me.. pppd still spews out invalid UTF-8 chars baulking the log. Still connects and works for me. Anyway, the bug is in wvstreams. Unfortunately, bitrot is the culprit. Searching around reveals that newer libc isn't so good with wvdial/wvstreamsKarl Godt wrote:the newer wvdial version seems to have *bugs* .Code: Select all
Jan 2 09:39:35 puppypc31083 user.info kernel: wvdial[9755]: segfault at 4 ip b7515d83 sp bfe9bb80 error 4 in libwvbase.so.4.6[b74e0000+7d000]
Sounds interesting. I'll have a think about that and perhaps make the firewall more configurable and allow a more generic option, perhaps by way of a checkbox, set to 'generic' as default. It would certainly make USB installs more portable where the interface may change.ozsouth wrote:Mick, I tested my earlier suggestion
http://murga-linux.com/puppy/viewtopic. ... 575#874575
via GRC & PCFLANK sites - all tested ports stealthed, including high numbers.
Perhaps if others run their own tests on their own systems successfully, that generic firewall could be used.
I am no Coder .. Good Luck !But what? Maybe we can write our own frontend to ppp??