[opensuse] Missing eth0 interface
As I reported in a previous thread, the inability of my laptop system to see the Ethernet controller was solved, and I was able to connect with the Internet. After shutting the machine down and booting it in the morning, I found that I am no longer able to communicate with the outside world. Network Devices now reports the controller as "not connected", meaning that it can see it. (In theprevious thread, it reported that the controller was not in hwinfo.) Running ifup on the interface produced: ***** # ifup eth0 Interface eth0 is not available. ***** I have to google for help in rectifying this. I got many hits, but nothing very helpful. How can I restore eth0? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman wrote:
As I reported in a previous thread, the inability of my laptop system to see the Ethernet controller was solved, and I was able to connect with the Internet.
After shutting the machine down and booting it in the morning, I found that I am no longer able to communicate with the outside world.
Network Devices now reports the controller as "not connected", meaning that it can see it. (In theprevious thread, it reported that the controller was not in hwinfo.)
Running ifup on the interface produced:
***** # ifup eth0 Interface eth0 is not available. *****
Stan (in private discussion with me) also reported that /etc/udev/rules.d/70-persistent-net.rules is empty - AFAIK, it is automagically populated, so I don't quite understand why it would be empty. /Per -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 14:30:35 on Monday Monday 12 October 2009, Per Jessen
Stan Goodman wrote:
As I reported in a previous thread, the inability of my laptop system to see the Ethernet controller was solved, and I was able to connect with the Internet.
After shutting the machine down and booting it in the morning, I found that I am no longer able to communicate with the outside world.
Network Devices now reports the controller as "not connected", meaning that it can see it. (In theprevious thread, it reported that the controller was not in hwinfo.)
Running ifup on the interface produced:
***** # ifup eth0 Interface eth0 is not available. *****
Stan (in private discussion with me) also reported that /etc/udev/rules.d/70-persistent-net.rules is empty - AFAIK, it is automagically populated, so I don't quite understand why it would be empty.
/Per
Actually, the file I was asked to examine was . I did report it as empty, but now I check again and find that it doesn't exist at all. Overlooking vi's remark that it is New File is yet another reminder that I mustn't do this sort of thing at late hours. Now examining the file instead, I see that it is populated and has rules: ***** SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:26:b9:01:11:af", ATTR(type)=="1", KERNEL=="eth*", NAME=="eth0" ***** -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman wrote:
Actually, the file I was asked to examine was . I did report it as empty, but now I check again and find that it doesn't exist at all. Overlooking vi's remark that it is New File is yet another reminder that I mustn't do this sort of thing at late hours.
Now examining the file instead, I see that it is populated and has rules:
***** SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:26:b9:01:11:af", ATTR(type)=="1", KERNEL=="eth*", NAME=="eth0" *****
Okay, that's better. Yet you still can't bring the interface up with "ifup eth0". That would indicate that perhaps the module wasn't loaded properly. Check to see what 'lsmod' says - is "r8169" loaded? If not, try to load it with "modprobe r8169". Then check that it was loaded, and if not, use 'dmesg" to see why. The last few lines will usually tell you. /Per -- Per Jessen, Zürich (7.7°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 09:17:40 on Tuesday Tuesday 13 October 2009, Per Jessen
Stan Goodman wrote:
Actually, the file I was asked to examine was . I did report it as empty, but now I check again and find that it doesn't exist at all. Overlooking vi's remark that it is New File is yet another reminder that I mustn't do this sort of thing at late hours.
Now examining the file instead, I see that it is populated and has rules:
***** SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:26:b9:01:11:af", ATTR(type)=="1", KERNEL=="eth*", NAME=="eth0" *****
Okay, that's better. Yet you still can't bring the interface up with "ifup eth0". That would indicate that perhaps the module wasn't loaded properly. Check to see what 'lsmod' says - is "r8169" loaded? If not, try to load it with "modprobe r8169". Then check that it was loaded, and if not, use 'dmesg" to see why. The last few lines will usually tell you.
Actually, what I had installed was r8168. But neither of the two appeared in the lsmod list. I ran modprobe r8168, which says "FETAL: Module r8168 not found". Running modprobe rr8169 gave no response at all, which sounded better, and r8169 does appear in the lsmod list; it has "0" users. The network, is still unreachable, even after reboot.
/Per
-- Per Jessen, Zürich (7.7°C)
-- Stan Goodman Qiryat Tiv'on (32C Today, 36C for Friday) Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman wrote:
Okay, that's better. Yet you still can't bring the interface up with "ifup eth0". That would indicate that perhaps the module wasn't loaded properly. Check to see what 'lsmod' says - is "r8169" loaded? If not, try to load it with "modprobe r8169". Then check that it was loaded, and if not, use 'dmesg" to see why. The last few lines will usually tell you.
Actually, what I had installed was r8168. But neither of the two appeared in the lsmod list. I ran modprobe r8168, which says "FETAL: Module r8168 not found".
Okay, so no such module. I'm pretty certain r8169 will support the r8168 chip too.
Running modprobe rr8169 gave no response at all, which sounded better, and r8169 does appear in the lsmod list; it has "0" users.
Very good - so the module can be loaded. At this point, did you try "ifup eth0"? /Per -- Per Jessen, Zürich (7.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 10:03:53 on Tuesday Tuesday 13 October 2009, Per Jessen
Stan Goodman wrote:
Okay, that's better. Yet you still can't bring the interface up with "ifup eth0". That would indicate that perhaps the module wasn't loaded properly. Check to see what 'lsmod' says - is "r8169" loaded? If not, try to load it with "modprobe r8169". Then check that it was loaded, and if not, use 'dmesg" to see why. The last few lines will usually tell you.
Actually, what I had installed was r8168. But neither of the two appeared in the lsmod list. I ran modprobe r8168, which says "FETAL: Module r8168 not found".
Okay, so no such module. I'm pretty certain r8169 will support the r8168 chip too.
Running modprobe rr8169 gave no response at all, which sounded better, and r8169 does appear in the lsmod list; it has "0" users.
Very good - so the module can be loaded. At this point, did you try "ifup eth0"?
I did: "Interface eth0 is not available". -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman wrote:
At 10:03:53 on Tuesday Tuesday 13 October 2009, Per Jessen
wrote: Stan Goodman wrote:
Okay, that's better. Yet you still can't bring the interface up with "ifup eth0". That would indicate that perhaps the module wasn't loaded properly. Check to see what 'lsmod' says - is "r8169" loaded? If not, try to load it with "modprobe r8169". Then check that it was loaded, and if not, use 'dmesg" to see why. The last few lines will usually tell you.
Actually, what I had installed was r8168. But neither of the two appeared in the lsmod list. I ran modprobe r8168, which says "FETAL: Module r8168 not found".
Okay, so no such module. I'm pretty certain r8169 will support the r8168 chip too.
Running modprobe rr8169 gave no response at all, which sounded better, and r8169 does appear in the lsmod list; it has "0" users.
Very good - so the module can be loaded. At this point, did you try "ifup eth0"?
I did: "Interface eth0 is not available".
Okay. Can you post the last 20-30 lines of the 'dmesg' output? Either to pastebin.com or directly to the list. I want to see if the module complained about anything when you loaded it. Also, what does "ls -l /etc/sysconfig/network/ifcfg*" say? I'm slowly beginning to suspect the card may not have been configured at all. /Per -- Per Jessen, Zürich (8.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 10:26:20 on Tuesday Tuesday 13 October 2009, Per Jessen
Stan Goodman wrote:
At 10:03:53 on Tuesday Tuesday 13 October 2009, Per Jessen
wrote: Stan Goodman wrote:
Okay, that's better. Yet you still can't bring the interface up with "ifup eth0". That would indicate that perhaps the module wasn't loaded properly. Check to see what 'lsmod' says - is "r8169" loaded? If not, try to load it with "modprobe r8169". Then check that it was loaded, and if not, use 'dmesg" to see why. The last few lines will usually tell you.
Actually, what I had installed was r8168. But neither of the two appeared in the lsmod list. I ran modprobe r8168, which says "FETAL: Module r8168 not found".
Okay, so no such module. I'm pretty certain r8169 will support the r8168 chip too.
Running modprobe rr8169 gave no response at all, which sounded better, and r8169 does appear in the lsmod list; it has "0" users.
Very good - so the module can be loaded. At this point, did you try "ifup eth0"?
I did: "Interface eth0 is not available".
Okay. Can you post the last 20-30 lines of the 'dmesg' output? Either to pastebin.com or directly to the list. I want to see if the module complained about anything when you loaded it.
*****
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
fuse init (API version 7.9)
type=1505 audit(1255423490.632:2): operation="profile_load"
name="/bin/ping" name2="default" pid=1950
type=1505 audit(1255423490.696:3): operation="profile_load"
name="/sbin/klogd" name2="default" pid=2009
type=1505 audit(1255423490.764:4): operation="profile_load"
name="/sbin/syslog-ng" name2="default" pid=2013
type=1505 audit(1255423490.828:5): operation="profile_load"
name="/sbin/syslogd" name2="default" pid=2042
type=1505 audit(1255423490.892:6): operation="profile_load"
name="/usr/sbin/avahi-daemon" name2="default" pid=2055
type=1505 audit(1255423490.989:7): operation="profile_load"
name="/usr/sbin/identd" name2="default" pid=2070
type=1505 audit(1255423491.045:8): operation="profile_load"
name="/usr/sbin/mdnsd" name2="default" pid=2071
type=1505 audit(1255423491.129:9): operation="profile_load"
name="/usr/sbin/nscd" name2="default" pid=2072
type=1505 audit(1255423491.213:10): operation="profile_load"
name="/usr/sbin/ntpd" name2="default" pid=2073
type=1505 audit(1255423491.269:11): operation="profile_load"
name="/usr/sbin/traceroute" name2="default" pid=2074
IA-32 Microcode Update Driver: v1.14a
Also, what does "ls -l /etc/sysconfig/network/ifcfg*" say? I'm slowly beginning to suspect the card may not have been configured at all.
***** # ls -l /etc/sysconfig/network/ifcfg* -rw-r--r-- 1 root root 219 2009-10-12 15:08 /etc/sysconfig/network/ifcfg-eth0 -rw-r--r-- 1 root root 174 2008-12-03 12:45 /etc/sysconfig/network/ifcfg-lo -rw-r--r-- 1 root root 27605 2008-12-03 12:45 /etc/sysconfig/network/ifcfg.template ***** How is it possible that it was never configured? It worked until I rebooted. Was there a place where I should have saved the configuration explicitly, and I missed it?
/Per
-- Per Jessen, Zürich (8.2°C)
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman wrote:
Okay. Can you post the last 20-30 lines of the 'dmesg' output? Either to pastebin.com or directly to the list. I want to see if the module complained about anything when you loaded it.
***** [snip] *****
That didn't look like the last 20-30 lines, but like some of the first - there was no mention of the module being loaded.
Also, what does "ls -l /etc/sysconfig/network/ifcfg*" say? I'm slowly beginning to suspect the card may not have been configured at all.
***** # ls -l /etc/sysconfig/network/ifcfg* -rw-r--r-- 1 root root 219 2009-10-12 15:08 /etc/sysconfig/network/ifcfg-eth0 -rw-r--r-- 1 root root 174 2008-12-03
Okay.
How is it possible that it was never configured?
I don't know, but "when you have eliminated the impossible, whatever remains, however improbable, must be the truth". Anyway, we've checked the following: 1) that the NIC exists and works. 2) that the module exists and can be loaded. (I think) 3) that you have a udev rule for giving it a device name 4) that you have a network config (ifcfg-eth0) for it. And yet when you run "ifup eth0" is says "Interface eth0 is not available". -- Per Jessen, Zürich (8.5°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
And yet when you run "ifup eth0" is says "Interface eth0 is not available".
The /sbin/ifup script uses a function is_iface_available which is defined in /etc/sysconfig/network/scripts/functions - afaict, this function returns 0 because it can't find "/sys/class/net/eth0". Can you check if that is present on your system? /Per -- Per Jessen, Zürich (8.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 12:10:19 on Tuesday Tuesday 13 October 2009, Per Jessen
Stan Goodman wrote:
Okay. Can you post the last 20-30 lines of the 'dmesg' output? Either to pastebin.com or directly to the list. I want to see if the module complained about anything when you loaded it.
*****
[snip]
*****
That didn't look like the last 20-30 lines, but like some of the first - there was no mention of the module being loaded.
Nevertheless, those were the last lines in the output, as you can see from noting the command prompt at the end. The first lines look entirely different. And I can verify that the string "r8" occurs only once in the file, in an entirely different connection. Neither does "eth0". But again, the NIC worked, and I was able to visit the LAN and the 'Net, until I rebooted.
Also, what does "ls -l /etc/sysconfig/network/ifcfg*" say? I'm slowly beginning to suspect the card may not have been configured at all.
***** # ls -l /etc/sysconfig/network/ifcfg* -rw-r--r-- 1 root root 219 2009-10-12 15:08 /etc/sysconfig/network/ifcfg-eth0 -rw-r--r-- 1 root root 174 2008-12-03
Okay.
How is it possible that it was never configured?
I don't know, but "when you have eliminated the impossible, whatever remains, however improbable, must be the truth".
Elementary, my dear Watson. And from that I deduce that you have been in Meringen.
Anyway, we've checked the following:
1) that the NIC exists and works. 2) that the module exists and can be loaded. (I think) 3) that you have a udev rule for giving it a device name 4) that you have a network config (ifcfg-eth0) for it.
And yet when you run "ifup eth0" is says "Interface eth0 is not available".
-- Per Jessen, Zürich (8.5°C)
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman wrote:
That didn't look like the last 20-30 lines, but like some of the first - there was no mention of the module being loaded.
Nevertheless, those were the last lines in the output, as you can see from noting the command prompt at the end. The first lines look entirely different.
And I can verify that the string "r8" occurs only once in the file, in an entirely different connection. Neither does "eth0".
I have justed checked a couple of my production machines which also use the R816X chip: 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) 00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) They both use the r8169 driver - looking through my dmesg output (on a recently rebooted machine) I see e.g.: r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded eth0: RTL8168c/8111c at 0xf8884000, 00:24:21:5f:1a:b0, XID 3c4000c0 IRQ 218 r8169: eth0: link up Granted, this is openSUSE 11.0, kernel 2.6.25.5-1.1-pae so maybe your dmesg will look slightly different. If the module loads properly (like you said it did), I'm sure you'll something like the above. -- Per Jessen, Zürich (10.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 14:22:46 on Tuesday Tuesday 13 October 2009, Per Jessen
Stan Goodman wrote:
That didn't look like the last 20-30 lines, but like some of the first - there was no mention of the module being loaded.
Nevertheless, those were the last lines in the output, as you can see from noting the command prompt at the end. The first lines look entirely different.
And I can verify that the string "r8" occurs only once in the file, in an entirely different connection. Neither does "eth0".
I have justed checked a couple of my production machines which also use the R816X chip:
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
That is the controller that is in this machine.
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
They both use the r8169 driver - looking through my dmesg output (on a recently rebooted machine) I see e.g.:
r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded eth0: RTL8168c/8111c at 0xf8884000, 00:24:21:5f:1a:b0, XID 3c4000c0 IRQ 218 r8169: eth0: link up
Granted, this is openSUSE 11.0, kernel 2.6.25.5-1.1-pae so maybe your dmesg will look slightly different. If the module loads properly (like you said it did), I'm sure you'll something like the above.
As I said, there is nothing like that in dmesg. I'll try to reinstall the driver, and hope it takes this time. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman wrote:
They both use the r8169 driver - looking through my dmesg output (on a recently rebooted machine) I see e.g.:
r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded eth0: RTL8168c/8111c at 0xf8884000, 00:24:21:5f:1a:b0, XID 3c4000c0 IRQ 218 r8169: eth0: link up
Granted, this is openSUSE 11.0, kernel 2.6.25.5-1.1-pae so maybe your dmesg will look slightly different. If the module loads properly (like you said it did), I'm sure you'll something like the above.
As I said, there is nothing like that in dmesg. I'll try to reinstall the driver, and hope it takes this time.
Hmm, I've just tried loading that module on a machine that does not have such an interface. The module loads just fine (i.e. modprobe doesn't complain), but as it doesn't find the card, there's nothing to be seen in dmesg. We have already verified that the card is present in your machine, so why it isn't recognized by the driver, I simply don't know. /Per -- Per Jessen, Zürich (10.7°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 15:05:59 on Tuesday Tuesday 13 October 2009, Per Jessen
Stan Goodman wrote:
They both use the r8169 driver - looking through my dmesg output (on a recently rebooted machine) I see e.g.:
r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded eth0: RTL8168c/8111c at 0xf8884000, 00:24:21:5f:1a:b0, XID 3c4000c0 IRQ 218 r8169: eth0: link up
Granted, this is openSUSE 11.0, kernel 2.6.25.5-1.1-pae so maybe your dmesg will look slightly different. If the module loads properly (like you said it did), I'm sure you'll something like the above.
As I said, there is nothing like that in dmesg. I'll try to reinstall the driver, and hope it takes this time.
Hmm, I've just tried loading that module on a machine that does not have such an interface. The module loads just fine (i.e. modprobe doesn't complain), but as it doesn't find the card, there's nothing to be seen in dmesg. We have already verified that the card is present in your machine, so why it isn't recognized by the driver, I simply don't know.
Perhaps I zigged at some point when I should have zagged. It wouldn't be the first time. I'm going to try now to install it again. As you see, by the way, my regular email account recovered this morning, as spontaneously as it froze the previous day. I am perfectly sure that the problem was at the hosting service, and had nothing to do with me. The hosting service, of course, thinks otherwise. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Per Jessen
-
Stan Goodman