[HP Pavilion 15-ab188ca Notebook PC] Intermittent black screens

[nukedathlonman]

Using Kubuntu 16.04, my screen will go black any time from the login screen until hours later. I can ssh into the system to shut it down. If I unplug the system from it's power brick, close the lid causing it to go to sleep, and flip the screen back up, the system wakes up and the screen works again for 1-2 minutes.

Disabling DPMS didn't change anything. I don't have any remnants of the former closed Crimson display driver and never had an xorg.conf file (I made a small one that I'm using at the moment consisting of only a server layout to ensure screen savers, DPMS, etc are all off).

This didn't happen using Kubuntu 15.10 with Linux Crimson 15.12 driver.

SYSTEM INFO:
Purchased Dec 2015 (build date from BIOS - Aug 2015), HP Pavilion 15" notebook, AMD A10-8700P "Carrizo", 16GB RAM, 960GB SSD

WORKAROUND: Install https://github.com/M-Bab/linux-kernel-amdgpu-binaries

WORKAROUND: In 16.04 use http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/

[nukedathlonman (areginato)]

I believe the bug is in the current open DRI amdgpu display driver.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1577074/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[nukedathlonman (areginato)]

Been investigating a wireless problem that lead me to install Kernel 4.6-RC6 from PPA - this Kernel seems to fix this bug (as haven't run into this issue with the release candidate kernel).

[jakedp (jakedp)]

I have the same Carrizo (A10-8700P)chip and also in a HP Pavilion.This is also a bug that effects Fedora 23 and it seems the radeon driver on Mageia 5. I have noticed it also on Ubuntu 15.10 and Ubuntu Mate 15.10. It effects Korora 23 the least. It is maddening that when you buy a laptop with a AMD processor you have been waiting for you are thrown to the curb.0

[nukedathlonman (areginato)]

I was using the closed fglrx (a.k.a. Crimson 15.12) on Kubuntu 15.10 (the latest updates from the regular repository - not the ones form the various PPA's) and that worked fine for me. For 16.04 Wily, the kernel packages from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily have newer open source AMDgpu kernel drivers and those seem to work fine on the A10-8700P. Give that Kernel (or the newer RC7 one) a shot.

Just a note for Jakedp (it's another unrelated bug and really doesn't apply to this bug - so this can be ignored so far as the AMDgpu bug report) - If we have the same laptop (and I believe we do), you'll also have the same Realtek RTL8723BE Wireless adapter - there's another bug that might affect you regarding that driver's antenna selection... The fix is projected to be included in the Kernel 4.7 by the developer. I was hoping it might have got backported into the 4.6 release candidates - but it hasn't.

[jakedp (jakedp)]

I have the broadcom wireless which is the bane of my existence. Linux Mint
17.3 is having no issues. So far it is certain versions of radeon and the
amdgpu of 4.3-4.5. It is good to know that it seems to be fixed. Hopefully
the fixes will be backported into the LTS kernel. Forgot to mention this
problem is happening on Win10.
On May 9, 2016 7:25 PM, "nukedathlonman" <email address hidden> wrote:

> I was using the closed fglrx (a.k.a. Crimson 15.12) on Kubuntu 15.10
> (the latest updates from the regular repository - not the ones form the
> various PPA's) and that worked fine for me. For 16.04 Wily, the kernel
> packages from http://kernel.ubuntu.com/~kernel-
> ppa/mainline/v4.6-rc6-wily have newer open source AMDgpu kernel drivers
> and those seem to work fine on the A10-8700P. Give that Kernel (or the
> newer RC7 one) a shot.
>
> Just a note for Jakedp (it's another unrelated bug and really doesn't
> apply to this bug - so this can be ignored so far as the AMDgpu bug
> report) - If we have the same laptop (and I believe we do), you'll also
> have the same Realtek RTL8723BE Wireless adapter - there's another bug
> that might affect you regarding that driver's antenna selection... The
> fix is projected to be included in the Kernel 4.7 by the developer. I
> was hoping it might have got backported into the 4.6 release candidates
> - but it hasn't.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1577074
>
> Title:
> AMDGPU driver problems on "Carrizo" APU
>
> Status in xserver-xorg-video-amdgpu package in Ubuntu:
> Confirmed
>
> Bug description:
> Summery: I'm having a hard time tracing this down. I updated to
> Kubuntu 16.04 (from Kubuntu 15.10 - that was using the Linux Crimson
> 15.12 driver) a couple days ago on my notebook (HP Pavilion, A10-8700P
> APU), and ever since I've been having random black screens. I started
> debugging the driver, then thought it might be a DPMS issue (it's not
> - I have DPMS fully disabled currently), and now I'm back to debugging
> the driver. I don't have any remnants of the former closed Crimson
> display driver and never had an xorg.conf file (I made a small one
> that I'm using at the moment consisting of only a server layout to
> ensure screen savers, DPMS, etc are all off). The Black screen can
> happen any time from the login screen until hours later. I can ssh
> into the system to shut it down. And just discovered that if I unplug
> the system from it's power brick, I can close the lid - the system
> will goto sleep. When I flip the screen back up, the system wakes up
> and the screen works again for 1-2 minutes. I don't see any errors in
> the log files (well, outside some nasty looking ACAPI errors in
> dmesg).
>
> Steps to reproduce: boot system and use normally or simply leave
> system alone. Blank screen will happen any time after x comes up.
>
> Expected results: Screen doesn't blank unless a screen saver or power
> saver kicks in.
>
> System info: Purchased Dec 2015 (build date from BIOS - Aug 2015), HP
> Pavilion 15" notebook, AMD A10-8700P "Carrizo"...

[nukedathlonman (areginato)]

I'm sure it will - the kernel in every release receives periodic updates. But 4.6 is only a "candidate release" - a technical preview if you will while bugs and such are fully baked out of the pie for final release. You'll see one of the 4.5 kernels first - hopefully with a fix, but it's also possible that a fix might not get backported. We know there was a change, but what the change hasn't been pin pointed exactly - makes it a bit harder for the Dev/packager to backport a fix since the exact issue with the driver wasn't pinned down. Then again, I suppose they could just backport the whole driver from 4.6g, but that might lead into other bug's or issues... I'm sure they'll try to figure it out.

Aside - I don't have random black screens on the Windows 10 side. I do have (multiple) other AMD graphics drivers problems on that side though... But let's not continue this discussion - this is supposed to be a bug report and I'm sure the packagers/maintainers/Dev's would rather see discussions relevant to the filed bug.

[James Payne (jamoflaw)]

I get a simliar issue to you on my A10-8780P, although on 16.04 I can't even get it to boot without nomodeset as the blackscreen is as far as it gets. Not even sure to know where to begin getting more info on that but:

jenni@hp-grey:~/Desktop$ lspci -vvnn | grep -i AMD
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:1576]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Device [1022:1577]
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 00 [VGA controller])
00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio [1002:9840]
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:157b]
00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:157c] (prog-if 00 [Normal decode])
00:02.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:157c] (prog-if 00 [Normal decode])
00:02.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:157c] (prog-if 00 [Normal decode])
00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:157b]
00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:157c] (prog-if 00 [Normal decode])
00:08.0 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Device [1022:1578]
00:09.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:157d]
00:09.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Device [1022:157a]
00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller [1022:7914] (rev 20) (prog-if 30 [XHCI])
00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 49) (prog-if 01 [AHCI 1.0])
00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller [1022:7908] (rev 49) (prog-if 20 [EHCI])
 Subsystem: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller [1022:7908]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 4a)
 Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b]
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 11)
 Subsystem: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:1570]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:1571]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:1572]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:1573]
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:1574]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:1575]
04:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265] [1002:6900] (rev ff) (prog-if ff)

