Has anybody booted F44 on a Lenovo Yoga Slim 7X?

Ask Fedora
1

I’ve tried the beta, the latest Fedora-44-20260405.n.0, and Fedora-Rawhide-20260403.n.0, and I can see the boot menu, but when I try to choose “Install Fedora” my screen goes black and then my keyboard backlight goes black and then my laptop reboots.

Am I holding it wrong?

2

Welcome to Fedora @slashclee

I could find several topics with the Lenovo model you mentioning. Did you go thru tem to get an overview of the problem?

3

Hi @ilikelinux,

Thanks for replying! Yes, I did search before posting.

None of the results I found seemed relevant since they’re either not for my specific device (like ThinkPad L380 Yoga stylus input no longer rotates with screen which is an Intel, or Audio issues on Lenovo Yoga Slim 7i (Gen 10 - 14ILL10), also intel not Snapdragon X1)… or the results are old enough to be irrelevant (like this F41 discussion Issues installing Linux on Lenovo Yoga Slim 7 (Snapdragon X Elite)) or it’s a long thread with lots of posts and nothing specific to F44 like this F42 thread Snapdragon X Elite Fedora 42 System Bring-Up (and looking for collaborators or SIGs)!

So, yes, I’ve gone through the search results and any related threads I could find, and I found a tip in that F42 thread to try booting with modprobe.blacklist=qcom_q6v5_pas (thanks @kevin for the suggestion!) but that didn’t work for me on the F44 beta, the latest F44 nightly, or Rawhide.

F44 specifically is supposed to include Changes/Automatic DTB selection for aarch64 EFI systems - Fedora Project Wiki to make booting on arm64 laptops like mine work better, but it doesn’t seem to be working out yet.

4

Do note that those changes are “Fedora Live ISO images” only.

I think you mentioned you are trying to use the netboot iso?

What happens when you boot a live iso?

5

Ah, somehow I missed that. I had tried the raw image for the F44 beta and I tried the netboot ISOs for F44-nightly and Rawhide.

Grabbed this: Fedora-44-20260406.n.0 and wrote it to a USB flash drive.

Without modifying the kernel args, I get dumped to a text console with errors starting various services like dev-tpm0.device (but the right DTB must be loading at least, since it’s not crashing or rebooting). Lots of errors about failed to read inode meta block on device loop0.

If I add the blacklist option above, instead of a text console I get a bright blue background with no mouse cursor or UI of any kind, and then a few minutes later the machine reboots.

1 Like
6

As noted in the change:

Before booting the kernel commandline must be edited in grub to add " clk_ignore_unused pd_ignore_unused"

try that?

7

Heyyy, there we go! Booted up after a few minutes, and now I can see the desktop! But my battery status and my wifi aren’t working, hm. Well, this is at least usable enough for me to get going from here. Thanks for the kernel parameters!

8

Odd. I thought that was fixed a while back. ;(

Try:

echo start > /sys/class/remoteproc/remoteproc0/state
echo start > /sys/class/remoteproc/remoteproc1/state

1 Like
9

I have that in my startup scripts on the Debian install on the machine :slight_smile:

But I haven’t had much luck booting stock Debian kernels on this thing and building my own is time-consuming… it would be real nice to have a distribution where I don’t need to think about the DTB files.