On Mon, May 03, 2004 at 04:44:59PM -0400, Victor wrote:
>Hi, I have 600x with NeoMagic 256ZX and 4MB video ram. WinXP works fine=20
So do I, although I've never tried XP on it :-)
>Everything works great at 16bit. Has anyone gotten 256ZX working right=20
>with 24bit color in XFree86 ? (I am on 4.3.0)
It works fine on mine (2645-4EU). I'm running Debian Sarge (also
works fine with Sid on the same machine), XFree86 4.3.0. I've never had
any screen artifacts, although the window borders flicker when moving
windows around. However, it's perfectly evenly spaced and is done in
white bars, such that I believe that to be intentional on the part of KDE.
I hadn't even noticed it until I looked very closely after reading your
post.
>Should dbe, glx, and dri be enabled for neomagic? Any other neomagic=20
>specific options?
IANAXXB (I Am Not an X eXpert But):
IIRC DRI is only supported by a handful of late-model video chipsets
such as Radeon and Geforce. Enabling it on a machine that doesn't support
it should not cause a problem, and I accepted it as the default, although
I suppose it would use slightly less memory and very slightly reduce the
startup time to disable it.
Here are the relevant sections of the XF86Config-4 on my Debian Sid and
Sarge systems. You'll also notice the default color depth is 16. This is
because I read a tip that said you won't be able to tell the difference
=66rom 24-bit (and it's true, I can't), and you'll get slightly better
performance. I don't really notice the performance difference, either,
though. I left it at 16-bit, but 24-bit does work perfectly well.
One line to pay attention to in the video card definition is that
UseFBDev is set to true. According to the setup routine in Debian,
on some systems it works better to use it, on others not to. So
if yours is set to false and you have a frame-buffer kernel (most
distros ship kernels with frame buffer enabled, I believe; maybe they
all do these days), try setting that to true. Converely, if it's
already true, set it to false and see if it helps, although the fact
that it's worked for me set to true on two different 600X machines=20
tends to indicate true is the way to go if your kernel supports it.
If it doesn't, compile one that does :-)
HTH,
Jonathan
--=20
gpg --keyserver pgp.mit.edu --recv-keys ACC46EF9
Key fingerprint =3D E52E 8153 8F37 74AF C04D 0714 364F 540E ACC4 6EF9
"Talkin' 'bout my baby, she's some kind of wonderful"
Section "Module"
Load "GLcore"
Load "bitmap"
Load "dbe"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "record"
Load "speedo"
Load "type1"
Load "vbe"
EndSection
Section "Device"
Identifier "Neomagic "
Driver "neomagic"
VideoRam 4096
Option "UseFBDev" "true"
EndSection
Section "Monitor"
Identifier "1024 x 768 LCD"
HorizSync 28-49
VertRefresh 43-72
Option "DPMS"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "Neomagic "
Monitor "1024 x 768 LCD"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768"
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Generic Mouse"
EndSection
Section "DRI"
Mode 0666
EndSection
<End of Sid>
<Start of Sarge>
Section "Module"
Load "GLcore"
Load "bitmap"
Load "dbe"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "record"
Load "speedo"
Load "type1"
Load "vbe"
EndSection
Section "Device"
Identifier "Neomagic "
Driver "neomagic"
VideoRam 4096
Option "UseFBDev" "true"
EndSection
Section "Monitor"
Identifier "1024 x 768 LCD"
HorizSync 28-49
VertRefresh 43-72
Option "DPMS"
EndSection
_______________________________________________
Thinkpad mailing list
Thinkpad@stderr.org
http://stderr.org/cgi-bin/mailman/listinfo/thinkpad
Received on Wed May 5 04:57:09 2004
This archive was generated by hypermail 2.1.8 : Fri May 26 2006 - 16:02:50 EDT