Ok, I have another update.  I managed to get SSH setup and was able to
save some XOrg and dmesg logs.  However, I think this bug report can be
closed.  Why?  Because, I'm able to get full resolution video with the
4.4 kernel.   This is what I've found:  if I boot my Ubuntu 16.04.1
system normally, with "quiet splash" set in the GRUB default config file
(/etc/default/grub), I'll eventually get full resolution video on
terminal #7 *but* only after about 30 mins.

Here's the situation:

1)  I boot the system normally
2)  I get a black screen for 30 "wall clock" minutes
3)  After 30 mins, if I press Ctrl-Alt-F7, I get the Ubuntu login screen
4)  I login as normal and get the Unity desktop at full resolution

So, I'm not sure why it takes 30 minutes for things to work but this is
the case.  We don't reboot the system very often, so this might not be a
huge deal even though we will want to get this fixed, at some point.

So, from the perspective of this being a kernel bug, I'm not sure this
bug report is valid.   How do we proceed?

Thanks!

-- 
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/1598935

Title:
  Ubuntu 16.04 won't properly boot due to radeon module issue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I boot an Ubuntu 16.04 live DVD on a Gateway system with an AMD A6-5400K 
APU, with an integrated Radeon HD 7540D graphics adapter, I get a black screen 
with no video image. If I look at "dmesg" output, I see these messages:
  ubuntu@ubuntu:~$ dmesg | grep "UMS"
  [    4.827258] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!
  [   39.561534] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!
  [   76.905778] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!

  We currently run Ubuntu 14.04.2 on the system with no issue, including
  using the "radeon" video driver.

  WORKAROUND: Boot using kernel parameter:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC2:  ubuntu     2057 F.... pulseaudio
   /dev/snd/controlC0:  ubuntu     2057 F.... pulseaudio
   /dev/snd/controlC1:  ubuntu     2057 F.... pulseaudio
  CasperVersion: 1.376
  Date: Mon Jul  4 20:08:04 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: Gateway DX4380G
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash nomodeset ---
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware                            1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-A1
  dmi.board.name: DX4380G
  dmi.board.vendor: Gateway
  dmi.board.version: 1.02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-A1:bd09/04/2012:svnGateway:pnDX4380G:pvr:rvnGateway:rnDX4380G:rvr1.02:cvnGateway:ct3:cvr:
  dmi.product.name: DX4380G
  dmi.sys.vendor: Gateway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1598935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to