void-linux / void-linux/void-packages
gdm does not launch after enabling nvidia DRM (nvidia optimus)
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.4k
- Forks
- 2.8k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 299
Description
Is this a new report?
Yes
System Info
Void 6.3.13_1 x86_64 GenuineIntel uptodate rrrmmnFFFFFFFF
Package(s) Affected
gdm-44.1_2, nvidia-535.86.05_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
Setting the nvidia_drm.modeset=1 kernel parameter (or options nvidia-drm modeset=1 in /etc/modprobe.d) enables nvidida Direct Rendering Manager KMS and gdm works like usual.
Actual behaviour
Setting the kernel parameter and starting gdm freezes the entire system, i.e. even switching to an another tty is impossible.
Steps to reproduce
- install the nvidia proprietary driver and gnome; enable dbus
- set the
nvidia_drm.modeset=1kernel parameter (through grub in my case) - start the gdm service
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the freeze with gdm-44.1_2 and nvidia-535.86.05_1 after enabling nvidia_drm.modeset=1, following the listed installation and service-start steps. Inspect the gdm service and the kernel/modprobe configuration involved; done means gdm starts normally without freezing the system.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100