this post was submitted on 13 Feb 2024
21 points (70.6% liked)

Linux

47361 readers
1087 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

got told to crosspost over here to reach more people:

https://kbin.social/m/linuxquestions/p/4631784

I don't know if and how crossposting functions in kbin/lemmy, so hopefully it'll work that way

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 7 months ago* (last edited 7 months ago) (9 children)

I have another kernel option for you to try: "earlyprintk is useful when the kernel crashes before the normal console is initialized. It is not enabled by default because it has some cosmetic problems."

  • earlyprintk=vga,keep debug
  • earlyprintk=efi,keep or earlyprintk=bios,keep

I'm not sure if it gets you anywhere, but it could make the fist kernel messages show up.

And you could try replacing the acpi=off with acpi=noirq. If it's something with the interrputs, there are extra options like apic=irqfixup or nolapic (mind the difference apic <-> acpi). (Taken from this document)

I had the time to google a bit and I was right, I am about to run out of ideas. There is a good general guide in the arch wiki on how to approach issues:

https://wiki.archlinux.org/title/General_troubleshooting#Boot_problems

Maybe also read that, but that's pretty much it.

[–] [email protected] 2 points 7 months ago (8 children)

Wow thank you so much for keeping up on it!

I tried the earlyprintk options, but unfortunately none of them did work. Neither did the orher acpi options show up something, I do still have the exact same behaviour :(

I will work through the troubleshoot link you pasted, thank you as well for that.

Appreciate your help, I guess I‘ll start thinking about replacing the mobo

[–] [email protected] 1 points 7 months ago (7 children)

I guess I‘ll start thinking about replacing the mobo

Yeah, I'm slowly getting to the same conclusion. You could try and rip out all other non-essential components to rule them out. If there are any. And go through the BIOS options once more, switch everything to "Other OS" and try the "legacy" modes for ACPI, boot etc. But at this point I somehow doubt any of this will make any difference. Just make sure the next mobo is alright 😆

[–] [email protected] 2 points 7 months ago* (last edited 7 months ago) (1 children)

got some news. I don't think, that it might change something, but who knows.
I added in grub the option "insmod progress" (which I found by googling somewhere). It should show, if kernel and initrd do load or not and now I can see, that the vmlinuz and initrd are loading to 100% and after that it hangs. So it looks like the kernel loads but then stucks.
As said before, I don't think that this might change something in regards to further tests with my actual mobo, but I didn't want to left that out ...

[–] [email protected] 1 points 7 months ago

Ah nice. At least something. But I don't think it'll change anything since it's still grub outputting that, and not a life sign from the kernel.

load more comments (5 replies)
load more comments (5 replies)
load more comments (5 replies)