Re: Screen resolution problem with 8.04.1 and 8.10 I'm the originator of this thread. tgs1952 jumped in with his problem, thinking it is the same, but it would have been better (less confusing) if he had begun his own thread. At any rate, welcome thomasaaron from System 76! My Ratel is the 1000 and my monitor is a Medion 17 inch LCD color. Its book-recommended resolution is 1024x768, but with Ubuntu 6.06 and prior versions, it defaulted to 1280x1024--which I prefer.
With 8.04.1 and also 8.10 (and also Debian etch), the xorg.conf file lists "configured monitor" in the monitor Identifier section, "configured video device" in the Device Identifier section and "Default Screen" in the Screen Identifier section. Of course, in 6.06 specific information was given in the xorg.conf. Monitor identifier listed "MD9404QB" with option "DPMS". Under Device > Identifier was listed "Generic video card", and as driver "vesa". I can give you the lot if you need it.
xrandr gives this: haas@desktop:~$ xrandr Screen 0: minimum 320 x 240, current 800 x 600, maximum 960 x 600 default connected 800x600+0+0 0mm x 0mm 960x600 60.0 960x540 60.0 800x600 60.0* 56.0 768x576 60.0 720x576 60.0 856x480 60.0 800x480 60.0 720x480 61.0 640x480 60.0 400x300 60.0 320x240 61.0
I read the Ubuntu wiki on troubleshooting wrong resolutions. Here it says to run xrandr, as suggested by a respondent. I ran it and it gave the same too-low and incorrect resolutions listed in the GUI for screen resolution. Then I ran sudo get-edid|parse-edid and this indicated an EDID fail, if I understood its lingo correctly. According to the wiki, this result means I'll need to manually configure my xorg.conf settings. Of course, my first attempt crashed xorg completely! The command's result is below:
haas@desktop:/etc/apt$ sudo get-edid|parse-edid parse-edid: parse-edid version 1.4.1 get-edid: get-edid version 1.4.1
Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 Function supported Call successful
VBE version 300 VBE string at 0x11110 "SiS"
VBE/DDC service about to be called Report DDC capabilities
Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0 Function supported Call successful
Monitor and video card combination does not support DDC1 transfers Monitor and video card combination does not support DDC2 transfers 0 seconds per 128 byte EDID block transfer Screen is not blanked during DDC transfer
Reading next EDID block
VBE/DDC service about to be called Read EDID
Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function supported Call failed
The EDID data should not be trusted as the VBE call failed parse-edid: EDID checksum failed - data is corrupt. Continuing anyway. parse-edid: first bytes don't match EDID version 1 header parse-edid: do not trust output (if any).
# EDID version 1 revision 3 Section "Monitor" # Block type: 2:0 3:fd # Block type: 2:0 3:fc Identifier "MD9404QB" VendorName "MED" ModelName "MD9404QB" # Block type: 2:0 3:fd HorizSync 30-83 VertRefresh 50-75 # Max dot clock (video bandwidth) 140 MHz # Block type: 2:0 3:fc # Block type: 2:0 3:fe # DPMS capabilities: Active off:yes Suspend:yes Standby:no
Mode "1280x1024" # vfreq 60.020Hz, hfreq 63.981kHz DotClock 108.000000 HTimings 1280 1328 1440 1688 VTimings 1024 1025 1028 1066 Flags "+HSync" "+VSync" EndMode # Block type: 2:0 3:fd # Block type: 2:0 3:fc # Block type: 2:0 3:fe EndSection
The video card in the Ratel is "Integrated Graphics -- SIS Real2" (from your sheet) and "VGA compatible controller: Silicon Integrated Systems (SIS) 661/741/760/761 PCI/AGP VGA Display Adapter" (from lspci|grep VGA).
What do you think--do I need to hand-configure xorg.conf, and if so, can you make recommendations about how to do this? What is the driver for this card? I'm surprised that "vesa" was listed in xorg.config as the driver in 6.06, and yet 6.06 ran perfectly.
Thanks, David