Announcement

Collapse
No announcement yet.

Updated and Optimized Ubuntu Free Graphics Drivers

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

  • Hello, I have some problem with this ppa and ubuntu 18.04, 16.04 and 17.10, driver is nouveau on nv43(GeForce 6600), it can't work.
    glxinfo | grep OpenGL

    libGL error: failed to create dri screen
    libGL error: failed to load driver: nouveau
    OpenGL vendor string: VMware, Inc.
    OpenGL renderer string: llvmpipe (LLVM 6.0, 128 bits)
    OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.0-devel
    OpenGL core profile shading language version string: 3.30
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 3.1 Mesa 18.2.0-devel
    OpenGL shading language version string: 1.40
    OpenGL context flags: (none)
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.0-devel
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
    OpenGL ES profile extensions:

    dmesg | grep nouveau

    [ 1.946935] nouveau 0000:04:00.0: NVIDIA NV43 (043100a4)
    [ 1.978810] nouveau 0000:04:00.0: bios: version 05.43.02.88.00
    [ 1.979634] nouveau 0000:04:00.0: fb: 512 MiB DDR2
    [ 2.028805] nouveau 0000:04:00.0: DRM: VRAM: 508 MiB
    [ 2.028806] nouveau 0000:04:00.0: DRM: GART: 512 MiB
    [ 2.028810] nouveau 0000:04:00.0: DRM: TMDS table version 1.1
    [ 2.028812] nouveau 0000:04:00.0: DRM: DCB version 3.0
    [ 2.028815] nouveau 0000:04:00.0: DRM: DCB outp 00: 01000300 00000028
    [ 2.028818] nouveau 0000:04:00.0: DRM: DCB outp 01: 04011320 00000028
    [ 2.028820] nouveau 0000:04:00.0: DRM: DCB outp 02: 04011322 00000000
    [ 2.028822] nouveau 0000:04:00.0: DRM: DCB outp 03: 020223f1 00a0c030
    [ 2.028824] nouveau 0000:04:00.0: DRM: DCB conn 00: 0000
    [ 2.028825] nouveau 0000:04:00.0: DRM: DCB conn 01: 1130
    [ 2.028827] nouveau 0000:04:00.0: DRM: DCB conn 02: 0210
    [ 2.028828] nouveau 0000:04:00.0: DRM: DCB conn 03: 0211
    [ 2.028830] nouveau 0000:04:00.0: DRM: DCB conn 04: 0213
    [ 2.029095] nouveau 0000:04:00.0: DRM: Saving VGA fonts
    [ 2.082443] nouveau 0000:04:00.0: DRM: MM: using M2MF for buffer copies
    [ 2.082456] nouveau 0000:04:00.0: DRM: Setting dpms mode 3 on TV encoder (output 3)
    [ 2.220206] nouveau 0000:04:00.0: DRM: allocated 1024x768 fb: 0x9000, bo 000000003e1c19e6
    [ 2.249930] fbcon: nouveaufb (fb0) is primary device
    [ 2.520971] nouveau 0000:04:00.0: fb0: nouveaufb frame buffer device
    [ 2.536301] [drm] Initialized nouveau 1.3.1 20120801 for 0000:04:00.0 on minor 0
    [ 17.521310] nouveau 0000:04:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=nonewns=io+mem

    And I can't use any games. What is solution? I saw, that for nouveau i need to install libdrm mesa experimental package, but there is no such package in ppa. What should I do?

    Comment


    • After the last update (16.04), programs stopped working and an apt upgrade gave me this error message:

      The following packages have unmet dependencies:
      libwayland-egl1-mesa : Conflicts: libwayland-egl1

      This is the last entry in my history.log:

      Upgrade: libgles2-mesa:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libegl1-mesa-dev:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libglapi-mesa:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libglapi-mesa:i386 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), mesa-common-dev:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), google-chrome-stable:amd64 (67.0.3396.62-1, 67.0.3396.79-1), libxatracker2:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libegl1-mesa:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libgbm1:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), xserver-xorg-video-intel:amd64 (2:2.99.917+git1806010733.42c24d~oibaf~x, 2:2.99.917+git1806091935.3d3950~oibaf~x), libwayland-egl1-mesa:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libgles2-mesa-dev:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libgl1-mesa-dev:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libgl1-mesa-dri:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libgl1-mesa-dri:i386 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libosmesa6:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libosmesa6:i386 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), code:amd64 (1.23.1-1525968403, 1.24.0-1528306776), libgl1-mesa-glx:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libgl1-mesa-glx:i386 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), mesa-vdpau-drivers:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x)
      End-Date: 2018-06-11 09:16:11

      After removing the drivers via ppa-purge everything was working again.

      Comment


      • Originally posted by vindolin View Post
        After the last update (16.04), programs stopped working and an apt upgrade gave me this error message:

        The following packages have unmet dependencies:
        libwayland-egl1-mesa : Conflicts: libwayland-egl1

        This is the last entry in my history.log:

        Upgrade: libgles2-mesa:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libegl1-mesa-dev:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libglapi-mesa:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libglapi-mesa:i386 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), mesa-common-dev:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), google-chrome-stable:amd64 (67.0.3396.62-1, 67.0.3396.79-1), libxatracker2:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libegl1-mesa:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libgbm1:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), xserver-xorg-video-intel:amd64 (2:2.99.917+git1806010733.42c24d~oibaf~x, 2:2.99.917+git1806091935.3d3950~oibaf~x), libwayland-egl1-mesa:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libgles2-mesa-dev:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libgl1-mesa-dev:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libgl1-mesa-dri:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libgl1-mesa-dri:i386 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libosmesa6:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libosmesa6:i386 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), code:amd64 (1.23.1-1525968403, 1.24.0-1528306776), libgl1-mesa-glx:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), libgl1-mesa-glx:i386 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x), mesa-vdpau-drivers:amd64 (18.2~git1806060730.17a420~oibaf~x, 18.2~git1806110730.525cfe~oibaf~x)
        End-Date: 2018-06-11 09:16:11

        After removing the drivers via ppa-purge everything was working again.
        Mesa devs decided to go with libwayland-egl1 directly starting wayland 1.15 and ditch the in-house libwayland-egl1-mesa altogether.
        just remove libwayland-egl1-mesa and install libwayland-egl1, and everything will work again.

        Im waiting on debian to decide HOW they want to fix this packaging mess (redirect, overwrite, whatever).

        sorry for the inconvenience.

        BTW this is for padoka ppa but oibafs is suffering the same problem.

        Comment


        • I made some fixes, can you try it again?

          Comment


          • After the recent updates, my computer won't boot with the Oibaf drivers.

            XOrg crashes before the Window Manager loads but leaves no error that I can find.

            Any clue what could cause this and how to fix this? Do I need to update my kernel, or change my kernel modules. Do I need to switch to GDM from LightDM? (Mate Edition still uses LightDM)

            My system:
            Ubuntu MATE Edition 18.04
            Ryzen 1500X (4 Core / 8 Thread)
            16GB RAM
            AMD Rx480 (Asus Stryx 8GB OC)
            ASUS DVI Monitor (900x1600 resolution)
            Biostar X370GT5 Motherboard

            Comment


            • Ruediix
              I also have this problem. I tested both Padoka and Oibaf PPAs but my PC won't boot.

              My system:
              Ubuntu 18.04
              Ryzen 1600X
              16GB RAM
              Radeon RX580

              Comment


              • Same problem here in AMD┬« A10-7860k radeon r7 Kaveri.

                the system enter in a loop before reach the GDM screen to enter the user-password.

                The only solution was ppa-purge the ppa.

                Same with padoka ppa. (Actually worst, the ppa-purge gives a lot of errors with padoka's ppa)

                Any solution?
                ...

                Comment


                • It may be a driver bug, try reporting it there: https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa

                  Comment


                  • I had to remove the PPA to get my PC to boot too. This is with Linux Mint 18.3 and Ubuntu 18.04, with a Radeon HD 7850 and a Nvidia 7900 mobile GPU. Both won't boot after installing this PPA. This is really bad especially when I can install Nvidia 304 on Ubuntu 18.04.

                    Comment


                    • I have been reading that both oibaf and padoka are causing issues on the latest Ubuntus. I think it's due to a change in packaging policies or mismatched dependencies. Should be ironed out in a few days I guess.

                      Comment

                      Working...
                      X