On Tue, Mar 18, 2025 at 8:28 AM Georg Gottleuber
<g.gottleuber@xxxxxxxxxxxxxxxxxxx> wrote:
>
> Am 07.03.25 um 07:45 schrieb Dmitry Baryshkov:
> [...]
> >>> diff --git a/arch/arm64/boot/dts/qcom/x1e80100-tuxedo-elite-14-gen1.dts b/arch/arm64/boot/dts/qcom/x1e80100-tuxedo-elite-14-gen1.dts
> >>> new file mode 100644
> >>> index 000000000000..86bdec4a2dd8
> >>> --- /dev/null
> >>> +++ b/arch/arm64/boot/dts/qcom/x1e80100-tuxedo-elite-14-gen1.dts
> >>
> >>> +&gpu {
> >>> + status = "okay";
> >>> +
> >>> + zap-shader {
> >>> + firmware-name = "qcom/a740_zap.mbn";
> >>
> >> Are the laptop's OEM key/security fuses not blown?
> >
> > Can this laptop use "qcom/x1e80100/gen70500_zap.mbn" which is already a
> > part of linux-firmware?
>
> It seems so.
>
> Because there were no logs about loading zap.mbn, I activated dyndbg
> (dyndbg="file drivers/base/firmware_loader/main.c +fmp"). See attachment
> for dmesg output. But GUI freezes after sddm login.
Hmm, if zap were incorrectly signed, the error would come after
firmware_loader. You should see something with "Unable to authorize
the image" (`dmesg | grep drm` would show it).
As Konrad mentioned, make sure you have mesa v24.3 or later, v24.2 is
missing some needed fixes
BR,
-R
