Problems Booting Old Laptop HP 340 G1 (2014 laptop)

I migrated from Windows to Linux (Fedora 42 SilverBlue/Kinoite) a laptop model HP 340 G1, replaced their SATA 1TB by a mSATA 500GB, but I did not notice that their bios only support SATA, anyway tried to install Fedora 37 (then updated to 42 Silverblue, then rebase to Kinoite because a problem with mesa and old intel graphics) and worked.

… but is always there a problem, I need to turn on and turn off 4 to 6 times my laptop, disconnecting all USBs, to finally turn on my OS. the first turn on is always an empty screen, the second is empty screen with finally kernel panic, the third and the next turn on are the grub option sometimes with only empty screen and other times’ kernel panic, all this until finally my OS finally load. This problem is a bit annoying. Is there any method to load the drivers for mSATA to solve my booting problem? Or any suggestion?

Hi Jn, newbie here :smiley:

I recently migrated my old 2014 ThinkPad to Fedora workstation. I wanted to go straight to SilverBlue, but as a Linux newbie found the transition too complex, so went for Fedora workstation, and have been practising with SilverBlue in VirtualBox to get the hang of it.

The only other thing I can think of, although I don’t really understand your problem, is you have to update from one edition to the next, rather than ‘jumping’

So from 37 you’d have to go to 38, then 39 etc.

Apologies if I’m completely off the mark :grin:

1 Like

The software store updates my system automatically.

When I installed version Fedora 37 Silverblue the first boot was not problems, only after upgrade to 42 i have this problem.

Also, I did same install in 2 laptops, only my old laptop hp 340 G1 without mSATA bios support have this problem, I think the problem is for drivers.

Okay well I’m out of my depth then. Good luck on a solution :+1:

1 Like

https://www.cpumedics.com/lite-on-lmt-32l3m-32gb-msata-solid-state-ssd-drive/ lists HP 340 G1 as compatible. Maybe you can update your BIOS.

There could be diagnostic messages for the failed boots available using something like journalctl --no-hostname -b -<N> -p 3 where N is the number for the previous boots.
journalctl commands are run in a terminal. Post relevant entries as pre-formatted text. If some lines end in >, add | cat to the end of the journalctl command line to wrap lines in the terminal.

Hardware more than 10 years old has a high failure rate, and the current economic conditions combined with the need for large enterprises to move off Windows 10 has created a flood of “reconditioned” enterprise grade laptops less than 10 years old that are significantly faster and more capable than your current model.

1 Like

Looks like last update fixed anything, but anyway, still I need to reboot 2 times.

Is there any possibility to integrate light DeepSeek to run commands in the grub?