"intel" video driver makes laptop crash

Bug #146931 reported by Elmer van Baal
2
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

After a fresh install of Gutsy Gibbon beta, the "intel" driver was chosen by default in stead of "i810". This newer(?) driver has at least one terrible bug: my system crashes completely (need to use the power button!) when the current x-session switches to console (either by logging out, or by CTRL+ALT+F1, or by changing resolution). When this driver will be installed by default on machines with intel video chipsets, this will be a complete showstopper for people that are just beginning to explore linux.
My solution is to manually edit xorg.conf: put the "i810" driver in stead of "intel", and restart the machine.

Of course, the i810 driver has its disadvantages: for higher (native) resolutions you need to install the 915resolution package and manually edit some configuration files, but at least the system will not crash.

The "intel" driver is not ready to be installed by default and I suppose this should really be resolved in the final release of Gutsy Gibbon.

Info:
My HP NC6620 laptop gives the following output with LSPCI:
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)

Revision history for this message
Elmer van Baal (evbaal) wrote :

This little video (made with a seperate camera) shows the screen output after the crash.

Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #127101, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.