Announcement

Collapse
No announcement yet.

ATI 8.28.8 FC6 2.6.20 driver install

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

  • ATI 8.28.8 FC6 2.6.20 driver install

    Hi Everyone
    I have tried not to make this post. I have a Dell C600 (well actually 12 of them) one with FC6 2.6.20-1.2952.fc6 as an OS and ATI Technologies Inc Rage Mobility M3 AGP 2x (rev 02) for video hardware on all 12. I would like to use 2.6.20 on all (FC5 is just a little dated). Firefox and Google earth are just to slow with the open drivers. As far as I can see that leaves 8.28.8.

    I read all the posts and installed all the packages. I make all the simbolic links and tried both the direct package install and the –buildpkg option. But I must have forgotten something. I just can't find it.

    The output from the /use/share/fglrx/fglrx-install.log

    [root@jimalap fglrx]# more 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.
    ATI module generator V 2.0
    ==========================
    initializing...
    cleaning...
    patching 'highmem.h'...
    assuming new VMA API since we do have kernel 2.6.x...
    Assuming default VMAP API
    doing Makefile based build for kernel 2.6.x and higher
    make -C /lib/modules/2.6.20-1.2952.fc6/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
    make[1]: Entering directory `/usr/src/kernels/2.6.20-1.2952.fc6-i686'
    CC [M] /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:180: error: expected declaration specifiers or ‘...’ before ‘mlock’
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:180: error: expected declaration specifiers or ‘...’ before ‘addr’
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:180: error: expected declaration specifiers or ‘...’ before ‘len’
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:182: warning: return type defaults to ‘int’
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function ‘_syscall2’:
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:182: error: expected declaration specifiers before ‘_syscall2’
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:215: error: parameter ‘__ke_debuglevel’ is initialized
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:216: error: parameter ‘__ke_moduleflags’ is initialized
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:219: error: storage class specified for parameter ‘__mod_author219’
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:219: error: parameter ‘__mod_author219’ is initialized
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:219: warning: ‘__used__’ attribute ignored
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:219: error: section attribute not allowed for ‘__mod_author219’
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:220: error: storage class specified for parameter ‘__mod_...

    And The End Of The Install Log After Many Err And Warning Messages

    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:180: error: parameter name omitted
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:180: error: parameter name omitted
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:180: error: parameter name omitted
    /lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4049: error: expected ‘{’ at end of input
    make[2]: *** [/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o] Error 1
    make[1]: *** [_module_/lib/modules/fglrx/build_mod/2.6.x] Error 2
    make[1]: Leaving directory `/usr/src/kernels/2.6.20-1.2952.fc6-i686'
    make: *** [kmod_build] Error 2
    build failed with return value 2
    [Error] Kernel Module : Failed to compile kernel module - please consult readme.

    It looks like firegl_public.o is missing something. I am at the end of what my meager coding abilities allow. If someone could point me in the right direction. I would much applicate it.

    Thanks

  • #2
    fglrx 8.28.8 is ancient and is not supposed to work with 2.6.20.

    Here's a patch: http://aur.archlinux.org/packages/at...l-2.6.20.patch
    I didn't test it though.

    fglrx will do you no good with "rage mobility m3" (it's ancient!). That chipset is not supported by fglrx, but r128 should work with it

    Also,
    I read all the posts and installed all the packages
    no idea what you read. A little search shows http://www.phoronix.net/forums/showthread.php?t=342
    Last edited by Xipeos; 06-16-2007, 02:54 PM.

    Comment


    • #3
      Originally posted by Xipeos View Post
      fglrx 8.28.8 is ancient and is not supposed to work with 2.6.20.

      Here's a patch: http://aur.archlinux.org/packages/at...l-2.6.20.patch
      I didn't test it though.

      fglrx will do you no good with "rage mobility m3" (it's ancient!). That chipset is not supported by fglrx, but r128 should work with it

      Also,

      no idea what you read. A little search shows http://www.phoronix.net/forums/showthread.php?t=342
      We are running FC5 with fglrx and it work great for what we want. r128 is to slow. So you will know next time:

      http://www.fedoraforum.org/forum/sho...d.php?t=144681

      Thanks for trying.

      Comment


      • #4
        Originally posted by OldMarine View Post
        We are running FC5 with fglrx and it work great for what we want. r128 is to slow. So you will know next time:

        http://www.fedoraforum.org/forum/sho...d.php?t=144681

        Thanks for trying.
        You obviously missed the part on how fglrx doesn't work with rage 128. It never did (well...at least as far back as the rss feed goes 8.18.8).

        And how does it work great when you complained in the previous post that it doesn't even compile?! fglrx 8.28 was released ~7 months before linux 2.6.20 so there's no way you can make it work without modifying it (like using the patch I linked to).

        r128 is to slow
        Rage 128 first appeared in 1998, how can you expect any decent performance for modern-day programs?! Try lowering those settings or beowulf all those ancient Dells.

        Right...


        LATER EDIT: hey...what do you know? this has been "discussed" before. If you don't believe me then maybe you'll believe Michael
        Originally posted by Michael
        The Livna / official fglrx drivers will not work with the ATI Rage Mobility M3. Your only choice is to use the open-source Xorg drivers.
        from here

        Turns out there was a fglrx version that worked with rage though. And that guy was a bit more realist than you are
        Telling me not to expect too much from a Rage 128 is um... how shall I say... pointless.
        Amazing what a bit of search reveals
        Last edited by Xipeos; 06-16-2007, 07:55 PM. Reason: Update

        Comment


        • #5
          I realize you are confused Xipeos. I will try to explain.

          I realize you are confused Xipeos. I will try to explain.

          I work in the IT dept. for a SMB. We have 12 Dell 600 laptops we bought in late 2002 or early 2003. The boxes came with ATI graphic cards. ATI at the time was making noises like they would support Linux. That is one of the reasons that we bought them. They(ATI) were putting together a program to give the Linux driver coders the specifications for their cards. That the coders need for the open source drivers. We were running RH 7.1 WS and 9.0 EP at the time I think. I remember downloading drivers for the video but I just can't think what they were. I know we used Xfree86 ver 4 something because of the M3 ATI video cards in the laptops. Anyway we put 9.0 on the first two laptops and used NIS and NFS for connective to the Suns in the engineering dept. and the AS-400 in accounting. We were at the time starting to change the entire company over to Linux for internal use. XP at the time had not been released very long and there were some real problems. This was pre SP1 or maybe a little after. What can I say Star Office was really cheap $ 75.00 per seat when compared to $ 400.00 for MS Office 2000 at the time. Well back to the point. We soon upgraded to FC3 and a 2.4 something kernel and then to FC4 after the 2.6 kernel was released. We were behind the normal Fedora upgrade cycle but we liked that. That was the first time I remember the fglrx drivers. I think they were called fglix maybe. I remember that we tried the ATI drivers but the DRI drivers that came with FC4 2.6.11 were faster. It was mid 2005 I think. If you want to know more you can Google it. When FC5 was released we started taking notice. Red Hat had split and taken RHN with it. Yum, Open Office 2.0 and the ATI driver looked awful good. It was the GL 3D acceleration in the the driver that really made the difference. We tried the ATI driver on the Rage 128 M3 and it had some problems but it made Netscape's browsers a real pleasure. That was a 2.6.11 kernel. When everyone was back after the new year (1/2006) we downloaded FC5 2.6.15 kernel and could not install the ATI drivers because we had to wait. Some problem Red Hat had with external drivers that were not open source. In March we got the 2.6.16 kernel and ATI 8.23.7. Big difference we are running 8.27 now and they beat the open source driver enough that Google Earth is very usable for the sales dept. salesmen on the old laptops.

          What happen. Last year ATI dropped support for anything that was older than about 2 years in their driver. So 8.28.8 is the last ATI driver with support for the Rage 128 M3 in the Dell Dimensions and the s video port will not work on that rev. That is why we went with the 2.6.20 kernel and the 2.28.8 driver. We wanted to get FC6 but not lose the ATI driver acceleration for the old M3s.

          I hope this will clear up things for you. Now does anyone know what I did wrong with the 2.28.8 build? After all the laptops are only 4 years old and we don't use them for “ beowulf “.

          Edit:A little after thought. Anyone you have every heard say they wish Linux could be accepted by the business world. Well this is what it looks like. Doing a job. Not maybe state of the art but getting the job done. The laptops are not game machines. The difference in performance between Firefox using the open source drivers and the ATI drivers will not mean much game wise. Just use it everyday for Open Office or Firefox then you'll see the big difference.
          Last edited by OldMarine; 06-17-2007, 10:42 AM. Reason: bad ver. # poor grammer, a passing thought

          Comment


          • #6
            Originally posted by OldMarine View Post
            I work in the IT dept. for a SMB. We have 12 Dell 600 laptops we bought in late 2002 or early 2003. The boxes came with ATI graphic cards. ATI at the time was making noises like they would support Linux. That is one of the reasons that we bought them. They(ATI) were putting together a program to give the Linux driver coders the specifications for their cards. That the coders need for the open source drivers. We were running RH 7.1 WS and 9.0 EP at the time I think. I remember downloading drivers for the video but I just can't think what they were. I know we used Xfree86 ver 4 something because of the M3 ATI video cards in the laptops. Anyway we put 9.0 on the first two laptops and used NIS and NFS for connective to the Suns in the engineering dept. and the AS-400 in accounting. We were at the time starting to change the entire company over to Linux for internal use. XP at the time had not been released very long and there were some real problems. This was pre SP1 or maybe a little after. What can I say Star Office was really cheap $ 75.00 per seat when compared to $ 400.00 for MS Office 2000 at the time. Well back to the point. We soon upgraded to FC3 and a 2.4 something kernel and then to FC4 after the 2.6 kernel was released. We were behind the normal Fedora upgrade cycle but we liked that. That was the first time I remember the fglrx drivers. I think they were called fglix maybe. I remember that we tried the ATI drivers but the DRI drivers that came with FC4 2.6.11 were faster. It was mid 2005 I think. If you want to know more you can Google it. When FC5 was released we started taking notice. Red Hat had split and taken RHN with it. Yum, Open Office 2.0 and the ATI driver looked awful good. It was the GL 3D acceleration in the the driver that really made the difference. We tried the ATI driver on the Rage 128 M3 and it had some problems but it made Netscape's browsers a real pleasure. That was a 2.6.11 kernel. When everyone was back after the new year (1/2006) we downloaded FC5 2.6.15 kernel and could not install the ATI drivers because we had to wait. Some problem Red Hat had with external drivers that were not open source. In March we got the 2.6.16 kernel and ATI 8.23.7. Big difference we are running 8.27 now and they beat the open source driver enough that Google Earth is very usable for the sales dept. salesmen on the old laptops.
            How interesting...

            What happen. Last year ATI dropped support for anything that was older than about 2 years in their driver. So 8.28.8 is the last ATI driver with support for the Rage 128 M3
            Partially false. 8.28.8 was the last to support newer r200. Your rage 128 is r100 and at least 3 years older that those 9000s (again, rage 128 came out at the end of 1998)

            Like I said, as far as the RSS feed goes (8.18.8 - that is ~november 2005) fglrx doesn't support rage 128.

            Now does anyone know what I did wrong with the 2.28.8 build?
            I told you you...old marine!! That driver is too old for the kernel that you have. Use the patch that I linked to http://aur.archlinux.org/packages/at...l-2.6.20.patch

            Calm your rage

            Comment


            • #7
              Something is wrong I have laptops with FC5 and a video driver from livna repo named kmod-fglrx. That much I know. The laptops are at work. Let's put this off till tomorrow so I am not working from memory for the numbers. I really need to get this solved. Thanks till tomorrow.


              Edit: P.S. I am mad at ATI. Please don't think it's you. I know you are just trying to help.
              Last edited by OldMarine; 06-17-2007, 01:09 PM. Reason: Little PS

              Comment


              • #8
                I concur with Xipeos, and I seriously doubt ATI fglrx 8.28.8 has the support for Rage128 series graphic cards.

                As far as I know, if I am going to configure a Rage128, I would not be using driver from ATI. I would use the "r128" driver from Xorg. For DRI, I would download the latest drm from http://dri.freedesktop.org/wiki/Download

                Comment


                • #9
                  Originally posted by lenrek View Post
                  I concur with Xipeos, and I seriously doubt ATI fglrx 8.28.8 has the support for Rage128 series graphic cards.

                  As far as I know, if I am going to configure a Rage128, I would not be using driver from ATI. I would use the "r128" driver from Xorg. For DRI, I would download the latest drm from http://dri.freedesktop.org/wiki/Download
                  8.28.8 does NOT support the Rage128.
                  Michael Larabel
                  http://www.michaellarabel.com/

                  Comment


                  • #10
                    I know what is going on now. We have:

                    2 Dell C600 with Rage 128 M3 video The First We bought
                    2 Dell C610 with M6P video The Next order
                    8 Dell C610s with M9+ video. The Last 4 orders

                    No wonder things are confused. We bought these over a year or a year and a half. The 610 M9s have kmod-fglrx-8.28.8-1.2.6.17_2174_FC5 for the driver. The 2 C600s with the M3 and the 2 C610s with M6Ps have the ATI open source r128 driver. I know I knew that. Some how I made a mistake and thought they all were M3 with the ATI 8.28.8 driver. Next time maybe I'll listen. I have been keeper of this zoo to long.

                    Well that solves part of the problem. The M3s and M6Ps will run the same R128 driver when we upgrade to FC6. Unless one of you boys have another idea. The C610s with the ATI 9200s I need to install the r128 driver on one and see if there is that much difference between fglrx and R128. No need to mess with 8.28.8 unless necessary.

                    Xipeos I thought they were all a like. But as the top of the Dell Dimenstion line changed they sold us a better box. I should have known.
                    Thanks Boys. Maybe I can help you all next time.

                    Comment


                    • #11
                      One last question. I noticed on the boxes with the r128 driver that the direct render was off. Does anyone think it is worth the trouble to find out why and turn in on? The boxes are used for Open Office and Web stuff(Firefox) mostly.

                      Comment


                      • #12
                        You may want to read up on DRI troubleshooting for OpenSource driver:

                        http://dri.freedesktop.org/wiki/DriTroubleshooting

                        I used to be using a Rage128 card, but that was really quite sometime ago. So, I can't really remember how I got it working. However, as much as I can remember, it was not that difficult. I just need load the proper kernel module and make sure X is configure with proper DRI setting.

                        Comment


                        • #13
                          Thanks lenrek. That was very helpful.

                          I took one of the oldest laptops with the M3 video and loaded FC6 2.6.20-1.2952.fc6 i686 and the open source ati driver. Works Great. I turned on direct rendering and glxgears went from 120 fps to 530 fps. I think this is going to work well.

                          I will try fglrx 8.28.8 with the ati 9200 and FC6 as time permits.

                          Thanks everyone for a job well done and Xipecso for putting up with a mad Old Marine. I have post the xorg.conf if anyone needs it.
                          file:///u/usr/xorg.conf

                          # Xorg configuration created by system-config-display

                          Section "ServerLayout"
                          Identifier "single head configuration"
                          Screen "Screen0"
                          InputDevice "Keyboard0" "CoreKeyboard"
                          Option "AIGLX" "true"
                          EndSection

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

                          Section "Monitor"

                          ### Comment all HorizSync and VertSync values to use DDC:
                          ### Comment all HorizSync and VertSync values to use DDC:
                          Identifier "Monitor0"
                          ModelName "LCD Panel 1024x768"
                          ### Comment all HorizSync and VertSync values to use DDC:
                          HorizSync 31.5 - 48.5
                          VertRefresh 40.0 - 70.0
                          Option "dpms"
                          EndSection

                          Section "Device"
                          Identifier "Videocard0"
                          Driver "r128"
                          Option "Accel" "true"
                          Option "AGPMode2x"
                          Option "AGPMode" "2"
                          Option "XAANoOffscreenPixmaps" "true"
                          EndSection

                          Section "Module"
                          load "dri"
                          load "glx"
                          EndSection

                          Section "Screen"
                          Identifier "Screen0"
                          Device "Videocard0"
                          Monitor "Monitor0"
                          DefaultDepth 16
                          SubSection "Display"
                          Viewport 0 0
                          Depth 16
                          Modes "1024x768" "800x600" "640x480"
                          EndSubSection
                          EndSection

                          Section "DRI"
                          Mode 0666
                          EndSection

                          I take it back. Direct Rendering does not work. the glxgears speed increase is real. Direct Rendering is not working.
                          Last edited by OldMarine; 06-18-2007, 07:44 PM. Reason: Up date at end

                          Comment


                          • #14
                            You may want to do: "grep WW /var/log/Xorg.0.log" and see any warning message in the system. Maybe you can get more clues on why your card is not working.

                            By the way, did you do 'dmesg | grep drm'? Is DRM for Rage128 loaded properly?

                            Comment


                            • #15
                              I don't see anything here:

                              [root@jimalap log]# grep WW Xorg.0.log
                              (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
                              (WW) The core pointer device wasn't specified explicitly in the layout.
                              (WW) No FontPath specified. Using compiled-in default.
                              (WW) R128(0): Option "DRI" is not used
                              (WW) R128(0): Option "AGPMode2x" is not used
                              (WW) R128(0): Option "AddARGBGLXVisuals" is not used
                              (WW) AIGLX: 3D driver claims to not support visual 0x23

                              Some stuff removed.

                              (WW) AIGLX: 3D driver claims to not support visual 0x32
                              (WW) <default pointer>: No Device specified, looking for one...

                              As a side light, boy this would not be much of a compiz box. Ok back to the subject. Here is the dmesg.

                              [root@jimalap log]# dmesg |grep drm
                              [drm] Initialized drm 1.1.0 20060810
                              [drm] Initialized r128 2.5.0 20030725 on minor 0
                              [root@jimalap log]#

                              I know it's not a good benchmark but the incease in glxgears may have been from the xorg.conf changes in the Display section.

                              SubSection "Display"
                              Viewport 0 0
                              Depth 16 <--------------------------------- was 24
                              Modes "1024x768" "800x600" "640x480"
                              EndSubSection

                              I bet that made it faster. I left out a lot of things in the Devices section also. There is the old xorg.conf:

                              [root@jimalap X11]# cat xorg.old
                              # Xorg configuration created by system-config-display

                              Section "ServerLayout"
                              Identifier "single head configuration"
                              Screen "Screen0"
                              InputDevice "Keyboard0" "CoreKeyboard"
                              Option "AIGLX" "true"
                              EndSection

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

                              Section "Monitor"

                              ### Comment all HorizSync and VertSync values to use DDC:
                              ### Comment all HorizSync and VertSync values to use DDC:
                              Identifier "Monitor0"
                              ModelName "LCD Panel 1024x768"
                              ### Comment all HorizSync and VertSync values to use DDC:
                              HorizSync 31.5 - 48.5
                              VertRefresh 40.0 - 70.0
                              Option "dpms"
                              EndSection

                              Section "Device"
                              Identifier "Videocard0"
                              Driver "r128"
                              Option "Accel" "true"
                              Option "AGPMode2x"
                              Option "AGPMode" "2"
                              Option "XAANoOffscreenPixmaps" "true"
                              EndSection

                              Section "Module"
                              load "dri"
                              load "glx"
                              load "GLcore"
                              load "i2c"
                              load "bitmap"
                              load "dbe"
                              load "ddc"
                              load "extmod"
                              load "freetype"
                              load "int10"
                              load "type1"
                              load "vbe"
                              load "record"
                              load "v41"
                              load "pex5"
                              load "xie"
                              EndSection

                              Section "Screen"
                              Identifier "Screen0"
                              Device "Videocard0"
                              Monitor "Monitor0"
                              DefaultDepth 24
                              SubSection "Display"
                              Viewport 0 0
                              Depth 16
                              Modes "1024x768" "800x600" "640x480"
                              EndSubSection
                              EndSection

                              Section "DRI"
                              Mode 0666
                              EndSection

                              This is the new file.

                              [root@jimalap X11]# cat xorg.conf
                              # Xorg configuration created by system-config-display

                              Section "ServerLayout"
                              Identifier "single head configuration"
                              Screen "Screen0"
                              InputDevice "Keyboard0" "CoreKeyboard"
                              Option "AIGLX" "true"
                              EndSection

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

                              Section "Monitor"

                              ### Comment all HorizSync and VertSync values to use DDC:
                              ### Comment all HorizSync and VertSync values to use DDC:
                              Identifier "Monitor0"
                              ModelName "LCD Panel 1024x768"
                              ### Comment all HorizSync and VertSync values to use DDC:
                              HorizSync 31.5 - 48.5
                              VertRefresh 40.0 - 70.0
                              Option "dpms"
                              EndSection

                              Section "Device"
                              Identifier "Videocard0"
                              Driver "r128"
                              Option "DRI" "true"
                              Option "Accel" "true"
                              Option "AGPMode2x"
                              Option "AGPMode" "2"
                              Option "AddARGBGLXVisuals" "true"
                              Option "XAANoOffscreenPixmaps" "true"
                              EndSection

                              Section "Module"
                              load "dri"
                              load "glx"
                              load "dbe"
                              EndSection

                              Section "Extensions"
                              Option "Composite" "Enable"
                              EndSection

                              Section "Screen"
                              Identifier "Screen0"
                              Device "Videocard0"
                              Monitor "Monitor0"
                              DefaultDepth 16
                              Option "AddARGBGLXVisuals" "true"
                              SubSection "Display"
                              Viewport 0 0
                              Depth 16
                              Modes "1024x768" "800x600" "640x480"
                              EndSubSection
                              EndSection

                              Section "DRI"
                              Group 0
                              Mode 0666
                              EndSection

                              I know dbe would get called but just to be sure. This is the glxinfo:

                              [root@jimalap X11]# glxinfo
                              name of display: :0.0
                              display: :0 screen: 0
                              direct rendering: No
                              server glx vendor string: SGI
                              server glx version string: 1.2


                              This is the tail of the Xorg.0.log file. As you can see it thought that Direct Rendering was working. I thought after seeing this it was working. See the post above. Here is the file tail.

                              (II) R128(0): Largest offscreen area available: 1024 x 763
                              (**) Option "dpms"
                              (**) R128(0): DPMS enabled
                              (WW) R128(0): Option "DRI" is not used
                              (WW) R128(0): Option "AGPMode2x" is not used
                              (WW) R128(0): Option "AddARGBGLXVisuals" is not used
                              (II) R128(0): X context handle = 0x1
                              (II) R128(0): [drm] installed DRM signal handler
                              (II) R128(0): [DRI] installation complete
                              (II) R128(0): [drm] Added 128 16384 byte vertex/indirect buffers
                              (II) R128(0): [drm] Mapped 128 vertex/indirect buffers
                              (II) R128(0): [drm] dma control initialized, using IRQ 11
                              (II) R128(0): Direct rendering enabled <----------------------------
                              (==) RandR enabled



                              Strange. Did it start then crash? I can't find a log that says that.

                              Comment

                              Working...
                              X