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 dec
I saw one report that said that disabling a PCI controller solved the issue
as well, but I don't know what in my laptop could be running on that,
unless it's the memory card adapter.
Do we know that anyone is working on this upstream, or are we just
installing builds hoping something will work mag
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
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:
Bla
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
20
Public bug reported:
This bug appears to occur in several distros and architectures. On this
machine, it appeared somewhere in the last week of January, 2016, after
a system update.
On boot, the laptop monitor often flickers several times (signal
connecting and disconnecting) and always settles
I'm having the same issue. The black screen problem showed up somewhere
in the last week of January, as I documented having to use the nomodeset
boot parameter in the course of investigating another bug
(https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1537308).
The nomodeset was a valid worka
I believe this has also provided a workaround for my problems. (I never
saw the repeating keys, only intermittent random control characters.) I
finally made the change last night and left it running; after about 12
hours I had no bad events. I've occasionally seen the problem take
longer than th
Can someone with experience with the kernel devs comment on if
additional reports to the mailing list would be helpful, or just annoy
them?
--
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/15
Andrea's email to the kernel.org linux-input list can be found here:
http://www.spinics.net/lists/linux-input/msg43030.html. There doesn't
seem to be much activity on it from anyone other than Andrea. I
couldn't find a way to respond to that thread to let them know that
there are more affected us
I've got the same issue. Reported it at
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1537308.
--
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/1532746
Title:
SHIFT, ALT and CTRL pr
11 matches
Mail list logo
