Looking for support on installing Ubuntu on Snapdragon X

Support and Help
1

Looking for support on installing Ubuntu on Snapdragon X

Ubuntu Version:
26.04, 25.10

Desktop Environment (if applicable):
NA

Problem Description:
I’ve got a new Asus laptop Vivobook based on Snapdragon X.
I tried Ubuntu 26.04 LTS but it fails straight away after Try Ubuntu with some error
mount: efivarfs failed /sys/firmware/efi/efivars … Operation not supported
displayed for a fraction of a second then laptop reboots in Windows 11

I did follow advice to change BIOS values (from Insyde), e.g. Secure Boot, Fast Boot

I could see there is some success installing Ubuntu on X1E (Elite), I’m looking forward seeing some development on basic X1.

Relevant System Information:
Asus Vivobook X1407Q
Snapdragon X1-26-100

2

26.04 is beta and is available only to test and report results to Canonical developers. It might work but is not expected to as it is only for testing so have you also tried with 25.10 with the same results ? Is this a new Asus model just released?

Is the drive or are the drives on the computer GPT. I would expect so with windows 11 and I would expect an EFI install. If you can boot any Linux usb, you can use a terminal and as root (use sudo) run: parted -l That command will list the information needed. If you can’t boot and use any Linux, you can find the disk label from windows explained at the link below.

https://stackoverflow.com/questions/3840870/detect-gpt-and-mbr-partitions-with-powershell

The error regarding efivars would mean that the iso you are booting from or the hardware are not EFI capable which is highly unlikely if the computer is new. Most computers have an option in the BIOS for a one time boot which can be either EFI or legacy/CSM and I would think you would need EFI. You can easily determine if there is an EFI partition on the current drive with windows with the parted -l command listed above from any Linux system. If you can’t boot a Linux, you can get it from windows but it is a multi step process described at the link below.

https://linuxbsdos.com/2024/09/29/2-simple-ways-to-access-the-efi-system-partition-on-windows-11/

3

You may want to look in Ubuntu Architectures - Ubuntu Community Hub as there are a few snapdragon discussions going on there

1 Like
4

See the megathread about Snapdragon Ubuntu installs at:

That covers most of the possibilities with this hardware.

1 Like
5

I did try 25.10 - same failure.
Asus model from 2025-04? (label on the back).

As you expected, it is GPT:
Get_Disk (as Admin) says
Drive Number 0 … Size 476.94 GB … Partition Style GPT

As I said, I did make two changes in BIOS, Disabled
Secure Boot
Fast Boot
There is no Legacy / CSM switch.

Is it possible that the RAM is somehow protected so efivarfs cannot be created?
I couldn’t see any obvious switch in BIOS, I was considering trying to contact the provider Insyde. Any other idea?

