Wolfgang Lauterbach wrote: > thank you for your answer. Well, I never before tried xrandr, and it did not > help me now. I think it is a bug in the intel driver. > I'll append my xorg.conf and two logfiles, one from the intel-driver, the > otherone from the old i810-driver, and the output of xrandr. > > When you search the logfiles for "Virtual", you can see, that the i810-driver > states: > (**) I810(0): Virtual size is 1824x1152 (pitch 2048) > (**) I810(0): *Built-in mode "1024x768" > ... > and gives me a correct virtual screen, within which I can move around, >
How do you move around in there? > while the intel-driver says: > . > . > (II) intel(0): Not using default mode "1280x960" (vrefresh out of range) > (II) intel(0): Not using default mode "1280x1024" (hsync out of range) > (II) intel(0): Not using default mode "1280x1024" (hsync out of range) > (II) intel(0): Not using default mode "1280x1024" (vrefresh out of range) > (II) intel(0): Not using default mode "1600x1200" (height too large for > virtual size) > (II) intel(0): Not using default mode "1600x1200" (height too large for > virtual size) > .(II) intel(0): Printing probed modes for output VGA > (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 > 964 1000 +hsync +vsync (60.0 kHz) > (II) intel(0): Output VGA connected > (II) intel(0): Output VGA using initial mode 1280x960 > > . > and in the end takes: > . > (II) intel(0): Printing probed modes for output VGA > (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 > 964 1000 +hsync +vsync (60.0 kHz) > (II) intel(0): Output VGA connected > (II) intel(0): Output VGA using initial mode 1280x960 > ... > a resolution, my screen is not capable of. > Ok, that's probably a resolution miss-detection problem. A couple other problems like this have been reported... > Section "Device" > BoardName "915 G" > BusID "0:2:0" > Driver "i810" > Identifier "Device[0]" > Option "NoDDC" > Option "usevnc" "no" > Screen 0 > VendorName "Intel" > # Option "UseEdidDpi" "0" > # Option "DPI" "93 x 93" > EndSection > Do you really need NoDDC here ? I thought the Intel driver 2.0 needed DDC to detect the supported resolutions... I don't know about "usevnc". > (II) intel(0): Attempting memory allocation with tiled buffers and > large DRI memory manager reservation: > (WW) intel(0): xf86AllocateGARTMemory: allocation of 10 pages failed > (Cannot allocate memory) > (II) intel(0): Allocating 4476 scanlines for pixmap cache > [...] > (WW) intel(0): ESR is 0x00000010, page table error > (WW) intel(0): PGTBL_ER is 0x00000010, display A pte > (WW) intel(0): PRB0_CTL (0x0000f001) indicates ring buffer enabled > (WW) intel(0): Existing errors found in hardware state. > [...] > (WW) intel(0): Option "usevnc" is not used > (WW) intel(0): Option "CalcAlgorithm" is not used > (--) RandR disabled > [...] > (II) intel(0): [drm] removed 1 reserved context for kernel > (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xdf9e1000 at 0xb7f70000 > (EE) intel(0): I830 Vblank Pipe Setup Failed 0 > Lots of warnings, most of them already reported upstream. > xrandr > Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1824 x 1152 > VGA connected 1024x768+0+0 (normal left inverted right) 54mm x 486mm > 1024x768 75.0*+ 75.1 70.1 60.0 > 832x624 74.6 > 800x600 72.2 75.0 60.3 56.2 > 640x480 75.0 72.8 66.7 60.0 > 720x400 70.1 > ----------------------------------------------- > This is xrandr with intel driver 2.0, right? There's no 1280x960 in there, I don't see how the driver might be choosing it then... Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
