QQ RC boots to purple screen on Acer Aspire 5253
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Regression - QQ amd64 was booting O.K.
Acer Aspire 5253 1366x768 wide screen notebook
Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310]
RC boots to solid purple screen. Some hard drive accesses when trying everything possible on the keyboard.
Cannot get command line or anything.
Holding down Ctrl-Alt-Del for some time it does reboot
Advanced options gives a crazy jumpy jerky 1024x768 offset screen extremely slow and unusable.
WORKAROUND:
"splash" removed from "linux" line boots as expected.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-
ProcVersionSign
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
Date: Thu Oct 18 20:18:36 2012
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121014)
MachineType: Acer Aspire 5253
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.95
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/06/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.05
dmi.board.name: Aspire 5253
dmi.board.vendor: Acer
dmi.board.version: V1.05
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: Aspire 5253
dmi.product.
dmi.sys.vendor: Acer
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
jerrylamos, thank you for reporting this and helping make Ubuntu better. Could you please provide the information following https:/ /wiki.ubuntu. com/DebuggingKe rnelBoot ?
As well, could you please test the latest upstream kernel available following https:/ /wiki.ubuntu. com/KernelMainl ineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag: testing
needs-upstream-
This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text: testing
needs-upstream-
If this bug is fixed in the mainline kernel, please add the following tags: fixed-upstream fixed-upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested.
If the mainline kernel does not fix this bug, please add the following tags: bug-exists- upstream bug-exists- upstream- VERSION- NUMBER
kernel-
kernel-
If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: unable- to-test- upstream unable- to-test- upstream- VERSION- NUMBER
kernel-
kernel-
Please let us know your results. Thank you for your understanding.