Slacko(32/64) 6.3.2/6.3.0 bug reports.

[8Geee]

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.

[OscarTalks]

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.

Hello tenbob,

Always difficult to diagnose remotely and especially when everything just goes black, but that sounds to me like something going wrong in the early part of the unetbootin boot sequence.

Do you have an optical drive? If so I would suggest trying to burn and boot a live CD and then use the on-board tools to install to USB drive if that is what you want to do. These will probably use syslinux to set up the boot sequence and I have always found this works flawlessly.

EDIT:- Actually I just noticed in your later post that the stick boots on other hardware so probably my suggestions will be of no use to you. Must say I am surprised that "puppy pfix=nox" doesn't seem to help you. It would be interesting to know if other Pups will boot on that machine.

[01micko]

@tenbob

The only work around I can come up with is to blacklist the via kernel module.

Try this:

Code: Select all

puppy modprobe.blacklist=via

That should at least work with pfix=nox (you can append that alsoif you wish) to get you to the CLI interface, but may work with the VESA xorg driver for GUI.

[01micko]

3G modem users

I am connecting successfully, with DNS working. The problem for me was interference from dhcpcd. It is rewriting the /etc/resolv.conf after wvdial has written to it. The simple fix is to kill any dhcpcd process. I might add a line to pupdial to see if there is a process id for dhcpcd and if so kill it.

-----------

Later I unlocked a hutchinson 3 mobile dongle (huawei E160G, the virgin one was an E160E) and I can connect ootb on my vodafone sim.

The modified pupdial is committed to woof-CE - get a copy here. Make it executable and overwrite the version of pupdial in /usr/sbin.

[AshwaniGaur]

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

------------------------------------------------------

Thanks for your efforts, BUT problem remains same -SAD
I installed Fix provided by you one by one, still not able to connect to surf.

here is my log from Wvdail window:-

Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S1 S2 S3
ttyUSB0<*1>: ATQ0 V1 E1 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB0<*1>: Modem Identifier: ATI -- Manufacturer: huawei
ttyUSB0<*1>: Speed 9600: AT -- OK
ttyUSB0<*1>: Max speed is 9600; that should be safe.
ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyUSB1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 9600 baud
ttyUSB1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyUSB2<*1>: ATQ0 V1 E1 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB2<*1>: Modem Identifier: ATI -- Manufacturer: huawei
ttyUSB2<*1>: Speed 9600: AT -- OK
ttyUSB2<*1>: Max speed is 9600; that should be safe.
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

Found a modem on /dev/ttyUSB0.
Modem configuration written to /etc/wvdial.conf.

*** WARNING! Line "115200"
in /etc/ppp/options may conflict with wvdial!

ttyUSB0<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
ttyUSB2<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
Welcome to PupDial, written by Barry Kauler, with
contributions from Richard Erwin, for Puppy Linux.

There is a configuration file, /etc/wvdial.conf, that is read by
PupDial, and changes made to any of the above boxes will be saved
to wvdial.conf when you click the 'Exit' or 'Connect' buttons.
Note, you can also manually edit wvdial.conf with a text editor.

If you are using PupDial for the first time, it is recommended that
you click the help buttons, in particular the 'Modem setup' button.


And after Connect this LOG is from pupdail-WvDail window:-

--> WvDial: Internet dialer version 1.61
--> Warning: section [Dialer wireless] does not exist in wvdial.conf.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1,"IP","rcomnet"
AT+CGDCONT=1,"IP","rcomnet"
OK
--> Modem initialized.

and this one is from old puppy5.7 (Working) :-

--> WvDial: Internet dialer version 1.53
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1,"IP","rcomnet"
AT+CGDCONT=1,"IP","rcomnet"
OK
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
ATDT*99#
CONNECT
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Thu Dec 31 12:14:09 2015
--> pid of pppd: 6881



I donot know if this can help you to find missing BUG.

[watchdog]

I confirm no way to surf after the 3G connection is established. Resolv.conf is ok.

EDIT: from /var/log/messages:

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 

[peebee]

Slacko64-6.3.0 - x264

Library check shows that x264 needs to be recompiled as it links to old versions of libraries:

/usr/bin/x264:
libavformat.so.55 => not found
libavcodec.so.55 => not found
libavutil.so.52 => not found
libswscale.so.2 => not found

Cheers
peebee

[Dennola4]

Hey there,

