My chromium os can not go to CTRl+ALT+F2 or shell mode.

[t***@public.gmane.org]

CTRl+ALT+F2 and shell works when I boot from USB, but after I
install to disk, on log page CTRl+ALT+F2 don't work,and after login,shell

[Richard Barnette]

(again, from the right address)

CTRl+ALT+F2 and shell works when I boot from USB, but after I install to disk, on log page CTRl+ALT+F2 don't work,and after login,shell command not found in crosh. Can any one give some advices?

VT2 is enabled conditionally with a run time check. One of the checks
is that 'chronos' has a password; you can set that at build time:
http://www.chromium.org/chromium-os/developer-guide#TOC-Set-the-chronos-user-password

If you built the image yourself, that shouldn't be necessary to enable
VT2, but if there's a bug, "shouldn't be" may not apply.

Is your hardware a Chromebook or just a stock system? I think this
is an area where the code would distinguish a system with Chrome OS
firmware from standard BIOS.

The code that actually enables VT2 is here:
src/platform/init/hotkey-access.conf

The code with the logic for "should we enable VT2" is this
script:
src/third_party/chromiumos-overlay/chromeos-base/chromeos-auth-config/files/is_developer_end_user

--
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

-- jrb

[Richard Barnette]

Post by Richard Barnette
(again, from the right address)

CTRl+ALT+F2 and shell works when I boot from USB, but after I install to disk, on log page CTRl+ALT+F2 don't work,and after login,shell command not found in crosh. Can any one give some advices?

VT2 is enabled conditionally with a run time check. One of the checks
http://www.chromium.org/chromium-os/developer-guide#TOC-Set-the-chronos-user-password
If you built the image yourself, that shouldn't be necessary to enable
VT2, but if there's a bug, "shouldn't be" may not apply.
Is your hardware a Chromebook or just a stock system? I think this
is an area where the code would distinguish a system with Chrome OS
firmware from standard BIOS.
src/platform/init/hotkey-access.conf
The code with the logic for "should we enable VT2" is this
src/third_party/chromiumos-overlay/chromeos-base/chromeos-auth-config/files/is_developer_end_user

... and the code for enabling the 'shell' command in crosh is here:
src/platform/crosh/crosh
Look for the code that includes the "crosh-dev" file.

A common theme in all of these failures is that the 'crossystem'
command would have to return that your system isn't a debug
system. That shouldn't happen for a properly built developer
image. How did you build your image?

Post by Richard Barnette

--
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

-- jrb
--
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

-- jrb

[Richard Barnette]

Forwarding this response to the alias, so anyone who's been following the thread
can benefit from what's been learned.

thank you,Richard, I install on HP compaq nc4400 notebook, today I build OS according to developer guide,set a password,this time Ctrl+Alt+F2 worked when boot from disk

Post by Richard Barnette
(again, from the right address)

CTRl+ALT+F2 and shell works when I boot from USB, but after I install to disk, on log page CTRl+ALT+F2 don't work,and after login,shell command not found in crosh. Can any one give some advices?

VT2 is enabled conditionally with a run time check. One of the checks
http://www.chromium.org/chromium-os/developer-guide#TOC-Set-the-chronos-user-password
If you built the image yourself, that shouldn't be necessary to enable
VT2, but if there's a bug, "shouldn't be" may not apply.
Is your hardware a Chromebook or just a stock system? I think this
is an area where the code would distinguish a system with Chrome OS
firmware from standard BIOS.
src/platform/init/hotkey-access.conf
The code with the logic for "should we enable VT2" is this
src/third_party/chromiumos-overlay/chromeos-base/chromeos-auth-config/files/is_developer_end_user

src/platform/crosh/crosh
Look for the code that includes the "crosh-dev" file.
A common theme in all of these failures is that the 'crossystem'
command would have to return that your system isn't a debug
system. That shouldn't happen for a properly built developer
image. How did you build your image?

Post by Richard Barnette

--
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

-- jrb
--
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

-- jrb

-- jrb

[Richard Barnette]

Forwarding to the alias, so that everyone can benefit from the advice.

i have this problem too, in chromium os branch 26, following the instructions of quick start guide on a ubuntu precise.
The usb boot, but i don't have the text mode, in ctrl alt f2 or ctrl alt T + shell, and can't install.
I think that is because i build non a dev mode image.

There are various questions below for the OP about his system
and how he built; you'll need to provide the answers to those questions
as they apply to you.

Also, have you made sure that the chronos account has a
password?

Post by Richard Barnette
(again, from the right address)

CTRl+ALT+F2 and shell works when I boot from USB, but after I install to disk, on log page CTRl+ALT+F2 don't work,and after login,shell command not found in crosh. Can any one give some advices?

VT2 is enabled conditionally with a run time check. One of the checks
http://www.chromium.org/chromium-os/developer-guide#TOC-Set-the-chronos-user-password
If you built the image yourself, that shouldn't be necessary to enable
VT2, but if there's a bug, "shouldn't be" may not apply.
Is your hardware a Chromebook or just a stock system? I think this
is an area where the code would distinguish a system with Chrome OS
firmware from standard BIOS.
src/platform/init/hotkey-access.conf
The code with the logic for "should we enable VT2" is this
src/third_party/chromiumos-overlay/chromeos-base/chromeos-auth-config/files/is_developer_end_user

src/platform/crosh/crosh
Look for the code that includes the "crosh-dev" file.
A common theme in all of these failures is that the 'crossystem'
command would have to return that your system isn't a debug
system. That shouldn't happen for a properly built developer
image. How did you build your image?

Post by Richard Barnette

--
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

-- jrb
--
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

-- jrb
--
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

-- jrb