F5F Stay Refreshed Software Operating Systems NVIDIA driver 440 xconfig coolbits assistance guide

NVIDIA driver 440 xconfig coolbits assistance guide

NVIDIA driver 440 xconfig coolbits assistance guide

Pages (2): Previous 1 2
T
Tao200
Junior Member
46
05-23-2016, 12:28 AM
#11
Activate coolbits by running nvidia-xconfig with the command sudo nvidia-config --cool-bits=12. This will provide the required details to xconfig and enable coolbits.
T
Tao200
05-23-2016, 12:28 AM #11

Activate coolbits by running nvidia-xconfig with the command sudo nvidia-config --cool-bits=12. This will provide the required details to xconfig and enable coolbits.

Y
yker72
Junior Member
13
05-23-2016, 06:40 AM
#12
this seems correct. i'll install ubuntu on the nvme once more. i copied elements from my 16.04/driver 418 working xconfig and added items from the generated file on 440. i also included nvenc since it appears wasn't added by someone must have forgotten. i hope this is the right module name. i made some adjustments to the server layout to match the 16.04 version, aiming to fix the screen recorders on 440. @igormp @GrumpyOldMan Section "ServerLayout" Identifier "layout" Screen 0 "nvidia" Inactive "intel" EndSection Section "Module" Load "dbe" Load "extmod" Load "type1" Load "freetype" Load "glx" Load "nvenc" EndSection Section "Device" Identifier "intel" Driver "modesetting" BusID "PCI:0@0:2:0" Option "AccelMethod" "None" EndSection Section "Screen" Identifier "intel" Device "intel" EndSection Section "Device" Identifier "Nvidia Card" Driver "nvidia" BusID "PCI:1@0:0:0" VendorName "NVIDIA Corporation" BoardName "P102-100" Option "NoLogo" "1" Option "Coolbits" "12" Option "SLI" "Off" Option "MultiGPU" "On" EndSection
Y
yker72
05-23-2016, 06:40 AM #12

this seems correct. i'll install ubuntu on the nvme once more. i copied elements from my 16.04/driver 418 working xconfig and added items from the generated file on 440. i also included nvenc since it appears wasn't added by someone must have forgotten. i hope this is the right module name. i made some adjustments to the server layout to match the 16.04 version, aiming to fix the screen recorders on 440. @igormp @GrumpyOldMan Section "ServerLayout" Identifier "layout" Screen 0 "nvidia" Inactive "intel" EndSection Section "Module" Load "dbe" Load "extmod" Load "type1" Load "freetype" Load "glx" Load "nvenc" EndSection Section "Device" Identifier "intel" Driver "modesetting" BusID "PCI:0@0:2:0" Option "AccelMethod" "None" EndSection Section "Screen" Identifier "intel" Device "intel" EndSection Section "Device" Identifier "Nvidia Card" Driver "nvidia" BusID "PCI:1@0:0:0" VendorName "NVIDIA Corporation" BoardName "P102-100" Option "NoLogo" "1" Option "Coolbits" "12" Option "SLI" "Off" Option "MultiGPU" "On" EndSection

M
MrZezeu
Member
57
05-28-2016, 08:13 PM
#13
The setup generally fills in details automatically, but some overrides can lead to problems. My AMD version runs only five lines. https://wiki.archlinux.org/index.php/NVI...figuration They provide warnings for Nvidia cards on the Arch Wiki. Perhaps one of these resources will help. https://forums.developer.nvidia.com/t/so...nf/37305/2 I notice settings like BusID "PCI:1:0:0" and an option to allow empty initial config. You can find the BusID using lspci or /etc/gdm3/custom.conf. Waylandenable=false is another setting I see. It might be connected to Wayland, which Ubuntu uses by default now if a compatible driver exists. Alternatively, it could stem from a faulty NVIDIA driver. I don’t have a working NVIDIA card or use Wayland for troubleshooting.
M
MrZezeu
05-28-2016, 08:13 PM #13

The setup generally fills in details automatically, but some overrides can lead to problems. My AMD version runs only five lines. https://wiki.archlinux.org/index.php/NVI...figuration They provide warnings for Nvidia cards on the Arch Wiki. Perhaps one of these resources will help. https://forums.developer.nvidia.com/t/so...nf/37305/2 I notice settings like BusID "PCI:1:0:0" and an option to allow empty initial config. You can find the BusID using lspci or /etc/gdm3/custom.conf. Waylandenable=false is another setting I see. It might be connected to Wayland, which Ubuntu uses by default now if a compatible driver exists. Alternatively, it could stem from a faulty NVIDIA driver. I don’t have a working NVIDIA card or use Wayland for troubleshooting.

S
Sebluigi
Senior Member
727
05-29-2016, 12:42 PM
#14
I retrieved those bus IDs from lspci on 16.04, but coollbits didn’t work properly. xconfig functions correctly, yet the Ubuntu 20.04/440 driver issues cause terminal/tty1 prompts during boot, and an ongoing "bad USB port 7" error keeps appearing even when I can’t type commands like CDS. All USB ports function normally, so I swapped keyboards between them. That’s why I had to reinstall again—hope this helps with your setup. Does your xconfig appear correct? It seems like a mix of old files and outdated drivers, as you suggested.
S
Sebluigi
05-29-2016, 12:42 PM #14

I retrieved those bus IDs from lspci on 16.04, but coollbits didn’t work properly. xconfig functions correctly, yet the Ubuntu 20.04/440 driver issues cause terminal/tty1 prompts during boot, and an ongoing "bad USB port 7" error keeps appearing even when I can’t type commands like CDS. All USB ports function normally, so I swapped keyboards between them. That’s why I had to reinstall again—hope this helps with your setup. Does your xconfig appear correct? It seems like a mix of old files and outdated drivers, as you suggested.

G
GrinningTube
Member
185
06-02-2016, 07:32 AM
#15
In grub dropdown to the editor, set loglevel=0 for the kernel parameter before quiet spash, before booting. This should temporarily resolve USB issues so you can access the terminal. Your xorg.conf appears correct. You might consider disabling Wayland as I noticed it in my previous attempt.
G
GrinningTube
06-02-2016, 07:32 AM #15

In grub dropdown to the editor, set loglevel=0 for the kernel parameter before quiet spash, before booting. This should temporarily resolve USB issues so you can access the terminal. Your xorg.conf appears correct. You might consider disabling Wayland as I noticed it in my previous attempt.

G
Gavoga
Junior Member
40
06-02-2016, 11:01 AM
#16
deleted.
G
Gavoga
06-02-2016, 11:01 AM #16

deleted.

Pages (2): Previous 1 2