Knoppix 3.8: booting stops at eth0

OK, I'm on the internet with Knoppix 3.8 now.
This is the workaround I used:

Download to floppy dhcp3-common and dhcp3-client.

Boot Knoppix with nodhcp option.

rmmod de4x5
modprobe de2104x
ifconfig eth0 up
ifconfig

dpkg -r pump
dpkg -r knoppix-terminalserver
dpkg -r dhcp3-server
dpkg -r dhcp3-common

dpkg -i /UNIONFS/floppy/dhcp3-common_3.0+3.0.1rc9-2.2_i386.deb
dpkg -i /UNIONFS/floppy/dhcp3-client_3.0+3.0.1rc9-2.2_i386.deb
dhclient
ifconfig

Hope this helps, and hope someone comes up with an easier solution!

Dave

Quote:

---

Originally Posted by davey

immediately after starting to install. Ubuntu uses de2104x and dhclient (instead of pump).

So would dhclient be better with Knoppix kernel 2.6.x than pump, for my ancient DECchip 21040?
How to do that without installing Knoppix?

---

de2104x is a different module v. de4x5 and I think there is an issue with the de4x5 module under 2.6.x and I don't know if the de2104x module is included on the Knoppix CD.

I'll have to give this a try if they have a live CD to test to see what happens.

Quote:

---

Originally Posted by davey

OK, I'm on the internet with Knoppix 3.8 now.
This is the workaround I used:

Hope this helps, and hope someone comes up with an easier solution!

---

I'll give this a whirl to see what happens.

Did you by chance try just the new 2104x module with pump and not replacing with dhclient? It would interesting to see if its the module or pump to get this fixed for future releases since V3.8 and up will be kernel 2.6.x only.

Well I decided I would see what happens with Kubuntu, Gnomes are banned in my area, from another post.

So I booted it up, on my ancient test machine, LAN works fine, so its either the de4x5 module, my hunch or pump. As it dies if you do ANYTHING to the LAN card, I lean to the de4x5 module. I've got an issue with video on under Kunutu Hoary but thats a result of the xserver used.

I'll post what I get with this method and see what happens.

Quote:

---

rec9140 wrote:
Did you by chance try just the new 2104x module with pump and not replacing with dhclient? It would interesting to see if its the module or pump to get this fixed for future releases since V3.8 and up will be kernel 2.6.x only.

---

2104x module with pump froze machine, if I recall correctly; so maybe it's pump at fault?
Thanks for your investigations.
Dave

Quote:

---

davey wrote in error:
2104x module with pump froze machine, if I recall correctly; so maybe it's pump at fault?

---

Sorry I got that wrong, just tried it again:
rmmod de4x5
modprobe de2104x
ifconfig eth0 up
ifconfig
pump
ifconfig

eth0 looks like it's up, but still no internet "unknown host www.google.ca". Won't even connect to my router "refused connection". File /etc/resolv.conf looked OK, had my router as nameserver:
cat /etc/resolv.conf
search flfrd.phub.net.cabl
nameserver 192.168.0.1

Quote:

---

Originally Posted by davey

Code:

---

rmmod de4x5
modprobe de2104x
ifconfig eth0 up
ifconfig
 
dpkg -r pump
dpkg -r knoppix-terminalserver
dpkg -r dhcp3-server
dpkg -r dhcp3-common
 
dpkg -i /UNIONFS/floppy/dhcp3-common_3.0+3.0.1rc9-2.2_i386.deb
dpkg -i /UNIONFS/floppy/dhcp3-client_3.0+3.0.1rc9-2.2_i386.deb
dhclient
ifconfig

---

---

This works great, :) :) :) Thanks! ! I had to change the dpkg -i steps as follows:

dpkg -i /UNIONFS/mnt/floppy/dhcp3-common_3.0+3.0.1rc9-2.2_i386.deb
dpkg -i /UNIONFS/mnt/floppy/dhcp3-client_3.0+3.0.1rc9-2.2_i386.deb

I am posting this from a working 3.8 on my test machine with the problem DEC21041 card.

Will have to see if pump or the module is the problem with some tests.

Thanks for help!

Any one else with DEC Tulip cards that were doing this please post your results and chip, and card, lspci -v info so we can get this cleared up for the future.

[quote="davey"]

Quote:

---

davey wrote in error:
2104x module with pump froze machine, if I recall correctly; so maybe it's pump at fault? eth0 looks like it's up, but still no internet "unknown host www.google.ca". Won't even connect to my router "refused connection". File /etc/resolv.conf looked OK, had my router as

---

Same for me, so its a combo between the module and pump.

At least I can get this solved to go from ancient 2003 to the lastest version for now.

Thanks again for the help.

Hey all, just so you know, I think this eth0 problem is with the current version of the 2.6 kernel (2.6.11). Simply because I also use Kanotix which uses the 2.6.6 kernel and eth0 works fine with it... Perhaps someone might consider doing a remaster with the 2.6.6 kernel. I've noticed that Kanotix boots a bit faster than Knoppix using this 2.6 kernel version.

Quote:

---

Originally Posted by poppe

Hey all, just so you know, I think this eth0 problem is with the current version of the 2.6 kernel (2.6.11). Simply because I also use Kanotix which uses the 2.6.6 kernel and eth0 works fine with it...

---

That's been a very goog idea! I have tried Kanotix 2005-02 which uses Kernel 2.6.11, too, I think - and eth0 works fine - no longer any problem with tulip or not tulip... :-)

Quote:

---

Originally Posted by rgruhn

That's been a very goog idea! I have tried Kanotix 2005-02 which uses Kernel 2.6.11, too, I think - and eth0 works fine - no longer any problem with tulip or not tulip... :-)

---

Please VERIFY that Kanotix is using kernel V2.6.11 and which module and version of the module(s): tulip, de4x5, or de2104x and which Tulip chip? 21040,21041, 21043?

I would like to get this nailed down to what the exact cause is: Tulip module(s), pump or kernel.

Once nailed down I want to get this submitted to the proper people to correct for future versions.

One workaround is posted here, and it works. I am going to have to try some more tests but some combo of kernel, pump, module, and dhclient are the problem.