Ready to take the (next) Nvidia plunge?
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Ready to take the (next) Nvidia plunge?
Version 410.57 just came out (via the PPA). I heard a couple of Arch users talking about this last week; supposedly it fixes a bunch of problems, but I didn't bother to verify as my 396.54 drivers have been excellent.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Ready to take the (next) Nvidia plunge?
OK, I just did it - so far, so good. My display seems a little brighter that it was; at least the installation completed without any errors.
Re: Ready to take the (next) Nvidia plunge?
any interesting happening with dmesg?
Code: Select all
dmesg | grep -i nvidia
- catweazel
- Level 19
- Posts: 9763
- Joined: Fri Oct 12, 2012 9:44 pm
- Location: Australian Antarctic Territory
Re: Ready to take the (next) Nvidia plunge?
Nothing earth-shattering. It's running fine here.trytip wrote: ⤴Mon Oct 15, 2018 11:59 pm any interesting happening with dmesg?Code: Select all
dmesg | grep -i nvidia
https://devtalk.nvidia.com/default/topic/1041820
Full changelog.
"There is, ultimately, only one truth -- cogito, ergo sum -- everything else is an assumption." - Me, my swansong.
Re: Ready to take the (next) Nvidia plunge?
trytip wrote: ⤴Mon Oct 15, 2018 11:59 pm any interesting happening with dmesg?Code: Select all
dmesg | grep -i nvidia
Code: Select all
dmesg | grep -i nvidia
[ 19.631163] nvidia: loading out-of-tree module taints kernel.
[ 19.631169] nvidia: module license 'NVIDIA' taints kernel.
[ 19.639316] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[ 19.648087] nvidia-nvlink: Nvlink Core is being initialized, major device number 240
[ 19.648525] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[ 19.748298] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 410.57 Tue Sep 18 23:25:09 CDT 2018 (using threaded interrupts)
[ 19.759238] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 410.57 Tue Sep 18 23:23:43 CDT 2018
[ 19.761554] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[ 19.761555] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
[ 19.957657] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 238
[ 20.176846] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input12
[ 20.176931] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input13
[ 20.176998] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input14
[ 20.177058] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input15
[ 20.407477] caller os_map_kernel_space.part.7+0xda/0x120 [nvidia] mapping multiple BARs
[ 29.558696] caller os_map_kernel_space.part.7+0xda/0x120 [nvidia] mapping multiple BARs