In my case it’s the 13.8 inch x1e80100 with 16gb of RAM
Do we need a different dtb than the romulus13.Dtb?
Weird, I’d expect that to work. Do you get a “no dtb found” error in grub? what does echo $dtb on the grub command line say?
Nothing, grub loads and after about 3 seconds the device resets.
While in grub keyboard inputs do not work. (Including from an external USB keyboard)
Although I think grub is just frozen until the reset since the 30s countdown stays at 30s.
It looks to my like a grub issue, since no kernel should be loaded at the point where the laptop resets.
I tried all the 25.04 concept isos, the 25.04 standard arm release and about half of the 24.10 concept isos.
I’ll try the rest of the 24.10s tomorrow.
Thanks for this, I’m also trying to run on my new zenbook a14.
For the record I did
- disable bitlocker
- disable secure boot (i switched back to setup mode)
- follow instructions given in the comment i replied to
However after the installation the system keeps looping back to grub after I select “Ubuntu” in the grub menu.
Hi @alexvinarskis ,
I suspect I’m getting the same problem with zenbook a14,
How can I get the dtb and manually load it?
Thank you!
Hi @rhythm16 ,
@tobhe has promptly fixed the image, I did a clean install with ISO from 20250703, worked like a charm. Did you download the latest image? There is also no need to disable bitlocker, as 25.04 Ubuntu allows to install next to encrypted volume directly from the installer. You only want to have decryption key to be able to run qcom-firmware-extract on the windows partition, though even that is not needed as you can do something like this (saves time for updates as no need to go to windows, update, go to Ubuntu, update).
@david8271 no hoops in windows are needed, you can press ESC (Asus) / F12 (Dell) during reboot, and one-time-boot-selector menu will appear, you can select USB stick from there.
RE qcom-firmware-extract: its indeed not supposed to be installed by default, and you should get it manually.
RE networking: x1 variant has ath11k WLAN module with boards file that isn’t upstream, I document a solution here.
RE audio: on Zenbook A14 its actually very usable. You would need to additionally follow these steps, and depending on kernel version recompile your own with patches from the repo to enable sound subsystem.
Overall, im daily driving Zenbook A14 with a great success. Known issues:
- HDMI not working (WIP, there seems to be a better solution to mine, but I did not test it yet)
- Camera requires patches from my repo and a number of CAMSS patches for x1e in general, which is why I did not upstream device-tree bits for it yet
- As per latest report, brightness control on LCD / non-OLED variant of X1-26-100 (UX3407QA) did not work, successfully tested solution is available here. I will be submitting it upstream and to Ubuntu’s kernel once get additional confirmation from the user.
Hi, you can add in grub boot option “Ubuntu”:
devicetree /lib/firmware/6.14.0-35-qcom-x1e/device-tree/qcom/x1p42100-asus-zenbook-a14.dtb for UX3407Q
or
devicetree /lib/firmware/6.14.0-35-qcom-x1e/device-tree/qcom/x1e80100-asus-zenbook-a14.dtb for UX3407R
I confirmed that it’s a GRUB issue.
I used the working GRUB from openSUSE Tumbleweed (replacing the files on the Ubuntu USB Stick with those from an openSUSE ISO) to obtain a working GRUB shell and then booted Ubuntu manually.
The issue is with the GRUB config.
Adding:
insmod gfxterm
terminal_output gfxterm
Solves the issue.
@tobhe could you add this to the grub.cfg, if it doesn’t cause issues on other devices?
Also Ubuntu fails to boot after installation.
Adding the dtb manually fixed it, but that isn’t a long term solution.
2 Likes
How have you found the Zenbook? I saw one at local store and was blown away by how light and ridged the chassis was. It looked really nice (I have a Yoga7x at the moment) so have my eye on the Zenbook once the XElite 2 comes out 
Thanks for the tips, unfortunately I was using the 20250703 image, just redownloaded and trying again it still doesn’t work ;(
Maybe I’m doing something wrong, will keep testing
Thanks! I’ll try that in a bit
Hmm not quite sure what you mean by this, if you meant how I became aware of it I saw it in a local Asus store!
Do you remember whether you ticked the install additional drivers checkbox?
This could be a bug in hwe-qcom-x1e-meta.modaliases « debian - ~ubuntu-concept/ubuntu/+source/ubuntu-x1e-settings - [no description]
What does cat /sys/devices/virtual/dmi/id/modalias show on your machine?
As far as I remember, I ticked the box.
Here is the contents of modalias:
dmi:bvnMicrosoftCorporation:bvr175.77.235:bd03/11/2025:svnMicrosoftCorporation:pnMicrosoftSurfaceLaptop,7thEdition:pvr124I00108T000M0000000F0B10C12M02D05U02T2R21S0A0:rvnMicrosoftCorporation:rnMicrosoftSurfaceLaptop,7thEdition:rvr:cvnMicrosoftCorporation:ct9:cvr:skuSurface_Laptop_7th_Edition_2036:
For those asking about Surface Pro 11, there seems to be good news ahead
https://www.phoronix.com/news/MS-Surface-Pro-11-Linux-Patches
1 Like
Hmm. thats weird, there shouldn’t been need for that. Can you share your modalalias as per Tobhe’s manual? Is it an x1/ux3407qa or x1e/ux3407ra variant?
So, our pattern is wrong:
dmi:bvnMicrosoftCorporation:*:pvrMicrosoftSurfaceLaptop,7thEdition*
vs
dmi:bvnMicrosoftCorporation:*:rnMicrosoftSurfaceLaptop,7thEdition:pvr124I00108T000M0000000F0B10C12M02D05U02T2R21S0A0:*
Let me fix that.
I set the Battery Charging option to “Maximize Charge” and now can’t seem to set it back to “Maximize Charge” and it keeps reverting. So can’t charge beyond 80%. Anyone knows how to fix it?
dmesg output:
[ 1960.236008] qcom_battmgr.pmic_glink_power_supply pmic_glink.power-supply.0: unknown notification: 0x83
[ 1998.966304] qcom_battmgr.pmic_glink_power_supply pmic_glink.power-supply.0: unknown notification: 0x583
[ 2124.881435] qcom_battmgr.pmic_glink_power_supply pmic_glink.power-supply.0: unknown message 0x48
[ 2124.881659] qcom_battmgr.pmic_glink_power_supply pmic_glink.power-supply.0: unknown message 0x48
[ 2126.461031] qcom_battmgr.pmic_glink_power_supply pmic_glink.power-supply.0: charge control start threshold exceed range: [50 - 95]
[ 2129.319075] qcom_battmgr.pmic_glink_power_supply pmic_glink.power-supply.0: unknown message 0x48
[ 2129.319238] qcom_battmgr.pmic_glink_power_supply pmic_glink.power-supply.0: unknown message 0x48
I guess I should reply to that mailing list thread… that DMI pattern won’t match the models with 5G mobile broadband.
Their devicetree string:
Microsoft Surface Pro 11th Edition
The one I have:
Microsoft Surface Pro with 5G, 11th Edition
1 Like
The one that has submitted the patches - Dale Whinham - has written here before and he has a GitHub here:
One another note I’m noticing a large improvement in WiFi on 6.16.0-10.qcom-x1e 25.04 Plucky 
with Lenovo Yoga Slim 7x
Hi @alexvinarskis sorry for the late reply, modalias is
dmi:bvnInsyde:bvrUX3407QA.306:bd02/03/2025:br3.6:efr3.11:svnASUSTeKCOMPUTERINC.:pnASUSZenbookA14UX3407QA_UX3407QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3407QA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
Luckily, after I specify the dtb in the grub menu it boots! (I’m still certain I’m using 20250703 tho)
For anyone else with the same problem I did:
- turn off secure boot
- boot from USB drive and install Ubuntu
- copy
lib/firmware/6.14.0-35-qcom-x1e/device-tree/qcom/x1p42100-asus-zenbook-a14.dtbfrom the root partition on disk to the boot partition
(there is probably another way but I just manually located the partitions and mounted the two i.e./dev/nvme0n1pX) - edit Ubuntu grub boot option so it has
devicetree /x1p42100-asus-zenbook-a14.dtb
Another tip is the uefi on this machine does NOT allow secure boot to be turned off (you can’t navigate to the settings page for some reason) once there isn’t a secure-bootable OS on disk or on a bootable usb.
In other words, if you wipe Windows, and turn secure boot back on, you’re cooked.
I did this and had to bring the laptop back for repair…
Strange, that should probably match our regexp "ASUS Zenbook A14 UX3407Q.*" (sysfs node removes whitespace).
Can you also paste:
$ sudo dmidecode -s system-product-name
and
$ sudo dmidecode -s processor-version