#StackBounty: #boot #drivers #nvidia #xorg #wayland How to activate Wayland before arriving at login screen?

Bounty: 100

I have a boot video problem Ubuntu 18.04-4 installs in safe graphics mode only, but boots to purple screen where mouse works (NVIDIA) that can be solved by putting the video card in the first slot, arriving at the login screen, changing from xorg to wayland (xorg does not work), then putting the GPU back at slot 2.

Instead of moving my GPU everytime I reinstall my Ubuntu, how can I enable Wayland without arriving at the login screen? I don’t arrive at this screen if I use the GPU in the 2nd slot.


Get this bounty!!!

#StackBounty: #nvidia #cuda CUDA 10.2 – different installation paths

Bounty: 50

i have a problem regarding the instzallation of CUDA 10.2 and the cublas libraries.

The Cuda files are in /usr/local and the cublas files are in the /usr/include file.

Now i have a program, where i must enter a HOMe_PATH for the cuda installations, where to find them.

I tried to symlink the cublas files to /usr/local but the program cannot find the files needed.

Is there a way to copy (it is portected) the cublas files to /usr/local? Or to change the installation path of the cublas files in any way?

Thank you very much in advance

Chris


Get this bounty!!!

#StackBounty: #drivers #nvidia fresh 20.04 install with nvidia and iGPU.. only get iGPU resolutions

Bounty: 150

I am curious how am I supposed to switch to using the nvidia card on my ubuntu 20.04 setup?

on 18.04 once installed, I could just plug in and go.. seems with 20.04 it is using both iGPU and PCI-E GPU… I see the device is here, I have nvidia-smi responding with output.. but the ubuntu gnome resolution is only going up to 1920×1080.. telling me it’s using the intel iGPU off my core i7 2600K

Edit:

strangely, after reinstalling.. it now eroneously occupies the GPU even though I only get intel resolutions..

how do I revert so the iGPU is used 100% and the GPU is left freed ?

enter image description here


Get this bounty!!!

#StackBounty: #nvidia #multiple-monitors #xrandr NVIDIA – Ubuntu 20.04 – HDMI second monitor with blank screen, but xrandr detects it

Bounty: 50

For some reason, the second monitor connected via HDMI is in black (black screen), but xrandr and Nvidia Settings detects it.

    Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
   1920x1080 60.00*+ 59.97 59.96 59.93
   1680x1050 59.95 59.88
   1600x1024 60.17
   1400x1050 59.98
   1600x900 59.99 59.94 59.95 59.82
   1280x1024 60.02
   1440x900 59.89
   1400x900 59.96 59.88
   1280x960 60.00
   1440x810 60.00 59.97
   1368x768 59.88 59.85
   1360x768 59.80 59.96
   1280x800 59.99 59.97 59.81 59.91
   1152x864 60.00
   1280x720 60.00 59.99 59.86 59.74
   1024x768 60.04 60.00
   960x720 60.00
   928x696 60.05
   896x672 60.01
   1024x576 59.95 59.96 59.90 59.82
   960x600 59.93 60.00
   960x540 59.96 59.99 59.63 59.82
   800x600 60.00 60.32 56.25
   840x525 60.01 59.88
   864x486 59.92 59.57
   800x512 60.17
   700x525 59.98
   800x450 59.95 59.82
   640x512 60.02
   720x450 59.89
   700x450 59.96 59.88
   640x480 60.00 59.94
   720x405 59.51 58.99
   684x384 59.88 59.85
   680x384 59.80 59.96
   640x400 59.88 59.98
   576x432 60.06
   640x360 59.86 59.83 59.84 59.32
   512x384 60.00
   512x288 60.00 59.92
   480x270 59.63 59.82
   400x300 60.32 56.34
   432x243 59.92 59.57
   320x240 60.05
   360x202 59.51 59.13
   320x180 59.84 59.32
DP-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm
   1920x1080 60.00 + 50.00 59.94 30.00 25.00 24.00 29.97 23.98
   1920x1080i 60.00 50.00 59.94
   1280x1024 60.02
   1360x768 60.02
   1152x864 59.97
   1280x720 59.81 60.00 50.00 59.94
   1024x768 60.00
   800x600 60.32*
   720x576 50.00
   720x576i 50.00
   720x480 60.00 59.94
   640x480 60.00 59.94
   720x400 70.08
DP-1-2 disconnected (normal left inverted right x axis y axis)
HDMI-1-3 disconnected (normal left inverted right x axis y axis)

