Bug 85522

Summary: Failure initializing radeon (as /dev/card1) renderer: unexpectedly disconnected from boot status daemon
Product: plymouth Reporter: Dariusz Gadomski <dariusz.gadomski>
Component: generalAssignee: Ray Strode [halfline] <rstrode>
Status: RESOLVED MOVED QA Contact:
Severity: major    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: Log from a failed run.

Description Dariusz Gadomski 2014-10-27 16:30:08 UTC 
Created attachment 108522 [details]
Log from a failed run.

In a setup as follows:

1. Ubuntu 14.04 booting from a live CD with updated plymouth (0.9.0 from https://launchpad.net/~xnox/+archive/ubuntu/backports)
2. Hardware is an iMac 12,1 with an integrated intel (/dev/card0) and a discrete radeon (/dev/card1). The display is connected to the radeon and a prompt for an disk encryption password is needed.

Expected results:
A password prompt should be displayed on each display (including the main display connected to the radeon).

Actual result:
On the only display connected to radeon right after leaving GRUB all what may be seen is:
error: unexpectedly disconnected from boot status daemon
/dev/loop0: UUID="<the device UUID>" TYPE="crypto_LUKS"

According to the plymouth changelog it should have been fixed by https://bugs.freedesktop.org/show_bug.cgi?id=25943 (http://cgit.freedesktop.org/plymouth/commit/?id=e982dc255c0f471e67eb7bd0858c170d103d39ce)
but according to the plymouth debug log (attached) radeon fails to open.
Comment 1 GitLab Migration User 2018-08-07 09:28:25 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/plymouth/plymouth/issues/56.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.