Announcement

Collapse
No announcement yet.

Problem with fglrx 8.11 and Fedora 10 (preview)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
    Christian_L
    Phoronix Member

  • Christian_L
    replied
    There was a fix reported on fedoraforum
    http://forums.fedoraforum.org/showthread.php?p=1117703

    Didn't change anything for me, though.

    Leave a comment:

  • Kano
    Kanotix Developer

  • Kano
    replied
    Well radeon/drm may not be loaded, thats clear. If it is in the initrd you can unload it maybe or change the initrd. On debian blacklisting and then

    update-initramfs -u

    would work, no idea what fedora uses.

    Leave a comment:

  • planetf1
    Junior Member

  • planetf1
    replied
    I tried this out when 8.11 came out.

    The bad kernel module was the radeon driver being loaded. I initially tried

    a) Adding "blacklist radeon" to /etc/modprobe.d/ati
    b) uninstalling the xorg*ati*rpm package
    c) removing the "rhgb" and adding "nomodeset" options to /boot/grub/menu.lst to stop the graphical boot

    However the radeon module was still loaded

    I then (after the above) rebuilt initrd , and after a reboot - no ati module!

    I then installed the fglrx drivers (I tried both the feed on rpmfusion, as well as an install from the official driver, but in neither case could I get sensible behaviour

    More details here -> http://forums.fedoraforum.org/showpo...9&postcount=18

    Note that interestingly I had no issues with changing xorg to run "radeonhd" instead of "radeon" -- not that radeonhd was any better, indeed I think ati works the best.

    Overally the opensource ati is working fairly well for desktop. 3D comes and goes dependent on the kernel/ati updates from the update feeds. more on that here -> http://forums.fedoraforum.org/showthread.php?t=204296

    Leave a comment:

  • Christian_L
    Phoronix Member

  • Christian_L
    replied
    Originally posted by Kano View Post
    dkms status
    fglrx, 8.552, 2.6.27.5-117.fc10.i686, i686: installed

    [Edit] Ah yes, the first line in /var/log/boot.log is this, which has been reported by others on fedoraforum as well:
    FATAL: Error inserting fglrx (/lib/modules/2.6.27.5-117.fc10.i686/fglrx.ko): Operation not permitted
    Christian_L
    Phoronix Member
    Last edited by Christian_L; 25 November 2008, 02:49 AM.

    Leave a comment:

  • Kano
    Kanotix Developer

  • Kano
    replied
    dkms status

    Leave a comment:

  • Christian_L
    Phoronix Member

  • Christian_L
    replied
    Originally posted by Kano View Post
    @Christian_L

    (EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work

    That means that you are using the fglrx kernel module from an older driver. You have to reboot if you don't know how to unload that correctly.
    I've rebooted multiple times since the installation (with hibernation being broken...) but the problem is still there. "lsmod | grep fglrx" returns nothing, while "lsmod | grep radeon" spits out

    radeon 234192 2
    drm 158260 2 radeon
    i2c_algo_bit 8836 1 radeon
    i2c_core 21396 4 i2c_i801,radeon,drm,i2c_algo_bit

    Is the presence of the radeon driver a problem? I have installed the driver with "sh ati-driver-installer-8-11-x86.x86_64.run" and it returned no errors. Since I only installed 8.11 in the new F10 kernel, there should be no way for a kernel module from an old driver to be present there - or am I understanding this wrong?

    Leave a comment:

  • Kano
    Kanotix Developer

  • Kano
    replied
    @Christian_L

    (EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work

    That means that you are using the fglrx kernel module from an older driver. You have to reboot if you don't know how to unload that correctly.

    Leave a comment:

  • muep
    Junior Member

  • muep
    replied
    Originally posted by NeoBrain View Post
    Your problem is that you're telling the fglrx package to create an F9 rpm while using F10. That actually shouldn't be much of a problem, but with the F10 update one also updates the rpm utility to version 2.6, which breaks compatibility, and thus the fglrx package fails to create the rpm file.
    For a workaround just install it via the automatic installation routine. This isn't very clean, but it should work.
    It doesn't work, no matter which way is used to install the driver. I tried the RPM package generated by the RPM Fusion repository.

    By the way, the RPM program version number in Fedora is actually 4.6.0, not 2.6. In addition, the all the packages for the older RPM should work just fine, since the file format hasn't changed in an incompatible way.

    Leave a comment:

  • NeoBrain
    Senior Member

  • NeoBrain
    replied
    Your problem is that you're telling the fglrx package to create an F9 rpm while using F10. That actually shouldn't be much of a problem, but with the F10 update one also updates the rpm utility to version 2.6, which breaks compatibility, and thus the fglrx package fails to create the rpm file.
    For a workaround just install it via the automatic installation routine. This isn't very clean, but it should work.

    Leave a comment:

  • Christian_L
    Phoronix Member

  • Christian_L
    replied
    I did an upgrade to the F10 preview and installed Catalyst 8.11, which gives me a graphical display, but without OpenGL. The relevant errors are as following:

    $ egrep "WW|EE" /var/log/Xorg.0.log
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled.
    (WW) Disabling Keyboard0
    (II) Loading extension MIT-SCREEN-SAVER
    (WW) Warning, couldn't open module type1
    (EE) Failed to load module "type1" (module does not exist, 0)
    (WW) Falling back to old probe method for v4l
    (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 4.1
    (WW) fglrx(0): Failed to get kernel info
    (EE) fglrx(0): Failed to initialize ASIC in kernel.
    (EE) fglrx(0): [FB] Can not get FB MC address range.
    (WW) fglrx(0): board is an unknown third party board, chipset is supported
    (WW) fglrx(0): Unknown vendor-specific block f
    (EE) fglrx(0): Failed to enable interrupts.
    (WW) fglrx(0): Kernel Module version does *not* match driver.
    (EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work
    (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.
    (EE) fglrx(0): XMM failed to open CMMQS connection.
    (WW) fglrx(0): Option "VendorName" is not used
    (WW) fglrx(0): Option "ModelName" is not used

    $ glxgears
    X Error of failed request: BadRequest (invalid request code or no such operation)
    Major opcode of failed request: 158 (GLX)
    Minor opcode of failed request: 19 (X_GLXQueryServerString)
    Serial number of failed request: 12
    Current serial number in output stream: 12

    Same error for "amdcccle", "glxinfo", "fglrxinfo"

    Kernel version 2.6.27.5-117.fc10.i686

    The start-up sequence does not show me a graphical boot. Xv does of course not work, but as somebody else pointed out here before, videos in x11 video mode look surprisingly good and fluid. Going into hibernation hangs the system and gives me a garbled display.
    So yeah, the new Xserver is working with Catalyst 4.11 on F9 (tested before upgrading to F10) and I manage to get a graphical display with F10 - does this mean that the problem does not lie with the Xserver but with the kernel (and might be solved with a kernel update)?
    Christian_L
    Phoronix Member
    Last edited by Christian_L; 24 November 2008, 01:35 PM.

    Leave a comment:

Working...
X