nic 3c900B not working

Bug #49042 reported by andrew wood
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.15-23-386

Ethernet controller: 3Com Corporation 3c900B-TPC Etherlink XL [Cyclone] (rev 04)
 kernel module loads and interface appears up but error message comes up saying "localhost kernel: [ 91.207853] ADDRCONF(NETDEV_UP): eth0: link is not ready"

I have had to revert back to linux-image-2.6.10-5-386 where it is working fine.

Revision history for this message
jcinacio (jcinacio) wrote :

Same here, 3com nic with 3c900 chipset and 2.6.15-26-amd64-k8 kernel.

output of lspci:
0000:00:0e.0 Ethernet controller: 3Com Corporation 3c900 10BaseT [Boomerang]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (750ns min, 2000ns max)
        Interrupt: pin A routed to IRQ 209
        Region 0: I/O ports at b000 [size=64]
        Expansion ROM at f9c00000 [disabled] [size=64K]

modprobe'd the kernel module with debuging, dmesg relevant output:

[ 1696.039734] eth1: Filling in the Rx ring.
[ 1696.039917] ACPI: PCI Interrupt 0000:00:0e.0[A] -> GSI 19 (level, low) -> IRQ 209
[ 1696.040036] eth1: first available media type: 10baseT
[ 1696.040119] eth1: Initial media type 10baseT.
[ 1696.040196] eth1: vortex_up() InternalConfig 010302d8.
[ 1696.040282] eth1: vortex_up() irq 209 media status 88c0.
[ 1696.041511] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 1697.438038] eth1: Media selection timer tick happened, 10baseT.
[ 1697.438042] dev->watchdog_timeo=1250
[ 1697.438058] eth1: Media 10baseT has no link beat, 80c0.
[ 1697.438060] eth1: Media selection failing, using default 10baseT port.
[ 1697.438065] wrote 0x010302d8 to Wn3_Config
[ 1697.438073] eth1: Media selection timer finished, 10baseT.

Roel Huybrechts (rulus)
Changed in linux-source-2.6.15:
status: Unconfirmed → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
MillenniumBug (millenniumbug) wrote :

This bug report concerns only obsolete releases of Ubuntu. Is it still relevant?

Revision history for this message
MillenniumBug (millenniumbug) wrote :

Closing this bug report due to obsolete versions and lack of activity.

If a similar bug appears in Ubuntu 10.10, please open a new report.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.