Help with Nvidia drivers on Laptop dual graphics

(I’m not sure if I should call it that way “Dual graphics” Because Amd has registered that as something of its own but it is more to express what I have without knowing too much)

Well, I spent a week researching how to install the latest version of drivers for my graphics card and got more questions than answers, I summarize:

I have an Asus laptop with integrated amd graphics and dedicated Nvidia (3060) graphics. But what I really need to update the drivers for is for the Nvidia one, which is what I need for demanding tasks like running a program with wine, lutris or playing games.

So I instinctively check 2 pages:
-The official nvidia page where I can get the file with the latest update.
-And the Archwiki where they recommend me to do everything with pacman so I don’t have to always install when the kernel is updated or something like that.

Before doing anything I do some more research and find that EndeavourOS has its own way of installing Nvidia drivers (which calms me down a bit).

In principle I have 2 problems with this;

1.When I check the available drivers with nvidia-inst --drivers or when using other option, always before the response I get an error that I haven’t been able to figure out how to fix:

pcilib: Error reading /sys/bus/pci/devices/0000:00:08.3/label: Operation not permitted
NVIDIA card id: 2520
Fetching driver data from nvidia.com ...

Series 525: supported (nvidia.com: 525.89.02)

(So far it hasn’t stopped me from getting results but it’s a little scary)

2.Supposedly I should use the --bumblebee option which should work for cases where you have integrated + dedicated graphics but I have found that it is not recommended for new devices so…

In conclusion, I have very contradictory data and I don’t know how to proceed, I shouldn’t install the drivers manually, I should use pacman, but EndaeavourOS has nvidia-inst that should make things easier but left me with more doubts.

The only thing I’ve come to is that I probably shouldn’t use bumblebee because it seems like the only difference is that it handles changing graphics but I already have asusctl to take care of that but I’m not too sure if that’s the only difference. :cold_sweat:

For all this I ask you for help, beautiful community! :blush:

hi this is only the common “Nvidia Confusion” we all have this me too still … after years try o support Nvidia.

nvidia-inst is only a helper script that uses pacman and scriptlets to check driver compatibility and set options if needed.

And right… do not use bumblebee …

Usually installing Nvidia driver and set the DRM modesetting option will make you able to switch GPU on manually…

So from what we know the default behavior if Nvidia driver is installed and the DRM Modesetting is enabled on Boot system will boot on the igpu and switching should be possible from the cli.

if this is working you can try installing a switcher helper that handle this in the one way or the other.

You can set Nvidia to be used all the time or use switcher to switch it on when you need it and leave it of for normal process working…

1 Like

would be @manuel to check if this is an issue in the script?

Can you show the output of commands

ls -l /sys/bus/pci/devices/
ls -l /sys/bus/pci/devices/0000:00:08.3/

Don’t use Nvidia driver from website, it may work but will cause more problems down the road. Install from pacman instead and reboot.

sudo pacman -S nvidia-dkms nvidia-utils lib32-nvidia-utils nvidia-settings
1 Like

Sure!

