Unable to boot into IdeaPad Slim 5x through stubble.

[hardikpathakin-eng]

Ubuntu 26.04 and Fedora 44 have extended support for WoA devices using stubble. However, it still doesn't boot into the os. The pc just endlessly restarts into grub menu. I've been trying install Linux into my device for so long but all other methods fail to work for me. I raised an issue before into the stubble months ago and I think I was informed that the system should boot after 25.04. I don't know if it's because the difference in lcd and oled. Would be thankful if you please look into the issue. I will attach the required files.

apic.zip
lsusb_tree.txt
dmesg_full.txt

HWiNFO64.LOG

[jglathe]

I tried with the raw image to test, it fails within stubble already. Ok, I have an Ideapad 5 2in1 (83GH), slightly different. Tbh, neither one of these devices is upstreamed yet. It is running a stubble-activated kernel like a champ, though. No devicetree statement in the grub.cfg. Ubuntu 26.04. And with sound ootb 🤨

[jglathe]

The Fedora image adds an EFI boot menu entry to bring up its grub (Ubuntu can do the same, I hate it). However, the stubble fails badly. I can try and install my kernel on this image (which definitely has the Ideapad dtbs)... Oh and I can confirm, with the Ubuntu 26.04 kernel (stubble and all) - no dtb found, will just reboot. I can build a newer modified Resolute image with my kernel (6.19.14-jg-0), that would help.

[hardikpathakin-eng]

Thank you so much for your reply man. I'd really appreciate your assistance. I mean i can handle commands but idk I've never gotten the dtb done right when I do it myself. I'd really appreciate if there is something pretty built. I've been dying to use and explore linux a lil. Also my model is 14Q8X9. THANK YOU SO MUCHH AGAIN. Btw getting fedora to work would be great too

[1-Me-Abhi]

My device is same Idea slim5x but there is no LCD dtb in stubble so it won't boot

[jglathe]

@1-Me-Abhi yeah I know :) I don't know how, yet, and ofc I was busy doing stuff 😎 Like, getting audio via display outputs to actually work, which is a big item for me. Works on my Windows Dev Kit 2023 now, Snapdragon Dev Kit (and also Ideapads) will follow. Since the wdk is a daily driver console for me... GUI with sound and over display is a quality of computer life improvement.

[1-Me-Abhi]

Thanks for the update!
On my IdeaPad Slim 5x (14Q8X9, LCD):
Still hitting reboot loop due to missing LCD DTB (stubble)
Speaker audio is working on kernel 6.19.13-jg-2
Additional issue:
Wired networking / USB tethering is not working (no usable network over USB)
Let me know if you want me to test newer builds or capture anything specific (ACPI/EDID/dmesg) to help with the LCD DTB bring-up

[hardikpathakin-eng]

@jglathe Yeah it must get so busy🫴🎩(hats off). Was wondering how long it would take tho. Love your pfp btw lol. Ohh and alsoo, how far has the work been on battery life

[jglathe]

Battery life: They do constant improvements. Some benefit the budget models, some don't. Can't complain about battery life tbh. Not my primary concern.
Ethernet adapter not working is odd and points to an issue with usb2 repeaters. Would be good to have a dmesg after plugging that one in. Haven't had repeater issues for a long time, but Idon't have a slim5(x). I have a slim3x, though, and that one is a b*tch on a few frontiers.
Regarding a new image, well that should be doable this weekend I'd say. There are 2 possible ways, I would deliberately chose the faster one as a stubble-aware kernel which can't boot the slim5x lcd will not boot the slim5x lcd. There will be extra boot menu entries for slim5x oled and lcd, but the base is the latest daily resolute from 04/23.
I also experimented with actually replacing the kernel on the ISO, thus opening up the squashfs for... reasons, that one wouldn't really resolve the issue at hand. And was a hard task.
To use the extended images I wrote up a wiki entry. Still valid and the recommended way to do things. Also, the latest ISO now on Google Drive really should work to boot the slim5x. It installs 26.04, and it upgrades nicely.

[1-Me-Abhi]

❯ diff before.txt after.txt
1458a1459,1497

