Announcement

Collapse
No announcement yet.

ATI fglrx 8.31.5 Display Drivers

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #71
    I am struggling with this driver on FC6 x86_64. Here is my xorg.conf and my log. Any suggestions?


    Code:
    (--) Assigning device section with no busID to primary device
    (WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
    (--) Chipset RADEON 9600 (RV350 4150) found
     
    ...
     
    (II) fglrx(0): doing DRIScreenInit
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: Open failed
    [drm] failed to load kernel module "fglrx"
    (II) fglrx(0): [drm] drmOpen failed
    (EE) fglrx(0): DRIScreenInit failed!
    (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): ********************************************* *
    Code:
    # Working /etc/X11/xorg.conf for ATI fglrx 8.29.6 and Fedora Core 6
    # Created by Michael Larabel / Phoronix
    # See: http://www.phoronix.com/redblog/index.php?p=blog&i=NTU1MA
    
    Section "ServerLayout"
    	Identifier     "Default Layout"
    	Screen      0  "aticonfig-Screen[0]" 0 0
    	InputDevice    "Keyboard0" "CoreKeyboard"
    EndSection
    
    Section "Files"
    EndSection
    
    Section "Module"
    Load "dri"
    Load "glx"
    EndSection
    
    Section "InputDevice"
    	Identifier  "Keyboard0"
    	Driver      "kbd"
    	Option	    "XkbModel" "pc105"
    	Option	    "XkbLayout" "us"
    EndSection
    
    Section "Monitor"
    	Identifier   "aticonfig-Monitor[0]"
    	Option	    "VendorName" "ATI Proprietary Driver"
    	Option	    "ModelName" "Generic Autodetecting Monitor"
    	Option	    "DPMS" "true"
    EndSection
    
    Section "Device"
    	Identifier  "aticonfig-Device[0]"
    	Driver      "fglrx"
    	Option	    "TVFormat" "NTSC-M"
    	Option	    "TVOverscan" "off"
    EndSection
    
    Section "Screen"
    	Identifier "aticonfig-Screen[0]"
    	Device     "aticonfig-Device[0]"
    	Monitor    "aticonfig-Monitor[0]"
    	DefaultDepth     24
    	SubSection "Display"
    		Viewport   0 0
    		Depth     24
    	EndSubSection
    EndSection
    
    Section "ServerFlags"
    	Option	    "AIGLX" "off"
    EndSection
    
    Section "DRI"
    	Group        0
    	Mode         0666
    EndSection
    
    Section "Extensions"
    	Option	    "Composite" "Disable"
    EndSection

    Comment


    • #72
      Ok, got it working. Here is what I did:

      1. Follow the instructions here to stop the fireglcontrol panel from compiling, and not generate the rpm files: http://www.phoronix.net/forums/showt...age=2#post2501

      Once I did the above successfully, I had the following rpm files:
      Code:
      -rw-r--r--  1 root     root     10488424 Dec  5 21:25 ATI-fglrx-8.31.5-1.fc6.x86_64.rpm
      -rw-r--r--  1 root     root         7312 Dec  5 21:25 ATI-fglrx-control-panel-8.31.5-1.fc6.x86_64.rpm
      -rw-r--r--  1 root     root       121791 Dec  5 21:25 ATI-fglrx-devel-8.31.5-1.fc6.x86_64.rpm
      -rw-r--r--  1 root     root      5803223 Dec  5 21:25 ATI-fglrx-IA32-libs-8.31.5-1.fc6.x86_64.rpm
      -rw-r--r--  1 root     root       310360 Dec  5 21:25 kernel-module-ATI-fglrx-2.6.18-1.2849.fc6-8.31.5-1.fc6.x86_64.rpm
      2. Removed all the fglrx rpms from the system (I used Add/Remove Software GUI)

      3. Installed kernel-module-ATI-fglrx-2.6.18-1.2849.fc6-8.31.5-1.fc6.x86_64.rpm, ATI-fglrx-8.31.5-1.fc6.x86_64.rpm and ATI-fglrx-control-panel-8.31.5-1.fc6.x86_64.rpm

      4. Used this xorg.conf file:
      Code:
      # Xorg configuration created by system-config-display
      
      Section "ServerLayout"
      	Identifier     "single head configuration"
      	Screen      0  "aticonfig-Screen[0]" 0 0
      	InputDevice    "Keyboard0" "CoreKeyboard"
      EndSection
      
      Section "Files"
      EndSection
      
      Section "Module"
      	Load  "glx"
              Load  "dri"
      EndSection
      
      Section "InputDevice"
      	Identifier  "Keyboard0"
      	Driver      "kbd"
      	Option	    "XkbModel" "pc105"
      	Option	    "XkbLayout" "us"
      EndSection
      
      Section "Monitor"
      	Identifier   "aticonfig-Monitor[0]"
      	Option	    "VendorName" "ATI Proprietary Driver"
      	Option	    "ModelName" "Generic Autodetecting Monitor"
      	Option	    "DPMS" "true"
      EndSection
      
      Section "Device"
      	Identifier  "aticonfig-Device[0]"
      	Driver      "fglrx"
      	Option	    "TVFormat" "NTSC-M"
      	Option	    "TVOverscan" "off"
      EndSection
      
      Section "Screen"
      	Identifier "aticonfig-Screen[0]"
      	Device     "aticonfig-Device[0]"
      	Monitor    "aticonfig-Monitor[0]"
      	DefaultDepth     24
      	SubSection "Display"
      		Viewport   0 0
      		Depth     24
      	EndSubSection
      EndSection
      
      Section "DRI"
      	Mode         0666
      EndSection
      
      Section "Extensions"
      	Option	    "Composite" "Disable"
      EndSection
      
      Section "ServerFlags"
      	Option	    "AIGLX" "off"
      EndSection
      5. Restart X and viola!!

      Hope that helps some of you.

      Comment


      • #73
        3D acceleration is not working on my FC6, configs are fine.

        Hi guys,

        I have read this whole thread and saw that some people are having problems similar to my ones. I am running FC6 and am having problem to get 3D acceleration working with my card. I have a X600 PCIX with two channels and to 24" Dell monitors, everything works fine but just not as fast as I would like it to be.

        I have bilt RPMs using the ati-driver-installer-8.31.5-x86.x86_64.run, drivers installed and working but when I run fglrxinfo I get the below output.

        Xlib: extension "XFree86-DRI" missing on display ":0.0".
        display: :0.0 screen: 0
        OpenGL vendor string: Mesa project: www.mesa3d.org
        OpenGL renderer string: Mesa GLX Indirect
        OpenGL version string: 1.2 (1.5 Mesa 6.5.1)

        This is my config:
        # Xorg configuration created by system-config-display

        Section "ServerLayout"
        Identifier "Multihead layout"
        Screen 0 "Screen0" LeftOf "Screen1"
        Screen 1 "Screen1" 0 0
        InputDevice "Mouse0" "CorePointer"
        InputDevice "Keyboard0" "CoreKeyboard"
        Option "Xinerama" "on"
        Option "Clone" "off"
        EndSection

        Section "Module"
        Load "glx"
        Load "dri"
        EndSection

        Section "ServerFlags"
        Option "AIGLX" "off"
        EndSection

        Section "InputDevice"
        Identifier "Keyboard0"
        Driver "kbd"
        Option "XkbModel" "pc105"
        Option "XkbLayout" "us"
        Option "XkbVariant" "intl"
        EndSection

        Section "InputDevice"
        Identifier "Mouse0"
        Driver "mouse"
        Option "Protocol" "IMPS/2"
        Option "Device" "/dev/input/mice"
        Option "ZAxisMapping" "4 5"
        Option "Emulate3Buttons" "yes"
        EndSection

        Section "Monitor"

        ### Comment all HorizSync and VertSync values to use DDC:
        Identifier "Monitor0"
        VendorName "Monitor Vendor"
        ModelName "DELL 2407WFP"
        Option "dpms"
        EndSection

        Section "Monitor"

        ### Comment all HorizSync and VertSync values to use DDC:
        Identifier "Monitor1"
        VendorName "Monitor Vendor"
        ModelName "Dell 2407FPW"
        Option "dpms"
        EndSection


        Section "Device"
        Identifier "Videocard0"
        Driver "fglrx"
        VendorName "Videocard vendor"
        BoardName "ATI Technologies Inc RV370 5B62 [Radeon X600 (PCIE)]"
        Option "MonitorLayout" "TDMS, TDMS"
        BusID "PCI:1:0:0"
        EndSection

        Section "Device"
        Identifier "Videocard1"
        Driver "fglrx"
        VendorName "Videocard Vendor"
        BoardName "ATI Technologies Inc RV370 5B62 [Radeon X600 (PCIE)]"
        # Option "SWcursor" "On"
        BusID "PCI:1:0:0"
        Screen 1
        EndSection

        Section "Screen"
        Identifier "Screen0"
        Device "Videocard0"
        Monitor "Monitor0"
        DefaultDepth 24
        SubSection "Display"
        Viewport 0 0
        Depth 24
        Modes "1920x1200" "1680x1050"
        EndSubSection
        EndSection

        Section "Screen"
        Identifier "Screen1"
        Device "Videocard1"
        Monitor "Monitor1"
        DefaultDepth 24
        SubSection "Display"
        Viewport 0 0
        Depth 24
        Modes "1920x1200" "1680x1050"
        EndSubSection
        EndSection

        Section "DRI"
        Group 0
        Mode 0666
        EndSection

        Section "Extensions"
        Option "Composite" "Disable"
        EndSection


        And this is my log file. If anyone knows what is going on here and could give a hand it would be very much appreciated. Thanks a lot in advance

        Vini

        Comment


        • #74
          Sorry the log seems to be too long and the website is crashing everytime when I post it.

          (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
          (WW) No FontPath specified. Using compiled-in default.
          (WW) fglrx(0): MonitorLayout is no longer supported.
          (WW) fglrx(0): ***********************************
          (WW) fglrx(0): * DRI initialization disabled! *
          (WW) fglrx(0): * 2D acceleraton available (MMIO) *
          (WW) fglrx(0): * no 3D acceleration available *
          (WW) fglrx(0): ***********************************
          (WW) fglrx(1): ***********************************
          (WW) fglrx(1): * DRI initialization disabled! *
          (WW) fglrx(1): * 2D acceleraton available (MMIO) *
          (WW) fglrx(1): * no 3D acceleration available *
          (WW) fglrx(1): ***********************************
          (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

          Comment


          • #75
            vini,

            Do the drivers work if you use a simple xorg.conf with only a single head?

            Had you tried using aticonfig with an ATI Big Desktop to run both of your screens? If not, you may want to try that as it should work better in most situations.

            Originally posted by aticonfig --help
            2. Setting up big desktop to horizontal and set overlay on secondary display.
            aticonfig --dtop=horizontal --overlay-on=1
            Michael Larabel
            https://www.michaellarabel.com/

            Comment


            • #76
              Hi Michael,

              I think the only test that I didn't do was with a single head. I don't think it would work though, I know it worked before with dual head. I used to have FC5 and it was just fine but the ATI driver was a little older.

              I think I tried the big desktop sometime ago, it was a bit strange I think because I was as if the screen was one long screen. This is not quite what I want as I need the windows to behave based on the screen they are on.

              It is really strange as I have done everything that you recommended to people and some other things that I read on the net. The configuration looks good but it doesn't work at all with DRI. One question though, do I have to have the DRM module loaded to be able to use DRI?

              Thanks
              Vini


              Originally posted by Michael View Post
              vini,

              Do the drivers work if you use a simple xorg.conf with only a single head?

              Had you tried using aticonfig with an ATI Big Desktop to run both of your screens? If not, you may want to try that as it should work better in most situations.

              Comment


              • #77
                Trying a single head xorg.conf (backup your current config and then run aticonfig --initial) would be worth trying.

                Big Desktop with GNOME 2.16 or KDE 3.5.4 shouldn't cause issues with "long screens". I had used Big Desktop earlier this year for a few months.

                You shouldn't need to mess with DRM and the DRI setup for the drivers to work, or did you build the kernel yourself?
                Michael Larabel
                https://www.michaellarabel.com/

                Comment


                • #78
                  Ok I will try with single head to see what happens.

                  Do you think a Big desktop would be the same as far as the window manager goes? I my windows don't go crazy I think there is no problem in using it. Also, I was going to post this here as well but forgot, I haven't managed to get my card working with 1920x1200, it works only with 1600x1050. The screens do support the 1920x1200 but it falls back to 1600x1050. Any ideas why it isn't working with this resolution?

                  I haven't built the kernel myself, I it is the default (but latest) FC6 kernel. It was updated by yum. The reason why I asked that question about DRM is that the drm kernel modules is not being loaded and when I try to load it I get a message saying that "cannot allocate memory (or something like that)" does this modules have to be loaded? The fglxr modules is being loaded just in case you wondered.

                  THnaks
                  Vini

                  Originally posted by Michael View Post
                  Trying a single head xorg.conf (backup your current config and then run aticonfig --initial) would be worth trying.

                  Big Desktop with GNOME 2.16 or KDE 3.5.4 shouldn't cause issues with "long screens". I had used Big Desktop earlier this year for a few months.

                  You shouldn't need to mess with DRM and the DRI setup for the drivers to work, or did you build the kernel yourself?

                  Comment


                  • #79
                    Hello Vini,

                    it seems quite a few people are trying to get this solved. Here is what I did (After a few days of lots of linking and then starting from scratch):

                    When trying to build the ati.com ATI driver on FC6 , one MUST have installed:
                    1. development libraries packages
                    2. development tools packages
                    3. GNOME development packages
                    4. X development packages
                    5. Old Software development -> compat-libdistc++-33-*
                    6. qt-devel
                    7. rpm-build

                    Then it compiles fine, no problems with "cannot stat firecontrolxyz . ." etc. I do not know exactly what is being installed to prevent the "cannot stat ... " problem, but this way you can solve it. Afterwards, you remove 1.-4.,6. and 7.

                    Solution to persistent MESA GL renderer when installing the 8.31.5 driver from livna (as you apparently did)

                    yum install xorg-X11-drv-fglrx.i386

                    The corresponding libGL.so.1.2 from this package will be installed in /usr/lib/ati-fglrx/ . Of course, the existing ligGL.so.1.2 provided by MESA, which resides in /usr/lib, will be found in the path first. So rename /usr/lib/libGL.so.1.2 to /usr/lib/ligGL.so.1.2.MESA and copy /usr/lib/ati-fglrx/ligGL.so.1.2 to /usr/lib. It did the trick. After rebooting (NOT only restarting X, funny, that . . ) I got the following on fglrxinfo:

                    display: :0.0 screen: 0
                    OpenGL vendor string: ATI Technologies Inc.
                    OpenGL renderer string: MOBILITY RADEON X300 Generic
                    OpenGL version string: 2.0.6174 (8.31.5)

                    So there you are

                    Regards,

                    J.

                    Comment


                    • #80
                      Big Desktop shouldn't give window manager problems.

                      In regards to your resolution issues, you could manually specify the higher resolution in your xorg.conf. The drivers likely aren't pulling all of the EDID information.
                      Michael Larabel
                      https://www.michaellarabel.com/

                      Comment

                      Working...
                      X