ubuntu-sponsors was still subscribed and a task open for gdm3/focal.
AFAICT, the issue was somehow resolved in ubuntu-drivers in focal and
there's nothing to actually sponsor.
If sponsorship is still needed, please provide more details and
resubscribe ubuntu-sponsors.
** Changed in: gdm3 (Ubuntu
Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: gdm3 (Ubuntu Impish)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3
Thanks, just opened a separate bug:
[nvidia340] display hangs 10s on boot with nvidia-340
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1973604
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpa
looks like nvidia-drm is not built in nvidia-340.
could you report the other bug for it takes 10 seconds when booting in
nvidia-340?
and we can leave the information there.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubunt
Thanks for investigating !
below is what you requested ...
1.dkms status
nvidia-340, 340.108, 5.4.0-109-generic, x86_64: installed
nvidia-340, 340.108, 5.4.0-110-generic, x86_64: installed
virtualbox, 6.1.32, 5.4.0-109-generic, x86_64: installed
virtualbox, 6.1.32, 5.4.0-110-generic, x86_64: insta
nope, drm is not nvidia_drm.
I don't have 5.4 + nvidia-340 environment.
Thus, I would like to get more information from you.
Could you please share
1. dkms status
2. find /lib/modules/$(uname -r) -name 'nvidia*'
3. your "/var/lib/dkms/" probably have nvidia-340 build log with your current
kernel
modinfo nvidia-drm
modinfo: ERROR: Module nvidia-drm not found.
modinfo nvidia_drm
modinfo: ERROR: Module nvidia_drm not found.
modinfo nvidia
filename:
/lib/modules/5.4.0-110-generic/kernel/drivers/char/drm/nvidia.ko
inxi -G
Graphics: Device-1: NVIDIA GT218 [GeForce 210] driver:
but it doesn't show in your lsmod.
how about `modinfo nvidia_drm`?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race
Hi,
I do not remember blacklisting nvidia-drm intentionally, but will check !
Anyway don't you think this line from journalctl:
kernel: [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0
indicates nvidia-drm is fine ?
Running Mint 20.3 still with kernel 5.4 if that matters
update:
no transition plan for nvidia-340.
Then let's see why your nvidia-drm gone.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot
ok, I aware the `nvidia-drm` should support in nvidia-340.
Did you blacklist it?
Can you check the nvidia-drm whether presenting in your system?
you could probably found it under
find ... /lib/modules/$(uname -r)/...
--
You received this bug notification because you are a member of Ubuntu
Deskto
Hi,
I aware you don't have "nvidia_drm" which is needed for gdm as well.
u-d-c was wait the "nvidia_drm" be probed and your nvidia driver is 340 is
quite old as what I known.
FWIK, the legacy driver should be nvidia-390 and the next is 470.
I wondering why nvidia-340 is not yet be transited to 3
Hi,
did it reverting to ubuntu-drivers-common 1:0.8.1 (focal) >
XXX_before.txt logs in ZIP
accountname@hostname:~$ systemd-analyze time
Startup finished in 5.469s (kernel) + 5.395s (userspace) = 10.864s
graphical.target reached after 4.814s in userspace
accountname@hostname:~$ systemd-analyze
Hi, would you please share:
1. lspci -nvk
2. /var/log/gpu-manager.log
3. journalctl -b -k
4. dpkg -l | grep nvidia
5. lsmod | grep nvidia
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/
Hi,
seems that the change from 1:0.9.0~0.20.04.5 to 1:0.9.0~0.20.04.6
did introduce for me a 10s extra delay at each startup,
despite the fact that it's a desktop with only one (pretty old) Nvidia discrete
graphic card.
systemd-analyze blame
10.403s gpu-manager.service
9.927s plymouth-quit
** Changed in: gdm3 (Ubuntu Focal)
Status: Incomplete => Triaged
** Changed in: gdm3 (Ubuntu Impish)
Status: Incomplete => Triaged
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => Medium
** Changed in: gdm3 (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: g
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to rac
This bug was fixed in the package ubuntu-drivers-common -
1:0.9.2.4~0.21.10.1
---
ubuntu-drivers-common (1:0.9.2.4~0.21.10.1) impish; urgency=medium
[ Jeremy Szu ]
* 71-u-d-c-gpu-detection.rules,
gpu-manager.c:
- Wait for the nvidia-drm module to be loaded. This works arou
This bug was fixed in the package ubuntu-drivers-common -
1:0.9.0~0.20.04.6
---
ubuntu-drivers-common (1:0.9.0~0.20.04.6) focal; urgency=medium
[ Jeremy Szu ]
* 71-u-d-c-gpu-detection.rules,
gpu-manager.c:
- Wait for the nvidia-drm module to be loaded. This works around
Note that if nvidia_drm is starting so late then plymouth won't display
in that case. Because Plymouth prioritises DRM and won't fall back to
any other options (hence won't display anything!) unless boot takes
longer than 8 seconds. It's related to
https://gitlab.freedesktop.org/plymouth/plymouth/-
This bug was fixed in the package gdm3 - 42.0-1ubuntu1
---
gdm3 (42.0-1ubuntu1) jammy; urgency=medium
* Merge with debian, remaining changes:
+ readme.debian: update for correct paths in ubuntu
+ control.in:
- don't recommend desktop-base
- depend on bash for con
Tested impish version
```
ubuntu-drivers-common:
Installed: 1:0.9.2.4~0.21.10.1
```
and the log shows
```
...
Takes 660ms to wait for nvidia udev rules completed.
```
thus, the result is PASS.
** Tags removed: verification-needed verification-needed-impish
** Tags added: verification-done ver
Tested focal version
```
ubuntu-drivers-common:
Installed: 1:0.9.0~0.20.04.6
```
and the log shows
```
...
Takes 640ms to wait for nvidia udev rules completed.
```
thus, the result is PASS.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received thi
Hello jeremyszu, or anyone else affected,
Accepted ubuntu-drivers-common into impish-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.9.2.4~0.21.10.1 in a few hours, and then in the -proposed
repository.
Please help us by tes
Hello jeremyszu, or anyone else affected,
Accepted ubuntu-drivers-common into focal-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.9.0~0.20.04.6 in a few hours, and then in the -proposed
repository.
Please help us by testin
Hi Seb,
FWIK, the fix from gdm is not mandatory.
The display-manager (inside u-d-c) will handle it.
but if any flavor which doesn't use u-d-c then gdm upstream also provide this
commit
https://gitlab.gnome.org/GNOME/gdm/-/commit/ecbd9694458194e24f356ba9d37fc4f3a515c3dd#note_1402863
to fix this i
is there anything needed from gdm there?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia driver
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
** Changed in: gdm3 (Ubuntu Focal)
Status: New => Incomplete
** Changed in: gdm3 (Ubuntu Impish)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.5.1
---
ubuntu-drivers-common (1:0.9.5.1) jammy; urgency=medium
* Change maximum open file descriptors limit for the process in
the test suite. This should fix the FTBFS.
-- Alberto Milone Mon, 07 Mar 2022
17:16
** Tags removed: gdm3
** Tags added: nvidia
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia dri
** Summary changed:
- [nvidia][xorg] display hangs on boot LOGO
+ [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia
driver probe
** Tags added: gdm3
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubunt
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Impish)
Importance: Undecided => High
--
You received this bug notification because
** Also affects: gdm3 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: gdm3 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-co
** Description changed:
[Impact]
- * In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
+ * In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some
u-d-c for focal
** Patch added: "0001-Make-sure-nvidia-drm-rules-action-processed.focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1958488/+attachment/5562740/+files/0001-Make-sure-nvidia-drm-rules-action-processed.focal.debdiff
--
You received this bug not
u-d-c for impish
** Patch added: "0001-Make-sure-nvidia-drm-rules-action-processed.impish.patch"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1958488/+attachment/5562739/+files/0001-Make-sure-nvidia-drm-rules-action-processed.impish.patch
--
You received this bug noti
u-d-c patch for jammy
** Patch added: "0001-Make-sure-nvidia-drm-rules-action-processed.jammy.patch"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1958488/+attachment/5562733/+files/0001-Make-sure-nvidia-drm-rules-action-processed.jammy.patch
--
You received this bug n
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) => jeremyszu (os369510)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
** Changed in: oem-priority
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO
To manage
** Description changed:
[Impact]
* In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm start
When I build the 536491641, I use meson build.
When 1c9e4c93d, I use gbp buildpackage.
Thus, I tried dh_quilt_patch then gbp buildpackage on 1c9e4c93d.
The issue is gone.
Based on above test, I think it's likely related to debian/rules.
Something cause it (or has higher fail rate) happens.
Also
The issue is happening in debian/ubuntu only. Thus, I'm not sure the
upstream is correct place to discuss instead of debian/ubuntu.
This commit (536491641) works good.
| * 1c9e4c93d (HEAD, refs/bisect/bad) New upstream release
| * 4106a87d5 Update upstream source from tag 'upstream/41.0'
| |\
I tried the upstream gdm on focal (60 reboot cycles) and can not
reproduce the issue.
I'm trying jammy and could reproduce this issue.
Let me build upstream version on jammy.
** Description changed:
[Impact]
* In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
ca
Last time I checked, "gdm_prefer_xorg" is still required in 61-gdm.rules
otherwise the issue still occurs.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg]
the "gdm-wait-for-drm" is only maintain in ubuntu-focal also upstream
doesn't use "gdm-disable-wayland" anymore but "gdm-runtime-config"
instead.
Anyway, I will try the gdm from upstream version to see whether having
the same issue.
--
You received this bug notification because you are a member
The attachment "lp1958488_gdm-wait-for-drm_wait_for_boot_vga.debdiff"
seems to be a patch. If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-pr
** Description changed:
+ [Impact]
+
+ * In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
+ * If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm start
"boot_vga" only exists for PCI device, so this change will make VMs and
boards that don't use PCI GFX wait for straight 10 seconds.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Note that gnome-shell (which also renders the login screen for gdm)
always uses the primary iGPU for rendering regardless of whether some
monitors are plugged into a dGPU port. The latter get their framebuffers
rendered on the iGPU but copied to the dGPU for output on every frame.
This makes sense
This patch doesn't need to apply to jammy/impish because
debian/patches/gdm.rules-Keep-wayland-enabled-in-all-nvidia-configuratio.patch
Please let me know if my assumption is incorrect.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
for focal
** Patch added: "lp1958488_gdm-wait-for-drm_wait_for_boot_vga.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1958488/+attachment/742/+files/lp1958488_gdm-wait-for-drm_wait_for_boot_vga.debdiff
** Tags added: oem-priority originate-from-1956556 sutton
** Changed in
52 matches
Mail list logo
