[HP Compaq nc6400] Blank screen on boot

Bug #1743797 reported by Greta Regan on 2018-01-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Low
Unassigned

Bug Description

A few months after upgrading to Ubuntu 16.04, I got a black screen after booting.

WORKAROUND: Use kernel parameter:
radeon.modeset=0

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
.tmp.unity_support_test.1:

ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Jan 17 10:15:32 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV515/M52 [Mobility Radeon X1300] [1002:714a] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company RV515/M52 [Mobility Radeon X1300] [103c:30ac]
InstallationDate: Installed on 2014-04-10 (1378 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204)
MachineType: Hewlett-Packard HP Compaq nc6400 (RB523UA#ABA)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 ro radeon.modeset=0
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68YCD Ver. F.08
dmi.board.name: 30AC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 56.34
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68YCDVer.F.08:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnc6400(RB523UA#ABA):pvrF.08:rvnHewlett-Packard:rn30AC:rvrKBCVersion56.34:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq nc6400 (RB523UA#ABA)
dmi.product.version: F.08
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
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.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Jan 17 08:23:08 2018
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.18.4-0ubuntu0.7

Greta Regan (clacso) wrote :
Timo Aaltonen (tjaalton) wrote :

putting 'radeon.modeset=0' to kernel options is what disables all hw acceleration

if it doesn't boot properly without that, you need to test a newer kernel, so try installing 'linux-generic-hwe-16.04'

Changed in xorg (Ubuntu):
status: New → Incomplete
Greta Regan (clacso) wrote :
Download full text (3.5 KiB)

I installed 'linux-generic-hwe-16.04', as suggested, but there's no change. Perhaps because the radeon.modeset=0 is still in my system - but I can't find where. My boot sequence no longer shows radeon.modeset=0, but it came up when I ran dmesg | egrep | 'drm|radeon'. I've included both outputs below.

I checked all versions of the boot sequence, including the 4.4.0-104 versions, specified in the dmesg output. The recovery mode has 'nomodeset', but no radeon.modeset=0.  I included outputs of the 4.4.0-104 generic and recovery boot sequences below, in case they'd be of use.

Can you tell me how to get at the radeon.modeset=0 settings to remove them, or if you think that's not the problem, offer any other suggestions? My knowledge of Linux is miniscule.

Thanks.

My boot sequence:

recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  123f436f-0331-4097-8a8e-54cc927298c4
else
  search --no-floppy --fs-uuid --set=root 123f436f-0331-4097-8a8e-54cc927298c4
fi
        linux
/boot/vmlinuz-4.13.0-26-generic root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 ro  drm.debug=0xe plymouth:debug
initrd
/boot/initrd.img-4.13.0-26-generic

dmesg | egrep | 'drmradeon':

greta@NSH-HP-Compaq-nc6400-RB523UA-ABA:~$ dmesg | egrep 'drm|radeon'
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 ro radeon.modeset=0
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 ro radeon.modeset=0
[    2.935307] [drm] Initialized drm 1.1.0 20060810
[    3.022679] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
[   21.247887] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!

4.4.0-104 generic boot sequence:

recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  123f436f-0331-4097-8a8e-54cc927298c4
else
  search --no-floppy --fs-uuid --set=root 123f436f-0331-4097-8a8e-54cc927298c4
fi
echo
'Loading Linux 4.4.0-104-generic ...'
        linux
/boot/vmlinuz-4.4.0-104-generic root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 ro  drm.debug=0xe plymouth:debug
echo
'Loading initial ramdisk ...'
initrd
/boot/initrd.img-4.4.0-104-generic

4.4.0-104 generic (recovery mode) boot sequence:

Recovery mode
recordfail
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  123f436f-0331-4097-8a8e-54cc...

Read more...

description: updated
tags: added: bios-outdated-f.0b

Greta Regan, in order to obtain necessary debugging logs, could you please remove your WORKAROUND and capture the logs following https://wiki.ubuntu.com/DebuggingKernelBoot ?

Changed in xorg (Ubuntu):
importance: Undecided → Low
summary: - Xorg not recognizing AMD graphics card
+ [HP Compaq nc6400] Blank screen on boot
Greta Regan (clacso) wrote :

I've had trouble trying to capture a boot log with the settings requested in the last posting. Different things have happened on different attempts, including the boot stopping dead. I'll try for a couple of more days to see if I can get a complete log to post.

Greta Regan:

>"I've had trouble trying to capture a boot log with the settings requested in the last posting."

What are you using to capture the boot log? It shouldn't be too difficult to record a video of the screen with a cellphone or camera while it is booting up.

>"Different things have happened on different attempts, including the boot stopping dead. I'll try for a couple of more days to see if I can get a complete log to post."

Don't worry about the different variations of bad booting. If it doesn't boot properly in any way then post a video of the failed boot, screenshot of when the boot stopped dead, etc. Developers just need something to get a better sense of the issue.

tags: added: regression-update
Greta Regan (clacso) wrote :

I'm using a camera to record the video, that's not causing problems - aside from having to experiment a bit to get a clear shot of the log. The problems have been with the boots themselves. But, I'll do as you say. I'll try later today - when I can do without the laptop for awhile, as even after I reverse the changes to the grub it's taken some time to get it working properly (or at all) again.

Greta Regan, if reproducible in a live environment you could use instead http://cdimage.ubuntu.com/daily-live/current/ if this is more convenient, so you don't have to undo the WORKAROUND on your install.

Greta Regan (clacso) wrote :

I've attached a boot recording - all went smoothly this time. I trimmed it down to just the boot log itself. It may look like I cut off the start of the log, but I didn't. I have the complete file, though, if needed, including what happens after the boot (not much visibly). If it's not clear enough or you think I've missed something you need at the top or bottom of the screen, I can have another go.

Greta Regan (clacso) wrote :

I've attached the complete file of the boot recording.

Great Regan:

The last couple lines from the video until blank screen:
[OK] Started Light Display Manager.
     Starting WPA Supplicant...

taking this along with the boot up history didn't confirm the root cause for me.

Despite this, as per your Bug Description, you noted this problem started happening after an update. Could you please advise to which one specifically?

Greta Regan (clacso) wrote :

It happened after upgrading from 14.04 to 16.04. I did this when prompted by Software Updater, so presumably it was the first version of 16.04 released through Updater. It didn't happen right after, or soon after, that upgrade, and I don't think there were any updates to 16.04 in the days immediately before the problem started. - I can't swear to that, as, naturally, I wasn't paying that much attention to all the little updates one gets almost every day.

If there's a way to check my update history, you'll have to tell me how. I do remember when the problem hit, as it was Christmas day, so I have a definite date to search back from.

From what I was able to find online, I gather that ultimately the problem originates with 16.04 no longer using fglrx, although my video card is still supposed to be supported in 16.04 - and for awhile, it was.

Greta Regan:

1) The package update history would be in the /var/log/apt folder.

2) Regarding 14.04, were you using fglrx in it or the open source driver?

Greta Regan (clacso) wrote :

Sorry, can you be a bit more specific on how to get the update history? I tried a couple of commands but neither got me the package update history. Really, I know almost nothing about getting around Ubuntu.

On your second question, I can only say that I did a normal install of 14.04, and everything worked, so I had no occasion look at how it worked. - But, if I would've had to install the open source driver separately, I never did that.

Changed in xorg (Ubuntu):
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers