I’ve got a G-sync compatible monitor, connected by display port cable. I have already reinstalled drivers (470.86), nothing. Am I missing something?
The monitor uses only two dp-lanes which doesn’t provide enough bandwidth. Did you already try a different DP-cable?
Thanks for your answer. I did not think about cable, I were using the one which ame in the monitor’s box. Well I could get a new dp cable 1.2 version, but I got no video at all. I restarted my PC, still nothing on monitor, even bios screen does not appear on boot stage. However PC boots normally (my keyboard and mouse are on and responding). Maybe, with my last days luck cable is defective, I will try to get a new one and test again. I also include additional info.
To rule out a driver bug, please also try with the boxed cable and the 390 driver.
I tried to install nvidia-driver-390 with no luck. I’ve got error while install nvidia-dkms-390 (log attached):
Loading new nvidia-390.144 DKMS files…
Building for 5.16.11-76051611-generic
Building for architecture x86_64
Building initial module for 5.16.11-76051611-generic
ERROR (dkms apport): kernel package linux-headers-5.16.11-76051611-generic is not supported
Error! Bad return status for module build on kernel: 5.16.11-76051611-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.144/build/make.log for more information.
dpkg: error processing package nvidia-dkms-390 (–configure):
installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10
Processing triggers for initramfs-tools (0.136ubuntu6.7) …
update-initramfs: Generating /boot/initrd.img-5.16.11-76051611-generic
cryptsetup: WARNING: Resume target cryptswap uses a key file
kernelstub.Config : INFO Looking for configuration…
kernelstub : INFO System information:
OS:..................Pop!_OS 20.04
Root partition:....../dev/sda3
Root FS UUID:........d03e8164-c02b-4bc1-9ae1-c1b45d020450
ESP Path:............/boot/efi
ESP Partition:......./dev/sda1
ESP Partition #:.....1
NVRAM entry #:.......-1
Boot Variable #:.....0000
Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash
Kernel Image Path:.../boot/vmlinuz-5.16.11-76051611-generic
Initrd Image Path:.../boot/initrd.img-5.16.11-76051611-generic
Force-overwrite:.....False
kernelstub.Installer : INFO Copying Kernel into ESP
kernelstub.Installer : INFO Copying initrd.img into ESP
kernelstub.Installer : INFO Setting up loader.conf configuration
kernelstub.Installer : INFO Making entry file for Pop!_OS
kernelstub.Installer : INFO Backing up old kernel
kernelstub.Installer : INFO Making entry file for Pop!_OS
Errors were encountered while processing:
nvidia-dkms-390
E: Sub-process /usr/bin/dpkg returned an error code (1)
make.log (22.0 KB)
Those files already exist:
/usr/src/linux-headers-5.16.11-76051611-generic/include/generated/autoconf.h
/usr/src/linux-headers-5.16.11-76051611-generic/include/config/auto.conf
nvidia-driver-470 installs correctly (even nvidia-driver-510)
Maybe this error is already known, that is why I post it here. Anyway, I will try a previous kernel version (things seems so different nowadays)
That doesn’t look like a standard kernel.
That kernel is Popos’s stock kernel, I have nothing fancy in here, and nvidia-driver-470 and 510 install correctly.
Well, I had no luck with 5.15-XXXX and 5.13-XXX kernels and 390 drivers. I will try with a different distro in live mode (in order to test with a different kernel), cause I do want to format my PC yet.
Just getting back to the original problem, do you have any extra suggestion to test my card, in order to know if everything is ok with it.
I guess you should report to the PopOS bug-tracker that the 390 driver doesn’t compile.
There are currently regressions in the driver that wrong DP settings are used so the only test you could do would be cross-checking with the 390 driver, which doesn’t compile. Catch22.