gutsy too high resolution

[mikko]

I have Acer Aspire 1362LC laptop, 15" XGA lcd-monitor, Via K8M800 display adapter

Gutsy live cd starts always in 1400x1050, but I want 1024x768. Feisty worked without problems, 1024x768 was always the default resolution.
I can't change resolution in Screen and Graphics Preferences. And at first, I can see only the upper left corner, but after pressing Ctrl-Alt-- or Ctrl-Alt-+ a couple of times, I can see the rest of my desktop. Not all at the same time, but when I move the cursor to the right edge, I can see also the right side because of desktop moves. The desktop doesn't move without Ctrl-Alt-- command.

[mikko (mikko-)]

gutsy tribe 5
I don't have an external monitor but I know 1400x1500 is max resolution for it, laptop lcd only 1024x768. Why xorg offers ext. monitor resolution to my laptop's lcd-screen?

ubuntu@ubuntu:~$ xrandr
Screen 0: minimum 640 x 480, current 1400 x 1050, maximum 1400 x 1050
default connected 1400x1050+0+0 0mm x 0mm
   1400x1050 60.0*
   1280x1024 61.0
   1280x800 60.0
   1280x768 61.0
   1024x768 85.0
   800x600 86.0
   640x480 86.0
ubuntu@ubuntu:~$

ubuntu@ubuntu:~$ lspci -vvnn
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter [1106:3108] (rev 01) (prog-if 00 [VGA])
        Subsystem: Acer Incorporated [ALI] Unknown device [1025:006e]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (500ns min)
        Interrupt: pin A routed to IRQ 22
        Region 0: Memory at f0000000 (32-bit, prefetchable) [size=64M]
        Region 1: Memory at d1000000 (32-bit, non-prefetchable) [size=16M]
        Capabilities: <access denied>

[mikko (mikko-)]

Xorg.0.log

(II) VIA(0): Trying VBE Mode 640x480 (0xc112)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
(II) VIA(0): Trying VBE Mode 800x600 (0xc115)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
(II) VIA(0): Trying VBE Mode 1024x768 (0xc118)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
(II) VIA(0): Trying VBE Mode 1280x768 (0xc17b)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
(II) VIA(0): Trying VBE Mode 1280x800 (0xc1b8)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
(II) VIA(0): Trying VBE Mode 1280x1024 (0xc11b)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
(II) VIA(0): Trying VBE Mode 1400x1050 (0xc13e)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
(II) VIA(0): Trying VBE Mode 640x480 (0xc112)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
(II) VIA(0): Trying VBE Mode 800x600 (0xc115)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
(II) VIA(0): Trying VBE Mode 1024x768 (0xc118)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
(II) VIA(0): Trying VBE Mode 1280x768 (0xc17b)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
(II) VIA(0): Trying VBE Mode 1024x768 (0xc118)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
(II) VIA(0): Trying VBE Mode 1280x768 (0xc17b)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.
(II) VIA(0): Trying VBE Mode 1024x768 (0xc118)
(II) VIA(0): VBESetVBEMode failed...but worked OK without customized refresh and dotclock.

[mikko (mikko-)]

ubuntu@ubuntu:~$ sudo ddcprobe
vbe: VESA 3.0 detected.
oem: VIA K8N800
vendor:
product:
memory: 65536kb
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x256
mode: 1280x1024x256
mode: 80x60 (text)
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 1600x1200x256
mode: 1600x1200x64k
edid:
edidfail

[mikko (mikko-)]

same bug?
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/131734

[mikko (mikko-)]

same machine in feisty:

mikko@unelma-laptop:~$ xrandr
 SZ: Pixels Physical Refresh
*0 1024 x 768 ( 347mm x 260mm ) *61
 1 800 x 600 ( 347mm x 260mm ) 61
 2 640 x 480 ( 347mm x 260mm ) 60

My xorg.conf in feisty:
Section "Monitor"
 Identifier "Generic Monitor"
 Option "DPMS"
 HorizSync 28-51
 VertRefresh 43-60
EndSection

Why in gutsy xrandr shows this:
1024x768 85.0
I think 85 Hz is too much for laptop lcd.

[mikko (mikko-)]

messages from terminal after changing resolution to 1024x768 and pressing ok:
ubuntu@ubuntu:~$ sudo displayconfig-gtk

Gdk-ERROR **: The program 'displayconfig-gtk' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 13 error_code 2 request_code 157 minor_code 2)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Aborted (core dumped)

and after changing to 1024 and pressing test -button:
ubuntu@ubuntu:~$ sudo displayconfig-gtk
on_button_test_config_clicked()
xauth: creating new authority file /tmp/guidance.9794/xauthority
Got pid 9810
(0, 0)
displayconfig-gtk: Fatal IO error 104 (Connection reset by peer) on X server :9.0.

root@ubuntu:/tmp/guidance.9794# cat testserver.xoutput

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu
Current Operating System: Linux ubuntu 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686
Build Date: 26 July 2007
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.9.log", Time: Wed Sep 5 12:46:13 2007
(++) Using config file: "/tmp/guidance.9794/testserver.config"
(EE) Failed to load module "openchrome" (module does not exist, 0)
(EE) No devices detected.
Fatal server error:
no screens found

Is this openchrome driver problem????
"Failed to load module "openchrome" (module does not exist, 0)"

[mikko (mikko-)]

If I command dpkg-reconfigure xserver-xorg and select vesa, resolution works ok. But if select safe mode in live cd's boot menu, same resolution problem.

[mikko (mikko-)]

Via driver works ok. But why only after dpkg-reconfigure?

[mikko (mikko-)]

Also, only "dpkg-reconfigure -phigh xserver-xorg" and select 1024x768 shows the whole Desktop.