I have the following PCI nic card: 3Com Corporation 3c905 100BaseTX [Boomerang] 2004.2 x86 Live CD's recognize this card and load the 3c59x module. I'm able to run "net-setup" and manually specifiy ip and dns server just fine. "ifconfig eth0" confirms the correct settings. I can ping my loopback and my asigned host ip but I can't ping anything else inside my lan or outside (ofcourse). I would attatch the logs but I can't connect to the machine in question or send the log capture out. This seems to be a well know occurence I've found in Google. For instance this URL shows almost exactly the same errors that I get. http://www.fedoraforum.org/forum/archive/index.php/t-3280.html I believe Kudzu or Hotplug seem to misconfiguring my card. Atleast thats what the internet seems to find as well as my work around that seems to verify this is as well. If I boot the live cd with the "gentoo nodetect" Option then when I "modprobe 3c59x" and run "net-setup eht0" per usual I can ping all devices on the local lan as well as the internet. I've only encountered this problem with the 2004.2 x86 live cd's. And come to think of it, this is the first Gentoo Live cd that has actually automagically detected and loaded the 3c59x module for me. Thats really nice. But the only problem is the card cannot transmit data out through the network interface. ;) Reproducible: Always Steps to Reproduce: 1. Boot using 2004.2 x86 live cd (universal or minimal doesn't matter)with 3com 3c905 pci nic. 2. Manually configure host ip,gateway and dns ip info with "net-setup" 3. Unable to ping anymachine on local lan or internet. But can ping lo and host ip of machine. Actual Results: Inability to transmit data out to local lan or internet through eth interface which is a 3com 3c905 make/model nic. Expected Results: At a minimum layer 3 connectivity to same subnet on the attached local lan with ping. When I google on "eth0: Host error, FIFO diagnostic register 2000 3com 3c59x" I find the same exact logs that I show. Booting with "gentoo nodetect" solves the the problem. I'm able to "modprobe 3c59x" use "net-setup" and have internet connectivity. livecd everything # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 3 model name : Pentium II (Klamath) stepping : 3 cpu MHz : 300.687 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov mmx bogomips : 599.65 livecd everything # lspci 0000:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 02) 0000:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 02) 0000:00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) 0000:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) 0000:00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) 0000:00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02) 0000:00:0f.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang] 0000:00:11.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 02) 0000:01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev b2)
Hrrrmn... I have a Vortex (3c905c) card that is detected and works fine. I actually don't have an older 905 card to test with. What error are you getting exactly? That link didn't seem to go to anything related.
Chris said: "What error are you getting exactly?" This system is building right now (from a stage1 install)and should be done by the end of today. Once the system is finished building I can replicate and save the error messages to the freshly partitioned drive and upload them to this ticket. I'll update the ticket once the compiling is done. Thanks.
Hi Chris, Ok.... Here's the goods you asked for. I've trimmed the excess fat off these log captures. If you would like or need a full copy of the log let me know and I will attach it. If you would like me to do any other testing let me know. 1: First Capture is of dmesg right after the 2004.2 Live CD boots-up. 2: Second Capture is of dmesg after successfully running "net-setup" but then trying to ping outside of the host either the intertnal lan or out to the internet without success. Ping of the loopback and manually assigned host ip address I get good replies. 3: Third Capture is of dmesg after the first reboot of the system going live after installation/system compilation. Keep in mind that I had to use "gentoo nodetect" boot option. After that I modprobed 3c59x, ran "net-setup" and dl'ed the x86 stage1 tarball via links2 just fine. I then compiled the specific driver into the kernel after chrooting in. ******** 1st Dmesg capture ******************** Here's a copy of "dmesg". Its the first command executed right after booting off the "2004.2 Minimal Install Live CD" What I thought was really cool was the 2004.2 cd apparently modprobed the card for me as confirmed by exe'ing "lsmod". START***********************************<snip<snip PCI: Found IRQ 9 for device 00:0f.0 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html See Documentation/networking/vortex.txt 00:0f.0: 3Com PCI 3c905 Boomerang 100baseTx at 0xe400. Vers LK1.1.18-ac 00:10:4b:72:f8:7e, IRQ 9 product code 4d4e rev 00.0 date 03-21-98 Internal config register is 16302d8, transceivers 0xe040. 8K word-wide RAM 3:5 Rx:Tx split, autoselect/MII interface. MII transceiver found at address 24, status 786f. Enabling bus-master transmits and whole-frame receives. 00:0f.0: scatter/gather enabled. h/w checksums disabled eth0: Dropping NETIF_F_SG since no checksum feature. PCI: Found IRQ 9 for device 00:0f.0 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html See Documentation/networking/vortex.txt 00:0f.0: 3Com PCI 3c905 Boomerang 100baseTx at 0xe400. Vers LK1.1.18-ac 00:10:4b:72:f8:7e, IRQ 9 product code 4d4e rev 00.0 date 03-21-98 Internal config register is 102001b, transceivers 0xe040. 64K word-wide RAM 1:1 Rx:Tx split, autoselect/10baseT interface. Enabling bus-master transmits and whole-frame receives. 00:0f.0: scatter/gather enabled. h/w checksums disabled eth0: Dropping NETIF_F_SG since no checksum feature. eth0: Transmit error, Tx status register d0. Flags; bus-master 1, dirty 1(1) current 1(1) Transmit list 00000000 vs. c5ff1240. 0: @c5ff1200 length 8000024e status 8000024e 1: @c5ff1240 length 00000000 status 00000000 2: @c5ff1280 length 00000000 status 00000000 3: @c5ff12c0 length 00000000 status 00000000 4: @c5ff1300 length 00000000 status 00000000 5: @c5ff1340 length 00000000 status 00000000 6: @c5ff1380 length 00000000 status 00000000 7: @c5ff13c0 length 00000000 status 00000000 8: @c5ff1400 length 00000000 status 00000000 9: @c5ff1440 length 00000000 status 00000000 10: @c5ff1480 length 00000000 status 00000000 11: @c5ff14c0 length 00000000 status 00000000 12: @c5ff1500 length 00000000 status 00000000 13: @c5ff1540 length 00000000 status 00000000 14: @c5ff1580 length 00000000 status 00000000 15: @c5ff15c0 length 00000000 status 00000000 >snip>snip***********************************END ********** 2nd dmesg capture ***************** The following capture seemed to go on indefinitely after pinging www.yahoo.com or someother host on the internal lan, until hitting ctrl-c. I'm cutting out the lines numbered 1-15 which are the exact same as what is shown above. START******************************************* NETDEV WATCHDOG: eth0: transmit timed out eth0: transmit timed out, tx_status 00 status e000. diagnostics: net 0cc0 media 8802 dma 00000020. Flags; bus-master 1, dirty 1(1) current 17(1) Transmit list 00000000 vs. c5ff1240. [LINES 1-15 CUT OUT] eth0: Resetting the Tx ring pointer. eth0: Transmit error, Tx status register 90. Flags; bus-master 1, dirty 1(1) current 17(1) Transmit list 05ff1280 vs. c5ff1240. [LINES 1-15 CUT OUT] The above logout repeats the same patter directly above, over and over and then when I hit ctrl-c I get the last little unique error output.. eth0: Host error, FIFO diagnostic register 2000. eth0: PCI bus error, bus status 00000029 *******************************************END *********** 3rd Dmesg Capture ************... after using "gentoo nodetect" option and compiling driver directly into the kernel via "make menuconfig". START********************************************* PCI: Found IRQ 9 for device 0000:00:0f.0 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html 0000:00:0f.0: 3Com PCI 3c905 Boomerang 100baseTx at 0xe400. Vers LK1.1.19 eth0: Dropping NETIF_F_SG since no checksum feature. ***********************************************END I'm not the only one having this issue either... Check out.. http://forums.gentoo.org/viewtopic.php?p=1439607#1439607 I found a few others as well.. but didn't bookmark them. Why does this ticket say "Fixed"? ... Did I miss something? These are the same exact errors that other people are getting on different distros and this seems to be related to "Kudzu" doing something wrong from what I can gather but you say your card works fine. Hmmmmm.. Thanks
Woopsee.. My bad. That first link was wrong. Thanks for pointing that out.. Put this in google and you will see what I mean.. eth0: Host error, FIFO diagnostic register 2000 3com 3c59x
This ticket *isn't* marked FIXED at all... Anyway, just out of curiosity, what happens if you boot with the smp kernel?
SMP kernel works fine. I don't get it? :D
Well, the SMP kernel is a 2.6 kernel. The 2.6 kernels on the LiveCD seem to have little to no problems, while almost every error, complaint, or bug that I have gotten about the LiveCD has all been with the "gentoo" kernel. Rest assured, there will be no 2.4 kernel on the 2004.3 LiveCD... *grin*
Great. Thanks for your time Chris.
To add to this bug I'm also unable to boot one of my systems unless I use the smp/2.6 kernel. When using the gentoo disc it does the little ansi bar saying it's detecting hardware, completes that and then locks up before any further output. The hardware is an Asus K7V motherboard with an AMD 800 proc. The only time I have seen this board lock up is when hwclock is run without --directisa but that issue may have been resolved long ago. Otherwise it's been perfectly stable as an extremely busy server for 3 years. 0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8371 [KX133] (rev 02) 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] 0000:00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22) 0000:00:04.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10) 0000:00:04.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10) 0000:00:04.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10) 0000:00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30) 0000:00:0b.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX (rev 10) 0000:00:0d.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 0c) 0000:01:00.0 VGA compatible controller: S3 Inc. 86c368 [Trio 3D/2X] (rev 02)
See if this ISO solves the problem... http://dev.gentoo.org/~wolf31o2/releng/install-x86-2004.2-r1-minimal.iso
I should have closed this a long time ago but apparently missed it.
