Open leonpano2006 opened 9 hours ago
this isn't a mesa ppa issue but actually an issue caused by Nvidia manually overwriting libdrm with their own proprietary fork that does not contain the newer symbols necessary for software like the mesa libraries to link to.
libdrm is only useful for wayland and since its effectively broken on pre-jetpack 36 you might as well revert nvidia's change by doing something such as this. similar to the following is done on Switchroot Ubuntu Jammy/Noble to prevent any such issues.
dpkg-divert --package nvidia-bsp-diversions --add --rename --divert /usr/lib/aarch64-linux-gnu/tegra/libdrm.orig /usr/lib/aarch64-linux-gnu/tegra/libdrm.so.2
dpkg-divert --package nvidia-bsp-diversions --add --rename --divert /usr/lib/aarch64-linux-gnu/libdrm_nvdc.orig /usr/lib/aarch64-linux-gnu/libdrm_nvdc.so
ldconfig
Might be worth adding that to the runonce on Focal, if the user's on Tegra hardware
Might be worth adding that to the runonce on Focal, if the user's on Tegra hardware
waiting on confirmation from @leonpano2006 before I do anything
that does the trick thanks i was not expecting such issue i really wonder what are people working in nvidia thinking is there goal to fuck up everything?(like EA)
install-fail-Steam.txt it will install kiask-mesa but that has a problem making that linker broken, Even on a fresh flashed/installed system, issues can still occur.
and after steam script is failed then 99% of scripts used compiled from source will fail for the same reason.