ubuntu-x-swat team mailing list archive

[Nicholas Christian Langkjær Ipsen <sephiroth7vii@xxxxxxxxx>]

Well, without nomodeset, I won't be able to use my laptop at all. I guess
I'll run the command, and then  get the files by chrooting in from a livecd.


On Mar 1, 2010 12:25 PM, "Geir Ove Myhr" <gomyhr@xxxxxxxxx> wrote:

Nicholas, the logs you provided are without drm.debug=0x04. From dmesg.txt:
[    0.000000] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.33-020633-generic
root=UUID=33f45800-d1dc-45aa-9098-839ef5477cac ro quiet splash nomodeset
i8042.noloop=1
and Xorg.0.log:
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.33-020633-generic
root=UUID=33f45800-d1dc-45aa-9098-839ef5477cac ro quiet splash nomodeset
i8042.noloop=1

You should also not use nomodeset, since the intel driver will not work
with that (you may need nomodeset to make the vesa driver work, though).
Did you add nomodeset instead of drm.debug=0x04 by mistake?


-- 
[i945gme] Ubuntu falls back on vesa driver (no screens)
https://bugs.launchpad.net/bugs/507196
...

-- 
[i945gme] Ubuntu falls back on vesa driver (no screens)
https://bugs.launchpad.net/bugs/507196
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.