Comment 76 for bug 577340
Revision history for this message
| gene (eugenios) wrote it might be interesting... | #76 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
OK, I might have gotten some interesting data. First, I should explain. I decided gain (after a couple years) to switch to fglrx and see how it works. Last time it was also very buggy but in more annoying way...
So I installed fglrx and it... didn't giving me configure errors with my custom kernels , I did not want to bother any further. So I decided to switch the sides again :) and removed it.
I tried to see how suspend-resume would work (DRI and 3D was on). So it did not, however, instead of usual blank unresponsive to SysRq keys monitor I had a dump and REISUB restarted the machine. Oops I did it again, and got nothing gain... :) In the usual way all resume attempts were numb, no syslog info was left.
The corresponding kernel.log (the section between the sleep and a waking attempt) is attached below.
I hope that this would be helpful for more knowledgeable people than me.
--