Announcement

Collapse
No announcement yet.

KMS + Radeon quick mini guide

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

  • #31
    No I use 2.6.31-16, the one which has been provided as a dependancy for everything that was updated from xorg-edgers.

    Comment


    • #32
      Originally posted by netkas View Post
      >radeon have DRI2 fglrx only dri..

      you can't really compare them.
      be sure i can!

      Comment


      • #33
        Originally posted by bridgman View Post
        Right. The fglrx driver does not use the DRI2 protocol but provides most of the same benefits, including Redirected Direct Rendering.
        FGLRX = Dinosaur

        OK ease DRI2 from the must have list.. add KMS and EXA/UAX

        o yes? fglrx can't ? i'm so so soooo sorry---



        i come to the "Burial" of the FGLRX ---->RIP!

        Comment


        • #34
          Originally posted by Guilo View Post
          No I use 2.6.31-16, the one which has been provided as a dependancy for everything that was updated from xorg-edgers.
          the xorg-edgers need kernel 2.6.32!

          Comment


          • #35
            Here is tarball with few patches:

            first one - all drm patches which was merged yet to upcoming 2.6.33, including irq support (and vblank).

            second - hdmi audio support on some chips(these -rdev->family >= CHIP_R600 || rdev->family == CHIP_RS600 || rdev->family == CHIP_RS690 || rdev->family == CHIP_RS740), apply only after previous one.

            and two firmware fiels needed for irq, they go to /lib/firmware/<kernel version>/radeon/

            Apply to 2.6.32 and disable intel's drm module in config.

            http://files.netkas.org/drm_vsync_new.tar.bz2
            Last edited by netkas; 12-11-2009, 12:06 PM.

            Comment


            • #36
              I am having an issue getting my display not garbled in xorg.. I have been using radeon (non-KMS) for a while..

              I boot with 2 different kernels with 2 different firmware requests, but with same end result garbled screen..

              I am a Karmic user, using edgers PPA for a while, but decided to try KMS today and see how it went..

              2.6.32-rc8:
              [ 13.452210] [drm] radeon kernel modesetting enabled.
              [ 13.452474] radeon 0000:01:00.0: setting latency timer to 64
              [ 13.455472] [drm] radeon: Initializing kernel modesetting.
              [ 13.456882] [drm] radeon: 256M of VRAM memory ready
              [ 13.456884] [drm] radeon: 512M of GTT memory ready.
              [ 13.456935] platform radeon_cp.0: firmware: requesting radeon/RV635_pfp.bin
              [ 13.492619] platform radeon_cp.0: firmware: requesting radeon/RV635_me.bin
              [ 13.538533] [drm] radeon: ib pool ready.
              [ 13.539832] [drm] Radeon Display Connectors
              [ 14.153821] fb0: radeondrmfb frame buffer device
              [ 14.153827] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0

              2.6.32-drm-next:
              [ 13.300536] [drm] radeon kernel modesetting enabled.
              [ 13.300588] radeon 0000:01:00.0: setting latency timer to 64
              [ 13.303803] [drm] radeon: Initializing kernel modesetting.
              [ 13.306165] [drm] radeon: 256M of VRAM memory ready
              [ 13.306166] [drm] radeon: 512M of GTT memory ready.
              [ 13.306226] radeon 0000:01:00.0: irq 32 for MSI/MSI-X
              [ 13.306231] [drm] radeon: using MSI.
              [ 13.306252] [drm] radeon: irq initialized.
              [ 13.306460] platform radeon_cp.0: firmware: requesting radeon/RV635_pfp.bin
              [ 13.349652] platform radeon_cp.0: firmware: requesting radeon/RV635_me.bin
              [ 13.366377] platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin
              [ 13.419284] [drm] radeon: ib pool ready.
              [ 13.420434] [drm] Radeon Display Connectors
              [ 14.035090] fb0: radeondrmfb frame buffer device
              [ 14.035099] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0

              I have a candy striped screen with either, and no errors in my log. I can switch to a VT at anytime, but login and shell is only visible if I *do not* log into gdm blindly.. after I log in blindly, my VTs go blank (even though I can still run commands in them)..

              Anyone else see this and know how to work around it? I read an old post about >256MB memory, but that was back in september, and it appears to be OK with my 512..

              Thanks,

              Greg

              Comment


              • #37
                I've found that Ubuntu's splash screen interferes somehow with kms. You may want to remove it from the grub boot line, if you haven't done so already.

                Comment


                • #38
                  Just got radeon up and running on my lenovo.
                  Two things happened :
                  First I was full of joy, I got my 26" screen capable of 1920x1200 and still have good performances using coompiz.
                  Next I decided to switch from VGA to DVI and then the screen in completely messed up. Only if I start in clone mode (lenovo t400 is 1440x900) I get a decend image.
                  How should I investigate more the issue ?
                  Packages come from drm-next kernel on the mainline ppa + xorg-edgers and kms off

                  Kudos to devs and AMD themselves for providing support for decent poen source drivers.
                  Really delighted,
                  Last edited by lucky_; 12-11-2009, 06:44 PM.

                  Comment


                  • #39
                    *EDIT*

                    I finally got it working by restarting/disabling gdm like another thread had posted. It is extremely slow though.

                    Are there any tips or tricks to speed it up any? I do unfortunately have one of those 6xx series RV635 cards (mx86) or whatever the OEM shared memory jobs they sold to dell is...

                    I just want tear free full screen video

                    It is much better than it was 6 months ago!

                    Thanks

                    -----

                    Well, either the edgers packages are broken today, or my card is not gonna work...

                    Xorg log is telling me:

                    (II) [KMS] drm report modesetting isn't supported.
                    Package: xserver-xorg-video-ati
                    State: installed
                    Automatically installed: no
                    Version: 1:6.12.99+git20091210.0e5c9d87-0ubuntu0tormod~karmic

                    Package: libdrm-radeon1
                    State: installed
                    Automatically installed: no
                    Version: 2.4.16+git20091209.edc77dd2-0ubuntu0sarvatt~karmic

                    Package: libdrm2
                    State: installed
                    Automatically installed: no
                    Version: 2.4.16+git20091209.edc77dd2-0ubuntu0sarvatt~karmic

                    Package: libgl1-mesa-dri
                    State: installed
                    Automatically installed: no
                    Version: 7.7.0~git20091210+mesa-7-7-branch.e624b77e-0ubuntu0tormod

                    (--) PCI:*(0:1:0:0) 1002:9593:1028:0272 ATI Technologies Inc Radeon Mobility HD 3670 rev 0, Mem @ 0xd0000000/268435456, 0xcfef0000/65536, I/O @ 0x00002000/256, BIOS @ 0x????????/131072

                    Anyone have any ideas?

                    Thanks,

                    Greg
                    Last edited by ghost_o; 12-12-2009, 01:54 AM.

                    Comment


                    • #40
                      Hm, this doesn't seem to work with r7xx cards yet...

                      I'm still getting "OpenGL renderer string: Software Rasterizer" from glxinfo.

                      But on the other hand, everything else seems to work fine, including XVideo playback. multi-screen desktop with xrandr, screen rotation and even desktop effects with AIGLX, although I'm apparently using software rendering...

                      However, if I don't configure KDE to use AIGLX, I get weird screen distortions in the form of white horizontal lines of maybe one or two pixels in height that go over about half the width of one of the screens and disappear after a split seconds. They usually appear when something is drawn somewhere on the screen, especially when its animated in some form, and the effect gets much worse when the system is under load. (Like compiling a kernel.)

                      Comment


                      • #41
                        guidow I had that to in the beginning, rebuild it again all in the correct order, and use a kernel that supports KMS

                        Comment


                        • #42
                          build order?

                          Originally posted by pheldens View Post
                          update
                          [CODE]
                          > cat builddri
                          #!/bin/sh

                          cd drm
                          make clean
                          git pull
                          ./configure --enable-radeon-experimental-api --disable-intel && make && make install
                          cd ..


                          cd xf86-video-ati
                          make clean
                          git pull
                          ./configure && make && make install
                          cd ..

                          cd mesa
                          make clean
                          git pull
                          i can't build in this order.
                          If you build xf86-video-ati before mesa, you fail with
                          missing GL headers.
                          If you don't fail, you compile against wrong/old mesa.

                          Comment


                          • #43
                            you need dri and drm support these have seperate includes (proto) and so does opengl, the xserver needs them too, starting with 6.7 you no longer need mesa to build xserver

                            Comment


                            • #44
                              Hello!

                              I have succeeded to install 3D with the radeon drivers, but not KMS.
                              My problem is that KMS wants to load the firmware file on boot time and doesn't have access to the file system yet.

                              So I am supposed to build the firmware into the kernel, but it doesn't seem to work.

                              What I did is:
                              Code:
                              CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
                              # CONFIG_DEVTMPFS is not set
                              CONFIG_STANDALONE=y
                              # CONFIG_PREVENT_FIRMWARE_BUILD is not set
                              CONFIG_FW_LOADER=y
                              CONFIG_FIRMWARE_IN_KERNEL=y
                              CONFIG_EXTRA_FIRMWARE="radeon/RV710_cp.bin radeon/RV710_me.bin radeon/RV710_pfp.bin RV710_cp.bin RV710_me.bin RV710_pfp.bin"
                              CONFIG_EXTRA_FIRMWARE_DIR="firmware"
                              I put the firmware files in both the firmware and a created firmware/radeon directories, just to make sure they are found.
                              After building, I see .gen.S and .gen.o files in those directories, so I assume they have been found and built in.

                              But after calling lilo and rebooting, it's the same thing all over. Booting stops when it tries to locate radeon/RV710_pfp.bin and continues after some time. After that: no KMS, no direct rendering, no XV.

                              Can anybody tell me what I did wrong?

                              Comment


                              • #45
                                Most likely it is loaded in the initrd and there the firmware was not copied.

                                Comment

                                Working...
                                X