The problem persists with Kernel 5.8.0-50, but I found out that it only
occurs if the usage of the Nvidia GPU is set to "on-demand".
In pure Intel or Nvidia mode the system boots as expected.
The mode van be set via graphical Nvidia tool or via "prime-select
{nvidia|intel|on-demand|query}".
NVID
After having played around with "prime-select" instead of using the
graphical Nvidia tool my system now also boots in "on-demand" mode.
(You have to reboot after changing the settings with "prime-select".)
--
You received this bug notification because you are a member of Kernel
Packages, which i
Ben, can you tell us if it was 5.8.0-34 kernel or later?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1911352
Title:
Black screen on boot after 20.04 upgraded to kernel 5.8
Status in
apport information
** Tags added: apport-collected
** Description changed:
Yesterday Ubuntu asked me to reboot after automatic updates, and when I
rebooted it doesn't start up. Sometimes it stays on the Dell logo,
sometimes it goes to a black screen and doesn't get past that (not sure
wh
The kernel it's trying to run (assuming it's the top one in the
"advanced options" boot list) is 5.8.0-36-generic.
I run apport-collect in case it helps -- boy, that's noisy in terms of
number of comments. :-)
--
You received this bug notification because you are a member of Kernel
Packages, wh
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1911352
Title:
Black screen on boot after 20.04 upgraded to kernel 5.8
Can't reproduce this on XPS 15 9560
BIOS Information
Vendor: Dell Inc.
Version: 1.20.0
Release Date: 07/21/2020
Linux acelan-xps15-9560 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan
6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
nvidia, 460.32.03, 5.8.0-36-generic,
Good data point, thanks. It looks like there are some significant
differences between the 9550 and the 9560 that could explain that:
1) Next generation CPU: i7-6700HQ on the 9550 vs i7-7700HQ on the 9560
2) Intel HD graphics 530 on the 9550 vs 630 on the 9560
3) NVIDIA GTX 960M on the 9550 vs NVID
I have the same problem on my Acer.
Since Kernel 5.8.0-36 and also 5.8.0-38 Ubuntu 20.04.1 cannot start in graphics
mode.
(It is possible to log in on the console using e.g. Ctrl+Alt+F4 though.)
With Kernel 5.4.0-58 the system works as expected.
The problem occurs only on this system, which is
Maybe contains extra information.
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+attachment/5453569/+files/Xorg.0.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
I've got the same issue on a system76 gazelle - I just reinstalled 20.04
hoping that this would fix the issue, but the 5.8.0-38 kernel does not
complete the boot cycle by itself.
I have found that switching to tty2 and then back to tty1 causes the
boot to complete
--
You received this bug notifi
Charles, very interesting. Though I wonder if yours is a different
problem, partly because it's not in tty mode at all (for me it's in a
graphical mode, sometimes with the Dell logo up). I can't seem to switch
to tty2 using Alt-F2 or Ctrl-Alt-F2 -- what are the exact keys you're
using?
--
You rec
Just a note: in attempting to fix this issue I borked my laptop - after
disabling UEFI boot and then re-enabling it in the BIOS settings, I
couldn't boot at all. So I reinstalled Ubuntu and then was getting the
following issue after doing system updates (but still on the 5.4
kernel): https://bugs.l
If anyone affected by this bug can still reproduce it in their
environments, I would like them to try installing linux-modules-extra
and rebooting to see if the issue clears. You will need to do this with
your 5.4 kernel.
Thanks in advance,
Terry
--
You received this bug notification because yo
I have these installed:
dpkg -l | grep "linux\-[a-z]*\-"
rc linux-modules-extra-5.4.0-42-generic 5.4.0-42.46
ii linux-modules-extra-5.4.0-58-generic 5.4.0-58.64
ii linux-modules-extra-5.8.0-36-generic 5.8.0-36.40~20.04.1
ii linux-modules-extra-5.8.0-38-generic 5.8.0-38
It seems that in at least 1 case, this condition arises with linux-
modules-extra installed so my suggestion above may not help
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1911352
Title
My laptop running Groovy (20.10) is affected by this bug as well, but I
also can't figure or at least isolate where the problem could be. The
hardware is similar to what other people have reported (it's a ASUS
K501UQ, with a Core i7-6500U, Nvidia 940MX and Intel HD 520).
It seemed to have started
The ctrl+alt+f2 - this was a fresh install on a system76 machine,
running the integrated graphics. I have since loaded the NVidia drivers
and my some miracle, I no longer need this work around.
The ttys run from 1 to 7, I think, but the keyboard shortcuts to
activate them are always ctrl+alt+f
I have also had the boot problem disappear, return, and disappear
again.
On 1/22/21 11:12 AM, Wolf Pichler wrote:
> I have these installed:
>
> dpkg -l | grep "linux\-[a-z]*\-"
>
> rc linux-modules-extra-5.4.0-42-generic 5.4.0-42.46
> ii linux-modules-extra-5.4.0-58-generic 5.4.0
19 matches
Mail list logo