xf86-video-intel-2.5.0 causes my laptop to boot up to a blank screen with a blinking cursor in the top left corner instead of to KDM. Reproducible: Always Steps to Reproduce: 1. emerge --sync 2. emerge xf86-video-intel-2.5.0 3. Reboot Actual Results: Boots to blank screen with blinking cursor in upper left corner. Expected Results: Boot to KDM or graphical login on console 7. I have confirmed that this version of xf86-video-intel is the culprit by switching between that and earlier versions, which do not cause problems.
Step 2 should be emerge =xf86-video-intel-2.5.0.
Please post your `emerge --info', attach the Xorg.?.log, and the relevant information from dmesg.
Some relevant info: xorg-server: 1.4.2 xorg-x11: 7.4 libdrm: 2.4.0
I forgot to add kernel: 2.6.27-gentoo-r1
By the way, this also happens when xf86-intel-video-2.5.0 is used with xorg-server-2.5.2 - so an upgrade won't fix it. I should also mention that when I upgrade to xorg-server-2.5.2, the same result as this bug occurs, using a older xf96-video-intel that works with xorg-server-1.4.2.
Created attachment 170219 [details] Xorg.0.log with xf86-video-intel-2.5.0
Created attachment 170221 [details] Emerge --info with xf86-video-intel
Please let me know what info to grep from dmesg and I will post it.
(In reply to comment #8) > Please let me know what info to grep from dmesg and I will post it. Just post all of it. You could look through it and blur some of the private stuff you don't want the world to know about. :) Posting your xorg.conf is probably more informative, though - it seems to want to autoload the i810 driver.
You should just need to edit your xorg.conf file to point to the "intel" driver instead of "i810". Please don't hesitate to reopen this bug if you still have issues :) Thanks
Ok. So maybe this is really a bug for xorg-server-1.5.2 then? Shouldn't it look for "intel" instead of i810?
If your xorg.conf specifically asks for the "i810" driver module, then it'll look that up (which is bound to fail, since 2.5.0 no longer provides the "i810" driver module). If you don't specify the driver, I think Xorg should be able to figure out which driver to load on its own. Thanks
I agree - but the latest ~arch version just doesn't. I'll try it again and manually specify the driver and report back.