• rufus@discuss.tchncs.de
    link
    fedilink
    arrow-up
    8
    ·
    edit-2
    9 months ago

    https://asus-linux.org/ seems to have some guides and tutorials.

    Generally:

    1. Turn off Safe Boot and features that inhibit booting other operating systems and USB media in your BIOS.
    2. Get the installer running. Try the failsafe and fallback video mode options. Try different distributions next.
    3. Tackle one problem at a time. Google it. Add your hardware in question (“Asus Strix G15”) and error message or exact issue (“black screen”) to your query.
    4. Get the OS installed and then again do one thing at a time. Get it running first, maybe kernel options again help. Then the proprietary NVidia drivers, then the keyboard illumination and other less important stuff.
    5. If it’s running somewhat alright and you’re sure you’re going to keep it, you can start moving your stuff there and installing applications.

    You’re somewhat likely to find answers to single issues by googling. Unless the hardware is really new, someone else has faced that issue before. For lots of manufacturers and common hardware, there are dedicated guides, wikis and forums. Try to find those and you might get a step-by-step instruction to get it running. Otherwise you have to isolate single problems by some means to be able to tackle them. This is difficult, especially if there are multiple issues at the same time. But that’s why I recommend focusing on one problem at a time and googling it with the most specific query you can come up with.

    I’m sorry that your hardware is so difficult to get running. The acpi=off could be a hint. But you have to figure out what exactly is causing the issue. Turning all ACPI off isn’t something you want. Maybe you could try installing it this way and see if it’s just the installer. Maybe the installed distro (after an update) does better. And choose a recent one with a recent kernel, in case the problem got solved in a recent kernel version.

    • Varen@kbin.socialOP
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      9 months ago

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

      Turn off Safe Boot and features that inhibit booting other operating systems and USB media in your BIOS.

      did already, unfortunately not working

      Get the installer running. Try the failsafe and fallback video mode options.

      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.

      Tackle one problem at a time. Google it. Add your hardware in question (“Asus Strix G15”) and error message or exact issue (“black screen”) to your query.

      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.

      • rufus@discuss.tchncs.de
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        9 months ago

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

        • nvidia-drm.modeset …
        • video=“vesafb”

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

        • Varen@kbin.socialOP
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          9 months ago

          @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

          • rufus@discuss.tchncs.de
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            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
              link
              fedilink
              arrow-up
              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
                link
                fedilink
                arrow-up
                1
                ·
                edit-2
                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
                    link
                    fedilink
                    arrow-up
                    1
                    ·
                    edit-2
                    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 )