[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#420203: Config and logs



Brice Goglin wrote:
forwarded 420203 https://bugs.freedesktop.org/show_bug.cgi?id=10623
thank you

luben karavelov wrote:
Screen 0: minimum 320 x 200, current 1280 x 768, maximum 1280 x 1280
VGA connected 1280x768+0+0 normal (normal left inverted right) 0mm x 0mm
	Identifier: 0x4b
	Timestamp:  303234099
	Subpixel:   unknown
Clones: CRTC: 0
	CRTCs:      0
  1280x800 (0x4c)   83.5MHz
        h: width  1280 start 1344 end 1480 total 1680 skew    0 clock   49.7KHz
        v: height  800 start  801 end  804 total  828           clock   60.0Hz
  1280x768 (0x4d)   80.1MHz
        h: width  1280 start 1344 end 1480 total 1680 skew    0 clock   47.7KHz
        v: height  768 start  769 end  772 total  795           clock   60.0Hz
  1024x768 (0x4e)   65.0MHz
        h: width  1024 start 1048 end 1184 total 1344 skew    0 clock   48.4KHz
        v: height  768 start  771 end  777 total  806           clock   60.0Hz
  800x600 (0x4f)   40.0MHz
        h: width   800 start  840 end  968 total 1056 skew    0 clock   37.9KHz
        v: height  600 start  601 end  605 total  628           clock   60.3Hz
  640x480 (0x50)   25.2MHz
        h: width   640 start  656 end  752 total  800 skew    0 clock   31.5KHz
        v: height  480 start  490 end  492 total  525           clock   59.9Hz


Ok this shows that only 5 resolutions are detected, and 1280x768 is
chosen by default for some reason. Note that you may use 'xrandr
--output VGA --mode 1024x768' to change to 1024x768 at runtime. It looks
like your old 1280x1024 is not detected here because hsync and vrefresh
are out of range.

Ok, thanks. For now I am using the old i810-1.7.2 driver. It gives me 1200x1024 @ 85 Hz refresh.

BTW, do you use a package such as 915resolution? IIRC, it is not
required anymore since it modifies BIOS tables that are not used anymore
by the new driver.

No, I am not using it.

I see that you already reported the bug at
https://bugs.freedesktop.org/show_bug.cgi?id=10623 so I am marking this
bug as forwarded.

Brice


Thanks, yes. I first reported it there. The driver was still in "experimental" but now is in "unstable" so I have decided to report it at debian also.

Best regards
luben



Reply to: