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.
I don't know if it's a kernel compile issue (I did strip it down pretty well), or a ATI + 2.6.2 issue where maybe their driver isn't 2.6.2 ready for some reason.
Right now I have loadable module support + module unloading. I have the AGPGART module as well as the ATI option under AGPGART as a module. DRI is a module as well as the ATI option under DRI. (Sorry, on my work PC so I can't be more specific).
When running make.sh under lib/modules/fglrx it echoed 2.6.x but I can't insmod the fglrx.ko module or another one named fglrx.2.6.2.ko. I get the above referenced issue.
Has anyone else gotten the fglrx drivers to work in 2.6.2?
for 2.6.2? i did back when i had 2.4.20 i think, but that just gave the option to compile the kernel with nvidia chipset support. haven't needed it since. good luck!
i didn't have mtrr support when it worked for me. however, last night i added (because of a suggestion from xine-check) mtrr support and it killed my nicely running machine... recompiled with it included, started up slack, and only vesa drivers would work after. this opened pandoras box, and now, after a lot of work and troubleshooting, i managed to make my machine unable to get through POST =(
anyways, you say you have agpgart loaded, but do you have the nvidia-agp module loaded as well? you need both. also, i think i remember getting an error like that when trying to install fglrx 3.2.8 drivers in 2.6.2. if you're trying to use 3.2.8, get 3.7. if i could get to my desktop, i have a good link for dealing with the fglrx module. if i get my computer up and running, i'll post the link.
Which script denotes what modules are loaded at boot time?
/etc/modules.conf or /rc.d/rc.modules?
I wanted to try just loading fglrx and not loading agpgart.
I don't understand what other DRM module is being loaded before fglrx other than agpgart.
lsmod only shows my ethernet module.
Nothing else was selected as being compiled in. I did a cat proc/dri/0/modules which showed i835 or something. I tried to rmmod i835 which returned an error, and I don't see any other character devices selected as being compiled in/modules.
Originally posted by zigmund555 The error from dmesg is:
[fglrx:firegl_stub_register] *ERROR* Fire GL kernel module has to be loaded prior to any other DRM kernel module!
Under character devices I have:
Unix 98 PTY support compiled in (it came up as a default)
/dev/agpgart as a module.
that's it.
That's exactly what I was looking for.
I think you have agpgart already loaded while you're loading fglrx... Load fglrx first :-D
Either that, or you have DRI compiled in.
edit: Pardon me, I skipped your last post.
Yes, that module you tried to unload is compiled into your kernel from what I can see.
Go through your config and take note around the agpgart section
You'll not want to have any sort of DRI compiled in.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.