I also have an Asus Vivobook S 15 X1P42100 and want to help test.
Any news regarding Surface Pro 11? A user managed to boot Arch Linux and really hoped this could help the development
There is some activity. GitHub - dwhinham/linux-surface-pro-11: Arch Linux ARM for Surface Pro 11.
With the dtb being there it should be possible to boot / integrate the Surface Pro 11.
Does that mean that all our firmware is now in the upstream linux-firmware
package? That would be great.
Yes, the T14s firmware was committed to linux-firmware by Lenovo last week, see https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/qcom/x1e80100/LENOVO?id=b35537889108bffd33ef071ff2f0de9f1d73c8ad
T14s users won’t need to run qcom-firmware-extract anymore and we can include all firmware in the installer media from now on.
EDIT: until we enable a component that does not currently have the firmware published of course
(Yoga Slim 7 with LVM encryption) Late reply, but I have tested many different options now but the password window is always a black screen - the reason for reinstall is just to remove the encryption again.
It’s surprising, I have LVM encryption on the slim 7x, it works everytime.
Is your bios up to date?
Has anyone tried upgrading to the plucky daily packages yet?
I get the following error when trying to update via apt dist-upgrade:
Unpacking linux-firmware (20250204.git0fd450ee-0ubuntu1) over (20241118.git6e4e9
4b0-0ubuntu1) ...
dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20250204.g
it0fd450ee-0ubuntu1_arm64.deb (--unpack):
trying to overwrite '/lib/firmware/qcom/x1e80100/LENOVO/21N1/adspr.jsn', which
is also in package qcom-x1e-firmware-extracted 20250202
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/linux-firmware_20250204.git0fd450ee-0ubuntu1_arm64.deb
Error: Sub-process /usr/bin/dpkg returned an error code (1)
Thanks, I am working on a proper fix for this. See also Ubuntu 24.10 Concept ♥️ Snapdragon X Elite - #494 by tobhe
You can apt remove qcom-x1e-firmware-extracted
manually and then upgrade to fix the issue.
Yes, I booted windows recently and installed all the updates. I saw that there is an update to Ubuntu now, Im gonna install that then try some Edge 6.13 X1E debs I found, if that does not work then im probably doing a new unencrypted install again.
Also - do you get the Ubuntu splash-password-screen or just regular text-screen ?
I have the Ubuntu Splash password.
Its strange, updating to 6.13_8 and 6.14_RC1 did not work either.
Im probably trying a new clean LVM install again, and if I have the same problem Im removing the encryption.
It is likely that something is different with your hardware and you are missing modules in your initrd for it to work. Have a look at lsmod and maybe try adding more of them to the initrd via /etc/initramfs-tools/modules
to find out which ones.
If we know what’s missing it is an easy fix.
so excited for this work, if i am understanding correctly I will be able to completely format my drive now and not worry about keeping the windows partitions for using the firmware extractor now when the change has been implemented for the base installer correct?
so excited for this work, if i am understanding correctly I will be able to completely format my drive now and not worry about keeping the windows partitions for using the firmware extractor now when the change has been implemented for the base installer correct?
I wouldn’t do that just yet. The firmware in linux-firmware is for the various peripheral devices used by the hardware. They get loaded at boot time by the kernel. This is the same files we used to extract with qcom-firmware-extract
, so that isn’t needed on that hardware anymore.
There is also your UEFI firmware which runs before Linux boots and that also receives updates via Windows. It might be possible to do those manually as well but I am not so sure about that.
Also so far only the T14s firmware has been added to linux-firmware, since the devices use signed blobs with and keys differ for each hardware each of them would need to be added individually. Realistically I don’t think all of the laptops will ever be supported but it is likely that we will see more, especially the more popular ones with more of an enterprise focus.
Edit: Nevermind.
Either there is something wrong with my SSD or there is some other hardware fault with my computer.
The new install ISO from today (20250207) is the first time I have had a install window without flicker (without changing resolution) but neither ordinary or LVM install works after a install.
Im trying to install windows again to see if there is bios fix for me (even if I did the same thing not long ago)
PSA: linux-firmware upgrades should work normally again on T14s, qcom-firmware-extract behaves a little differently than before to make sure the resulting packages don’t conflict in the first place.
Maybe consider rerunning qcom-firmware-extract, that should just update the package to the new format. As a side effect you get new firmware if the Windows firmware was updated in the meantime. It should not make a functional difference.
EDIT: please make sure to update your packages before rerunning

Also so far only the T14s firmware has been added to linux-firmware
Lenovo
Adds a bit of Acer Swift 14 plumbing and T14s firmware