--- Begin Message ---
Package: xserver-xorg-video-i810
Version: 2:2.0.0-1
Severity: important
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-3-686 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages xserver-xorg-video-i810 depends on:
ii xserver-xorg-video-intel 2:2.0.0-1 X.Org X server -- Intel i8xx, i9xx
xserver-xorg-video-i810 recommends no packages.
-- no debconf information
I have two machines running Sid; one a Dell Inspiron 1100 laptop, one a Dell GX 170L, both with Intel integrated graphics.
After upgrading Sid on both, both stopped having working X setups; switching to the vesa driver in xorg.conf sort of restores X, but at reduced resolution and other issues.
When using the i810 driver in xorg.conf:
On the laptop, the screen switches from text mode to a dark glow like it's in a blank graphics mode. Trying to kill X with Ctrl-Alt-Backspace doesn't work, nor does trying to switch to a VT (Ctrl-Alt-F1, etc). I can plug in an external 19" monitor and press Fn-F8 (the video switch combo on the Dell laptop), and the vidoe switches to the external, and sometimes gives me workable video, sometimes not. Fn-F8 again will bring the video back to the laptop, but it remains dark and "frozen". When I'm switched to the external monitor, I can switch to a VT, and another Fn-F8 or three and I can get text mode working again on the laptop screen.
Lockups have become common, and automatic power-saving (hibernation, standby) has ceased working (although that might be unrelated); if I manually put it in standby, when I try to wake it up, the keyboard appears unresponsive (I've not had ssh ability to see if it's remotely accessible), and I wind up powering down the laptop and restarting.
When using the vesa driver, the laptop works better, but still not correctly, so the problem may not be in the xserver-xorg-video-i810 driver, but elsewhere in the graphics system.
The desktop machine, also being freshly upgraded in X, has started exhibiting similar symptoms. It's a dual-head box, and when I switch the i810 driver to vesa, the machine is, like the laptop, semi-usable, but not very; it allows the ATI-driven monitor to fire up, but the Intel-driven monitor stays dark; I can move windows from one monitor to the other, so the system _thinks_ the monitor is there (but of course I can't see the windows once they're moved to the dark Intel-driven one).
When using the i810 driver on the desktop box, I get the following types of messages (snippage; I'm unsure if reportbug will let me attach the log file, so here's what seems to me to be relevant):
(**) intel(0): Depth 16, (--) framebuffer bpp 16
(==) intel(0): RGB weight 565
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) 865G
(--) intel(0): Chipset: "865G"
(--) intel(0): Linear framebuffer at 0xE8000000
(--) intel(0): IO registers at addr 0xFEB80000
(II) intel(0): 1 display pipe available.
(==) intel(0): Using XAA for acceleration
(--) intel(0): Will try to allocate texture pool for old Mesa 3D driver.
(II) intel(0): Will try to reserve 32768 kiB of AGP aperture space
for the DRM memory manager.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"(II) Module already built-in
(II) intel(0): Output VGA using monitor section Generic Monitor
(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): Output TMDS has no monitor section
(II) intel(0): I2C bus "DVODDC_D" initialized.
(II) Loading sub module "sil164"
(II) LoadModule: "sil164"
(II) Loading /usr/lib/xorg/modules/drivers//sil164.so
(II) Module sil164: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(II) intel(0): I2C bus "DVOI2C_E" initialized.
(EE) intel(0): detecting sil164
(EE) intel(0): Unable to read from DVOI2C_E Slave 112.
(II) Loading sub module "ch7xxx"
(II) LoadModule: "ch7xxx"
(II) Loading /usr/lib/xorg/modules/drivers//ch7xxx.so
(II) Module ch7xxx: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(II) intel(0): I2C bus "DVOI2C_E" removed.
(II) intel(0): I2C bus "DVOI2C_E" initialized.
(EE) intel(0): Unable to read from DVOI2C_E Slave 236.
(II) intel(0): I2C bus "DVOI2C_E" removed.
(II) intel(0): I2C bus "DVODDC_D" removed.
(II) intel(0): Output VGA connected
(II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0.
(II) intel(0): I2C device "CRTDDC_A:ddc2" removed.
(II) intel(0): EDID for output VGA
(II) intel(0): Manufacturer: VSC Model: e809 Serial#: 16843009
(II) intel(0): Year: 2003 Week: 24
(II) intel(0): EDID Version: 1.3
(II) intel(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
(II) intel(0): Signal levels configurable
(II) intel(0): Sync: Separate CompositeSerration on. V.Sync Pulse req. if CompSync or SyncOnGreen
(II) intel(0): Max H-Image Size [cm]: horiz.: 40 vert.: 30
(II) intel(0): Gamma: 2.92
(II) intel(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) intel(0): First detailed timing is preferred mode
(II) intel(0): redX: 0.628 redY: 0.328 greenX: 0.280 greenY: 0.598
(II) intel(0): blueX: 0.146 blueY: 0.060 whiteX: 0.283 whiteY: 0.297
(II) intel(0): Supported VESA Video Modes:
(II) intel(0): Kernel reported 110336 total, 17 used
(II) intel(0): I830CheckAvailableMemory: 441276 kB available
(==) intel(0): VideoRam: 131072 KB
(II) intel(0): Attempting memory allocation with tiled buffers and
large DRI memory manager reservation:
(II) intel(0): Allocating 7152 scanlines for pixmap cache
(II) intel(0): Success.
(II) intel(0): Memory allocation layout:
(II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
(II) intel(0): 0x00020000-0x00024fff: HW cursors (20 kB)
(II) intel(0): 0x00025000-0x0002cfff: logical 3D context (32 kB)
(II) intel(0): 0x0002d000-0x0003cfff: xaa scratch (64 kB)
(II) intel(0): 0x00200000-0x003fffff: back buffer (2048 kB)
(II) intel(0): 0x00400000-0x005fffff: depth buffer (2048 kB)
(II) intel(0): 0x007df000: end of stolen memory
(II) intel(0): 0x007df000-0x007dffff: overlay registers (4 kB, 0x1c62c000 physical)
(II) intel(0): 0x007e0000-0x017d7fff: front buffer (16352 kB)
(II) intel(0): 0x017d8000-0x037d7fff: DRI memory manager (32768 kB)
(II) intel(0): 0x037d8000-0x057d7fff: textures (32768 kB)
(II) intel(0): 0x08000000: end of aperture
(II) intel(0): front buffer is not tiled
(II) intel(0): back buffer is tiled
(II) intel(0): depth buffer is tiled
(WW) intel(0): Direct rendering is not supported when Xinerama is enabled
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
(II) intel(0): Page Flipping disabled
(==) intel(0): Write-combining range (0xe8000000,0x8000000)
(II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) intel(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Horizontal and Vertical Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x007df000 (pgoffset 2015)
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x007e0000 (pgoffset 2016)
(WW) intel(0): PRB0_CTL (0x0000f001) indicates ring buffer enabled
(WW) intel(0): Existing errors found in hardware state.
(II) intel(0): Output configuration:
(II) intel(0): Pipe A is on
(II) intel(0): Display plane A is now enabled and connected to pipe A.
(II) intel(0): Output VGA is connected to pipe A
(**) Option "dpms"
(**) intel(0): DPMS enabled
(II) intel(0): Set up overlay video
(II) intel(0): direct rendering: Failed
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8591]
1: [0xb7fcb420]
2: /usr/bin/X11/X(xf86RandR12SetRotations+0x6b) [0x80fc37b]
3: /usr/bin/X11/X(xf86CrtcScreenInit+0x9e) [0x80f85ee]
4: /usr/lib/xorg/modules/drivers//i810_drv.so [0xb7c06b53]
5: /usr/bin/X11/X(AddScreen+0x1ee) [0x80764be]
6: /usr/bin/X11/X(InitOutput+0x21e) [0x80a7b6e]
7: /usr/bin/X11/X(main+0x27b) [0x8076c6b]
8: /lib/libc.so.6(__libc_start_main+0xdc) [0xb7dd8ebc]
9: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e5) [0x80761a1]
Fatal server error:
Caught signal 11. Server aborting
--- End Message ---
--- Begin Message ---
Kent West wrote:
> On 5/22/07, Kent West <westk@acu.edu> wrote:
>> (I think just for kicks I may switch to the ATI-driven side in a few
>> mins
>> and see if that works also.)
>
> Yep; works fine. Let me study up on the dual-head issues a bit, and
> I'll let you know what happens.
>
> btw, unrelated, but any idea why X ignores my resolution settings in
> xorg.conf? I've got 1280x1024x24 as my max, but it's starting up in
> 1600x1200x24. Don't research it; I can do that, but if you know the
> quick answer off the top of your head ....
Yes, the Modes line is basically ignored now since they are
automatically detected. If you want to force a mode on startup, I think
there's a "PreferredMode" option. I never tried but there are some
examples online, for instance [1].
I am closing this bug report now, as you suggested earlier.
Thanks,
Brice
[1]
http://www.tetromino.net/blog/2007/04/25/manual-modesetting-for-xf86-video-intel/
--- End Message ---