[pikaloid@FlowX16EndeavourOS ~]$ ls -l /sys/bus/pci/devices/
total 0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:00.0 -> ../../../devices/pci0000:00/0000:00:00.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:00.2 -> ../../../devices/pci0000:00/0000:00:00.2
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:01.0 -> ../../../devices/pci0000:00/0000:00:01.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:01.1 -> ../../../devices/pci0000:00/0000:00:01.1
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:01.2 -> ../../../devices/pci0000:00/0000:00:01.2
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:02.0 -> ../../../devices/pci0000:00/0000:00:02.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:02.2 -> ../../../devices/pci0000:00/0000:00:02.2
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:02.3 -> ../../../devices/pci0000:00/0000:00:02.3
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:02.4 -> ../../../devices/pci0000:00/0000:00:02.4
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:03.0 -> ../../../devices/pci0000:00/0000:00:03.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:04.0 -> ../../../devices/pci0000:00/0000:00:04.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:04.1 -> ../../../devices/pci0000:00/0000:00:04.1
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:08.0 -> ../../../devices/pci0000:00/0000:00:08.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:08.1 -> ../../../devices/pci0000:00/0000:00:08.1
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:08.3 -> ../../../devices/pci0000:00/0000:00:08.3
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:14.0 -> ../../../devices/pci0000:00/0000:00:14.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:14.3 -> ../../../devices/pci0000:00/0000:00:14.3
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:18.0 -> ../../../devices/pci0000:00/0000:00:18.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:18.1 -> ../../../devices/pci0000:00/0000:00:18.1
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:18.2 -> ../../../devices/pci0000:00/0000:00:18.2
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:18.3 -> ../../../devices/pci0000:00/0000:00:18.3
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:18.4 -> ../../../devices/pci0000:00/0000:00:18.4
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:18.5 -> ../../../devices/pci0000:00/0000:00:18.5
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:18.6 -> ../../../devices/pci0000:00/0000:00:18.6
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:00:18.7 -> ../../../devices/pci0000:00/0000:00:18.7
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:01:00.0 -> ../../../devices/pci0000:00/0000:00:01.1/0000:01:00.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:01:00.1 -> ../../../devices/pci0000:00/0000:00:01.1/0000:01:00.1
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:06:00.0 -> ../../../devices/pci0000:00/0000:00:01.2/0000:06:00.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:07:00.0 -> ../../../devices/pci0000:00/0000:00:02.2/0000:07:00.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:08:00.0 -> ../../../devices/pci0000:00/0000:00:02.3/0000:08:00.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:09:00.0 -> ../../../devices/pci0000:00/0000:00:02.4/0000:09:00.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:3a:00.0 -> ../../../devices/pci0000:00/0000:00:08.1/0000:3a:00.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:3a:00.1 -> ../../../devices/pci0000:00/0000:00:08.1/0000:3a:00.1
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:3a:00.2 -> ../../../devices/pci0000:00/0000:00:08.1/0000:3a:00.2
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:3a:00.3 -> ../../../devices/pci0000:00/0000:00:08.1/0000:3a:00.3
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:3a:00.4 -> ../../../devices/pci0000:00/0000:00:08.1/0000:3a:00.4
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:3a:00.5 -> ../../../devices/pci0000:00/0000:00:08.1/0000:3a:00.5
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:3a:00.6 -> ../../../devices/pci0000:00/0000:00:08.1/0000:3a:00.6
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:3a:00.7 -> ../../../devices/pci0000:00/0000:00:08.1/0000:3a:00.7
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:3b:00.0 -> ../../../devices/pci0000:00/0000:00:08.3/0000:3b:00.0
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:3b:00.3 -> ../../../devices/pci0000:00/0000:00:08.3/0000:3b:00.3
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:3b:00.4 -> ../../../devices/pci0000:00/0000:00:08.3/0000:3b:00.4
lrwxrwxrwx 1 root root 0 feb 21 12:01 0000:3b:00.6 -> ../../../devices/pci0000:00/0000:00:08.3/0000:3b:00.6
[pikaloid@FlowX16EndeavourOS ~]$ ls -l /sys/bus/pci/devices/0000:00:08.3/
total 0
drwxr-xr-x 3 root root    0 feb 21 12:01 0000:00:08.3:pcie001
drwxr-xr-x 3 root root    0 feb 21 12:01 0000:00:08.3:pcie002
drwxr-xr-x 3 root root    0 feb 21 12:01 0000:00:08.3:pcie010
drwxr-xr-x 8 root root    0 feb 21 12:01 0000:3b:00.0
drwxr-xr-x 8 root root    0 feb 21 12:01 0000:3b:00.3
drwxr-xr-x 8 root root    0 feb 21 12:01 0000:3b:00.4
drwxr-xr-x 7 root root    0 feb 21 12:01 0000:3b:00.6
-r--r--r-- 1 root root 4096 feb 21 15:27 acpi_index
-r--r--r-- 1 root root 4096 feb 21 15:27 aer_dev_correctable
-r--r--r-- 1 root root 4096 feb 21 15:27 aer_dev_fatal
-r--r--r-- 1 root root 4096 feb 21 15:27 aer_dev_nonfatal
-r--r--r-- 1 root root 4096 feb 21 15:27 aer_rootport_total_err_cor
-r--r--r-- 1 root root 4096 feb 21 15:27 aer_rootport_total_err_fatal
-r--r--r-- 1 root root 4096 feb 21 15:27 aer_rootport_total_err_nonfatal
-r--r--r-- 1 root root 4096 feb 21 15:27 ari_enabled
-rw-r--r-- 1 root root 4096 feb 21 15:27 broken_parity_status
-r--r--r-- 1 root root 4096 feb 21 12:01 class
-rw-r--r-- 1 root root 4096 feb 21 15:27 config
-r--r--r-- 1 root root 4096 feb 21 15:27 consistent_dma_mask_bits
-r--r--r-- 1 root root 4096 feb 21 15:27 current_link_speed
-r--r--r-- 1 root root 4096 feb 21 15:27 current_link_width
-rw-r--r-- 1 root root 4096 feb 21 15:27 d3cold_allowed
-r--r--r-- 1 root root 4096 feb 21 12:01 device
-r--r--r-- 1 root root 4096 feb 21 15:27 dma_mask_bits
lrwxrwxrwx 1 root root    0 feb 21 12:01 driver -> ../../../bus/pci/drivers/pcieport
-rw-r--r-- 1 root root 4096 feb 21 15:27 driver_override
-rw-r--r-- 1 root root 4096 feb 21 15:27 enable
lrwxrwxrwx 1 root root    0 feb 21 15:27 firmware_node -> ../../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:3d
lrwxrwxrwx 1 root root    0 feb 21 15:27 iommu -> ../0000:00:00.2/iommu/ivhd0
lrwxrwxrwx 1 root root    0 feb 21 15:27 iommu_group -> ../../../kernel/iommu_groups/11
-r--r--r-- 1 root root 4096 feb 21 15:27 irq
-r--r--r-- 1 root root 4096 feb 21 15:27 label
drwxr-xr-x 2 root root    0 feb 21 12:01 link
-r--r--r-- 1 root root 4096 feb 21 15:27 local_cpulist
-r--r--r-- 1 root root 4096 feb 21 15:27 local_cpus
-r--r--r-- 1 root root 4096 feb 21 15:27 max_link_speed
-r--r--r-- 1 root root 4096 feb 21 15:27 max_link_width
-r--r--r-- 1 root root 4096 feb 21 12:01 modalias
-rw-r--r-- 1 root root 4096 feb 21 15:27 msi_bus
drwxr-xr-x 2 root root    0 feb 21 12:01 msi_irqs
-rw-r--r-- 1 root root 4096 feb 21 15:27 numa_node
drwxr-xr-x 3 root root    0 feb 21 12:01 pci_bus
drwxr-xr-x 2 root root    0 feb 21 12:01 power
-r--r--r-- 1 root root 4096 feb 21 15:27 power_state
--w--w---- 1 root root 4096 feb 21 15:27 remove
--w------- 1 root root 4096 feb 21 15:27 rescan
--w------- 1 root root 4096 feb 21 15:27 reset
-rw-r--r-- 1 root root 4096 feb 21 15:27 reset_method
-r--r--r-- 1 root root 4096 feb 21 15:27 resource
-r--r--r-- 1 root root 4096 feb 21 12:01 revision
-r--r--r-- 1 root root 4096 feb 21 15:27 secondary_bus_number
-r--r--r-- 1 root root 4096 feb 21 15:27 subordinate_bus_number
lrwxrwxrwx 1 root root    0 feb 21 12:01 subsystem -> ../../../bus/pci
-r--r--r-- 1 root root 4096 feb 21 12:01 subsystem_device
-r--r--r-- 1 root root 4096 feb 21 12:01 subsystem_vendor
-rw-r--r-- 1 root root 4096 feb 21 12:01 uevent
-r--r--r-- 1 root root 4096 feb 21 12:01 vendor

