** Also affects: nvidia-graphics-drivers-430 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
Status: New => Confirmed
** Also affects: nvidia-graphics-drivers-435 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: n
I just installed popOS 19.10 an an Optimus laptop, nvidia option. Out of
the box you get gdm3 and tear-free prime-sync; it uses Jeremy Soller's
solution (root rights granted in Xwrapper)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvid
Test on Intel Tiger Lake platform with nvidia dGPU (N17S-G5
PCI\VEN_10DE&DEV_1C94).
Distribution: Ubuntu
Codename: focal
kernel: 5.6.0-1018-oem
NV driver: 440.100
nvidia_drm modeset=1
gdm3: 3.34.1-1ubuntu1
xserver-xorg-core: 2:1.20.8-2ubuntu2.1
The device can detect external 4K/UHD monitor sucess
Closed due to no reply after 5 months. If anyone still experiences
problems then please open new bugs for them using the 'ubuntu-bug'
command.
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: systemd (Ubuntu)
Status: Incomplete => Wo
Can someone please retest on Ubuntu 21.10?
http://cdimage.ubuntu.com/daily-live/current/
** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: nvidia-grap
Jeremy Soller's fix to edit Xwrapper seems to be good.
The edits to the gdm service cause a crash to happen on boot.
Currently using an HP Laptop with an Intel CPU and Nvidia GPU that I
believe is Optimus.
I have the proprietary Nvidia driver running on nvidia-driver-430 as of
this comment's dat
** Summary changed:
- nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors
detected by Xorg, Pop!OS fix works.
+ nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors
detected by Xorg
--
You received this bug notification because you are a membe
I've added systemd to the bug because that seems to be involved in
device permissions, as well as proving useful in the above comments.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received t
Hi, thanks to everyone, especially Daniel for unpacking this issue.
I have had a very similar issue, where gnome shell fails to run my
external 4K/UHD display at 60HZ and I see the following failure loop
triggered in `journalctl -b -p warning _COMM=gnome-shell`:
May 02 20:39:38 JNBA434499PLL gno
Apologies, continuing the comment above (mistakenly posted when adding
the log attachment). Let me retry.
Failure loop observed:
- Failed to blit shared framebuffer: EGL failed to allocate resources for the
requested operation.
- Failed to set CRTC mode 3840x2160: No such file or directory
To s
Here's the script I run to workaround the intital failure of gnome to
use the external display after unlocking or resuming from DPMS
suspend/off.
** Attachment added: "fix-hdmi-uhd.sh"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365719/+files/fix-hdmi-uhd.sh
--
Y
Another correction. For the one workaround, switching to discrete
graphics in the BIOS only seemed to get past the initial gnome login.
But resuming from DPMS off/suspend, the same error loop happens even
when hybrid graphics is disabled in the BIOS.
Even worse, seems hardware acceleration ends up
19.10 beta and nvidia drivers 430 and 435 have the same problem. I have
made the bug title correctly specific.
** Summary changed:
- nvidia-drm.modeset=1 results in no monitors detected by Xorg
+ nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors
detected by Xorg
--
And PS: workaround continues to be: use lightdm, a five minute fix at
worst.
https://askubuntu.com/questions/139491/how-to-change-from-gdm-to-lightdm
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
h
I confirm Xwrapper root rights worked for me too.
Ubuntu 18.04
kernel: 5.3.x and 4.15.x
Nvidia driver: 435.21
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1716857
This bug persists in 20.04 daily.
The one-line Pop!OS solution
(https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/comments/26)
works, just logout and login.
Pop!OS has used this for several releases now, just saying.
** Summary changed:
- nvidia-drm.modeset=1, gdm3 and optimus lap
I think forcing all users (even on systems that don't use the NVIDIA
driver) to run X with root privileges would be a little heavy-handed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.
Is it a kernel, systemd or Nvidia issue to get the right device nodes
exposed here?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
nvidia-drm.modeset
@Alberto, couldn't prime-select do this when going into hybrid or
Optimus mode? Only users with nvidia hybrid graphics would go down this
logic path, and they are only ones who need the fix (but only if they
are using gdm3, sddm and lightdm continue to be unaffected by this)
The set of users who "
19 matches
Mail list logo