Ubuntu Concept ♥️ Snapdragon X Elite

taprobane99 · March 31, 2026, 12:42pm

Is there a way to install previous kernels alongside 7.0? My Slim 7x worked with my USB-C DP external monitor on 9th March, but doesn’t work now. So I want the exact kernel from then.

tobhe · March 31, 2026, 12:46pm

You can get all the old debs from https://launchpad.net/~ubuntu-concept/+archive/ubuntu/x1e/+packages?field.name_filter=linux&field.status_filter=&field.series_filter=questing

For example you could download https://launchpad.net/~ubuntu-concept/+archive/ubuntu/x1e/+files/linux-image-6.19.0-13-qcom-x1e_6.19.0-13.13_arm64.deb and https://launchpad.net/~ubuntu-concept/+archive/ubuntu/x1e/+files/linux-modules-6.19.0-13-qcom-x1e_6.19.0-13.13_arm64.deb
and then install them with apt install ./ linux-image-6.19.0-13-qcom-x1e_6.19.0-13.13_arm64.deb ./linux-modules-6.19.0-13-qcom-x1e_6.19.0-13.13_arm64.deb

haider5c · March 31, 2026, 5:02pm

i solve the software rendering issue in my surface pro 11 and enable hardware rendering first its was

OpenGL renderer string: llvmpipe (LLVM 21.1.8, 128 bits)

now

glxinfo | grep "renderer string"
OpenGL renderer string: Adreno X1-85

i install

git clone https://salsa.debian.org/debian/qcom-firmware-extract.git
cd qcom-firmware-extract
sudo ./qcom-firmware-extract

and then after reboot nothing work but i found the issue with the ZAP shader (bitlocker disabled) and since no microsoft folder so simply

sudo mkdir -p /lib/firmware/qcom/x1e80100/microsoft/