Can you read (=output) file /sys/bus/pci/devices/0000:00:08.3/label ?

Omg not, I cant. Then is due to lack of user permissions, isnt it?

bash: /sys/bus/pci/devices/0000:00:08.3/label: Permission denied

Neither with su it let me read.

Not sure if it is the permissions or something else.
But you can see if any of the folders in that file’s path is restricted from ordinary users.

That’s interesting. Something special with that file, maybe some linux guru here can explain?

1 Like

One long shot idea: have you rebooted lately? Just thinking if there have been e.g. recent kernel update and reboot has not been done yet…

Oh, and keeping system fully updated is essential: sudo pacman -Syu
And as others said, avoid downloading software from third party sources, instead use pacman (or yay) for installing it.

Yes, every day I reboot at least once either for updates or because I turn off completely so that the battery does not discharge.
I have never installed anything other than with pacman and use -Syuu once a week. :smiling_face_with_tear:

Ps: I just used -Syu and reboot but nothing.

Have you not installed the Nvidia drivers yet? It would be nice to see your hardware output. You can post the url.

inxi -Faz | eos-sendlog

Also have you tried running a test install of the nvidia drivers? You could post the output here from the test.

nvidia-inst -t

Since normal user can view/read the folder contents, there is nothing blocking.
Then

user/other can read the file. Permissions issue does not make sense… :face_with_head_bandage:

I just think it’ a hardware issue related to poor UEFI Bios.

2 Likes

Not a proper habit. Use pacman -Syu instead, unless you have issues that suggest this as a solution/workaround.

Not yet, I’ll try and post the hardware output when I get home again.

1 Like

No, until now I had no problems with software.
It was a recommendation that I read in many places in case it was necessary to downgrade to maintain compatibility, but from what I see it would be better to stick to -Syu.

1 Like

What desktop are you running?

DE? Kde plasma / Wayland

Yeah… that’s what i use too! :wink:

Edit: Not Wayland though for me. If you have Nvidia it also needs to have some additional things and it does work.

1 Like