ernstp / ppa-mesarc Goto Github PK

Hey!

I really love CoreCtrl and just installed 21.04 (wanna get that sweet Wayland working) - but no Corectrl :-| Tried with groovy resp. but missing some library that I cannot figure out how to install.

If you would like to add CoreCtrl for 21.04 I would be super grateful (and happy again).

Btw, are you Swedish? Anyway, greetings from Stockholm :-)

Looks like Ubuntu 20.04 and 19.04 have builds but not 18.04. Is there any chance this could be added?

I'm setting up a fresh Ubuntu 20.04 (focal) environment with deboostrap:

debootstrap --variant=minbase --arch=amd64 \
   --include="build-essential,dbus,binutils,lsb-release,wget,rsync,nano,software-properties-common" \
   "focal" "/tmp/testroot" ""http://ftp.fau.de/ubuntu"

Change sources.list to add updates/security/etc.:

deb http://ftp.fau.de/ubuntu focal main restricted universe
deb http://ftp.fau.de/ubuntu focal-updates main restricted universe
deb http://ftp.fau.de/ubuntu focal-security main restricted universe

Then I add the PPA:

add-apt-repository ppa:ernstp/mesarc

After that, e.g. apt install wireshark gives me:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 wireshark : Depends: wireshark-qt (= 3.2.3-1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Chasing down the dependency chain this is because libegl-mesa0 depends on libwayland-client0 (>= 1.20.0) but there only is 1.18.0-1ubuntu0.1 available.

I guess I can just look for a PPA with more recent builds of that, but the current situation is... not ideal? I get that this is for testing mostly, but if you have an existing setup with this PPA and do apt full-upgrade you're left without a working graphical session as far as I can tell.

So, not sure whether this is "works as expected" or an accident; I thought I'm gonna open an issue just in case.

Hello, please excuse me to open a ticket here, since the build run on 2020-05-01 I am only getting a black screen running Vulkan games. A ppa-purge, the standard ubuntu 20.04 mesa packages will let my games work again. I also tried the builds from today and the issue still persists.

I expect this to be a regression on the mesa git, so you probably are able to tell me that you are able to reproduce my issue but if it isnt and you are not able to reproduce it, please tell me that.

My system is on Ryzen 9-5900X & RX 6900XT

I had to downgrade to 22.2.2+git2210261923.159bc5b3dedkmesarc1 to fix the glitches.

These are the ones I downgraded:

libegl-mesa0/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 amd64 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
libegl-mesa0/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 i386 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
libgbm1/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 amd64 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
libgbm1/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 i386 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
libgl1-mesa-dri/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 amd64 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
libgl1-mesa-dri/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 i386 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
libglapi-mesa/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 amd64 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
libglapi-mesa/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 i386 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
libglx-mesa0/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 amd64 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
libglx-mesa0/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 i386 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
libosmesa6/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 amd64 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
libosmesa6/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 i386 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
libxatracker2/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 amd64 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
mesa-va-drivers/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 amd64 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
mesa-va-drivers/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 i386 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
mesa-vdpau-drivers/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 amd64 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
mesa-vulkan-drivers/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 amd64 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]
mesa-vulkan-drivers/kinetic 22.3.0~rc3+git2211171818.76e3938fec4~k~mesarc3 i386 [upgradable from: 22.2.2+git2210261923.159bc5b3ded~k~mesarc1]

Figure I should point it out

Hello. I hope this is the right place for this. I installed your branch for mesa to run corectrl (thanks for that, btw). However, since then, it seems every time I have an update that includes the mesa branch, Epic Games Store, when launching from Lutris, just has a black screen in it's window (still has min/max/close buttons) and the loading bar across the bottom (blue swirl line). If I reinstall Epic Games Store, it works again. Not a huge deal, since there's a workaround, but I'm willing to work with you to figure out what's wrong. Happened again this morning, so I grabbed the --upgradable and upgrade screen messages to see if this is even connected at all to this branch. What do you think?
epic-store.log

I noticed frequent GPU crashes with Hogwarts legacy, like this one I posted: ValveSoftware/Proton#6510 (comment)

Feb 12 16:31:46 Y4M1-II kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          RW: 0x0
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          MAPPING_ERROR: 0x0
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          WALKER_ERROR: 0x0
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          MORE_FAULTS: 0x0
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501430
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x0000800026c9c000 from client 0x1b (UTCL2)
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32788, for process HogwartsLegacy. pid 119019 thread HogwartsLegacy. pid 119144)

Is it possible?

Hi Ernst,

I would love to check out Rusticl in the latest mesa release (Karol has done some amazing work).

Would it be possible to build it?

Link to the docs is here https://docs.mesa3d.org/rusticl.html

Heya,

Been using your PPA for a while now - love your work!

Was wondering if it was possible to sync the mesa x-swat debian package building files? https://git.launchpad.net/~ubuntu-x-swat/mesa/tree/debian?h=ubuntu-focal

they have added in mesa's shiny new opengl over vulkan "Zink" driver (in the rules file) :)

Again, Thanks for providing this PPA - it's pretty awesome!

Wayland ppa:ernstp/wayland, gives graphics glitches after resume from sleep, only way to fix is to force shutdown and reboot.

Upgrade failed with:

