Red Hat Bugzilla – Bug 127791
NIC 3Com 3C905b doesn't work.
Last modified: 2015-01-04 17:07:52 EST
Description of problem:
Can not connect to the internet.
Am unable to ping my default gateway.
Version-Release number of selected component (if applicable):
Fedora Core 3 Test 1 (2004JUL13)
Very. I reinstalled OS, & problem remained.
Steps to Reproduce:
1.Installed Fedora Core 3 Test 1
2.Tried to ping gateway router, not able to get to Internet via Web.
Ping results indicated that my gateway was unreachable.
Was able to work around the problem by removing 3Com 3C905b &
replacing with an "Intel Pro 100".
so it seems that the driver for 3Com 3C905b did not work and the one
for Intel Pro 100 did?
BTW, the "Version" for this bug should be "test1" not "test3".
Yes, the driver for the Intel Pro 100 did work.
with the same configuration? if yes, shouldn't this be a bug of
Can you post the output of 'dmesg' at some point after you tried to
bring up the 3com card and it didn't work?
Kernel 2.6.5 has a bug in the 3c905 driver. Kernel 2.6.7 fixes it.
fixed in current updates ?
My 3Com 3c905B works with kernel-2.6.10-1.770_FC3 but not with
+-11.0 3Com Corporation 3c905B 100BaseTX [Cyclone]
(on-board NIC in a Dell Precision 410)
I see link info with mii-tool that looks correct, can configure a fixed IP
address, but can't send or receive traffic. (ARP cache doesn't get filled up,
but even with a static ARP definition a ping -n reports 100% loss). No apparent
errors in dmesg.
Haven't tried tcpdump yet as it wasn't installed on the machine.
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.
There are a large number of inactive bugs in the database, and this is the only
way to purge them.