Re: [XFree86] S3 ViRGE/MX locks up
On Thu, 15 May 2003, Kevin Brosius wrote:
> Mark Vojkovich wrote:
> > On Thu, 15 May 2003, Kevin Brosius wrote:
> > > Basz wrote:
> > > > I've been trying to get a generic no-name laptop up using Debian. The video
> > > > chip is a S3 Virge / MX.
> > > > I started on Woody, then Sarge and now I'm on Sid. The problem is the
> > > > same. (I've also tried RH7.2-RH8, I haven't yet tried RH9).
> > > > After "startx", the screen clears, the hard disk light is on for a second,
> > > > and then hard lock (no responce from the keyboard, network and still
> > > > the same blank screen).
> > > > The lcd is a generic 24bit 1024x768 panel. The processor is an amd k6.
> > > > The Virge driver claims it can do 24 bit color, I dropped the default
> > > > color depth to 8 with no effect.
> > > > Any help, thanks,
> > > > -Frank Baszler
> > > > XFree86 Version 4.2.1.1 (Debian 4.2.1-5 20030122074040 buildd@cyberhq.internal.cyberhqz.com) / X Window System
> > [...]
> > > > (--) PCI:*(0:2:0) S3 ViRGE/MX+MV rev 3, Mem @ 0xc0000000/26, BIOS @ 0x000c0000/16
> > [...]
> > > > (II) VGA: Generic VGA driver (version 4.0) for chipsets: generic
> > > How about a log from a depth 16 run? That's the most likely candidate
> > > to work. Also, XFree86 4.3.0 is newest, and may run MX better.
> > The VGA driver only supports depths 1, 4 and 8. 8 only at 320x240,
> > 4 only at 640x480. It's just VGA.
> Yes, excellent point. Have you tried 'Driver "s3virge"' ?
I've had a similar problem for a while (although I haven't kept up with
the latest XFree86 releases...). Find the file libvbe.a in
/usr/X11R6/lib/modules/ (or wherever Debian puts it) and rename it. May
have to do likewise with libddc.a. XFree86 should then start and run fine.
Watch out if you let apt do any package upgrades, as upgrades to XFree86
will replace these files and the problem will return.
My laptop is a Clevo model 660 (Intel Pentium/MMX), rebadged Pico/dip
Systems (now defunct), and has the same attribute (hard lockups when using
the s3virge driver).
Possibly related is problems trying BeOS, which can be overcome by picking
safe mode, and enabling the option to not call the BIOS. (although
somewhat off-topic)...
--
Regards, iain.thomas@dial.pipex.com
My website: http://www.iain.thomas.dial.pipex.com/
Reply to: