[Hardy] system freezes after start with Intel driver (Intel G35)

Please rename your file /etc/X11/xorg.conf and restart X. Maybe it is just a configuration issue. If system still hangs please attach the following information:

List any versions you tried that did not have this issue
Does the keyboard LED come on when hitting the CAPSLOCK key?

/var/log/Xorg.0.log
/var/log/Xorg.0.log.old
~/.xsession-errors
output of cat /proc/acpi/video/*/DOS
output of sudo cat /proc/acpi/dsdt

<<List any versions you tried that did not have this issue>>
xserver-xorg-video-intel (2:2.2.1-1ubuntu2)
xserver-xorg-video-intel (2:2.2.1-1ubuntu1)
xserver-xorg-video-intel (2:2.2.1-1)
xserver-xorg-video-intel (2:2.2.0.90-3)

<<Does the keyboard LED come on when hitting the CAPSLOCK key?>>
CAPSLOCK key doesn't work

lex@kubuntu:~$ cat /proc/acpi/video/*/DOS
cat: /proc/acpi/video/*/DOS: Nessun file o directory (in English "No files or directories")

Sorry....I wrong....
<<List any versions you tried that did not have this issue>>
xserver-xorg-video-intel (2:2.2.1-1ubuntu1)
xserver-xorg-video-intel (2:2.2.1-1)
xserver-xorg-video-intel (2:2.2.0.90-3)

How to downgrade the package please? I tried:

sudo apt-get install xserver-xorg-video-intel=2.2.1-1ubuntu1
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso
Lettura delle informazioni di stato in corso... Fatto
E: Non è stata trovata la versione '2.2.1-1ubuntu1' per 'xserver-xorg-video-intel'

Thanks

The problem is that packages are removed from mirrors after upgrade so it isn't that easy afaik. I would stick with Vesa or maybe i810 driver until the fix is released.

1ubuntu1 didn't even build, so you could not have that one running.. I guess some drm backport broke it, they were introduced in the -10 kernel. Try an older kernel first if you have one installed.

I tried with kernel 2.6.24-8-generic and kernel vanilla 2.6.24.3 but I have same problem.
Driver i810 works with 2.6.24-8-generic, 2.6.24-10-generic and kernel vanilla.
Direct rendering works with driver i810
I think it is not a problem of kernel

Ok, changing back to the driver.

check if you have the old package in the cache: /var/cache/apt/archives, and if yes, check which one is the last one that worked.

I guess the problem is that /var/cache/apt/archives is cleaned regularly.

Yes, /var/cache/apt/archives is cleaned :-(
Where can I retrieve the package 2:2.2.1-1ubuntu1 ? Is there in live cd?

Now, I tried with this package:
xserver-xorg-video-intel_2.2.0.90-2ubuntu7_amd64.deb
works :-)

Same issue with xserver-xorg-video-intel (2:2.2.1-1ubuntu4)

The package xserver-xorg-video-intel_2.2.0.90-2ubuntu7_amd64.deb worked fine for you? Do you could post your Xorg.0.log if it worked?

Does it work if you replace the driver intel or vesa with i810 in xorg.conf?

If the i810 driver works fine I guess it is the best to push it upstream.
There are two possibilities: You could open a bug report and attach the needed information (http://intellinuxgraphics.org/how_to_report_bug.html) or you provide it here and we create it for you.

Btw. please add the line
option "ModeDebug" "yes"
to your xorg.conf device section before creating/uploading new Xorg.0.logs.

xserver-xorg-video-intel_2.2.0.90-2ubuntu7_amd64.deb worked fine for me with driver "intel" in xorg.conf
xserver-xorg-video-intel (2:2.2.1-1ubuntu4) my system freezes with driver "intel" in xorg.conf
i810 and vesa in xorg.conf works with 2.2.0.90-2ubuntu7 and 2:2.2.1-1ubuntu4
I open a bug report in intellinuxgraphics.org, thanks
I added in xorg.conf ModeDebug, this is the log after start with xserver-xorg-video-intel_2.2.0.90-2ubuntu7_amd64.deb (works)

This is the log after start with xserver-xorg-video-intel (2:2.2.1-1ubuntu4) (doesn't works, system freezes)

Thanks. Please post the link to your report afterwards so we can keep track.

Where I can open a bug?
https://bugs.freedesktop.org/ is down.....

Okay, from the investigation so far, it looks like the issue occurred on the intel driver between -1ubuntu2 and -1ubuntu3. That would indicate that our change to switch on "greedy" is what did it.

So the questions we need to answer are - does this work if EXA is on but "greedy" disabled, or will it only work with XAA? While using 2:2.2.1-1ubuntu1 or 2:2.2.1-1ubuntu2, please test both options "EXA" and "XAA". If "EXA" works, then also try setting the "MigrationHeuristic" "greedy" option and see if that reproduces the freeze.

2.2.1-1ubuntu11 works with:

Section "Device"
        Identifier "Intel Corporation 965 G1 Integrated Graphics Controller"
        Driver "intel"
        BusID "PCI:0:2:0"
        VideoRam 262144
        Option "AccelMethod" "EXA"
        Option "MigrationHeuristic" "greedy"
        Option "ExaNoComposite" "false"
EndSection

If cpu is overclocked, FSB 450Mhz (x8 ->@3600Mhz), system freezes after start with 2.2.1-1ubuntu11 but with 2.2.0.90-2ubuntu7 or vesa does not happen and system is rock solid...imho, this is very strange.

Sorry, is not a overclock issue. Unfortunately the issue occurs randomly when in xorg.conf I have:
Section "Device"
        Identifier "Intel Corporation 965 G1 Integrated Graphics Controller"
        Driver "intel"
        BusID "PCI:0:2:0"
        VideoRam 393216
        Option "AccelMethod" "EXA"
        Option "MigraionHeuristic" "greedy"
        Option "ExaNoComposite" "false"
EndSection

and also:

Section "Device"
        Identifier "Intel Corporation 965 G1 Integrated Graphics Controller"
        Driver "intel"
        BusID "PCI:0:2:0"
        VideoRam 393216
        Option "AccelMethod" "XAA"
EndSection

Bios setting for Integrated video card:
DVMT Mode Select -> DVMT Mode
DVMT/Fixed Memory -> Maxim DVMT (384 Mb)

How to for debug?
Thanks

Ok. Now I built intel driver from git (http://intellinuxgraphics.org/download.html) and works really good with any xorg.conf I tried (EXA with MigraionHeuristic greedy or XAA)
I tried to reboot or shutdown and start my system several times, I had no issue this time and I have "direct yes" even without building DRM kernel module and Mesa 3D GL driver.

I have the same problem, are there new drivers available (e.g. in repository) for download that doesnt need to be complied?

Best regards

Hi Ola Ekedahl.... I'm using xf86-video-intel-2.3.0 and this works for me. New drivers in repository doesn't works in my system. You can try with sources in attachment
Regards

Thanks for letting us know that it works with -intel 2.3.0. We've got -intel 2.3.2 uploaded into Intrepid, so closing this bug as fixed.

I've opened a Hardy task. If someone would like to do a git-bisect and identify which patch(es) are needed, we can consider SRUing them for Hardy.

I have built several machines with Asus P5E-V HDMI mainboards (G35 chip set), and I can confirm that the xserver-xorg-video-intel in version 2.2.1 still locks the systems randomly. Other people confirm this as well in http://ubuntuforums.org/showthread.php?t=647449&page=12 ff.

Version 2.3.2 from Intrepid (Debian Lenny has it as well) works fine, so could you please provide that updated Intel driver for Hardy? I've tried it myself, but due to dependency issues I never got the Intrepid driver working in Hardy, even after additionally installing/changing to the newer xserver-xorg-core, and libgl1-mesa-dri (still had no kbd and mouse after that).

TIA,
Wolfgang

Ok; I have a workaround which fixed it for me: take the 2.3.2 version (32 or 64 bit) from Debian Lenny, which doesn't depend on the latest xorg core. You can download them from:

http://packages.debian.org/lenny/i386/xserver-xorg-video-intel/download (32 bit), or from
http://packages.debian.org/lenny/amd64/xserver-xorg-video-intel/download (64 bit).

That solved it for us for the moment. In fact I only discovered the bug after installing Ubuntu, with my wife's Lenny, the hardware just worked fine.

HTH,
Wolfgang

I can confirm that Wolfgang's workaround works nicely. However, it depends on the libdrm2 package for lenny, which can be found here:

(32bit) http://packages.debian.org/lenny/i386/libdrm2/download
(64bit) http://packages.debian.org/lenny/amd64/libdrm2/download

best regards,
Bartek

As no patch has been isolated, we won't be SRUing a fix for this. The workaround listed in recent comments can suffice for anyone who cannot upgrade.