Wow! Thanks. But I need more help. See below. On 20100312_131114, Stephen Powell wrote: > On Fri, 12 Mar 2010 10:58:08 -0500 (EST), Paul E Condon wrote: > > On 20100312_092355, Stephen Powell wrote: > >> > >> Paul, please provide the following information: > >> > >> (1) Make and model of your computer > > Compaq Presario S3200NX (sn MX31028632) > >> (2) Make and model of your video card > > integrated graphics on mother board > >> (3) Make and model of your monitor > > Acer X163W > >> (4) Your existing /etc/X11/xorg.conf file > > there is no such file. this is a new install done yesterday > > and I have not yet attempted any hacking > >> (5) The contents of /var/log/Xorg.0.log > > There follows 858 lines of the above named file: > > OK, we learn a lot from the /var/log/Xorg.0.log file. > > Your Integrated graphics card is > > > (--) PCI:*(0:1:0:0) 5333:8d04:1462:3908 S3 Inc. VT8375 [ProSavage8 > > KM266/KL266] rev 0, Mem @ 0xe1000000/524288, 0xd8000000/134217728, BIOS @ > > 0x????????/65536 > > I thought at first that the stuff within parentheses might be the chipset. > But I found out later that I was wrong. We'll see why in a minute. > X chose the "savage" driver. It lists the chipsets which it supports. > > > (II) SAVAGE: driver (version 2.3.1) for S3 Savage chipsets: Savage4, > > Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX, > > Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133, > > Twister PN133, Twister KN133, SuperSavage/MX 128, SuperSavage/MX 64, > > SuperSavage/MX 64C, SuperSavage/IX 128, SuperSavage/IX 128, > > SuperSavage/IX 64, SuperSavage/IX 64, SuperSavage/IXC 64, > > SuperSavage/IXC 64, ProSavage DDR, ProSavage DDR-K > > I'm not sure what to make of this next section. First it says it's defaulting > to 16 bit color. > > > (II) SAVAGE(0): Creating default Display subsection in Screen section > > "Builtin Default savage Screen 0" for depth/fbbpp 16/16 > > (==) SAVAGE(0): Depth 16, (--) framebuffer bpp 16 > > (==) SAVAGE(0): RGB weight 565 > > But then it says it's going to use true color mode, which requires at least > 24 bits! > > > (==) SAVAGE(0): Default visual is TrueColor > > And then we have this little tidbit. > > > (==) SAVAGE(0): Using video BIOS to set modes > > That's trouble. If it uses this method, then you're limited to the video > modes that are > pre-defined in the video BIOS. And if 1366x768 isn't one of them, too bad. > > > (--) SAVAGE(0): Chip: id 8d04, "ProSavage DDR-K" > > There's the actual chipset: ProSavage DDR-K, which is one of the supported > chipsets for this driver. (It's the last one listed.) > > > (--) SAVAGE(0): probed videoram: 32768k > > Plenty of video RAM to do true color mode even at 1366x768 resolution. > > 1366x768x24/1024 = 24588k; 1366x768x32/1024 = 32784k. > Hmm. If we have to use 32 bits of RAM per pixel, we may not have enough. > We'll see about that later. > > It did find the DDC2/EDID information about your monitor though: > > > (II) SAVAGE(0): Manufacturer: ACR Model: 15 Serial#: 2441181409 > > (II) SAVAGE(0): Year: 2009 Week: 18 > > (II) SAVAGE(0): EDID Version: 1.3 > > (II) SAVAGE(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V > > (II) SAVAGE(0): Sync: Separate > > (II) SAVAGE(0): Max Image Size [cm]: horiz.: 34 vert.: 19 > > (II) SAVAGE(0): Gamma: 2.20 > > (II) SAVAGE(0): DPMS capabilities: Off; RGB/Color Display > > (II) SAVAGE(0): Default color space is primary color space > > (II) SAVAGE(0): First detailed timing is preferred mode > > (II) SAVAGE(0): redX: 0.637 redY: 0.333 greenX: 0.284 greenY: 0.596 > > (II) SAVAGE(0): blueX: 0.154 blueY: 0.083 whiteX: 0.313 whiteY: 0.329 > > These are the VESA standard modes that the monitor supports: > > > (II) SAVAGE(0): Supported established timings: > > (II) SAVAGE(0): 720x...@70hz > > (II) SAVAGE(0): 640x...@60hz > > (II) SAVAGE(0): 640x...@67hz > > (II) SAVAGE(0): 640x...@72hz > > (II) SAVAGE(0): 640x...@75hz > > (II) SAVAGE(0): 800x...@56hz > > (II) SAVAGE(0): 800x...@60hz > > (II) SAVAGE(0): 800x...@72hz > > (II) SAVAGE(0): 800x...@75hz > > (II) SAVAGE(0): 832x...@75hz > > (II) SAVAGE(0): 1024x...@60hz > > (II) SAVAGE(0): 1024x...@70hz > > (II) SAVAGE(0): 1024x...@75hz > > More monitor stuff: > > > (II) SAVAGE(0): Manufacturer's mask: 0 > > (II) SAVAGE(0): Supported standard timings: > > (II) SAVAGE(0): #0: hsize: 1280 vsize 720 refresh: 60 vid: 49281 > > (II) SAVAGE(0): Supported detailed timing: > > (II) SAVAGE(0): clock: 85.5 MHz Image Size: 344 x 193 mm > > (II) SAVAGE(0): h_active: 1366 h_sync: 1435 h_sync_end 1578 h_blank_end > > 1790 h_border: 0 > > (II) SAVAGE(0): v_active: 768 v_sync: 771 v_sync_end 781 v_blanking: 798 > > v_border: 0 > > (II) SAVAGE(0): Ranges: V min: 50 V max: 75 Hz, H min: 30 H max: 80 kHz, > > PixClock max 160 MHz > > (II) SAVAGE(0): Monitor name: Acer X163W > > (II) SAVAGE(0): Serial No: LBF080014210 > > (II) SAVAGE(0): EDID (in hex): > > (II) SAVAGE(0): 00ffffffffffff0004721500e1788191 > > (II) SAVAGE(0): 12130103682213782e1e95a355489827 > > (II) SAVAGE(0): 155054bfee0081c00101010101010101 > > (II) SAVAGE(0): 010101010101662156a851001e30458f > > (II) SAVAGE(0): 3a0058c11000001c000000fd00324b1e > > (II) SAVAGE(0): 5010000a202020202020000000fc0041 > > (II) SAVAGE(0): 6365722058313633570a2020000000ff > > (II) SAVAGE(0): 004c42463038303031343231300a003d > > (II) SAVAGE(0): EDID vendor "ACR", prod id 21 > > (II) SAVAGE(0): Using EDID range info for horizontal sync > > (II) SAVAGE(0): Using EDID range info for vertical refresh > > Here are all the modes listed by the monitor as modes that it supports. Some > may be > VESA standard modes, others may not be. > > > (II) SAVAGE(0): Printing DDC gathered Modelines: > > (II) SAVAGE(0): Modeline "1366x768"x0.0 85.50 1366 1435 1578 1790 768 > > 771 781 798 -hsync +vsync (47.8 kHz) > > (II) SAVAGE(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 > > 605 628 +hsync +vsync (37.9 kHz) > > (II) SAVAGE(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 > > 603 625 +hsync +vsync (35.2 kHz) > > (II) SAVAGE(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 > > 484 500 -hsync -vsync (37.5 kHz) > > (II) SAVAGE(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 > > 492 520 -hsync -vsync (37.9 kHz) > > (II) SAVAGE(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 > > 486 525 -hsync -vsync (35.0 kHz) > > (II) SAVAGE(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 > > 492 525 -hsync -vsync (31.5 kHz) > > (II) SAVAGE(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 > > 414 449 -hsync +vsync (31.5 kHz) > > (II) SAVAGE(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 > > 769 772 800 +hsync +vsync (60.0 kHz) > > (II) SAVAGE(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 > > 771 777 806 -hsync -vsync (56.5 kHz) > > (II) SAVAGE(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 > > 771 777 806 -hsync -vsync (48.4 kHz) > > (II) SAVAGE(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 > > 628 667 -hsync -vsync (49.7 kHz) > > (II) SAVAGE(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 > > 604 625 +hsync +vsync (46.9 kHz) > > (II) SAVAGE(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 > > 643 666 +hsync +vsync (48.1 kHz) > > (II) SAVAGE(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 > > 721 724 746 -hsync +vsync (44.8 kHz) > > These appear to be the modes supported by the video BIOS at depth 16. > > > (--) SAVAGE(0): Found 13 modes at this depth: > > [10e] 320 x 200, 70Hz > > [133] 320 x 240, 72Hz > > [143] 400 x 300, 72Hz > > [153] 512 x 384, 70Hz > > [11d] 640 x 400, 70Hz > > [111] 640 x 480, 60Hz, 75Hz, 85Hz, 100Hz, 160Hz > > [114] 800 x 600, 60Hz, 75Hz, 85Hz > > [117] 1024 x 768, 60Hz, 70Hz, 75Hz, 85Hz, 100Hz, 130Hz > > [17a] 1280 x 768, 60Hz > > [14f] 1280 x 960, 60Hz, 85Hz > > [11a] 1280 x 1024, 60Hz, 75Hz, 85Hz, 100Hz > > [13c] 1400 x 1050, 60Hz, 75Hz > > [122] 1600 x 1200, 60Hz > > Note that 1366x768 is not one of them! That's trouble. > > > (II) SAVAGE(0): <default monitor>: Using hsync range of 30.00-80.00 kHz > > (II) SAVAGE(0): <default monitor>: Using vrefresh range of 50.00-75.00 Hz > > (II) SAVAGE(0): <default monitor>: Using maximum pixel clock of 160.00 MHz > > The above probed monitor characteristics agree with the specs in your owner's > manual. > > > (II) SAVAGE(0): Estimated virtual size for aspect ratio 1.7895 is 1366x768 > > It correctly chose 1366x768 as the virtual screen size. But there's trouble > ahead. > > > (II) SAVAGE(0): Clock range: 10.00 to 250.00 MHz > > The maximum dot clock rate supported by the video card (250MHz) is plenty > high enough > to run your monitor at the 1366x768 resolution, which only requires a dot > clock rate > of 85.5 MHz. > > OK, now it starts chucking out modes that are not supported by the video BIOS. > > > (--) SAVAGE(0): No suitable BIOS mode found for 640x350 85Hz. > > (II) SAVAGE(0): Not using default mode "640x350" (no mode of this name) > > (--) SAVAGE(0): No suitable BIOS mode found for 320x175 85Hz. > > (II) SAVAGE(0): Not using default mode "320x175" (no mode of this name) > > Here's one that it kept. This is 640x400. > > > (--) SAVAGE(0): Chose mode 11d at 70Hz. > > More keeping and throwing away. > > > ... > > (--) SAVAGE(0): No suitable BIOS mode found for 1366x768 59Hz. > > (II) SAVAGE(0): Not using driver mode "1366x768" (no mode of this name) > > Oops! There went your your treasured 1366x768 mode! > > > (WW) SAVAGE(0): Shrinking virtual size estimate from 1366x768 to 1024x768 > > After tossing out all the modes that aren't supported by the video BIOS, > or that won't work for some other reason, it decides to reduce the virtual > screen size. > > > (--) SAVAGE(0): Virtual size is 1024x768 (pitch 1024) > > And things are all downhill from there. > > The bottom line: the problem is not with your monitor. The problem is that > the savage driver wants to use the video BIOS to set the video mode. > > The single most important thing you must have in any xorg.conf file is > > Option "UseBIOS" "off" > > This goes in the "Device" section. If you need more help, let me know, > and I'll try to come up with a specific xorg.conf file for you.
The log file that you examined was for the Squeeze installation, which had no file named /etc/X11/xorg.conf. So, at first, I was wondering what else must I put in the file? Surely something that identified a Device section, at least. Then I remembered that there was a file, /etc/X11/xorg.conf, in the Lenny installation. When I looked at it, I realized that it was a skeletal generic xorg.conf file that just introduced generic names for required sections. I put your "Option" line in that, and Lenny went from 1280x768 to the ideal 1366x768 ! I copied that file into the Squeeze partition and it also worked there !!! And !!! we have your wonderful commentary on the /var/log/Xorg.0.log text, for study in how to solve X problems by reading the log. I wonder why there is no generic /etc/X11/xorg.conf installed by Squeeze. And why there is not your magic line pre-configured in /etc/X11/xorg.conf in Lenny. -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100312193607.gk4...@big.lan.gnu