Knoppix 3.8: booting stops at eth0

[rgruhn]

I am using Knoppix 3.6. and 3.7 without any problems with always the same standard hardware. Booting Knoppix 3.8 stops at recognizing eth0, wainting on DHCP - no way going on. There is a DSL router with DHCP server.
I tried to boot with parameter "expert" but there was no possibility to interact at eth0 or ignore.

Who knows ta solution for this problem?

Reinhart.

[UnderScore]

At the bootup Knoppix 3.8 splash screen, type:
knoppix nodhcp

[rgruhn]

Thnx !
Finally I found this parameter [nodhcp] by myself and used it, but after starting Knoppix I cannot install the network card by hand. The system freezes totally after the input of the correct IP addresses.

[rec9140]

Thnx !
Finally I found this parameter [nodhcp] by myself and used it, but after starting Knoppix I cannot install the network card by hand. The system freezes totally after the input of the correct IP addresses.

What kind of card?

I have the same issue with DEC 21041 Tulip based cards under 2.6.x kernel

Reference: http://www.knoppix.net/forum/viewtopic.php?t=17894

I too have tried to do the nodhcp, rmmod or modprobe -r to remove the module and put a new module for a LAN driver in with out success.

So I am sticking to V3.7 under 2.4.x kernel, and since newer versions of Knoppix will only include 2.6 will just have to wait till what ever the bug is, is resolved.

[rgruhn]

It is an Intel 21143 fast ethernet PCI adapter.

I 've read the thread you pointed to - may be it is a bug in the 2.6.xx kernel. because I had the same problem with knoppix 3.7 and the 2.6 kernel! I only use the 2.4 and hope the problem will be fixed soon.
Thanks so much.

[rec9140]

It is an Intel 21143 fast ethernet PCI adapter.

I 've read the thread you pointed to - may be it is a bug in the 2.6.xx kernel. because I had the same problem with knoppix 3.7 and the 2.6 kernel! I only use the 2.4 and hope the problem will be fixed soon.
Thanks so much.

I think it is but I need to compile some evidence to support this.

Thanks for the info on the card, can you possible post a lspci -v and dmesg with the key parts for reference.

Thanks!

[rgruhn]

I think my problem is just the same as the well known with a DEC-Chip!
Here is the information:

lspci:
0000:02:0b.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 41)
Flags: bus master, medium devsel, latency 96, IRQ 23
I/O ports at e880 [size=128]
Memory at f7fff800 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at f7f80000 [disabled] [size=256K]

DMESG:
de4x5.c:V0.546 2001/02/22 davies@maniac.ultranet.com
Intel 810 + AC97 Audio, version 1.01, 07:27:43 Feb 23 2005
ACPI: PCI interrupt 0000:00:1f.5[B] -> GSI 17 (level, low) -> IRQ 17

[davey]

Is this any help, from dmesg and lspci?
Something related to IRQs?
____________________________________

PCI: Found IRQ 9 for device 0000:01:02.0
PCI: Sharing IRQ 9 with 0000:00:1f.3
PCI: Sharing IRQ 9 with 0000:00:1f.5
IRQ routing conflict for 0000:01:02.0, have irq 5, want irq 9
0000:01:02.0: DE434/5 at 0x7880, h/w address 00:00:92:91:2b:78,
and requires IRQ5 (provided by PCI BIOS).
de4x5.c:V0.546 2001/02/22 davies@maniac.ultranet.com
__________________________________________________ __________________

0000:01:02.0 Ethernet controller: Digital Equipment Corporation DECchip 21040 [Tulip] (rev 23)
Flags: bus master, medium devsel, latency 96, IRQ 5
I/O ports at 7880 [size=128]
Memory at febeff80 (32-bit, non-prefetchable) [size=128]

I'm a newbie in this area of linux. Would changing IRQ help? How do I do that in linux?
Thanks.
Dave

[davey]