It does seem to work with the fglrx driver on 14.04 (although even then I had to boot using nomodeset before installing the fglrx driver as I had a similar black screen issue there)

Are these iss...

[penalvch (penalvch)]

nukedathlonman, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information:
apport-collect -p xorg 1577074

When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[rajat kr ghosh (rajat06)]

i had the same problem in my netbook which also have the same amd chip A10-8700p with r7 m360 i try centos 7, fedora 23-24, mint 17-18,ubuntu all have the same network problem(both wireless and wire ) display problem battery drain very low sound and all of disto show black screen at first startup and problem incise day by day

[penalvch (penalvch)]

rajat kr ghosh, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Joshua (jreynaud1)]

This bug affects me on Ubuntu 14.04, 15.10, 16.04, and Arch Linux. I too have the same AMD chip, A10-8700p, on an HP 17-g121wm. I can only get past the black screen if I boot into low-graphics mode with the nomodeset parameter.

I have scoured countless online resources looking for a solution to this problem. I hope someone knowledgeable and able to do something about it takes notice of this page and works on the bug.

[Brian (cargohook)]

This bug affects me on Ubuntu 16.04, but not on 15.10 where the fglrx drivers are still available. I have the graphics card A10-8700P APU "Carrizo" on my HP ProBook 455 G3 laptop. Like Joshua above, but only on 16.04, I can only get past the black screen if I boot into low-graphics mode with the nomodeset parameter.

