Sorry for responding so late, I've been using the workaround of setting
the device model of the virtual NIC to use "virtio" instead of "e1000e"
for the last several months for some critical production work and I
didn't want to rock the boat.
I'm currently running kernel: 5.3.0-26-generic and I'm
Kernel 5.0.0-13 (currently in disco-proposed) also solves this problem
on my XPS 15 9575 2-in-1 with a 1080p laptop panel. Thanks @sforshee
for getting this fix in so quickly!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
OK, after compiling 5.0.7 mainline + Ubuntu Patches + this patch from
here (https://patchwork.freedesktop.org/patch/296411/) to fix the link
training issue for my laptop panel, I am able to boot with modesetting.
Now I *am* noticing the problem. As others have suggested, bending back
the laptop
I've compiled a mainline build from here: https://kernel.ubuntu.com
/~kernel-ppa/mainline/v5.0.7/.
I applied all the Ubuntu patches as well as the patch from here:
https://patchwork.freedesktop.org/patch/296411/
Raw patch download here:
https://patchwork.freedesktop.org/patch/296411/raw/
And
** Summary changed:
- Linux 5.0 regression i915 module, black screen on boot for certain laptop
panels
+ Linux 5.0 black screen on boot, display flickers (i915 regression with
certain laptop panels)
--
You received this bug notification because you are a member of Kernel
Packages, which is
I also run a Dell XPS 9575 2 in 1, with BIOS 1.40 and my system is *not*
exhibiting this particular problem after a fresh 19.04 install.
Keyboard and mouse work fine with GDM, but this is also after booting
with the nomodeset kernel boot parameter.
Note: for other folks reading this thread
Sorry for the spam, last post for now I promise!
Reading this bug report more closely, it does appear different than the
bug I am encountering. With *this* bug, one sees a black screen *with*
a cursor, my symptoms are different, as the laptop panel is failing
display link training, so nothing is
OK reading the original bug reports more closely, this *does* appear to
be a different bug entirely. Because we never see a cursor on the
screen, the laptop panel literally fails link training.
** This bug is no longer a duplicate of bug 1821820
Cannot boot or install - have to use nomodeset
Here are drm messages from logs booting up with drm.debug=14 with
5.0.0-11.12. You can see the link training issues are still present.
21:00:11 kernel: [drm:intel_dp_get_link_train_fallback_values [i915]] Retrying
Link training for eDP with same parameters
21:00:11 kernel:
*** This bug is a duplicate of bug 1821820 ***
https://bugs.launchpad.net/bugs/1821820
So I'm not sure if this bug is actually a duplicate after all. I've
done a fresh install of 19.04 and upgraded to kernel 5.0.0-11.12 (which
supposedly fixed the other bug), and the link training issues
*** This bug is a duplicate of bug 1821820 ***
https://bugs.launchpad.net/bugs/1821820
Here are the relevant portions of my dmesg with drm.debug=14 as a boot
paramater. You can see my laptops display panel is still failing link
training.
21:00:11 kernel:
I just tested with a fresh install of 19.04 (booted up with nomodeset
and installed). After installation I confirmed I was running
5.0.0-11.12, but the laptop panel link training issue is still present
(Dell XPS 9575) causing a black screen on boot. The only way to boot is
with nomodeset as a
As a side note, this was the bug I had originally opened up in
launchpad, which I thought might have been a duplicate of this bug
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Doh, sorry that's what I meant to say, disco proposed.
I guess my main concern is that the release ISO for 19.04 contains this
fixed kernel. If not, users would have to boot with nomodeset, install,
then update to the fixed kernel which might be a hurdle for some folks.
--
You received this
*** This bug is a duplicate of bug 1821820 ***
https://bugs.launchpad.net/bugs/1821820
** This bug has been marked a duplicate of bug 1821820
Cannot boot or install - have to use nomodeset
--
You received this bug notification because you are a member of Kernel
Packages, which is
Question for everybody, I noticed that linux-5.0.0-10.11 which is
currently in proposed for cosmic has an explicit fix for this bug
(mentioned in the changelog). Will this kernel make it into the
official 19.04 release - or will the release use linux-5.0.0-8.9?
If the official release doesn't
Might be a duplicate of this bug?:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820
--
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/1824216
Title:
Linux 5.0 regression i915
Here's a link to the Fedora bug report tracking the same issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1695275 which also includes
lots of useful information.
** Bug watch added: Red Hat Bugzilla #1695275
https://bugzilla.redhat.com/show_bug.cgi?id=1695275
--
You received this bug
Unfortunately due to the nature of this bug, it's very hard to get any
concrete logs (at least I'm not sure how to). If I boot with kernel
modesetting for i915, then I can't even get to the ttys to pull down a
dmesg. I'd rather not install 19.04 (wiping out my existing 18.10
installation) to
Public bug reported:
On my Dell XPS 9575, I get a black screen on boot when running the 19.04
live image, OR after updating from 18.10 to 19.04. It appears to be a
kernel related bug that was introduced in 5.0 that is affected by
certain laptop panels not conforming to their stated
Looks like 4.20.3 on kernel.ubuntu.com built successfully. Thanks for
the fix!
--
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/1811721
Title:
Mainline Kernel Builds Failing for > v4.20
Thanks for the response. Who on the kernel.ubuntu.com team would able
to make these changes? I can also try to build the kernel locally to
confirm.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
One other thing to note is that the v5.0rc1 build actually succeeded, it
was v5.0rc2 that failed. Checking on the build logs again it appears
that building the nvidia kernel module is causing the problem.
--
You received this bug notification because you are a member of Kernel
Packages, which
Unfortunately the bug appears to be in on the build system that
kernel.ubuntu.com uses, so we'll be unable to provide logs from our
systems. We did point out the build log on kernel.ubuntu.com that shows
the build errors.
--
You received this bug notification because you are a member of Kernel
** Summary changed:
- Mainline Kernel Builds Failing for > v4.20.1 for amd64 on kernel.ubuntu.com
+ Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
It appears that mainline kernel builds (on kernel.ubuntu.com) have been
failing for amd64 since v4.20.1. Interestingly enough v4.20 was able to
build successfully.
Note: this also includes 5.0rc builds as well.
You can see the build logs here:
26 matches
Mail list logo
