Red Hat Bugzilla – Bug 128957
kudzu does not detect and configure ISAPNP 3c509
Last modified: 2014-03-16 22:47:00 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
An AMD-K6-2 (400MHz) has two ISAPNP devices, the CMI8330 audio
controller is now detected and configured but the Etherlink III
(3c509) is not detected and configured as eth1. The device does not
appear in the /etc/sysconfig/hwconf file at all; it does get detected
by the kernel during bootup.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install rawhide/development of 2004-07-29
2. install updates
3. install 3c509
Actual Results: no detection or configureation of 3c509
Expected Results: configuration as eth1
Can you tar up your /sys directory?
tar wouldn't work right for me. There is a sys.cpio.gz file at:
for your edification and retrieval
still not detected and configured by rawhide/development of 2004-08-18
I had the opportunity to remove the 3c509 card from my test system for
a while. When the system came back, I installed rawhide of 2004-09-26
without the card in the system. I then shutdown and installed the
3c509b card and rebooted.
Kudzu pased for a few moments, but still failed to detect and install
Workaround is still using system-config-network to configure the new
The link referenced above does not appear to be a valid file.
okay, here is another try at tar'ing /sys on the problem machine:
Still only get a ~1k file, which yields:
gzip: stdin: unexpected end of file
Apologies for the delay. If you've got this under a rawhide kernel, that would
be really helpful - there's been some PnP changes since then. :/
Unfortunately, I'm not using that machine and netcard as the testbed anymore.
I will try installing the 3c509 card in the new testbed as soon as I can,
probably on Monday the 26th. Sept 2005.
Finally found the 3c509b-tpo card and installed it in the test machine.
Kudzu and or other hardware detection did *not* find the card and autoconfigure
it for me. I had to bring up system-config-network and manually configure the card.
Note that this card is an ISA card, not pci.
I realize this is a repeat request, but if you can get a tarball of the /sys
directory (under a recent kernel) posted, that would be greatly appreciated.
I understand the request, but I seem to be unable to get a tarball of /sys
successfully. I've tried:
tar czvvSpf /tmp/sys.tgz /sys
but that sits and grinds for more than 15 minutes without doing anything but
fill up the /tmp partition! If you tell me how to generate exactly what you
want I'll do my best, but I'm rather frustrated at this point.
It gets to /sys/class/net/sit0/carrier and dumps forever! Is there a loop in
the symbolic links?
Trying to "cat /sys/class/net/sit0/carrier" yeilds an "invalid argument" error!
Hm, then just a tar of /sys/bus/pnp and /sys/devices/pnp* should suffice - is
tgz files of /sys/bus/pnp and /sys/devices/pnp* are at:
tar czvvSf /tmp/<file> <tree>
files are world-readable. Dated 2005-11-04 00:37.
FC5T1+rawhide of 2005-11-28 still doesn't see the 3c509 ISA Card on the work1
machine. BIOS sees the card and handles it. Should I disable BIOS PNP handling?
Workaraound is still to use system-config-network and hand enable the card.
rawhide of 2006-01-02; kernel sees ISA PNP card correctly, kudzu and anaconda
do NOT see or recognize the card as eth1.
Fc6t3: kernel sees and reports the ISA PNP card correctly. I can use
system-config-network to configure the card; however, kudzu and anaconda don't
see the card during installations.
Might want to toss this in the release-notes that ISA-PNP cards have to be
configured via s-c-network and be done with it.
I note for the record that Knoppix doesn't see the card automatically either.
Changing version to correct one. (test1 -> fc3test1, and some were filed as
test3 accidentally instead; but clearly must be fc3test1 given the date of filing.)
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?