However, in my web search regarding this issue, I found a recommendation at https://bugzilla.kernel.org/show_bug.cgi?id=117591 Comment #7, to append "amdgpu.runpm=0" to the kernel command line in Grub setparams. I'm going to try that with the Ubuntu 16.04 LiveUSB and report back.

[penalvch (penalvch)]

Brian, it would be helpful to track your issue and hardware, if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Brian (cargohook)]

OK, I tried the "amdgpu.runpm=0" solution with the Ubuntu 16.04 LiveUSB and while it booted in high graphics mode, I still got the black screen after a few minutes.

Christopher, I have done as you asked in Comment #15 on this thread, and the bug report I filed is at https://bugs.launchpad.net/ubuntu/+source/xorg/+filebug/34a9fa5a-51e8-11e6-8b1c-68b5996a96c8?

However I don't know how this will do any good, as I'm running Ubuntu 15.10, not 16.04 where the problem occurs. I wish AMD or Canonical or whoever is responsible for the decision to make fglrx unavailable in 16.04 would reconsider and provide for a smoother transition by allowing users with graphics cards that are still unsupported by amdgpu to "opt-in" to fglrx until AMD works out the all the kinks. It's as if they just don't care about end users whatsoever. Man, am I frustrated!

[jakedp (jakedp)]

With Linux Mint 18 and KDE Neon the bug changes from random to boot up. It
happens the first time from a cold boot. After a restart, which means
screwing up my hard drive and holding the power button. Then turning it on
and the black screen comes back.

I' am very fustrated like Brian. Canonical doesn' t need AMD to repackage
the driver for the new X Server. Abandoned by AMD and the commercial
distros. Do not advocate AMD, they must have known this problem and ignored
it.

On Sun, Jul 24, 2016 at 5:53 PM, Brian <email address hidden> wrote:

