[RESOLVED] Linux wont start on AMD without nomodeset

[Luis_Cunha]

@Luis_Cunha

You are right, but when I run journalctl --list-boots, the boots without nomodeset are not there, so when I was doing -b-1 I was not getting the previous (without nomodeset) but the one before.

This means I again don’t know how to get more info.

Just to confirm, I noted the time of boot 0 on --list-boots, I did about 10 boots without nomodeset and booted again, when running --list-boots again, what was previously boot 0 was now -1, so none of the other boots were saved.

[Mario_Limonciello]

Got it; so what’s happening is that once this issue occurs the system is stalled so it can’t flush the logs out to disk.

IMO given this works with plenty of other people on Fedora 39 with no changes, something must be awry with your hardware/firmware setup (either a RAM incompatibility issue or BIOS corruption). Here’s what I’d think you should do:

1. Try to “reset BIOS default settings”.
2. fwupdmgr reinstall the firmware.
3. Double check the speed/brand for the RAM against what Framework suggested.

If none of those help I think you should contact Framework support for next steps.

[Luis_Cunha]

Thanks

[Matt_Hartley]

@Luis_Cunha

I’ve tried Fedora 39 and Mint 21.2 Edge, without setting nomodeset the installers won’t even start, after install if I don’t have nomodeset it also won’t boot.

With nomodeset I can’t use any external monitor, to do my work I need to connect my external monitor, so it’s not a good workaround.

The strange thing is that with nomodeset I’ve seen it crash in several different ways, not a single one.

Any help? Thanks.

Edit: There are other problems, but this one is the worse for now, if I solve this at least I can start using the laptop.

Feel like there must be something else at play. On a current ISO of Fedora 39, it will absolutely boot up successfully on 3.03 BIOS unless something else is in the mix somewhere. I’d triple verify this first. Booting into BIOS and triple checking the BIOS version - a lot of AMD laptops went out with 3.02 and a lot of folks honestly thought they had 3.03 - they did not.

The only things I can think of causing an inability to boot to Fedora 39 (steer clear of Mint for now), download a new ISO, another flash drive, boot to it.

Using nomodeset would be a Fedora 38 thing or older BIOS.

If this is still no good. As Mario indicated, the steps he indicated are where my mind lands as well.

1. Try to “reset BIOS default settings”.
2. fwupdmgr reinstall the firmware.
   3. Double check the speed/brand for the RAM against what Framework suggested.

Here is that list for comparison.

[Luis_Cunha]

@Matt_Hartley

Feel like there must be something else at play. On a current ISO of Fedora 39, it will absolutely boot up successfully on 3.03 BIOS

As Mario_Limonciello, there is something wrong, I contacted Framework, they asked me a bunch of questions, I’ve answered, I’m waiting for further replies.

@Matt_Hartley

a lot of AMD laptops went out with 3.02 and a lot of folks honestly thought they had 3.03 - they did not.

I confirmed in more than one way, I have the 3.03.

[Luis_Cunha]

Just a closure for this thread, it was an hardware problem. They’ve sent a new MB, I replaced the MB on the laptop and it’s now booting fine.

[Loell_Framework]

Thanks for the update @Luis_Cunha