On 1/6/12 2:45 AM, Knut Petersen wrote:
1: Xorg.0.log is full of (besides timestamp) identical EDID entries:
==================================================
[ 2502.358] (II) intel(0): EDID vendor "ENC", prod id 5769
[ 2502.358] (II) intel(0): Using EDID range info for horizontal sync
[ 2502.358] (II) intel(0): Using EDID range info for vertical refresh
[ 2502.358] (II) intel(0): Printing DDC gathered Modelines:
[ 2502.358] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328
1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 2502.358] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056
600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 2502.358] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800
480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 2502.358] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900
400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 2502.358] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184
1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
Does this happen with no X apps running, just a naked X server? If so
you have something causing spurious hotplug interrupts. If not,
something in your session is querying the server a lot.
I believe gnome attempts to isolate calls to XRRGetScreenResources to
gnome-settings-daemon for precisely this reason (only one app really
needs to call it and the rest should query through the session bus).
5. Xorg fails to start without a manually created "Section Modules" in
config
=========================================================
see: https://bugs.freedesktop.org/show_bug.cgi?id=41208
You really do have a toolchain bug there.
- ajax
_______________________________________________
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
