Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
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.
There is a newer firmware for the realtek 8168 and so I updated to use that new firmware. After rebooting I got no link-light. I feared that I may have bricked my ethernet controller. So I reflashed the bios and reverted to the previous ethernet firmware. But still no link-light. Okay so I powered down the system and rebooted. Still no link-light. Changed the ethernet cable. Still not working. Finally I unplugged the PSU and bled off any capacitor storage. Powered it back up and now I got a link-light.
Just posting this in case you have one of these realtek ethernet controllers. Mine is built-in. I do not know if this is particular to realtek or not but I suspect that it is.
Actually kernel driver has the ability to load firmware. Firmware must be provided by user, of course. Kernel has no 8168 driver, so in most cases 8169 driver is used instead. You can inspect your dmesg to see if the driver is requesting firmware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.