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

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

    • Varen@kbin.socialOP
      2·
      9 months ago

      @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…

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

        I don’t know what gets written to disk on which distro and which logs are just kept in memory. dmesg alone just shows the current boot. I think if you’re doing it that way journalctl --dmesg --boot=-1 would be the correct command. That should do it.

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

            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 )

            • Varen@kbin.socialOP
              2·
              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
                1·
                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.)

                • Varen@kbin.socialOP
                  2·
                  9 months ago

                  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.

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

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

                    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?

            • Varen@kbin.socialOP
              2·
              9 months ago

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