plymouth causes a hard reset of the nexus
Bug #1065644 reported by
Bryce Harrington
This bug report is a duplicate of:
Bug #1084063: plymouth in raring causes system hardlock if console_setup is not run in the initramfs on nexus7 prior to starting plymouthd.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Plymouth |
New
|
Undecided
|
Unassigned | ||
ubuntu-nexus7 |
Confirmed
|
Critical
|
Oliver Grawert |
Bug Description
Plymouth on the Nexus7 (tegra3) seems to kill the kernel. On the AC100 (tegra2) is just caused a black screen. We disabled plymouth in our image, but would like a better fix.
Changed in newark: | |
assignee: | nobody → Alex Chiang (achiang) |
status: | New → In Progress |
importance: | Undecided → Critical |
tags: | added: mobile nexus7 tegra3 |
description: | updated |
Changed in ubuntu-nexus7: | |
assignee: | nobody → Oliver Grawert (ogra) |
To post a comment you must log in.
ubuntu- defaults- nexus7 (0.2) quantal; urgency=low
* rootfs/ etc/init/ plymouth* .override
- do not run any plymouth jobs since they kill the kernel (LP: #1065644)
-- Alex Chiang <email address hidden> Thu, 11 Oct 2012 21:18:39 -0700