> OK, I tried the "amdgpu.runpm=0" solution with the Ubuntu 16.04 LiveUSB
> and while it booted in high graphics mode, I still got the black screen
> after a few minutes.
>
> Christopher, I have done as you asked in Comment #15 on this thread, and
> the bug report I filed is at
> https://bugs.launchpad.net/ubuntu/+source/xorg/+filebug/34a9fa5a-
> 51e8-11e6-8b1c-68b5996a96c8?
>
> However I don't know how this will do any good, as I'm running Ubuntu
> 15.10, not 16.04 where the problem occurs. I wish AMD or Canonical or
> whoever is responsible for the decision to make fglrx unavailable in
> 16.04 would reconsider and provide for a smoother transition by allowing
> users with graphics cards that are still unsupported by amdgpu to "opt-
> in" to fglrx until AMD works out the all the kinks. It's as if they just
> don't care about end users whatsoever. Man, am I frustrated!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1577074
>
> Title:
> AMDGPU driver problems on "Carrizo" APU
>
> Status in xorg package in Ubuntu:
> Incomplete
>
> Bug description:
> I'm having a hard time tracing this down. I updated to Kubuntu 16.04
> (from Kubuntu 15.10 - that was using the Linux Crimson 15.12 driver) a
> couple days ago on my notebook (HP Pavilion, A10-8700P APU), and ever
> since I've been having random black screens.
>
> I started debugging the driver, then thought it might be a DPMS issue
> (it's not - I have DPMS fully disabled currently), and now I'm back to
> debugging the driver.
>
> I don't have any remnants of the former closed Crimson display driver
> and never had an xorg.conf file (I made a small one that I'm using at
> the moment consisting of only a server layout to ensure screen savers,
> DPMS, etc are all off).
>
> The Black screen can happen any time from the login screen until hours
> later. I can ssh into the system to shut it down. And just
> discovered that if I unplug the system from it's power brick, I can
> close the lid - the system will goto sleep. When I flip the screen
> back up, the system wakes up and the screen works again for 1-2
> minutes.
>
> I don't see any errors in the log files (well, outside some nasty
> looking ACAPI errors in dmesg).
>
> HOT TO REPRODUCE:
> Boot system and use normally or simply leave system alone. Blank screen
> will happen any time after x comes up.
>
>
> EXPECTED RESULT:
> Screen doesn't blank unless a screen saver or power saver kicks in.
>
> SYSTEM INFO:
> Purchased Dec 2015 (build date from BIOS - Aug 2015), HP Pavilion 15"...

[jakedp (jakedp)]

Here is my lshw output:

description: Notebook
   product: HP Pavilion Notebook (N5R36UA#ABL)
   vendor: HP
   version: Chassis Version
   serial: 5CD6044W0B
   width: 64 bits
   capabilities: smbios-2.8 dmi-2.8 vsyscall32
   configuration: boot=normal chassis=notebook family=103C_5335KV G=N L=CON
B=HP S=PAV sku=N5R36UA#ABL uuid=35434436-3034-3457-3042-DC
4A3EF51D71
 *-core
      description: Motherboard
      product: 80AF
      vendor: HP
      physical id: 0
      version: 81.29
      serial: PFDTU018J103IL
      slot: Base Board Chassis Location
    *-firmware
         description: BIOS
         vendor: American Megatrends Inc.
         physical id: 0
         version: F.16
         date: 11/27/2015
         size: 64KiB
         capacity: 8128KiB
         capabilities: pci upgrade shadowing cdboot bootselect edd
int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9
keyboard int14serial int17printer acpi usb smartbattery
biosbootspecification netboot uefi
    *-cache:0
         description: L1 cache
         physical id: d
         slot: L1 CACHE
         size: 320KiB
         capacity: 320KiB
         clock: 1GHz (1.0ns)
         capabilities: pipeline-burst internal write-back unified
         configuration: level=1
    *-cache:1
         description: L2 cache
         physical id: e
         slot: L2 CACHE
         size: 2MiB
         capacity: 2MiB
         clock: 1GHz (1.0ns)
         capabilities: pipeline-burst internal write-back unified
         configuration: level=2
    *-memory
         description: System Memory
         physical id: 16
         slot: System board or motherboard
         size: 8GiB
       *-bank:0
            description: SODIMM DDR3 Synchronous 1600 MHz (0.6 ns)
            product: M471B1G73DB0-YK0
            vendor: Samsung
            physical id: 0
            serial: 14BE9E85
            slot: Bottom-Slot 1 (left)
            size: 8GiB
            width: 64 bits
            clock: 1600MHz (0.6ns)
       *-bank:1
            description: DDR3 [empty]
            product: A1_PartNum1
            vendor: A1_Manufacturer1
            physical id: 1
            serial: A1_SerialNum1
            slot: Bottom-Slot 2 (right)
            width: 64 bits
    *-cpu
         description: CPU
         product: AMD A10-8700P Radeon R6, 10 Compute Cores 4C+6G
         vendor: Advanced Micro Devices [AMD]
         physical id: 20
         bus info: cpu@0
         version: AMD A10-8700P Radeon R6, 10 Compute Cores 4C+6G
         slot: P0
         size: 1600MHz
         capacity: 1800MHz
         width: 64 bits
         clock: 100MHz
         capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxs
r sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp constant_tsc
rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclm
ulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c
lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalign
sse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm
topoext perfctr_core perfctr_nb bpext mwaitx cpb hw_pstate vmmcal
l fsgsbase bmi1 avx2 smep bmi2 xsaveopt a...

[Timo Aaltonen (tjaalton)]

I need the exact model of the laptop, this might be one that has been certified in the past and has now regressed.

[Timo Aaltonen (tjaalton)]

scratch that, 8700P has not been certified.

You probably should try running newer mainline kernel builds to see if they work better, and do a rough bisect to see where it got fixed:

http://kernel.ubuntu.com/~kernel-ppa/mainline/

The amdgpu driver on 16.04 kernel is essentially backported from 4.5, so start with 4.7 and if it works, try 4.6 etc.

[Brian (cargohook)]

I have tried with several 4.6 kernels and the 4.7 kernel in 16.04. With and without the ppa:paulo-miguel-dias/mesa and ppa:oibaf/graphics-drivers. Nothing works.

[Timo Aaltonen (tjaalton)]

then it's an upstream bug which would be good to report to bugs.freedesktop.org (DRI; DRM/AMDgpu)

[jakedp (jakedp)]

I have some further information. Shutting off the driver power management with amdgpu.runpm=0 does not work. nomodset just puts my screen in a low resolution and cannot change resolutions. I' am using KDE Neon 5.7.3 as I do not like Unity but it is still stock Ubuntu 16.04 with the desktop switched out. So what I do now is have my BIOS sit there for 10 seconds before loading GRUB. When the Plymouth boot screen comes up I do a soft reboot after a second or two. I do this again. The third boot it seems the APU is warm enough and no random black screens.

[penalvch (penalvch)]

jakedp, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Daniel Quiñones (danielqp1)]

I try install with LiveUSB Ubuntu 16.10 Final Beta with Kernel 4.8 but i have the black screen

I have APU AMD A10-8700P with AMD R6 and dedicated AMD R7 360M

[penalvch (penalvch)]

Daniel Quiñones, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

As a back stop, use https://bugs.launchpad.net/ubuntu/+source/xorg/+filebug to file a manual report.

[Alex (palex)]

I have the same problem with the hp pavilion 15-ab103nl with the same APU amd a10 8700p. The system boot and then i have the black screen. The chat support has not be able to help me.

[pacblo64 (pacblo64)]

Me too, I have the same problem with laptop hp pavilion.
Processor: AMD A10-8700P Radeon R6, 10 Compute Cores 4C+6G × 4.
Graphics: Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)

The system boot and then i have the black screen. After second reboot, system seems work but in any unexpected moment, black screen appears.

[Tamás Tóth (tomjtoth)]

Same thing happens on Arch Linux, too, there's a dumb workaround: if you add modprobe.blacklist=amdgpu to the kernel line during boot, there won't be a problem with the faulty amdgpu driver :D

you can use the vesa driver without any HW acceleration (HTML5 vids seem to play okay-ish) but not even the lowest resolution of downloaded movies via VLC..

