I've tried the latest Lucid build and that produces very similar results. The main thing I notice about it is that it's using the nouveau driver which is what I think is responsible for what I'm seeing.
Again, I ran the test in single user mode. It wasn't possible to remove or disable the nouveau driver. Running a pm_trace produces the same results as before. But seen as it resumes from suspend that's of no use? When it comes out of suspend, unlike previously, the power light on my LCD monitor turns green and pops up with the message No Signal. I'm guessing this is down to the nouveau driver, it's sending the signal to the monitor to turn back on but it's not turning on the output. My Media Live system is connected via an HDMI port on the back to a DVI port on my monitor. Looking at the dmesg output generated by the nouveau driver it recognises this. A few seconds later the monitor then goes into automatic suspend, the led turns orange. Everything on it appears to work correctly, USB keyboard etc. >From Google I did come across a windows driver "nVIDIA ForceWare 81.98" and in the change log of bug fixes it mentioned "GeForce 6150/6100, Windows XP Media Center Edition 2005: The display remains inactive when resuming from Suspend mode." So I don't know if there's anything special that needs to be done with this particular chipset to wake it up? As another test, I tried "vbetool dpms off" which works though when I try "vbetool dpms on" it doesn't turn the monitor back on. However for some reason when I did "vbetool vbemode set 283" the monitor turned itself back on though the screen was messed up - the left handside was now in the center of the screen and it scrolls off the bottom. I just thought I'd try something to manually set the resolution in the hope that it would pop back into life. This though did not have any affect after a resume from suspend. The change I've seen, the monitor now turning back on after resume but still not having a signal, I'd image would be due to the nouveau driver. Should it not 'work' without this? I found a post about suspend http://forum- en.msi.com/index.php?topic=120345.0 ,presumably it's on windows, saying that it started to work correctly in BIOS 1.63 which is the same version I'm using. So I'm guessing something's been missed out when the system resumes from suspend for the display to not wake up. -- [MSI MS-7329] suspend/resume failure [non-free: nvidia] https://bugs.launchpad.net/bugs/390158 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
