Posts: 1
orblin
Joined: 24 Oct 2017
#1
Hi, I recently installed antiX-16 Berta Cáceres on a very old laptop.
The nouveau drivers caused 100% cpu usage and strange artifacts to be drawn 
to the screen, so I installed with nomodeset boot option to load the vesa driver.
With this, when xserver is started I get horizontal cascading lines until Slim
display manager loads. Once logged on the system performs exceptionally
well and is completely stable. The problem is that when I shutdown I
get the horizontal cascading lines back, Xserver seems to crash and
I’m unable to do a clean shutdown.
 
Searching the web it seems that this is a Debian specific fault with this 
graphics card that goes back years and has never been addressed.
I’ve tried a multitude of things like different boot options, changing Slim
For Lightdm etc, and I’m now out of ideas.

 I really think I’m never going to get this working on this laptop which 
is such a shame as this is such a great lightweight distro. 
So out of desperation I’m going to throw it open to the community here.
Are you able to help?

Code: Select all

System:    Host: time-laptop Kernel: 4.4.10-antix.1-486-smp i686 (32 bit gcc: 4.9.3)
           Desktop: IceWM 1.3.8
           Distro: antiX-16.1_386-full Berta Cáceres 16 January 2017
Machine:   Device: laptop System: Times product: N/A v: 5a
           Mobo: Times model: N/A v: 5a BIOS: Insyde v: V1.07 date: 10/06/2003
CPU:       Single core mobile AMD Athlon XP-M 2600+ (-UP-) cache: 512 KB
           flags: (pae sse) bmips: 2786 speed/max: 1393/1990 MHz
Graphics:  Card: S3 Graphics VT8375 [ProSavage8 KM266/KL266] bus-ID: 01:00.0
           Display Server: X.Org 1.16.4 driver: vesa
           Resolution: 1024x768@61.00hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
           GLX Version: 3.0 Direct Rendering: Yes
Audio:     Card VIA VT8233/A/8235/8237 AC97 Audio Controller
           driver: snd_via82xx port: e100 bus-ID: 00:11.5
           Sound: ALSA v: k4.4.10-antix.1-486-smp
Network:   Card: VIA VT6102 [Rhine-II]
           driver: via-rhine port: e300 bus-ID: 00:12.0
           IF: eth0 state: down mac: <filter>
Drives:    HDD Total Size: 160.0GB (3.3% used)
           ID-1: /dev/sda model: SAMSUNG_HM160HC size: 160.0GB
Partition: ID-1: / size: 7.8G used: 3.5G (47%) fs: ext4 dev: /dev/sda3
           ID-2: /home size: 6.5G used: 738M (12%) fs: ext4 dev: /dev/sda4
           ID-3: swap-1 size: 0.90GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 135 Uptime: 3 min Memory: 84.0/971.5MB
           Init: SysVinit runlevel: 5 Gcc sys: 4.9.2
           Client: Shell (bash 4.3.301) inxi: 2.3.21 

Posts: 1,445
skidoo
Joined: 09 Feb 2012
#2
results of websearch"linux S3 Graphics card VT8375 ProSavage8"

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://wiki.archlinux.org/index.php/Savage"
linktext was:"https://wiki.archlinux.org/index.php/Savage"
====================================


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://forums.freebsd.org/threads/37245/"
linktext was:"https://forums.freebsd.org/threads/37245/"
====================================


suggest creating (or edit if it already exists) /etc/X11/xorg.conf.d/named 99-savage.conf
adding a line
Option"NoAccel" "True"
the ArchWiki page (marked as"last edited on 28 August 2017") also mentions
Unfortunately, there is no framebuffer driver for the Savage chipset. Your best bet is to set the framebuffer video mode by the (bootline) vga kernel parameter.
For example, put vga=0x314 at the end of your bootline parameters for an 800x600 framebuffer, or vga=0x317 for a 1024x768 framebuffer.