Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
When I reinstalled my laptop I tried getting ACPI sleep to work with no success. Now I decided to try again. I have upgraded some software in the hope that it would solve the problems but unfortunately not. Can anyone point me in the right direction here?
# echo 3 > /proc/acpi/sleep
puts computer to sleep. Powering it up again causes it to crash badly. Not even caps lock LED:s are working. Screen is blank, etc.
I don't even know how to find out where the crash did occur. Without any error message it's like a needle in a haystack.
I know that the last time I tried I got the computer to wake up and respond to ping but then the graphics was totally corrupted until I cycled power to the computer.
Why is it so damn hard to get this seemingly trivial function to work? For mobile users it is a major factor in switching over to linux.
System: Dell Inspiron 8600 (P-M 1.4 GHz, ATI Radeon 9600)
hmmm first of all, have you tried to put it on sleep using /sys instead of /proc?
Putting my laptop to sleep using /proc/acpi/sleep was leading my laptop into problem but it works fine if I do this with /sys/power/state. Try echo "standby" > /sys/power/state
Hmmm also, you were using "S3" sleep, which is "suspend to ram" if I remember right. This is probably less reliable than the good ol' "standby". If you want something "better" I suggest you to download and install "swsusp2" which is the new version of "suspend-to-disk". It was quite reliable with kernel < 2.6.8 (there seem to be some bug in earlier kernel).
ACPI is really complex, very few laptop are exactly following the standard so kernel developper have hard time supporting every single model, since very few company release strong specifications of their ACPI implementation.
Thank you for the tip. I will try /sys/power/state when I'm get to my own computer.
I don't know what you mean by "the good ol' standby", but yes it is suspend to ram I want. Suspend to disk (S5) would be acceptable but it doesn't work at all on my laptop (nothing happens -- could be that I have upgraded the HD so the "Dell" partition is now gone). I have never heard of other sleep modes (not counting the powersave that just turns off the LCD panel and HD).
Update: I wanted to try echo standby > /sys/power/state so I hurried to my computer . What happened was that my power LED started flashing in a strange way (short, "hard" flashes instead of the ordinary fading-style flash like in sleep mode). And the computer didn't turn off (maybe the harddrive turned off but not the LCD). Pressing the power button made it crash (it outputted something that looked like a kernel stacktrace containing calls like acpi_wakeup or something like that -- by the way are these stacktraces stored somewhere in case of a crash? I would really want to have a look at where the crash happened). I also tried echoing mem to /sys/power/state. Then it went to sleep as usual but didn't wake up (exactly the same as with the /proc counterpart).
Hmmmm look like you have some broken ACPI or some unsupported one.
There's not much you could do.... I suggest you to post a bug report to ACPI developper ( try : http://bugme.osdl.org/enter_bug.cgi?product=ACPI ). If you want to try, you might be able to use suspend-to-disk anyways.
Btw, sometime ACPI failed because of some hardwares... if you really want to give a try, you could recompilate your kernel removing every optionnal feature to see if that help
If I should even consider writing a bug report, I need at least some kind of info. Which brings me back to the question, can I save that stackdump somehow? I guess the suspend-to-ram wakeup produces the same or a similar output but I cannot see it because the LCD is turned off.
The thing is, I know people with Dell laptops that have succeeded in putting their computers to sleep (or more importantly, waking them up afterwards!), so I don't think this is a bug. Some driver incompatibility maybe? In that case, I need to know which driver so I can try to upgrade it or even disable it.
I dont think stacktrace are wrote into a log file.... you could try to raise up your kernel logging in /etc/syslog.conf (assuming you are running syslogd) (create a line like *.* /var/log/all ) but I doubt it will do it... can't you just copy and paste it to a file?
About the driver incompatibility... well, unless the stacktrace gave you some info, the only thing you can do is guess... like disabling all device (by removing these from kernel) and trying to sleep. Then adding few one and trying again... there's no miracle :s
Problem is, the interesting lines fall off the screen. And there is nothing I can do since the computer has crashed by then and won't respond to keyboard. Otherwise I could always use my digital camera to take a picture of it but the bottom of the stack isn't that interesting as the last line shown is still some generic acpi function and not anything specific.
Also about syslog, I think that service is pretty much terminated when this happens. I was thinking of something more low-level. Isn't there some way of forcing kernel output to a file (for example, adding something like insanedebugoutput=/var/log/lotsoftext.log to the grub command line) ?
It is easily worth recompiling the kernel to fix this problem but I am in the blind right now, I don't even know what to google for
there is probably a way to get some lowlevel "debug" from kernel but I don't know how, it is mostly some developper stuff.
Hmmm and about kernel recompilation... have you done it before? If you want to try I could give you some basic instruction, but there's no step by step instruction, you will probably need 'guess and tries'
Yes I have recompiled a kernel before but then I knew what I wanted to accomplish, what config options to set and so on. Now I don't have a clue of what to change so I'm open to suggestions as to what I could try to change. I guess I should go for the modules first, since I can just chmod 000 them or whatever and I don't have to wait like 40 minutes for the kernel to compile. Any suggestions as to what can be causing this? WLAN? Radeon graphics? USB?
USB is pretty buggy in the last few kernels, that would be my first guess. Then the graphic card indeed.
But as I told you, my guess would be to desactivate EVERYTHING that is not essential. No network, not wlan, no USB, desactivate EVERYTHING that you don't need to boot (except ACPI of course). Then try to sleep. If it fails, dont give yourself an headache, it's worthless, it's not a drivers causing the trouble. But if it suceed, the you can start reenabling each feature one by one, 'til you find the failing one.
Btw, compiling kernel take 40 min the first time you do it, but then it should be faster (since it wont compile thing that are already compiled)
OK so this is what I tried:
Booting in initlevel 3, disable graphical boot.
Removed the following:
USB (ehci, uhci, hid), Bluetooth, ieee1394, ipw2100 (WLAN), fglrx (ATI driver) and some more (ALSA etc).
echo standby > /sys/power/state
Same thing, goes into this quasi standby state where the LCD +backlight is kept on but the computer thinks it is sleeping (no keyboard response, power button wakes it up). When waking up, the kernel stacktrace is printed as before. The topmost lines I see has something to do with memory allocation (_kmalloc etc). The lines below that are ACPI functions.
echo mem > /sys/power/state
This time the computer wakes up (responds to Ctrl+Alt+Del, Soft power off, caps log LED:s working etc) but no LCD. I even tried blind typing "radeontool light on" which is supposed to turn on the LCD (I have verified that it works when the computer is awake). Didn't work.
Note that this is when Xorg is killed or in runlevel 3. I also tried when in X, but then I think the graphics card crashed or something. The computer totally hanged.
echo disk > /sys/power/state
Still nothing happens. I guess I need that Dell partition, the RAM has to go somewhere...
Conclusion: The best bet seems to be the "mem" mode, which is the only mode I have in Windows, probably meaning it is the only one supported by Dell. If I just could get the LCD panel back on.
hmmm my laptop have a fn key to turn on the LCD. When I go to sleep and come back, with older kernel ( < 22.214.171.124 I think ) I had to manually restore the LCD ( with the fn key... the combinaison is fn-F1 on my laptop but I doubt it is the same on your ). Newer kernel fixed this bug for me. If you have a function key like this, you might want to try...
By the way, these links you gave me... 2 on 3 were running kernel 2.6.9, you might want to try the exact same one. I think I remember there is a special option in kernel about "NVIDIA chipset" laptop... make sure you have this on.
oh and, from these links again :
Suspend/Sleep and hibernate work, for restore need readeonfb patch
fb == framebuffer... might this be why your LCD doesn't turn back on on resume?
Hmmm... some more hacking done. No good result yet
Originally posted by Half_Elf hmmm my laptop have a fn key to turn on the LCD. When I go to sleep and come back, with older kernel ( < 126.96.36.199 I think ) I had to manually restore the LCD ( with the fn key... the combinaison is fn-F1 on my laptop but I doubt it is the same on your ). Newer kernel fixed this bug for me. If you have a function key like this, you might want to try...
I have Fn+F8 = CRT/LCD. Doesn't work.
I will try and see if I get a picture on the TV when I find the necessary cables.
By the way, these links you gave me... 2 on 3 were running kernel 2.6.9, you might want to try the exact same one.
I was afraid of that.... I am very reluctant to this. My choice of kernel was the result of hours of hacking to get the Radeon OpenGL acceleration to work satisfactory (actually, X will not work at all without it). Messing around too much will probably ruin this. I have 2.6.10, can things really worsen that much? I was kind of hoping that problems like mine were fixed eventually given enough patience....
I remember there is a special option in kernel about "NVIDIA chipset" laptop... make sure you have this on.
I don't have anything nvidia on my computer.
fb == framebuffer... might this be why your LCD doesn't turn back on on resume?
Yes, I read this too but it was for an older kernel. I did not find anything similar for the newer kernel so I kind of assumed it had made its way into the main kernel code. Anyway, I don't feel sure enough what I'm doing to start editing the kernel source manually (especially not that kind of low-level code) ... Also I just remembered that compiling a new kernel is a lot more work than I first anticipated, since all the modules need to be recompiled even if I stick to the same kernel version. And as mentioned, the ATI modules are a mix of some ATI closed-source binaries and some c files that needed to be patched, and I don't remember all the steps... (yes I know, I should have written them down). If I waste my graphics driver I have a non-functional computer (well, winxp...), so I'm not quite that desperate yet.
Anyway, thank you very much for your help ... although my computer fails to respond to common sense so far
I finally got it to work!!
I upgraded to the latest FC3 kernel (2.6.11-1.14_FC3) and it worked straight from the beginning. Graphics driver had to go though, since as soon as I reinstalled it the graphics got all corrupted after wakeup (same problem as everyone's having but not the same as I had before when the everything just died). The weird thing is the vesa driver only lets me have about 1024x768 or so, while my lcd (and I... :P) want 1680x1050. I'll try to find a hack someday until ATI gets this problem fixed (I assume the problem is with their driver).
ACPI sleep was my #1 priority since I carry my computer around and Linux takes EONS to boot, even after I disable all non-essential services.