Good, I see it's working a little better with the latest updates from xorg-edgers. It's now giving problems with the DRM driver in the kernel: [ 25.710] drmGetBusid returned '' [ 25.710] (EE) intel(0): [drm] failed to set drm interface version. [ 25.710] (EE) intel(0): Failed to become DRM master. so it'd be helpful to get the dmesg output for the error and see what the kernel says.
I'm willing to bet that if you can shutdown normally using the power button, you can also switch to another VT with Ctrl+Alt+F1. This makes gathering logs much easier, as I'm sure you know. So now I'd like you to recreate the scenario above, but this time add 'drm.debug=0x06' as the only kernel parameter. This will add debugging information to dmesg. Then switch to another VT after recreating and get a copy of /var/log/dmesg, the output of 'dmesg', and another copy of /var/log/Xorg.0.log for consistency. cat /var/log/dmesg > BootDmesg.txt dmesg > CurrentDmesg.txt cat /var/log/Xorg.0.log > Xorg.0.log.txt (or however else you want to capture those three files.) If you can't switch to another VT, you'll need to SSH in from another computer to get the two dmesg logs (alternately you could cherrypick that particular boot from kern.log, copy it to another file (so the file is smaller and only contains the relevant boot) and upload that along with Xorg.0.log.old). -- [arrandale] Maverick boots to a black screen: "(EE) intel(0): No kernel modesetting driver detected." https://bugs.launchpad.net/bugs/605667 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
