On 09/01/2010 04:36:06 PM, dp wrote:
I find that the following update causes suspend/resume to fail:
========================================================================== Updating: NetworkManager i686 1:0.8.1-4.git20100817.fc13 NetworkManager-glib i686 1:0.8.1-4.git20100817.fc13 NetworkManager-gnome i686 1:0.8.1-4.git20100817.fc13
==========================================================================
The suspend appears to happen normally, but resume seems to do very little, and ends with a blank screen. I think it makes no entry in "messages". I haven't noticed anyone else reporting this.
The laptop is Dell 9400: Nvidia 7900GS, Kernel 6.33.8-149.fc13.i686.PAE
retest with the 6.34 kernel.
Thanks for your suggestion. It still fails with:
2.6.34.6-47.fc13.i686.PAE NetworkManager-0.8.1-4.git20100817.fc13.i686
Perhaps I should add that it is using nouveau and no xorg.conf.
Thanks again.
On 09/02/2010 03:45:31 PM, dp wrote:
On 09/01/2010 04:36:06 PM, dp wrote:
I find that the following update causes suspend/resume to fail:
==========================================================================
Updating: NetworkManager i686 1:0.8.1-4.git20100817.fc13 NetworkManager-glib i686 1:0.8.1-4.git20100817.fc13 NetworkManager-gnome i686 1:0.8.1-4.git20100817.fc13
==========================================================================
The suspend appears to happen normally, but resume seems to do
very
little, and ends with a blank screen. I think it makes no entry
in
"messages". I haven't noticed anyone else reporting this.
The laptop is Dell 9400: Nvidia 7900GS, Kernel 6.33.8-149.fc13.i686.PAE
retest with the 6.34 kernel.
Thanks for your suggestion. It still fails with:
2.6.34.6-47.fc13.i686.PAE NetworkManager-0.8.1-4.git20100817.fc13.i686
Perhaps I should add that it is using nouveau and no xorg.conf.
xorg.conf is pretty much redundant these days.
You need to do some diagnosis with submitting a Bugzilla report as your goal or, hopefully, finding the problem. With regard to the report, heep in mind that the better the evidence, the more likely you are to get a fix.
For starters, have a look at /var/log/pm-suspend.log. The actions taken in suspending and resuming are recorded there. Look for actions that are not recorded as 'success' or 'not applicable'. Towards the end, if everything is working, you should see something like:
Thu Sep 2 14:32:17 PDT 2010: performing suspend Thu Sep 2 16:21:02 PDT 2010: Awake. Thu Sep 2 16:21:02 PDT 2010: Running hooks for resume
You might also have a look at http://www.mjmwired.net/kernel/Documentation/power/basic-pm- debugging.txt
Good luck.
On Fri, Sep 3, 2010 at 12:43 AM, Geoffrey Leach geoff@hughes.net wrote:
Perhaps I should add that it is using nouveau and no xorg.conf.
xorg.conf is pretty much redundant these days.
"Pretty much" != "completely" !
If you need to load the vnc server module when x loads then you can only do it via a (simplified if necessary) xorg.conf file as far as I am aware?
If you know how to load the vnc module for X without xorg.conf then I would be very interested to hear how to do it?
On Fri, Sep 3, 2010 at 9:08 AM, mike cloaked mike.cloaked@gmail.com wrote:
On Fri, Sep 3, 2010 at 12:43 AM, Geoffrey Leach geoff@hughes.net wrote:
Perhaps I should add that it is using nouveau and no xorg.conf.
xorg.conf is pretty much redundant these days.
"Pretty much" != "completely" !
If you need to load the vnc server module when x loads then you can only do it via a (simplified if necessary) xorg.conf file as far as I am aware?
If you know how to load the vnc module for X without xorg.conf then I would be very interested to hear how to do it?
I did not mean to hijack this thread and maybe this should be a new thread instead?
-
d p -
Geoffrey Leach -
mike cloaked