ATI Radeon Mobility 9600 + fglrx: Failed Module Load
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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.
ATI Radeon Mobility 9600 + fglrx: Failed Module Load
Dear Penguins:
Ok, here's the deal. I'm using an eMachines M6805, the most notorious of them all, and I'm trying to get 3D acceleration. I've heard several people discussing the fact that the actual Radeon driver that runs the normal 9600 WILL run the Mobility 9600, but whether that's true or not, I want to see for myself.
I've installed the modules and built them correctly. I had to retrograde to an earlier version of X, but I'll survive. Here's the interesting thing: Whenever I try to insmod the module, or modprobe it even, it claims that the module does not exist. The file is named:
insmod: can't read 'fglrx': No such file or directory
And, 'modprobe fglrx':
FATAL: Module fglrx not found.
I've tried to depmod, no results. Tried insmod with the full filepath:
insmod: error inserting '/lib/modules/2.6.6/kernel/drivers/char/drm/fglrx.ko': -1 Operation not permitted
I don't need a lot of information about whether or why the driver will or won't work . . . I just want to see if anyone could help me understand why this module won't load. I DO have loadable module support enabled in my kernel. Thanks in advance.
Re: ATI Radeon Mobility 9600 + fglrx: Failed Module Load
Quote:
And it does exist. 'insmod fglrx':
insmod: can't read 'fglrx': No such file or directory
Okay, that is no surprise, insmod needs a full path to the module file, as you correctly tried later.
Quote:
And, 'modprobe fglrx':
FATAL: Module fglrx not found.
I've tried to depmod, no results.
What exactly do you mean with "no results"? Give depmod -av|grep fglrx a shot to see whether it actually touches the file at all. What do you mean it doesn't?! You are root, aren't you? Typos don't help much, either, but I'll presume you're capable of spellchecking commands and module names yourself.
In the surprising case that depmod doesn't even show one sucky line mentioning this module, you might want to double-check if you're running the 2.6.6 kernel at the moment. Dunno how generously your boot menu is endowed with all kinds of different kernels after all. To be safe you can also explicitly tell depmod which kernel version module directory to scour for modules.
Quote:
Tried insmod with the full filepath:
insmod: error inserting '/lib/modules/2.6.6/kernel/drivers/char/drm/fglrx.ko': -1 Operation not permitted
Please tell me you ARE root and didn't apply any obscure security kernel patches. I could fully understand "Unknown symbol in module", but not a permission problem. Maybe, if you feel adventurous, run this command again through strace to see what system calls are actually leading up to this error. It might give a hint where to look for trouble. (Simply run strace insmod /lib/modules/[...] to do that).
Once you are positive that depmod did it's job fine, forget about insmod altogether and exclusively try to get modprobe fglrx to work. It's much more clever than it's cousin.
I have exactly the same problem. Went through a HOWTO on some website - can't remember which at the moment - and got down to the final line, modprobe fglrx, and it failed with that FATAL error.
Is it anything to do with not having EXACTLY the same source code downloaded as the kernel version you have compiled the fglrx module for? I can't seem to find exactly the same kernel source on apt and had to settle for a (very) close version.
I am having the exact same problem (Although, ATI Radeon 9000). I have had this working properly with the 2.6.7 kernel before, but I had some hardware failure and had to format and such. Anyways, my distro is Slackware 10, and I'm using 2.6.7. I applied the 2.6.7 patch, builed and tried to run ./make_install.sh. The only difference this time is it fails to insert the module. So, I run modprobe fglrx, and I get...
I am root, I have no special kernel security modules, or anything else like that. I also ran the strace you asked for, and got the same error as guzugi.
Can anyone point me in the right direction to this? The upgrade you explained previously was most likely not the fix, but something in the kernel settings may have been changed that we are unaware of. Any pointers would be muchly appericated. Thanks
your solution could save alot of us suckers who bought the M68xx line some trouble. I had to rma my M6809 to Best Buy, who just swapped it out with the M6811 model, i kept my HD, and she is back to work. Can you email it maybe? New to linux/suse 9.1 and couldn't compile to fix it either. thanks for your posting
Actualy, instead of directly emailing it.. Posting here would be the easiest and most helpful (as I'm sure other Linux users can benifit from this). Thanks Again
I appericate the reply, however, running the RPM simply will follow the instructions defined by ATI.. It does things no differently (Simply builds/installs using the make.sh, and make_install.sh). I have had this working flawless with no problems before, so there should be a simple reason why this is failing now.
Also, i ran strace modprobe fglrx as a user as well as root, and I got the exact same errors... Both root and a userlevel account got premission denied on init_module.
Any new ideas why both root and user are being denied access to inserting this module? I tested inserting a random driver module, and it went in fine... So The problem points to the ATI driver specifically... I don't think modules can conflict with echother, but I am not to experienced. I am going to try and removing all ATI Radeon drivers that are included with the kernel, and move from there... I have spoken to alot of people, and noone has a clue on why its acting like it is.. So I really want to find out why it is doing this. The only hardware changes I have gone through since my working 2.6.7 w/ fglrx was a harddrive upgrade (I had a 40gb and 60gb... Removed the 40, and now I have a 120gb and 60gb). Also, the ATI drivers were working on 2.4.26 flawless, so its not like the card is damaged or anything. I've narrowed it down as much as possible.. Just the User and Root having the same operation not premitted problem is quite confusing. Any ideas??? Thanks again, lol.
-- Okay, I am still not entirly sure why there was an Operation Not Premitted error... but the solution to my problem, was re-compiling the kernel, but removing my ATI drvers under the DRM. DRM is still embeded in the kernel, but the ATI drivers are no longer. Maybe, the Operation Not Premitted, was being displayed as fglrx was trying to unload an embeded module... I don't know, I know very little about the Linux kernel. Remove the ATI Drivers from the DRM support, re-compile, and then modprobe fglrx again .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.