Page 1 of 1

Puppy 2.20alpha - eth0 driver not loaded

Posted: Mon 03 Sep 2007, 17:39
by tronkel
Just had a go with 2.20alpha using puppy pfix=ram

Ethernet wizard GUI does not show any driver as loaded, hence no live eth0 interface.

Neither auto-detect nor manual loading of the eepro100 driver will work. Message comes up saying driver failed to load. Works fine using a pup_save from 2.17.1

So might be something to do with the altered zdrv setup. No zdrv_220.sfs has been saved to the home drive hda1, but I think that is intentional with the new system as far as I understand.

The new start-up script is fast on this PC here, a pre-2000 400MHz Compaq Deskpro.

Will submit more probs when/if I find them.

Posted: Mon 03 Sep 2007, 19:52
by SirDuncan
I had the same problem with the driver. It also occurs with my wireless card, so no internet in 2.20 for now. Others seem to have been able to connect, so it must be certain drivers only.

Posted: Mon 03 Sep 2007, 20:23
by toronto
tried puppy 2.20alpha using puppy pfix=ram on my laptop a compaq pressario and an older packard bell desktop, on both machines couldn't get ethernet wizard to work. previously had no similar problems with puppy 2.16 2.17 and pizzapup 3.0

network driver not loaded

Posted: Tue 04 Sep 2007, 09:53
by gray
Tried 2.20 from CD.

During boot up I get a switch_root failed message and then a 60 second pause after which puppy continued with the boot.

When I tried the network wizard it did not detect my eth0 NIC, a via_rhine card. Tried to load the driver manually but it failed also.

All previous puppies have worked. Whats up doc ?

Puppy 2.20alpha -eth0 driver not loaded

Posted: Tue 04 Sep 2007, 10:53
by faughanvale
On a Dimension 4100 with Linksys NC100 --- no joy with either Network Wizard or manually. This has worked on versions 108 through 214.
and ...
On a Thinkpad 600 with Netgear WG511T and ndiswrapper --- no joy.
This has worked 108 through 217.

Thank you Barry, et al. for many months of enjoyment.

Re: network driver not loaded

Posted: Tue 04 Sep 2007, 11:45
by eriefisher
gray wrote:Tried 2.20 from CD.

During boot up I get a switch_root failed message and then a 60 second pause after which puppy continued with the boot.
I got the same message?

However this was the first Puppy to detect eth0(wireless) on my laptop out of the box and only the second Linux distro. The other was Mepis7. It uses a broadcom chip and it's very fussy.

eriefisher

Posted: Tue 04 Sep 2007, 14:10
by vern72023
2 problems so far >
First
During boot up I get a switch_root failed message and then a 60 second pause after which puppy continued with the boot.

Second the eth0 setup has to be reset on every boot
I see the following errors in the log

dhcpcd: relocation error: /lib/libpthread.so.0: symbol errno, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
Error initializing interface eth0.!

The error about GLIBC_PRIVATE occurs multiple times within the bootsysinit.log
relating to various modules

George

Posted: Tue 04 Sep 2007, 17:56
by kjoe
I also have troubles with the driver for eth0 in puppy 2.20-alpha, which neither gets loaded automatically nor can be loaded manually.

I do not know the hardware, but in prior puppy versions (2.16/2.17.1) the via_rhine module automatically was chosen and loaded correctly.

If there is anything I can I do for testing purposes, just let me know.

kjoe

Posted: Wed 05 Sep 2007, 15:35
by vern72023
okay - I think I have fixed my problem with the errors regarding GLIBC I was getting
I had a wine939.sfs that i put together with an earlier distro.
So i redid that sfs file by removing the lib folder that I had in there, then re-running the ldconfig so that I now use the updated libs
That also fixed the problem I had with the eth0 needing to be reset each boot

I use wbar as well and I have not got that working yet but apart from that anf the annoying 60sec pause on boot up the rest of the stuff I use is looking good
George

Posted: Wed 05 Sep 2007, 19:30
by Alienx
I was without sound and network when testing 2.20 alpha from live cd

then I installed new puppy alpha to an usb pen drive, booted from there and all started working :roll:

Posted: Wed 05 Sep 2007, 19:42
by Alienx
when I was booting from live cd I saw that the kernel module of my eth0 wasnt in /lib/modules

I copyed all the kernel modules from the last stable puppy with files module.dep and module.alias, did modprobe 8139too and the network wizard worked and I get connected too

workaround for eth0 and sound

Posted: Thu 06 Sep 2007, 00:30
by tazoc
Alienx,
Thank you! I had no eth0 drivers loaded (eepro100) in 2.20 alpha frugal install and your suggestion worked for me. In addition I had no sound (snd_via82xx) and now that is fixed also.
-TazOC

Posted: Thu 06 Sep 2007, 11:35
by BarryK
Alienx wrote:I was without sound and network when testing 2.20 alpha from live cd

then I installed new puppy alpha to an usb pen drive, booted from there and all started working :roll:
Yes, see my recent developer blog post. I did most of my testing from a usb flash drive, so I got that mostly debugged. I have now found the cause of the modules not loading when boot from CD.

Probably enough feedback for the 2.20alpha. I'm fixing the bugs, and if it looks real good will bring out a beta, or if I still have doubts then there will be an alpha2.