- Package:
- xserver-xorg-video-savage
- Source:
- xserver-xorg-video-savage
- Description:
- X.Org X server -- Savage display driver
- Submitter:
- Yvan Masson
- Date:
- 2015-09-14 08:39:15 UTC
- Severity:
- normal
Dear maintainers, With a fresh installation of Jessie on a Packard Bell EasyNote E1260W with graphic card ProSavage8 KM266/KL266, the Savage driver allows a maximum resolution of 800x600, and everything displayed is really ugly (looks like there is no anti-aliasing). You can find attached the Xorg.0.log-savage If I use the Vesa driver by writing a file named (for example) 99-video-quirk.conf in /usr/share/X11/xorg.conf.d/, with the following contents, 1024x768 is then automatically used, with "anti-aliasing" : Section "Device" Identifier "ProSavage8 KM266/KL266" Driver "vesa" EndSection You can find attached the Xorg.0.log-vesa I suppose that normally the Savage driver should work better. This bug does not seem to be Debian specific : I also tried whith ArchLinux and it was similar. Also, the font on the tty is ugly : normally a few seconds after boot the tty becomes "prettier", but here it is the opposite : resolution stays the same and font becomes ugly. uname -a : Linux EasyNote 3.16-3-686-pae #1 SMP Debian 3.16.5-1 (2014-10-10) i686 GNU/Linux xorg version : 1:7.7+7 dpkg -l | grep xserver : ii x11-xserver-utils 7.7+3+b1 ii xserver-common 2:1.16.1-1 ii xserver-xorg 1:7.7+7 ii xserver-xorg-core 2:1.16.1-1 ii xserver-xorg-input-all 1:7.7+7 ii xserver-xorg-input-evdev 1:2.9.0-2 ii xserver-xorg-input-mouse 1:1.9.1-1 ii xserver-xorg-input-synaptics 1.8.1-1 ii xserver-xorg-input-vmmouse 1:13.0.0-1+b3 ii xserver-xorg-input-wacom 0.26.0+20140918-1 ii xserver-xorg-video-all 1:7.7+7 ii xserver-xorg-video-ati 1:7.5.0-1 ii xserver-xorg-video-cirrus 1:1.5.2-2+b1 ii xserver-xorg-video-fbdev 1:0.4.4-1+b2 ii xserver-xorg-video-geode 2.11.16-4 ii xserver-xorg-video-intel 2:2.21.15-2+b2 ii xserver-xorg-video-mach64 6.9.4-2 ii xserver-xorg-video-mga 1:1.6.3-2+b1 ii xserver-xorg-video-modesetting 0.9.0-1+b1 ii xserver-xorg-video-neomagic 1:1.2.8-1+b2 ii xserver-xorg-video-nouveau 1:1.0.11-1 ii xserver-xorg-video-openchrome 1:0.3.3-1+b2 ii xserver-xorg-video-qxl 0.1.1-2+b1 ii xserver-xorg-video-r128 6.9.2-1+b2 ii xserver-xorg-video-radeon 1:7.5.0-1 ii xserver-xorg-video-savage 1:2.3.7-2+b2 ii xserver-xorg-video-siliconmotion 1:1.7.7-2+b2 ii xserver-xorg-video-sisusb 1:0.9.6-2+b2 ii xserver-xorg-video-tdfx 1:1.4.5-1+b2 ii xserver-xorg-video-trident 1:1.3.6-2+b2 ii xserver-xorg-video-vesa 1:2.3.3-1+b3 ii xserver-xorg-video-vmware 1:13.0.2-3+b1 You can also find attached lspci -v and kern.log (using the savage driver). Regards, Yvan
Dear maintainers, I don't know if it can help, but I installed (and updated) Lubuntu 14.04 on this same computer : Although the bootsplash is also 800x600 and "ugly", lightm and lxsession are displayed with full resolution (1024x768), automatically. You can find the corresponding Xorg log attached. Thanks for your time, YvanM
Hi, Same issue here after upgrading a Vobis Uniwill N341C2 from Wheezy to Jessie. The Savage Twister KN133 worked with 1024x768 under Wheezy, with xserver-xorg-core 2:1.16.2.901-1 and xserver-xorg-video-savage 1:2.3.7-2+b2 it is limited to 800x600. The Xorg.log from Wheezy shows an additional "Driver mode" Modeline with 1024x768. I have tried various xserver versions, the last working was 1.14. There are some changes related to modeline handling in the last Xorg releases so I took a closer look to relevant lines in savage_driver.c. It seems that xf86CVTMode() should not be called with reduced blanking set to TRUE. Rebuilding xserver-xorg-video-savage with the attached xf86CVTMode patch gives me the 1024x768 resolution back (see Xorg.0.log_jessie_patch). Would be nice to get this fix released with Jessie. Regards, Alexander
Hi,
thought I tested this before, but this upstream fix solves the
modeline problem, no other patch needed:
commit 2e9217bb88b76cebfcd2b65b76c8733f80da77ea
Author: Jeremy White <jwhite@codeweavers.com>
Date: Thu Mar 21 10:59:13 2013 -0500
Include xf86Modes.h to use functions from hw/xfree86/modes/xf86Modes.c.
Signed-off-by: Jeremy White <jwhite@codeweavers.com>
Reviewed-by: Robert Morell <rmorell@nvidia.com>
diff --git a/src/savage_driver.h b/src/savage_driver.h
index ec4b1ea..de042af 100644
--- a/src/savage_driver.h
+++ b/src/savage_driver.h
@@ -54,6 +54,7 @@
#if GET_ABI_MAJOR(ABI_VIDEODRV_VERSION) < 6
#include "xf86Resources.h"
#endif
+#include "xf86Modes.h"
#include "xf86Pci.h"
#include "xf86_OSproc.h"
#include "xf86Cursor.h"
Regards,
Alexander
Hello It seems there is a patch available in Ubuntu. Is it possible to use this path also here? Kind regards
Dear Maintainer, Same problem with a LifeBook C1020. Solved this way : - remove xserver-xorg-video-savage (BTW is it DRI2 compatible?) - take care of some meta packages (task-*, *-video-all) - comment/remove 'blacklist savagefb' from /etc/modprobe.d/fbdev-blacklist.conf - use fbdev as the device driver for X (xorg.conf) savagefb is useful in that case. Could you please consider make some change for xserver-xorg-video-all: - remove xserver-xorg-video-savage from Depends - add it to Recommends No more breaking then if the *-video-savage package is removed. Thanks a lot,
Laptop Mitac 8375 ProSavage8 KM266/KL266 mobile AMD Athlon(tm) XP-M 2400+ (1,8 GHz max.) 1280 MB RAM Desktop LXDE There seem to be some problems in Xorg, seems that all current distributions are affected. Upgrade of the driver to 2.3.8 [*] (installed in Jessie: 2.3.7) restores resolution 1024x768, but scrolling and dragging of windows remain extremely slow. Fiddling with xorg.conf.d (E.g. "DisableTile" "on") may yield some "interesting" effects, but no further improvement. Regards Ludwig [*] Cooking recipe: Install Jessie packages - build-essential - xserver-xorg-dev Download http://www.x.org/archive/individual/driver/xf86-video-savage-2.3.8.tar.gz Do the usual things (tar -xzvf xf86*, cd xf86*, ./configure, make, make install) Remove /usr/lib/xorg/modules/drivers/savage_drv.so, and replace it by the new savage_drv.so (somewhere in /usr/local) or set an appropriate link. Restart the display manager or reboot.