The patch I'm attaching (diff'ed against git master) should stop the monitor from being incorrectly reported as connected and also fix this annoying warning I saw in your logs:
> [ 3.482336] (WW) SMI(0): invalid frequency 157.000 MHz [freq <= 135.000 MHz] That was preventing the driver from programming the maximum memory clock. It's unlikely that it will fix the DPMS problem though. In fact, I doubt it is really about DPMS because 1.7.0 switches to DPMS off temporarily during mode setting and if it were broken you would never see anything at all on the screen. To confirm this you can try: $ xset dpms force off; sleep 1; xset dpms force on That should turn the LCD off and then on again. To find out what is the server doing when the screen remains black, you can try to build the driver with CFLAGS="-DSMI_DEBUG", and then invoke it with some high verbosity level, like: # Xorg -logverbose 8 Then try to reproduce it. BTW, has the VT switching problem mentioned above been solved on 1.7.0? I'm quite sure that the "awful slowness" problem with 32bpp was fixed on commit 1fc340dcf0abd7fa0837fef2c711aaec4fa8bcb8. ** Attachment added: "fix_sm712_clock_limit_and_monitor_detection.patch" http://launchpadlibrarian.net/24327386/fix_sm712_clock_limit_and_monitor_detection.patch -- Screen blanks and freezes after a few minutes of idling, possibly due to broken DPMS https://bugs.launchpad.net/bugs/136853 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
