Re: [PATCH 0/7] arm64: dts: qcom: IdeaCentre Mini 01Q8X10 Hamoa + Purwa
From: Mostafa Saleh
Date: Wed Sep 09 2026 - 08:58:46 EST
On Tue, Sep 08, 2026 at 08:15:27PM +0200, Jens Glathe wrote:
> Hi Mostafa,
>
> On 08.09.26 19:47, Mostafa Saleh wrote:
> > On Tue, Sep 08, 2026 at 05:04:44PM +0200, Jens Glathe wrote:
> > > Hi Mostafa,
> > >
> > > This is my .config [1].
> > >
> > > [1]: https://pastebin.com/QhDizqCB
> > Thanks! I tested with your config plus
> > - CONFIG_EFI_ARMSTUB_DTB_LOADER=y otherwise I can't load my device
> > tree from UEFI shell
> > - CONFIG_SERIAL_QCOM_GENI=y, otherwise I can't see the console.
> >
> > Booting in EL2 is similar to before with SMMUv2 errors.
>
> For that you would need the patch as listed before: [2]
>
> [2]: https://github.com/jglathe/linux_ms_dev_kit/tree/b4/x1-el2-unfuck
>
> This should give you boot on EL2.
>
> > Booting in EL1 hangs with timeouts and missing suppliers:
> > [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x512f0011]
> > [ 0.000000] Linux version 7.3.0-rc1-next-20260904+ (smostafa@xxxxxxxxxxxxxxxxxxxxxxx) (Debian clang version 21.1.8 (3), Debian LLD 21.1.8) #2 SMP PREEMPT_DYNAMIC Tu6
> > [ 0.000000] KASLR enabled
> > [ 0.000000] Machine model: Lenovo IdeaCentre Mini 01Q8X10 (Purwa)
> > [ 0.000000] earlycon: qcom_geni0 MMIO:0x0000000000894000 (options '')
> > [ 0.000000] printk: legacy bootconsole [qcom_geni0] enabled
> > [ 0.000000] CPU features: SYS_ID_AA64MMFR0_EL1[63:60]: forced to 1
> > [ 0.000000] ITS@0x0000000017040000: Devices Table too large, reduce ids 32->19
> > [ 0.000000] ITS@0x0000000017040000: Devices too large, reduce ITS pages 1024->256
> > [ 0.163152] qcom-pcie 1c00000.pcie: supply vdda not found, using dummy regulator
> > [ 0.163313] qcom-pcie 1c08000.pcie: supply vdda not found, using dummy regulator
> > [ 0.168334] clk: Not disabling unused clocks
> > [ 0.168336] PM: genpd: Not disabling unused power domains
> > [ 0.170770] qcom-pcie 1c00000.pcie: supply vddpe-3v3 not found, using dummy regulator
> > [ 0.178347] qcom-pcie 1c08000.pcie: supply vddpe-3v3 not found, using dummy regulator
> > [ 0.184718] qcom-pcie 1c00000.pcie: supply vdda not found, using dummy regulator
> > [ 0.211932] Warning: unable to open an initial console.
> > [ 0.212057] qcom-pcie 1c00000.pcie: supply vddpe-3v3 not found, using dummy regulator
> > [ 0.213907] qcom-pcie 1c08000.pcie: supply vdda not found, using dummy regulator
> > [ 0.213928] qcom-pcie 1c08000.pcie: supply vddpe-3v3 not found, using dummy regulator
> > [ 0.244210] qcom-pcie 1c08000.pcie: supply vdda not found, using dummy regulator
> > [ 0.244275] qcom-pcie 1c00000.pcie: supply vdda not found, using dummy regulator
> > [ 0.251833] qcom-pcie 1c08000.pcie: supply vddpe-3v3 not found, using dummy regulator
> > [ 0.259418] qcom-pcie 1c00000.pcie: supply vddpe-3v3 not found, using dummy regulator
> > [ 10.213618] qcom-pcie 1bf8000.pcie: supply vdda not found, using dummy regulator
> > [ 10.214873] arm-smmu 3da0000.iommu: deferred probe timeout, ignoring dependency
> > [ 10.228713] arm-smmu 3da0000.iommu: probe with driver arm-smmu failed with error -110
>
> Since you don't load firmwares, maybe try these? However, I was able to boot
> and install with the Ubuntu Resolute ISO by providing the dtb, without the
> firmwares. Odd.
>
> > I believe we are testing on different SoCs from your fastfetch:
> > CPU: Qualcomm Snapdragon X Elite 1E80100 (8) @ 2.96 GHz
> >
> > While mine:
> > CPU: Qualcomm Snapdragon X Elite 1P42100 (8) @ 2.96 GHz
> >
> > I enabled CONFIG_QCOM_SOCINFO which shows:
> > [root@alarm ~]# cat /sys/devices/soc0/soc_id
> > 635 # which does not exist in qcom,ids.h
> > [root@alarm ~]# cat /sys/devices/soc0/revision
> > 1.0
> Looks like nope:
>
> root@mini-x-jg:~# cat /sys/devices/soc0/soc_id
> 635
> root@mini-x-jg:~# cat /sys/devices/soc0/revision
> 1.0
>
> We have the same SoC, maybe different binning. You could try to boot up with
> the extended Resolute ISO to boot without firmwares [3]. It contains the
> same dtb.
>
> [3]:
> https://drive.google.com/drive/folders/1sc_CpqOMTJNljfvRyLG-xdwB0yduje_O
>
Thanks! I can boot ubuntu with:
resolute-desktop-arm64+x1e-20260831_extended_jg.iso
I figured out the issue, the problem is that I am using the console
which is missing. And all the warnings in the logs were just a red
herring.
With that patch on top of your device tree I can fully boot:
diff --git a/arch/arm64/boot/dts/qcom/x1-lenovo-ideacentre-mini-01q8x10.dtsi b/arch/arm64/boot/dts/qcom/x1-lenovo-ideacentre-mini-01q8x10.dtsi
index b720622c5d90..973e603bbb6a 100644
--- a/arch/arm64/boot/dts/qcom/x1-lenovo-ideacentre-mini-01q8x10.dtsi
+++ b/arch/arm64/boot/dts/qcom/x1-lenovo-ideacentre-mini-01q8x10.dtsi
@@ -13,7 +13,7 @@ / {
chassis-type = "desktop";
aliases {
- serial0 = &uart14;
+ serial0 = &uart21;
};
wcd938x: audio-codec {
@@ -1183,3 +1183,8 @@ &usb_mp_qmpphy0 {
status = "okay";
};
+
+&uart21 {
+ compatible = "qcom,geni-debug-uart";
+ status = "okay";
+};
However, the kernel logs are extremely verbose (I have 39 warnings)
Disabling MDSS makes it cleaner:
diff --git a/arch/arm64/boot/dts/qcom/purwa-lenovo-ideacentre-mini-01q8x10.dts b/arch/arm64/boot/dts/qcom/purwa-lenovo-ideacentre-mini-01q8x10.dts
index 9813a570cf69..8dc038566f93 100644
--- a/arch/arm64/boot/dts/qcom/purwa-lenovo-ideacentre-mini-01q8x10.dts
+++ b/arch/arm64/boot/dts/qcom/purwa-lenovo-ideacentre-mini-01q8x10.dts
@@ -40,3 +40,34 @@ &remoteproc_cdsp {
status = "okay";
};
+
+
+&mdss {
+ status = "disabled";
+};
+
+&mdss_dp0 {
+ status = "disabled";
+
+};
+
+&mdss_dp0_out {
+ status = "disabled";
+};
+
+&mdss_dp1 {
+ status = "disabled";
+
+};
+
+&mdss_dp1_out {
+ status = "disabled";
+};
+
+&mdss_dp2 {
+ status = "disabled";
+};
+
+&mdss_dp2_out {
+ status = "disabled";
+};
I do not have any media attached nor drivers enabled, but that
shouldn't make the logs that verbose, I can dig more into it.
One other problem, is that there is a missing a PCI bus with the WIFI
card:
0005:00:00.0 PCI bridge: Qualcomm Technologies, Inc SC8380XP PCIe Root Complex [Snapdragon X / X Plus / X Elite]
0005:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 1b)
0006:00:00.0 PCI bridge: Qualcomm Technologies, Inc SC8380XP PCIe Root Complex [Snapdragon X / X Plus / X Elite]
0006:01:00.0 Non-Volatile memory controller: SK hynix Platinum P41/PC801 NVMe Solid State Drive
Compared to with my device tree:
0004:00:00.0 PCI bridge: Qualcomm Technologies, Inc SC8380XP PCIe Root Complex [Snapdragon X / X Plus / X Elite]
0004:01:00.0 Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] (rev 01)
0005:00:00.0 PCI bridge: Qualcomm Technologies, Inc SC8380XP PCIe Root Complex [Snapdragon X / X Plus / X Elite]
0005:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 1b)
0006:00:00.0 PCI bridge: Qualcomm Technologies, Inc SC8380XP PCIe Root Complex [Snapdragon X / X Plus / X Elite]
0006:01:00.0 Non-Volatile memory controller: SK hynix Platinum P41/PC801 NVMe Solid State Drive
Thanks,
Mostafa
> with best regards
>
> Jens
>