Ticket #5388 (assigned bug)

Opened 6 weeks ago

Last modified 4 weeks ago

Garbled screen on an Intel Mobile graphics card

Reported by: Grunt Owned by: axeld
Priority: normal Milestone:
Component: Drivers/Graphics/intel_extreme Version:
Keywords: Cc:
Blocked By: Platform: All
Blocking:

Description

During the install phase, and after the system booted, the screen looks garbled. Multiple vertical bands of different colors are visible, some text does not show at all, some images are distorted.

I have an Acer 5315 with a Mobile Intel display adapter (Intel 965 Express chipset).

Attached are 3 images, and I think it's the most obvious in the 3rd (freshly installed system).

Attachments

DSC00585.JPG Download (86.4 KB) - added by Grunt 6 weeks ago.
DSC00588.JPG Download (64.1 KB) - added by Grunt 6 weeks ago.
DSC00590.JPG Download (75.9 KB) - added by Grunt 6 weeks ago.

Change History

Changed 6 weeks ago by Grunt

Changed 6 weeks ago by Grunt

Changed 6 weeks ago by Grunt

Changed 5 weeks ago by Grunt

  • priority changed from normal to high

Changed 5 weeks ago by stippi

  • owner changed from stippi to axeld
  • priority changed from high to normal
  • status changed from new to assigned
  • component changed from User Interface to Drivers/Graphics/intel_extreme

For the time being, you should be able to remove/rename the "intel_extreme" driver from /boot/system/add-ons/kernel/drivers/bin. (Renaming will break a link to this driver which also disables it.) That will then give you VESA graphics. On notebooks, the VESA BIOS usually includes the native resolution of the panel, so that you don't have any drawbacks. In any case, we reserve the "high" priority for more serious bugs. I know it sucks for you if this bug doesn't get fixed (although the above should help), but please don't try to push the urgency.

Changed 5 weeks ago by Grunt

Sorry about that.

Changed 5 weeks ago by stippi

Hey no worries! :-) Did my suggestion about using the VESA driver work out ok for you?

Changed 5 weeks ago by Grunt

Yes, thanks a lot!

Changed 4 weeks ago by axeld

Looks like the pixel clock is set too high, causing the chip not being able to keep up. Can you please attach a syslog (when using the driver, of course)?

Note: See TracTickets for help on using tickets.