I did a do-release-upgrade, but I am also not using ZFS on this machine.
I haven’t yet tried any of the new kernels; as described, it seems even the 6.14.0-3* have regressions over older ones. Especially having to unplug/replug the external screen four or five times after boot until it works and random reboots during idle time, are quite annoying.
I haven’t encountered any additional problems due to the 25.04 userland, though.
The only issue during the update was that my cutmem was lost from the grub settings and needed to be added again.
Hi there, I used a stress test to check my cpu temp and fan status. I found my fan speed does not change after the CPU is loaded with heavy processing. How can I fix that ?
My Device Is Vivobook S 15
An update on my T14s in combination with the kernels from the gdrive (@glathe’s?):
linux-image-6.15.0-rc4-jg-0-qcom-x1e
The kernel installs fine, boots fine, but like with much older kernels, the built-in screen is off during the FDE password prompt. It is possible to enter the password blindly and the boot will continue.
There is no way to use the external monitor, it just stays black, although swaymsg -t get_outputs correctly detects it and claims it is on. This is the first time that it reproducibly does not work (see below for more details).
It’s the first time the display brightness controls worked for me
Wifi didn’t work,but that may the one-in-three-boots where it does not.
linux-image-6.14.0-25-jg-0-qcom-x1e
There is some dependency problem during install of all the debs, but the kernel is available, and the system boots fine. The FDE password prompt is shown.
The external monitor works in the same (un)reliable way it did before.
Summary of the screen “states”:
Everything works as expected
The screen turns on, but only shows 640x480; swaymsg reports unknown monitor.
The screen gets no signal; swaymsg reports no external monitor.
The screen gets no signal; swaymsg reports the correct external monitor and thinks it is there; I can move the mouse or windows to the turned-off screen.
With early kernels, I was always between 1. and 2. and had to unplug-replug at most 2-3 times on boot (and never afterwards). More recent kernels (6.14-3*) resulted in all of the above happening and the working state having at most a chance of 20%. Also, the system could switch states on powersave and even permanently go into state 3 with no chance of getting the screen back on without reboot.
Now, the 6.15-kernel mentioned above seems to always be in state 4 with no chance of getting the screen to work.
=> I feel like this is getting worse with every update. Is there anything I can do to help fix this? I have been using the system as a daily driver, but the current state is making that difficult. I will try running an older kernel for now.
People are reporting the issue is gone with kernel 6.15, however Ubuntu 25.04 still seems to rely on kernel 6.14. Do have a hint for me what’s the best chance to get this working again? Building kernel 6.15 myself? (If so, do you have a hint, how to do this?) Or is it likely that these changes are already backported to the Ubuntu 25.04 kernel?
People are reporting the issue is gone with kernel 6.15, however Ubuntu 25.04 still seems to rely on kernel 6.14. Do have a hint for me what’s the best chance to get this working again? Building kernel 6.15 myself? (If so, do you have a hint, how to do this?) Or is it likely that these changes are already backported to the Ubuntu 25.04 kernel?
I wish we knew which of the changes between 6.14 and 6.15 actually fixed it. We can’t just bump the 25.04 (-generic) kernel to 6.15 but we can backport bug fixes.
For the concept -qcom-x1e kernels we will probably switch to 6.15 eventually, when depends a bit on when the kernel team provides a WIP ubuntu kernel based on 6.15 that carries all the non-qualcomm Ubuntu patches.
Looks like you didn’t fetch the firmwares from the Windows partition. Try to run qcom-firmware-extract(?). It should extract the firmware files needed, and update the initramfs. May also be required to install qcom-x1e-settings(?).
Thanks, I’ll try)
But, the next question. Should I extract firmware from Windows parition every time that I reinstall system? And what if I would like to fully format and forget Windows?
Yes, if you nuke your system, you would need to re-extract the firmware. Depending on OEM, you may be able to download these binaries directly from device support page instead of extracting from live windows partition. You can do that for Asus (called BSP package), Dell. Afaik Lenovo didn’t publish any for Yoga, so that won’t work. You can then extract and flatten the .exe via 7z e filename.exe, fool qcom-firmware-extract which expects Windows/System32/DriverStore/FileRepository path by creating it, placing files there, and running firmware extract on that folder. Vuala, no need for Windows partition:
mkdir -p ~/firmware/Windows/System32/DriverStore/FileRepository
7z -y e YourDownoadedFilename.exe -ofirmware/Windows/System32/DriverStore/FileRepository
sudo qcom-firmware-extract -d ~/firmware
# reboot to apply changes
Ideally, one day these firmware will be available ‘automatically’ when installing linux, if OEMs share it to linux-firmware. So far, only Lenovo did for a few models. Its a silly legal copyright issue, but without OEMs uploading it there, we all have to personally extract it, and cannot share it with others as its non-redistributable.
And I hope the asus would share OEM to linux-firmware) I would like to fully erase and format SSD.
And what about sound and camera?
Do you know something about this? Is it available now in any firmware? The notebook without sound and camera is non-working device. Also, I forgot about problems:
There is no HDMI, and derivatives like: HDMI (notebook) → HDMI monitor, or Type-C (notebook) → DisplayPort (monitor), or Type-C (notebook) → Type-C (monitor).
psarapkin@psarapkin-ASUS-Vivobook-S-15-S5507QA-S5507QAD:~/Downloads/firmware/extracted-firmware$ mkdir -p ./firmware/Windows/System32/DriverStore/FileRepository
psarapkin@psarapkin-ASUS-Vivobook-S-15-S5507QA-S5507QAD:~/Downloads/firmware/extracted-firmware$ 7z -y e SOCPackage_forWebSite_Qualcomm_Z_V1.362.7450.2_42696.exe -ofirmware/Windows/Syst
Then I ran qcom-firmware-extract
psarapkin@psarapkin-ASUS-Vivobook-S-15-S5507QA-S5507QAD:~/Downloads/firmware/extracted-firmware$ sudo qcom-firmware-extract -d ./firmware/Windows/System32/DriverStore/FileRepository/
Extracting firmware from ./firmware/Windows/System32/DriverStore/FileRepository/
adsp_dtbs.elf
find: ‘./firmware/Windows/System32/DriverStore/FileRepository/’: No such file or directory
cp: cannot stat '': No such file or directory
Edit: just realized you asked about Vivobook, not Zenbook. Edited accordingly.
For video output - both Type C connectors work with both Type C monitors and Type C (not thunderbolt!) docking stations very well. This is the case for most x1e/x1p devices.
For hdmi there is a way to make it work only on coldboot, no hotplug. Suspending Laptop would also break it. Zenbook specific patch in my repo for reference.
For audio, its experimental for now. You can make it work, but you need to do extra steps. Its also not 100% safe, as you may end up blowing speakers.
