1
Ok I nearly lost hope, since not being able to figure it out. (kbin.social)
submitted 8 months ago by Varen@kbin.social to c/linuxquestions@kbin.social
33 comments fedilink hide all child comments

Ok I nearly lost hope, since not being able to figure it out.

PLEASE. SEND. HELP.

_ First: this might gonna get a long one, but I‘m desperately looking for help!
Second: I‘m a total newb on Linux, so I have really limited Linux know-how.

Specs:
Asus ROG Strix G15DS-R7700X088W
AMD Ryzen 7 7700X
NVIDIA GeForce RTX 3070
2x 1TB SSDs; 1x M2 NVME with W11 running, 1x SATA

Goal:
Running Dual Boot with W11 on the first, M2 SSD (already running fine) and Linux (Nobara preferred) on the second, SATA SSD

Distros I tried:
Nobara 39
Fedora 39
Fedora 38
Ubuntu 22.04
Pop!_OS

Problem I run into:
I can‘t boot even from the LiveUSB without the „acpi=off“ option. If I do, I get just a black Screen (with Backlight still on) or, if I get into the Grub options first, there‘s only „booting command list“ visible but nothing else happens (even with „quiet“ disabled, no info on the Screen at all).
One thing I noticed, since my Keyboard, Mouse and Mousemat (Razerfly) have lighting, when I try to boot without the acpi=off, they go dark. And stay dark. With acpi=off the keyboard alone goes dark but then lights up again after 2-3 seconds.
If I run it with acpi=off, I can boot and install, but I then have to boot every time with acpi=off. This leads to the graphics driver not being recognized by the OS and running always in 1024x768 „software rendering“ resolution (even with proper drivers installed and enabled and nouveau on blacklist). So just let „acpi=off“ enabled isn‘t an option.

I did, after researching for several hours, try with various other options (nomodeset, acpi=ht, pci=biosirq, noapic, nolapic, and so on, tried a ton of those) but nothing did the trick - always black screen of death without acpi=off.

I did update my BIOS to the latest Version (306), did try every possibilty of options enabled/disabled (Fast Boot, Secure Boot, IOMMU, acpi settings in BIOS, secondary on-board Graphics,…) with no change.

Since I ran out of options (in relation to my google and reddit search skills), knowledge (total newb on Linux) and possibility to ask friends (that know more about linux than me), I‘m desperate enough to ask for help.

You are my last hope, before giving up on Linux with my PC.

If someone has an idea I could try or even a solution, I‘d be endlessly thankful!

If I missed some info or something is needed, don‘t hesitate to as for specific details._

#linuxquestions

you are viewing a single comment's thread
view the rest of the comments
[-] Varen@kbin.social 1 points 8 months ago

Sure. The whole output or something like dmesg -T --level=emerg,alert,crit,err,warn ?

[-] onlinepersona@programming.dev 1 points 8 months ago

I don't think it reveals anything private, so the entire output should be fine. If you're uncomfortable, then --level=emerg,alert,crit,err,warn should probably do. -T is unncessary, IMO.

[-] Varen@kbin.social 1 points 8 months ago* (last edited 8 months ago)

there you go:
https://pastebin.com/kNFqya2L

taken with acpi=off boot.
Since without acpi=off it's not possible to boot and there is absolutely no output after grub (as if the kernel wouldn't load at all) there simply nothing to show ...

[-] onlinepersona@programming.dev 0 points 8 months ago

[ 9.101103] mt7921e 0000:09:00.0: can't find IRQ for PCI INT A; please try using pci=biosirq

Have you tried pci=biosirq? From the description of the kernel parameter I don't think it's the right solution, but it might be worth trying.

biosirq		[X86-32] Use PCI BIOS calls to get the interrupt
				routing table. These calls are known to be buggy
				on several machines and they hang the machine
				when used, but on other computers it's the only
				way to get the interrupt routing table. Try
				this option if the kernel is unable to allocate
				IRQs or discover secondary PCI buses on your
				motherboard.

This one below though, might be the most important clue to a solution.

[   12.149945] NVRM: The NVIDIA probe routine failed for 1 device(s).
[   12.150113] NVRM: None of the NVIDIA devices were initialized.
[   14.289240] NVRM: Can't find an IRQ for your NVIDIA card!
[   14.294129] NVRM: Please check your BIOS settings.
[   14.294303] NVRM: [Plug & Play OS] should be set to NO
[   14.294475] NVRM: [Assign IRQ to VGA] should be set to YES

Maybe check your BIOS settings for anything that resembles those last 2 lines?

CC BY-NC-SA 4.0

[-] Varen@kbin.social 1 points 8 months ago

Yep, saw this entries already and tried with it. To no change unfortunately.
Did some research and also found the suggest to try with
acpi=noirq noapic
but also tried to no change.

Regarding the BIOS options, I did also check for these options, bug they simply aren‘t there 🤷🏻‍♂️ but will look again after those. Got told that this error might be due to the acpi=off thingy

[-] onlinepersona@programming.dev 0 points 8 months ago

Unfortunately, there's not much I can do anymore. My knowledge is insufficient to help.

Good luck with the rest. Probably in the future, avoid NVIDIA if you want to run linux. The company has consistently been terrible with Linux.

CC BY-NC-SA 4.0

[-] Varen@kbin.social 1 points 8 months ago

Alright, no worries! Appreciate you trying to help, thank you

this post was submitted on 11 Feb 2024
1 points (100.0% liked)

Linux Questions

2 readers
1 users here now

A place to ask Linux-related questions, post advice and suggestions, etc. Any questions pertaining to Linux from novice to greybeard level are welcome. ---- ### Asking Questions: Please provide enough info to for people to actually help you. While there are some things that are generally the same, there is no one "Linux" - every distro has some things they do different and you'll get better answers if you provide some info. And remember the people here are helping you purely out of their own good will - so be nice! If you are encountering a problem, please include: 1. Which distro you are using 2. A brief summary of the problem 3. Any steps you have attempted 4. Relevant details such as hardware specs (see below), application versions, etc. ---- ### Capturing System Specs In almost all cases, posting output from inxi -Fmz - either as in a code block, as a linked file, or as a screenshot - will be appreciated. Some distros may pre-install inxi but on others (such as Fedora), you may need to install it yourself. But we understand that there will be times when you are unable to provide this info (such as with boot problems). The output from inxi info should be safe (especially with the -z option)... But in general,**YOU SHOULD ALWAYS REVIEW OUTPUT AND REMOVE ANY PRIVATE DATA BEFORE POSTING ONLINE** (e.g. replace "Your Name" with `` or something similar - this helps in preventing doxxing, identity theft, and similar issues). - Some common graphical screenshot apps:gnome-screenshot, ksnip, shutter, and flameshot . There are also terminal-based ones like maim and scrot.

founded 1 year ago