Not able to install nvidia drivers for my graphics card

Hi, about an hour ago I posted problems with my audio in the sound category. Therefore id did inxi -Fz in the terminal to provide system information and posted that as well. Reading that information, I realized that my GeForce RTX 3050ti mobile does not seem to have a proper driver. I tried to fix that in different ways now but yet I am not successful. I tried to install drivers by using the hardware configuration GUI tool, tried to install drivers via the GUI software manager and even to install an actual .run file from the nvidia website but none of that did work.

Actually it seems, my attempts made everything worse. Right now inxi refuses to work properly and does not show information about graphics. It stops after CPU:

System:
  Kernel: 6.6.16-2-MANJARO arch: x86_64 bits: 64
  Desktop: Cinnamon v: 6.0.4 Distro: Manjaro Linux
Machine:
  Type: Laptop System: ASUSTeK product: Vivobook_ASUSLaptop N7401ZE_N7401ZE
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: N7401ZE v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: N7401ZE.301 date: 06/02/2022
Battery:
  ID-1: BAT0 charge: 51.7 Wh (70.3%) condition: 73.5/70.0 Wh (105.0%)
CPU:
  Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12700H bits: 64
    type: MST AMCP cache: L2: 11.5 MiB
  Speed (MHz): avg: 404 min/max: 400/4600:4700:3500 cores: 1: 400 2: 400
    3: 487 4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
    13: 400 14: 400 15: 400 16: 400 17: 400 18: 400 19: 400 20: 400


System:
  Kernel: 6.6.16-2-MANJARO arch: x86_64 bits: 64
  Desktop: Cinnamon v: 6.0.4 Distro: Manjaro Linux
Machine:
  Type: Laptop System: ASUSTeK product: Vivobook_ASUSLaptop N7401ZE_N7401ZE
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: N7401ZE v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: N7401ZE.301 date: 06/02/2022
Battery:
  ID-1: BAT0 charge: 51.7 Wh (70.3%) condition: 73.5/70.0 Wh (105.0%)
CPU:
  Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12700H bits: 64
    type: MST AMCP cache: L2: 11.5 MiB
  Speed (MHz): avg: 404 min/max: 400/4600:4700:3500 cores: 1: 400 2: 400
    3: 487 4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
    13: 400 14: 400 15: 400 16: 400 17: 400 18: 400 19: 400 20: 400



That doesn’t look to good. Is there anything I could do to fix that?

Undo everything you did, especially the .run file stuff.
I think it has an uninstall flag, ex

./NVIDIA-Linux-x86_150.50.run --uninstall

Thanks for your quick reply. I had no success trying to install that file because I had to exit x-server before. I did some research on the internet about that and then decided not to go further this way because of warnings about .run files .

I tried to undo the rest as good as I could but so far it didn’t work out. Any other ideas?

It is difficult for us to suggest how to walk back the previous actions if we dont know what they were.

history | tail -n100

That for example should show us the last 100 commands.
Maybe it can be used to uncover those previous actions?

I fear it doesn’t. It shows me not beeing successful about my audio and graphics issues:

  1  sudo pamac update
    2  sudo add-pamac-repository multiverse
    3  sudo pamac-build ttf-ms-fonts
    4  sudo pamac build ttf-ms-fonts
    5  mhwd-kernel -li
    6  sudo pamac -Syyu
    7  sudo pacman -Syyu
    8  df -h
    9  free -h
   10  alsamixer
   11  exit
   12  alsamixer
   13  inxi -Aa
   14  pavucontrol
   15  sudo alsa-info.sh --upload
   16  inxi -Fz
   17  ls /home
   18  sudo bash NVIDIA-Linux-aarch64-535.154.05.run
   19  sudo bash /home/NVIDIA-Linux-aarch64-535.154.05.run
   20  rm /home/NVIDIA-Linux-aarch64-535.154.05.run
   21  sudo rm /home/NVIDIA-Linux-aarch64-535.154.05.run
   22  ls /Downloads
   23  ls /home/timok/Downloads
   24  sudo mv /home/timok/Downloads/NVIDIA-Linux-x86_64-535.154.05.run /home
   25  sudo bash NVIDIA-Linux-x86_64-535.154.05.run
   26  sudo bash /home/NVIDIA-Linux-x86_64-535.154.05.run
   27  reboot
   28  sudo pacman update
   29  pacman -Syu
   30  sudo pacman -Syu
   31  sudo mhwd -a pci nofree 0300.
   32  nvidia-Einstellungen
   33  nvidia-Einstellungen.
   34  reboot
   35  inxi -Fz
   36  inxi -Fz
   37  inxi -Fz
   38  sudo pacman -Syu
   39  inxi -Fz
   40  ./NVIDIA-Linux-x86_64-535.154.05.run
   41  history | tail -n100

