[Kernel-packages] [Bug 1596216] Re: Black screen on boot; no modeset workaround broken by 16.04

2016-09-15 Thread Christopher M. Penalver
Joe Helfrifch, the next step is to fully commit bisect from kernel 4.2 to 4.4 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following

[Kernel-packages] [Bug 1596216] Re: Black screen on boot; no modeset workaround broken by 16.04

2016-09-13 Thread Joe Helfrifch
4.8-rc6 does not resolve this issue. Neither did the Oibaf driver PPA, or the AMD Catalyst drivers for 16.04. I have to question this process of just blindly testing the next RC each time one comes out. This problem is related to the 8700P AMD processor (and similar AMD chipsets) and/or the

[Kernel-packages] [Bug 1596216] Re: Black screen on boot; no modeset workaround broken by 16.04

2016-09-09 Thread Christopher M. Penalver
Joe Helfrifch, to keep this relevant to upstream, one would want to test the latest mainline kernel (now 4.8-rc5) as it is released. Could you please advise? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1596216] Re: Black screen on boot; no modeset workaround broken by 16.04

2016-09-08 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1596216] Re: Black screen on boot; no modeset workaround broken by 16.04

2016-07-09 Thread Joe Helfrifch
This issue IS NOT resolved by v4.7-rc6-yakkety/, nor is the nomodeset workaround restored. -- 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/1596216 Title: Black screen on boot; no modeset

[Kernel-packages] [Bug 1596216] Re: Black screen on boot; no modeset workaround broken by 16.04

2016-06-26 Thread Christopher M. Penalver
Joe Helfrifch, both is fine. However, the primary focus is the black screen on bootup without any WORKAROUNDs (it should just work in the default configuration). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1596216] Re: Black screen on boot; no modeset workaround broken by 16.04

2016-06-26 Thread Joe Helfrifch
Can you specify if I should be testing for the black screen on bootup, the failure of the nomodeset workaround, or both? -- 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/1596216 Title:

[Kernel-packages] [Bug 1596216] Re: Black screen on boot; no modeset workaround broken by 16.04

2016-06-25 Thread Christopher M. Penalver
Joe Helfrifch, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following: 1) The one to test is

[Kernel-packages] [Bug 1596216] Re: Black screen on boot; no modeset workaround broken by 16.04

2016-06-25 Thread Joe Helfrifch
The laptop is an HP 15-ab153nr. Specs: http://support.hp.com/us-en/product/HP-Pavilion-15-Notebook-PC- series/8499302/model/8857403/document/c04773160/ I'm not certain what specific update caused the black screen issue to appear. I know that the problem first appeared between Jan 23 and Feb 1

[Kernel-packages] [Bug 1596216] Re: Black screen on boot; no modeset workaround broken by 16.04

2016-06-25 Thread Christopher M. Penalver
Joe Helfrifch, thank you for reporting this and helping make Ubuntu better. 1) Could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description)? 2) Could you please advise to which update specifically correlates to this issue