Red Hat Bugzilla – Bug 56647
ethernet hardware not detected after upgrade
Last modified: 2015-03-04 20:09:57 EST
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 4.0; Q312461) Description of problem: neat does not detect my network card. It is detected by kudzu correctly, but I have tried 2 different cards neither of which is detected by neat. The same hardware configuration work for a fresh install. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. upgrade to RH7.2 from RH6.2 2. run neat 3. attempt to add an ethernet device Actual Results: The device is not detected and an error message is produced: The Ethernet card could net be initialized. Please verify your settings and try again. running ifup eth0 fails. Expected Results: Card is detected and the interface is initialised. Additional info: The cards are configured correctly and always worked on RH6.2. Another person with identical hardware has successfully installed RH7.2. Not even my lo device and routes are not initialised. using ifup eth0 fails with and error message: Cannot send dump request: Connection refused I can configure the interface manually using ifconfig lo 127.0.0.1/8 up ifconfig eth0 broadcast 10.3.100.255 10.3.100.53/24 up route add -net 127.0.0.0/8 lo route add default gw 10.3.100.1 These ifconfig commands produce error: cannot assign network address but they work and if run a second time no errors are produced. everything works fine except the dns updates for the dhcp client on eth0. These keep resetting themselves and I must run pump once or twice. I have tried with a kernel which has only the correct ethernet device compiled.
In the ifup script, I have narrowed the error down to this statement: [root@rhl etc]# /sbin/ip -o link show eth0 Cannot send dump request: Connection refused and I get the same result for lo [root@rhl etc]# /sbin/ip -o link show lo Cannot send dump request: Connection refused There is no manual on this command so I don't know how to fix this.
I solved this problem by compiling kernel netlink user device allowing /sbin/ip to run without errors. I still think this is a bug that should be fixed. My old kernel didn't use the netlink device but the new one requires it and the upgrade does not take this into account.
Similar bug with Intel EtherExpress Pro 100B after installing RH 7.2 (and upgrading to 2.4.9-13): Attempted to add network device using GNOME Network Configuration tool. Received error message: "The Ethernet card could not be initialized. Please verify your settings and try again." Disabled adapter, rebooted, and removed configuration in Kudzu. Re-enabled adapter, rebooted, skipped Kudzu, and tried to add network device. Same error message. Rebooted, configured network using Kudzu. No problems. Result: Adding a network card fails using Network Configuration, but works using Kudzu.
Can you try the new rpms of redhat-config-network from http://people.redhat.com/teg/neat/ and see if they help?
I updated to redhat-config-network-0.9.9-0.1 and attempted to add the ethernet using Network Configuration. eth0 automatically appears under the "Devices" tab, but not under "Hardware". I add the the device under "Hardware" and the error message appears again, but eth0 is still added anyways.
I updated to redhat-config-network-0.9.9-0.1 and attempted to add the ethernet using Network Configuration too. I got the same result, which is better than before as the hardware is added now, but still shows the same error message.
After a laptop install on a Dell C600 with internal wireless and Xircom NIC/Modem, eth0 does not show up under the devices tab but Wireless does. I add a three line ifcfg-eth0 file to /etc/sysconfig/network-scripts and then eth0 shows up in the devices tab and I can configure it. I configured the wireless card as eth1. ONBOOT=no in /etc/sysconfig/network-scripts/ifcfg-eth1 does not work.
Still not fixed with redhat-config-network-0.9.10-2
this is your part, pknirsch :)
Harold, Would you mind being a bit more specific. What exaclty is my part and what can I do to fix it?
sorry, huge, I meant pknirsch@redhat.com whom you will find on the CC list of this bug.
Ok, the hardware gets detected by scanning /etc/modules.conf. Normally there are lines like: alias eth3 3c59x Which gives redhat-config-network the hint, which card is used for which device. So could you guys please check, if there are such lines in modules.conf?
There is such a line in the modules.conf. This may have been added by neat. alias eth0 3c59x Problem is I do not use modules for this device. My hardware driver is compiled into the kernel. I use a 3c905C-TX [Fast Etherlink] (rev 116). Since I fixed this manually the device is present and working, but when I try to detect it, neat reports that the ethernet card could not be initialised and that I should verify my settings and try again. It adds the interface anyway though, and it works fine. My latest kernel is 2.4.9-21 and neat redhat-config-network-0.9.10-2.
System running redhat-config-network-0.9.18-1 and attempted to add the ethernet using Network Configuration. eth0 automatically appears under the "Devices" and "Hardware" tabs. No error message. eth configured successfully. redhat-config-network-0.9.20-1.i386.rpm is now available at: http://people.redhat.com/teg/neat/
Closing as fixed in response to above comment.