I’d like to apologize in advance if this topic has been posted before, but I’ll give it a try.
I’m currently using SuSE 11.4 and after running the full online updates and restarting the machine as YAST suggested, I no longer have eth0/eth1 available.
I’m clueless about what to do since I’m kinda new to Linux and at the moment, I’m trying out all the distros before making a full commitment to anyone. So far, Ubuntu has been trouble-free from day one, but I’m willing to give this distro (opensuse) some slack.
Sorry for the late reply and thanks for your time.
This is what I got from what you suggested me:
/sbin/ifconfig
Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:340 (340.0 b) TX bytes:340 (340.0 b)
/sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
cat /etc/resolv.conf
/etc/resolv.conf file autogenerated by netconfig!
Before you change this file manually, consider to define the
static DNS configuration using the following variables in the
/etc/sysconfig/network/config file:
NETCONFIG_DNS_STATIC_SEARCHLIST
NETCONFIG_DNS_STATIC_SERVERS
NETCONFIG_DNS_FORWARDER
or disable DNS configuration updates via netconfig by setting:
NETCONFIG_DNS_POLICY=’’
See also the netconfig(8) manual page and other documentation.
Note: Manual change of this file disables netconfig too, but
may get lost when this file contains comments or empty lines
only, the netconfig settings are same with settings in this
file and in case of a “netconfig update -f” call.
Please remove (at least) this line when you modify the file!
search site
What’s weird is that my eth0 was available before I installed this major update from YAST online update which took almost 4 hours to complete. After I restarted the machine, no internet, no network, nothing…
As a side note, my ethernet device is a Realtek RTL8139/810x (according to windows device manager).
AFAIU, the ‘r8168’ driver should be ok. (Although, I have seen reports that some 8168b chipsets require the ‘r8169’ driver instead. Maybe one of the gurus can answer this more definitively here.
If not present, use the software search tool to download the appropriate packages (including the appropriate kernel package):
Edit: This thread discussing a Dell machine with the same ethernet chipset, has an lspci entry showing that the r8169 driver is in use. So give that a go first.
shows that this NIC should work with the r8169 driver. The only difference is “rev 02” (yours) against “rev 03” (mine). What happens when you try to activate the NIC in Yast?
Thanks for your valuable help guys. When I have a little chance (since I’ve been kinda busy), I’ll download the driver for the realtek NIC and install it and see what happens.
And about the FATAL error, I’m clueless on how to solve that one.
EDIT: Would I need to install ALL NIC devices on whichever machine I’ll be using? (I’m using a live distro on my USB drive)
For some mysterious reason, my Live USB won’t boot anymore.
Anyhow, it’s the second time this incident happened whenever I install all online updates through Yast. If I’m not wrong, I guess there’s a kernel update which seems to be crapping out my Live Gnome ethernet drivers. I might just avoid running Yast update at all costs or just install the necessary modules.
It’s possible. To make sure You can taboo the kernel update or You can enable kernel multiversion in zypper config. That way instalation of a new kernel won’t erase the old one and You will have a choice of all the kernels. I don’t remember the name of the zypper config file and I’m not at my openSUSE at the moment but I’m sure You can find it somwhere in the forums. If not just say so here and I’ll post here the exact name of the file once I get to my system.