sudo cp /lib/firmware/updates/qcom/qcom/x1e80100/microsoft/Denali/*.mbn /lib/firmware/qcom/x1e80100/microsoft/

sudo cp /lib/firmware/updates/qcom/qcom/x1e80100/microsoft/Denali/gen70500* /lib/firmware/qcom/ 2>/dev/null

and finally update

sudo update-initramfs -u

and then reboot

haider5c · March 31, 2026, 7:14pm

about the Surface Pro 11 (X Elite) Wi-Fi: Firmware Loaded, but Stuck on SAM “Hard Block”

Hardware: Surface Pro 11

Internal Wi-Fi: Qualcomm WCN7850 (hw2.0)

I have successfully resolved the initial firmware loading issues. The ath12k driver is now attaching to the hardware, but the interface is stuck in a Hard Block state that cannot be cleared via rfkill.

Steps taken to reach this point:

Firmware Extraction: Extracted wlanfw20.mbn from Windows DriverStore and renamed/aliased to firmware.bin and amss.bin.

Power Management: Extracted and decompressed m3.bin to resolve the MHI POWER_ON(2) timeout (Error -110).

Board Data: Tested several BDFs. Currently using bdwlan_wcn785x_2p0_ncm825_QC_revB.elf renamed to board.bin.

Result: The kernel successfully identifies the hardware (chip_id 0x2, soc_id 0x40170200) and creates the interface wlP4p1s0.

The Blocker: Despite the driver being ready, rfkill reports phy0 as Hard blocked: yes. Since the SP11 lacks a physical kill switch, it appears the Surface Aggregator Module (SAM) is holding the radio power (GPIO) low.

haider5c · March 31, 2026, 7:19pm

the funny thing i cant enable usb wifi adapter anymore

celticwarrior · March 31, 2026, 7:37pm

Any FN+F… key combo is also a physical switch.

taprobane99 · March 31, 2026, 9:03pm

Uh-oh - I have a problem!

I tried sudo do-release-upgrade -d from [Ubuntu 25.10, latest kernel] and my Slim 7x rebooted half way through installing it. Now it won’t go beyond the Ubuntu logo. I have the latest x1e resolute iso on a usb stick. What commands from live usb (or GRUB) can I use to fix the upgrade?

glathe · April 1, 2026, 4:08am

It did run through, though? If yes, “just” add the devicetree line in grub.cfg. I have written a bit about this: Home · jglathe/linux_ms_dev_kit Wiki · GitHub . Also, there’s a discussion thread re sp11/sp12 on my repo, and a Matrix room with ongoing discussion (link is in the thread).

gianlucamirci · April 1, 2026, 8:11am

Hi,
I’m experiencing a Bluetooth A2DP issue with my Marshall Emberton II speaker on a ThinkPad T14s Gen 6 with Snapdragon X Elite, running Ubuntu Concept (kernel 7.0.0-22-qcom-x1e) with KDE Plasma 6.6.3.

Problem:

Speaker shows “connection failed” in Bluetooth manager, but eventually shows as connectedNo audio output (A2DP profile fails to establish)
Connection drops after a few minutes
Error in logs: avdtp_connect_cb() connect to 50:5E:5C:14:6F:F9: Connection reset by peer (104)

What works:
Bluetooth controller is detected and firmware loads correctly (hmtbtfw20.tlv, hmtnv20.b112)
Other Bluetooth devices (mouse, keyboard) work fine
The same speaker worked on earlier Ubuntu Concept builds with kernel 6.x and GNOME 45

What I’ve tried:
Paired/re-paired multiple times
Tested with Blueman and KDE Bluetooth manager (same result)
Forced SBC codec only in PipeWire config
Disabled hardware volume control
Disabled headset profiles in /etc/bluetooth/main.conf
Tested with PulseAudio (same issue, no audio at all)
Firmware is up-to-date on the speaker

System info:
Kernel: 7.0.0-22-qcom-x1e
Desktop: KDE Plasma 6.6.3
PipeWire: 1.6.2
BlueZ: 5.85
Speaker: Marshall Emberton II (MAC: 50:5E:5C:14:6F:F9)

Hypothesis:
This appears to be a kernel 7.0 regression or A2DP protocol compatibility issue specific to the Qualcomm X1E-78-100 (X1E78100) Bluetooth controller. The speaker worked on kernel 6.x with GNOME 45 on the same hardware.

Any suggestions or known workarounds? Happy to provide more logs if needed.

haider5c · April 1, 2026, 10:49am

anyone have the same issue with audio with surface pro 11

[sudo: authenticate] Password:  
[    1.206231] remoteproc remoteproc0: adsp is available
[    1.217166] remoteproc remoteproc0: powering up adsp
[    1.224592] remoteproc remoteproc1: cdsp is available
[    1.226170] remoteproc remoteproc1: powering up cdsp
[    1.226421] remoteproc remoteproc0: Booting fw image qcom/x1e80100/microsoft/Denali/qcadsp8380.mbn, size 22092168
[    1.228173] remoteproc remoteproc1: Booting fw image qcom/x1e80100/microsoft/Denali/qccdsp8380.mbn, size 3072424
[    1.380252] remoteproc remoteproc1: remote processor cdsp is now up
[    1.580644] remoteproc remoteproc0: remote processor adsp is now up
[    1.610194] qcom,apr 6800000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:1
[    1.610308] qcom,apr 6800000.remoteproc:glink-edge.adsp_apps.-1.-1: Adding APR/GPR dev: gprsvc:service:2:2
[    4.170529] qcom,fastrpc 32300000.remoteproc:glink-edge.fastrpcglink-apps-dsp.-1.-1: no reserved DMA memory for FASTRPC
[    4.197589] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@1: Adding to iommu group 9
[    4.225268] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@2: Adding to iommu group 10
[    4.226376] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 11
[    4.231046] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 12
[    4.233886] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 13
[    4.236479] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 14
[    4.239434] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 15
[    4.243220] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@8: Adding to iommu group 16
[    4.249198] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@10: Adding to iommu group 17
[    4.255728] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@11: Adding to iommu group 18
[    4.261182] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@12: Adding to iommu group 19
[    4.264449] platform 32300000.remoteproc:glink-edge:fastrpc:compute-cb@13: Adding to iommu group 20
[    4.266313] qcom,fastrpc 6800000.remoteproc:glink-edge.fastrpcglink-apps-dsp.-1.-1: no reserved DMA memory for FASTRPC
[    4.269731] platform 6800000.remoteproc:glink-edge:fastrpc:compute-cb@3: Adding to iommu group 21
[    4.270584] platform 6800000.remoteproc:glink-edge:fastrpc:compute-cb@4: Adding to iommu group 22
[    4.271886] platform 6800000.remoteproc:glink-edge:fastrpc:compute-cb@5: Adding to iommu group 23
[    4.272548] platform 6800000.remoteproc:glink-edge:fastrpc:compute-cb@6: Adding to iommu group 24
[    4.273330] platform 6800000.remoteproc:glink-edge:fastrpc:compute-cb@7: Adding to iommu group 25
[    9.701300] platform 6800000.remoteproc:glink-edge:gpr:service@1:dais: Adding to iommu group 26

aplay: device_list:279: no soundcards found...

taprobane99 · April 1, 2026, 2:41pm

I fixed my failed do-release-upgrade -d using the following from a live usb (actually these are generic commands, not specific to x elite)

/mnt and /mnt/boot/efi
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
sudo chroot /mnt
dpkg -configure -a
apt install -f
apt update
apt dist-upgrade

On a different topic, any x elite users with an OLED panel can now add this to their ~/.config/monitors.xml for more accurate colours:

<colormode>sdr-native</colormode> within <monitor></monitor>

haider5c · April 1, 2026, 4:20pm

my surface pro 11 current state

1. GPU & Firmware Success

Issue: Adreno 750 (X1-85) failed to load firmware with error -2.
Fix: Manual decompression of gen70500_sqe.fw.zst and gen70500_gmu.bin from the Qualcomm firmware tree.
Result: Full Vulkan/OpenGL hardware acceleration via freedreno.
Observation: System defaults to llvmpipe without the specific gen70500 SQE firmware.

2. Audio Subsystem Progress

Topology: Successfully utilized the Lenovo X13s (SC8280XP) topology binary as a compatible base.
Hardware State: Card 0 initialized and visible in aplay -l.
Blocker: ALSA Use Case Manager (UCM2) name-matching. The hardware reports as X1E80100Microso (truncated ID), causing a mismatch in standard PipeWire/PulseAudio sink creation.

3. Bluetooth State

Transport: UART-based QCA WCN7850.
Firmware: hmtbtfw20.tlv and hmtnv20.bin successfully loaded.
Blocker: hci0 node is created but fails hciconfig up with Error 95 (Operation not supported), suggesting a power-sequencing or baud-rate handshake issue in the hci_uart driver for this specific Surface revision.

# Verify GPU
vulkaninfo --summary | grep deviceName  # Should return Adreno X1-85

# Verify Audio Card
cat /proc/asound/cards                  # Should show Card 0 [X1E80100Microso]

# Verify CPU Scaling
cpupower frequency-info                 # Should show SCMI driver up to 3.42GHz

haider5c · April 1, 2026, 4:21pm

sadly its do nothing

garganite · April 2, 2026, 8:34am

This is good news for this project right? How quickly does this Dell firmware get into the latest iso images here? I installed Ubuntu on my Dell XPS 9345 a few months ago but a recent update meant it couldn’t boot into the desktop. Hoping stuff like this improves the situation. Really appreciate all the work that’s going into this

https://www.phoronix.com/news/Dell-XPS-13-9345-EC-Driver

https://www.phoronix.com/news/Dell-Firmware-XPS-13-9345

tobhe · April 2, 2026, 3:40pm

It is indeed. Both should be included in the latest updates. the firmware change is in resolute (official archive) and the EC driver is included in the latest questing and resolute PPA kernels to give it some test exposure.

grealish · April 2, 2026, 11:36pm

I spotted PPA shows now Kernal 7.0.0-29-qcom-x1e available, gave it a spin on the T14s G6 LCD and so far, stable, suspend is working way better, camera still grainy and not the same quality as in W11 WoA (dual-boot), unsure about DP-Atl USB-C hot plugging displays, that still sketchy

here’s what It looks like:

[  702.263464] PM: suspend entry (deep)
[  702.267088] Filesystems sync: 0.003 seconds
[  702.311565] Freezing user space processes[  702.313518] Freezing user space processes completed (elapsed 0.001 seconds)[  702.313522] OOM killer disabled.[  702.313523] Freezing remaining freezable tasks
[  702.314528] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[  702.314530] printk: Suspending console(s) (use no_console_suspend to debug)
[  702.517128] Disabling non-boot CPUs …[  702.518734] migrate_one_irq: 34 callbacks suppressed[  702.518736] IRQ146: set affinity failed(-22).[  702.518753] IRQ210: set affinity failed(-22).[  702.518754] IRQ211: set affinity failed(-22).[  702.519288] IRQ261: set affinity failed(-22).[  702.519332] psci: CPU11 killed (polled 0 ms)[  702.521626] IRQ146: set affinity failed(-22).[  702.521639] IRQ210: set affinity failed(-22).[  702.521640] IRQ211: set affinity failed(-22).[  702.521756] IRQ261: set affinity failed(-22).[  702.521785] psci: CPU10 killed (polled 0 ms)[  702.523487] IRQ146: set affinity failed(-22).[  702.523499] IRQ210: set affinity failed(-22).[  702.523641] psci: CPU9 killed (polled 0 ms)[  702.527006] psci: CPU8 killed (polled 0 ms)[  702.532155] psci: CPU7 killed (polled 0 ms)[  702.535581] psci: CPU6 killed (polled 0 ms)[  702.540711] psci: CPU5 killed (polled 0 ms)[  702.547378] psci: CPU4 killed (polled 1 ms)[  702.551363] psci: CPU3 killed (polled 1 ms)[  702.553904] psci: CPU2 killed (polled 0 ms)[  702.557077] psci: CPU1 killed (polled 0 ms)[  702.558553] Enabling non-boot CPUs …[  702.558936] Detected PIPT I-cache on CPU1[  702.558971] GICv3: CPU1: found redistributor 100 region 0:0x00000000170c0000[  702.559448] CPU1: Booted secondary processor 0x0000000100 [0x512f0011][  702.561132] CPU1 is up[  702.561396] Detected PIPT I-cache on CPU2[  702.561420] GICv3: CPU2: found redistributor 200 region 0:0x0000000017100000[  702.561859] CPU2: Booted secondary processor 0x0000000200 [0x512f0011][  702.562826] CPU2 is up[  702.563085] Detected PIPT I-cache on CPU3[  702.563111] GICv3: CPU3: found redistributor 300 region 0:0x0000000017140000[  702.563554] CPU3: Booted secondary processor 0x0000000300 [0x512f0011][  702.564645] CPU3 is up[  702.566829] Detected PIPT I-cache on CPU4[  702.566899] GICv3: CPU4: found redistributor 10000 region 0:0x0000000017180000[  702.567545] CPU4: Booted secondary processor 0x0000010000 [0x511f0011][  702.571946] CPU4 is up[  702.572279] Detected PIPT I-cache on CPU5[  702.572324] GICv3: CPU5: found redistributor 10100 region 0:0x00000000171c0000[  702.572893] CPU5: Booted secondary processor 0x0000010100 [0x511f0011][  702.574761] CPU5 is up[  702.575082] Detected PIPT I-cache on CPU6[  702.575129] GICv3: CPU6: found redistributor 10200 region 0:0x0000000017200000[  702.575700] CPU6: Booted secondary processor 0x0000010200 [0x511f0011]
[  702.577754] CPU6 is up[  702.578076] Detected PIPT I-cache on CPU7[  702.578127] GICv3: CPU7: found redistributor 10300 region 0:0x0000000017240000[  702.578698] CPU7: Booted secondary processor 0x0000010300 [0x511f0011][  702.580933] CPU7 is up[  702.582990] Detected PIPT I-cache on CPU8[  702.583036] GICv3: CPU8: found redistributor 20000 region 0:0x0000000017280000[  702.583334] CPU8: Booted secondary processor 0x0000020000 [0x511f0011][  702.586293] CPU8 is up[  702.586473] Detected PIPT I-cache on CPU9[  702.586490] GICv3: CPU9: found redistributor 20100 region 0:0x00000000172c0000[  702.586726] CPU9: Booted secondary processor 0x0000020100 [0x511f0011][  702.587574] CPU9 is up[  702.587768] Detected PIPT I-cache on CPU10[  702.587786] GICv3: CPU10: found redistributor 20200 region 0:0x0000000017300000[  702.588023] CPU10: Booted secondary processor 0x0000020200 [0x511f0011][  702.588991] CPU10 is up[  702.589152] Detected PIPT I-cache on CPU11[  702.589171] GICv3: CPU11: found redistributor 20300 region 0:0x0000000017340000[  702.589407] CPU11: Booted secondary processor 0x0000020300 [0x511f0011]
[  702.590376] CPU11 is up

[  702.799923] mhi mhi0: Requested to power ON[  702.799955] mhi mhi0: Power on setup success[  702.894387] mhi mhi0: Wait for device to enter SBL or Mission mode[  703.287439] ath12k_wifi7_pci 0004:01:00.0: chip_id 0x2 chip_family 0x4 board_id 0xff soc_id 0x40170200[  703.287448] ath12k_wifi7_pci 0004:01:00.0: fw_version 0x110cffff fw_build_timestamp 2025-06-25 09:26 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.115823.3[  703.503828] OOM killer enabled.[  703.503832] Restarting tasks: Starting
[  703.505696] Restarting tasks: Done[  703.505712] efivarfs: resyncing variable state[  703.785824] efivarfs: finished resyncing variable state[  703.785918] random: crng reseeded on system resumption
[  703.799350] PM: suspend exit

taprobane99 · April 3, 2026, 10:13pm

I have the same problem on Slim 7x of a usb-c dp alt mode display not working, when it was working fine early March.

I tried booting with the 6.19 series kernels when it was working, but they don’t work. So there must be some package (drm, mesa) etc. that has a regression. Problem is I don’t know which package.

jeremiah-cornelius · April 4, 2026, 6:39pm

Excellent. I wish that the launchpad hosting wasn’t so very slow!

andorekandore · April 5, 2026, 5:57am

nice

im looking the mailing list but there are so many commits its hard to tell, but im wondering getting suspend working is a specific goal of 7.0.0 for qcom xe1?

currently this is the biggest issue i have so far (asus vivobook s15) so it would be super great if this is finally fixed ^^

markusmannheim · April 5, 2026, 10:42am

Thanks to those helping to build this. I just applied the latest updates and was thrilled to see progress.

Working: Nightlight (wasn’t previously)
Not working: Camera, speakers, microphone (Bluetooth audio is fine)

Hardware Information:

Hardware Model: Dell Inc. XPS 13 9345
Memory: 32.0 GiB
Processor: Oryon × 12
Graphics: Adreno X1-85
Disk Capacity: 1.0 TB

Software Information:

Firmware Version: 2.11.0
OS Name: Ubuntu 25.10
OS Build: (null)
OS Type: 64-bit
GNOME Version: 49
Windowing System: Wayland
Kernel Version: Linux 7.0.0-31-qcom-x1e