But it does not show the stuff that I tried to do with installing more actual nvidia drivers via the software manager GUI.

So your actions were isolated to ‘installing some things in pamac’ ?

If so, it still uses the pacman log so we can look there

tail -n100 /var/log/pacman.log

(again I use the last 100 lines 
 of course edit that number to see more or less etc)

I took al larger number and scrolled a little bit through it and that seems to be the important part to me:

2024-02-22T23:05:22+0100] [ALPM] installed nvidia-470xx-dkms (470.223.02-2)
[2024-02-22T23:05:22+0100] [ALPM] transaction completed
[2024-02-22T23:05:22+0100] [ALPM] running '30-systemd-update.hook'...
[2024-02-22T23:05:22+0100] [ALPM] running '70-dkms-install.hook'...
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing srv kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing desktopfs-pkgs.txt kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing usr kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing proc kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing sys kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing etc kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing mnt kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing bin kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing boot kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing root kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing sbin kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing rootfs-pkgs.txt kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing tmp kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing home kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing run kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing swap kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing dev kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing lib64 kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing var kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing opt kernel headers for module nvidia/470.223.02.
[2024-02-22T23:05:22+0100] [ALPM-SCRIPTLET] ==> ERROR: Missing lib kernel headers for module nvidia/470.223.02.

Is that the problem?

I cant tell if its throwing those errors while installing anyways, or if they aborted the install.

But now we have some idea.

pacman -Qsq 'dkms|nv' 

That should show us all packages matching those strings.
If all you did was install some things like that, then we should be able to pick and remove them.

First of all: Thank you for your help!

adobe-source-code-pro-fonts
babl
double-conversion
egl-wayland
ffmpeg
java-runtime-common
jre8-openjdk
jre8-openjdk-headless
lib32-libvdpau
lib32-xcb-util-keysyms
libetonyek
libimagequant
libnumbertext
libnvme
libpipeline
libsamplerate
libsixel
libvdpau
libwebp
libwpg
libxnvctrl-470xx
linux66-nvidia-470xx
mhwd-nvidia
mhwd-nvidia-390xx
mhwd-nvidia-470xx
networkmanager-openvpn
nvidia-470xx-dkms
nvidia-470xx-settings
nvidia-470xx-utils
nvidia-prime
openvpn
perl
perl-http-date
prrte
s-nail
v4l-utils
v86d
xcb-util-keysyms
xcb-util-renderutil
xf86-video-nouveau
zimg

I also updated the kernel to version 6.6.16-2-MANJARO . Should I undo that also?

One last thing might be to check configuration files in /etc/X11/

ls /etc/X11/xorg.conf.d

If you see anything in there thats not keyboard, touchpad, or similarly innocuous you probably want to backup/remove it.

Ok, I am going to run with the idea that 470 is what you want for now.
(just in case of the off chance simply ripping out what was added might break desktop interaction)

This should install any of the following needed packages and replace the problematic dkms ones.

sudo pacman -Syu nvidia-470xx-utils nvidia-470xx-settings libxnvctrl-470xx nvidia-prime

With that done lets use mhwd

sudo mhwd -f -i pci video-hybrid-intel-nvidia-470xx-prime

Now 
 this should be marginally functional.
But I dont think 470 is actually what you want.

Either way, please review mhwd at this point (maybe inxi too? but I dont expect much change until a reboot, given the need for modules to be started etc)

mhwd -li -l

If you are feeling good about it and its offered then you probably want the latest (unnumbered).

sudo mhwd -i pci video-hybrid-intel-nvidia-prime

At this point you can come back to show us how things are looking or jump right in to a reboot.

That should be fine. Probably even desirable.

De nada :slight_smile:

I already struggle here:

sudo mhwd -f -i pci video-hybrid-intel-nvidia-470xx-prime

It returns:

config 'video-hybrid-intel-nvidia-470xx-prime' conflicts with config(s): video-hybrid-intel-nvidia-prime

Alright, I thought we might hit something with the way things are, but I didnt expect that.
Its probably the mhwd profile installed before this began (and the steps afterwards were outside of mhwd, etc).
Still with the -f (force) I would have expected it to go through.

Option 1:
Remove it first.

sudo mhwd -r pci video-hybrid-intel-nvidia-prime

And continue.

Technically you want to end up on the one it thinks you already have.
Reinstalling 470 was a middle step.

Option 2:

So if you are feeling extra gumption today you can skip ahead with force reinstalling the one you really want right away.

sudo mhwd -f -i pci video-hybrid-intel-nvidia-prime

I chose option one and did successfully remove ‘video-hybrid-intel-nvidia-prime’.

But when I continued with:

