Comment 36 for bug 391215

Revision history for this message
Flabdablet (flabdablet) wrote :

As described in my careless post to a duplicate bug report at

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391705/comments/10

this happens to me as well. Acer SK20, Intel 845 graphics so I don't think it's just an nVidia issue.

The following lines from dmesg (attached) are interesting:

[ 3.663897] [drm] Initialized drm 1.1.0 20060810
[ 3.681482] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 3.681491] i915 0000:00:02.0: setting latency timer to 64
[ 3.822499] [drm] fb0: inteldrmfb frame buffer device
[ 3.822515] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 3.834769] Console: switching to colour frame buffer device 80x43
[ 3.907975] render error detected, EIR: 0x00000010
[ 3.907981] [drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking
[ 3.908009] render error detected, EIR: 0x00000010
[ 3.922937] [drm] DAC-5: set mode 640x350 13
[ 4.053962] vesafb: framebuffer at 0xd8000000, mapped to 0xe0680000, using 3072k, total 8000k
[ 4.053968] vesafb: mode is 1024x768x16, linelength=2048, pages=4
[ 4.053971] vesafb: scrolling: redraw
[ 4.053978] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
[ 4.054063] fb1: VESA VGA frame buffer device

It looks like the option is not being ignored, but is failing to do what it should.