• rufus@discuss.tchncs.de
    8·
    10 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
      4·
      10 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
        1·
        10 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
          2·
          10 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
            1·
            10 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·
              10 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·
                10 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.

  • orsetto@lemmy.dbzer0.com
    2·
    10 months ago

    Unfortunately i can’t help you, but just to be sure, have you downloaded the -nvidia version of the ISO? In case, check it out

    Also try not to daily run with acpi=off, especially on a laptop, as it won’t be very power efficient

    • Varen@kbin.socialOP
      2·
      10 months ago

      @orsetto
      it’s not a laptop, it’s a desktop.
      Yes, I did download the -nvidia versions, didn’t do the trick and daily run it with acpi=off is no option since many things don’t work anyways with that setting

    • Varen@kbin.socialOP
      2·
      10 months ago

      @lemmyreader

      tried just right now. I get „booting a command list“ and nothing more, stays like that and USB Devices seem to be off.

        • Varen@kbin.socialOP
          2·
          10 months ago

          @lemmyreader
          Thank you for the suggestion, I really do appreciate anyone who could have a clue what could go wrong and takes the time trying to help me out.

          Yeah, Ventoy is the latest I had to burn the ISOs on the USB and stayed with it since :)

          • lemmyreader@lemmy.mlEnglish
            2·
            10 months ago

            You could try this The OP installed the drivers from an older iso and then upgraded. Manjaro Linux is not very much liked by many but you could give it a try. If it works you can go for plain Arch or EndeavourOS. From what I found the closed source Nvidia driver exist since 2022 so don’t use an iso that is too old :-)

            • Varen@kbin.socialOP
              2·
              9 months ago

              ok took me 3 days to test, apologies :D
              but unfortunately, no, doesn’t work. Even the “old” iso stucks at the exact same position with the exact same behavior :(

            • Varen@kbin.socialOP
              1·
              10 months ago

              Will have look into it and try it out, but will need some time. Will defo reply back once tested 👍🏻 thank you!

          • lemmyreader@lemmy.mlEnglish
            2·
            10 months ago

            Thank you for the suggestion, I really do appreciate anyone who could have a clue what could go wrong and takes the time trying to help me out.

            Tried nvidia-drm.modeset=1 as kernel parameter already ?

            Yeah, Ventoy is the latest I had to burn the ISOs on the USB and stayed with it since :)

            :)

            • Varen@kbin.socialOP
              1·
              10 months ago

              I tried so many parameter, that i can‘t remember anymore everyone ^^ but tried just now, unfortunately no change, same behavior

    • Varen@kbin.socialOP
      2·
      10 months ago

      yeah … as you can see in one of my other comments, I already joined the asus-linux discord and asked the “same” question (really, nearly with the exact same words…) and got , unfortunately, absolutely no reaction to it (besides on comment about “you need to disable the nouveau driver”)…

      • lemmyreader@lemmy.mlEnglish
        2·
        10 months ago

        Lots of people to the time to reply here and at kbin.

        It probably will not hurt to also ask on https://superuser.com/ https://stackexchange.com/ and Reddit linuxquestions or another appropriate subreddit. To me it seems like Discord is similar like IRC : questions will get snowed under after others write newer things and your reading audience is likely decreasing.

        And a question : What are your plans with Linux on your desktop ?

        • Gaming ?
        • Coding ?
        • Reading books and watching videos ?
        • Web surfing ?
        • Social media ?

        If you are interested in learning more Linux then a refurbished laptop is a good start to run Linux natively without a dual boot.

        • Varen@kbin.socialOP
          2·
          10 months ago

          Don‘t get me wrong, I‘m not complaining at all, in contrary, I am enormous grateful for any help I get.
          I posted alread in reddit as well - subreddits r/Nobara, r/linux4noobs and r/linuxquestions
          Asus-Linux has a thready-like area in their discord „general-issues“, where I made the thread…

          At first it is to learn how everything behaves, test my use-cases to see, if linux could become an all-dayer for me - that would be the main goal - until then the dual-boot to have a fallback option.

          • lemmyreader@lemmy.mlEnglish
            1·
            10 months ago

            Don‘t get me wrong, I‘m not complaining at all, in contrary, I am enormous grateful for any help I get. I posted alread in reddit as well - subreddits r/Nobara, r/linux4noobs and r/linuxquestions Asus-Linux has a thready-like area in their discord „general-issues“, where I made the thread…

            Cool. 👍

            At first it is to learn how everything behaves, test my use-cases to see, if linux could become an all-dayer for me - that would be the main goal - until then the dual-boot to have a fallback option.

            In that case, VirtualBox and other emulators could be useful to look into. And WSL may be limited (I’ve read) but also useful. Never tried WSL but a friend of mine is happy with it.

            • Varen@kbin.socialOP
              1·
              10 months ago

              yeah, already played around with VirtualBox and WSL, but there are use-cases (e.g. in gaming) where just an emulation can’t really show what’s possible and what not, that’s why I would love to have the dualboot, so I can reliably test everything without any excuses like “runs probably bad because of emulation”