Summary: | x11-drivers/xf86-video-i810-2.0.0 crashes Xorg with dual head | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fred Röhner <Fred> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED UPSTREAM | ||
Severity: | critical | CC: | radek, shahar.evron, sven.koehler |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | https://bugs.freedesktop.org/show_bug.cgi?id=10945 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Fred Röhner
2007-04-24 07:40:18 UTC
I got similar errors when I upgraded to 2.0.0, however, it made no difference whether I used single or dual head layouts (also tried not running 915resolution, no change). Downgrading solved the problem. This happened with an Intel 945GM in a Macbook. Same thing happens to me when using dual head and 2.0.0 - works fine for single head. Had to downgrade back to 1.7.4 for dual head to work. System is a Dell D420. From lspci: 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) Which X server version are you guys using? (In reply to comment #3) > Which X server version are you guys using? > Fatal server error: Caught signal 11. Server aborting Same Problem here: I am using: x11-base/xorg-x11-7.2 x11-base/xorg-server-1.2.0-r3 What happens if you update your server to 1.3? I have the same issue with xorg-server 1.3.0 Doesn't matter whether I'm on dual head or not. This is to be expected as Intel has changed the internal stuff. The dual-head setup is now achieved using xrandr and not MonitorLayout anymore. I've just finished solving this in debian. See http://lists.freedesktop.org/archives/xorg/2007-May/024411.html Yes, unfortunately, this is an upstream bug that is known about in the new 2.0 intel driver. It's not a gentoo bug. (In reply to comment #9) > Yes, unfortunately, this is an upstream bug that is known about in the new 2.0 > intel driver. Alan: Is there an upstream bugzilla bug that we could link this to? Sure.... https://bugs.freedesktop.org/show_bug.cgi?id=10945 not much there, but I know about it and so does Eric. Great. Please reopen the bug once it's fixed upstream. |