Problem with drivers and bootloader

Hello, I’m relatively new to the Linux world. I recently got a computer (from a clevo reseller called Dream Machines). It has 2 disks inside (a Patriot and a Samsung). I installed Windows 11 Pro on the patriot, which is also the first one. However, I use Linux, and only in specific cases do I enter Windows. On the Samsung, I installed PopOS (the disk used to have Windows inside). The entire installation was successful, but the bootloader doesn’t work. Instead of disabling secure boot, I set “enforce secure boot=false” to uefi. I should also say that I want to experiment with Linux, so I was thinking of installing CachyOS on a partition on the Samsung. I tried to solve the issue by installing grub, but it didn’t work, I had read that they don’t fully support it. In PopOS, I have a problem with the RTX5060 drivers, the system sees it but can’t use it, so it only uses the integrated Intel. Finally I have a problem with the fans which I can’t control. Pressing Fn+1 they work but I can’t hear them working on their own (but the laptop doesn’t get hot).

In summary I need help with the RTX5060 drivers and the fans. For the bootloader of the 2 OS (or 3 in the future).
I have been looking for a solution to these but I couldn’t. I would like to thank in advance those who read the problem

Technical Info:
i9-14900HX
RTX5060
32GB ram
3 fans total (one of them is not even controlled by Windows)
PopOS 22.04 - Windows 11 Pro

1 Like

Welcome @Android_Creator

You’ve got a strong setup to experiment with, so let’s break this down since you mention a few things:

1. the bootloader (also see link at the end of my post)
Pop!_OS uses systemd-boot by default, which can act weird if Secure Boot isn’t fully off. Instead of “enforce secure boot=false,” disable Secure Boot completely in your BIOS.

Once you finish that, run:

sudo bootctl install

If it still doesn’t boot, efibootmgr will show whether the entry exists. If you later install CachyOS, letting it use GRUB can make managing all OS entries simpler.

2. RTX 5060 Driver
Pop!_OS might not have the latest NVIDIA driver for your card yet. Update and install:

sudo apt update && sudo apt full-upgrade
sudo apt install system76-driver-nvidia

Then reboot and check with nvidia-smi. If it still fails, the GPU may need a newer driver version than what 22.04 ships. Upgrading Pop!_OS to 24.04 LTS or installing the latest NVIDIA driver manually should fix that.

3. Fan Control
Clevo may have limited fan control in Linux. If Fn+1 works, your fans are functional but not managed automatically try:

sudo apt install nbfc
sudo nbfc config -l

Look for a matching Clevo profile or something close to your model. You can also check if the kernel is loading WMI properly:

dmesg | grep -i wmi

Disable Secure Boot fully, stick to one EFI partition on the first drive, and install all OSes in UEFI mode for smoother dual/triple boot.

I have not tested this, as I’m not on Pop!_OS anymore, but take a look here:

Edit: Also see if you find any hints here:

2 Likes

Thanks for your extremely quick response

I tried everything except boot.
First of all, the RTX5060 is now visible in the system and I can select it for use. When PopOS was installed, there was an application called Nvidia X Server Settings. I had opened it out of curiosity. I found various information about my gpu. However, while I was looking for drivers for the built-in LED keyboard, I went to nvidia to get the latest version, and in the popOS Shop it wanted me to download the 580 drivers package. After that, when I opened the application, these settings were not there. I’ll mention it more for the future users
Regarding the fans, it gives me “Unable to locate the nbfc package”. I had tried it again but it still gave me the same result. Is there a possibility that the computer could be damaged by these high temperatures?
Does active bitlocker cause problems?

1 Like

Nice progress! Good to hear the RTX 5060 is finally being detected properly. :smiling_face_with_sunglasses:

Regarding NVIDIA Settings disappearing, that usually happens when you switch to a different driver version. The nvidia-settings package can be reinstalled:

sudo apt install nvidia-settings

See if you find anything globally relevant here (even though it’s Arch-specific, much of it applies broadly):

For fan control nbfc isn’t in the default Pop!_OS repos, which is why it says “unable to locate.” You can install it through a PPA or build from source.

Or try Clevo-specific WMI kernel module might be easier. :face_with_diagonal_mouth:

Check if your model is supported with:

dmesg | grep -i clevo

or

dmesg | grep -i wmi

Also maybe try:

Laptops throttle well before reaching dangerous levels (so will get slower before damage). But long term, keeping temps in check is smart. If Fn+1 works, that’s a good backup until fan control is sorted.

Active BitLocker on your Windows drive won’t break Linux, but it can complicate things if you ever want to chainload or access that partition from Linux.