I did read the suggested threads, I can see there are a few other people stuck in exactly the same failure @stuart.mark.anderson
and
@alexvinarskis said in May25 “Asus Zenbook A14 should work in all three variants (x126100 that I personally tested…” slightly different model (Zenbook) same processor

6

Which specific iso for the different releases of Ubuntu did you download? You did download from the official site, correct? Did you verify the download as explained at the Ubuntu download page? What software did you use to write the iso to the usb? Do you have another computer available to test boot the usb to eliminate a bad download or bad write as the problem? And finally, what software did you use to write the iso to the usb? The Ubuntu site recommends balena etcher although I don’t know if that will help.

https://ubuntu.com/tutorials/install-ubuntu-desktop#3-create-a-bootable-usb-stick

7

Indeed a few more people reported some issue with x1-26-100 and/or LCD variant booting Ubuntu ISO on Zenbook A14. Unfortunately I had issue with my laptop, but im getting it back next week and will then be able to re-test and either verify what and how works, of fix if it doesn’t.

8

Downloaded from official Ubuntu website (e.g. https://ubuntu.com/download/desktop)

resolute-desktop-arm64.iso

ubuntu-25.10-desktop-arm64.iso

Used kubuntu Startup Disk Creator to write on SD card. Plugged into a classic USB port (not USB-C - I did read that some slower USB ports don’t work on some machines, but since it does start I thought that should be OK - I don’t have a USB-C pen drive yet).

I don’t have another Snapdragon laptop.

The fact that it failed in similar way with two different iso images suggests to me it’s a problem with the HW / config (BIOS/UEFI) - assuming the iso should work.

9

No news, probably not good news :⁠-⁠( most likely you didn’t have time to try installing again on your Snapdragon X1 laptop (NB. Not X1E nor X1P - it seems like at least X1E was installed successfully by a number of people).

Anyone any suggestion why I’m seeing this efivars error?

Can I try something in the BIOS config?

10

Hi,

I got my Zenbook A14 back last week. Used latest Ubuntu 25.10 arm64 image, installation was flawless, encrypted rootfs alongside Windows.

I re-read your answers above, you mention its a Vivobook 14”, I dont recall it being supported upstream, are you running your own device tree? Or are you just booting the ISOs you describe above as is, and getting that error almost immidiately? With the arm64 devices, each device sadly needs its own device tree, and some other changes (compatible name to be whitelisted in qseecom driver to access efivars, for example). The new Ubuntu ISOs use stubble which helps package kernel and ‘known map’ of hardware IDs to detect which device it is, which in this case is most definitely missing your device.

If that was the case, the way forward would be probably to modify created ISO’s grub config, to ‘hardcode’ DT to load (eg. Vivbook S15? or Zenbook A14?) - with some luck this will be enough to boot with at least some features working (keyboard, mouse).

To try this out - start with older 25.04 image instead (this one from 2025-07-25 is old enough) from the 25.04 support page (its older, and GPU won’t work on X1P, but does not use stubble making it a bit easier to try out different existing device trees that are not from your laptop). Once you flash it onto USB stick, go to /boot/grub/grub.cfg, this file will list all supported ‘models’ and their respective device trees. Copy one of the supported devices, and places its cmdline, dtb in the end outside of individual if statements, right before the error out message, eg. Zenbook A14 LCD device-tree:

image
image921×669 117 KB

With that USB stick, you should hopefully be able to boot a bit further, though maybe not too much :stuck_out_tongue:

From there on, you would need to derive dedicated device tree, that would help enable all the other features (type C ports, audio, camera, fingerprint readers, HDMI etc etc). I could help with that a bit, if you willing to do a lot of testing which may be time consuming. Feel free to reach out in DMs, so we don’t pollute the public thread :slight_smile:

1 Like
11

I think I understand what you are saying. I’m not yet convinced I can start this project pretty much from scratch, IMO. Because now I started to grasp the real reason the boot fails so early.

It’s not only a new machine but it seems like nobody tried this processor before!

What are the chances that modifying grub.cfg would just work? (on a new processor, admittedly same core?) If you say it’s over 90% I’d be inclined to try this first step.

are you running your own device tree?

I have never heard before about that, I assume it’s not trivial. Just to have a rough idea, how long you estimate it would have taken an experienced linux developer (*) to get the Zenbook A14 to the current stage? (I think X1E was more advanced when X1P was not supported, so somehow a similar situation)

(*) I assume you are one but you know better :slight_smile:

Feel free to reach out in DMs, so we don’t pollute the public thread

I don’t know what DM is in this context. And I suppose “public” is this thread (to be closed in 13 days).

12

It’s not only a new machine but it seems like nobody tried this processor before!

Thats incorrect, i think there is some confusion with naming. There are actually only two SOCs, higher end hamoa (X1E, high end X1P like X1P-64-100) and lower end purwa that came out significantly later (starting from X1P-42-100 and lower, including X1-26-100). Both are now fully supported upstream. All the other ‘models’ are just binning variants (see semiconductor binning) of hamoa and purwa.

Zenbook a14 UX3407QA with device tree is called ..x1p42100.. is actually device with x1-26-100. So this processer was tested before, and is now we’ll supported. It’s Vivobook 14” that wasn’t tested before.

What are the chances that modifying grub.cfg would just work? (on a new processor, admittedly same core?) If you say it’s over 90% I’d be inclined to try this first step.

‘just work’ is broad definition :stuck_out_tongue: there is high chance, I would say over 90% that at least one purwa device tree will allow you to boot up, with at least USB2.0 ports working. There is low chance other things like USB type C and mousepad will just work, but adding them is trivial at this point. Thinks like Audio will 100% not just work, most likely camera as well.

I have never heard before about that, I assume it’s not trivial. Just to have a rough idea, how long you estimate it would have taken an experienced linux developer (*) to get the Zenbook A14 to the current stage? (I think X1E was more advanced when X1P was not supported, so somehow a similar situation)

There are by now a lot of examples and resources. I suggest joining IRC channel ‘aarch64-laptops’ and asking, perhaps someone is already working on support for this device even. Asus took me quite long time, but it was also blocked by Qualcomm things. Getting new Vivobook to have almost everything running (audio and/or camera may be more tricky) could be done a in a full day of pair debugging.

I don’t know what DM is in this context. And I suppose “public” is this thread (to be closed in 13 days).

Ah sorry, i meant direct message, by email, or on Matrix, as getting device tree to work would require lots of small back and forth.

13

Well, IIRC you can get the VivoBook 14 up with the x1p42100 variant of the Vivobook S15 device tree. Like its in my kernel tree and packages, and also in the extended ISOs that I publish occasionally. The latest is still Ubuntu Concept 25.04, but I have the 25.10 one on the bench, working already. Trying to improve on the sound part before publishing this one. So maybe worth a try.

14

Well thats actually pretty far in… question is which dtb is used. The problem is this: efivars is only still allowed by qcom_scm per model, and the Vivobook 14 is for sure not on the list. The hack/workaround to make this work is to specify something that is on the list as compatible in the device tree to boot. All(?) non-upstreamed device trees use something like “lenovo, thinkpad-t14s” as compatible. This works :tm: The extended ISOs I mentioned employ that trick to boot and install with the Canonical kernels on them.

1 Like
15

Hello alexvinarskis

Thanks for all your posts and info regarding the Zenbook - I recently got a Zenbook A14 UX3407QA-QD244W and have got Ubuntu dual booting with Windows 11 via the Ubuntu 25.04 live disk but I was not able to get the WIFI device working.

I am just writing to check if I am in the best place to get more information about that or if there is a better thread on this site or another site elsewhere that I should be reading?

Thanks again for all your hard work.

1 Like
18

This is most likely the reason for my efivars error.

I did follow @glathe advice and used one of his extended ISO images with Vivobook S15 as an “alias” for my laptop. It did boot and I was able to Try Ubuntu.

I didn’t connect to a network, screen looked as expected, used the laptop keyboard and pad.

I tried a few apps like Files and Terminal.

The fan cooler was active all the time, so the Power management didn’t seem to be working properly.

19

This was valuable information, thanks for clearing up the processor confusion.

Your suggestion to modify grub.cfg didn’t work as I wasn’t able to modify that read-only file system.

20

The fan cooler was active all the time, so the Power management didn’t seem to be working properly.

This is sort of expected. Most of these laptops, including Zenbook A14 do not have EC (embedded controller) driver. On my device, once fans start spinning when it gets warmer, they won’t slow down until shutdown/reboot.

Your suggestion to modify grub.cfg didn’t work as I wasn’t able to modify that read-only file system.

Hmmm if i recall I used rufus on Windows to flash the USB stick, that automatically removed the read-only limitation. Otherwise, there are some apps like cubic to repack Ubuntu ISO, but they are not as easy to use.

I did follow @glathe advice and used one of his extended ISO images with Vivobook S15 as an “alias” for my laptop. It did boot and I was able to Try Ubuntu.

That sounds like a good progress! You probably dont need to modify grub then, did you try to ‘install ubuntu’? It should hopefully succeed. Once you are in running system, you can pull firmware from Windows to enable GPU etc.

21

Hi,

Apologies, somehow missed the messages here. Sadly WiFi on X1P variant won’t work out of the box - you need to pull board config file, and integrate it in Linux. As these are ‘non-redistributable’, one cannot just share these online as that would be technically illegal. You would have to follow this guide I made sometime ago, should be ~15mins of work if you do it the first time.

I assume you already did, but if not - to enable GPU acceleration, battery info and audio, you need to extract firmware from Windows. Same story as above, everyone need to extract it as it cannot be freely shared. On ubuntu, there is qcom-firmware-extract tool to automate this process.

1 Like