SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello,
My computer (opensuse 10.3) is suddenly unable to connect to the network. When the computer is first switched on the hub indicates a connection between it and the computer. But part of the way through the boot process the light goes out and the network card is then unable to communicate with the network and can't get an ip address.
The device is a Realtek 8110SC/8169SC on a AMD 690V motherboard that causes problems with USB too. It says it is waiting for dhcpd but the there appears to be no connection with the hub.
Other devices work through the hub I suspect either a hardware failure or an update has killed the card.
The device is a Realtek 8110SC/8169SC on a AMD 690V motherboard that causes problems with USB too. It says it is waiting for dhcpd but the there appears to be no connection with the hub.
What does the output of "lspci" show? Also run "lspci -n" to get the vendor:devicid list. See if the "vendor:deviceid" pair that corresponds to your network device is in "/lib/modules/`uname -r`/modules.pcimap". If not, you do not have a driver for that NIC.
I will check this when I get home. Could this cause the NIC to work one day and not the next?
So you were able to get traffic through the NIC one day, and not the next? If so, you may have blown the port on the NIC, or on the switch, or both.
I static zapped a port on a switch and on my laptop (at the other end of a 15 foot Cat5 cable) during the winter here. Still couldn't convince my boss that we needed some anti-static protection. Finally we hired a hardware guy and they listened to him.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.