Cleaning Nvidia Packages

foozarinho · 12 February 2022 11:59

Hello everyone!
Before typing this message and starting this new thread I tried to use the search function for the request I am willing to do.

I've changed the 90% of the hardware from the past desktop. New moba, cpu and ram.. So happy At the moment I am using the integrated graphic of the 12900K while waiting for the new AMD Radeon card. Before I had a NVIDIA 3080.

Now the question is: how can I perfectly clean and remove the nvidia driver that triggers at each kernel/nvidia driver update ? If i just try to remove it from pacman it says that many dependencies will break.

To be clear: now the pc is useable and is a beast, I want to do this just to remove unneeded nvidia packages and have everything clean.

Additional question: is worth to enable Wayland now that I dont use Nvidia Graphic?

Thanks a lot,
G.

System:
  Kernel: 5.16.8-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=14d91570-f762-4106-889d-9a851d6dc02c rw rootflags=subvol=@
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1
    resume=UUID=f1d4967a-02c4-4be4-be76-96ec8d6adaf1 loglevel=3
  Desktop: GNOME 41.3 tk: GTK 3.24.31 wm: gnome-shell dm: GDM 41.3
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME Z690-A v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 1003
    date: 01/19/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: Discharging
CPU:
  Info: model: 12th Gen Intel Core i9-12900K bits: 64 type: MST AMCP
    arch: Alder Lake family: 6 model-id: 0x97 (151) stepping: 2 microcode: 0x18
  Topology: cpus: 1x cores: 16 mt: 8 tpc: 2 st: 8 threads: 24 smt: enabled
    cache: L1: 1.4 MiB desc: d-8x32 KiB, 8x48 KiB; i-8x32 KiB, 8x64 KiB
    L2: 14 MiB desc: 8x1.2 MiB, 2x2 MiB L3: 30 MiB desc: 1x30 MiB
  Speed (MHz): avg: 4655 high: 5210 min/max: 800/5200:3900 scaling:
    driver: intel_pstate governor: performance cores: 1: 5074 2: 5100 3: 5107
    4: 4993 5: 5110 6: 5110 7: 5109 8: 5210 9: 5109 10: 5100 11: 5102
    12: 5108 13: 4751 14: 4406 15: 5037 16: 5100 17: 3899 18: 3905 19: 3904
    20: 3881 21: 3887 22: 3899 23: 3911 24: 3915 bogomips: 152985
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
    mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel AlderLake-S GT1 vendor: ASUSTeK driver: i915 v: kernel
    bus-ID: 00:02.0 chip-ID: 8086:4680 class-ID: 0300
  Display: x11 server: X.Org 1.21.1.3 compositor: gnome-shell driver:
    loaded: modesetting alternate: fbdev,intel,vesa display-ID: :1 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0")
    s-diag: 777mm (30.6")
  Monitor-1: DP-1 res: 2560x1440 hz: 165 dpi: 109
    size: 598x336mm (23.5x13.2") diag: 686mm (27")
  OpenGL: renderer: Mesa Intel Graphics (ADL-S GT1) v: 4.6 Mesa 21.3.5
    direct render: Yes
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
    chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: Sennheiser Sennheiser USB-ED 01 type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-2.1:4 chip-ID: 1395:003c
    class-ID: 0300 serial: <filter>
  Sound Server-1: ALSA v: k5.16.8-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.45 running: yes
Network:
  Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
    port: N/A bus-ID: 05:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 port: N/A bus-ID: 00:0e.0 chip-ID: 8086:467f rev: class-ID: 0104
Drives:
  Local Storage: total: 4.56 TiB used: 215.36 GiB (4.6%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT1000P1SSD8
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B
    speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: P3CR013
    temp: 28.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD40EFAX-68JH4N0 size: 3.64 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 0A82 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Cruzer Edge
    size: 14.66 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: 1.27 scheme: GPT
Partition:
  ID-1: / raw-size: 896.84 GiB size: 896.84 GiB (100.00%)
    used: 215.32 GiB (24.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 896.84 GiB size: 896.84 GiB (100.00%)
    used: 215.32 GiB (24.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 896.84 GiB size: 896.84 GiB (100.00%)
    used: 215.32 GiB (24.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 896.84 GiB size: 896.84 GiB (100.00%)
    used: 215.32 GiB (24.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 34.38 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
  ID-2: swap-2 type: zram size: 31.09 GiB used: 2.5 MiB (0.0%)
    priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 483 Uptime: 4m wakeups: 2 Memory: 31.09 GiB
  used: 4.47 GiB (14.4%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.1.0 Packages: pacman: 1374 lib: 433 Shell: fish v: 3.3.1
  default: Bash v: 5.1.16 running-in: gnome-terminal inxi: 3.3.12
Garuda (2.5.4-2):
  System install date:     2021-11-03
  Last full system update: 2022-02-12
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       No/Undetected
  Snapshots:               Snapper
  Failed units:

TNE · 12 February 2022 12:09

Run mhwd -li
And then remove any of those Nvidia configs via sudo mhwd -r pci [name]

foozarinho · 12 February 2022 12:30

Thanks for the fast reply

Now there are only those packages that tells me there is a required dependency. Is it safe to remove mhwd-db-garuda-git ?

could not satisfy dependencies:
- removing mhwd-nvidia-470xx breaks dependency 'mhwd-nvidia-470xx' required by mhwd-db-garuda-git
- removing mhwd-nvidia-390xx breaks dependency 'mhwd-nvidia-390xx' required by mhwd-db-garuda-git

Do you suggest me to use wayland ?

jonathon · 12 February 2022 14:57

Only if you don’t want to use MHWD in the future. These remaining packages are database files containing PCI IDs of the hardware.

Try it and see how it works for you.

TNE · 12 February 2022 17:05

No. It has nothing to do with nvidia drivers so I don’t see why you would either.

Bro · 12 February 2022 19:34

It’s do-able. Basically, if all of your hardware has been successfully identified, drivers installed & configured, etc. Do not do so if doing so breaks critical dependencies. Know what you are doing.

I have done so recently just to see what hooks it was going to break–dependencies, configs, etc. It was painless on this Intel/Intel desktop rig. It was relatively painless, but…this is a 2019 rig, all of my hardware is common and all bought with Linux in mind. It has no problems running Arch, Debian Testing, or Slackware.

Then again, I don’t mind breaking a system if doing so satisfies a current curiosity. Your mileage may vary. I certainly do not recommend it to anyone. I am just replying to your question. Personally, unless you have some driving need to do so, I’d leave it sit. It does no harm that I’m aware of. Except I don’t know anything about nVidia anymore, I don’t have your computer, and you and I probably have very different computing habits and needs.

Curated distributions like Garuda are not like Arch or a few other distributions where knowing your hardware’s requirements is needed before you can even make a start. Distributions such as this one assume you do not have that same level of knowledge, skill, experience, and drive.

Garuda, like many other distributions such as Manjaro, is a tightly woven fabric. You can’t expect to pluck at a loose end without risking damage to the whole weave.

system · 14 February 2022 19:34

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.