Ubuntu 16.04 LiveCD does not boot on AMD A10 chip
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD A10-5800K AGP, Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try to boot I get an error message, "ERROR: no UMS support in radeon module." When I edit the boot command line to add the parameter 'nomodeset' I first get an error message, "No UMS support on radeon module," then the familiar aubergine background with the ubuntu logo and the five dots below it changing from white to red and back again. After twenty or thirty seconds the background goes to black, I get the error message "No UMS support in radeon module," and the ubuntu logo disappears but the five dots continue. After another twenty or thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or less the screen goes black and I can't do anything except reboot. I've tried old Live CDs, from 10.10 to 15.10, and they all boot fine.
---
.tmp.unity.
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
CompositorUnred
CompositorUnred
DistUpgraded: Fresh install
DistroCodename: wily
DistroRelease: Ubuntu 15.10
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
ExtraDebuggingI
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901]
InstallationDate: Installed on 2016-06-07 (27 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
Package: xorg 1:7.7+7ubuntu4
PackageArchitec
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
Tags: wily ubuntu compiz-0.9
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.2.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 03/18/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.
dmi.board.name: F2A75M-HD2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To be filled by O.E.M.
dmi.product.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Tue Jul 5 00:55:16 2016
xserver.configfile: default
xserver.devices:
input Power Button KEYBOARD, id 6
input Power Button KEYBOARD, id 7
input USB Optical Wheel Mouse MOUSE, id 8
input Logitech USB Keyboard KEYBOARD, id 9
input Logitech USB Keyboard KEYBOARD, id 10
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9.1
xserver.
tags: | added: xenial |
tags: | added: yakkety |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
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/ FindRightPackag e. 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/1584284/ +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.]