I also meant to say that after logging in into this black screen you can
"prime select nvidia" and reboot again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
I'm facing the same problem with Ubuntu 20.04.1 LTS and GeForce 310M,
using an old Samsung QX310.
Without these drivers, the preinstalled intel driver works fine.
But with "prime-select intel" I boot into a black screen.
To go back into the DE, first I have to press Ctrl+Alt+F4 and then input
my
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: nvidia-prime (Ubuntu Eoan)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: ubuntu-drivers-common (Ubuntu Eoan)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime
Ubuntu 20.04
sudo prime-select intel
restart
stuck on HP/Kubuntu logo
Had to switch back in recovery mode:
sudo prime-select nvidia
Laptop:
https://support.hp.com/ru-ru/document/c06074117
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I'm facing the exact same problem on Ubuntu 20.04. Is there any
workaround?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with
Great, thanks for testing!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with prime-select intel: prime-select does not
update
This bug was fixed in the package ubuntu-drivers-common - 1:0.7.8.1
---
ubuntu-drivers-common (1:0.7.8.1) focal; urgency=medium
* tests/gpu-manager.py:
- Do not test against renamed intel modules.
We don't rename intel modules (such as i915-brw) any more.
This fixes
albertomilone, looks good to me.
I tried switching from nvidia to intel and back rebooting on each
attempt and haven't managed to reproduce the issue. Looks like
reordering udev rules and/or adding another device class in your change
helped (thanks a lot!).
I don't see an nvidia device in lspci
Also, please make sure to do a cycle of "sudo prime-select intel" and
"sudo prime-select intel" so that the new udev rules are in place.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
Ok, that would be nvidia-prime (0.8.14) and ubuntu-drivers-common
(1:0.7.8.1) then. Thank you.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error
I'm on focal now, just got the updated packages.
I will give it a try soon.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with
*would like
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with prime-select intel: prime-select does not
update initramfs to blacklist
@Dmitrii: if you would to test, please add the following PPA:
https://launchpad.net/~oem-solutions-group/+archive/ubuntu/nvidia-
driver-staging
and update nvidia-prime (0.8.14~0.19.10.1) and ubuntu-drivers-common
(1:0.7.8.1~0.19.10.1)
Also, make sure that the nvidia driver is not blacklisted in
This bug was fixed in the package nvidia-prime - 0.8.14
---
nvidia-prime (0.8.14) focal; urgency=medium
* prime-offload:
- Detect nvidia modules more accurately before using prime.
We don't want to catch i2c_nvidia_gpu or any other module
that is not relevant.
*
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-prime (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => In Progress
** Changed in: nvidia-prime (Ubuntu)
Thanks, will help you with testing for sure.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with prime-select intel: prime-select does not
I am working on a few fixes to make sure that the nvidia devices are
removed before the nvidia modules are loaded (I think this is what is
going on in your case), and that booting in intel ("Power Saving") mode
doesn't mislead GDM into using PRIME when the NVIDIA GPU is actually
disabled (this
** Tags added: champagne
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with prime-select intel: prime-select does not
update initramfs
Based on a discussion with ~albertomilone, powering down the NVIDIA GPU
while keeping the modules loaded is the way to go long-term as opposed
to blacklisting the modules.
The power management feature is described here (requires Turing GPUs and above):
20 matches
Mail list logo
