Does kernel 6.19 include 5GHz Wi-Fi fixes?
1 Like
Hmm checking on Ideapad 5… booted with the questing-260119 ISO, it connects with a 5,2GHz frequency here (and a 2,4GHz one, too). Not sure if it was a kernel change that’s necessary. Kernel booted is 6.19.0-3-qcom-x1e built by Canonical.
1 Like
You’re right. I have t14s. Drain during shutdown is now fixed for me with 6.19! Suspend though still drains. ~3% an hour for me. Great progress though! Anyone gotten audio to work yet?
On T14s? Yes. Tinkering on DP/HDMI sound.
Speakers and Aux or Bluetooth and USB?
Speaker, Headphone, internal mic, headphone mic. And USB.
ok, for me the speaker, Headphone and internal mic don’t work. They don’t show up on my T14s. Did you install something to get them to work?
Almost everything else (Webcam, GPU) seems to work as expected.
Edit:
I can see the devices with aplay -l but when I run
pw-cli list-objects | grep node.name
I only get a dummy driver, freewheel driver and a midi bridge.
1 Like
There is a Wiki entry I wrote a long time ago which generally also works for the T14s. I need to update it, was working on verifying that sound works the last few days. Yesterday I was able to get sound out of the HDMI-connected external display 
I have uploaded the newest ISO image based on Ubuntu Concept Questing-260119 with an extra ext4 partition and the audioreach and alsa-ucm-conf repos checked out (and where required, built) with the right commit. So, you could take the files required from there.
1 Like
On my Slim 7x I installed the git version of alsa-ucm-conf, sound just worked after a reboot.
I then manually changed the 85 volumes to 5.
I didn’t need any extra kernel parameters or topology files
I’m not entirely sure the setup is correct though. In Ubuntu’s system settings 4 speakers are shown in the test window, but it freezes when clicking either of the lower 2 speakers.
1 Like
Big thanks to both of you. Audio is now working for me.
Can confirm the freezing with the two lower speakers.
2 Likes
does suspend to ram work on Asus Vivobook S15? there was no confirmation on this thread [0] but i just wanted to double check if more recent kernel made more progress
1 Like
Hi, there were some general suspend issues IMO. I just tested a bit on 6.19-rc6 with ThinkBook 16, works well-ish. I see the suspend messages in dmesg, time stops, and the resume messages. Had some weird stuff on 6.18.7. Also, 6.18.4 on T14s, suspend /resume works so well that I don’t think about it. I’m sometimes surprised when a type-c hotplug when suspended leads to a reboot, but that’s not very often.
It could be that Vivobook S15 may have some component important for power management missing in the device tree. I’ve seen that upstream doesn’t have the sound definitions, for example. This can also affect suspend/resume behaviour.
Hello All, I’m trying to enable secure boot but no luck so far. I’ve downloaded the generic arm64 image and it seems to boot fine on my Snapdragon X Elite laptop. However when I enable secure boot then reboot, it says it cannot load GRUB/mmaa64.efi. Does anyone have any idea on how to get Ubuntu to load with secure boot turned on?
I appreciate the help, and thanks,
- Bana
Generally (unsure if applicable to ARM, but it should), if installed with Secure Boot enabled, it will bot with Secure Boot enabled.
I do own one of these (surface 12 inch) but have no idea how to execute that python script. To me it looks as oft I should run it in Linux which isn’t available on the surface or am I missing something?
Surface pro 12 inch should be bootable/installable with the questing-desktop-arm64+x1e-20260119_extended_jg.iso. Should be enough to run the python script 
The actual change on the ISO is just providing additional menu entries and dtbs for not-yet supported devices. There is also an additional ext4 partition with the same dtbs, a kernel package, and sound repos with the basics to enable sound on many of these devices.
1 Like
Oh. Did not know that. Just tried it but am not able to get past grub. Hooked up a usb keyboard to select an entry but that does not seem to be recognized. It also doesn’t auto boot in to the selected option but restarts after a few seconds and boots to grub again.
Reading on Phoronix about “Qualcomm adding their QUPv3 firmware to linux-firmware.git for their Snapdragon X1 Elite “x1e80100”“, what are the implications for this project? Are these drivers now available on all Linux X1 Elite Snapdragons without the need to keep the Windows partition to receive lates updates?
EDIT:
Uhoh.. I see that Qualcomm’s firmware only contains firmware for “managing serial interfaces on the SoC like SPI, I2C/I3C, and UART.“
I guess Linux is still a loooong ways before being treated properly on X1 Elite Snapdragons. It saddens me, especially because I don’t understand this practice; why can these firmwares not be made available to Linux?
I’ve been trying for a couple hours now to install the latest build on a Lenovo Yoga 7 14 and I keep getting an error during installation. It appears it doesn’t know what’s causing it, but it always has “curtin command in-target”. At first I thought there was a bitlocker issue, but I’m on Windows home so no bitlocker. I made sure secure boot was disabled and after a few failed attempts I even wiped the hard drive so it could start with a clean slate instead of the windows partitions that were already there and still no luck.
Oh thank you for reporting this. I also had a report on Ideapad 5 2in1, and this may make sense. Win11 Home and Bitlocker are Schrödinger’s Beast now. Meaning, it gets shipped encrypted, but it doesn’t show. You need to explicitly enable and then disable bitlocker to get it unencrypted. You can access the encrypted ntfs, but only after saving the recovery key (MSA, the works). And you can probably resize it after having this access on Linux, but I actually did this one on Windows every time.