From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031014 Firebird/0.7+ Description of problem: I have a Compal ACL10 laptop with built in Realtek 8139 ethernet and a Gemtek Prism 2.5 wavelan PCI card (driver orinoco_pci). By default, kudzu maps both devices to be "eth0", and only by manually editing modules.conf (adding an "alias eth1 orinoco_pci" line) can I separate the two. This is the output after editing the modules.conf file - not that it now thinks it is "eth2" for some vaguely frightening reason; it is mapped to be eth1 in modules.conf (and is working as such as I write). # kudzu -p -c NETWORK - class: NETWORK bus: PCI detached: 0 device: eth0 driver: 8139too desc: "Realtek|RTL-8139/8139C/8139C+" network.hwaddr: 00:02:3F:B0:75:9C vendorId: 10ec deviceId: 8139 subVendorId: 14c0 subDeviceId: 0012 pciType: 1 pcibus: 2 pcidev: 1 pcifn: 0 - class: NETWORK bus: PCI detached: 0 device: eth2 driver: orinoco_pci desc: "Harris Semiconductor|Prism 2.5 Wavelan chipset" vendorId: 1260 deviceId: 3873 subVendorId: 1260 subDeviceId: 3873 pciType: 1 pcibus: 2 pcidev: 2 pcifn: 0 Version-Release number of selected component (if applicable): kudzu-1.1.35-1 How reproducible: Always Steps to Reproduce: It just happens by default for me. Actual Results: Mapped to the same device. Expected Results: Mapped to different devices. Additional info: The description says it all, really.
Please try the kudzu-1.1.36.1-1 packages at: http://people.redhat.com/notting/kudzu/ These may resolve some of your issues.
Same problem on Thinkpad T23. Fixing /etc/modules.conf doesn't fix it if you want to use redhat- config-network, which runs kudzu -p. When I compile both the wired and wireless as modules, I see that the wireless is probed as eth0 at boot time, then the wired is probed as eth1, then (both are unloaded, I assume) then the wired is probed as eth0. In other words, if only one module is loaded, it becomes eth0. I'll attach the dmesg output. Maybe that confuses kudzu? Does it probe one device at a time? I'm already using 1.1.36-1.
Created attachment 97824 [details] my dmesg when both are compiled as modules
Also, when I compile both into the kernel (the e100 and the orinoco_pci, that is), kudzu will still probe both on eth0. If I remove my /etc/sysconfig/hwconf file (and all ifcfg-* files in /etc/sysconfig/network-script, and everything in /etc/sysconfig/networking) and reboot, kudzu will say that a Prism2 card was removed (how the hell does it know that without a hwconf? It should have no memory whatsoever). When I say, okay, keep configuration it tells that me that a Prism2 card was added. When I say "ignore" it creates an entry for eth2 in hwconf. Obviously "keep configuration" and "ignore" don't do what they say they do. Where, btw, does kudzu keep track of whether the user asked it to ignore something? There doesn't seem to be field in hwconf.
Does the patch in #119655 help? I had the same problem - since fixing the problem I found & reported there & retesting w/ my Orinoco card, it looks to have gone away.
I'm having a similar problem with my Sony Vaio PCG-SRX77P, but since both wired and wireless are built into this system, I can't simply remove a card to get it to work right. There are also problems with the insistence by kudzu network setups of storing the MAC address in the /etc/sysconfig/network- scripts/ifcfg-eth* files. This makes swapping out PC cards particularly adventuresome, since the old MAC address doesn't properly get flushed when you cnage devices or re-arrange which eth* device is which and makes it refuse to even shut down the previously active driver.
Please try the test rpms at: http://people.redhat.com/notting/kudzu/
This should be resolved as of FC4.