SIS 6326 (and/or Monitor): low-res configuration in Kubuntu 7.10

Hi,

to get further infos on what got wrong, you may use :

https://help.ubuntu.com/community/DebuggingXAutoconfiguration

the xresprobe part being of importance as it is this tool that is used to get the resolution of the screen

I suspect the bug to be related to https://bugs.launchpad.net/ubuntu/+source/casper/+bug/93996

Regards

to be sure if your bug is related to the one mentioned above, the casper log would be helpful.

Thanks

Olivier Lacroix wrote:
> to be sure if your bug is related to the one mentioned above, the casper
> log would be helpful.
>
> Thanks
>
>
casper seems not to be installed. Should I install it?

xresprobe needs a driver parameter. Which command exactly should I run?

Sander

casper is only present on the liveCD : casper is responsible for launching the liveCD and therefore for autoconfiguring the system.

you shoud type :

"sudo xresprobe sis"

Olivier

The result is:

sander@athlon:~$ sudo xresprobe sis
id:
res: 800x600 720x450 640x480 1x1
freq:
disptype: crt
sander@athlon:~$

Sander

-------- Original-Nachricht --------
Datum: Mon, 23 Apr 2007 18:17:13 -0000
Von: Olivier Lacroix <email address hidden>
An: <email address hidden>
Betreff: [Bug 108843] Re: SIS 6326 (and/or Monitor): low-res configuration in Kubuntu 7.10

> casper is only present on the liveCD : casper is responsible for
> launching the liveCD and therefore for autoconfiguring the system.
>
> you shoud type :
>
> "sudo xresprobe sis"
>
> Olivier
>
> --
> SIS 6326 (and/or Monitor): low-res configuration in Kubuntu 7.10
> https://bugs.launchpad.net/bugs/108843
> You received this bug notification because you are a direct subscriber
> of the bug.

--
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail

Guess what ? I think we found the culprit !

xresprobe gives 800x600 as your monitor's maximal resolution and therefore the xorg.conf is badly automatically configured.

Olivier Lacroix wrote:
> Guess what ? I think we found the culprit !
>
> xresprobe gives 800x600 as your monitor's maximal resolution and
> therefore the xorg.conf is badly automatically configured.
>

Yes, OK, but: everything worked in 6.04 and 6.10. Is xresprobe something
new, or has it been changed? Why is this problem occurring now? Any idea
why xresprobe is reporting this low res?

Sander

yep, xresprobe has been updated since Edgy.

I am not a dev and have no idea why it is occuring. In fact feisty also badly configured my screen resolution, and searching for similar bugs, i found yours and tried to help you determine the origine of your problem... At least we found it :-)

you may try to contact Timo Aaltonen ( https://bugs.launchpad.net/~tepsipakki ) who is in charge of xresprobe for ubuntu or let him find your report by himself : he seems to be already working on several reports of misconfigured resolution in feisty

OK. Olivier, merci beaucoup.

Sander

Olivier Lacroix wrote:
> yep, xresprobe has been updated since Edgy.
>
> I am not a dev and have no idea why it is occuring. In fact feisty also
> badly configured my screen resolution, and searching for similar bugs, i
> found yours and tried to help you determine the origine of your
> problem... At least we found it :-)
>
> you may try to contact Timo Aaltonen (
> https://bugs.launchpad.net/~tepsipakki ) who is in charge of xresprobe
> for ubuntu or let him find your report by himself : he seems to be
> already working on several reports of misconfigured resolution in feisty
>
>

it's a feature.. if the monitor is a crt then the maximum resolution is dropped from the list. Your old config doesn't seem like it's been automatically generated.

and the reason why it is dropped is because on better crt's you can get insane resolutions otherwise.

I am not sure to understand...

setting the resolution as low as 800x600 on a monitor supporting 1280x854 is actually a feature ??

If it was to happen to any user, he would try to get back his usual resolution... and I don't think the normal user will be very pleased to do it by manually modifying his xorg.conf.

This is even more frustrating knowing that xresprobe could get it right :-)

Or did I miss something ?

Thanks

Olivier

Timo Aaltonen wrote:
> it's a feature.. if the monitor is a crt then the maximum resolution is
> dropped from the list.
Why? Is using the maximum resolution on a CRT bad for one's eyes? ;-)

> Your old config doesn't seem like it's been
> automatically generated.
>
Well, I guarantee you I have not generated, edited nor changed it
myself. The config was there after I installed 6.04 and 6.10. So it was
really automacitcally generated.

Sander

Sorry, I now realize a typo: Kubuntu 7.10 should read Kubuntu 7.04

Sander

Sander:

looking at your old configfile again, it's clear that it was not generated by the ubuntu installer.. It never has added Modelines for the user, so you or someone else has modified it :)

lowering the importance, hardly critical.

On 9/21/07, Timo Aaltonen <email address hidden> wrote:
>
> Sander:
>
> looking at your old configfile again, it's clear that it was not
> generated by the ubuntu installer.. It never has added Modelines for the
> user, so you or someone else has modified it :)

What is a "Modeline"? Is it a line with the word "mode", like:

  Modes "800x600" "720x450" "640x480" "1x1"
 Mode 0666

Shall I do a fresh install of 7.04 on the same machine to see what config is
generated? The Siemens monitor is gone, but the same SIS is available.

What if the fresh install also generates "modelines" ... ?

Sander

