Summary: | x11-drivers/xf86-video-i810-2.0.0: low resolution mode, not changeable | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin von Gagern <Martin.vGagern> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | rane, sven.koehler |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.freedesktop.org/show_bug.cgi?id=10860 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
diff of Xorg verbose log from 2.0.0 to 1.7.4
xorg.conf xrandr output with the old 1.7.4 driver xrandr output with the new 2.0.0 driver Xorg backtrace after failed xrandr call |
Description
Martin von Gagern
2007-04-29 20:41:20 UTC
Created attachment 117670 [details, diff]
diff of Xorg verbose log from 2.0.0 to 1.7.4
This is not really a patch, but as a diff output the patch markup facilities might be useful nonetheless. I started Xorg (without any window manager or other apps) twice, once with the broken 2.0.0 driver, and once with the working 1.7.4 driver. I used -logverbose in both cases and also have ModeDebug enabled.
Of special interest to mee seems this line:
-(II) intel(0): Output VGA using initial mode 1152x768
That is the only mode available.
Created attachment 117672 [details]
xorg.conf
This is my X.org configuration file, in case you are interested in my settings.
Oh yes, and this is the hardware according to lspci:
00:02.1 Display controller: Intel Corporation 82915G Express Chipset Family
Graphics Controller (rev 04)
Subsystem: ASUSTeK Computer Inc. P5GD1-VW Mainboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 0
Region 0: Memory at bfd00000 (32-bit, non-prefetchable) [size=512K]
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Make sure you have the RandR 1.2 headers, lib and client and attach the output of 'xrandr'. Please reopen when you respond to comment #3. (In reply to comment #3) > Make sure you have the RandR 1.2 headers, lib and client and attach the output > of 'xrandr'. I don't know about randr headers, but I have the 1.2 lib and client. The output of xrandr even increased, in number of resolutions as well as in rates per resolution. My desired mode of 1600x1200 is there as well. I managed to have a wrapper session script call xrandr before starting my window manager, and as a result I now have my usual resolution back. The hotkeys to change resolution however still don't work. Created attachment 117926 [details]
xrandr output with the old 1.7.4 driver
Created attachment 117928 [details]
xrandr output with the new 2.0.0 driver
Created attachment 117929 [details]
Xorg backtrace after failed xrandr call
While experimenting with xrandr, I once called it from another vt which at that time was in text mode. As a result my monitor switched to standby mode and remained there. Logging in from another machine via ssh I found out that the X server had died, and I had to reboot the system via ssh to get my video output back. Attached is a backtrace from the Xorg log of that X server session.
Do you believe this to be related to my driver problem, or is this a separate bug for xorg-x11 or xrandr?
There is a forum thread on this: http://forums.gentoo.org/viewtopic-t-555058.html Which X server version are you using? 1.3? (In reply to comment #10) > Which X server version are you using? 1.3? Yes, 1.3.0.0. Basically I have an up-to-date (daily) ~x86 system. (In reply to comment #11) > (In reply to comment #10) > > Which X server version are you using? 1.3? > > Yes, 1.3.0.0. Basically I have an up-to-date (daily) ~x86 system. > Thanks. Please find or file a new bug upstream at https://bugs.freedesktop.org and post the link here. Thanks! (In reply to comment #12) > Please find or file a new bug upstream at https://bugs.freedesktop.org and post > the link here. Thanks! Found one: https://bugs.freedesktop.org/show_bug.cgi?id=10860 Changed URL accordingly, overwriting the forum link from comment 9. (In reply to comment #13) > Found one: https://bugs.freedesktop.org/show_bug.cgi?id=10860 > Changed URL accordingly, overwriting the forum link from comment 9. > Thanks for doing that. |