NVIDIA GA106M driver N/A

You skipped part of my post.

1 Like

Sorry, sure did...

λ nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
1 Like

Output of

dkms status

?

1 Like
[🔴] × dkms status
acpi_call/1.2.2: added
bbswitch/0.8: added
nvidia/495.46: added

Hm. "Added" is not "installed", it should look something like:

nvidia/510.39.01, 5.15.15-lqx1-1-lqx, x86_64: installed
nvidia/510.39.01, 5.16.1-zen1-1-zen, x86_64: installed

Try

sudo dkms autoinstall

and paste any output.

1 Like

Output from the autoinstall.

λ sudo dkms autoinstall

Building module:
cleaning build area...
make -j16 KERNELRELEASE=5.15.15-1-lts KVER=5.15.15-1-lts...
cleaning build area...

acpi_call.ko.zst:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/
depmod...

Building module:
cleaning build area...
make -j16 KERNELRELEASE=5.15.15-1-lts KVERSION=5.15.15-1-lts...
cleaning build area...

bbswitch.ko.zst:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/
depmod...

Building module:
cleaning build area...
'make' -j16 IGNORE_PREEMPT_RT_PRESENCE=1 NV_EXCLUDE_BUILD_MODULES='__EXCLUDE_MODULES' KERNEL_UNAME=5.15.15-1-lts IGNORE_CC_MISMATCH='__IGNORE_CC_MISMATCH' modules............
cleaning build area...

nvidia.ko.zst:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/

nvidia-uvm.ko.zst:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/

nvidia-modeset.ko.zst:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/

nvidia-drm.ko.zst:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/

nvidia-peermem.ko.zst:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/
depmod...

They're reporting similar to yours now...

❮ dkms status
acpi_call/1.2.2, 5.15.15-1-lts, x86_64: installed
bbswitch/0.8, 5.15.15-1-lts, x86_64: installed
nvidia/495.46, 5.15.15-1-lts, x86_64: installed

I will try to reboot and see if everything is working.

1 Like

Also watch out for any Bumblebee-related issues - you don't need Bumblebee for your dGPU.

1 Like

Reboot now hangs. Going to roll back unless you've got ideas to check?

Loading Linux linix-lts
Loading initial ramdisk

Hi, back to your topic.

Using Linux-LTS maybe source of issue. So try booting into default kernel, that is, Linux-Zen.

Also, boot into live medium and check if it still shows driver N/A. I don't remember for dr460nized, tbh, but in Cinnamon edition, there is nice system tray icon to switch between Nvidia only / hybrid / Integrated GPU, in live medium too.
image

So, maybe boot into cinnamon live medium might be worth it as well.
And off course, always use the option Boot with Nvidia in live medium

1 Like

This means you did something else to your system at some point, e.g. adding the nvidia drivers modules to /etc/mkinitcpio.conf, or you did a partial upgrade.

You can fix this by chrooting into the system using a live installer environment.

1 Like

Boot with nvidia drivers from installer hangs

Starting Terminate Plymouth Boot Screen

So I booted with open source drivers with the intention of switching to nvidia, after.

The only thing I did to the system after install was a system update (pacman - Syu) which would fail with a conflict between something and pipewire-jack, so I removed pipewire-jack and then update finished successfully. I certainly didn't touch /etc/mkinitcpio.conf.

λ cat /etc/mkinitcpio.conf 
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(crc32c-intel intel_agp i915 amdgpu radeon nouveau)
MODULES=(crc32c-intel intel_agp i915 amdgpu radeon nouveau)

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard keymap consolefont plymouth filesystems"

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

Hmm. I think this will conflict with the nvidia driver so shouldn't be built into the initramfs.

Change this line to

MODULES=(crc32c-intel i915)

then run

sudo mkinitcpio -P

Also ensure there's a file /etc/modprobe.d/nvidia.conf that contains blacklist nouveau .

There's some further detail about enabling KMS on the Arch wiki page, NVIDIA - ArchWiki

1 Like

Also re-run dkms autoinstall to get the three items back to installed?

I don't know what you did since NVIDIA GA106M driver N/A - #12 by nwadave so if you removed the NVIDIA drivers then yes, reinstall them.

I had to restore to a point before the dkms autoinstall to get it to boot again, but will re-run now.

1 Like

Create the file with the content I mentioned above. This should be done by default when you install the NVIDIA driver so I'm not sure what state your system is in.

It might be worth reinstalling and setting things up step-by-step rather than trying to work out what's different... :thinking:

On the other hand, read the wiki page I linked to as it contains all of the necessary information for getting the NVIDIA drivers installed and working, but it boils down to these two steps (which I mentioned above):

1 Like

Still no luck.

As for reinstalling, that's literally what this round is. Other than some typical software I always install (android studio, sublime, zoom, discord, chrome, firefox), where we started above was...

  1. A new install using open source drivers
  2. pacman -Syu (with the pipewire-jack removed to allow it to succeed)
  3. Hardware Configuration -> Auto Install Proprietary Drivers
  4. Then I started this thread

But sounds like we may have reached the end of anything straightforward, so I appreciate your help. If I get a chance, I'll keep plugging away and start digging in to the intricacies of video cards :confused:

This doesn't give me any information about what isn't working at this point. If you have the nvidia driver installed, nouveau blacklisted, and KMS enabled then the driver will work just fine.

Unless something is creating an /etc/X11/xorg.conf file, or a file under /etc/X11/xorg.conf.d? Specific configuration files aren't needed for the majority of systems, generally only to do things like enable CoolBits.

It can only be this step that's failing to work correctly, for whatever reason.

You could try a fresh install, update, then install the drivers using the steps I've outlined in this thread - it's actually trivial to install them "manually".

5 Likes

@jonathon - Fresh install and doing the install manually appears to have done the trick. Everything appears to be working as expected now after just the sudo pacman -S nvidia-dkms nvidia-settings --needed and not using the "Hardware Configuration" screen.

I appreciate your help here!

PS - Apologies for the delayed reply, apparently noobs can't post much in the first 24 hours :slight_smile:

2 Likes

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