VT3 is not visible in recovery mode |
||
Issue descriptionVT3 does not appear to be rendering when in recovery mode, historically this was used to be able to view the recovery process logs in real time, super useful if the logs fail to save to the USB drive for some reason (e.g. b/36189998). Some steps: 1. Start recovery on a system. 2. Switch to VT2, which says to go to VT3 to see more logs. 3. Press ctrl+alt+refresh(F3) and VT3 does not come up. This repros at a minimum on canary OS images (59) on SKL-Y systems. Dominik, does this fall under your jurisdiction with Frecon?
,
Mar 22 2017
Everything (except for stateful recovery) in recovery scripts seems to use dlog function which spits the same stuff to VT2 and VT3. So they look identical.
,
Mar 22 2017
And if I modify recovery like this:
~/chromiumos/src/platform/initramfs/recovery$ git diff
diff --git a/recovery/recovery_init.sh b/recovery/recovery_init.sh
index 021654c..9cc1a63 100644
--- a/recovery/recovery_init.sh
+++ b/recovery/recovery_init.sh
@@ -324,6 +324,7 @@ setup_install_mounts() {
mount -t tmpfs -o mode=0755 run "${USB_MNT}/run" || return 1
mkdir -p -m 0755 "${USB_MNT}/run/lock" || return 1
+ echo "This is VT3" > /run/frecon/vt2
dlog "Re-binding $BASE_MOUNTS for $NEWROOT_MNT"
for mnt in $BASE_MOUNTS; do
# $mnt is a full path (leading '/'), so no '/' joiner
I can see "This is VT3" message only on VT3 and VT2 and VT3 are not identical anymore.
So, VT3 works just fine.
,
Mar 22 2017
Ah thanks for digging into this, apologies this was a bit of a misroute, it seems we need a bug for someone involved with the recovery scripts. |
||
►
Sign in to add a comment |
||
Comment 1 by dbehr@chromium.org
, Mar 21 2017