No power management/ACPI on Toshiba Satellite L500D
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
No power management/ACPI on Toshiba Satellite L500D
When I try to boot pretty much any Linux on my Toshiba Satellite laptop, I see a whole bunch of ACPI errors and then a kernel panic. Boot fails. When I boot with the option acpi=off, it boots just fine except that cpu throttling, fan speed control, and multi-core support (It's a dual-core AMD Turion Mobile M520)are unavailable. I have tried VectorLinux (slackware based), Ubuntu, Fedora, and BlueWhite64 Linux. None of them were able to make any of the above things work. There is almost nothing about power management or ACPI in the BIOS. Can anybody help with this? I can provide more information if needed. Thanks.
I didn't see anything in the BIOS for power management except for CPU frequency scaling which was enabled. I didn't see anything about pnp os either. I have tried both 32 and 64 bit kernels. I even compiled my own kernel and tried adding acpi support modules and stuff but it didn't really help. I would like to get acpi working, but if I can't, I would like a way to idle the cpu and fan so that I could close the laptop up, put it in my backpack, and take it somewhere else without it roasting inside the bag on the way.
I've done that already with acpi=off as a boot parameter. How would I get apm working? When I try to run apmd as root, it says "no apm support in kernel". Would I need to recompile the kernel again with apm stuff?
If it is apm (which seems a plausible reason), where should I go from there?
Try building a kernel with Toshiba Laptop Extras. This is under "X86 Platform Specific Drivers"; it is only listed when some other options have been set. Clues in /usr/src/linux/drivers/platform/x86/Kconfig or here.
I suggested the old knoppix since it was built about that time and may have offered clues to apm or acpi. I still can't tell if either are well supported but the old knoppix ought to boot. Matter of fact the system would seem to me to be new enough to boot anyway on a newer distro.
Faced the same problem when trying to install SuSE or Ubuntu on my wife's then new Toshiba laptop. Amongst the many things I tries was recompiling the kernel which (under Ubuntu) this fixed the ACPI errors and restored functionality to the function keys, the downside was that the NIC started behaving erratically, an endless loop of unpredictable connect/disconnect cycle.
One of the possible explanations I found for not having a permanent fix (this was several months ago and things might have changed) was that in that series Toshiba used H2O bios which according to what I read passes erroneous address information for certain devices/buses which results in a conflict of address assignments which caused s the kernel to 'panic'. Recompiling the kernel with what ever modules that were involved only allowed the kernel to force the correct address assignment (i.e. ignore what the bios was saying) but at the expense of the NIC. Unfortunately after a few days my wife was running out of patience and needed her a functional laptop so I stopped trying and reinstalled the annoying Win 7 which came with the laptop for her.
If your laptop has the H2o bios, you may want to explore this rout further and try to find exactly how it's doing what it's doing wrong and go from there by either looking for a fix (if there is one) or coming up with one yourself.