FedoraForum.org - Fedora Support Forums and Community
Page 1 of 2 12 LastLast
Results 1 to 15 of 26
  1. #1
    Join Date
    Aug 2004
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Post How to install ATI Catalyst 9.6 in Fedora 11 (as of Jun 20th)

    Alright, it seems a lot of people are curious about whether ATI catalyst driver 9.6 runs in F11, including me, I decided to give it another try - the first try was a failure when I tried to downgrade kernel to 2.6.27.24-170.2.68.fc10 directly. Now, the result of second try is out, it works.

    That is, when you do the following steps. It is worth mentioning that there is absolutely NO guarantee that it will work in your system. If you want a stable system, I suggest a little more patience while playing with community driver, which in my opinion deserves praises, since it is getting better all the time.

    My hardware specifications:
    Athlon X2 7750 BE + DDR2-1066 2G x2 + Asrock 790GMH/128M + integrated graphics HD3300

    OS: Fedora 11 x86_64

    1) download fc10 kernel source rpm:
    Code:
    $wget http://kojipkgs.fedoraproject.org/packages/kernel/2.6.27.24/170.2.68.fc10/src/kernel-2.6.27.24-170.2.68.fc10.src.rpm
    2) rebuild 2.6.27.24 kernel for F11
    Code:
    $rpmbuild --rebuild kernel-2.6.27.24-170.2.68.fc10.src.rpm
    note: keep it in mind, this step may take while and require about 7G disk space
    3) install new kernel and kernel-devel packages
    Code:
    #yum localinstall kernel-2.6.27.24-170.2.68.fc11.x86_64.rpm kernel-devel-2.6.27.24-170.2.68.fc11.x86_64
    note: you need to disable gpgcheck temporarily.
    4) download ATI catalyst driver
    Code:
    $wget https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-9-6-x86.x86_64.run
    note: if you have a different chipset, choose what you need accordingly.
    5) install ATI catalyst driver
    Code:
    #sh ati-driver-installer-9-6-x86.x86_64.run
    6) check out xorg.conf file. If you don't have a /etc/X11/xorg.conf beforehand, I recommend create it before step 5 by:
    Code:
    #Xorg -configure :1
    #cp ~/xorg.conf.new /etc/X11/xorg.conf
    7) disable SELinux by append 'selinux=0' . Yeah, you have to do this, otherwise, at least in my box, it won't boot.
    Code:
    #sed -ie 's/\(kernel .*2.6.27.24-170.2.68.*\)/\1 selinux=0/' /boot/grub/grub.conf
    8) reboot system, and good luck!
    9) when you are tired of fglrx, or rpmfusion release fglrx rpms, you just need to do:
    Code:
    #cd /usr/share/ati
    #./fgl_uninstall.sh
    #yum remove kernel-2.6.27.24-170.2.68.fc11.x86_64.rpm kernel-devel-2.6.27.24-170.2.68.fc11.x86_64
    then everything back on track again.

    Known issues:
    1) the alsa driver in kernel 2.6.27.24 is 1.0.17, so, if your audio card is not supported like mine, you'd better download alsa driver 1.0.20 and install it.
    2) some system services may need to be manually enabled again.
    3) the driver runs basically stable here, but I find the window minimize/maximize function does not work rightly. But I'm not sure whether it's a compiz problem or fglrx issue.

    Ok, the difference of glxgears benchmark when using radeon or fglrx driver is quite noticable, about 330~360 fps (radeon) vs 2000~2900 fps (fglrx), although the difference of realtime performance aren't that different.

    Another thing, when selinux is enabled, F11 won't boot, in my case, it hangs at system logger after auditd failed message. So, i whether it is a selinux conflict or audit daemon issue. I hope someone may give a hint here.

    thanks.
    Last edited by aaccdd; 28th June 2009 at 02:42 AM. Reason: Modify kernel source rpm download link

  2. #2
    Join Date
    Aug 2005
    Posts
    57
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    This actually runs on your system? I encouter the same problems, I had with the tests before. The gdm seems to run fine, but after login the system actually has between 2-10 seconds to life in average. Anyone else who tries this with an 4850? I think, that I have here an issue with "fglrx" and another yet unknown component.
    btw: On GDM I had a small system lookup for about 1-2 seconds. User having this problem might want to use "nopat" aus boot option. This actually works the drivers <=9.4
    Fedora 36
    KDE Frameworks 5.94

  3. #3
    Join Date
    Aug 2004
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Yes, it does. But I have only tested 9.5/9.6 with gdm. I'm not sure whether it works in other conditions. When selinux is disabled, the boot process is quite smooth. And I have not met crash, lockup, etc, till now.

  4. #4
    Join Date
    Nov 2008
    Posts
    176
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    For what it's worth, I tried the Fedora 11 2.6.28 kernel and the 9.6 catalyst from ATI's site, per their instructions.

    My desktop would lockup after a few seconds after login and getting to my desktop. I could ssh to the system and restart it, though.

    Below are the errors and warnings from Xorg.0.log....not sure if anyone would be able to figure out how to resolve the issue or not but I'm posting this in case others were interested.

    (I have an ATI 4850 with dual screens connected but one screen I do not actively use with Linux at the moment)

    Jeff

    X.Org X Server 1.6.1.901 (1.6.2 RC 1)
    Release Date: 2009-5-8
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.18-128.1.6.el5 i686
    Current Operating System: Linux w1 2.6.28-3.fc11.i686.PAE #1 SMP Fri Dec 26 07:54:02 EST 2008 i686
    Kernel command line: ro root=UUID=0e9336c8-30e4-4d07-9075-0eb02bd61ce6 nomodeset rhgb quiet vga=0x323
    Build Date: 18 May 2009 02:47:59PM
    Build ID: xorg-x11-server 1.6.1.901-1.fc11
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jun 21 16:22:15 2009
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "aticonfig Layout"
    (**) |-->Screen "aticonfig-Screen[0]-0" (0)
    (**) | |-->Monitor "aticonfig-Monitor[0]-0"
    (**) | |-->Device "aticonfig-Device[0]-0"
    (**) |-->Screen "aticonfig-Screen[0]-1" (1)
    (**) | |-->Monitor "aticonfig-Monitor[0]-1"
    (**) | |-->Device "aticonfig-Device[0]-1"
    (==) Automatically adding devices
    (==) Automatically enabling devices
    (==) FontPath set to:
    catalogue:/etc/X11/fontpath.d,
    built-ins
    (==) ModulePath set to "/usr/lib/xorg/modules"
    (II) Cannot locate a core pointer device.
    (II) Cannot locate a core keyboard device.
    (II) The server relies on HAL to provide the list of input devices.
    If no devices become available, reconfigure HAL or disable AllowEmptyInput.
    (II) Loader magic: 0x640
    (II) Module ABI versions:
    X.Org ANSI C Emulation: 0.4
    X.Org Video Driver: 5.0
    X.Org XInput driver : 4.0
    X.Org Server Extension : 2.0
    (II) Loader running on linux
    (++) using VT number 1

    (--) PCI:*(0@1:0:0) ATI Technologies Inc RV770 [Radeon HD 4850] rev 0, Mem @ 0xd0000000/268435456, 0xe5000000/65536, I/O @ 0x00009000/256, BIOS @ 0x????????/131072
    (II) No APM support in BIOS or kernel

    (NOTE: the rest cut to fit in this message)

    $ grep EE Xorg.0.log
    (EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
    (EE) fglrx(0): XMM failed to open CMMQS connection.
    (EE) fglrx(1): DRI initialization for 2nd screen failed - aborting!
    (EE) fglrx(1): XMM failed to open CMMQS connection.

    $ grep WW Xorg.0.log
    (WW) Falling back to old probe method for fglrx
    (WW) This ATI Proprietary Linux Driver does not guarantee support of video driver ABI higher than 2.0
    (WW) Video driver ABI version of the X server is 5.0
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
    (WW) EDID preferred timing clock 162.00MHz exceeds claimed max 160MHz, fixing
    (WW) fglrx(0): Hasn't establisted DRM connection
    (WW) fglrx(0): No DRM connection for driver fglrx.
    (WW) EDID preferred timing clock 162.00MHz exceeds claimed max 160MHz, fixing
    (WW) fglrx(1): Unable to register ADL handler for 0x00110000
    (WW) fglrx(1): Unable to register ADL handler for 0x00120000
    (WW) fglrx(1): Unable to register ADL handler for 0x00130000
    (WW) fglrx(0): could not detect X server version (query_status=-1)
    (WW) fglrx(0): ***********************************************
    (WW) fglrx(0): * DRI initialization failed! *
    (WW) fglrx(0): * (maybe driver kernel module missing or bad) *
    (WW) fglrx(0): * 2D acceleraton available (MMIO) *
    (WW) fglrx(0): * no 3D acceleration available *
    (WW) fglrx(0): ********************************************* *
    (WW) fglrx(0): Textured Video not supported without DRI enabled.
    (WW) fglrx(0): Option "VendorName" is not used
    (WW) fglrx(0): Option "ModelName" is not used
    (WW) fglrx(1): DRI initialization on primary screen failed.
    (WW) fglrx(1): ***********************************************
    (WW) fglrx(1): * DRI initialization failed! *
    (WW) fglrx(1): * (maybe driver kernel module missing or bad) *
    (WW) fglrx(1): * 2D acceleraton available (MMIO) *
    (WW) fglrx(1): * no 3D acceleration available *
    (WW) fglrx(1): ********************************************* *
    (WW) fglrx(1): Textured Video not supported without DRI enabled.
    (WW) fglrx(1): Option "VendorName" is not used
    (WW) fglrx(1): Option "ModelName" is not used
    Last edited by Jeff72; 21st June 2009 at 11:22 PM.

  5. #5
    Join Date
    Aug 2004
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    jeff72, I don't know how you did it. Did you try run modinfo fglrx after install ati driver? But in kernel-2.6.28, fglrx.ko does not compile here. And I tested the 2.6.28 kernel you mention, it did not work. I guess you could try kernel 2.6.27, at least, it is known to work.
    Code:
    grep -i "Loading.*fglrx" /var/log/Xorg.0.log
    (II) Loading sub module "fglrxdrm"
    (II) Loading /usr/lib64/xorg/modules/linux//libfglrxdrm.so
    (II) Loading /usr/lib64/xorg/modules/drivers//fglrx_drv.so
    (II) Loading sub module "fglrxdrm"
    (II) Reloading /usr/lib64/xorg/modules/linux//libfglrxdrm.so
    (II) Loading extension ATIFGLRXDRI
    (II) Loading extension FGLRXEXTENSION
    there's a lot Warnings too
    Code:
    grep "WW.*fglrx" /var/log/Xorg.0.log
    (WW) Falling back to old probe method for fglrx
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:17:0) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:1) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:2) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:1) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:1) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:2) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:5) found
    (WW) fglrx(0): board is an unknown third party board, chipset is supported
    (WW) fglrx(0): Only one display is connnected,so single mode is enabled
    (WW) fglrx(0): could not detect X server version (query_status=-1)
    (WW) fglrx(0): Option "VendorName" is not used
    (WW) fglrx(0): Option "ModelName" is not used
    Last edited by aaccdd; 22nd June 2009 at 01:56 AM.

  6. #6
    Join Date
    Nov 2008
    Posts
    176
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by aaccdd
    jeff72, I don't know how you did it. Did you try run modinfo fglrx after install ati driver? But in kernel-2.6.28, fglrx.ko does not compile here. And I tested the 2.6.28 kernel you mention, it did not work. I guess you could try kernel 2.6.27, at least, it is known to work.
    Code:
    grep -i "Loading.*fglrx" /var/log/Xorg.0.log
    (II) Loading sub module "fglrxdrm"
    (II) Loading /usr/lib64/xorg/modules/linux//libfglrxdrm.so
    (II) Loading /usr/lib64/xorg/modules/drivers//fglrx_drv.so
    (II) Loading sub module "fglrxdrm"
    (II) Reloading /usr/lib64/xorg/modules/linux//libfglrxdrm.so
    (II) Loading extension ATIFGLRXDRI
    (II) Loading extension FGLRXEXTENSION
    there's a lot Warnings too
    Code:
    grep "WW.*fglrx" /var/log/Xorg.0.log
    (WW) Falling back to old probe method for fglrx
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:17:0) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:1) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:2) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:1) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:1) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:2) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:5) found
    (WW) fglrx(0): board is an unknown third party board, chipset is supported
    (WW) fglrx(0): Only one display is connnected,so single mode is enabled
    (WW) fglrx(0): could not detect X server version (query_status=-1)
    (WW) fglrx(0): Option "VendorName" is not used
    (WW) fglrx(0): Option "ModelName" is not used
    How do I try to compile the fglrx.ko module?

    When I did the "sh ati-driver-installer-9-6-x86.x86_64.run" it seemed to finish and complete successful. I didn't see any compiling though. I'm new to installing the ATI driver manually, so let me know what you'd like me to try.

    Currently the system is unstable on 2.6.28 kernel with ATI driver. I don't think the fglrx.ko is available but not sure when it is suppose to be compiled.

  7. #7
    Join Date
    Nov 2008
    Posts
    176
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by aaccdd
    jeff72, I don't know how you did it. Did you try run modinfo fglrx after install ati driver? But in kernel-2.6.28, fglrx.ko does not compile here. And I tested the 2.6.28 kernel you mention, it did not work. I guess you could try kernel 2.6.27, at least, it is known to work.
    Code:
    grep -i "Loading.*fglrx" /var/log/Xorg.0.log
    (II) Loading sub module "fglrxdrm"
    (II) Loading /usr/lib64/xorg/modules/linux//libfglrxdrm.so
    (II) Loading /usr/lib64/xorg/modules/drivers//fglrx_drv.so
    (II) Loading sub module "fglrxdrm"
    (II) Reloading /usr/lib64/xorg/modules/linux//libfglrxdrm.so
    (II) Loading extension ATIFGLRXDRI
    (II) Loading extension FGLRXEXTENSION
    there's a lot Warnings too
    Code:
    grep "WW.*fglrx" /var/log/Xorg.0.log
    (WW) Falling back to old probe method for fglrx
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:17:0) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:1) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:2) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:1) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:1) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:2) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
    (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:5) found
    (WW) fglrx(0): board is an unknown third party board, chipset is supported
    (WW) fglrx(0): Only one display is connnected,so single mode is enabled
    (WW) fglrx(0): could not detect X server version (query_status=-1)
    (WW) fglrx(0): Option "VendorName" is not used
    (WW) fglrx(0): Option "ModelName" is not used
    OK, yeah, looks like the module compile failed. Here is the log. Any suggestions on how to get it to compile the module?

    By the way, I am using the Fedora 32bit version and the PAE kernel.

    # cat /usr/share/ati/fglrx-install.log
    [Message] Kernel Module : Trying to install a precompiled kernel module.
    [Message] Kernel Module : Precompiled kernel module version mismatched.
    [Message] Kernel Module : Found kernel module build environment, generating kernel module now.
    AMD kernel module generator version 2.1
    doing Makefile based build for kernel 2.6.x and higher
    rm -rf *.c *.h *.o *.ko *.GCC* .??* *.symvers
    make -C /lib/modules/2.6.28-3.fc11.i686.PAE/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
    make[1]: Entering directory `/usr/src/kernels/2.6.28-3.fc11.i686.PAE'
    CC [M] /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function ‘KCL_SetPageCache_Array’:
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1230: warning: unused variable ‘ret’
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:1229: warning: unused variable ‘i’
    CC [M] /lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.o
    CC [M] /lib/modules/fglrx/build_mod/2.6.x/kcl_agp.o
    CC [M] /lib/modules/fglrx/build_mod/2.6.x/kcl_debug.o
    CC [M] /lib/modules/fglrx/build_mod/2.6.x/kcl_ioctl.o
    CC [M] /lib/modules/fglrx/build_mod/2.6.x/kcl_io.o
    CC [M] /lib/modules/fglrx/build_mod/2.6.x/kcl_pci.o
    CC [M] /lib/modules/fglrx/build_mod/2.6.x/kcl_str.o
    CC [M] /lib/modules/fglrx/build_mod/2.6.x/kcl_wait.o
    LD [M] /lib/modules/fglrx/build_mod/2.6.x/fglrx.o
    Building modules, stage 2.
    MODPOST 1 modules
    FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'lock_acquire'
    make[2]: *** [__modpost] Error 1
    make[1]: *** [modules] Error 2
    make[1]: Leaving directory `/usr/src/kernels/2.6.28-3.fc11.i686.PAE'
    make: *** [kmod_build] Error 2
    build failed with return value 2
    [Error] Kernel Module : Failed to compile kernel module - please consult readme.

  8. #8
    Join Date
    Aug 2004
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    If the official ATI Catalyst driver is sucessfully compiled, there'll be a fglrx.ko in /lib/module/fglrx, like:
    Code:
    ls /lib/modules/fglrx/fglrx.ko -l
    lrwxrwxrwx 1 root root 41 06-22 08:15 /lib/modules/fglrx/fglrx.ko -> ./fglrx.2.6.27.24-170.2.68.fc11.x86_64.ko
    here is my /usr/share/ati/fglrx-install.log:
    Code:
    .....
      Building modules, stage 2.
      MODPOST 1 modules
      CC      /lib/modules/fglrx/build_mod/2.6.x/fglrx.mod.o
      LD [M]  /lib/modules/fglrx/build_mod/2.6.x/fglrx.ko
    make[1]: Leaving directory `/usr/src/kernels/2.6.27.24-170.2.68.fc11.x86_64'
    build succeeded with return value 0
    done.
    You also get:
    Code:
    modinfo fglrx
    filename:       /lib/modules/2.6.27.24-170.2.68.fc11.x86_64/kernel/drivers/char/drm/fglrx.ko
    license:        Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY
    description:    ATI Fire GL
    author:         Fire GL - ATI Research GmbH, Germany
    srcversion:     9EE2FA409B5E408A23E1396
    alias:          pci:v00001002d000095CFsv*sd*bc*sc*i*
    ...
    alias:          pci:v00001002d00009610sv*sd*bc*sc*i*
    depends:        
    vermagic:       2.6.27.24-170.2.68.fc11.x86_64 SMP mod_unload 
    parm:           firegl:charp
    In your case, it's quite clear that compiling failed, and kernel-2.6.28-3 doesn't compile, I've tried that.

  9. #9
    Join Date
    Aug 2005
    Posts
    57
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    For those, who claim themself insane and beeing a masochist:
    http://www.fedoraforum.de/viewtopic.php?f=31&t=17841

    A good month ago, I posted in the german forum (use bablefish or just take the code) my try to get the fglrx running. The patch based IMAO on the archlinux community patch, with beeing merged with another one. This one should also work for 9.5 and 9.6 and I was able to compile and load the driver. However the result was the same as using the downgrade mentioned from the thread starter. Be also warned that even if this "patch" works for you for newer kernel, the fglrx might spam your kernel messages and fill up your harddisk. If someone manage to get its driver running this way, please report.

    Meanwhile another one in the german forum got it running using the hint from the thread starter. He also using realtek networkcards, so my initial idea that the NIC makes the trouble seems to be wrong. If someone got the fglrx working with F11 (which way...) he might post his "lspci". Maybe we might locate the root of my problem.
    Fedora 36
    KDE Frameworks 5.94

  10. #10
    Join Date
    Oct 2007
    Posts
    469
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)
    No such file `kernel-2.6.27.24-170.2.68.fc10.src.rpm'.

  11. #11
    Join Date
    Aug 2004
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Try download kernel-2.6.27-24-170.2.68.fc10.src.rpm from koji, as modified in the above post; or use new kernel-2.6.27.25-170.2.72.fc10.src.rpm

  12. #12
    Join Date
    Aug 2004
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Update: I have again installed ati catalyst 9.6 in a self-spinned kernel-2.6.30-6 ( from kernel-2.6.30-6.fc12.src.rpm in rawhide). This time, F11 is able to boot with selinux enabled, and there's a little performance enhancement with glxgears/fgl_glxgears. To do so:

    1) download kernel-2.6.30-6.fc12.src.rpm, rebuild rpm with CONFIG_LOCKDEP option unset, then install the new kernel rpm, mine is kernel-2.6.30-6.fc11.x86_64.rpm.
    Code:
    $wget http://kojipkgs.fedoraproject.org/packages/kernel/2.6.30/6.fc12/src/kernel-2.6.30-6.fc12.src.rpm"]kernel-2.6.30-6.fc12.src.rpm
    $rpm -ivh kernel-2.6.30-6.fc12.src.rpm
    $cd rpmbuild/SOURCE #  here, I assume, you have installed rpmdevtools and rebuild rpms as non-root user
    $tar xjvf linux-2.6.30-6.tar.bz2
    $gedit linux-2.6.30-6/arch/x86/Kconfig # find config LOCKDEP_SUPPORT, modify def_bool y --> def bool n
    $tar cjvf linux-2.6.30-6.tar.bz2 linux-2.6.30-6/
    $rpmbuild -bb rpmbuild/SPECS/kernel.spec # rebuild kernel/kernel-devel
    $rpmbuild -bb --target noarch --nodeps rpmbuild/SPECS/kernel.spec # rebuild kernel-firmware
    $ su 
    #rpm -ivh rpmbuild/RPMS/x86_64/kernel-2.6.30-6.fc11.x86_64.rpm rpmbuild/RPMS/x86_64/kernel-devel-2.6.30-6.fc11.x86_64.rpm rpmbuild/RPMS/noarch/kernel-firmware-2.6.30-6.fc11.noarch.rpm
    2) boot F11 with kernel-2.6.30-6, enter single user mode, install official ati catalyst 9.6 driver, and enter /lib/modules/fglrx, manually apply the 6 patches mentioned in this post: http://aur.archlinux.org/packages.php?ID=22899, then cd build_mod directory run make.sh

    3) then you may try to install compiz-fusion-8.3 as leigh123linux said: http://forums.fedoraforum.org/showthread.php?t=173317
    know issues:
    1) system-config-services seems broken, I have to enable certain services manually
    2) r8168 driver doesn't compile, but it seems to be a kernel related problem
    3) I don't know whether it's just me, but I feel compiz (8.3) from fusion is more resource consuming than that comes from fedora repo.

    With CONFIG_LOCKDEP disabled, what will happen to F11 I'm not so sure. If you can't live with it, just do not try this.
    Last edited by aaccdd; 29th June 2009 at 10:50 AM.

  13. #13
    Join Date
    Oct 2007
    Posts
    469
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by aaccdd
    Update: I have again installed ati catalyst 9.6 in a self-spinned kernel-2.6.30-6 ( from kernel-2.6.30-6.fc12.src.rpm in rawhide). This time, F11 is able to boot with selinux enabled, and there's a little performance enhancement with glxgears/fgl_glxgears. To do so:

    1) download kernel-2.6.30-6.fc12.src.rpm, rebuild rpm with CONFIG_LOCKDEP option unset, then install the new kernel rpm, mine is kernel-2.6.30-6.fc11.x86_64.rpm.
    Could you clarify how to unset the CONFIG_LOCKDEP ?
    I skipped that part (just downloaded the kernel and did the rebuild), and I believe that's why YUM LOCALINSTALL gave me:
    Code:
     --> Missing Dependency: kernel-firmware >= 2.6.30-6.fc11 is needed by package kernel-2.6.30-6.fc11.x86_64 (/kernel-2.6.30-6.fc11.x86_64)
    Error: Missing Dependency: kernel-firmware >= 2.6.30-6.fc11 is needed by package kernel-2.6.30-6.fc11.x86_64 (/kernel-2.6.30-6.fc11.x86_64)
     You could try using --skip-broken to work around the problem
     You could try running: package-cleanup --problems
                            package-cleanup --dupes
                            rpm -Va --nofiles --nodigest

  14. #14
    Join Date
    Aug 2004
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Sorry, I forgot to mention that you have to rebuild a kernel-firmware rpm.

  15. #15
    Join Date
    Oct 2007
    Posts
    469
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by aaccdd
    Sorry, I forgot to mention that you have to rebuild a kernel-firmware rpm.
    Bah, yum install says I already have it..

    Setting up Install Process
    Package kernel-firmware-2.6.29.5-191.fc11.noarch already installed and latest version

    I guess its version is not high enough. Unfortunately yum update kernel-firmware finds nothing.. -t

Page 1 of 2 12 LastLast

Similar Threads

  1. I can't find/install kmod-catalyst
    By newc0mer in forum Hardware
    Replies: 2
    Last Post: 7th October 2009, 08:10 AM
  2. Desktop keeps freezing after kmod-catalyst install
    By lhorace in forum Using Fedora
    Replies: 0
    Last Post: 26th September 2009, 08:55 PM
  3. ATI Catalyst 9.x fglrx driver manual install on Fedora 11
    By Jeff72 in forum Guides & Solutions (Not For Questions)
    Replies: 25
    Last Post: 30th August 2009, 08:29 PM
  4. rawhide install from boot.iso for Mar 20th
    By SlowJet in forum Alpha, Beta & Snapshots Discussions (Fedora 11 Only)
    Replies: 2
    Last Post: 20th March 2009, 11:03 PM
  5. Replies: 1
    Last Post: 11th January 2009, 07:04 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •