[HP Compaq nc6400] Blank screen on boot

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'

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...

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 ?

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.

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.

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.

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?

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?

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.