Cannot modprobe fglrx

Some older cards aren't supported in drivers later than 8.28.8.

Release 8.28.8:
August 18, 2006
 Note - This is the last driver version to support the following products:
 Radeon® 8500/9000/9100/9200/9250
 Mobility™ Radeon® 9000/9100/9200
 Radeon® IGP 9000/9100/9200

If this bug is related to #83145, it should be merged, and the devs should include a legacy package for older ATI cards.

No, that's not the case here. My card is a Mobility Radeon X300 (M300), which is supported by 8.33.6 according to ATI's site.

Probably you compiled the driver with gcc 3.x, try recompiling the driveri with gcc4.1

Probably you compiled the driver with gcc3.x, try recompiling the driver with gcc4.1

No, this is the driver included with linux-restricted-modules, in which fglrx is already compiled.

Conkling, your card is an X300, which isn't listed in the unsupported cards. It is therefore detected and working properly.

The unsupported cards should really get a legacy package.

On 2/16/07, Soaa- <email address hidden> wrote:
> Conkling, your card is an X300, which isn't listed in the unsupported
> cards. It is therefore detected and working properly.

No, it's not working properly, which is why I reported this bug. I know my card is supported by fglrx (now at 8.33.6), so the inability to modprobe the driver is a bit confusing.

Issues with unsupported cards are already filed on bug #83145.

Also, a bit more information: this is probably related to bug #77957, which describes not being able to start X with fglrx 8.28.8+ and kernel 2.6.20.

I've tried modprobe'ing fglrx on 2.6.19 and each of the versions of 2.6.20, each with the same failure.

Same problem on my Thinkpad t43, with the Radeon X300.

I ran into the same problem on edgy once, and I have no idea how I got past it. I have this vague recollection that it has something to do with a conflict between fglrx and the open source r300 drivers, but I'm not sure, and blacklisting intel_agp doesn't help.

Make sure the fglrx module is not disabled in /etc/default/linux-restricted-modules-common (see bug #57716).

I upgraded today to Feisty and got the exact same problem with a Radeon X600.. Unable to load fglrx module. I tried to remove /etc/modprobe.d/fglrx as there was a big hack in there.. Why do you guys want to check fglrx appears in xorg.conf before loading the module??

philn, simply because the fglrx module is only used by the "fglrx" driver, and might cause problems for other drivers. So if you haven't specified the "fglrx" driver in xorg.conf, you don't want to have the fglrx module loaded.

Yeah but why the user would want to load that module if he's not using fglrx in xorg.conf ? This is probably more a legal issue and I can understand that

So, are you sure that sed/grep/whatever un-understandable test in /etc/modprobe.d/fglrx is working with any xorg.conf? Anyway i removed that file, how can I recover it (i made no backup) with dpkg ? I tried apt-get install --reinstall xorg-driver-fglrx without much success :-(

So, are you sure that sed/grep/whatever un-understandable test in /etc/modprobe.d/fglrx is working with any xorg.conf? Anyway i removed that file, how can I recover it (i made no backup) with dpkg ? I tried apt-get install --reinstall xorg-driver-fglrx without much success :-(

That test is now inside /etc/modprobe.d/lrm-video from linux-restricted-modules-common.

Has the package maaintainer used the correct GCC version for kernel 2.6.20-15-386?

I had the ATI fglrx drivers working for more than a year by now, but since I run 2.6.20-16-generic with the restricted modules installed I do not have direct rendering anymore.
I also get

$ sudo modprobe fglrx
FATAL: Error running install command for fglrx

My ATI Graphics card is still supported, it is Radeon Xpress 200M, and this definitely looks like a bug in fglrx kernel module from linux-restricted-modules-generic package. Has anyone found a solution?

I got some more output, which reminds me of what someone said earlier in this thread:

$ sudo modprobe fglrx -v
install /sbin/lrm-video fglrx
FATAL: Error running install command for fglrx

Please try: sudo modprobe --ignore-install fglrx
and tell us what the error messages are.

$ sudo modprobe --ignore-install fglrx
FATAL: Module fglrx not found.

In advance: I certainly have the package linux-restricted-modules for the running kernel, 2-6-20-16-generic, installed.

Did you check /etc/default/linux-restricted-modules-common? Please run: sudo sh -x /sbin/lrm-manager --quick
and add the output here as attachment.

my /etc/default/linux-restricted-modules-common is:
   DISABLED_MODULES=""

Is the module built? ls -l /lib/modules/2.6.20-16-generic/volatile/fglrx.ko
Try "depmod -a" and run modprobe again.

$ ls -l /lib/modules/2.6.20-16-generic/volatile/fglrx.ko
-rw-r--r-- 1 root root 942396 2007-06-29 14:40 /lib/modules/2.6.20-16-generic/volatile/fglrx.ko

$ sudo depmod -a

$ sudo modprobe fglrx

(without any error)

whoa! This is a big surprise for me. can you give me a hint what that means? What could have been the cause of this being resolved by running depmod? I will reboot and give the fglrxinfo output in a minute...

$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON XPRESS Series
OpenGL version string: 2.0.6334 (8.34.8)

Thank you very much, Tormod! As it seems, everything is fine again. I was expecting more hazzle than just running depmod. I hope this was not due to some stupidity of mine.

I am surprised depmod has not been run at some point, however I am not sure whether and when linux-restricted-modules is supposed to run it. The init script runs lrm-manager --quick, where "quick" exactly means do not run depmod.

This "depmod" problem is not the only one:
root@DeathStar:/etc/modprobe.d# ls /lib/modules/2.6.20-16-lowlatency/volatile/fglrx.ko
ls: /lib/modules/2.6.20-16-lowlatency/volatile/fglrx.ko: No such file or directory
root@DeathStar:/etc/modprobe.d#

I also confirm this bug on kernel 2.6.20-16-generic an 2.6.20-16-lowlatency.

depmod -a

solved it.

[Expired for linux-restricted-modules-2.6.20 (Ubuntu) because there has been no activity for 60 days.]

This bug was closed automatically because it was marked "incomplete" and had no actitivity for 2 months. However I think the issue was clearly confirmed and just marked "incomplete" waiting for auxiliary information, so I reopen it.

Well, I'm not having this problem anymore (successfully using fglrx on Gutsy and now on Hardy). Is anyone else still having this problem?

Yes, I just experienced the same problem, but using Kubuntu 7.10 with the 2.6.22-14-server kernel. This kernel is apparently installed because of the VMware Server kernel module. I fixed the problem by manually installing the 2.6.22-14-386 kernel (somehow 2.6.22-14-generic doesn't contain the fglrx driver either), but then the vmnet module is gone. So now I have two kernels: one with vmnet module needed for VMware Server, and one with fglrx driver, but I cannot use both at the same time. Another disadvantage of using the 386 kernel is that it only recognizes 3GB of my 4GB RAM, so I really would like to be able to use fglrx driver with my server kernel.
Can someone explain to me why different kernels are pulled in when different modules are desired, rather than just installing the modules for the current kernel? I can understand the modules having to be precompiled for a particular kernel, but the kernel itself is the same version, so where's the conflict?
Note that all kernels I installed were installed through the package manager, and I have not attempted to install any kernel or kernel modules from source.

This package has become obsolete so we're closing out the bug report as WONTFIX.
Thanks for reporting it though!