[HP Pavilion Notebook - 17-g164ng] black screen when booting

[FFab]

When booting the screen is black – backlight on – off - on.
When HDD is inactive
- keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or Strg + Alt + Del
- remote access e.g. using ssh is possible

Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

My notebook is a HP Pavilion 17-g164ng with an AMD A10-8780P APU and 2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

It seems very similar to that described in #1597079.

The bug report was generated from a remote PC. My HP notebook was started without any workaround parameters.
This apport doesn't display the second graphic subsystem Topaz R7 as an apport generated with nomodeset xforcevesa.

WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

WORKAROUND: When booting in UEFI mode, use kernel parameters:
nomodeset

or:
nomodeset xforcevesa

Resolution without xforcevesa: 800x600
Resolution with xforcevesa: 1600x900 – the optimal resolution

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Nov 5 23:40:19 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
InstallationDate: Installed on 2016-11-03 (2 days ago)
InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP HP Pavilion Notebook
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.41
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 80B6
dmi.board.vendor: HP
dmi.board.version: 81.32
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion Notebook
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Nov 5 23:32:11 2016
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.1
xserver.video_driver: amdgpu

[Launchpad Janitor (janitor)]

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

[Alberto Salvia Novella (es20490446e)]

Please, could you provide in (https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1597079) the information asked in (https://wiki.ubuntu.com/DebuggingKernelBoot)?

Thanks

[penalvch (penalvch)]

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

To clarify your Bug Description:

>"When booting the screen is black – backlight on – off - on."

 Are you noting that the laptop LCD backlight goes from 0% brightness to 100% automatically? If so, how often does it cycle between the two?

If so, as per your attachment https://launchpadlibrarian.net/292333261/CurrentDmesg.txt :
[ 0.576786] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness

[FFab (ffab)]

Christopher M. Penalver, re backlight cycle.

Booting, grub config: no workaround, "quiet splash", reboot - I note following cycle:

Grub menu - gray backlight (brightness same as grub menu background) - then a flash (white), not covering the whole screen - black( 0% brigthness, lasting 6 sec) - gray like before.

cold start:

grub-menu - gray - flash (white), not covering the whole screen -a cycle of 16 times: black and gray - the last gray

note:
runnig Ubuntu, brightness cannot be changed
running Windows10, no brightness problem.

[FFab (ffab)]

Alberto Salvia Novella, re from #1639517 to #1597079, DebuggingKernelBoot

Information has been added to #1597079

[penalvch (penalvch)]

FFab, 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 at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

[FFab (ffab)]

Upstream kernel test - kernel 4.11-rc1

Test-environment:
Ubuntu 16.04.2, kernel 4.8, installed on a separate partition.
Network: LAN
tests without workaround, no changes of installed grub configuration.

test 1:
installed kernel 4.8

results:
backlight change: similar to that reported on 2017-02-26.
dmesg: no BQC message
brigthness adjustment: (booting with workaround): not possible

(remote) login: n o t possible

test 2:
upstream kernel 4.11 rc1
results:
backlight change: similar to that reported on 2017-02-26.
dmesg: no BQC message
brigthness adjustment: not possible

boot time (remote login): > 3 minutes after entering grub-selection (kernel 4.4, ubuntu 16.04.1 about 2 minutes)

[FFab (ffab)]

Upstream kernel test - kernel 4.11-rc2

installation:
when installing, error message: header file not installed;
dpkg -i displays header file 4.11-rc2.

results:
backlight change similar that reported on 2017-02-26.
dmesg - 1 of the error messages:
      Direct firmware load for amdgpu/topaz_k_smc.bin failed with error -2

brightness adjustment: not possible

remote login: > 4 minutes after entering grub-selection (kernel 4.4, ubuntu 16.04.1 about 1 minute (not 2))
booting (workaround): <1 minute

[FFab (ffab)]

Upstream kernel test - kernel 4.11-rc3

Installation without errors.

booting (no workaround) > 3 min
no local login
remote login (ssh)

dmesg: some errors

backlight: as formerly described

[FFab (ffab)]

Upstream kernel test - kernel 4.11-rc5

boot-time >3 min.
no local login
only remote-login

brigthness adjustment: not possible
HDMI not usable (not new)

[FFab (ffab)]

Upstream kernel test - kernel 4.11-rc6

boot-time >3 min.
no local login
only remote-login

brigthness adjustment: not possible
HDMI not usable (not new)

40 error and fail lines - compared to 2017-04-04 (rc5) - minimal differences

[FFab (ffab)]

Upstream kernel test - kernel 4.11-rc7
compared to rc6 - no (minimal) differences

[FFab (ffab)]

Upstream kernel test - kernel 4.11
compared to rc7 - no (minimal) differences

[FFab (ffab)]

Upstream kernel test - kernel 4.12-rc1
Differences between 4.11 and 4.12-rc1:
boot time now 1 minute and - first time "boot finished" sound

[Timo Aaltonen (tjaalton)]

try booting the distro kernel with amd_iommu=off kernel parameter

[FFab (ffab)]

booting distro kernel 4.8.0-52 with kernel parameter amd_iommu=off:
boot time 1 minute and "boot finished" sound -
just like upstream kernel 4.12-rc1 without amd_iommu parameter.

[Timo Aaltonen (tjaalton)]

then file it upstream at bugs.freedesktop.org, product DRI, component DRM/AMDgpu

[FFab (ffab)]

Upstream kernel test - kernel 4.12-rc2 – rc5
Test results differ from rc1:
no "boot finished" sound, no remote login (ssh).
Reboot/shutdown by SysRQ keys after about 3 minutes possible.

Upstream kernels were installed on an updated Ubuntu installation.
For comparison I installed rc5 on an Ubuntu installation, which was updated 8 weeks ago (2017-04-17) .
The test result was just like that of rc1 ("boot finished" sound after 45 sec.).

[FFab (ffab)]

to comment #18
filed upstream

[FFab (ffab)]

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

[FFab (ffab)]

Upstream kernel test - kernel 4.12-rc6

1. Used installation basis for 4.12-rc6: ubuntu 16.04.2, kernel4.8.0-36, no updates

Result: "boot finished" sound after 50 sec.; ssh login possible

Booting a second time, using workaround parameters nomodeset xforcevesa:
some file system error message while booting . System finished booting.

2. Used installation basis for 4.12-rc6: ubuntu 16.04.2,, kernel 4.8.0-56, update today

no "boot finished" sound, no remote login (ssh).
Reboot/shutdown by SysRQ keys after about 3 minutes possible.

Booting a second time, using workaround parameters nomodeset xforcevesa:
error messages "containes file system with errors .." while booting . System finished booting.

[FFab (ffab)]

Upstream kernel test - kernel 4.12

Installation, on which upstream kernel was installed:

1. ubuntu 16.04.2,download installation, kernel4.8.0-36, no updates

booting without any workaround parameters:
boot-time 50sec (message sound),
black screen
remote-login (ssh) o.k.

2. ubuntu 16.04.2,updated on 2017-07-03, kernel4.8.0-58

booting without any workaround parameters:

hdd activity about 80 sec
black screen
no ssh connection possible

after reboot by SysRQ b

boot with parameters "nomodeset xforcevesa":

error messages

"... sdaX contains a file system with errors
check forced..."

than a lot of error messages - all containing
        " ... AE_AML_BUFFER_LIMIT"

booting not finished

[FFab (ffab)]

I suggest to change the importance of tis bug from "low" to "high"!

I bought this notebook in May 2016; installed was windows 10. I hardly use windows. Additionally, for "productivity" work, I installed 3x linux - at that time kubuntu and ubuntu 14.04 with amd driver fglrx.

I upgraded 1 installation to 16.04, because while working 14.04 often suddenly "died", i.e. no further keyboard or mouse input was possible; no reboot was possible, I had to shutdown by pressing the off-button for several-seconds.

16.04 does not support fglrx, it can only be started by using kernel parameter nomodeset.
Hoping this situation would change, I tested all new kernels and versions. One effect was,three times I had to set up the pc completely, also recovering win 10 - that lasted every time about one week:

E.g. installing 16.10 at a seperate partition and starting without any workaround parameters, the esp (efi system partition) was destroyed, I was not able to repair the installion.

Meanwhile, for productivity use, I have changed to a tower. The hp pavilion is only used for testing graphic driver support!

[FFab (ffab)]

Upstream kernel test - kernel 4.13-rc3

Installation, on which upstream kernel was installed:

ubuntu 16.04.2, kernel4.10.0-28, updated 2017-08-01

booting without any workaround parameters:
boot-time 45sec (message sound),
black screen
remote-login (ssh) o.k.

[FFab (ffab)]

Upstream kernel test - kernel 4.13-rc4

Installation updated 2017-08-07.
Results just like 4.13-rc3 test.

[Timo Aaltonen (tjaalton)]

you should add test results upstream, there's no-one here who can fix this I'm afraid

[Timo Aaltonen (tjaalton)]

You could test the amdgpu-pro dkms from amd.com with 4.4 or 4.8 kernel (doesn't work with anything newer). Install just the dkms, nothing else.

[FFab (ffab)]

Testing amdgpu-pro dkms from amd.com - results at https://bugs.freedesktop.org/show_bug.cgi?id=101483#c16 and (#c15)

[FFab (ffab)]

Upstream kernel test - kernel 4.15-rc3

Test results:
https://bugs.freedesktop.org/show_bug.cgi?id=101483#c32
Bug fixed in this upstream kernel!