Bug 112972

Summary: Unable to change monitor geometry manually
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Fabrizio Magni <fabrizio.magni>
Component: SaX2Assignee: Marcus Schaefer <ms>
Status: RESOLVED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Beta 3   
Target Milestone: ---   
Hardware: i686   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: SaX.log after trying to change the geometry
forgot to attach the log

Description Fabrizio Magni 2005-08-25 13:28:54 UTC 
This is almost the same as bug #105432.

After installation I'm not able to change the monitor geometry via SaX.

# hwinfo --monitor
20: None 00.0: 10000 Monitor
  [Created at fb.70]
  Unique ID: rdCR.EY_qmtb9YY0
  Hardware Class: monitor
  Model: "Generic Monitor"
  Vendor: "Generic"
  Device: "Monitor"
  Resolution: 800x600@75Hz
  Driver Info #0:
    Max. Resolution: 800x600
    Vert. Sync Range: 50-90 Hz
    Hor. Sync Range: 31-48 kHz
  Config Status: cfg=new, avail=yes, need=no, active=unknown


I'm uploading SaX.log
Comment 1 Fabrizio Magni 2005-08-25 13:30:13 UTC 
Created attachment 47553 [details]
SaX.log after trying to change the geometry
Comment 2 Marcus Schaefer 2005-08-26 09:35:34 UTC 
according to your log you want to use the resolution 1152x864. Well 
SaX did it correct but the driver (i810) is bound to the BIOS and your 
BIOS doesn't offer that resolution therefore the driver denied to use 
it. 
 
you can get information how to handle your broken BIOS here: 
 
   http://perso.wanadoo.fr/apoirier/ 
 
This tools are not supported so be carefull :-)
Comment 3 Fabrizio Magni 2005-08-26 10:12:50 UTC 
Yes, I know the problem and the page... I fought enough against the
incapabilities of my BIOS. :(

I sometimes hope to find that driver already integrated in new X version.

However even on a lower resolution I get the same problem.
The geometry cannot be changed manually by SaX.

The log shows several command returned (null).

Is it still my BIOS fault?
Comment 4 Fabrizio Magni 2005-08-26 11:33:41 UTC 
Created attachment 47754 [details]
forgot to attach the log