Hi I have problems getting standby to work under Suse 9.1. Mostly, I have trouble finding out exactly what the problem is or in other words: reading the log files. Details: I am using an Asus M3000NP laptop with a centrino certification. The laptop has an Intel 855gm graphics card and an Intel 2000BG wifi card. Suspend (to disk) works fine, although I have only tried it, not really used it. As countless other users, I find that the laptop enters suspend mode but has problems starting X. I have put my agp modules into the hotplug/blacklist file and I am using linuxant's driverloader to handle my wifi card. Now, other (more knowledgable) users are at least able to diagnostice the problem in the lines of "something is wrong with...., I try putting that into the blacklist or the "onload_before_standby" or ...". I am unable to do that. What logs should I look at (dmesg, /var/log/messages, etc?), what debug level should I put powersave in and what info should I look at. Is there any line in the log which designates that "from now on, all output has to do with resume after standby"? For now, all I can do is use the timestamp in /var/log/messages to get an idea of when the rebooting process starts... Any help with this basic question would be appreciated. Thanks, Kasper Daniel Hansen
Hallo, I don't know how to read those logs either, in my eyes this is kind of a mess... Perhaps the problems come from the linuxant driver? There is a native driver available (http://ipw2100.sourceforge.net/) for your wlan card, so there is no need to use a wrapper. There is also a problem with DRI and your graphics driver (I also have a i855PM chipset), it just doesn't support standby/resume but works fine without DRI. DRI means Direct Rendering Infrastructure and enables the use of 3D graphics (OpenGL and such). After resuming this won't work anymore and programs using it sometimes crash or even make the whole system hang - so perhaps try removing the line >> Load "dri" << from your /etc/X11/XF86Config (which will disable DRI and make every OpenGL application painfully slow). The X log file is called /var/log/XFree86.0.log. I hope you'll find a solution! Patrick. Kasper Daniel Hansen wrote:
Hi
I have problems getting standby to work under Suse 9.1. Mostly, I have trouble finding out exactly what the problem is or in other words: reading the log files.
Details: I am using an Asus M3000NP laptop with a centrino certification. The laptop has an Intel 855gm graphics card and an Intel 2000BG wifi card. Suspend (to disk) works fine, although I have only tried it, not really used it.
As countless other users, I find that the laptop enters suspend mode but has problems starting X.
I have put my agp modules into the hotplug/blacklist file and I am using linuxant's driverloader to handle my wifi card.
Now, other (more knowledgable) users are at least able to diagnostice the problem in the lines of "something is wrong with...., I try putting that into the blacklist or the "onload_before_standby" or ...". I am unable to do that.
What logs should I look at (dmesg, /var/log/messages, etc?), what debug level should I put powersave in and what info should I look at. Is there any line in the log which designates that "from now on, all output has to do with resume after standby"?
For now, all I can do is use the timestamp in /var/log/messages to get an idea of when the rebooting process starts...
Any help with this basic question would be appreciated.
Thanks, Kasper Daniel Hansen
Hi!
Details: I am using an Asus M3000NP laptop with a centrino certification. The laptop has an Intel 855gm graphics card and an Intel 2000BG wifi card. Suspend (to disk) works fine, although I have only tried it, not really used it.
As countless other users, I find that the laptop enters suspend mode but has problems starting X.
Maybe I will lead into a completely wrong direction, but let´s try anyway. I think I have a similar situation over here. Question: What do you mean by "has problems starting X"? After resuming - does it crash your current X-Session? I have this problem, and I think it is related to the i855GM gfx-chip. I use the "Alain Portier VBios Patch" to make my system support the TFTs native resolution of 1400*1050. After resuming my X-Server directly crashs and KDM is restarted. The reason for this (I think) is the fact, that the vbios is unpatched when the system resumes, and therefore the X-Server crashs. If so, this would only be fixable if the kernel automagically applied the vbios patch during start up before resuming, since it is a hardware problem - but maybe I´m awfully wrong here. (@list: please correct me if necessary.) So maybe we both have similar problem here? bye, Michael -- Michael Heß FI Anwendungsentwicklung Consultant ORDIX AG http://www.ordix.de Tel.: 05251 / 10 63 0 Fax : 05251 / 10 63 99 Mob : 0163 /673 49 43
participants (3)
-
Kasper Daniel Hansen -
Michael Heß -
Patrick Nagel