Laptop resolution with the savage driver and xorg 7.1.1

[Alex Deucher]

On 9/21/06, Bernat Tallaferro <bernat.tallaferro at gmail.com> wrote:
> Hi,
>
> I was wondering if someone could shed some light on a problem I've got
> with the 'savage' driver.
>
> According to the output of lspci, my laptop has got the following
> graphics card:
>
> 01:00.0 VGA compatible controller: S3 Inc. 86C380 [ProSavageDDR K4M266]
> (rev 02)
> (which according to Xorg.0.log is a "Twister PN133", Chip: id 8d01)
>
> on the AGP bus:
>
> 00:00.0 Host bridge: VIA Technologies, Inc. VT8605 [ProSavage PM133]
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8605 [PM133 AGP]
>
> reading 'man savage', I see that these chips, and in particular 8d01
> seem to be supported, so I tried to use the savage driver, since the
> vesa driver I had been using until xorg 7.0.0 has become unbearably slow
> after updating to 7.1.1 (which I'm using now).
>
> The problem I've got is that although the driver and X load fine, I can
> only get a maximal resolution of 800x600, which makes the laptop's
> screen look awful, as it's got a native resolution of 1024x768 -which I
> could use with the 'vesa' driver, at least.
>
> Now my xorg.conf is very simple:
>
> [...]
> Section "Device"
>         Identifier      "Generic Video Card"
>         Driver          "savage"
>         BusID           "PCI:1:0:0"
> EndSection
> [...]
>
> where the only mode which interests me is 1024x768, as in:
>
>         SubSection "Display"
>                 Depth           24
>                 Modes           "1024x768" "800x600" "640x480"
>         EndSubSection
>
> [...]
>
> However, after having a had look at Xorg.0.log, I see that all the
> 1024x768 modes are dropped for some reason or the other. Here are some
> bits of it which caught my attention:
>
> [...]
> (--) SAVAGE(0): Detected current MCLK value of 14.318 MHz
> (--) SAVAGE(0): 1024x768 TFT LCD panel detected and active
> (--) SAVAGE(0): - Limiting video mode to 1024x768
> (II) SAVAGE(0): Generic Monitor: Using default hsync range of
> 31.50-37.90 kHz
> (II) SAVAGE(0): Generic Monitor: Using default vrefresh range of
> 50.00-70.00 Hz
> (II) SAVAGE(0): Clock range:  10.00 to 220.00 MHz
> [...]
> (II) SAVAGE(0): Not using default mode "1024x768" (vrefresh out of
> range)
> (II) SAVAGE(0): Not using default mode "512x384" (vrefresh out of range)
> (II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
> (II) SAVAGE(0): Not using default mode "512x384" (hsync out of range)
> (II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
> (II) SAVAGE(0): Not using default mode "512x384" (hsync out of range)
> (II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
> (II) SAVAGE(0): Not using default mode "512x384" (hsync out of range)
> (II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
> [...]
> (II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
> (II) SAVAGE(0): Not using default mode "2048x1536" (bad mode
> clock/interlace/doublescan)
> (II) SAVAGE(0): Not using default mode "1024x768" (hsync out of range)
> (II) SAVAGE(0): Not using mode "1024x768" (no mode of this name)
> (--) SAVAGE(0): Virtual size is 800x600 (pitch 800)
> (**) SAVAGE(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
> (II) SAVAGE(0): Modeline "800x600"   40.00  800 840 968 1056  600 601
> 605 628 +hsync +vsync
> [...]
>
> So I basically end up with a maximum 800x600 mode.

You need to specify the hsync and vrefresh for the savage driver even
for the panel.  Add those to your monitor section and you should be up
and running.

Alex