Got a new question to the community. Where can I get the qcom firmware if I wiped my Windows partition. I knew that I had to scratch them from the NTFS Partition before doing that, but I achieved to brick the Windows before being able to sign in and I also reset the TPM-Keys. No rescue-media or partition is available. Any hints?
you can download qcom-firmware from github : GitHub - anonymix007/x1e-firmware
I am using yoga slim7x and the firmware works well
1 Like
I am having problems with suspend on the Lenovo T14s 64GB (21N1CTO1WW). I am using a kernel built from the Ubuntu-qcom-x1e-6.12.0-22.22 tag but running a different userspace. The machine sleeps as expected without problems using the live image with recent ISOs, but does not return from sleep on my own installation with a different userspace. This is the dmesg output when testing with the /sys/power/pm_test interface set to feeze:
[ 1896.458705] Filesystems sync: 0.001 seconds
[ 1896.460997] Freezing user space processes
[ 1896.463477] Freezing user space processes completed (elapsed 0.002 seconds)
[ 1896.463651] OOM killer disabled.
[ 1896.464259] PM: hibernation: Basic memory bitmaps created
[ 1896.464263] PM: hibernation: Preallocating image memory
[ 1897.582350] PM: hibernation: Allocated 1001036 pages for snapshot
[ 1897.582400] PM: hibernation: Allocated 4004144 kbytes in 1.11 seconds (3607.33 MB/s)
[ 1897.582453] Freezing remaining freezable tasks
[ 1897.585998] Freezing remaining freezable tasks completed (elapsed 0.003 seconds)
[ 1897.586053] PM: hibernation: debug: Waiting for 5 seconds.
[ 1902.586090] Restarting kernel threads ... done.
[ 1902.743707] PM: hibernation: Basic memory bitmaps freed
[ 1902.746002] OOM killer enabled.
[ 1902.746027] Restarting tasks ... done.
[ 1902.755942] PM: hibernation: hibernation exit
So freezing userspace appears to work as intended. Bumping the /sys/power/pm_test setting to devices fails. On a machine connected over UART I get to the “Freezing user space processes completed” dmesg output and that’s the end. The machine fails to return from sleep, or at least it appears that is problem. If I do not touch anything it will hang, as though asleep, for seemingly as long as I do not attempt to wake it, seemingly suspended. But when I attempt to wake it the machine does a hard reboot. There is no dmesg output to the UART.
I am not attempting to suspend to disk, but the above dmesg suggests it is trying to suspend to disk, which appears likely part of the issues, but I can’t seem to get it to suspend to idle/memory. The userspace does not use systemd and I am making use for full disk encryption via LUKS. I boot from an EFI stub directly without GRUB.
Any insight would be greatly appreciated.
With 6.12.0-28 I do now have working RTC on my XPS, so thats great! No more waiting till clock syncs with NTP, but always correct time on boot.
Hoped to also see video hw acceleration, but the firmware process in dmesg shows error. I tried with latest firmware from linux-firmware-git, but still error unfortunately.
[ 35.758732] qcom-iris aa00000.video-codec: error -22 initializing firmware qcom/vpu/vpu30_p4.mbn
[ 35.758795] qcom-iris aa00000.video-codec: firmware download failed
[ 35.758994] qcom-iris aa00000.video-codec: core init failed
[ 36.387546] qcom-iris aa00000.video-codec: error -22 initializing firmware qcom/vpu/vpu30_p4.mbn
[ 36.387597] qcom-iris aa00000.video-codec: firmware download failed
[ 36.387763] qcom-iris aa00000.video-codec: core init failed
1 Like
Please let me also thank you very much for your efforts. As far as I see, this hardware branch is played by a one-man-show?! I am very impressed, either by the Snapdragon SOC, as well as of the progress being made in this concept image. You just saved my weekend! 
1 Like
Regarding Surface Pro 11, I’ve just published this GitHub repo with some patches, device tree, and notes for getting Arch Linux ARM booting: GitHub - dwhinham/linux-surface-pro-11: Arch Linux ARM for Surface Pro 11.
There’s a bootable USB image there to try. Hopefully this can be used to help get Ubuntu Concept running on the SP11 too - if anyone can point me towards what I need to look at to build the Ubuntu ISO I can try to apply my changes and test it.
3 Likes
The errors show that this file is incompatible. It needs to be copied from the windows partition, it is also signed per device. I couldn’t find it on the Dev Kit, but qcav1e8380.mbn might be a candidate.
Yes, got video hw accel working now on my XPS! h264 decoding only though in Firefox Nightly.
qcvss8380.mbn from windows to /lib/firmware/qcom/vpu/vpu30_p4.mbn and removing .zst one
2 Likes
This is the Surface Pro 11? If so, can you please explain me how to do it?
It’s on the XPS. It will probably be fixed properly soon, otherwise just copy the file as mentioned and make sure you are on a .28+ kernel.
Now this is interesting. This is not Iris, it is Venus firmware, but whatever works 
I’m seeing some extreme instability on my thinkpad t14s 21N1CTO1WW. I’ve updated windows completely and, as far as I can tell, fully updated my firmware using lenovo vantage. I shrunk my main windows NTFS partition by 100GB for Ubuntu. I also tried letting Ubuntu shrink the NTFS partition.
No matter what, one of 5 things happens when I click next:
- “A system error has occurred”. I have to reboot after this happens
- Subiquity gets stuck. The spinner thing just keep spinning.
- Subiquity “something went wrong” with an empty log.
- Subiquity “something went wrong” with the below log:
- The next step opens
Jan 25 15:46:08 ubuntu subiquity_event.13714[13714]: subiquity/load_cloud_config/extract_autoinstall:
Jan 25 15:46:08 ubuntu subiquity_event.13714[13714]: subiquity/load_cloud_config/extract_autoinstall:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Early/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Early/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Reporting/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Reporting/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Error/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Error/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Userdata/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Userdata/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Package/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Package/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Debconf/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Debconf/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Kernel/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Kernel/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/KernelCrashDumps/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/KernelCrashDumps/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Zdev/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Zdev/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Ad/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Ad/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Late/apply_autoinstall_config:
Jan 25 15:46:09 ubuntu subiquity_event.13714[13714]: subiquity/Late/apply_autoinstall_config:
For 2, 3 and 4 I can click previous and next while 1 forces me to reboot and 5 will only work up until the timezone setting step.
The manual partitioning tool won’t ever stage changes. Any time I modify a partition the window just bugs out like it’s in the middle of rendering the partition table again.
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.
Handle 0x0009, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 21N1CTO1WW
Version: ThinkPad T14s Gen 6
Serial Number: ..
UUID: ..
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_21N1_BU_Think_FM_ThinkPad T14s Gen 6
Family: ThinkPad T14s Gen 6
Any ideas?
I’ve uploaded a new installer image earlier today so it could be a regression. You can try with an older one from Index of /~platform/images/ubuntu-concept (for example the previous one https://people.canonical.com/~platform/images/ubuntu-concept/oracular-desktop-arm64+x1e-20241213.iso) and see if that works better.
1 Like
Thanks. I tried that image yesterday with much of the same results. Is it possible for the regression to still have been on the dec 13 build but on some earlier build? I just ran journalctl -f:
Jan 25 16:33:27 ubuntu snapd[2357]: storehelpers.go:1044: cannot refresh: snap has no updates available: "bare", "core22", "core24", "desktop-security-center", "firefox", "gnome-42-2204", "gtk-common-themes", "prompting-client", "snap-store", "snapd", "snapd-desktop-integration", "thunderbird", "ubuntu-desktop-bootstrap"
Jan 25 16:33:30 ubuntu upowerd[4459]: value "nan" of type 'gdouble' is invalid or out of range for property 'percentage' of type 'gdouble'
Jan 25 16:33:39 ubuntu ubuntu-desktop-bootstrap.subiquity-server[31937]: /snap/ubuntu-desktop-bootstrap/289/bin/subiquity-server: line 47: 31977 Segmentation fault (core dumped) $PYTHON -m subiquity.cmd.server "${args[@]}"
Jan 25 16:33:39 ubuntu systemd[1]: snap.ubuntu-desktop-bootstrap.subiquity-server.service: Main process exited, code=exited, status=139/n/a
Jan 25 16:33:39 ubuntu systemd[1]: snap.ubuntu-desktop-bootstrap.subiquity-server.service: Failed with result 'exit-code'.
Jan 25 16:33:39 ubuntu systemd[1]: snap.ubuntu-desktop-bootstrap.subiquity-server.service: Consumed 3.886s CPU time, 371.3M memory peak.
Jan 25 16:33:39 ubuntu systemd[1]: snap.ubuntu-desktop-bootstrap.subiquity-server.service: Scheduled restart job, restart counter is at 38.
Jan 25 16:33:39 ubuntu systemd[1]: Started snap.ubuntu-desktop-bootstrap.subiquity-server.service - Service for snap application ubuntu-desktop-bootstrap.subiquity-server.
Could be but it seems unlikely because I haven’t seen any other complaints. Maybe try a different usb drive and/or a different port.
I’ve just tried a (different storage medium) portable SSD and also USB-A port with the same result
I also tried an early nov build, same thing
I’m debating completely wiping the windows drive and starting even windows over
I got it installed finally, some observations:
- I specifically let Ubuntu shrink the Windows partition - didn’t touch ahead of time
- I undersized the Ubuntu partition by 30GB or so of what was actually available
- Relied on
cutmemin GRUB instead ofmem=16GBormem=30Getc - Booted with
clk_ignore_unusedandpd_ignore_unusedkernel command line args - Seemingly most critically: the wifi did not work when the installer actually worked. There is some bug on my laptop causing wifi to not work sometimes. I’m struggling to find the LKML thread now but it was something to the effect of a cold boot triggering this case or even the opposite, I just can’t remember.
I’ve done everything other than going thru the installer without wifi previously and that is the only difference between yesterday and today. I can’t say if it’s correlation or causation, however (obviously the wifi is probably not the issue but whatever is causing the wifi to not work during that boot?). But I’ve tried at least 30 times before now with each consistently failing in predictable ways.
The installer should always run with cutmem and the *_ignore_unused args enabled by default, so it would be surprising if that actually made a difference. The WiFi not working could have other side effects, if there is an internet connection the installer will fetch the newest packages no matter how old the installer media is. Was this the older iso?
It was the latest image (jan 25). I also previously ran both with and without connecting to wifi, mostly without connecting.
Note that it was the first attempt this morning so I’m also wondering if just having left the laptop fully off for some amount of time couldn’t have reset something due to some firmware issue, although windows did work. I have tried cold boot / warm boot many times but not without having left it fully off overnight.
Is this with iwd ? If yes, see if you have in iwd.conf:
[General]
ControlPortOverNL80211 = false