|
Bugzilla – Full Text Bug Listing |
| Summary: | wrong X resolution | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Robert Love <rml> |
| Component: | Installation | Assignee: | Steffen Winterfeldt <snwint> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | suse-beta |
| Version: | Beta 7 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
output of `hwinfo --monitor --log=hwinfo.log`
`hwinfo --monitor --log=hwinfo.log` as root log from `sax2 -r` as root |
||
|
Description
Robert Love
2006-03-09 22:30:55 UTC
Here is the output of `hwinfo`. Oddly, it says the resolution is 1024x768, even though I am currently in the correct 1280x1024.
$ /usr/sbin/hwinfo --monitor
23: 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: 1024x768@76Hz
Driver Info #0:
Max. Resolution: 1024x768
Vert. Sync Range: 50-90 Hz
Hor. Sync Range: 31-61 kHz
Config Status: cfg=new, avail=yes, need=no, active=unknown
Currently using "VESA 1280X1024@75HZ" as the driver. During install, however, SaX autodected "VESA 1024X768@60HZ" Monitor is a Sony SDM-S93 1280x1024 19" your LCD wasn't detected by hwinfo (libhd) What does 'hwinfo --monitor --log=xxx' say? Created attachment 72613 [details]
output of `hwinfo --monitor --log=hwinfo.log`
Attached above. Please run as 'root. Created attachment 72619 [details]
`hwinfo --monitor --log=hwinfo.log` as root
Marcus, hwinfo sees it correctly. comment 1 was done as non-root user. In this case sax has to see the same values. Please call from a commandline as root sax2 -r and send me the log file /var/log/SaX.log If the log shows correct results I assume a problem while calling int10 (BIOS interrupt for reading DDC data) when a framebuffer X-server is active like it is the case during installation. I sometimes got that issue but it couldn't be solved because we are bound to that BIOS interrupt. Let's see what the log includes Thanks Created attachment 72635 [details]
log from `sax2 -r` as root
I see that it now lists the monitor model correctly, but it did not use to. During installation it thought it was a generic VESA. yes this is exactly the problem which happens sometimes. I assume this is a conflict with the active framebuffer X-Server while YaST is currently running but this is a wild guess and I wasn't able to reproduce this safely. Steffen as you can see in the last SaX.log the monitor is detected in the same way as hwinfo does... of course it's the same library :-) Could you imagine why calling in10 sometimes failed ? I'm aware that there are machines where monitor detection sometimes works, sometimes not. But I'd need direct access to such a beast to look at it. If you happen to come across one, let me know. |