From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
The card doesn't work, unable to bing anywhere.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2. ping anywhere (except localhost or my IP)
Actual Results: Host unreachable error message.
Expected Results: Working network.
When I put the 8139too compatible NIC, to the same PCI slot, everything works.
Created attachment 93054 [details]
Relevant part of message log
tried 3c900 and 3c905 neither work - mal
Try the kernel boot option acpi=off
Check out https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=100522 for more
Tried with this boot option, but network still doesn't work.
Rebuilt the kernel and put 3c900 in it rather than a module and it worked
( broke a few things :-) but networking was fine - hope that helps - mal
Does that 3c905 card work in other operating systems or other brands of Linux?
Do you have identical cards, and they all exhibit this problem?
I have several dozen of those cards. Sometimes a few of them stop working
properly either completely or slow-down inexplicably. It turns out that the
card has hit its end of life, so I just toss it and replace it with another.
Otherwise I have had no problems with the RHL drivers for those cards in over
Please be sure that particular card is not the problem.
Both cards I tried worked in RH9, Suse 8.2 and XP
The machine had XP, Suse8.2 and Servern and if you boot to the other OSs
it works fine - then I switched the Suse partition to RH9 and that worked
too - anyway I got fed up and put a US Robotics network card in and that
is fine for everything
Interestingly if you build the driver into the kernel that also works
the problem only happens with Severn and the 3com as a loadable module
However I do love the idea of a geriatric network card slowing down :-)
Hmm, I tried the card with the latest Rawhide kernel and the problem seems to be
solved for me.
Malcolm, is the problem persisting with the latest kernel ?
I can't download it because I don't have a working network card
catch 22 - when the next beta comes out I'll download it via RH9
and give it another go
I have the same problem after installing the latest Beta.
When booting the Rescue-Mode from CD the network works fine.
I still have trouble after updating to 2.4.22-1.2087.nptlsmp.
I have had the same problem with a 3c575 PCMCIA card since Severn 1 (worked ok
before), and after restarting pcmcia and network services everything is fine again.
I have also figured out that turning off the graphical boot (by editing
/etc/sysconfig/init or getting rid of the rhgb package) also gets rid of the
problem. So it might be something in rhgb?
Latest rawhide kernel-2.4.22-1.2087.nptl doesn't fix it for me, haven't tried
I'm having this problem with a 3CCFE575CT-D card (Dell-branded 3Com 10/100
CardBus card -- IIRC the actual network controller is a 3C905-C) and the
2087/2088 kernels. I *think* the problem did not happen with 2061 (the one that
ships with severn 2) although I'm really not sure of that. I also think it
doesn't happen if I insert the card after the system finishes booting, but again
I'm not sure of that either. I know that removing and reinserting the card
improves things if I booted with the card inserted, but I don't remember if
removing/reinserting just once is always sufficient (it's sufficient at least
part of the time though).
This card has been having problems like this on-and-off for 3 years under both
Linux and Windows. One of 3Com's driver updates seems to have fixed things for
good a year or two back under Windows. On the Linux side, things have been up
and down a bit, with the 2.6-test kernels that I ran during severn1 (with ACPI
enabled, BTW) being flawless as far as I can remember. The last time the card
was this flaky (as 2087 or 2088) under Linux was kernel 2.2.16 or so (Red Hat 7.0).
I didn't think of disabling rhgb but I'll try that now and see how things go. I
*think* it's fixed things but it's too soon to be certain...
*** This bug has been marked as a duplicate of 98767 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.