Description of problem: After upgrading from RHL 7.3 to FC1, kudzu detects that Elsa PCI ISDN card is a network adaptor and suggested to use it for "eth0"...which not matches the reality. Probably on a fresh install the result is the same. Version-Release number of selected component (if applicable): kudzu-1.1.36-1 How reproducible: Always Steps to Reproduce: 1. Use a system with an Elsa PCI ISDN card 2. Install FC1 Actual Results: kudzu suggest it using as "eth0" Expected Results: Not using it as "eth0", makes no sense. Additional info: Here are the related information from "kudzu -p" class: NETWORK bus: PCI detached: 0 device: eth0 driver: hisax desc: "Elsa AG|QuickStep 1000" vendorId: 1048 deviceId: 1000 subVendorId: 1048 subDeviceId: 1000 pciType: 1 pcibus: 0 pcidev: f pcifn: 0 I know, that also on W* system, the card is detected as network card, but a dump "is network card, use it for eth0" is not so well here. Perhaps kudzu can recognize that if the driver is not out of the network driver dir, skip this card.
NETWORK comes from the pci class of the device. The fun part is that if you exclude the generic network class, you lose PCI wireless cards. If you *include* it, you get ISDN adapters and the like.
Hmm, who tells kudzu that it should use the "hisax" driver? By PCI id? If yes, perhaps a black-list is needed...
Yes, it pulls it from modules.pcimap.
*** Bug 120319 has been marked as a duplicate of this bug. ***
Looks like it's solved in FC2.
Odd, I didn't change anything. Is the driver actually built?
Closing; this class match is needed for wireless cards.