acer aspire 1300 (S3 ProSavage) dsiplays distorted image after upgrading from Ubutn 12.04 to Ubuntu 12.10

Bug #1098661 reported by baltasarq
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-savage (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

I have a laptop Acer Aspire 1300, running Lubuntu since 10.x. Some years, already. Everything worked fine. The problem came after upgrading from Lubuntu 12.04 (in which display still worked correctly) to 12.10. After that, the laptop boots up correctly, but when it boots the display manager (lightdm) then the screen distorts completely. Only the upper thrid is more or less correctly displayed.

The graphics card is an S3 VT8363A ProSavage KN 133 (AGP4X VGA controller), as reported by lspci.

Modifying xorg.conf does not help.

Changing the display manager (from lightdm to lxdm) does not help, as well.

I tried with "sudo modprobe savage" (since savage does not appear with "lsmod"), stopping and starting the display manager. But that did not work. Also, it appears that the module is not kept after rebooting.

Any ideas?

Revision history for this message
Tormod Volden (tormodvolden) wrote :

A Savage user! I knew there was one :) Can you please run "apport-collect #1098661" so I get all logs and details?

Changed in xserver-xorg-video-savage (Ubuntu):
status: New → Incomplete
Revision history for this message
Tormod Volden (tormodvolden) wrote :

I meant "apport-collect 1098661" without the hash sign.

Revision history for this message
baltasarq (baltasarq) wrote : Re: [Bug 1098661] Re: acer aspire 1300 (S3 ProSavage) dsiplays distorted image after upgrading from Ubutn 12.04 to Ubuntu 12.10

Fine, but, will this collect meaningful information, provided that nothing
is crashing?
Thanks,

On Sat, Jan 12, 2013 at 12:14 AM, Tormod Volden
<email address hidden>wrote:

> I meant "apport-collect 1098661" without the hash sign.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1098661
>
> Title:
> acer aspire 1300 (S3 ProSavage) dsiplays distorted image after
> upgrading from Ubutn 12.04 to Ubuntu 12.10
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-savage/+bug/1098661/+subscriptions
>

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Yes, that is supposed to attach a number of logs and information. The same that would have been attached if you had filed the bug using "ubuntu-bug xserver-xorg-video-savage".

Revision history for this message
baltasarq (baltasarq) wrote :

Terrific! Sorry, did not know. I will do that first thing tomorrow. Thank
you very much.

On Sat, Jan 12, 2013 at 11:28 PM, Tormod Volden
<email address hidden>wrote:

> Yes, that is supposed to attach a number of logs and information. The
> same that would have been attached if you had filed the bug using
> "ubuntu-bug xserver-xorg-video-savage".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1098661
>
> Title:
> acer aspire 1300 (S3 ProSavage) dsiplays distorted image after
> upgrading from Ubutn 12.04 to Ubuntu 12.10
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-savage/+bug/1098661/+subscriptions
>

Revision history for this message
baltasarq (baltasarq) wrote :

I've tried "apport-collect 1098661", but the problem is that it reports that a browser window has been opened in the graphic console, and that I have to give permission inside that browser in order to continue.

The problem is, I cannot do anything in the graphic console, since the visualization is distorted (is mor like a mosaic than anything else), and the mouse pointer does not point to where it appears to be pointing.

In order to give you logs or other information, I need something that I can exclusively do in the text console (I press Ctrl+Alt+F1 while booting, and that lets me work with the laptop, but not with graphic applications).

If there is a "failsafe" graphics mode, than I could try that.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I see. Just attach /var/log/Xorg.0.log and dmesg output for a start. You can use the vesa driver by specifying it in xorg.conf but then apport-collect would attach the vesa log instead of the savage log anyway.

Revision history for this message
baltasarq (baltasarq) wrote :

Following your instructions, I am adding Xorg.0.log and dmesg.log.

Revision history for this message
baltasarq (baltasarq) wrote :

Here's xorg...log

Revision history for this message
baltasarq (baltasarq) wrote :

Here's dmesg.log

Revision history for this message
baltasarq (baltasarq) wrote :

I've set the VESA driver, and now everything works okay (though it still complains about xorg crashing at boot). Anyway, now I have a resolution of 1024x768 and everything seems fine.

Maybe the solution to all of this is just drop savage and make people (or just me, provided that I am the only one user of Savage) use the VESA driver, I don't know.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

No, you're not the only user :) Your log shows that the savagefb driver is being loaded. Unless you want to use this framebuffer driver (not X) this should not happen. Try blacklisting it.

Revision history for this message
baltasarq (baltasarq) wrote :

Yep, I remember I removed savagefb from the blacklist in /etc/modprobe.d in order to check if that would solve the problem. It obviously didn't, but I forgot to restore it in the blacklist.

I will restore the blacklist, but that's not the origin of the problem.

Revision history for this message
Michael Müller (michael-mueller-3) wrote :

I have the same problem: 12.04 is fine, but 12.10 or 12.04.02 is broken. The output of "lspci -d 5333: -nn":
01:00.0 VGA compatible controller [0300]: S3 Inc. VT8636A [ProSavage KN133] AGP4X VGA Controller (TwisterK) [5333:8d02] (rev 01)

Revision history for this message
baltasarq (baltasarq) wrote :

You'll be able to restore your functionality by creating a xorg.conf file
in the /etc/X11/ directory:

Section "Device"
Identifier "driver01"
Driver "vesa"
EndSection

On Sat, Feb 23, 2013 at 3:48 PM, Michael Müller
<email address hidden>wrote:

> *** This bug is a duplicate of bug 1083032 ***
> https://bugs.launchpad.net/bugs/1083032
>
> I have the same problem: 12.04 is fine, but 12.10 or 12.04.02 is broken.
> The output of "lspci -d 5333: -nn":
> 01:00.0 VGA compatible controller [0300]: S3 Inc. VT8636A [ProSavage
> KN133] AGP4X VGA Controller (TwisterK) [5333:8d02] (rev 01)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1098661
>
> Title:
> acer aspire 1300 (S3 ProSavage) dsiplays distorted image after
> upgrading from Ubutn 12.04 to Ubuntu 12.10
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-savage/+bug/1098661/+subscriptions
>

--
-- Baltasar

Revision history for this message
Tormod Volden (tormodvolden) wrote :

If you choose the vesa driver you may have reduced functionality. There was another workaround in the link in bug 1083032:

"Section "Device"
  Identifier "mydearsavage"
  Option "DisableTile"
EndSection

If anyone can help out with the testing I described there it would be great.

Michael, I have the same card as you! On a Presario 700.

Revision history for this message
pradyot (pradyotsn) wrote :

hey everyone,

I am a newbie at this. I have

 Processor: Intel(R) Pentium(R) 4 CPU 1.60GHz
Memory: 512MB RAM
Hard Disk: 160 GB

Display Devices
---------------
Card name: S3 Graphics Inc. Savage4
Manufacturer: S3 Graphics Inc.
Chip type: S3 Savage4

I am getting this weird coloured bars.

http://ubuntuforums.org/showthread.php?t=2128715

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.