Bug 112867 - ATI proprietary drivers not working on some 2.6 kernels
ATI proprietary drivers not working on some 2.6 kernels
Status: CLOSED DUPLICATE of bug 78616
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2004-01-04 16:15 EST by Bernie Innocenti
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:00:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bernie Innocenti 2004-01-04 16:15:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1; Linux 2.6.0-1.23custom; X11; , en) (KHTML, like Gecko)

Description of problem:
The kernel module fglrx.ko compiled from
fglrx-glc22-4.3.0-3.7.0.i386.rpm (available from ATI)
works fine with these kernels:

  2.6.0-1.103 (Arjan)
  2.6.0-1.23 (Fedora)

insmodding in 2.6.0-1.109 produces a OOPS for NULL
pointer dereference (sorry, can't provide more detail
right now).

My guess is that it has something to do with changes in
include/linux or include/asm-i386, because I've seen the
very same OOPS in -1.23 using fglrx.ko built with the
-1.109 headers.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. build and install kernel-source-2.6.0-1.109
2. download and install fglrx-glc22-4.3.0-3.7.0.i386.rpm
3. build module in /lib/modules/fglrx/build_mod/2.6.x
4. install module
5. insmod fglrx

Additional info:
Comment 1 Arjan van de Ven 2004-01-04 16:55:01 EST
I'm sorry but I don't care if binary only modules can be linked in the
kernel or not.

*** This bug has been marked as a duplicate of 78616 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:00:33 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.