xf86-video-intel 1.9.91 (2.0 RC1) is out, and would be nice to have as the source for the xserver-xorg-video-i810-modesetting package

As evidence in support of including a new version of this package:

I just purchased a new Dell Optiplex 745. It comes with an Intel Q965 (aka GMA3000) video chipset. I use a Dell 2005FPW widescreen display which has a native resolution of 1680x1050. (The problems described below occurred on both the DVI and VGA ports.)

In the install, as widely documented, it first comes up as 1280x1024. No amount of playing with 915resolution, Modelines, etc. could get it to do any better. (I don't remember all the steps I took, but I've been using Linux as my primary desktop for over a decade, so I'm pretty familiar with XF86 and various tricks to get it working on weird/new hardware, and I followed every tip I could find that seemed relevant.)

I installed the modesetting driver, which got further... now Xorg would run in 1680x1050 mode except for some reason it seemed to be doing so in a mode my display couldn't recognize. The display said "Cannot display this mode". Again, no amount of modeline tinkering would work (and, regardless, the modeline it claimed to be using in Xorg.0.log was the correct one even without my tinkering).

Then I noticed Debian experimental had a version of the deb: xserver-xorg-video-intel-modesetting_1.7.2.git20070213-1_i386.deb

I installed this deb, and everything immediately worked. This saved me from having to find another video card or return the computer.

I don't know if it's too late in the release cycle to add a new version, but I think there are likely to be others like me who would appreciate it.

Update the request to xf86-video-intel 1.9.92 (2.0 RC2) Since it's now out. Maybe we'll have 2.0 official out before feisty is released.

I have the same problem with an external Dell 2005FPW widescreen display with a native resolution of 1680x1050.

I have a laptop (Thinkpad X60 tablet) with an internal display of 1400x1050.

I have been able to instruct the driver to set the internal display to 1680x1050--it pans, which is the right thing to do. Idiotically enough, the card now sends a 1680x1050 signal to the monitor that exactly mimics the panning (and is slightly fuzzy).

This uses clone mode. Trying to use CRT+LDS fails with a messed-up display.

Another Thinkpad with an ATI card can do 1400x1050 internal/1680x1050 external just fine, so I don't think I am asking for something crazy.

Hi all,
       I made a longish post at http://www.ubuntuforums.org/showthread.php?p=2367180#post2367180 . To put things briefly, from the moment the Live CD loads, the install happens, the desktop comes up it all happens in 640*480 . I have an i845 chipset using 17" Philips 107E5 CRT monitor. So each install is from an alternate CD. This has been the case for Edgy as well as the Feisty Beta, unable to install via the GUI. Even when everything is installed, I'm able to do nothing as every screen is cut-off, the only good thing I can do on this is to play mahjong :( No productive work as every application's windows gets cut & I can't access/read the bottom half. I don't think I'm asking for too much. It's been 5 days since I've been trying to get it done right :(

please test the 2.0rc3 deb:

http://users.tkk.fi/~tjaalton/xorg72/new/xserver-xorg-video-intel_1.9.93-1ubuntu1_i386.deb

I'm running the xserver-xorg-video-intel_1.9.93-1ubuntu1_i386.deb driver and it seems to work but the log is rather big with some SDVO messages. My desktop also froze up but I can't say for sure this was Xorg related but if it happens again I suspect it is this version of the driver.

This is on an intel DG965SS board with a WINTEC 35111140-R dual-DVI ADD2 card.

I left out all the messages related to SDVOCTRL from the attached log file, here's a snippit of those messages.

(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" registered at address 0x70.
Getting SDVOCTRL_E for SDVOB: ^ ^
SDVOCTRL_E for SDVOB Debug: C D C D
Setting SDVOCTRL_E for SDVOB 0x00005020 to: ^ ^
Getting SDVOCTRL_E for SDVOB: ^ ^
Getting SDVOCTRL_E for SDVOB: ^ ^
Setting SDVOCTRL_E for SDVOB 0x00005020 to: ^ v
Getting SDVOCTRL_E for SDVOB: ^ v
Setting SDVOCTRL_E for SDVOB 0x00005020 to: v v
Getting SDVOCTRL_E for SDVOB: v v
Setting SDVOCTRL_E for SDVOB 0x00005020 to: v v
Getting SDVOCTRL_E for SDVOB: v v
Setting SDVOCTRL_E for SDVOB 0x00005020 to: ^ v

The original log was 35M+ and 750K lines with the above messages.

Timo,
        I tried to test it, but dependencies error showed up, but I think I'm getting ahead of myself. First of all I did Ctrl+Alt+F1 so I'm on the cmd line tty1. The first time I tried to install it gave a conflict error.
Then I gave the command :-
dpkg -i --force-conflicts xserver-xorg-video-intel_1.9.93-1ubuntu1_i386.deb While the command worked, it didn't do things as the 3 dependencies required :-
libc6 >= 2.5.0 ubuntu1 was required while I had 2.4-1
something other which was (>=2.3.0) while I had 2.2
and xserver-xorg-core (>=2:1.20-3ubuntu6) while I had 1:1.1.0-ubuntu12.1

   but not to worry would try it again for sure.

That deb is compiled for feisty, you're still running edgy.

The 2.0rc3 deb worked for me (Feisty beta, Thinkpad X60 tablet, 1400x1050 panel with i950 adapter and a Dell 1680x1050 monitor).

I use clone mode:

Option "MonitorLayout" "CRT,LDP"
Option "Clone" "true"

There are just two minor blemishes.

1) I added "Virtual 1680 1050" to the Display subsection. When I start X without the external monitor, then panning works on the laptop display, but when I attach the widescreen monitor, it doesn't pan.

2) Selecting the "Change screen resolution" applet in Gnome crashes X about every other time I try it.