Unpacking libgl1-mesa-dri:amd64 (23.0.0+git2303031837.42e6c344b57~k~mesarc1) over (22.2.1-1ubuntu1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-MajwOi/36-libgl1-mesa-dri_23.0.0+git2303031837.42e6c344b57~k~mesarc1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

Ubuntu 22.10

# cat ernstp-ubuntu-mesarc-kinetic.list 
deb https://ppa.launchpadcontent.net/ernstp/mesarc/ubuntu/ kinetic main

My T510 was upgraded with a Intel Core i7 640M. I discovered that it's using llvmpipe instead of Intel HD for graphics, and I don't know why. I have everything related to Intel graphics & mesa installed on the system.

$ sudo lshw -c display
  *-display                 
       description: VGA compatible controller
       product: Core Processor Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       logical name: /dev/fb0
       version: 02
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom fb
       configuration: depth=32 driver=i915 latency=0 resolution=1600,2700
       resources: irq:27 memory:f2000000-f23fffff memory:d0000000-dfffffff ioport:1800(size=8) memory:c0000-dffff

$ DRI_PRIME=0 glxinfo | grep "OpenGL renderer"
OpenGL renderer string: llvmpipe (LLVM 13.0.1, 128 bits)

I tried both 5.15 & Liquorix's 5.16 kernels, along with your Mesa, but none worked. Had to use yours because Mesa in Ubuntu repo wasn't working properly (constant freezes), and necessitated me to add this PPA (until today). Reverting back to official repo solved it.

Here's the link to Launchpad bug report that may be the cause as to why my laptop was using LLVMpipe.

OS: Kubuntu 22.04

Hi!

Upstream Mesa has stopped building in by default support for H.264 and H.265 decoding and encoding, as well as VC-1 decoding. Support isn't dropped, it's just that now we need to explicitly activate it at build time -- see Debian bug 1016687 for details.

As it stands now, with 22.2.0+git2209282103.897e382d9d, the VA profile looks like this:

libva info: VA-API version 1.11.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_11
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.11 (libva 2.1.0)
vainfo: Driver version: Mesa Gallium driver 22.2.0 for AMD Radeon RX 590 Series (polaris10, LLVM 11.0.0, DRM 3.47, 5.19.12-xanmod1)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc

The correct firmware is present, and the system exposes the now-missing entrypoints with 22.1 or older.

The upstream Debian fix was to include -Dvideo-codecs="vc1dec, h264dec, h264enc, h265dec, h265enc" in the build defs, as per https://salsa.debian.org/xorg-team/lib/mesa/-/commit/78fe00e7470aab38ab214161e28557ef2ff4d9ff -- could you maybe take a look at doing something similar? Or alternatively, depending on how you generate things (I admit I didn't look 😊) via meson_options.txt as per https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016687#20

Thank you!

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20761

I'm just wondering as this may help improve stability in Halo: Infinite.

At the moment, I don't have plans to play the game until Season 3 comes out.

Good day. I install ppa-mesarc on Ubuntu 20.04, thankyou.

Now I want to completly Uninstall this ppa.

Could you give the steps to remove it?

The reason is that i want default graphics drivers same as before. Then i will install corectl without the driver updates.

Thankyou for the work.

Immediately following the latest driver update, the 1080p desktop was broken/frozen on my system. It still technically functioned, as if you knew the keystrokes, you could do things as long as you didn't mind having zero visual indication of what you were doing other than hard drive activity, as the video was frozen solid.

It would freeze during the rebooting process as soon as it would try to display the Plasma desktop.

Only by either using the hardware switch or memorized [CAD]-[return] Reboot sequence then booting into recovery mode with low res software rendering could I get a functional desktop back.

None of the usual commands you find when searching for "frozen desktop" or various permutations of it involving xorg, xrandr, etc... made any difference.

Not being an expert in Linux, I ended up reinstalling the OS 2x. Yes, twice, because when I had first reinstalled Kubuntu, then enabled your repository and installed CoreCtrl, it immediately broke my fresh install just like it did before, which I considered a 50/50 win/fail, for even though it broke my system, it also confirmed for me exactly what it was that originally broke it. I didn't make the same mistake again.

System Hardware info as follows:

Mobo: Asus Sabertooth 990FX
CPU: AMD Phenom x6 1075T (not running turbo mode or OC)
8 GB 1600MHz SDRAM
GPU: Powercolor AMD HD7950
OS: Kubuntu 20.04.3LTS

I don't know if the problem is your ppa, the kernel or both.
Thats the Reason why i open this issue.

Ubuntu Mate 20.04
AMD Vega 56
The problem didn't occur with 5.4.0-56-generic

Everytime i start the game Prominence Poker with proton I get this:

I think everything is running in the Background quite normal (I think i see changes "behind" the graphic bugs) and the curser (which can also be seen on the pciture) is normal.
But i can't make any input.

I switched back to the old kernel, but i want to report this, because i couldn't use this kernel version for an ethernity^^

Another proton game (Rocket League) didn't crash, but i only tested it for a short time.
(When starting Prominence Poker the crash is happening!)

I reported this here, too:
https://ubuntu-mate.community/t/graphic-bug-with-kernel-5-4-0-58-generic-where-do-i-report-this/23315

Issue with the PPA
I just updated to Ubuntu 22.04 and noticed that corectrl is gone after adding the repo, this seems to be due to the package depending on libbotan-2-17, which is no longer available.

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 corectrl : Depends: libbotan-2-17 (>= 2.17.3+dfsg) but it is not installable
E: Unable to correct problems, you have held broken packages.

Only the following packages are available in 22.04: libbotan-2-19 libbotan-2-dev libbotan-2-doc