I just found out about this. I wanted to get rid of the screen tearing
that I observed on my Nitro AN515-53 laptop running Ubuntu 18.04.3 LTS
with NVIDIA GeForce GTX 1050 Mobile GPU.
I used https://askubuntu.com/a/020 and set nvidia_drm modeset=1 but
then my external monitors didn't work after
I should add that the "fix" I reported is only a narrow fix. The
internal display works. But external displays don't work if you have
nvidia drivers, gdm3 and if you are using modeset=1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Closed per comment #20. Discussion continues in bug 1714881...
** Changed in: gdm3 (Ubuntu)
Status: New => Invalid
** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Daniel, with the latest 17.10 the nvidia problems are now more specific and
easier to reproduce.
Neither of my Thinkpads gets to the login screen in discrete Nvidia mode iff
modeset=1 is used.
In hybrid graphics, the session starts, I suspect this is due to the
intel driver being available. If
** Summary changed:
- gdm3 nvidia modeset=1 is broken, external screens don't work
+ gdm3 nvidia modeset=1 is broken, external screens don't work on a Thinkpad p50
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Good news from my side; I just updated everything on th ThinkPad W520, an
old Optimus laptop. the Uubntu 17.10 desktop now works with hybrid
graphics, prime sync and gdm3 using the latest updates (pre-release
channel). I have not added any PPAs so it's using the 375 driver currently
in the 17.10 re
Thanks Doug, that bug report is exactly as the nvidia forum so you and I
are doing the same thing.
On 28 August 2017 at 02:41, Doug McMahon <1706...@bugs.launchpad.net>
wrote:
> bug reports aren't suitable for troubleshooting but anyway I do as shown
> here
> https://ubuntuforums.org/showthread.p
bug reports aren't suitable for troubleshooting but anyway I do as shown here
https://ubuntuforums.org/showthread.php?t=2365449
noting that I've lenovo ideapads, no options to use discrete only so using the
typical optimus, i.e. intel handles display, nvidia handles rendering, all via
nvidia-prim
HI Doug, it could be hardware dependent although my two Optimus laptops are
very mainstream (both Quadro). It's more likely to be configuration (I hope)
How do you achieve modeset=1? How do you confirm that you have Prime Sync
working? I use xrandr --verbose | grep PRIME
regards
Tim
On 27 Aug
As far as hybrid (optimus) machines maybe this is hardware dependent?
On all mine (660m, 775m, 940m) nvidia modeset=1 & Prime Synchronization work
just fine, 16.04.3 thru 17.10.
In 16.04.3 obviously using lightdm, in 17.10 using gdm3.
--
You received this bug notification because you are a membe
Sorry, that was premature. I had not enabled modeset=1 properly.
After doing that
a) in Optimus mode, only the laptop display works. The nvidia settings control
panel opens, but it detects no screens.
b) in discrete nvidia BIOS mode, gdm is stuck in a greeter loop when trying to
start a Gmome or
On the newer machine, the P50, I reinstalled 17.10 ubuntu yesterday,
with pre-release packages enabled. It is using gdm3. It works, even with
nvidia modeset=1 and external monitors. It is not obvious to me which
updated packages have fixed this, since I also tried pre-release on the
broken install.
It is also broken on a ThinkPad W520, which is much older hardware
(although still supported by current nvidia drivers). The Nvidia driver,
gdm3, gnome (or gnome ubuntu) and modeset=1 is broken. Replace gdm3 with
lightdm, and everything works.
--
You received this bug notification because you are
And also note that modeset=1 is not designed to activate wayland. It is
necessary to use the Prime Synchonization feature of the new nvidia
drivers, which is actually a feature of X 1.19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Update & simplication.
This bug affects 17.10 & 17.04 with the current LTS support nvidia drivers.
This bug affects both my laptops with nvidia hardware.
External monitors are not necessary to reproduce.
Reproduction is simple.
1. Activate the nvidia hardware using discrete mode. Therefore no int
Thanks, I look forward to it. It works with lightdm, though. What is GDM
doing that leads to a kernel panic, that lightdm does not do?
On 31 July 2017 at 12:03, Daniel van Vugt
wrote:
> Oh, it appears your "p50 with a quadro M1000M" is relatively new.
>
> I read that Canonical has a kernel fix o
Oh, it appears your "p50 with a quadro M1000M" is relatively new.
I read that Canonical has a kernel fix on the way that *might* help, but
that discussion is hidden in private bug 1647617. So if and when that
fix gets released I will give updates here.
--
You received this bug notification becau
** This bug is no longer a duplicate of bug 1705369
Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop
with an Intel GPU)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17064
*** This bug is a duplicate of bug 1705369 ***
https://bugs.launchpad.net/bugs/1705369
** This bug has been marked a duplicate of bug 1705369
Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop
with an Intel GPU)
--
You received this bug notification because you ar
That;s even worse. I don't any working screen, no login.
This is not a trivial bug, I think, although I'd be happy for an easy
solution.
ul 26 17:26:38 raffles systemd[2817]: Starting Accessibility services bus...
Jul 26 17:26:38 raffles dbus-daemon[2832]: Successfully activated service
'org.a11y
If everything works fine with lightdm then you can configure gdm to
behave the same as lightdm.
Just edit /etc/gdm3/custom.conf and uncomment: #WaylandEnable=false
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
The problem is that Optimus (Nvidia's hybrid driver technology) requires
modeset=1 to use it properly so there are millions of laptop users who will
have a problem with this :)
https://devtalk.nvidia.com/default/topic/957814/linux/prime-and-prime-synchronization/
Plus it works fine with lightdm.
I think it might be a general problem with Wayland (which is what gets
used if you set modeset=1):
https://bugs.freedesktop.org/show_bug.cgi?id=94851
So GDM/Wayland uses the first GPU only, which is your Intel GPU, the one
wired to the laptop screen.
** Bug watch added: freedesktop.org Bugzilla
I suggest you should just avoid Wayland if you want multi-GPU to work
properly. That means using modeset=0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706474
Title:
gdm3 nvidia modeset=1 is brok
** Also affects: nvidia-graphics-drivers-375 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: black-screen gnome-17.10 multimonitor nvidia
** Tags removed: gnome-17.10
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "xrandr output"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+attachment/4921331/+files/xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706474
Title:
** Attachment added: "nvidia-bug-report"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+attachment/4921327/+files/nvidia-bug-report.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
27 matches
Mail list logo