I tried with propietary drivers of Nvidia and Nouveau’s drivers, and I have the same result.
On Ubuntu 18.04 with the LTS Kernel (4.15 was?) works perfectly. Same with Windows 10.
Since 19.10 it doesn’t work.

The nvidia-drm modeset is on 0 (nvidia-drm modeset=0).

Laptop: Asus
Intel: i5-6300
Graphic card: Nvidia GTX960m

PD: With nomodeset it works perfectly. But still, it doesn’t work with propietary drivers and nouveau.

PD2: I tried with only Nvidia and only Intel graphics. No results.

PD3: I tried with a Live USB and it doesn’t work neither the second monitor. This just detects a second monitor, but in the second monitor the only thing I can see is a blank screen. I’m tired trying to make this work seeing a lot of pages. Please, if anyones can tell me if someone had a similar problem or what I can do. I don’t want to use again W10. Thanks!


Get this bounty!!!

#StackBounty: #drivers #nvidia #display #screen Screen tearing on laptop's built-in display

Bounty: 100

I have HP Pavilion (15-bc203nw with gtx1050) with fresh Ubuntu 20.04 and nvidia-440 driver installed.
I use it with external monitor and have a problem with screen tearing, but only on built-in monitor. The external one works perfectly.

I have tried adding options nvidia_drm modeset=1 to /etc/modprobe.d/zz-nvidia-modeset.conf, but this solution disables my external monitor ad doesn’t seem to work.

I have also tried to force composition pipeline in Nvidia settings, but I can’t do it, because: “PRIME Displays cannot be controlled by nvidia-settings and must be configured by external RandR capable tool…”

screen

Tearing on built-in screen disappears when I switch GPU to Intel, but it disables my external monitor.

The same problem occurs on Ubuntu 18.04.


Get this bounty!!!

#StackBounty: #drivers #nvidia #display #screen Screen tearing on laptop's built-in display

Bounty: 100

I have HP Pavilion (15-bc203nw with gtx1050) with fresh Ubuntu 20.04 and nvidia-440 driver installed.
I use it with external monitor and have a problem with screen tearing, but only on built-in monitor. The external one works perfectly.

I have tried adding options nvidia_drm modeset=1 to /etc/modprobe.d/zz-nvidia-modeset.conf, but this solution disables my external monitor ad doesn’t seem to work.

I have also tried to force composition pipeline in Nvidia settings, but I can’t do it, because: “PRIME Displays cannot be controlled by nvidia-settings and must be configured by external RandR capable tool…”

screen

Tearing on built-in screen disappears when I switch GPU to Intel, but it disables my external monitor.

The same problem occurs on Ubuntu 18.04.


Get this bounty!!!

#StackBounty: #dual-boot #18.04 #nvidia #crash #nvidia-geforce Ubtunu 18.04 crashes or freezes after login (Dual boot, nvidia graphics)

Bounty: 50

I have a dual boot system (Ubuntu 18.04 and Windows 10) and most the time it works fine, but occasionally at startup, after selecting Ubuntu from Grub Boot and logging in) the system will crash and I’m presented with the following output

/dev/nvme0n1p5: clean, XXX/XXX files, XXX/XXX blocks
[195.544151] ucsi_ccg 0-0008: failed to reset PPM!
[195.544179] ucsi_ccg 0-0008: PPM Init failed (-110)

Or:

