SlackwareThis Forum is for the discussion of Slackware 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.
Well, everything is running fine but for me apart from 3D games freeze a lot Just playing a game and - it'll randomly freeze - have to restart.
Running Slack10 with ATI 3.9.0 drivers on a P4 1.3Ghz with a Sapphire Radeon 9000, in Fluxbox. Looking around the forums doesn't seem a lot I can do realy - any suggestions ?
Steve
Which kernel are you using? Do you still have the log files from when you compiled the driver?
Ok, there are the exact steps that I took to get where I am now ;( (For Slackware 10 running the 2.4.26)
1) Downloaded fglrx-4.3.0-3.9.0.i386.rpm
2) Then I converted the file to a .tgz using rpm2tgz
3) installpkg fglrx-4.3.0-3.9.0.i386.tgz
4) cd /lib/modules/fglrx/build_mod/ && sh ./make.sh
That seems to work fine without any error messages.
5) Then I cd .. and ran the make_install.sh script which also seems to work fine.
6) I then shutdown X and as root ran fglrxconfig. (Now I think I answered every question correctly)
7) Backed up my old xorg.conf and renamed the newly created XFree86-4 whatever to xorg.conf
8) Edited these sections of xorg.conf
Code:
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "fglrx" <-- Changed this line to fglrx
Code:
# === ATI device section ===
Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx" <-- Changed this line to fglrx
Thats all I did, this is the output of lsmod and fglrxinfo after restarting X again;
I'm trying to get this working because when I use the radeon driver I cannot get MPlayer to play in fullscreen mode, and when I do get it using -zoom, its really slow and choppy.
I didn't have these MPlayer problems in Fedora Core 2, and I never installed the ATi drivers either. What was Fedora doing differently to Slackware to get this to work?
Thanks
Kristijan
EDIT: Is my post knocking out the formatting for anyone else, or is it just me?
First, only do one change at a time: Here's what I recommend first doing:
From your first exerpt, change
Code:
Driver "fglrx"
to
Code:
Driver "vga"
If that doesn't work, follow what I wrote originally (-->):
Hmm, what video card do you have? The output from fglrxinfo shows that fglrxconfig didn't probe your video card properly. Are you SURE you got X to die completely (Meaning no KDM running, no GDM running, etc.) I would recommend being in runlevel 3. If you did get X all the way off, I'm guessing that you didn't give proper permissions for either DRI or OpenGL. Here's my section from xorg.conf:
Code:
# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"
# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a
EndSection
I have a Radeon 9700 Pro, also my permissions look exactly like the ones you posted. I did also change the driver sections
I also have a NForce2 mobo, does that make any difference? By the way, there was something in the xorgconfig about using an external apgart or agp module, what should I select there. I can't remember what I selected.
The only things that are unique about my config file are the following:
I'm using an Intellimouse, so I have that setting instead of a standard PS/2 mouse
My monitor refresh settings- you'll want to change yours to what your monitor uses
I have TV-Out enabled, you might not want yours enabled if you don't use it.
My resolution settings are just what I prefer, you can keep them if you'd like, most monitors support those settings these days.
I got the driver compiled and working great with my 2.6.7 kernel, but there's just one problem. My 3D and everything works fine, but at the GDM login screen, the text that normally shows up there is just little lines (and when I type into the login screen, nothing shows up, but it's working, cuz it lets me log in fine, and once I'm in it seems to work great). I just installed it a few minutes ago, so I don't know if anything else is affected, but as of right now, it's just annoying and I'd like to get it fixed BEFORE I find out if it affects anything else :-P Any help is appreciated.
Your lsmod shows that you have agpgart loaded, but not the mobo-specific agpgart module (which would be formatted chipset-agp ...for instance, mine is intel-agp and would show up in the right column of your agpgart module (where it says unused for you). Both of those must be loaded if you want to use the EXTERNAL agpgart. If you want to / can use the internal one, I don't believe you want either loaded, but mine never works with the internal one (r_jensen's obviously does, because his xorg.conf shows that he's using the internal one). Hope this starts pointing you in the right direction.
Your lsmod shows that you have agpgart loaded, but not the mobo-specific agpgart module (which would be formatted chipset-agp ...for instance, mine is intel-agp and would show up in the right column of your agpgart module (where it says unused for you). Both of those must be loaded if you want to use the EXTERNAL agpgart. If you want to / can use the internal one, I don't believe you want either loaded, but mine never works with the internal one (r_jensen's obviously does, because his xorg.conf shows that he's using the internal one). Hope this starts pointing you in the right direction.
Jeff
I'm guessing that you can't use the internal because of possibly it being a 2.6.x kernel. I'm tempted to try the 2.6.7 kernel again, soley for the purpose of getting sleep modes with the acpi interface, but other than that one thing, the 2.4.26 kernel's been rock-solid for me, well, except for one thing: Whenever I run /sbin/lilo I can't boot into XP. I can when I use the bare.i kernel from the CD if I boot from the CD. It didn't use to be this way, but I can't fully remember when it changed. I install lilo on my /dev/hde's MBR because I keep /dev/hda's clean in case I pop hde out, then I can still safely boot into Windows. When lilo runs properly, it has a warning saying that the hard drive I'm installing LILO to (/dev/hde) isn't the first hard drive. When it doesn't install properly, it doesn't give me that warning. I can always boot into Linux, but for gaming and for my family's familiarity with Windows, it's a pretty big/annoying problem. I don't know if it's a kernel setting or what, but I havn't touched my /boot/vmlinuz-ide-2.4.26, I've removed the symbolic link between it and /boot/vmlinuz and /boot/System.map from the default System.map-ide-2.4.26, but I've replaced those, and I still don't get what's wrong with it.
Originally posted by TheRepublican I want to update my Slack 9.1 box to the new Slack 10, however 10 comes with the new x11-6.7.0-i486-4 package from x.org. Will the fglrx drivers work with this version, or do you even need them? Is the radeon or ati driver that comes with x.org as good as the fglrx drivers?
ok, i'm on the same path, having erased my perfectly working mandrake 9.1 for an attempt at slackware 10 (and a stab at the 2.6.7 kernal).
i'm using what must be the default xorg.conf as all my attempts to run xorgconf have failed to produce anything meaningful. i'm proding away at the xorg.conf with values from my old setup and i was able to get an acceptable display by adding the following:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
