GeForce 920M failing to initialize

Hello everyone,

I’m hitting a massive roadblock trying to get the dedicated graphics card working on a legacy laptop, and I'm hoping some of the Linux hardware or driver experts here might have run into this specific error behavior before.

The Setup:

• Laptop: Lenovo Yoga 500-14ISK
• CPU: Intel Core i5-6200U
• RAM: 8GB
• Integrated Graphics: Intel HD Graphics 520
• Dedicated GPU: NVIDIA GeForce 920M

The Problem: The dedicated 920M GPU simply refuses to initialize on boot. It consistently fails to start across clean installations of current, supported Linux distributions.

What I've Tried & Technical Specifics:

• BIOS: Secure Boot is completely disabled in the system firmware to rule out driver signature blocking.
• OS & Kernels: I am testing on Ubuntu 22.04 LTS and Ubuntu 26.04 LTS. On the 22.04 environment, I have tested using the stock modern kernel as well as target-testing Kernel 5.15 to better match the hardware era.
• Drivers Tested: I have attempted troubleshooting using both the NVIDIA 470 and 390 proprietary driver branches from the official repositories.
• The Logs (dmesg): The kernel consistently hits severe initialization loops right at boot: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x56:667) NVRM: rm_init_adapter failed, device minor number 0

Root Cause Clue: The logs indicate failures to copy the VBIOS to system memory, meaning the driver crashes hard right as it tries to negotiate power states via ACPI or handle early PCIe bus handshakes. I've tried forcing modprobe options like NVreg_DynamicPowerManagement=0x00 and NVreg_EnableMSI=0, but the adapter fails before it even reads them.

I have run the diagnostic tool and included my complete nvidia-bug-report.log.gz file in the first comment for review.
the post was removed by reddit filters maybe because I included the link.

Has anyone successfully dealt with this specific 0x22:0x56:667 initialization failure on older mobile Kepler/Maxwell GPUs under modern kernels? Is this a known ACPI/BIOS memory mapping conflict with current OS structures, or is there a specific kernel boot parameter (grub) required to coax this firmware to map correctly?

Any insights or technical pointers would be massively appreciated. Thanks!