Launchpad has imported 10 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=103351.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
This problem is still present within the 18.10 beta release
--
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/1723619
Title:
Ubuntu Desktop ISO fails to boot with nouveau on a displayport
** Changed in: linux (Ubuntu)
Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)
--
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/1723619
Title:
Ubuntu Desktop ISO fails to boot
Please try drm-tip [1] for this issue, there are some new runtime PM
fixes for nouveau.
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Could not install on GTX960 as well. Hopefully, 18.04.1 ISO installer on
next July 26th will fix this issue with Nvidia DisplayPort.
--
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/1723619
Have a similar problem. Ubuntu 18.04 with nvidia gtx 970. After the
screen locks, it's impossible to wake it up. Need to disconnect and
reconnect power to get it working again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Today's 18.04 upgrade from 17.10, using 4k or 1080 monitor with display port or
with HDMI for Radeon RX 460 booting until bios,then screen flashing with
jumbled colors every few seconds, shutdown displays Ubuntu logo.
Removing graphics card and using onboard HDMI for both is same as above, but
I stumbled upon this bug independently running Fedora 27 on Lenovo T420
with GeForce 119M, but because I plugged the monitor only after the boot
I have a stacktrace with hopefully helpful dmesg log. I attached the log
to the upstream bug report.
--
You received this bug notification because you
** Description changed:
- On the latest daily artful image (/current as of 2017-01-14), the
+ On the latest daily artful image (/current as of 2017-10-14), the
following occurs on a system with nVidia graphics (on my system, a
GTX970) when connected to a 4k display over a displayport:
** Changed in: ubuntu-release-notes
Status: Confirmed => Fix Released
--
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/1723619
Title:
Ubuntu Desktop ISO fails to boot with nouveau
** Changed in: linux
Status: Unknown => Confirmed
** Changed in: linux
Importance: Unknown => Medium
--
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/1723619
Title:
Ubuntu
** Also affects: linux via
https://bugs.freedesktop.org/show_bug.cgi?id=103351
Importance: Unknown
Status: Unknown
--
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/1723619
A bug has been filed upstream here:
https://bugs.freedesktop.org/show_bug.cgi?id=103351
** Bug watch added: freedesktop.org Bugzilla #103351
https://bugs.freedesktop.org/show_bug.cgi?id=103351
--
You received this bug notification because you are a member of Kernel
Packages, which is
For the record since I forgot to comment previously: kernel in #21
(mainline kernel with suspicious patch reverted) does boot fine with
nouveau.
(However just reverting it will probably cause other regressions)
--
You received this bug notification because you are a member of Kernel
Packages,
I just tested 4.15-rc5 and the problem still persists.
A (bit painful) workaround if you don't have a choice:
- Boot liveCD, enable "expert mode" (F6 at boot menu"
- Edit the boot line to have "blacklist=nouveau
modprobe.blacklist=nouveau" BOTH before AND after the "--" at the end of
the line.
uname -r
4.14.0-rc5-lp1723619+revert
That's (sadly) not my issue (the one that cropped up on October 6th. It
took me 4 times again to have Plymouth not freezing/GDM starting up.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Unfortunately that commit says that it fixes regressions from something
else, so I think it's too risky to simply revert it.
Have you tested any 4.14-rc kernels to see if the problem still exists
there?
--
You received this bug notification because you are a member of Kernel
Packages, which is
Mainline kernel with 13a86519202c5d119d83640d6f781f3181205d2c reverted:
http://people.canonical.com/~khfeng/lp1723619-revert/
--
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/1723619
Title:
Chris said 967003bb2cae121d345fd807eb757d949713 is good.
So the bad commit is
13a86519202c5d119d83640d6f781f3181205d2c drm/nouveau/i2c/gf119-: add support
for address-only transactions
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
The previous one is good.
Built on commit 967003bb2cae121d345fd807eb757d949713 drm/dp: Don't trust
drm_dp_downstream_id():
http://people.canonical.com/~khfeng/lp1723619-4/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Built on commit prior to c11a93f5fd9229dc7c8b90570c75cf70bc3976c2:
http://people.canonical.com/~khfeng/lp1723619-3/
--
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/1723619
Title:
Ubuntu
** Changed in: ubuntu-release-notes
Status: New => 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/1723619
Title:
Ubuntu Desktop ISO fails to boot with nouveau on a
Blacklisting nouveau allows a full boot (at a very low screen
resolution, obviously).
Kernel at #16 fails to boot.
--
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/1723619
Title:
Ubuntu
But "blacklist=nouveau modprobe.blacklist=nouveau" can boot, right?
13a86519202c5d119d83640d6f781f3181205d2c drm/nouveau/i2c/gf119-: add support
for address-only transactions:
http://people.canonical.com/~khfeng/lp1723619-2/
--
You received this bug notification because you are a member of
The kernel at #14 fails to boot.
--
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/1723619
Title:
Ubuntu Desktop ISO fails to boot with nouveau on a displayport
Status in Release Notes
Try kernel here: http://people.canonical.com/~khfeng/lp1723619-1/
Build on commit
4a5431af19bc52c4dd491e989543c66a52380f00 drm/nouveau/kms/nv50: update vblank
state in response to modeset actions
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You
As discussed on IRC kaihengfeng and I will sync up tomorrow and bissect
the problem together.
--
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/1723619
Title:
Ubuntu Desktop ISO fails to
** Tags added: nouveau
--
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/1723619
Title:
Ubuntu Desktop ISO fails to boot with nouveau on a displayport
Status in Release Notes for Ubuntu:
Do you know how you build kernel? I can build test kernels in deb format
if you don't know how to make one.
--
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/1723619
Title:
Ubuntu Desktop
Then it's highly likely that the culprit is one of the following
commits:
$ git log --pretty=oneline v4.13-rc2..v4.13-rc3 drivers/gpu/drm | grep -E
'dp|nouveau'
38bcb208f60924a031b9f809f7cd252ea4a94e5f drm/nouveau/bar/gf100: fix access to
upper half of BAR2
Tested all mainline kernels I could find for 4.13-rc*:
- 4.13-rc1: DisplayPort setup boots. Login screen appears. Choosing the
default option (wayland) results in broken desktop
(https://photos.app.goo.gl/xisx9EgTKTFoLXmJ3). Choosing the xorg
fallback works perfectly.
- 4.13-rc2: DisplayPort
Please try mainline kernel 4.13-rc*, so we can know which one contains
the first bad commit that causes the regression.
--
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/1723619
Title:
I've done further testing as you suggested. Here's a breakdown of my
findings:
I tested the following kernel versions on 4k + displayport (installed
from launchpad librarian, with their matching -extra package and an
"update-grub"):
- 4.12.0-12: Boots. System seems to crash after a few seconds
I think from you description you can install this system from the new
ISO using hdmi. Would you therefore be able to check out some of the
interim kernels between 4.12.0-12 and 4.13.0-16 to see which of those
work. They should be available in the launchpad librarian. Don't
forget to install
34 matches
Mail list logo
