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")...
Lots of people to the time to reply here and at kbin.
It probably will not hurt to also ask on superuser.comstackexchange.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.
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.
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.
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"
@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 :)
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 :-)
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 :(
@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
Turn off Safe Boot and features that inhibit booting other operating systems and USB media in your BIOS.
Get the installer running. Try the failsafe and fallback video mode options. Try different distributions next.
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.
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.
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.
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.
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.)
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…)
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. 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.
(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 )
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 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.
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!
No problem. I wish I could have provided you with a solution. If you have something like a 14 days free return policy, I’d consider returning it. Otherwise, wait a few days before you start thinking about a new motherboard. Maybe someone with a better idea still replies to you.
But I can empathize with your situation. I also used to have hardware that was a mess or didn’t work at all. It’s just annoying.
It’s likely the mobo. A Ryzen processor and a nvidia 3070 isn’t so uncommon. And you already said you updated the BIOS and put quite an amount of effort in.
If you can return it or have a friend in need of a mobo… I’d swap it… However, there is still a possibility that someone reads your post on the weekend and happens to know something more. Or you use Linux in a VM from within Windows. That may work, I don’t know you, I wouldn’t do it since I use Linux 99% of the time.
Only thing I would advise against is hoping the issue will someday get fixed. In many cases it never happens.
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:
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
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 😆
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)
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.
Hehe, no worries. I think the community needs to stick together. I used to do (voluntary) computer support once a week at university before I moved, now I occasionally do it here. It’s always nice being able to help people …Or in your case at least trying… To me, it’s way more fun than discussing politics or the latest news, anyways. And I mean I’m no exception. I also sometimes need support, ask questions about a new distro or get my itches scratched by people who solve my issues on Github.
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 ...
Don‘t want to dig up old posts, but wanted to update you since you took quite some time trying to help - it works now! I replaced the MoBo and everything works no smoothly on the new MoBo!
Thanks again so so much for the very appreciated help!
Add comment