[ 608.494834] fda000.phy-switch: qmp_combo_switch_set() enter new_orientation=2, altmode=0, orientation=2
[ 608.494854] usb-1-ss1-sbu-mux-switch: gpio_sbu_switch_set() enter orientation=2, altmode=0, swapped=1
[ 608.494861] usb-1-ss1-sbu-mux-switch: gpio_sbu_switch_set() exit orientation=2, altmode=0, swapped=1
[ 608.494867] fda000.phy-mux: qmp_combo_mux_set() enter mode=1, altmode=0
[ 608.494873] usb-1-ss1-sbu-mux-mux: gpio_sbu_mux_set() enter mode=1, altmode=0
[ 608.494883] usb-1-ss1-sbu-mux-mux: gpio_sbu_mux_set() exit mode=1, altmode=0
[ 608.495778] fda000.phy-switch: qmp_combo_switch_set() enter new_orientation=2, altmode=0, orientation=2
[ 608.495784] usb-1-ss1-sbu-mux-switch: gpio_sbu_switch_set() enter orientation=2, altmode=0, swapped=1
[ 608.495789] usb-1-ss1-sbu-mux-switch: gpio_sbu_switch_set() exit orientation=2, altmode=0, swapped=1
[ 608.495874] fda000.phy-mux: qmp_combo_mux_set() enter mode=1, altmode=0
[ 608.495876] usb-1-ss1-sbu-mux-mux: gpio_sbu_mux_set() enter mode=1, altmode=0
[ 608.495881] usb-1-ss1-sbu-mux-mux: gpio_sbu_mux_set() exit mode=1, altmode=0
[ 608.495998] fda000.phy-mux: qmp_combo_mux_set() enter mode=1, altmode=0
[ 608.496003] usb-1-ss1-sbu-mux-mux: gpio_sbu_mux_set() enter mode=1, altmode=0
[ 608.496009] usb-1-ss1-sbu-mux-mux: gpio_sbu_mux_set() exit mode=1, altmode=0
[ 608.844353] fda000.phy-switch: qmp_combo_switch_set() enter new_orientation=2, altmode=0, orientation=2
[ 608.844373] usb-1-ss1-sbu-mux-switch: gpio_sbu_switch_set() enter orientation=2, altmode=0, swapped=1
[ 608.844380] usb-1-ss1-sbu-mux-switch: gpio_sbu_switch_set() exit orientation=2, altmode=0, swapped=1
[ 608.844387] fda000.phy-mux: qmp_combo_mux_set() enter mode=1, altmode=0
[ 608.844393] usb-1-ss1-sbu-mux-mux: gpio_sbu_mux_set() enter mode=1, altmode=0
[ 608.844402] usb-1-ss1-sbu-mux-mux: gpio_sbu_mux_set() exit mode=1, altmode=0
[ 608.845300] fda000.phy-switch: qmp_combo_switch_set() enter new_orientation=2, altmode=0, orientation=2
[ 608.845307] usb-1-ss1-sbu-mux-switch: gpio_sbu_switch_set() enter orientation=2, altmode=0, swapped=1
[ 608.845312] usb-1-ss1-sbu-mux-switch: gpio_sbu_switch_set() exit orientation=2, altmode=0, swapped=1
[ 609.200216] usb 3-1: new high-speed USB device number 4 using xhci-hcd
[ 609.326485] usb 3-1: New USB device found, idVendor=2717, idProduct=ff40, bcdDevice= 5.10
[ 609.326509] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 609.326516] usb 3-1: Product: POCO X6 5G
[ 609.326521] usb 3-1: Manufacturer: Xiaomi
[ 609.326527] usb 3-1: SerialNumber: 4b167bc2
[ 615.529324] usb 3-1: USB disconnect, device number 4
[ 615.936899] usb 3-1: new high-speed USB device number 5 using xhci-hcd
[ 616.064561] usb 3-1: New USB device found, idVendor=2717, idProduct=ff80, bcdDevice= 5.10
[ 616.064582] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 616.064589] usb 3-1: Product: POCO X6 5G
[ 616.064595] usb 3-1: Manufacturer: Xiaomi
[ 616.064600] usb 3-1: SerialNumber: 4b167bc2
[ 616.134012] rndis_host 3-1:1.0 usb0: register 'rndis_host' at usb-xhci-hcd.2.auto-1, RNDIS device, fa:44:01:2f:a9:b0
[ 616.156771] rndis_host 3-1:1.0 enxfa44012fa9b0: renamed from usb0
~
❯

before.txt

after.txt

`

[1-Me-Abhi]

USB tethering (RNDIS) unstable on X1E — repeated disconnects, no connectivity

issue with USB tethering

Device / Setup:

• Laptop: Lenovo IdeaPad Slim 5x
• Kernel: 6.19.13-jg-2-qcom-x1e

Problem:
USB tethering is detected, and the RNDIS interface is created successfully, but it is not usable:

• DHCP requests receive no response
• Static IP also doesn’t work
• Cannot ping the phone (192.168.42.129)

Key observation:
The USB connection is not stable. The device repeatedly disconnects and reconnects.

From dmesg:

• Device switches between ff40 and ff80 modes
• Frequent USB disconnect events
• rndis_host repeatedly registers/unregisters
• Type-C mux logs (gpio_sbu_switch_set) appear during this

This seems to indicate that the USB link itself is unstable, so packets never reach the phone.

What I tested:

• Replugging and toggling tethering
• Reloading drivers (rndis_host, cdc_ether)
• Manual IP configuration

No change.

Conclusion:
This looks like a USB/Type-C or controller issue rather than a networking configuration problem.

Let me know if you want additional logs .

[hardikpathakin-eng]

@jglathe unfortunately, the 26.04 on Google drive did not work. The 25.10 one did but I couldn't figure out how to change grub after installing Ubuntu. I just got frustrated after errors while mounting and stuff. Also 26.04 didn't boot IdeaPad slim 5x LCD at all. I tried all the entries

[jglathe]

It looks like it is recognized as an USB2 device (High Speed is USB2), and then additionally as the same device. Not quite sure waht to make of this, does a normal mouse work on that port? Or is it type-c? Then something is really amiss.

[1-Me-Abhi]

It type c

[jglathe]

Ok does it work reliably on Windows? I mean, 5GbE could be some odd chipset or something, but it needs SuperSpeed connections, only USB2 (480MBit) will not cut it. I have only one 2,5GbE adapter which is Type-A and lives at a NAS for 5 years now, can't compare. All other type-c devices with Ethernet are hubs, and they work.

[jglathe]

The 25.10 one did

Oh but that one is archived because broken for install. Still a bit curious result, will check. I checked prices on the Slim5x here, will not go that route. My zoo is big enough 🤪