XFree86-Mach64-3.3.2

XFree86-Mach64-3.3.2

Post by Kjell Andersso » Fri, 24 Jul 1998 04:00:00



Hi!

Im rahter new to linux and i have gotten some trouble with the Xserver.
I have an IBM Aptiva Pentium II 300 Mhz with what seems to be an ATI 3D Rage
II grahpicscard.
Im using Redhat Linux 5.0. After installing it X did not work at all no
matter what config i used.
Than i got hold of an updated version of the X-server number 3.3.2. Now it's
possible to start X with the startx command but only if im logged in as Root
if i try as an ordinarie user the server says it has to be run with root
permision. This does not occur on another machine there i am using a Trident
grahpicscard.

Can anybody give me some advice please !

Regards Kjell

 
 
 

XFree86-Mach64-3.3.2

Post by jik- » Fri, 24 Jul 1998 04:00:00



> Hi!

> Im rahter new to linux and i have gotten some trouble with the Xserver.
> I have an IBM Aptiva Pentium II 300 Mhz with what seems to be an ATI 3D Rage
> II grahpicscard.
> Im using Redhat Linux 5.0. After installing it X did not work at all no
> matter what config i used.
> Than i got hold of an updated version of the X-server number 3.3.2. Now it's
> possible to start X with the startx command but only if im logged in as Root
> if i try as an ordinarie user the server says it has to be run with root
> permision. This does not occur on another machine there i am using a Trident
> grahpicscard.

> Can anybody give me some advice please !

> Regards Kjell

  As root...
chmod u+s XF_Server
chmod a+x XF_Server

 
 
 

1. Mach64 WinBoost with XFree86 3.2 problems

Perhaps someone can help me here.  I upgraded to XFree86 3.2 and am
attempting to use the Mach64 accelerated server.  Apparently the video
card is not being initialized properly; when I start up a variety of
window managers (e.g olwm, fvwm-2, twm, etc.) upon startup the colors
are all screwed up, and many of them are black, making it somewhat difficult
to use!  Quite by accident I discovered that setting and applying the window
manager properties in olwm fixed the colors; switching to fvwm and then back
to olwm resulted in the fixed colors being retained, but quitting X and
restarting olwm resulted in the screwed up colors again.

System is Linux 2.0.0, 16 MB, PCI bus Mach64 WinBoost graphics accelerator
card with 2 MB dram.  I believe this uses the ATI 88800GX-D chipset and
the ATI 68875 ramdac.

Other relevant info:  the 3.1.1 accelerated server works fine with this
card and that is what I am using to get work done (with appropriate mods
to XF86Config), while the 3.1.2 server had a problem with screenblank that
I never did resolve.  Also I tried adding the "no_block_write" option for
the 3.2 server because I saw a reference in the release notes to
initialization problems being solved by this (for a different chipset),
but this had no effect on the screwed up colors.

Please forward replies to me via email to ensure that I don't miss them.
Many thanks,

        Dan Eldred

2. info to an Iris

3. XFree86 3.2/Mach64/16 bit color problem

4. Only 4 shades on my Handbook

5. XFree86 3.2 stuck on ATI Mach64 chipset? Help!

6. accessfs v0.5 ported to LSM - 1/2

7. Mach64 WinBoost with XFree86 3.2 problems

8. Side by side...

9. XFree86 3.2 Mach64 Server in 1152X900 mode

10. XFree86 3.2 Mach64 setup troubles

11. ATI Mach64 vs XFree86 3.2

12. Xfree86 3.2A SVGA Server on Xfree86 3.2

13. RH 5.0 Error upgrading XFree86-3.3.1-14 to XFree86-3.3.2