Updated and Optimized Ubuntu Free Graphics Drivers

[MastaG]

Hi oibaf
Perhaps a silly question, but do you happen to publish the source for the debian packaging files in a public place?
I'd like to build mesa git with some unofficial turnip patches, however keeping up with all of the debian/control changes (dependencies etc) seems like a lot of work.

[oibaf]

Hello I am on ubuntu 24.10 oracular. As soon as I enable your repo I am getting these errors

Get:10 https://ppa.launchpadcontent.net/oib...drivers/ubuntu oracular InRelease [24.4 kB]
Err:10 https://ppa.launchpadcontent.net/oib...drivers/ubuntu oracular InRelease
The following signatures were invalid: 5ABCE68FF4633EA42E219156957D2708A03A4626 (untrusted public key algorithm: rsa1024) The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93F4D583494746C8

W: GPG error: https://ppa.launchpadcontent.net/oib...drivers/ubuntu oracular InRelease: The following signatures were invalid: 5ABCE68FF4633EA42E219156957D2708A03A4626 (untrusted public key algorithm: rsa1024) The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93F4D583494746C8
E: The repository 'https://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu oracular InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

It is an issue with every PPA, and I can do nothing myself, for more info see:

https://askubuntu.com/questions/1510042/how-to-fix-launchpad-ppa-which-uses-a-key-with-weak-algorithm

https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890/1#heading--new-features-in-24-04-lts

[oibaf]

Hi oibaf
Perhaps a silly question, but do you happen to publish the source for the debian packaging files in a public place?
I'd like to build mesa git with some unofficial turnip patches, however keeping up with all of the debian/control changes (dependencies etc) seems like a lot of work.

You can download the source with

apt source

or

apt-get source

, see

man apt-get

, also directly from here: https://launchpad.net/~oibaf/+archiv...vers/+packages
I don't know of another way to do it.

[MastaG]

You can download the source with

apt source

or

apt-get source

, see

man apt-get

, also directly from here: https://launchpad.net/~oibaf/+archiv...vers/+packages
I don't know of another way to do it.

Yeah, I had to look into it, but it seems to work.
I'm going to create a github action for doing this.
Here's the initial script: https://github.com/MastaG/mesa-turni.../main/build.sh
And here's my PPA: https://launchpad.net/~mastag/+archi...sa-turnip-kgsl

I still need to work on the script a bit and setup the github action, but its a start.

Unfortunately the armhf builds are failing to compile: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11392
Do you think you can fix this?
Because without arm32 drivers, we cannot use it with box86.

[jeff416]

Hello, I know 20.04 (focal) is no longer supported, but I am stuck with it until next year and I have an obscure issue with monitors going blank and sometimes xrandr showing HDMI output as "disconnected". There is nothing in the logs, even with drm.debug set to 14. The same issue doesn't happen on 22.04 but I can't upgrade yet.

Is there any way I can build the latest graphics stack from source myself?

[oibaf]

Yeah, I had to look into it, but it seems to work.
I'm going to create a github action for doing this.
Here's the initial script: https://github.com/MastaG/mesa-turni.../main/build.sh
And here's my PPA: https://launchpad.net/~mastag/+archi...sa-turnip-kgsl

I still need to work on the script a bit and setup the github action, but its a start.

Unfortunately the armhf builds are failing to compile: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11392
Do you think you can fix this?
Because without arm32 drivers, we cannot use it with box86.

Nice, it looks like you already figured out how to fix the build issue.
You may want to change the enabled architectures, it should be possibile at: https://launchpad.net/~mastag/+archi...nip-kgsl/+edit

[MastaG]

Nice, it looks like you already figured out how to fix the build issue.
You may want to change the enabled architectures, it should be possibile at: https://launchpad.net/~mastag/+archi...nip-kgsl/+edit

Yep
It's all working fine now.
The fix for armhf was actually in the error log.
I've opened a MR here: https://gitlab.freedesktop.org/mesa/...requests/30009

I've published my build scripts and runner configs here: https://github.com/MastaG/mesa-turnip-ppa

Thanks !

[oibaf]

Yep
It's all working fine now.
The fix for armhf was actually in the error log.
I've opened a MR here: https://gitlab.freedesktop.org/mesa/...requests/30009

I've published my build scripts and runner configs here: https://github.com/MastaG/mesa-turnip-ppa

Thanks !

I meant you could disable amd64/i386 from here https://launchpad.net/~mastag/+archi...nip-kgsl/+edit if they are not supposed to be used (to save PPA space and avoid eventual errors for these).

[MastaG]

I meant you could disable amd64/i386 from here https://launchpad.net/~mastag/+archi...nip-kgsl/+edit if they are not supposed to be used (to save PPA space and avoid eventual errors for these).

I know, but I'm keeping amd64 and i386 for now.
Reason for this, is that FEX comes with it's own x86-64 rootFS and the last time I've tried it, it wanted the same libraries for thunking.
But I'll have to try it first.
If it's not required any longer, then I'll disable the x86 builds.

[MastaG]

Hi oibaf

Is it possible you could update your signing key?
I'm having trouble checking out your repository on 24.10 because of:

The following signatures were invalid: 5ABCE68FF4633EA42E219156957D2708A03A4626 (untrusted public key algorithm: rsa1024) The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93F4D583494746C8