Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
I put in the Ubuntu 9.04 CD. On the install splash screen I chose F6 for the options and checked noacpi. I selected install without changing your computer. I HAD INTERNET. I restarted and installed with the same option selected and so far, so good.
It seems as though things are back to normal.
WHEW! One week without a computer is weird now.
Thanx for the help.
Last edited by ben44b; 07-26-2009 at 08:53 PM.
Reason: no message
Cool - though you could have done this by editing /boot/grub/menu.lst
What we've done, likely, is established that acpi is the problem.
Booting "noacpi" means that your fan will always run etc. Anything relying on power management will not work. For laptops, this can be pretty sucky but if you don't mind then that's as far as you need go.
If you want power management, then you'll have to supply, and/or repair, the DSDT table which linux reports as missing. The acpi project often has working dsdt for download. But this is pretty much advanced-end work. It is just sad that some vendors provide the things needed for acpi to work in a non-standard place (i.e. so only windows will work).
However - I often find that entering bios setup and disabling all the "advanced power" features does wonders. Often the advanced features in the bios are only needed to make up for deficiencies in windows. With your particular problem, there is often a power management option where you configure network devices. It may just be that bios put your nic to sleep when it was unused and the kernel could not turn it on.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.