I'm using an HP Envy tower with an Intel motherboard and an RTX3060 graphics card, and I've set up a dual-boot system with LinuxMint 22.2 and Windows on a new SSD. Unfortunately, I can't fit another SSD into my system. During the installation, I had to use a live USB that only booted in compatibility mode, but everything else seemed to go smoothly.
Now, every time I attempt to boot, I get a black screen that leads to a kernel panic displayed in pink. I did some research and found recommendations on the LinuxMint website, so I added "noapic noacpi nosplash irqpoll" to the kernel options in GRUB. This allowed me to boot into Linux and install the recommended Nvidia 580 driver, but I still can't start the system successfully without those modifications.
My Secure Boot is disabled, but my BIOS shows a secondary HDD set to RAID mode. When I tried switching it to AHCI, I was warned about potential data loss, so I left it as is. HP has also limited my access to advanced BIOS options, which adds to my frustration. The Nvidia driver seems to work fine, as everything else in LinuxMint—including Bluetooth and Wi-Fi—functions well.
I'm curious about what's causing this kernel panic and whether I could be causing issues by using those boot parameters. Is there a relation between them and the kernel panic? I also tried using POP OS with the Nvidia driver, but it led to a black screen too. Additionally, some monitoring tools I installed show no readings for the CPU or system fan, only for the GPU fan, which makes me anxious about system health. Any insights would be greatly appreciated!
3 Answers
From what you described, it sounds like the Nvidia driver might be causing the kernel panic, especially since the kernel keeps tainting with a signature issue. You're definitely not hurting anything by using those boot parameters; they often help in cases like yours to bypass certain hardware checks that lead to boot failures. What you might want to do is check if the secure boot is indeed affecting the Nvidia module. Sometimes that can prevent it from loading properly, especially if you're using a driver that doesn't have the correct signature. Also, maybe switch back to the Nouveau driver temporarily to see if that changes anything in your boot behavior.
It’s definitely possible that the RAID mode in BIOS is causing some issues too. If you change to AHCI, make sure to back up your data first, but most modern systems handle that transition fairly well. Another suggestion is to boot with an older kernel version temporarily and see if you can get to the desktop that way. If it works, then the problem likely lies in driver compatibility with the latest kernel.
I had a similar problem with Nvidia drivers before. It can be tricky with the modules and how they interact with the kernel. One thing you could consider is entering recovery mode as you did and seeing if there’s a way to completely clean out the Nvidia drivers and re-install. There are sometimes remnants of old installations that can throw things off. If you're comfortable with it, try running `sudo apt-get purge nvidia*` and then reinstalling the driver after a fresh boot.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures