s3 prosavage km133

Asked by tcodau

I've tried ubuntu, kubuntu and xubuntu (both 8.10 and 9.04) on an hp pavilion 431.it PC. I have a s3 prosavage km133 graphic card but always when I boot the operating system says graphic card not configured and boot in low resolution mode(800x600). With previous versions of ubuntu(8.04) the graphic card was automatically configured with a resolution of 1024x768. What is the problem? How can I resolve it? Can I submit the problem as a bug so it can be resolved in next version?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu xorg Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Buz Cory (buzco) said :
#1

Hello,

We can maybe resolve this:
First do in a terminal
    %lspci | egrep -i vga
and send the result.

A look at your current /etc/X11/xorg.conf might also help.

C U soon,
== Buz :)

Revision history for this message
tcodau (tcodau) said :
#2

Hello and thanks, from terminal results this: '' lspci | egrep -i vga
01:00.0 VGA compatible controller: S3 Inc. ProSavage KM133 (rev 03)''.
_From /etc/X11/xorg.conf results this:# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# Note that some configuration settings that could be done previously
# in this file, now are automatically configured by the server and settings
# here are ignored.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Device"
 Identifier "Configured Video Device"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
EndSection

Revision history for this message
Buz Cory (buzco) said :
#3

Hi,

Sorry for the delay getting back to you. I think we have the answer here.

These are relevant:
    01:00.0 VGA compatible controller: S3 Inc. ProSavage KM133 (rev 03)
tell us what driver you need and
    Section "Device"
       Identifier "Configured Video Device"
    EndSection
tells us that X is not using it. It is using default SVGA settings.

Taken from "synaptic":
    X.Org X server -- Savage display driver
    This package provides the driver for the S3/VIA Savage/ProSavage/Twister family of chipsets.

This is the driver you need to install for X.

Install this and whatever kernel driver goes with it, reboot (required after a kernel driver change) and you should be good.

If it appears to be installed, you could try purging it (it's not doing anything, anyway) and re-installing it.
But, before doing the purge, reinstall bit; you might check if there isn't a config file in /etc/X11 that will do the job (grep is your friend :). Careful with this, though. If you ask X to use a video driver that doesn't have a matching kernel driver in place it complains and won't start.

The simplest way to recover from that unless you are expert in all the ins & outs of "apt" is to go into /etc/X11 and copy the fail-safe config file into place then reboot (or restart X) and do the install I mentioned above.

You could even do the install before the reboot using "aptitude".

The command line is your friend :)
== Buz :)

Revision history for this message
Buz Cory (buzco) said :
#4

Oops, I just re-read the original message and saw that you did mention that ProSavage, so I gave you some extra work which confirmed what you already said.

Sorry 'bout that,
== Buz

Revision history for this message
tcodau (tcodau) said :
#5
Revision history for this message
Launchpad Janitor (janitor) said :
#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.