sudo mhwd -f -i pci video-hybrid-intel-nvidia-prime

it says:

udo mhwd -f -i pci video-hybrid-intel-nvidia-prime
> Installing video-hybrid-intel-nvidia-prime...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-prime/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
AbhĂ€ngigkeiten werden geprĂŒft 

Fehler: Vorgang konnte nicht vorbereitet werden (Kann AbhĂ€ngigkeiten nicht erfĂŒllen)
:: Entfernen von nvidia-470xx-utils verletzt AbhÀngigkeit »nvidia-utils=470.223.02«, benötigt von nvidia-470xx-dkms
Error: pacman failed!
Error: script failed!

Looks like we didnt replace one of the dkms package.

Oh, I know, its because it conflicts with the current (unnumbered) packages and not the 470 ones.

No matter. We will do the same thing here with the current packages.
(That is install the associated packages first, before using mhwd)

sudo pacman -Syu nvidia-utils lib32-nvidia-utils nvidia-settings libxnvctrl nvidia-prime

Accept replacements.

And mhwd to finish up

sudo mhwd -f -i pci video-hybrid-intel-nvidia-prime

I am sorry, but that did not work either:

sudo pacman -Syu nvidia-utils lib32-nvidia-utils nvidia-settings libxnvctrl nvidia-prime

sudo pacman -Syu nvidia-utils lib32-nvidia-utils nvidia-settings libxnvctrl nvidia-prime
[sudo] Passwort fĂŒr timok: 
:: Paketdatenbanken werden synchronisiert 

 core ist aktuell
 extra ist aktuell
 multilib ist aktuell
:: VollstÀndige Systemaktualisierung wird gestartet 

AbhĂ€ngigkeiten werden aufgelöst 

Nach in Konflikt stehenden Paketen wird gesucht 

:: nvidia-utils und nvidia-470xx-utils stehen miteinander in Konflikt (nvidia-libgl). nvidia-470xx-utils entfernen? [j/N] j
:: libxnvctrl und libxnvctrl-470xx stehen miteinander in Konflikt. libxnvctrl-470xx entfernen? [j/N] j
:: nvidia-settings und nvidia-470xx-settings stehen miteinander in Konflikt. nvidia-470xx-settings entfernen? [j/N] j
Fehler: Vorgang konnte nicht vorbereitet werden (Kann AbhĂ€ngigkeiten nicht erfĂŒllen)
:: Entfernen von nvidia-470xx-utils verletzt AbhÀngigkeit »nvidia-utils=470.223.02«, benötigt von linux66-nvidia-470xx
:: Entfernen von nvidia-470xx-utils verletzt AbhÀngigkeit »nvidia-utils=470.223.02«, benötigt von nvidia-470xx-dkms

Oh dkms.
It stands for ‘dynamic kernel module support’.

With a dependency hell like this we might be forgiven for just removing them first.

sudo pacman -Rns nvidia-470xx-utils nvidia-470xx-dkms linux66-nvidia-470xx

Even more unhinged would be skip dependency checks (dont normally do this)

sudo pacman -Rdd nvidia-470xx-utils nvidia-470xx-dkms linux66-nvidia-470xx

(and continue)

I am very sorry. I think “dependency hell” is very appropriate. And it continues:
I had to skip the dependency checks and then continued:

sudo pacman -Syu nvidia-utils lib32-nvidia-utils nvidia-settings libxnvctrl nvidia-prime

That seemed to work although there are some warnings:

sudo pacman -Syu nvidia-utils lib32-nvidia-utils nvidia-settings libxnvctrl nvidia-prime
:: Paketdatenbanken werden synchronisiert 

 core ist aktuell
 extra ist aktuell
 multilib ist aktuell
:: VollstÀndige Systemaktualisierung wird gestartet 

AbhĂ€ngigkeiten werden aufgelöst 

Nach in Konflikt stehenden Paketen wird gesucht 

:: libxnvctrl und libxnvctrl-470xx stehen miteinander in Konflikt. libxnvctrl-470xx entfernen? [j/N] j
:: nvidia-settings und nvidia-470xx-settings stehen miteinander in Konflikt. nvidia-470xx-settings entfernen? [j/N] j

Pakete (7) libxnvctrl-470xx-470.223.02-1 [Entfernung]
           nvidia-470xx-settings-470.223.02-1 [Entfernung]
           lib32-nvidia-utils-545.29.06-1  libxnvctrl-545.29.06-1
           nvidia-prime-1.0-4  nvidia-settings-545.29.06-1
           nvidia-utils-545.29.06-4

GesamtgrĂ¶ĂŸe der installierten Pakete:  840,54 MiB
GrĂ¶ĂŸendifferenz der Aktualisierung:    838,58 MiB

