Yeah, being that sluggish won't do it for me. And supposedly there are other solutions that can pull it off(?!)
I tried quickemu last week. And it was really easy. However, the fact that it doesn't support the latest version of MacOS (there's an PR for that) and that it felt way slower than anticipated made me stop. Maybe I'll explore other solutions to get MacOS virtualized.
It is git. You can fork repos. And some platforms can mirror a repository and keep it synced. If not, you'd need to build something with webhooks. Or keep both synced manually every now and then (or on a new release/tag.)
The axis aren't labeled properly. That's likely why we can't make sense of the diagrams.
Everyone elses life oscillates over time between positive and negative... OP's life's Y is X cubed. And it somehow contains big blue dots on the whole numbers... They consider that odd. And I'd agree.
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.
Gitlab.com just started doing shady stuff and requiring phone numbers or something on sign-up if what I read a few days ago here, is correct. For self-hosting the software should still be alright.
Github.com is by Microsoft and not free software. I don't know what direction Microsoft is taking with it, but it is widely adopted and they give you free CI and other stuff.
Codeberg, Sourcehut etc should be fine. I haven't heard negative things about them.
"Best" is running my own Forgejo on my server. At least that's what I think. But I also keep things on github, since all the people are there.
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.
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?
Uh yeah, I'm not sure. I've tried summarizing with AI tools. And there is the bot here on Lemmy that summarizes stuff... I never liked any of that. It's really a mixed bag, from pretty okay summaries to entirely missing the point of the original article to bordering on false information. I think we're far from there yet. However, it's a common use-case for AI. Maybe in 1-2 years I can stop being afraid of misinformation being fed to me. Currently, I think the incorrectness of the information still outweighs any potential benefit. The more complicated it gets, thus making you in need of a summary in the first place, the more biased and skewed the results get. So I don't see that happen in the very near future. But we definitely should keep up doing the research and pushing that.
Tagging and organizing is something I'd like an AI for.
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.
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.)
(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 )
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.
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...)
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.)
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.
Sure. But by the amount of adoption CUDA has, and the amount of GPUs / AI accelerators NVidia pumps out and into the datacenters of the world... AMD better hurry (and deliver an excellent product/ecosystem) or they won't be part of the AI boom.
Yeah, being that sluggish won't do it for me. And supposedly there are other solutions that can pull it off(?!)
I tried quickemu last week. And it was really easy. However, the fact that it doesn't support the latest version of MacOS (there's an PR for that) and that it felt way slower than anticipated made me stop. Maybe I'll explore other solutions to get MacOS virtualized.