This issue has been fixed in 510.54.
For installed incorrect version, please see comment#16.
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: oem-priority
Status: Confirmed => Fix Released
** Changed in:
Report a bug as https://bugs.launchpad.net/oem-priority/+bug/1964747
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963701
Title:
[NVIDIA][Wayland] graphic target not able to reach as the only
It seems a regression since https://launchpad.net/ubuntu/+source/nvidia-
graphics-drivers-510/510.54-0ubuntu0.18.04.1
because of
```
* debian/templates/control.in:
- Set XB-Support to PB (production branch).
```
Checking with maintainer on
Mar 14 02:38:53 ubuntu ubiquity: WARNING:root:_pkg_get_support
nvidia-driver-510: package has invalid Support PBheader, cannot determine
support level
Mar 14 02:38:53 ubuntu ubiquity: WARNING:root:_pkg_get_support
nvidia-driver-510-server: package has invalid Support PBheader, cannot
determine
In daily build:
kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX
platforms 470.103.01
From comment#2:
kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 510.39.01
In latest ubuntu archive:
kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX
Still could reproduce this issue with Jammy daily build (3/13)
$ sha256sum ~/Downloads/jammy-desktop-amd64.iso
1c46933bf1837e6427f994676c60d54515c6ce011276dbfe4c5a63e427fdc2c5
/home/jeremysu/Downloads/jammy-desktop-amd64.iso
1. Install third-part drivers during the installation.
2. After
** Tags added: jiayi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963701
Title:
[NVIDIA][Wayland] graphic target not able to reach as the only monitor
connect to NV GPU only on I+N machine
To
Hi Daniel,
yes, in hybrid system, different BIOS have their own way to configure
it. We just need to make sure the memory point of efifb passed from BIOS
is correct one and it's correct in this case, the boot_vga is dGPU.
I'll risk this issue on upstream to discuss and share the upstream bug
The OEM team seem to have this under control and I'm not planning on
doing any gdm3 work at all. But as a team we might want to keep an eye
on https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/171 and revisit
our defaults in the coming weeks.
** Changed in: gdm3 (Ubuntu)
Assignee: Daniel
That all said, I haven't seen any reason why we should do anything other
than go with upstream's gdm patches. If Wayland needs to be avoided in
some Nvidia setups then we should do so to get at least the login
screen.
I'm confused though, because some people have made comments suggesting
it
In a hybrid (usually muxless) laptop the BIOS will flag the Intel GPU is
the boot GPU, which means gnome-shell/mutter will flag that one as
"primary" and will do ALL shell rendering on it.
In a hybrid desktop/workstation the BIOS will *usually* disable the
integrated GPU leaving only the discrete
I did a review on the upstream MP that Daniel shared.
It looks to me that the upstream intend to disable Wayland in many of scenarios.
It contains a case:
(proprietary nvidia) + (hybrid graphics) + (laptop)
It make me feel curious that why only impact "hybrid laptop" but "hybrid
Daniel, could you check what we need here?
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => High
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The only difference is which GPU mutter/gnome-shell is trying to use as
"primary". According to the log in comment #2 it sounds like Nvidia is
indeed the primary here:
三 04 23:54:57 ubuntu-ThinkStation-P350-Tower gnome-shell[1127]: Added
device '/dev/dri/card1' (nvidia-drm) using non-atomic
*** This bug is a duplicate of bug 1959888 ***
https://bugs.launchpad.net/bugs/1959888
Hi Daniel,
This issue is talking about I+N desktop.
It may not same as a hybrid laptop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1959888 ***
https://bugs.launchpad.net/bugs/1959888
** Tags added: hybrid multigpu wayland wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963701
*** This bug is a duplicate of bug 1959888 ***
https://bugs.launchpad.net/bugs/1959888
While bug 1959888 is still open we should track it there.
** This bug has been marked a duplicate of bug 1959888
Wayland sessions can't use external monitors that are connected to an Nvidia
GPU with
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963701
Title:
[NVIDIA][Wayland] graphic target not able to reach as the only monitor
connect to NV GPU only on I+N
** Tags added: gdm3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963701
Title:
[NVIDIA][Wayland] graphic target not able to reach as the only monitor
connect to NV GPU only on I+N machine
To
** Summary changed:
- [NVIDIA][Wayland] graphic target not able to reach
+ [NVIDIA][Wayland] graphic target not able to reach as the only monitor
connect to NV GPU only on I+N machine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: nvidia-wayland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963701
Title:
[NVIDIA][Wayland] graphic target not able to reach
To manage notifications about this bug go to:
** Tags added: nvidia
** Changed in: oem-priority
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963701
Title:
[NVIDIA][Wayland] graphic target not able to reach
** Attachment added: "journal-b.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701/+attachment/5565824/+files/journal-b.txt
** Tags added: oem-priority originate-from-1956556 sutton
** Changed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
** Changed in:
23 matches
Mail list logo
