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.
Didn’t know that thanks,
In the case of starting from the USB before installing that won’t work, but for sure after installing that’s going to be helpful.
Will do that later today.
Meanwhile I’m uploading the boots that I took pictures.
Note, several of these look like they are still booting, (the kernel panic is obvious, others are not), but all of them I left them for more than one minute frozen before taking the picture.
The most common one is the one that goes up to “Started gdm.service” and freezes there, the kernel panic only happen once.
I need to see the full journal to understand if this soft lock is a perpetrator or a victim.
I would suggest if you haven’t already to check with no modules or anything else plugged in.
Have you changed any BIOS settings? By chance do you have Windows also and can see if it’s got problems too?
Fwiw from where it hung in the log you posted Windows might only show it after you have done hardware accelerated video playback if it’s the same problem.
I’m doing several boots to have several journal reports, I will post a good one when I have it.
By modules what do you mean? the 4 modules that cover the laptop ports? If it’s that, I have 2xUSB-C, 1xUSB-A and 1xHDMI. Apart for the power supply I have nothing connected to them.
I only changed a config that limit’s the battery charge to prolong battery life, but that should not have anything to do with this.
Ok, I did 3 boots and they crashed in the same way, the journal also looks similar.
I can’t post the entire text (too big) and I can’t upload the file (not authorized extensions), so I changed the extension to scad, but it’s just text.
None of those seem to match a boot with amdgpu loading. Can you double check the arguments you used and spacing? You can double check the kernel command line from a log in the header.
No modules…
crash-nomods1 and crash-nomods2 crashed visually in a different way, crash-nomods4 crashed in a similar way to the ones posted before but didn’t take a picture.
Don’t know if it helps (or if it’s related), but when I start with nomodeset, closing the lead does go to suspend and if send the computer to suspend it won’t wake again, I will need to force shutdown (press power for 10s).
Edit: To be frank I don’t know if it’s not waking up, the screen is black, maybe it’s waking up but just the screen keeps black.
This is one of the other things not working, if it’s not related we can not talk about this until the main problem is solved and get back to this after.
Many thanks, I really appreciate the time and help you’re giving.
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.
That’s actually a good news, it means when I solve this problem, potentially I’ll solve the other one.
