I'm having a tough time with my HP Envy tower, which has an Intel motherboard and an RTX3060 graphics card, after setting up a dual boot with Linux Mint 22.2 and Windows on a new SSD. Here's the situation: I created a live USB, but it only booted in compatibility mode and everything seemed to install fine. However, when I try to boot, I just end up with a black screen that leads to a pink kernel panic screen.
I did some research and followed instructions from the Linux Mint website to add "noapic noacpi nosplash irqpoll" to the grub configuration, which allowed me to boot into the system. I installed the recommended Nvidia 580 driver, and once I'm in, everything operates smoothly. However, I can't boot without those changes. My Secure Boot is off, but the BIOS has a secondary HDD set to RAID mode, and switching to AHCI warns me about potential data loss. Plus, HP really limits access to advanced BIOS settings, which doesn't help.
Now, I wonder what might be causing this kernel panic since everything else is working—Bluetooth, Wi-Fi, etc. Also, I'm puzzled about what exactly I'm disabling with the added boot parameters and if I'm causing any issues. I tried POP OS with the Nvidia driver too, and it also resulted in a black screen. Changing the RAID HDD to AHCI didn't work either. I'm a bit anxious because I can access Linux only with noapic, and when I check lm-sensors or HW-Monitor, I find no info on my CPU or system fan, only the GPU fan. So I'm any advice would be greatly appreciated!
2 Answers
It sounds like you're dealing with a pretty common issue related to the Nvidia drivers and your BIOS settings. The kernel panic usually occurs when there's a hardware or driver conflict. The errors you mentioned about the NVidia module verification failing suggest that the proprietary drivers might not be properly signed for secure boot, even though you have it disabled.
Have you tried reinstalling the Nvidia drivers from a terminal after booting with those parameters? It’s possible that a clean installation might help resolve the signature issue. Also, consider looking at your BIOS options, as sometimes there are legacy settings that can improve compatibility with Linux.
Lastly, disabling those options like "noapic" or "noacpi" can help with booting issues, but it’s worth checking if they’re critical for your hardware configuration. They might not harm your system, but they could also limit performance or functionality.
I had a similar setup and faced the same issues until I realized the RAID setting in BIOS was the culprit here. Even with secure boot disabled, RAID configurations can cause conflicts with Linux. You can try switching to AHCI, but make sure you back up your data first!
If you're worried about losing data when switching from RAID to AHCI, perhaps try connecting your SSD as the only drive temporarily while making that change. That way, you can ensure your data is safe while tweaking the BIOS settings. Once you get into Linux with AHCI set, you should see improvements without those added kernel parameters!
Also, have you verified that your SSD is recognized properly in Linux? It's crucial for avoiding kernel panic.
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