:: Installation fortsetzen? [J/n] j
(5/5) SchlĂŒssel im SchlĂŒsselbund werden geprĂŒft    [######################] 100%
(5/5) Paket-IntegritĂ€t wird ĂŒberprĂŒft              [######################] 100%
(5/5) Paket-Dateien werden geladen                 [######################] 100%
(5/5) Auf Dateikonflikte wird geprĂŒft              [######################] 100%
(7/7) VerfĂŒgbarer Festplattenspeicher wird erm...  [######################] 100%
:: PaketÀnderungen werden verarbeitet 

(1/2) Entfernung lÀuft nvidia-470xx-settings       [######################] 100%
(2/2) Entfernung lÀuft libxnvctrl-470xx            [######################] 100%
(1/5) Installiert wird nvidia-utils                [######################] 100%
If you run into trouble with CUDA not being available, run nvidia-modprobe first.
If you use GDM on Wayland, you might have to run systemctl enable --now nvidia-resume.service
Optionale AbhĂ€ngigkeiten fĂŒr nvidia-utils
    nvidia-settings: configuration tool [ausstehend]
    xorg-server: Xorg support [Installiert]
    xorg-server-devel: nvidia-xconfig
    opencl-nvidia=545.29.06: OpenCL support
(2/5) Installiert wird lib32-nvidia-utils          [######################] 100%
Optionale AbhĂ€ngigkeiten fĂŒr lib32-nvidia-utils
    lib32-opencl-nvidia
(3/5) Installiert wird libxnvctrl                  [######################] 100%
(4/5) Installiert wird nvidia-settings             [######################] 100%
(5/5) Installiert wird nvidia-prime                [######################] 100%
:: Post-transaction-Hooks werden gestartet 

(1/7) Creating system user accounts...
(2/7) Reloading system manager configuration...
(3/7) Reloading device manager configuration...
(4/7) Arming ConditionNeedsUpdate...
(5/7) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux65.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.5-x86_64 -g /boot/initramfs-6.5-x86_64.img --microcode /boot/intel-ucode.img
==> Starting build: '6.5.3-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.5-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux65.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.5-x86_64 -g /boot/initramfs-6.5-x86_64-fallback.img -S autodetect --microcode /boot/intel-ucode.img
==> Starting build: '6.5.3-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.5-x86_64-fallback.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64.img --microcode /boot/intel-ucode.img
==> Starting build: '6.6.16-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64-fallback.img -S autodetect --microcode /boot/intel-ucode.img
==> Starting build: '6.6.16-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64-fallback.img'
==> Image generation successful
(6/7) Reloading system bus configuration...
(7/7) Updating the desktop file MIME type cache...

But when I continued

sudo mhwd -f -i pci video-hybrid-intel-nvidia-prime

it again didn’t work:

sudo mhwd -f -i pci video-hybrid-intel-nvidia-prime
> Installing video-hybrid-intel-nvidia-prime...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-prime/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
:: Paketdatenbanken werden synchronisiert 

 core wird heruntergeladen 

 extra wird heruntergeladen 

 multilib wird heruntergeladen 

Warnung: nvidia-utils-545.29.06-4 ist aktuell -- Überspringe
Warnung: nvidia-settings-545.29.06-1 ist aktuell -- Überspringe
Warnung: libxnvctrl-545.29.06-1 ist aktuell -- Überspringe
Warnung: nvidia-prime-1.0-4 ist aktuell -- Überspringe
Warnung: lib32-nvidia-utils-545.29.06-1 ist aktuell -- Überspringe
Fehler: Ziel nicht gefunden: linux65-nvidia
Error: pacman failed!
Error: script failed!

At least, inxi is working properly again:

Graphics:
  Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] driver: i915 v: kernel
  Device-2: NVIDIA GA107M [GeForce RTX 3050 Ti Mobile] driver: N/A

But still no driver for the GeForce

(or would I have to reboot before anyways?)

Are you still in kernel 6.5? I thought we moved to 6.6

Please ensure you are booted into 6.6

uname -r

(if not you will need to boot into 6.6. selection can be made from grub during boot.)
If you are, then you can remove the 6.5 kernel, as it is EOL (end of life).

Then continue.


When we get there you will still not be using nvidia. At least not by default or for the desktop.
You have hybrid graphics.
That is an integrated intel iGPU, and a dedicated nvidia dGPU.
prime (and the associated mhwd profiles) helps with this by providing the necessary configs and scripts to use nvidia selectively.

Again, when we get there, we will then be able to test this functionality.

glxinfo | grep 'renderer string'
prime-run glxinfo | grep 'renderer string'

In this example if things are working as they should, the first command should return the intel device, and the second command should return the nvidia.

Ok, I checked the kernel version. I am in 6.6


I