Bug 63279

Thanks for your report. This broke in xserver 1.13 and was partly fixed in 1.14. Try Option "AccelMethod" "EXA". A workaround is to turn off acceleration with Option "DisableTile".

See also https://bugs.launchpad.net/bugs/1083032

Hi Tormod,

Thanks for your prompt response and assistance.

I have tried the suggested options, but I'm still having the same issue, no change at all.

- http://pastebin.com/yAgshj2V

Is there any other work around? When is it expected to have a fix for it?

Regards.

Simply using EXA (and a 1.14 fix backported to 1.13) worked for me. Maybe more is broken in 1.14. What exactly happens in your case? Please be more specific than "does not work".

There is no schedule for such bug fixes, most developers do not care about hardware which is more than a few years old. I will look closer into it sometime in the next weeks, although no guarantees given. There seems to be more continued use of the savage driver than I thought :)

Created attachment 77694 [details]
My scrambled screen

Hi Tormod,

Thanks once again for your prompt response.

When say "it doesn't work", I mean the screen is scrambled and nothing is distinguishable. As the telling goes, a picture is worth more than a thousand words, so please, have a look at the attached picture of the my screen.

Kindly, let me know if there is any patch that can be used to fix this issue.

Best regards,
Carlos.

I have committed a couple of fixes to the savage driver repository. One problem was that the driver, even when built for an xserver without XAA support, would internally default to XAA instead of EXA nonetheless. Secondly there was an EXA function that needed an update for recent xservers.

This works well for me. The only issue I see now is that console switching does not work, the text consoles are unusable. But I am not sure this is savage-specific since for instance the vesa driver locks up the machine completely if I try to switch consoles.

Hi Tormod,

Awesome mate!

What version will this fix be included in?

Regarding the console issue, I think this problem is being there for a long time. It would be nice to find a fix it too, but it's not a critical issue at all.

Thanks a lot for your effort, I appreciate it a lot.

Best regards,
Carlos.

Hi Tormod,

I have tried a new build of the savage package supposedly including your changes (https://bugs.archlinux.org/task/34527), but it doesn't solve my problem. I'm still getting my screen scrambled, just multi-color lines everywhere. I have tried a configuration forcing to use EXA module as well as a brand new xorg.conf file generated through X -configure command.

Please, let me know if there anything I can you to help you find the problem.

Best regards,
Carlos.

Musikolo, please attach (no pastebin) your new Xorg.0.log.

Created attachment 80797 [details]
xorg.conf.new

File generated using X -configure command

Created attachment 80798 [details]
xorg.conf_S3

Version I used to have working before the driver broke

Created attachment 80799 [details]
xorg.conf_VESA

Only configuration currently working based on vesa driver.

Created attachment 80818 [details]
Xorg.0.log_NEW

Log for xorg.conf.new configuration without patch

Created attachment 80819 [details]
Xorg.0.log_NEW_WITH_PATCH

Log for xorg.conf.new configuration with patch

Created attachment 80820 [details]
Xorg.0.log_S3

Log for xorg.conf_S3 configuration without patch

Created attachment 80821 [details]
Xorg.0.log_S3_WITH_PATCH

Log for xorg.conf_S3 configuration with patch

Created attachment 80822 [details]
Xorg.0.log_VESA

Log for xorg.conf_VESA configuration without patch

Created attachment 80823 [details]
Xorg.0.log_VESA_WITH_PATCH

Log for xorg.conf_VESA configuration with patch

Have you tried without any xorg.conf? You have two device sections in your configuration, I don't understand why. The last working configuration from comment 11 simply switches to EXA, which is the default now.

Created attachment 80873 [details]
Xorg.0.log_NO_CONF

Log having no xorg.conf configuration without patch

Created attachment 80874 [details]
Xorg.0.log_NO_CONF_WITH_PATCH

Log having no xorg.conf configuration with patch

Created attachment 80876 [details]
xorg.conf_S3_1_DEVICE

Same configuration as xorg.conf_S3 but having just 1 device

Created attachment 80877 [details]
Xorg.0.log_S3_1_DEVICE

Log for xorg.conf.S3_1_DEVICE configuration without patch

Created attachment 80878 [details]
Xorg.0.log_S3_1_DEVICE_WITH_PATCH

Log for xorg.conf.S3_1_DEVICE configuration with patch

Created attachment 80884 [details]
lspci output (lspci -vv -d 5333 -nn)

Created attachment 80885 [details]
lsmod output

Created attachment 80886 [details]
lsmod output

Can you please try savage driver version 2.3.7? It looks like it is already in Arch Linux.

Hi Tormod,

Sure, I will do it, but I'm not able to right now. Unfortunately, I'm traveling for business and we'll not go back home until beginning of November where my personal laptop is. I know it's quite a lot of time, but take for granted that I'll let you know as soon as I test it out.

Thanks a lot for your amazing effort and work.

Best regards,
Carlos.

Hi Tormod,

I'm happy to tell you that the problem is now fixed. I'm writing from the affected computer. The latest version (xf86-video-savage-2.3.7-1 + savage-dri-7.11.2-5) has fully sort it out now. So, I owe you a million thanks:

1000000 x Thanks!

Let me tell you that I appreciate the effort and time you've spent in the resolution of this issue.

Best regards,
Carlos