Some progress thanks to Mepis Forum. Based on
http://www.mepis.org/node/2485?from=30&comments_per_page=30
near bottom of page, I tried

rmmod de4x5
modprobe de2104x
ifconfig eth0 up
ifconfig
pump

Now eth0 seems to be up, but still no internet.
dmesg | tail shows eth0: no IPv6 routers present
What next?

[davey]

Hmmm, Ubuntu 5.04 gets eth0 up and internet connection up almost 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?

Thanks.
Dave

[davey]

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

[rec9140]

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.

[rec9140]

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.

[davey]

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

[davey]

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

[rec9140]

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.

[rec9140]

[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.

[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... 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.

[rgruhn]

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... :-)

[rec9140]

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.

[rgruhn]

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?

yes, Kanotix 2005-02 really uses Kernel 2.6.11-kanotix-7

Here is some more info from the running Kanotix:

lspci -v

0000:02:0b.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 41)
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at e880 [size=128]
Memory at f7fff800 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at f7f80000 [disabled] [size=256K]


dmesg

Linux Tulip driver version 1.1.13 (May 11, 2002)
ACPI: PCI interrupt 0000:02:0b.0[A] -> GSI 11 (level, low) -> IRQ 11
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
tulip0: Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY (2) block.
tulip0: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
tulip0: Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY (4) block.
eth0: Digital DS21143 Tulip rev 65 at 0001e880, 00:40:F6:4C:64:1D, IRQ 11.

I hope this will be helpful for you!

[rec9140]

yes, Kanotix 2005-02 really uses Kernel 2.6.11-kanotix-7

I just want to be sure, so that we are comparing apples to apples.


It appears thats a different tulip driver and version than whats being used in Knoppix. Which would explain why modprobe tulip may load the module it doesn't create a working eth0 device.

I think in Knoppix that the auto detect needs to be set to use the de2104x for the tulip based cards, and that NODCHP also should be auto set for 2104x cards.

From my tests it appears that tulip based cards and the DHCP client on Knoppix will not work even though it appears to get a valid DHCP packet, under 2.6.x kernel. In 2.4 this is fine upto Knoppix V3.7.

I decided to try just:

rmmod de4x5
modprobe de2104x
ifconfig eth0 up

THEN run the netcardconfig script select NO on use DHCP, and it works fine!

[rgruhn]

I decided to try just:

rmmod de4x5
modprobe de2104x
ifconfig eth0 up

THEN run the netcardconfig script select NO on use DHCP, and it works fine!

I noticed that Kanotix has a different procedure to check the eth0 device than Knoppix, but it works very fine, and Kanotix is just like Knoppix; I can use the same home directory on my HD. It also has a better hardware detection for my soundcard, so I like Kanotix!

I will try your proposal later and hope it will work with my hardware and Knoppix 3.8 as simple as you show.

[rwcitek]

This worked for me under Virtual PC v7 for Mac OS X:

boot: knoppix nodhcp 1
rmmod tulip
modprobe de2104x
pump -i eth0
init 5

VPC presents a virtual NIC to Knoppix as a DECchip 21041 card

# lspci -v -s 00:0a.0
0000:00:0a.0 Ethernet controller: Digital Equipment Corporation DECchip 21041 [Tulip Pass 3] (rev 11)
Flags: medium devsel, IRQ 11
I/O ports at ec00 [disabled] [size=128]
Memory at febff000 (32-bit, non-prefetchable) [disabled] [size=4K]
Expansion ROM at febfe800 [disabled] [size=2K]

Regards,
- Robert
http://www.cwelug.org/

[rwcitek]

This worked for me under Virtual PC v7 for Mac OS X:

boot: knoppix nodhcp 1
rmmod tulip
modprobe de2104x
pump -i eth0
init 5

Just realize a forgot one step:

boot: knoppix nodhcp 1
rmmod tulip
modprobe de2104x
pump -k
pump -i eth0
init 5

Regards,
- Robert
http://www.cwelug.org