lowering the importance, hardly critical.
>
> ** Changed in: xresprobe (Ubuntu)
> Importance: Critical => Low
>
> ** Changed in: xresprobe (Ubuntu)
> Assignee: Ubuntu X SWAT (ubuntu-x-swat) => (unassigned)
>
> --
> SIS 6326 (and/or Monitor): low-res configuration in Kubuntu 7.10
> https://bugs.launchpad.net/bugs/108843
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Can you attach the output of sudo ddcprobe? I suspect Timo is right, however this output should confirm that. If it's the case, then this is a dupe of 27667.

Here's the output of "sudo ddcprobe" during a live boot session of Kubuntu
7.04, with the same SIS 6326 VGA card, but another monitor (Belinea) because
the Fujitsu Siemens is gone.

HTH

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686
GNU/Linux

ubuntu@ubuntu:~$ sudo ddcprobe
vbe: VESA 2.0 detected.
oem: SiS
memory: 4096kb
mode: 80x60 (text)
mode: 132x25 (text)
mode: 800x600x16
mode: 1024x768x16
mode: 1280x1024x16
mode: 1600x1200x256
mode: 640x400x256
mode: 640x480x256
mode: 800x600x256
mode: 1024x768x256
mode: 1280x1024x256
mode: 1600x1200x32k
mode: 320x200x32k
mode: 640x480x32k
mode: 800x600x32k
mode: 1024x768x32k
mode: 1280x1024x32k
mode: 320x200x64k
mode: 640x480x64k
mode: 800x600x64k
mode: 1024x768x64k
mode: 1280x1024x64k
mode: 1600x1200x64k
mode: 320x200x16m
mode: 640x480x16m
mode: 800x600x16m
mode: 1024x768x16m
mode: 1280x1024x16m
edid:
edid: 1 0
id: 0be0
eisa: MAX0be0
serial: 000016bb
manufacture: 10 1999
input: sync on green, analog signal.
screensize: 28 21
gamma: 1.500000
dpms: RGB, active off, suspend, standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 720x400@88 Hz (XGA2)
timing: 640x480@60 Hz (VGA)
timing: 640x480@67 Hz (Mac II, Apple)
timing: 640x480@72 Hz (VESA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@56 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 832x624@75 Hz (Mac II)
timing: 1024x768@87 Hz Interlaced (8514A)
timing: 1024x768@60 Hz (VESA)
timing: 1024x768@70 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
timing: 1280x1024@75 (VESA)
dtiming: 1280x1024@70
dtiming: 640x400@70
ubuntu@ubuntu:~$

On 9/28/07, Bryce Harrington <email address hidden> wrote:
>
> Can you attach the output of sudo ddcprobe? I suspect Timo is right,
> however this output should confirm that. If it's the case, then this is
> a dupe of 27667.
>
> ** Changed in: xresprobe (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> SIS 6326 (and/or Monitor): low-res configuration in Kubuntu 7.10
> https://bugs.launchpad.net/bugs/108843
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Hmm, since the monitor has changed, it won't be possible to verify that it was indeed a dupe, but I'm pretty sure it was.

In any case, from your ddcprobe output, it looks like Gutsy is going to get your resolution right now, given the improvements we've made to xresprobe. Please test with Gutsy-beta or newer, and feel free to reopen this bug in the off chance that the issue still exists.

FYI the sudo ddcprobe from Kubuntu 7.10 beta (live boot) on the same
hardware.

$ cat kubuntu710beta-sudo-ddcprobe.log

Linux ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686
GNU/Linux

vbe: VESA 2.0 detected.
oem: SiS
memory: 4096kb
mode: 80x60 (text)
mode: 132x25 (text)
mode: 800x600x16
mode: 1024x768x16
mode: 1280x1024x16
mode: 1600x1200x256
mode: 640x400x256
mode: 640x480x256
mode: 800x600x256
mode: 1024x768x256
mode: 1280x1024x256
mode: 1600x1200x32k
mode: 320x200x32k
mode: 640x480x32k
mode: 800x600x32k
mode: 1024x768x32k
mode: 1280x1024x32k
mode: 320x200x64k
mode: 640x480x64k
mode: 800x600x64k
mode: 1024x768x64k
mode: 1280x1024x64k
mode: 1600x1200x64k
mode: 320x200x16m
mode: 640x480x16m
mode: 800x600x16m
mode: 1024x768x16m
mode: 1280x1024x16m
edid:
edid: 1 0
id: 0be0
eisa: MAX0be0
serial: 000016bb
manufacture: 10 1999
input: sync on green, analog signal.
screensize: 28 21
gamma: 1.500000
dpms: RGB, active off, suspend, standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 720x400@88 Hz (XGA2)
timing: 640x480@60 Hz (VGA)
timing: 640x480@67 Hz (Mac II, Apple)
timing: 640x480@72 Hz (VESA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@56 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 832x624@75 Hz (Mac II)
timing: 1024x768@87 Hz Interlaced (8514A)
timing: 1024x768@60 Hz (VESA)
timing: 1024x768@70 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
timing: 1280x1024@75 (VESA)
dtiming: 1280x1024@70
dtiming: 640x400@70

On 9/29/07, Bryce Harrington <email address hidden> wrote:
>
> Hmm, since the monitor has changed, it won't be possible to verify that
> it was indeed a dupe, but I'm pretty sure it was.
>
> In any case, from your ddcprobe output, it looks like Gutsy is going to
> get your resolution right now, given the improvements we've made to
> xresprobe. Please test with Gutsy-beta or newer, and feel free to
> reopen this bug in the off chance that the issue still exists.
>
> ** Changed in: xresprobe (Ubuntu)
> Status: Incomplete => Fix Released
>
> --
> SIS 6326 (and/or Monitor): low-res configuration in Kubuntu 7.10
> https://bugs.launchpad.net/bugs/108843
> You received this bug notification because you are a direct subscriber
> of the bug.
>