The X intel driver is not functioning correctly

Reported by Dave Morley on 2007-08-23
Affects Status Importance Assigned to Milestone
discover-data (Ubuntu)
Bryce Harrington

Bug Description

Binary package hint: xorg

The Xorg intel driver is faulty it gives screen images like http://www.davmor2.pwp.blueyonder.co.uk/Screenshot.png
and http://www.davmor2.pwp.blueyonder.co.uk/after-detect.jpg (this image was a text based install after driver detection before this point it worked flawlessly.)

If you change intel to i810 then the problems go away. Work Around listed below

1. Wait for pc to boot to desktop for the first time
2. Press Alt+Ctrl+F1
3. At the prompt type in your username and then your password or on live cd ubuntu then hit return
4. Type in sudo nano /etc/X11/xorg.conf
5. Press the down arrow until you get to the line that says Driver "intel"
6. Change the word intel to i810
7. Press Ctrl+x, then y, then return to save and exit
8. Press Alt+Ctrl+F7 When the screen appears hit Alt+Ctrl+backspace to restart the Xserver

trollord (trollenlord) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

We would ask you to attach the following information:
- Output of uname -a
- Output of lspci -n
- Output of sudo discover --disable=parallel,serial,usb,ide,scsi,pcmcia --format="%M\t%S\t%D\t%i\n" video
- Output of sudo xresprobe intel
- /var/log/Xorg.0.log (the one that gets generated when the problem is around)
- /etc/X11/xorg.conf and /etc/X11/xorg.conf.* (the one that gets generated when the problem is around)

Thank you in advance.

Dave Morley (davmor2) wrote :

This bug was set up because although it is tightly linked to nearly all the intel driver bugs we needed one specific one for iso tests that could be referred to with the work around.

My original bug is here 127677 which contains most of the info you need.

I've got a similar problem. See graphic below.

This is running alternate-amd64 installer, tribe 5 (downloaded 24-Aug-2007) on an intel graphics based macbook, C2D.

update: the installer cleanly finishes itself and ejects the CD. From previous experience knowing that it is asking to press ENTER I did. The machine reboots, boots cleanly and the machine works fine with compiz active by default. No more graphical issues so far. They are/were limited to the installer.

Dave Morley (davmor2) wrote :

Yes the work around for that is to set your screen resolution from the F1-5 menu at the bottom. If memory server I think it is F3. That stop the issue when the graphics driver is detected.

I just tried the installer (alternate-i386, vs amd-64 as above) on another machine with intel graphics chipset and *did not* run into the problem. Chipset:

82915G/GV/910GL Integrated Graphics Controller (from Device Manager)

Dave Morley (davmor2) wrote :

Yes this is only effecting drives using the x driver "intel". If it is an x driver "i810" then there is no fault.

Hopefully it'll get sorted soon.

Bryce Harrington (bryce) wrote :

Sounds like a quirk is needed for this particular Intel chipset - the -intel driver works fine for most Intel graphics hardware.

Please attach your lscpi -nnvv, so we can default the chipset to use the i810 driver.

Dave Morley (davmor2) wrote :

Bryce I already have the i810 driver enable will that effect the info your after. If so I can do it on the next round of iso tests. Which will kick in on Tuesday I think.

Dave Morley (davmor2) wrote :

Bryce here is the info you requested.

Dave Morley (davmor2) wrote :

Bryce here is the info you requested.

Dave Morley (davmor2) wrote :

Bryce here is the info you requested.

Dave Morley (davmor2) wrote :

apologies for the repeats it internet kept stalling so I thought it had failed.

Bryce Harrington (bryce) wrote :

Attached is a debdiff for making this device use i810.

Changed in xorg:
assignee: nobody → bryceharrington
importance: Undecided → Medium
status: New → In Progress
Bryce Harrington (bryce) wrote :

This seems to be a dupe of the well-known bug 127008; rather than switch to i810, I think we should focus on the true fix.

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

Other bug subscribers