On 03/17/2009 01:15:10 PM, Robby Workman wrote: > On Sun, 15 Mar 2009 14:18:47 -0700 > Geoffrey Leach <ge...@hughes.net> wrote: > > > The (relatively new) ASUS P5N7A-VM. The key components are Nvidia > > GeForce 9300 and nForce 730i. I have Fedora 10 installed and > (more-or- > > less) up to date, as are the Nvidia drivers. > > > > I have had no luck at all getting the system to restart from > suspend > > > (to ram) or hibernate (to disk). Suspending appears to work, but > > Working my way through the quirks has not given me any joy. > > > > Can anyone give me a suggestion on what to try? Or am I just > wasting > > my time. > > > Here are a few (not necessarily connected) thoughts: > > Does the system come back up at all? Are any keyboard led's blinking > afterward? Does it respond to pings, and/or can you log in to it via > ssh?
Thanks for the response. Sorry, no keyboard LEDs (lo-tech kboard). Nothing but a (blinking) cursor on the monitor, along with these messages: PM: Syncing filesystems ... done. Freezing user space processes ... (elapsed 0.00 seconds) done. Freezing freezable tasks ... (elapsed 0.00 seconds) done. Suspending console(s) (use no_console_suspend to debug) Running a kernel booted with no_console_suspend resulted in these messages not being displayed, but otherwise no change. No joy on ping or ssh. No response to kbd, mouse or power button. > Can you try using the xorg "nv" driver instead and see if that makes > a difference? Installation of Fedora 10 defaulted to text mode, so I think its safe to assume that the nv driver won't work. > You might also try running this (as root) from command line: > PM_DEBUG=true pm-suspend > That should put more information into /var/log/pm-suspend.log. > Granted, it may not be terribly useful if the machine won't resume at > all, but one can hope. > > Check your list of modules in use. If one of them is r8169, then I > know for certain that it can cause resume issues, although in my case > the only impact is no network. You can work around that by > creating /etc/pm/config.d/defaults and populating it with this line: > SUSPEND_MODULES="r8169" Module r8169 was not loaded. Where does it come from (perhaps I have something from the same source. I see its a network driver; Nvidia? In that respect, it might be relevant that my network is wireless only, and that I shut down NetworkManager and NFS before shutting down. My observations regarding ping/ssh were taken before deciding to do this. It appeared that the NFS daemon was not responding to killall during shutdown. The PM_DEBUG yielded a ton of info, which I'll have to pour over. The last three lines are: + log <date> performing suspend + do_suspend + echo -n mem No sign of resume. Should say "Awake" next. _______________________________________________ Pm-utils mailing list Pm-utils@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pm-utils