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. The second part should transfer to your installed system. - Boot into the live session. You now have horribly low resolution but it should allow you to run ubiquity. - Install Ubuntu normally using horrible graphics - Reboot. Hopefully your kernel cmdline parameters were saved and therefore you will reboot into a happy (still horrible) fresh system. Congratulations. - If your reboot crashes odds are parts of the command line was not carried over. No worries, spam ESC to get in the grub menu then edit the kernel's entry to have both "blacklist=nouveau" and "modprobe.blacklist=nouveau". Boot into your ugly new system as previous point. - Install the nvidia proprietary drivers: "sudo ubuntu-drivers" then install the appropriate nvidia-XXX package (was nvidia-384 in my case but it depends on your hardware). - Reboot into hopefully glorious native resolution. -- 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: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On the latest daily artful image (/current as of 2017-01-14), the following occurs on a system with nVidia graphics (on my system, a GTX970) when connected to a 4k display over a displayport: https://photos.app.goo.gl/gLUva3Vgvtv0lAmj2 Steps to reproduce: - Download latest daily image, check checksums, burn to USB - Boot from USB. - Choose "Install Ubuntu" or "try ubuntu" at the menu. This happens on the livecd, but also upon ugrading the system from a previous daily with a different kernel: my "old" daily booted and installed fine with kernel 4.12.0-12, then failed with same error once dist-upgraded. On the faulty system I could test with, it seems to *only* happen over displayport/on a 4k screen (I don't own a non-4k displayport screen to test the 4k out). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
