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?
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?
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.
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?
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.
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?
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!
Odd. I thought that was fixed a while back. ;(
Try:
echo start > /sys/class/remoteproc/remoteproc0/state
echo start > /sys/class/remoteproc/remoteproc1/state
I have that in my startup scripts on the Debian install on the machine 
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.
I see this is mostly resolved.
As you found out unfortunately install Fedora 44 is still not the plug-and-play experience it should be.
Because of this I’ve written instructions documenting the necessary kernel-commandline workarounds for this, as well as providing post-install instructions to fix things like the boot hanging for 90 seconds and the missing battery / sound issue:
This also contains a separate section explaining why these workarounds are necessary for now and what is being done / needs to be done to remove the need for these workarounds.
Before I ever powered this machine on, I removed the original SSD with the Windows installation and installed a new SSD to install Linux.
How doomed am I with my original launch-edition firmware that has never been updated? Is there any way to update any of the firmware from Linux with fwupdmgr or something yet, or do I need to dig out the original SSD and boot it up just to update firmware?
Also, Hans, if you don’t mind, I’d like to send a DM about some other questions I have specifically for you.
Launch edition BIOS probably has some issues which may be a problem with Linux. But there are some instructions to update the BIOS from a USB stick here:
and once you’ve Linux up and running a slightly more simple way to update the BIOS in the future is documented here:
The runtime loadable firmwares (/lib/firmware/… files) are in linux-firmware for this laptop, so you don’t need to get those from the Windows partition.
Sure that is fine, but I prefer email over a DM: johannes.goede@oss.qualcomm.com
Sorry, I was maybe unclear: my Yoga Slim 7X has been running Debian with a series of hand-crafted artisanal small-batch kernels I made myself. I’ve got most of my hardware working under Debian except for my audio, I managed to extract all those firmware files ages ago before they were upstream.
I’m mostly exploring Fedora here because I’m tired of trying to figure out why none of my kernel builds since 6.15.2 have booted properly.
p.s. The USB BIOS update method has only been tested on ThinkPads which at least on the x86_64 side often do things differently then to non ThinkPad Lenovo lines. Still worth a try though in the worst case scenario it will simply not work.
As usual make sure the laptop is charged to at least 70% and connected to a charger before doing a BIOS update.
Same. I got my slim7x, and did boot it in windows and applied updates, but after that I removed the windows drive and haven’t updated firmware since.
Swapping the nvme is a big pain on these, because they use clips instead of screws, so it seems like it’s just about to break before it comes loose. ;(
Finally: as far as I can tell, lenovo is not publishing any of the bios / firmware updates for download anywhere for this laptop. There are (so I hear) updates that show up in windows, but laptops and netbooks :: yoga series :: yoga slim 7 14q8x9 - Lenovo Support US never shows any available to download, so I don’t think there’s any way to upgrade from the linux side unless you can find the updates to download…