Announcement

Collapse
No announcement yet.

Updated and Optimized Ubuntu Free Graphics Drivers

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

  • Originally posted by thehowler View Post

    Apologies - the same issue that MahdiBaghbani has reported is still occurring
    I take it back. It is now confirmed as working. Humblest apologies for the confusion!

    Comment


    • Hello! After last update (16 April), I get broken graphics.
      Code:
      [  3838.129] (II) AMDGPU(0): Setting screen physical size to 1185 x 381
      [  3838.144] (EE)  
      [  3838.144] (EE) Backtrace:
      [  3838.146] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x56506afe95ac]
      [  3838.146] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f0e272a741f]
      [  3838.146] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f0e270e418b]
      [  3838.146] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f0e270c3859]
      [  3838.147] (EE) unw_get_proc_name failed: no unwind info found [-10]
      [  3838.147] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7f0e270c371a]
      [  3838.147] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) [0x7f0e270d4f36]
      [  3838.147] (EE) unw_get_proc_name failed: no unwind info found [-10]
      [  3838.147] (EE) 6: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7f0e26d5d2d0]
      [  3838.147] (EE) unw_get_proc_name failed: no unwind info found [-10]
      [  3838.147] (EE) 7: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7f0e26d5d4d0]
      [  3838.147] (EE) unw_get_proc_name failed: no unwind info found [-10]
      [  3838.147] (EE) 8: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7f0e26d6b750]
      [  3838.147] (EE) unw_get_proc_name failed: no unwind info found [-10]
      [  3838.147] (EE) 9: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7f0e26d6e630]
      [  3838.148] (EE) 10: /usr/lib/xorg/Xorg (MapWindow+0x20c) [0x56506aeb40fc]
      [  3838.148] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x355) [0x56506ae8bf65]
      [  3838.148] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f0e270c50b3]
      [  3838.148] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2e) [0x56506ae75a2e]
      [  3838.148] (EE)  
      [  3838.148] (EE)  
      Fatal server error:
      [  3838.148] (EE) Caught signal 6 (Aborted). Server aborting
      [  3838.148] (EE)  
      [  3838.148] (EE)
      I use ubuntu 20.04 (Kde neon) and gpu amd rx 580.
      How can I fix this problem?

      Comment


      • Hi,
        just updating oibaf mesa driver daily wanting to test new zink extensions/features but seems for a few days mesa builds are stuck at Mesa commit
        eb6d99014f027c3325024d6f3482f6427f254f13 any reason? if I remember correctly oibaf builds were using commits at most one or two hours ago from mesa master..
        thanks.

        Comment


        • Originally posted by oscar View Post
          Hi,
          just updating oibaf mesa driver daily wanting to test new zink extensions/features but seems for a few days mesa builds are stuck at Mesa commit
          eb6d99014f027c3325024d6f3482f6427f254f13 any reason? if I remember correctly oibaf builds were using commits at most one or two hours ago from mesa master..
          thanks.
          Yeah, currently it is blocked waiting for this patch that breaks armhf builds: https://gitlab.freedesktop.org/mesa/...requests/10409
          Mesa compile is broken since 2 weeks on armhf!
          I know I could just apply it as a patch, but I am currently busy right now, hopefully they'll merge it soon and I'll unblock updating to newer revision.

          Comment


          • Originally posted by oibaf View Post

            Yeah, currently it is blocked waiting for this patch that breaks armhf builds: https://gitlab.freedesktop.org/mesa/...requests/10409
            Mesa compile is broken since 2 weeks on armhf!
            I know I could just apply it as a patch, but I am currently busy right now, hopefully they'll merge it soon and I'll unblock updating to newer revision.
            The packages are now up to date.

            Comment


            • forgot to say thanks oibaf!

              Comment


              • Recent updates to the PPA include enabling Apple M1 driver, venus VirtIO Vulkan driver and also using newer libclc from llvm-12 (rather than old stand alone library).

                Comment


                • Hi oibaf, thanks for maintaining this PPA! I use it frequently and with great effect.

                  Are the Vulkan layers intentionally disabled in the PPA? The layer build flags seem malformed; I don't know if that's intentional or not. I didn't see anything relevant in a forum search. The following changes allow me to build and package the layers locally:

                  Code:
                  $ diff -r mesa-orig/mesa-21.2~git2105140600.d1e30c~oibaf~g/debian/mesa-vulkan-drivers.install mesa-mod/mesa-21.2~git2105140600.d1e30c~oibaf~g/debian/mesa-vulkan-drivers.install
                  1,2c1,2
                  < #usr/bin/mesa-overlay-control.py
                  < #usr/share/vulkan/explicit_layer.d/*.json
                  ---
                  > usr/bin/mesa-overlay-control.py
                  > usr/share/vulkan/explicit_layer.d/*.json
                  4c4
                  < #usr/share/vulkan/implicit_layer.d/*.json
                  ---
                  > usr/share/vulkan/implicit_layer.d/*.json
                  6,7c6,7
                  < #usr/lib/*/libVkLayer_MESA_device_select.so
                  < #usr/lib/*/libVkLayer_MESA_overlay.so
                  ---
                  > usr/lib/*/libVkLayer_MESA_device_select.so
                  > usr/lib/*/libVkLayer_MESA_overlay.so
                  diff -r mesa-orig/mesa-21.2~git2105140600.d1e30c~oibaf~g/debian/rules mesa-mod/mesa-21.2~git2105140600.d1e30c~oibaf~g/debian/rules
                  137c137
                  <       confflags_VULKAN += -Dvulkan-device-select-layer=true
                  ---
                  > #     confflags_VULKAN += -Dvulkan-device-select-layer=true
                  139c139
                  <       confflags_VULKAN += -Dvulkan-overlays="['device-select','intel-nullhw','overlay']"
                  ---
                  >       confflags_VULKAN += -Dvulkan-layers=device-select,intel-nullhw,overlay
                  If there's no technical limitation here, it'd be great to see these layers re-enabled. The FPS logging capabilities of the overlay layer are particularly useful.

                  Comment


                  • Originally posted by cqcallaw View Post
                    Hi oibaf, thanks for maintaining this PPA! I use it frequently and with great effect.

                    Are the Vulkan layers intentionally disabled in the PPA? The layer build flags seem malformed; I don't know if that's intentional or not. I didn't see anything relevant in a forum search. The following changes allow me to build and package the layers locally:

                    Code:
                    ...
                    If there's no technical limitation here, it'd be great to see these layers re-enabled. The FPS logging capabilities of the overlay layer are particularly useful.
                    Thanks for the hint, it should be properly fixed now.

                    Comment

                    Working...
                    X