965/x3000 video not supported

Can you re-test with dapper (6.06 LTS), I thought I'd patched it in before release.

This is 6.06LTS on a Gigabyte GA965-DS3. Forced to do netboot install because cdrom (pata) is also unavailable with default install

I have the G965 chipset with the Intel GMA X3000 as well and I also had to do a netboot installation of 6.10 Edgy because my cdrom is unavailable. I don't get the "no screens found" error. However, I haven't been able to set my resolution to 1680x1050 with my Dell 2007WFP.

I have an Intel DG956WH motherboard (G965, GMA X3000). I installed AMD64 Edgy from cd, using an IDE-USB adapter (handy gadget to have around).

 I had my CRT connected to the VGA port through a KVM during the install. I have since discovered that the KVM doesn't pass DDC signals, which explains my 60Hz refresh rate, and might have something to do with other problems. (which I maybe should have filed as separate bugs; let me know if I should split this up.)

 Video worked fine out of the box for me. Switching to a text console and back screwed up the video, though. My CRT loses vertical sync, and the screen becomes a flicker of the average colour of whatever is displayed. (I think the output image is fine, it's just not in a vid mode the monitor can sync to or something. I can ssh in and use x11vnc -display :0 and continue using my login session, which is how I can compare the displayed image with the colour of the flicker.)

  Upgrading the kernel to linux-image-2.6.19-7-generic 2.6.19-7.11 made switching to a text console safe, but starting a second X server (e.g. with gnome's switch user feature, or presumably with startx -- :1) still screws it up. With Edgy's 2.6.17 kernel, CTRL+ALT+Backspace to shut down the X server (so gdb restarts it) didn't help. The restarted X server outputs the same bad video. (I haven't tested that now because I unwisely started bonnie++ in a gnome-terminal tab on my 500GB WD RE2 hard drive, and it will probably take another 20 hours...)

 Further observations with 2.6.19: While switched to a text console, x11vnc shows a corner of the screen tiled across the whole 1024x768 . This doesn't work properly on other machines with other drivers; e.g. nvidia (proprietary) on i386 Edgy. This probably can't work because the X server can't hold onto the video RAM where the image is if another X server is going to be able to start.

 With 2.6.17 and 2.6.19, glx is a little flaky.
peter@tesla:~$ glxgears
libGL warning: 3D driver claims to not support visual 0x5a
but it does work. So do other opengl apps, like xmoto.
(I've attached output of glxinfo).
Sometimes trying to run an opengl program fails, and there's even a kernel log message:
[48096.418558] [drm:i915_cmdbuffer] *ERROR* i915_dispatch_cmdbuffer failed

I'll attach my Xorg.0.log, too.

The splash boot video is kind of corrupted (mostly gray, not full colour), even with 2.6.19. The difference I saw with switching to tty1 and back might just have been because I took the splash option out of my grub menu.lst before the reboot with the new kernel. The boot splash is fine with the i386 Edgy CD, but not the amd64 CD. (unsurprisingly, it's the same booting from the AMD64 CD as with the splash option after the install.) So I'm booting with a "colour VGA+ 80x25" console. fbcon and vesafb are loaded, but their use count is zero, and there's nothing the the kernel log about switching to an fb console. OTOH, the console font does change to a very spindly one after some boot scripts run. But fbset says no such device opening /dev/fb0, so I guess it's real text mode. Anyway, booting without the splash fixes VT switching, except for switching between two X ser...

one other note: hibernate and suspend work out of the box on AMD64 Edgy on the DG965WH :). IIRC, suspend/resume screwed up the video with the old kernel with splash boot. (with the same unsynced output, which my monitor's OSD measures as 60Hz vert, 48.3kHz horiz.)

The Feisty kernel doesn't always make switching to a text console and back work. Some boots it works, some boots it doesn't. Sometimes the first few switches work, but then it breaks. e.g. I booted just now (with a monitor and keyboard connected directly, not through a KVM), and the first thing I did was CTRL+ALT+F1 (while gdm was displaying the login prompt), then switch back. It worked a couple times, then I logged in. After starting firefox and starting to type this, I switched again, and this time the vid mode was screwed up when I switched back. Thank goodness for x11vnc, so I can finish sending this!

 I suspended the computer (from the gnome power button icon, whatever that does), and after I hit the space bar it woke up again and the VGA output was good again.

> kernel log message: [48096.418558] [drm:i915_cmdbuffer] *ERROR* i915_dispatch_cmdbuffer failed

 This was due to a miscompiled libgl1-mesa-dri. See https://bugs.launchpad.net/distros/ubuntu/+source/mesa/+bug/62135

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=394311

tuxkart and ppracer are fine now, but the vid mode thing is still sometimes a problem.

The original bug can be closed, since the driver has supported i965 since Edgy. There is a newer driver in Feisty, and if it doesn't fix the other issues please file separate bugs (first check for duplicates)