this post was submitted on 13 Feb 2024
21 points (70.6% liked)
Linux
47342 readers
1322 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
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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."
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=offwithacpi=noirq. If it's something with the interrputs, there are extra options likeapic=irqfixupornolapic(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.
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
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 😆
Yeah I already got one in mind and looked it up on linux-hardware.org - any other option I‘d have to make sure the next one is alright? (Besides socket and compatibility with my other hw)
Sorry I have no idea. It's been ages since I last bought a mainboard and that one was recommended in a computer magazine... I'd google it. See if other people have issues with it. And I't trust blogs, Reddit and forums more than the traditional compatibility charts.
Alright, no worries! You invested so much time and effort trying to help me out, I can‘t thank you enough for that, really really appreciate it much!
Hehe, no worries. I think the community needs to stick together. I used to do (voluntary) computer support once a week at university before I moved, now I occasionally do it here. It's always nice being able to help people ...Or in your case at least trying... To me, it's way more fun than discussing politics or the latest news, anyways. And I mean I'm no exception. I also sometimes need support, ask questions about a new distro or get my itches scratched by people who solve my issues on Github.
Oh I absolutely can relate haha
Maybe one day I‘ll be here asking dumb questions again, watch out 😁
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 ...
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.