sorry if this is an inappropriate place to post this (feel free to move it to your love letters box.... LOL) but as a long time Slackware and Puppy user who has been with Salix since its inception, I am absolutely blown away that this pup exists. Ever since TXZPUP I've dreamed of something like this. It's beautiful. Thanks so much for creating and maintaining it.

Dennis in San Diego,CA

[01micko]

@watchdog and AshwaniGaur

Absolutely make sure the firewall is off. Also, try unchecking 'Stupid mode'. I was able to reproduce the dropped packets but had inadvertently left the firewall on. Once connected then you can re configure the firewall.

Also there is some weird GTK/UTF-8 bug preventing the log from showing properly both in the Xdialog logbox and the gtkdialog logbox, BUT only in the 32 bit slacko. It is caused by ppp spewing out invalid utf8 characters and GTK chokes. 64 is fine, as ppp is not showing these entries in the log. In this case take a look (and post if you like) at the contents of /tmp/pupdial.log before closing pupdial.

----

@Dennola4 - filed to 'love letters'

[watchdog]

@watchdog and AshwaniGaur

Absolutely make sure the firewall is off.
<cut>
Once connected then you can re configure the firewall.

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

[01micko]

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

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.

Thanks for testing!

[AshwaniGaur]

@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'

Well, Firewall is OFF , StupidMode is Unchecked. still not able to connect to internet, Donot know what wrong i am doing

Here are LOG:-

--> WvDial: Internet dialer version 1.61
--> Warning: section [Dialer wireless] does not exist in wvdial.conf.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1,"IP","rcomnet"
AT+CGDCONT=1,"IP","rcomnet"
OK
--> Modem initialized.

AND FROM OLD WORKING PUPPY5.7:-

--> WvDial: Internet dialer version 1.53
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1,"IP","rcomnet"
AT+CGDCONT=1,"IP","rcomnet"
OK
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
ATDT*99#
CONNECT
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Fri Jan 1 14:53:27 2016
--> pid of pppd: 6876


Wishing every Puppian Happy New Year@2016

AshwaniGaur
with Warm Regards from INDIA

[01micko]

@AshwaniGaur

You maybe missed this:

In this case take a look (and post if you like) at the contents of /tmp/pupdial.log before closing pupdial.

That should be a more complete log.

Also, can you run this:

Code: Select all

pmodemdiag

It makes a log in /root. Can you please attach that with your next post.

Thanks for your help.

[AshwaniGaur]

@01micko

SIR,here is pmodemdiag file, KIndly find time to have a look.
Thanks

[Karl Godt]

the last line of the var log messages file may say everything :

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]

the newer wvdial version seems to have *bugs* .

[ozsouth]

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.

[01micko]

the last line of the var log messages file may say everything :

Yes it crashed, but we know that!

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]

the newer wvdial version seems to have *bugs* .

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/wvstreams . In the near future we are going to have to move away from wvdial/wvstreams to something which is light, maintained and most of all works! But what? Maybe we can write our own frontend to ppp?

[01micko]

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.

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.

[01micko]

Newest wvdial and wvstreams packages; both needed

http://distro.ibiblio.org/puppylinux/pe ... 6_s632.pet
http://distro.ibiblio.org/puppylinux/pe ... 6_s632.pet

------------------------------------------------

Attached below is a modified firewall_ng. Just gunzip the package, make it executable and overwrite the version in /usr/sbin.

It includes a new 'generic' checkbox on by default plus it now remembers settings. There are also new buttons to reload/refresh and one to add custom rules.

Have fun!

[Karl Godt]

But what? Maybe we can write our own frontend to ppp??

I am no Coder .. Good Luck !

Hmmm ... pppd relies on wvstream ?

Nevertheless, I used pupdial because I had knowledge about wvdial .

But recognizing how easier pgprs-connect is, I only used that .
pupdial is somehow a piece of crap IMO .
It overwrites /etc/wvdial.conf all the time.
Manual changes therein got deleted , which frustrated me much !

So, Bottom line is : Drop pupdial and wvdial all together and only use pgprs-connect !

I am also using an USB modem now by Huawei, that came with some linux usb_modeswitch bin and scripts ,
that uses cdc-ether, usbnet and e1000e .ko
and runs on eth1 with dhcpcd without any pppd or chat or wvdial .
Scripts were written in year 2008 for Red-Hat and SUSE with sysvinit that contained patches that created 3 additional binaries .