I hope this does make it into the final release.

I have another question. ATI has a nifty command line utility (aticonfig) to probe monitors dynamically and enable them without restarting X. Is there anything comparable for the Intel cards?

The driver posted by Timo works beautifully. The way I did it was go to CTRL+ALT+F2 (actually all the terminal shells show big fonts, which by default is very bad but thtś another story). Then gave the following commands :-

sudo /etc/init.d/gdm stop
dpkg -i --force-conflicts xserver-xorg-video-intel_1.9.93-1ubuntu1_i386

after it was installed then

sudo /etc/init.d/gdm restart

this landed me right into 1152*768 & I was able to change resolutions on the fly, good job there Tim :)

I'm on AMD64, so I can't test the i386 Ubuntu package that was posted. However, I installed xserver-xorg-video-intel_1.9.92-1_amd64.deb and xserver-xorg-core_1.2.99.902-1_amd64.deb from Debian-experimental, and it seems to have resolved several issues for me. One of the resolved issues was a system freeze that would happen while my laptop's screen was powered off.

Oh, I forgot to add I am running Feisty here cheers :)

Just as an off-hand there is now a xf86-video-intel-1.9.94 (2.0 RC4) in works. So Tim it would be cool if you could make a .deb for that also. In couple of days I would be re-installing Feisty when https://wiki.ubuntu.com/FeistyReleaseSchedule the rebuilt Test Herd6 would be on my table.

ok sometimes the display would not come in after login. Here is a X.org .old output of the last one which didn t finish well.

Output of dmesg http://paste.ubuntu-nl.org/14060/

I have also been experiencing what seems to be x.org crashes. Maybe due to the experimental nature of the driver . See bug #104223 for details. Please lemme know if any more info. is needed.

Some more crashes, this time with different side-effect, See bug #105390 for details. Please lemme know if more info. is required.

The latest one is after todayś updates.

The crashes were due to something with my .gnome2 session so seemingly unrelated . See bug # 90213 . I have also filed bugs for Live CD showing incorrect resolution bug #106202 as well as something perhaps related or not bug #105871 . Thanx in advance

Hi all,
        seems 1.9.92 has been put in sources. I have made a forum post about it at http://ubuntuforums.org/showthread.php?t=410866 . Feel free to add stuff there.

Edit: That was 1.9.94 , This one was yesterday https://launchpad.net/ubuntu/feisty/+source/xserver-xorg-video-intel/ while this is what Hobsee did today https://launchpad.net/ubuntu/feisty/+source/xserver-xorg-video-intel/2:1.9.94-1ubuntu3

1.9.94 is now in Feisty, upstream released 2.0.0 and that might be uploaded to feisty-updates.

Don't know if the package works as-is in edgy.

right http://lists.freedesktop.org/archives/xorg/2007-April/023906.html

Thanks for the good work, Timo.

Regarding the 2.0.0 release, it still doesn't have basic functionality on my laptop (855GM chipset), but the next update will at least enable proper XV support for older chipsets (see https://bugs.freedesktop.org/show_bug.cgi?id=10645 and http://lists.freedesktop.org/archives/xorg/2007-April/023909.html). I'm glad you're uploading this to feisty-updates, and I hope that future point updates will appear when possible too ;)...

Hi Timo,
       i tried the 2.0 which is on your site. The driver does not change & remains at static 1152*768. Any attempt to change it either via the System > Preferences > Screen Resolution applet or by using xrandr to change it to something like 1024*768 @ 75 hz the session ends unexpectedly (without any dialog boxes or anything) and one is thrown into GDM login.

Hi Timo,
      Another addition to this one. Any of the applications, including nautilus doesn't show the left-hand bar. The first column, letter gets eaten. I would be putting up the two screenies so you have a good idea of what I mean.

Sorry for that long name, That's actually the Take screenshot fault/feature :)

shirishag75,

It's a better idea to submit your bugs upstream (bugs.freedesktop.org) - Timo's only packaging debs from their official/milestone releases and including some debian-specific patches. I have the same issue with the driver (compiled from upstream) as you, see the report here:

https://bugs.freedesktop.org/show_bug.cgi?id=10467

I reported too many issues there at once, so I plan to open a proper bug regarding the issue soon. Anything fixed upstream can be made available in Feisty through feisty-updates or feisty-proposed, but it's best to be fixed upstream first regardless.