/dev/nvme0n1p5: recovering journal
/dev/nvme0n1p5: clearning orphaned inode XXX (uid=XXX, gid=XXX, mode=XXX, size=XXX
...
/dev/nvme0n1p5: clean, XXX/XXX files, XXX/XXX blocks

Sometimes the system just freezes and I’m unable to do anything at all.

Windows was installed first, then Ubuntu afterwards. I did have to modify the kernel parameters to be able to actually use the Ubuntu installer:

quiet splash nomodeset reboot=warm,acpi

After Ubuntu finished installing I also downloaded / updated the Additional Drivers to use NVIDIA driver metapackage from nvidia-driver-435(proprietary, tested)

Specs / Equipment:

  • Ubuntu 18.04.4 LTS Dual Booted (Windows 10 Pro N)
  • AMD Ryzen 3700x
  • 8-core processor * 16
  • GeForce RTX 2070 SUPER/PCIe/SSE2
  • 64-bit
  • Logitech G915 Wireless Keyboard
  • Logitech G703 Wireless Mouse
  • Corsair HS70 Wireless Headset

Note: Windows works fine, no issues


Get this bounty!!!

#StackBounty: #18.04 #nvidia #wine Wine with proprietary Nvidia driver on 64-bit Unbutnu

Bounty: 100

I have Ubutntu 18.04 (64 bit) with proprietary NVidia driver installed. Whenever I’m trying to start any Windows graphical app I get the following error:

libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  151 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  257
  Current serial number in output stream:  256

Having surfed around similar issues on SO communities I realized that this is likely caused by that wine is to use 32-bit graphical libs.

The issue is that NVidia proprietary 32-bit drivers installer checks for the architecture and fails the installation (despite I have multiarch-support package installed).

My question is if there is a way to work around this issue having proprietary drivers preserved. Or if not what would be the most robust way to set up those libs?

Thanks!


Get this bounty!!!

#StackBounty: #dual-boot #grub2 #nvidia #multiple-monitors Can't Boot on Dual Monitor

Bounty: 50

Summary of issue: Can’t see GRUB2 boot menu on monitor connected via DVI port.

Up until recently I had everything working fine for my Windows 10 / Ubuntu 18.04.2 dual boot setup. I had two monitors: one connected to HDMI and the other to Displayport on graphics card and using a Display-Port -> DVI cable to plug into second monitor. My primary monitor was the one connected over HDMI.

The monitor that I had plugged into HDMI failed and I bought a new one. To make the most of my new monitor, I want to connect it over Displayport. This means my 2nd monitor is now connected DVI-D to DVI-D.

Given the priority order of GPU (GTX 1050 Ti) is DVI, HDMI, Displayport this means that for booting my old 2nd monitor is now primary before the OS is loaded.

However, I am unable to see the dual boot menu. Instead I see a few lines of coloured pixels at the top of my 2nd monitor (the one connected via DVI).

Windows boot works fine (if I change BIOS to boot straight to Windows). However, the only way I can access Linux is to unplug my 2nd monitor. Then the Displayport monitor is the only one and everything works fine. Once into Linux I can then plug in the second monitor to the DVI cable and it is recognised and works.

I have tried the following (incrementally and individually):

  • Set GRUB_GFXMODE to 640×480
  • Set GRUB_TERMINAL to console
  • Changed display driver to NVIDIA rather than Linux default

Note that after updating the GRUB2 settings in /etc/default/grub I have ran the grub update. I can see the changes have taken effect when I boot with 2nd monitor unplugged.

This has me tearing my hair out – any suggestions very welcome. If I’ve ommitted any key information, please comment.

UPDATE 1

I have tried booting from a Linux boot USB. I see the same result (i.e. a few coloured lines of pixels at top of screen). Is GRUB2 compatible with DVI-D?


Get this bounty!!!

#StackBounty: #dual-boot #grub2 #nvidia #multiple-monitors Can't Boot on Dual Monitor

Bounty: 50

Summary of issue: Can’t see GRUB2 boot menu on monitor connected via DVI port.

Up until recently I had everything working fine for my Windows 10 / Ubuntu 18.04.2 dual boot setup. I had two monitors: one connected to HDMI and the other to Displayport on graphics card and using a Display-Port -> DVI cable to plug into second monitor. My primary monitor was the one connected over HDMI.

The monitor that I had plugged into HDMI failed and I bought a new one. To make the most of my new monitor, I want to connect it over Displayport. This means my 2nd monitor is now connected DVI-D to DVI-D.

Given the priority order of GPU (GTX 1050 Ti) is DVI, HDMI, Displayport this means that for booting my old 2nd monitor is now primary before the OS is loaded.

However, I am unable to see the dual boot menu. Instead I see a few lines of coloured pixels at the top of my 2nd monitor (the one connected via DVI).

Windows boot works fine (if I change BIOS to boot straight to Windows). However, the only way I can access Linux is to unplug my 2nd monitor. Then the Displayport monitor is the only one and everything works fine. Once into Linux I can then plug in the second monitor to the DVI cable and it is recognised and works.

I have tried the following (incrementally and individually):

  • Set GRUB_GFXMODE to 640×480
  • Set GRUB_TERMINAL to console
  • Changed display driver to NVIDIA rather than Linux default

Note that after updating the GRUB2 settings in /etc/default/grub I have ran the grub update. I can see the changes have taken effect when I boot with 2nd monitor unplugged.

This has me tearing my hair out – any suggestions very welcome. If I’ve ommitted any key information, please comment.

UPDATE 1

I have tried booting from a Linux boot USB. I see the same result (i.e. a few coloured lines of pixels at top of screen). Is GRUB2 compatible with DVI-D?


Get this bounty!!!