FS#13084 - catalyst 9.1-1 - error inserting fglrx module

Attached to Project: Arch Linux
Opened by Michael (SiD) - Sunday, 01 February 2009, 17:44 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 05 March 2009, 17:38 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture i686
Severity Critical
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
modprobe fglrx fails with this error:

FATAL: Error inserting fglrx (/lib/modules/2.6.28-ARCH/video/fglrx.ko): Cannot allocate memory


Additional info:
* package version(s)
catalyst-9.1-1

Steps to reproduce:
Install catalyst and try to modprobe fglrx.

I'm using the stock kernel and the system is up to date
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Thursday, 05 March 2009, 17:38 GMT
Reason for closing:  Upstream
Additional comments about closing:  unfixable crap
Comment by Marco Rocco (ech0s7) - Monday, 02 February 2009, 11:31 GMT
are you at 32bit or 64bit ?
Comment by Greg (dolby) - Monday, 02 February 2009, 11:59 GMT
Can you recompile it and see if its related to  FS#13013 ?
Comment by Michael (SiD) - Monday, 02 February 2009, 16:48 GMT
I use i686 on a pentium M.

Recompiling does not work.

I'm not shure, but is it possible that my graphics-card is not supportet by the new Catalyst.
It's a Mobility Radeon 9700 (lspci says its a 9600).

output of lspci:

01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]

Comment by Michael (SiD) - Tuesday, 03 February 2009, 14:40 GMT
I recompiled catalyst against the new stock kernel (2.6.28.3-1), but same problem.
"modprobe fglrx" gives me still this error:

FATAL: Error inserting fglrx (/lib/modules/2.6.28-ARCH/video/fglrx.ko): Cannot allocate memory

p.s.
In the catalyst 9.1 release notes the mobility radeon 9600 is listed as a supported card.
Comment by Andreas Radke (AndyRTR) - Sunday, 15 February 2009, 10:07 GMT
Is your system up to date? Are you running a custom gcc-libs/glibc/kernel pkg? It seems you are the only one having that problem. The package works well for all our users in the forum. Check google for your error message.
Comment by Michael (SiD) - Sunday, 15 February 2009, 12:51 GMT
Yes, my System is up to date and I don't use any custom gcc-libs, glibc and kernel packages.
In the german forum there is one user who has the same Problem.
Comment by Andreas Radke (AndyRTR) - Sunday, 15 February 2009, 13:09 GMT
this is probably an upstream error where we can't do much. think i have to close this soon as an upstream bug.
Comment by derek (derekhl) - Monday, 16 February 2009, 18:23 GMT
Hi, I'm having the exact same problem. When I found the problem (a week ago) my system was up to date, freshly installed, with stock kernel. Today I'm looking further into this problem and I see there is a kernel update, so I'm upgrading, but I just wanted to say that I'm also affected by this. Is there any more information about this problem? Thanks.
Comment by Uli (Army) - Tuesday, 17 February 2009, 12:50 GMT
I am this other user from the german forum, who has the same problem :)
I have the same graphics card SiD has and my lspci outputs are exactly the same. I usually don't use the catalyst driver, but SiD asked me to test it and I can confirm this, the module isn't being loaded and the error message is exactly the same. I didn't make further tests, because I'm sure everything will turn out to be exactly the same as on his computer. I use the arch stock kernel, glibc and all this essential stuff is from [core].
Comment by derek (derekhl) - Tuesday, 17 February 2009, 22:41 GMT
i didnt mention it :) but i also have the same card, mobility radeon 9700 (lspci says 9600)...
Comment by Marco Leli (MarcoL) - Friday, 20 February 2009, 21:27 GMT
Same problem here, on a freshly installaed system with a mobility radeon 9700 [Mobility Radeon 9600 M10]
Comment by Blaž Tomažič (billy) - Saturday, 21 February 2009, 10:10 GMT
same here on Radeon 9500 Pro. It seems only R3xx cards are affected.
Comment by Marco Rocco (ech0s7) - Saturday, 21 February 2009, 11:26 GMT
from catalyst 9.2 also rv620 are affected.
Comment by Michael (SiD) - Monday, 23 February 2009, 11:26 GMT
with catalyst-9.2-1 it works for me. :)
Comment by Marco Rocco (ech0s7) - Monday, 23 February 2009, 11:37 GMT
Hi, it's a problem of archlinux at 64bit.
For 64 bit edit arch/x86/kernel/tlb_64.c by adding
"EXPORT_SYMBOL(flush_tlb_page);" (it is present in tlb_32.c so I'm guessing
32 bit systems aren't seeing this problem) right after the end of the
flush_tlb_page function. Rebuild and install both kernel and fglrx module and
voila, you're good to go.

In this way i have fixed and now catalyst 9.2 works on archlinux 64bit and card hd3470

Good Work! (You can close the bug for me)
Comment by Andreas Radke (AndyRTR) - Monday, 23 February 2009, 16:18 GMT
nope. the people here are talking about an i686 issue (the x86_64 pkg is still at 8.12 due to another issue).

can someone point us to an upstream tracker and report it there? afaik the supported forum section @ phoronix is a good place to catch the AMD/Ati Devs.
Comment by Andreas Radke (AndyRTR) - Thursday, 05 March 2009, 17:38 GMT
this is not a packaging bug. closing as upstream. read also on the forums and mailing lists what's going on with AMD crap.

Loading...