Hey, how is support for x and x2 looking? Do you still need to use a custom image or can you use normal fc43?
No, it looks like Fedora doesnāt interested in getting to work on Snapdragon XElite. Now itās only enthusiasts like @gurnben can drive this activity.
Hey, how is support for x and x2 looking? Do you still need to use a custom image or can you use normal fc43?
You cannot (yet) use a vanilla fedora image.
There is work ongoing to get it to where you can. At that point you will
be able to boot a normal image, but you will have to pass a custom
argument to tell it what device you have.
1 Like
How do I upload my custom attributes to the fedora 43 aarch64.iso image?
One answer would be reach out to the Arm SIG and work in it with them.
For most teams Matrix has taken over from IRC, contact details at Architectures/ARM - Fedora Project Wiki
1 Like
Hi, Iāve picked up 2 snapdragon machines . Iām not a dev in any way but how can I contribute? Could I offer remote access to my machines for example? :
[X1E-78-100] HP Omnibook X 14
[X1P-42-100] Surface Pro 12ā (2025 cheap model)
These chips are fantastic for pro audio work and the machines can be found cheap on ebay.
If thereās anything I can do to contribute, let me know 
I am thinking of getting an Asus Vivobook S15 AI+PC and i want to use linux on it. what is the status now? i saw elsewhere that F43 supports it supposedly with the latest linux kernel? but i dont see that anywhere on fedora related pages. only this page seems to discuss it at all and for F42.
F43 is supported using the same process documented here - as long as the system has a DeviceTree in the Linux Kernel!
The remaining bumps are:
- Camera Support
- Sleep Support (currently requires airplane mode)
hopefully thereās still hope for us acer swift 14 ai (11t) users, the current thinkpad dtb Iām using has some stuff that is sadly incompatible for the elite laptop.
ā¦so i ended up making a whole repo for the acer 14 ai laptop that have been not included in the latest kernel sources. i also added my own rendition of the qcom-firmware-extract called the qcom-firmware-folder-extract that you can guess now can extract from the FileRepository if the folder is near the script. GitHub - pixel844/qcom-acer-swift-14-helper: just some small work
Bro, my device is Swift 14-11, and I just saw your GitHub repository, itās so cool! Iām currently trying to launch it using your DTB, looking forward to hearing from you!
Unfortunately, the f43 aarch64 ISO cannot be booted.
thats because you need to do a weird trail of events in order to actually boot it up, first you need to get crpalmers livecd for the yoga slim7x downloaded, and boot it up, right after that you then while it boots need to press e into the boot entry where it will show you the device path to be the yoga slim, use the fallback /qcom/x1e78 thinkpad.dtb driver, tbf i totally forgot the full file path so you can use autocomplete by using tab while typing it. after you finish writing the temporary boot go and press ctrl and x to boot with your temp settings. this will take a few seconds and boom now you have a working boot enviroment, after this go to and install linux fedora 42 using the installer, download the dtb i made and wait until its finished flashing the os, after its done go install in the live cd the easy-chroot package . you will need open the disks program inside the live cd to see where your / for your disk is mounted at for your install copy the path of partition 3 and save it for easy chroot where you will need it for the command, sudo easy-chroot <the filepath> after your in chroot go to where you will need to do sudo nano /etc/default/grub and put GRUB_DEFAULT_DTB=āā now this is where you will be putting the file location for the dtb and where to put it. for me i put the dtb into /boot/loader/ in the install path and made it to GRUB_DEFAULT_DTB="/loader/acer-swift-14.dtb". and boom thats it thats all you really need to do in order to make it functional.
yo just updated my dtb its now been fully modified to make everything works, now im mostly just waiting till a new kernel drops that adds speaker support
Removed my prior post as I was able to get Fedora Rawhide installed by creating a live CD with the following GIT with some modificationsā¦GitHub - crpalmer/lenovo-yoga-fc42
I now have Fedora Rawhide successfully up and running on my T14s G6 with a few niggles. I had to create a startup script to remove and reload the module qcom_q6v5_pas after the KDE desktop starts to have sound and battery status work. No luck on bluetooth or the camera.
If anyone has gotten either working on a 6.18 kernel I would be interested in knowing the secret.
Iāve attempted to add the following to /etc/dracut.conf.d/qualcomm.conf as suggested in another thread. However, this just gets me a screen full of errors when I run dracut. Iām afraid Iām too much of a linux newbie to sort out when they all mean.
install_items+=" /lib/firmware/qcom/gen70500_sqe.fw /lib/firmware/qcom/gen70500_gmu.bin " # DPU
install_items+=" /lib/firmware/qca/hmtbtfw20.tlv /lib/firmware/qca/hmtnv20.b112 " # Bluetooth
install_items+=" /lib/firmware/qcom/x1e80100/LENOVO/21N1/* /lib/firmware/qcom/x1e80100/LENOVO/83ED/* "
install_items+=" /lib/firmware/ath12k/WCN7850/hw2.0/* "
do the recent linux kernel changes related to qualcom snapdragon x eliet support change the install process at all?
No, the new kernel hasnāt made it in to the new install images yet so no change . Suspect there wonāt be much as the device trees will still be needed. Not much change either once I updated to the 6.19 vanilla kernel on the T14s at least either. Still no camera, bluetooth or thunderbolt. Iāve pretty well given up on Linux on the Snapdragon and am going to try to sell the laptop at this point. Itās unfortunate that Qualcomm doesnāt seem to care to support Linux on these CPUās. 
Self Intro: Iām a FOSS enthusiast, kernel developer and Fedora contributor since 2006. After working 17 years for Red Hat working on variety of subjects including flickerfree boot, improving laptop support and MIPI camera support Iāve recently started at Qualcomm working on improving upstream support.
I would like to improve the user experience of running (Fedora) Linux on Qualcomm based Windows on Arm laptops. Iāve filed a Fedora 44 change proposal to make the Workstation Live ISO work OOTB without requiring any modifications: Changes/Automatic DTB selection for aarch64 EFI systems - Fedora Project Wiki
As for the dracut.conf snippets shared here, yes the kernel (adding firmware tags to modules) and dracut both need some work to ensure the right firmwares are included in the initrd. Note that the LENOVO/21N1 part in the shared dracut.conf.d drop-in configs is model specific and this is for the T14s gen 6 only. For the Yoga Slim 7 the 21N1 part should be replaced by 83ED. For other laptop models the firmware unfortunately is not part of linux-firmware.
As for camera and bluetooth support, Iām running a locally compiled kernel based on: https://gitlab.com/Linaro/arm64-laptops/linux/-/commits/qcom-laptops on a T14s gen 6. The camera needs some fixes to not be upside down and with that kernel-tree Bluetooth works OOTB for me, I just tried my Bose QC35-II headphones with a couple of music videos.
Iāll try to make a COPR with a patched kernel available, but it will take some time (at least a month likely) to make this happen.
2 Likes
Hey Hans! Nice to see you around.
Self Intro: Iām a FOSS enthusiast, kernel developer and Fedora contributor since 2006. After working 17 years for Red Hat working on variety of subjects including flickerfree boot, improving laptop support and MIPI camera support Iāve recently started at Qualcomm working on improving upstream support.
I would like to improve the user experience of running (Fedora) Linux on Qualcomm based Windows on Arm laptops. Iāve filed a Fedora 44 change proposal to make the Workstation Live ISO work OOTB without requiring any modifications: Changes/Automatic DTB selection for aarch64 EFI systems - Fedora Project Wiki
Awesome. Yeah, getting the right dtb in a place were you can use it and
having to manually pass it in is a pretty giant barrier for folks. ;(
There was some work to get the live media just including the right dtbs
so people could manually pass them at least:
I look forward to discussing the change.
As for the dracut.conf snippets shared here, yes the kernel (adding firmware tags to modules) and dracut both need some work to ensure the right firmwares are included in the initrd. Note that the
LENOVO/21N1part in the shared dracut.conf.d drop-in configs is model specific and this is for the T14s gen 6 only. For the Yoga Slim 7 the21N1part should be replaced by83ED. For other laptop models the firmware unfortunately is not part of linux-firmware.As for camera and bluetooth support, Iām running a locally compiled kernel based on: https://gitlab.com/Linaro/arm64-laptops/linux/-/commits/qcom-laptops on a T14s gen 6. The camera needs some fixes to not be upside down and with that kernel-tree Bluetooth works OOTB for me, I just tried my Bose QC35-II headphones with a couple of music videos.
Yeah, I have been daily driving a slim 7x most of this year.
For a while I did a custom kernel, but then I now have switched to just
the normal default rawhide kernel since upstream support has improved.
There are also some install issues I hit back when I installedā¦
like having to pass modprobe.blacklist=qcom_q6v5_pas when booting from
usb so it wouldnāt reset on loading and mess up the usb rootfs.
The camera doesnāt work here with stock fedora kernel, but bluetooth is
fine. Thereās various nice to have things missing, like support to power
off the keyboard backlight when you suspend and blink the power button
to show you are suspended, but overall it works nicely once you can get
installed.
Thereās likely a ton of work to do on power saving also. A full battery
here shows around 6-7 hours of battery life.
Iāll try to make a COPR with a patched kernel available, but it will take some time (at least a month likely) to make this happen.
Looking forward to it.
I have sucsessfully booted fedora rawhide
now im wondering, would it be possable to patch the fedora 43 raw image using files from the rawhide image inorder to make fedora 43 bootable?