got told to crosspost over here to reach more people:
Varen@kbin.social to 
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
@rufus
thanks for taking the time. I already asked over at the asus-linux discord about the issue but got no reactions up until now.
did already, unfortunately not working
all installers (except nobara) do fail when trying to get the bootloader installed, since efibootmgr seems to be in need of the acpi options and I don't get it running with acpi option on.
that's exactly what I'm trying to do, first and most important (from my understanding) would be to get the OS booted from the USB with acpi on. I am going through google/DDG/qwant/whatever-search-engine to look it up and tried everything I was able to find in relation to my Hardware, but wasn't able to tackle the issue up until now, that's why I'm asking for help all over the reddits/lemmys/kbins/discords...
I can get Nobara - and only Nobara - installed so I can boot without USB, but there as well only with acpi off.
I tried with Fedora, Nobara, ubuntu LTS, pop!_os, GarudaOS, silverblue, Mint, with everyone having the issue not being able to boot without acpi=off and getting to a black screen and USBs (seem) powered off right after choosing the OS in grub.
appreciate your time replying, thank you.
Alright. You should also play with the options for the framebuffer, drm and video modes or forcefully enable some outputs. (I forgot how to do all of that.)
I'd skip the general acpi=off since that only causes more issues and isn't feasable in the long run anyways. You need to find the option that specifically fixes only the issue with that one component that isn't working correctly.
Another idea: Maybe you can find the error message. Can you perhaps login via SSH from another machine? This would allow you to run
dmesgwhile your screen is black. Maybe the error shows up in the dmesg kernel messages and you can take it from there. (Some installers even allow login from remote, that is a bit tricky but should be documented somewhere with the distro.)@rufus
I will try and report back if I can get the dmesg output. But since I guess that the USB gets cut off right before something happens I guess there simply isn‘t.
Will try with the installed Nobara and see, if dmesg catches anything up at all
But once you're trying to extract the log, you need to start it with acpi on. I mean we want to see that error happening.
Maybe paste the whole log somewhere on a pastebin service... If you manage to do it... Sometimes it's not an obvious error message. (...But something like the HDMI port being turned off...)
@rufus
I‘m afraid that it‘s where it will fail, cause I can‘t get it to work with acpi on
I thought of getting the „bad installed“ (acpi=off) OS, let it start with acpi on and afterwards grab the logs again with acpi off, but don‘t know if that will work…
I don't know what gets written to disk on which distro and which logs are just kept in memory.
dmesgalone just shows the current boot. I think if you're doing it that wayjournalctl --dmesg --boot=-1would be the correct command. That should do it.@rufus
Alright, will try later and report back the outcome / pastebin if I can grab it
Good luck! 😀
(FYI: You can skip mentioning names that way, a direct reply will show up on Lemmy. And if you want to mention someone, you'd need to add the instance name for it to have an effect. i.e. @rufus@discuss.tchncs.de )
Yeah thank you, I really hope we‘ll get some progress.
(Not doing it on purpose, it‘s just how kbin behaves 😅 really thinking about dropping it and give lemmy a try. Originally decided for kbin because I wanted both worlds but since the behaviour is so strange …yeah 😉)
Unfortunately nothing. Did install - reboot with acpi=off, reboot with no acpi parameter, reboot with acpi=off
Dmesg shows for the boot=-1 the first boot after install with acpi=off
No log for the try without acpi parameter 😢😢
Booting with acpi=off shows many logs with „IRQ not found for nvidia …“ (in the meaning, not wordly).
Edit: can‘t find an irq for your nvidia card
Edit 2: found a boot.log file. When trying to boot without acpi=off then no log is written, the bootprocess doesn‘t even start. From this point of view I‘d guess a Problem with UEFI. Still no idea what and where, but it‘s not graphics related if the bootprocess doesn‘t start at all… what d‘you think?
I think you can safely ignore all the errors that happen while acpi=off. That will switch all kinds of things around and the operating system can't set up the hardware properly without it, so it is to be expected that half the things crap out and throw error messages. Could be a red herring anyways.
Are you sure Secure Boot is switched to "Other OS"? (see https://www.asus.com/support/faq/1049829/ ) You could verify that with the 'msinfo32' in the guide.
And I'm really not sure if it's the UEFI. From your description it seems you're getting to the boot loader and something happens after... Maybe try not messing with the acpi, but removing the "quiet" and "splash" if they're there and adding "nomodeset" instead. After you hit Enter (or Ctrl-X with Grub) the early kernel messages should pop up. Something with loading and initrd or like that. What happens then? Does it load the kernel? Do additional log messages with a boot process appear? (If it's too fast, you can try a video recording of your screen with your phone.)
Yes, secure boot is set to Other OS - if set otherwise there’s a message after grub that secure boot is active, so pretty sure about that.
Unfortunately it doesn‘t show anything, even with no parameters at all. The only thing that shows up when changing the grub parameters is the „booting a command line“ message which stays there forever, nothing happens.
I‘ll record it with my phone when I get home later on today with the nomodeset parameter.
took the video
https://youtu.be/855QTzZlhWk
as you can see, absolutely nothing happens or shows up. (still uploading rn, should be available shortly)
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
Here is an alternative Piped link(s):
https://piped.video/855QTzZlhWk
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
Really weird. Honesty, I currently have no idea how to proceed. Maybe I can google a bit later/tomorrow. But it's not looking good. There doesn't seem to be any good information out there concerning that mainboard an Linux. And since we don't get an error message there isn't a clear thing to begin with.
I would have expected at least something happening on the video. Maybe a few lines of text and then the screen flickering and going to black... But nothing?
yeah, that's the reason I am so desperate ... I understand, so maybe about time to look around for a new mobo?
anyways, I wanted to thank you very much for your time and effort in figuring out and trying to help me, I really do appreciate it very much!