[Kernel-packages] [Bug 1724657] Re: Boot freeze with Ubuntu 17.10-beta2 on Surface Book

2017-10-22 Thread Benjamin Braun
** Also affects: linux (Arch Linux) Importance: Undecided Status: New ** No longer affects: linux (Arch Linux) -- 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/1724657 Title: Bo

[Kernel-packages] [Bug 1724657] Re: Boot freeze with Ubuntu 17.10-beta2 on Surface Book

2017-10-22 Thread Benjamin Braun
To clarify: It still affects Arch Linux but the use of Launchpad to report arch-linux-linux bugs is not supported. -- 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/1724657 Title: Boot free

[Kernel-packages] [Bug 1724657] Re: Boot freeze with Ubuntu 17.10-beta2 on Surface Book

2017-10-23 Thread Benjamin Braun
Does adding debug earlyprintk=efi to the kernel boot parameters give any output? -- 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/1724657 Title: Boot freeze with Ubuntu 17.10-beta2 on Su

[Kernel-packages] [Bug 1724657] Re: Boot freeze with Ubuntu 17.10-beta2 on Surface Book

2017-10-24 Thread Benjamin Braun
Your intel microcode is microcode : 0x9e and 0xb2 or newer was needed to boot linux 4.13 without a hang at boot least for me. Try installing / upgrading the intel-ucode package. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux

[Kernel-packages] [Bug 1724657] Re: Boot freeze with Ubuntu 17.10-beta2 on Surface Book

2017-10-24 Thread Benjamin Braun
Well, I'm not clear on the limitations of live ISOs but since you were able to install linux- image-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb, it shouldn't be any harder to install the .deb for intel- microcode-3.20170707.1~ubuntu17.04.0 or newer. I suppose try rebooting firs