SlackwareThis Forum is for the discussion of Slackware 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.
Check the BIOS to make sure it's not disabled, or has power saving enabled. On some systems that dual boot between Windows and Linux, Windows likes to enable power saving on some hardware (puts them to sleep). Linux has known issues waking most devices up. In the past this has plagued many on board RTL nics, and currently some Intel nics.
Check the BIOS to make sure it's not disabled, or has power saving enabled
bios has no facility for disabling lan or any power saving facilities. the bios features are very limited.
Quote:
On some systems that dual boot between Windows and Linux, Windows likes to enable power saving on some hardware (puts them to sleep)
i dont have a dual boot system... just a straight install of slackware64 13.1. there was of course a version of vista that came with the compy, maybe it put the nic to sleep permanently!
i also tried passing a few different combinations of parameters to the kernel at boot like:
nic=atl1c
ether=28,0,eth0
ether=0,0,eth0
noudev
none of them resurrected the ethernet card. also tried booting into the slackware setup dvd. "lspci" shows the same results.
im assuming my card isnt fried as it was working in vista that it first came dressed in. not sure where to go from here!
looks like you were right disturbed1. my network card was happily sleeping away until i tried this option from bios Boot Manager:
Network Boot: Atheros Boot Agent
i was hoping it might scare the card into life and apparently it did. ethernet card is now awake and breathing!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.