next step for me was to try out 14.04, yes it supports fglrx and yes you can install it with a click of a button, but still it's not Arch, so the next day I came home from work I managed to get it to work on Arch (first time in my life)

Home sweet home

Now I suffer from random ALT CTRL and SHIFT keystrokes ( I guess they would have appeared in Ubuntu also, since it's usually using an older kernel than Arch.

Anyways, I think I'll stick with the fglrx driver until I read some promising news on R6 Carrizo APU... xD

[victor gaspar (victor-gaspar)]

Same (or similar) issue here with Ubuntu 16.04.1 LTS on my laptop HP Pavilion with graphic card: Gallium 0.4 on AMD Carrizo (DRM 3.1.0, LLVM 3.8.0).

Already filled a report using ubuntu-bug. Bug #1642078.

[Patrick Laurin (plaurin)]

I'm installing fresh Ubuntu 16.04, I will be trying the latest kernel 4.9 rc-6 to see if this is fixed.

I have a AMD A10-8700P Radeon R6, 10 Compute Cores 4C+6G × 4.

I can see there are a whole lot of AMDGPU commits in upcoming linux-next. Maybe kernel 4.10 will finally solve this important issue.

I have to give thumb down on the Low 'Importance' of this bug. I do feel like complaining but understand that AMDGPU has really great performance for 2D acceleration and that's what I need. (catalyst has really poor 2D acceleration and makes my day to day work experience really laggy).

Can't wait for this to be fixed :-)

[Alberto Salvia Novella (es20490446e)]

@ Christopher M. Penalver (penalvch)

Notice that by changing priority to "low" you hid this critical bug for 4 months.

Setting status to "incomplete" would be enough for signalising this bug doesn't require further revision for the moment.

[Timo Aaltonen (tjaalton)]

just file a bug upstream and something will probably happen

[penalvch (penalvch)]

Alberto Salvia Novella, thanks for attending to this report. To advise, assigning an importance doesn't hide anything.

Also, this bug has no logs from the original reporter, so it's largely useless for developers to do anything with.

[Alberto Salvia Novella (es20490446e)]

@ Christopher M. Penalver

By setting bugs to low by procedure, there's no longer a way of telling how several their consequences are.

This is specially important, because searches by importance no longer distinguishes bugs by impact. So the original purpose of importances is broken.

If a developer doesn't want to deal with reports with incomplete information, they are better served by filtering incomplete bugs. But the fact that a report has an importance of low doesn't tell them very much about if to look at it or not, as importance only shows order.

Moreover by setting importance only based in impact, once the reported sets status back to "confirmed" after providing the required info, the importance is simply correct instantly without anyone having to modify it. Doing the opposite will lead to critical bugs set as low, and nobody realising it.

[James Funk (funkay)]

summary: - AMDGPU driver problems on "Carrizo" APU
+ [HP Pavilion 15] Intermittent black screens with Crimson 15.12 driver
tags: added: needs-apport-collect needs-debug-logs needs-full-computer-model

The above information is not correct, the bug is in AMDGPU, not the crimson driver.

The submitter writes "I updated to Kubuntu 16.04 (from Kubuntu 15.10 - that was using the Linux Crimson 15.12 driver) a couple days ago on my notebook (HP Pavilion, A10-8700P APU), and ever since I've been having random black screens."

He is saying he updated from 15.10 that was using the Crimson driver (which works and is the only available option for a working display at the moment), to 16.04, where the Crimson driver support was removed and AMDGPU is the only option. And that is when the black screens started happening for me also, and i had to downgrade to 15.10 and back to using the crimson driver.

My full computer model is: HP Pavilion 15-ab114no 15,6"

[penalvch (penalvch)]

James Funk, so your hardware may be tracked, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[James Funk (funkay)]

Done, please note that in the bug report i am using the crimson (fglrx) driver and kubuntu 15.10, because this is the only way that i can use my computer. If i try to upgrade to 16.04 and AMDGPU, my computer is unusable because of the bug. But maybe my hardware information helps.

[Patrick Laurin (plaurin)]

Great to see importance has moved to critical.
If only I was able to help.. I never debugged xorg before, never used xdiagnose for that matter.

[jakedp (jakedp)]

I solved the problem. I traded for an older i5 EliteBook.

On 12/29/2016 01:17 PM, Patrick Laurin wrote:
> Great to see importance has moved to critical.
> If only I was able to help.. I never debugged xorg before, never used xdiagnose for that matter.
>

[Timo Aaltonen (tjaalton)]

Lowering the priority does not "hide" anything, and bumping it doesn't help either.

This has not been filed upstream so there's nothing for me to do.

[penalvch (penalvch)]

nukedathlonman, could you please advise to the request of you in https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1577074/comments/10 ?

[Luciano Porta (lucianoporta97)]

Hello everyone,

I'm a noob on bug reporting, but I have an HP laptop with the exact problem described above and I would really like this problem solved. How can I help?

[Cristobal Ortiz Ortiz (prangfamily)]

Same problem to me here is my specs:

HP Laptop

AMD A10-87009 Radeon R6, 10 Compute COres 4c+6G x4
graphis: Gallium 0.4 on AMD Carrizo (DRM 3.9.0/4.10.9-041009-generic, llvm 3.8.0

OS: Ubuntu 16.04 LTS
OS Type: 64-bit

kernel: 4.10.9

this is my dmesg: https://pastebin.com/tjt54B9P

any other information required please feel free to contact me

already try the beta driver of amd did not help
microcode for amd processors did not helped
varios kernels versions also did not helped
so i am on on the open drivers no propietary drivers running now

[Cristobal Ortiz Ortiz (prangfamily)]

log: https://pastebin.com/sekckqCV

[Gianluca (aparesido)]

Hi penalvch,
I've just sent a bugreport following your instructions

Thanks

[Joshua (jreynaud1)]

Still not solved, huh? I've had this laptop for almost a year now, running the vesa driver on Gentoo. It's a shame, but I think I'll just have to get a new laptop as this problem has no hope of ever being solved in the foreseeable future.

[Luciano Porta (lucianoporta97)]

Consider yourself lucky, I cannot change my laptop so I'm stucked with this APU. Could we raise a Bountysource or something to attract some devs to this problem? I know I would donate to whoever fixes this bug. I just want to use Linux again, Windows is really getting on my nerves.

[Luciano Porta (lucianoporta97)]

People fighting the same fight:

https://bugs.freedesktop.org/show_bug.cgi?id=97055

https://bugs.freedesktop.org/show_bug.cgi?id=97605

https://bugs.freedesktop.org/show_bug.cgi?id=95306

[nukedathlonman (areginato)]

I was lucky and was able to pawn the computer off to another family member with Windows installed (and I got myself an i3 based Dell that works fine). That said, I had the computer back a month ago (to clean out the heat sink and remove a virus - natch) and looked into it with an external USB HDD. Nope, hasn't changed - BUT I tried a kernel with DAL (DC) enabled - worked fine with that kernel. So hopfully AMD gets there act together and make the needed changes to get it mainlined. Given that some Carrizo based systems work fine with out DC/DAL support, I'm betting it's a BIOS bug with the power settings of the GPU.

[nukedathlonman (areginato)]

Sorry, if you wish to try I breifly tested with this kernel: https://github.com/M-Bab/linux-kernel-amdgpu-binaries

[Luciano Porta (lucianoporta97)]

Wow! Thank you! Will try it tonight and tell you all.

By the way, my apologies for spamming a little bit out there. My mouse went nuts and I changed the Public information type a hella lots of times. Again, sorry.

[nukedathlonman (areginato)]

Well, I'm a bit sorry I only filed the bug and haven't done anything else except follow it (in hopes I'll be able to redo the system when Windows no longer cuts the mustard on it and it returns to my possession).

[Luciano Porta (lucianoporta97)]

Good news everyone!

I have been trying the kernel with amd-staging provided by nukedathlonman and it totally works! The system boots up to a completely functional environment at full-resolution. I've also tried Team Fortress 2 and Rocket League and it's pretty damn close to Windows performance, so you can pretty much ditch Windows away now if you want to. I'm so happy! I've been testing with Ubuntu GNOME 17.04 on a HP Pavilion 17-g133cl notebook. Hopefully, for Ubuntu 17.10 all fixes will be pushed to stable :) Yey!

[nukedathlonman (areginato)]

Whoa, hold up - it *may not* be. The kernel main line developers have rejected the code for various reasons. Untill it's acepted mainline, it's not a part of the kernel. Read the readme on the github site. AMD has to make changes to DC (formerly known as DAL) to be accepted. So anyone using the kernel I pointed out is just beta testers for the time being. Glad it does work for you.

[nukedathlonman (areginato)]

I just checked on Phoronix, AMD's DC stack has not been accepted for kernel 4.13 - so very unlikely to make it into Ubuntu 17.10. Maybe AMD steps on it they get it into kernel 4.14 at the earliest. The basic (overly simplistic) problem is how it's coded and would make it a total nightmare for the kernel dev's to maintain.

[nukedathlonman (areginato)]

Oh, BTW, to be ry clear - I didn't provide (or do) any work on this experimental (always consider it experimental) kernel - just the link to it. I only found it through a Phoronix article and used it to test. Thank M-bab for his hard work. :-)

[johnnynobody (engage1)]

I have the same problem with my brand new Pavilion 17 (product: HP Pavilion Notebook (N9E13UA#ABA)) with the AMD A10-8700P Radeon R6, 10 Compute Cores 4C+6G, and graphics VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo (rev c5). I tried the graphics PPA's but "no joy". Ubuntu 16.04.2 (64 bit), kernel 4.11.9-041109-generic. Seems to be a buggy driver since I can eventually get a desktop after multiple reboots but after 30+ minutes the screen goes dark and won't come back which, of course, means more reboots.

[Lee (lee48)]

I just tried to use the amdgpu-pro packages from AMD and that didn't fix my problem either. I tried ubuntu-17.04-desktop-amd64.iso and that didn't help. I tried various boot options and nearly all of them didn't help. The only boot option that works reliably is "nomodeset".

[nukedathlonman (areginato)]

I looked at the release notes and it appears amdgpu-pro only supports discrete/dedicated graphics. I don't see any APU GPU based core listed.

[Gustavo Jiménez Hidalgo (jimenezhidtavo)]

I have the same problem with my AMD-A10 8700P, someone has found some solution???????????

[johnnynobody (engage1)]

This fixed my problem: https://github.com/M-Bab/linux-kernel-amdgpu-binaries

[Edgar Mendoza (vesperdev)]

I have the same problem with laptop hp pavilion.
Processor: AMD A10-8700P Radeon R6, 10 Compute Cores 4C+6G × 4.
Graphics: Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)

The system boot and then i have the black screen. After second reboot, system seems work but in any unexpected moment, black screen appears.

[penalvch (penalvch)]

nukedathlonman, to advise, given there are no debugging logs provided, developers are unable to work on this issue. Hence, please answer all of the following questions:

1) Could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description, or the result of a terminal command)?

2) To see if this is already resolved in Ubuntu, could you please test for this via http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

3) If reproducible, could you please provide the missing information from https://help.ubuntu.com/community/DebuggingSystemCrash ?

[nukedathlonman (areginato)]

It was a Pavilion 15-ab188ca. And no I can't test, computer has been permanently retired (stripped down and parted out) when the battery charge circuit failed and could no longer properly detect a fully charged battery (don't want or need my mom using a fire hazard).

[penalvch (penalvch)]

nukedathlonman, thanks for the update. I'll close this given you don't have the hardware anymore.