Linux - GamesThis forum is for all discussion relating to gaming in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hey everybody. I'm pretty new to linux, but I know some things, so I'm not a complete newbie. Anyway, so far I've only tried 2 games on Red Hat 8. The first one was GTA: Vice City, which I ran with Wine. It was very very very choppy, like less than 1 frame per second choppy. The second one I tried was Enemy Territory, and that was very choppy also.
Anybody know what's causing this? These games work fine on my Windows partition.
You can check the DRI project (dri.sourceforge.net) but last I knew Trident didn't release 3D drivers and the DRI project didn't support them either. The only referance I can find to Trident 3D support is at:
Yea, sounds like you've got a library conflict between something installed as part of the Mesa stuff and from something else. Did you install binaries packaged for Ffedora Core 1 from somewhere or the RH binaries from ATI.. might be that you need some repackaged ones if that's the case. You may also need to change which XF86 server your loading in /etc/X11/XF86Config(-4) if the ATI driver doesn't go by the same name as the in-house XF86 driver.
That's actually the last card supported by the DRI project from ATI.
Well, this is what my xfree86-a file looks like, I notice that it recognises my video card, but I'm still getting a crappy 240 fps with glxgears. I did use the binaries from the ATI website, so should I snoop around for some ATI rpms elsewhere? Or compile a module for ATI?
Quote:
# XFree86 4 configuration created by redhat-config-xfree86
# RgbPath is the location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "unix/:7100"
EndSection
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
Identifier "DevInputMice"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
Okay, I went and grabbed the drivers, converted them to tarballs, and took a looksie for ya'. It *looks* like the driver name should be "fglrx" from those.
So, what you'll want to do is replace that bit that says "radeon" for the driver name with "fglrx" as the driver it installs is fglrx_drv.o.
Thanks! I'll try that out when I get home from school *fingers crossed*
EDIT:
I tried changing the entry and rebooting the whole system, I ran glxgears and even tried tuxracer (which was what led me to wonder why my fps was so slow) to see if things had changed.
I do get this error when I run glxgears tho' I wonder if this has anything to do with it.
Quote:
Xlib: extension "XFree86-DRI" missing on display ":0.0".
It sounds like the kernel bits needed for direct rendering aren't loading. I'm not totally sure there.. if no one else has any ideas (and my home internet service is back up tonight) I'll go ahead and install it and take a look for you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.