• Varen@kbin.socialOP
    0·
    9 months ago

    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?

    • rufus@discuss.tchncs.de
      0·
      9 months ago

      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.)

        • rufus@discuss.tchncs.de
          1·
          9 months ago

          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.

          • Varen@kbin.socialOP
            2·
            9 months ago

            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

            • rufus@discuss.tchncs.de
              1·
              9 months ago

              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 😆

              • Varen@kbin.socialOP
                2·
                9 months ago

                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)

                • rufus@discuss.tchncs.de
                  1·
                  9 months ago

                  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.

                  • Varen@kbin.socialOP
                    2·
                    9 months ago

                    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!

              • Varen@kbin.socialOP
                2·
                9 months ago

                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 …

                • rufus@discuss.tchncs.de
                  1·
                  9 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.