Display corruption and system lockup (Xorg server 1.4/xf86-intel 2.3.1)
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Display corruption and system lockup (Xorg server 1.4/xf86-intel 2.3.1)
Hi everybody,
When using the xorg-xf86-video-intel driver (2.3.1 current version at time of writing) with DRI enabled, display corruption and a system lockup occur when exiting an X session via menus or using Ctrl+Alt+Backspace. The system is unresponsive, however NumLock and other similar indicators respond correctly, but I cannot switch to any other consoles or otherwise control the system. The corruption is a collection of lines covering the screen, usually purple and white. Sometimes this is not the case, with the screen being partially covered in these lines and otherwise black, or black entirely. This problem also occurs using the older i810 driver. I've tried revisions 2.1.1 through to 2.3.1 (including version of 2.2.99 which fixes the problem for some) of the intel driver by modifying the xorg-xf86-video-intel port, all to no avail. It is worth noting that I've returned to using the 2.3.1 port as in the CRUX xorg repository.
I am using an Intel 950GMA graphics controller, listed by lspci as the following -
I'm running CRUX 2.4, with Linux 2.6.25.4. I have been able to reproduce the problem on Linux 2.6.24.7 and 2.6.25.3. I'm running the latest Xorg server build as per the xorg repository (1.4), with the system fully up-to-date at the time of writing. I've spent hours searching mailing lists and forums, even building my own version of the xorg-xf86-video-intel driver using patches reported to fix the problem (http://www.archlinux.org/packages/14160/).
I have included my X configuration file. It is of note that a variety of options mentioned by other people with this problem, such as what is mentioned in http://bugs.archlinux.org/task/7106 and http://bugs.archlinux.org/task/8976, have not fixed the problem. The only way I am able to use the intel driver is by disabling DRI. Disabling the composite extension, or using any other combination of options excluding DRI disabling, does not able me to exit X without a lockup. The load module line for dri has no effect if enabled or disabled, as with all other module load lines. If I enable DRI, the driver performs without issue until exiting. Regarding the examples used, I appreciate Arch Linux is not CRUX, but due to the similar nature of the problems described the references are of relevance to this bug.
At the risk of sounding stupid, the xorg-xf86-video-intel driver, "used to work". Recent updates to X and the kernel have resulted in this bug, but I am unable to pinpoint it in terms of it being a driver, X server or kernel issue. When the system locks up, no further writing to the X log occurs (i.e. no error messages are listed), which is why I have not included it in this post. If the log is required, I apologise in advance for not including it and will provide a copy on request. I've posted a CRUX bug report, but am looking for more general tips and guidance on any ways to mitigate or solve this problem as it doesn't appear to be specific to CRUX.
Using the vesa driver does not produce this bug, meaning (to my knowledge) only the intel and i810 drivers are experiencing problems. I have rebuilt my kernel, mesa3d, xorg-server and the drivers but this has not solved the problem.
I would appreciate any insight into this problem. I apologise if the information I have given is inadequate - if anything is missing let me know and I will provide what is needed. Thanks for taking the time to help.
I had similar problem, after digging in Xorg bugzilla (this problem seems appear and disappear for some users) I tried the GIT version of Xorg driver and haven't had this problem since then. I'm running 2.6.25-r3 kernel. DRI from Gentoo Portage was too old for this driver, so I had to switch to GIT version of DRM too.
I had similar problem, after digging in Xorg bugzilla (this problem seems appear and disappear for some users) I tried the GIT version of Xorg driver and haven't had this problem since then. I'm running 2.6.25-r3 kernel. DRI from Gentoo Portage was too old for this driver, so I had to switch to GIT version of DRM too.
Thanks for the reply. I've tried the git versions of the Intel driver and DRM library, but this hasn't fixed the problem. The display corruption looks a little different, but other than that the bug is still there. I'm thinking the problem is specific to my card. Do you have any further suggestions?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
