| View previous topic :: View next topic |
| Author |
Message |
cfroemmel
n00b
Joined: 09 Feb 2005
Posts: 14
Location: Germany
|
 Posted: Thu Mar 03, 2005 10:39 am Post subject: ati-drivers-8.10.19 and gentoo-dev-sources-2.6.11 |
 |
|
After building the new ~x86 Kernel gentoo-dev-sources-2.6.11 I emerged ati-drivers again.
| Code: | | emerge --sync && USE="~x86" emerge ati-drivers |
which happens with some errors (similar to dmesg output).
After a
I loaded the fglrx module
Here's the output:
| Quote: | | FATAL: Error inserting fglrx (/lib/modules/2.6.11-gentoo/video/fglrx.ko): Unknown symbol in module, or unknown parameter (see dmesg) |
Here's the output:
| Quote: | fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
fglrx: Unknown symbol agp_bind_memory
fglrx: Unknown symbol agp_enable
fglrx: Unknown symbol agp_backend_acquire
fglrx: Unknown symbol agp_free_memory
fglrx: Unknown symbol agp_allocate_memory
fglrx: Unknown symbol agp_unbind_memory
fglrx: Unknown symbol agp_copy_info
fglrx: Unknown symbol agp_backend_release |
Anyone else with this problem ? |
|
| Back to top |
|
 |
twilight
Tux's lil' helper
Joined: 09 Feb 2003
Posts: 144
Location: Linuxland
|
| Posted: Thu Mar 03, 2005 3:12 pm Post subject: |
|
|
i got a similar problem:
after emerging, configuring, compiling and rebooting with the new 2.6.11-kernel
and remerging the ati-drivers + "opengl-update ati" i try to load the
fglrx-modul,
here is my output:
| Code: | mobilecomputing thommy # modprobe fglrx
FATAL: Error inserting fglrx (/lib/modules/2.6.11-gentoo/video/fglrx.ko): Operation not permitted |
any help apreciated 
Greetings,
twilight
_________________
- The day Micro$oft produces anything that doens`t suck, is probably the day, they start making vacuum cleaners-
"The Box said: Requires Micro$oft Windows XP or better, so I installed Linux" |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Thu Mar 03, 2005 4:02 pm Post subject: |
|
|
cfroemmel: I've just tried emerging the 8.10.19 driver against the 2.6.11-gentoo kernel and everything worked fine. The command you used to emerge the drivers is incorrect, ~x86 is specified in ACCEPT_KEYWORDS, not USE. You were probably emerging the 8.8.25 driver rather than 8.10.19. Using ~x86 like that is also discouraged and maybe even ignored by portage IIRC. What you should do instead is: | Code: | mkdir -p /etc/portage
echo "media-video/ati-drivers ~x86" >> /etc/portage/package.keywords |
twilight, I think you have a different problem from cfroemmel - check you didn't enable "Direct Rendering Manager" under "Device drivers -> Character devices" in the kernel menu. If you enabled that and the "ATI Radeon" option beneath it, it can prevent the fglrx module from loading.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
Kovid
Apprentice
Joined: 25 Aug 2003
Posts: 217
Location: California, USA
|
| Posted: Thu Mar 03, 2005 6:37 pm Post subject: |
|
|
| I had the same problem. Compiling AGP support (agpgart) as a module solved it. Though since I have a pcie card, I don't know why agpgart would be useful. |
|
| Back to top |
|
|
twilight
Tux's lil' helper
Joined: 09 Feb 2003
Posts: 144
Location: Linuxland
|
| Posted: Fri Mar 04, 2005 10:41 am Post subject: |
|
|
hi,
i used exactly the same options as in 2.6.10 and changed nothing.
DRI is switched on, because the ati-driver needs it, but
i switched none of those modules on because i don`t need
that radeon-module because i want to use fglrx instead.
It worked without problems until 2.6.11 arrived, even the
-r1 release doesn`t fix a thing 
_________________
- The day Micro$oft produces anything that doens`t suck, is probably the day, they start making vacuum cleaners-
"The Box said: Requires Micro$oft Windows XP or better, so I installed Linux" |
|
| Back to top |
|
|
twilight
Tux's lil' helper
Joined: 09 Feb 2003
Posts: 144
Location: Linuxland
|
| Posted: Fri Mar 04, 2005 10:57 am Post subject: |
|
|
Hi,
| Quote: | | I had the same problem. Compiling AGP support (agpgart) as a module solved it. Though since I have a pcie card, I don't know why agpgart would be useful |
that solved the problem.
Anyway, it`s strange that it worked without problems in 2.6.10 and
i needed to change things into modules to get it working under 2.6.11
Anyway, thx and greetings,
twilight
_________________
- The day Micro$oft produces anything that doens`t suck, is probably the day, they start making vacuum cleaners-
"The Box said: Requires Micro$oft Windows XP or better, so I installed Linux" |
|
| Back to top |
|
|
atlantic
n00b
Joined: 03 Jan 2005
Posts: 3
|
| Posted: Fri Mar 04, 2005 10:34 pm Post subject: |
|
|
Hello.
After I compiled gentoo-dev-sources (2.6.11), re-emerged ati-drivers 8.10.19, and "modprobe fglrx", it says "Operation not permitted." kern.log says:
| Code: | | Mar 3 15:00:53 amilo [fglrx:firegl_stub_register] *ERROR* Unable to the open some already present DRM kernel module! |
DRM is compiled into the kernel. With 2.6.10-gentoo-r6 it works perfectly.
Any idea would be appreciated. |
|
| Back to top |
|
|
Sith_Happens
Veteran
Joined: 15 Dec 2004
Posts: 1807
Location: The University of Maryland at College Park
|
| Posted: Fri Mar 04, 2005 10:38 pm Post subject: |
|
|
I had some problems concerning the fglrx module and unknown symbols which were solved by compiling module unloading support into my kernel (2.6.10). Hope that helps somebody.
_________________
"That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
| Back to top |
|
|
battersea
Tux's lil' helper
Joined: 08 Nov 2003
Posts: 122
Location: Hove, Belgium
|
| Posted: Mon May 23, 2005 10:37 pm Post subject: |
|
|
The problem is the kernel revision.
I had the exact same "Unknown symbol" errors when loading my nvdia module.
In order to resolve this, I had to go back to an earlier kernel version or enable agpgart (before I was using nvdia's own agp support).
I believe this is a know problem and will be fixed soon. |
|
| Back to top |
|
|
|
Kernel & Hardware