It’s best to leave Windows alone and just boot it through the UEFI menu or GRUB when you set it up later. No need to disable it unless you plan to share files between OSes.

This is an old guide but may still be useful: Pop!_OS on a Clevo Laptop.

RTX5060 problem has been solved

sudo dmesg | grep -i clevo
[   13.512300] clevo_acpi: interface initialized
[   13.960853] clevo_wmi: interface initialized

sudo dmesg | grep -i wmi
[   13.960853] clevo_wmi: interface initialized

Unable to locate clevo-xsm-wmi :backhand_index_pointing_down:

I have 3 fans in total. If the fans are getting used automatically from PopOS is there gonna be a high temperature problem? Yesterday I tried to use a heavier application and the fans were quiet. I don’t know which of the fans were on use but the laptop wasn’t hot at all. So are they getting controlled automatically from the BIOS/UEFI or by the PopOS.
About Bitlocker its enabled and I have give to PopOS the password and I can transfer files without any seminal. May I turn off the secure boot? Does it offer actual protection or it’s just for special occasions? Otherwise I just keep up enforced-secured-boot=false. Furthermore at Samsung disc (the disc with Linux) I still have the partition EFI where I was booting the old windows, May I delete it?

1 Like

Good questions, not dumb at all! We all have to start somewhere. I have accidentally deleted my system files in part or in whole even 5 years after using Linux. :rofl:

Most laptops control the fans through the BIOS or firmware automatically. Pop!_OS doesn’t need to manage them for your machine to stay cool.

If the laptop isn’t heating up, it means the fans are already doing their job. You only need manual fan control if temperatures get too high, the fans don’t respond or if they are too loud. None of which is common.

You can safely turn off Secure Boot. For a normal dual-boot setup, most people do. It adds a bit of security but can also cause issues with drivers and bootloaders on Linux.

Unfortunately, some games with anti cheat like Battlefield 6 requires secure boot to be enabled or you can’t launch it. Beyond something like that you can disable it permanently.

If your system is booting fine from the Patriot disk, you can remove the old EFI partition from the Samsung drive.

Just check first with:

sudo efibootmgr

If it’s not listed there, it’s safe to delete.

If BitLocker is working fine and you can transfer files, there’s no need to change anything.

—-

Not really off topic, but a side note expanding on Secure Boot since it’s also affecting me. Secure Boot often causes issues with Linux installs if the bootloader or kernel isn’t signed with a key your firmware recognizes.

Windows bootloaders are signed by Microsoft, so UEFI trusts them out of the box.

Many Linux distros use shim + GRUB or systemd-boot with their own signed components. But not every distro signs or registers its keys the same way.

Also see Dealing with Secure Boot on Linux from this guide:

If the bootloader isn’t signed, or the firmware doesn’t recognize the signature, Secure Boot blocks it.

That’s why Linux boots fine when Secure Boot is off but fails when it’s on.

We have three main options:

  1. Keep or toggle Secure Boot off. Most Linux users do this
  2. Use a distro with signed bootloaders, like Ubuntu, Fedora, or openSUSE.
  3. Manually enroll a Machine Owner Key (MOK) to allow your distro’s bootloader under Secure Boot. This works, but it’s more advanced and can be annoying/repetitive after kernel updates.

Pop!_OS typically doesn’t support Secure Boot that I’m aware of.

If you want to keep Secure Boot enabled for Windows but still boot Linux, you’d either need to use a signed shim or a distro with built-in Secure Boot support.

1 Like

I did what it said and even after the reboot nothing changed. I logged into PopOS normally.

otheos@pop-os:/mnt/EFI$ sudo ls /boot/efi/EFI
BOOT   Microsoft				    Recovery-8138-A6FE
Linux  Pop_OS-eeacf7ce-54c4-47ac-a595-2c701aa28e2c  systemd
myusername:~$ sudo os-prober
/dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/nvme1n1p1@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows1:efi
/dev/nvme1n1p4@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows2:efi

On the first disk is Windows :index_pointing_up:

Also how can I uninstall grub? Because I had installed it before posting here

I have experienced similar stories too :sweat_smile:. I had accidentally installed Linux on a disk that didn’t have enough space, so it took over from Windows…

2 Likes

This is a good thread, and to be honest with you, this is also an area completely beyond my specific experience. It’s also why I enjoy reading and participating in places like this because other people who either have the knowledge, or at least the ability to quickly pick up additional things, can respond.

I’ve been decent at figuring things out; still it’s nice to find and appreciate the expertise of others; we don’t always have to be the one to dig out a solution when we have an excellent, sharing community to help us out! Great discussion gentlemen!

3 Likes