Hide Forgot
I recently installed RH6.1 on a home PC that's chock full of cards. I had my Intel 82557 based NIC configured to share an IRQ with my AHA-3940UW. It seems that kudzu couldn't handle this, as it never found my NIC. When I moved things around to put that card on it's own IRQ, it seemed to be detected and work properly. I shuffeled things around again, and with Donal Beckers help, got my NIC working with a shared IRQ, and kept my other devices running. I can probably reproduce this problem by installing RH6.1 on another partition, and I can provide a full hardware list upon request.
When they're set to share an IRQ, what does 'lspci' say?
[gleblanc@peecee gleblanc]# lspci 00:00.0 Host bridge: Acer Laboratories Inc. M1541 (rev 04) 00:01.0 PCI bridge: Acer Laboratories Inc. M5243 (rev 04) 00:02.0 USB Controller: Acer Laboratories Inc. M5237 (rev 03) 00:07.0 ISA bridge: Acer Laboratories Inc. M1533 (rev b4) 00:0e.0 Ethernet controller: Intel Corporation 82557 (rev 01) 00:0f.0 IDE interface: Acer Laboratories Inc. M5229 (rev 20) 00:12.0 PCI bridge: Digital Equipment Corporation DECchip 21050 (rev 02) 01:00.0 VGA compatible controller: ATI Technologies Inc 215GB [Mach64 GB] (rev 5c) 02:04.0 SCSI storage controller: Adaptec AIC-7882U 02:05.0 SCSI storage controller: Adaptec AIC-7882U [gleblanc@peecee gleblanc]# Don't understand it all, but there it is.
Odd, it appears there in the PCI scan, so it should show up in the probe. I take it this is completely repeatable? Did the installer detect the nic?
I repeated it with two or three attempts at installing RH6.1. The installer did not detect the NIC, but I was able to install it using both LinuxConf (ugly tool that it is) and by editing the network startup scripts (/etc/sysconf/network-scripts/).
Is the only difference in /etc/sysconfig/hwconf between the case where they do and don't share IRQs the fact that the network card is missing, or are other entries missing as well?
There was a bug in the eepro driver in that it didn't like shared IRQs; I believe this was fixed in the 2.2.14 kernel.
Repoen if this persists.