Visual installer boots normally, and everything works until I actually try booting into the system. Just crashes right after selecting the OS in systemd menu. Kernel panic - not syncing: Fatal exception in interrupt. It also happens in arch, tried installing it manually and with a script and in both cases the exact same error appears. Image of the error:
I have w11 running on the same machine without problems, I doubt it’s a hardware issue, everything seems fine. The hardware is a 4070 mobile + i9 13900h. Other distros work normally as well, tried booting Nix into it just for the sake of it and it worked as intended. I think there’s something up with the arch kernel.
Yeah that sure looks weird. Unfortunately, without being able to see the first call trace, or the beginning of that one, if it is the first, I’m not sure I’m going to be able to tell you what’s dying here. At the top, I can see a page fault, suggesting something to do with memory handling. Just to make sure we’re all understanding here: This is you trying the OS out after an install for the very first time on this hardware?
I appreciate the answer. Yeah, I’ve never installed Endeavour before; this is my first time. Although, this same hardware has run Arch previously. Is there a way to get the full log so I can share it here?
This kind of stuff is happening before the systemd journal starts, so it’s not logged, making it very hard to catch. I suppose, if it’s humanly possible, you could be ready with the “pause” key, on your keyboard. That said, I’m still not sure that’s going to get you anywhere…
It is not much information, but at least it clearly shows that this is a kernel issue. Try a life system from usb, try other linux life system like debian or ubuntu just o see if there are differences. You may check bios settings, maybe you reset them to default. As this is hardware related, switch off fast boot in windows. It may also related to specific hardware during loading a specific kernel module. To find that you you would need a more complete error output. You can try booting with terminal redirection, or if that is to complicated to accomplish try to catch a movie from the boot.
Tried other distros, they worked normally. Fast boot is disabled also. I’d like to share the complete output but I don’t know how to export the full error log.
Since it’s a fresh install try another install with another kernel as well. Like maybe the lts kernel, then you can try to boot from either kernel. Also post your installation logs.
@burensou
Doesn’t make sense with this new of hardware that it fails to boot on the current kernel and yet boots on the lts kernel. Is secure boot disabled? Are you using luks? Must be some other issue.
As I stated previously, I ran Arch on this same machine before. It worked as intended, errors appeared as usual but nothing major like it was happening here. I’d assume that since the lts-kernel is more outdated (I think?) there might be some update/change that wasn’t implemented on it yet. I have no idea, though. I’m pretty much assuming all of this so I could be very wrong, obviously.
No…it’s possible but Arch would have the exact same kernel so it must be some other package or something. It’s possible a kernel parameter is needed? Or something else is the issue.
My bad. What I meant there was that I previously ran Arch a long time ago, on this same machine. As I stated, it was a pretty solid experience, nothing major happened. After a while I hopped off Arch and went to test other distros, a good amount of testing after that, I decided I wanted to return to a Arch/Arch-based distro, which is when I discovered the problem.
