Crosh

[Alessandro Marani]

Hi guys,

I don't know why if I open with Ctrl+Alt+T the crosh and then write shell,the system told me unknown command: 'shell' .

I've installed Chromium OS on my ssd while on the USB crosh works fine.

Which is the differences?

I'm doing something wrong?

Ale

[Steve Pirk]

I do not know how this works on Chromium OS, but on a retail Chromebook, you have to flip a physical hardware switch.

When you say you installed Chromium OS on your SSD, did you build your own image, or get one from a 3rd party?

Now that I think about it, I do not know how you enable dev mode on your own Chromium builds. I assume it would be there by default.

-- steve

--
Chromium OS discuss mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

[Richard Barnette]

I think I understand what you're saying, but I'm not sure. Could
you please confirm that this is what happened:
1. You built your own Chromium OS image, and booted it from a USB stick.
2. When booted from USB, the 'crosh' command allows you to use the 'shell'
command.
3. You install your Chromium OS image onto the system's internal SSD,
using "chromeos-install".
4. After booting your image from SSD, the 'shell' command no longer works.

I've taken a look at the 'crosh' command sources, and I don't think it can
do that, but I haven't actually tested to prove it. If it does happen, it's a
bug.

> Ale
>
>
> --
> Chromium OS discuss mailing list: chromium-...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

-- jrb

[Alessandro Marani]

Hi,

you fully understand what I mean.

I hope to help me.

Thank you for your support.

Alessandro

[Richard Barnette]

On Feb 7, 2013, at 10:12 AM, Alessandro Marani <aless....@gmail.com> wrote:

> Hi,
> you fully understand what I mean.
> I hope to help me.
> Thank you for your support.
>

What hardware did you see this problem on?

> --

[Alessandro Marani]

On a Lenovo Thinkpad X230i

Alessandro

[Richard Barnette]

On Feb 7, 2013, at 12:12 PM, Alessandro Marani <aless....@gmail.com> wrote:

> On a Lenovo Thinkpad X230i
>

OK. A quick test to rule in/out obvious problems:
1. Switch to VT2 with ctrl+alt+F2
2. Log in at the terminal
3. Run this command:
crossystem 'cros_debug?1' ; echo $?
4. Report back what happened

This is supposed to print a 0 on the output.

[Alessandro Marani]

1 on the output.

Alessandro

[Richard Barnette]

On Feb 7, 2013, at 1:12 PM, Alessandro Marani <aless....@gmail.com> wrote:

> 1 on the output.
>
OK. The crosh script would only enable the 'shell' command if that command
had printed 0. So, we know why 'shell' doesn't work, but that doesn't really
explain much...

Can you run this command from the VT2 shell prompt:
tr ' ' '\n' </proc/cmdline | grep cros_debug

That should print 'cros_debug'. If it doesn't then there's something wrong
with the way your image got built.

[John Mongillo]

This happened to me too.

@Alessandro: Did you install the 64-bit version of Chromium or the 32-bit version? I have an AMD X3 laptop that I installed Chromium on. When I install the 64-bit version crosh did exactly what it did to you. I went back and re-compiled Chromium this time as 32-bit. After installing the 32-bit version crosh worked fine even after the install. You should try installing the 32-bit version of Chromium and see if you get the same results. If nothing else it can help narrow down where the bug is. Perhaps it is something that only affect 64-bit systems.

[Alessandro Marani]

Hi,

I've installed the Arnold build Cx86OS-20130206030101.img.7z from http://chromium.arnoldthebat.co.uk/

Alessandro

[Richard Barnette]

On Feb 8, 2013, at 12:14 AM, John Mongillo <5n4...@gmail.com> wrote:

> This happened to me too.
>
> @Alessandro: Did you install the 64-bit version of Chromium or the 32-bit version? I have an AMD X3 laptop that I installed Chromium on. When I install the 64-bit version crosh did exactly what it did to you. I went back and re-compiled Chromium this time as 32-bit. After installing the 32-bit version crosh worked fine even after the install. You should try installing the 32-bit version of Chromium and see if you get the same results. If nothing else it can help narrow down where the bug is. Perhaps it is something that only affect 64-bit systems.
>

The problem isn't 64- vs. 32-bit per se. The symptoms seem to suggest
a problem in the way the image was built. The build system distinguishes
the two different cases, which makes it possible to have a bug that affects
one but not the other.

You can confirm whether the problem is with the build by using the
command I mentioned earlier:

tr ' ' '\n' </proc/cmdline | grep cros_debug

If that doesn't print "cros_debug", there's a problem with the build.

> On Thursday, February 7, 2013 12:10:33 AM UTC-8, Alessandro Marani wrote:
> Hi guys,
> I don't know why if I open with Ctrl+Alt+T the crosh and then write shell,the system told me unknown command: 'shell' .
> I've installed Chromium OS on my ssd while on the USB crosh works fine.
> Which is the differences?
> I'm doing something wrong?
>
> Ale
>
>

[Alessandro Marani]

Hi,

this is the output:

tr:missing operand after ' \\n'

two strings must be given when translating

Alessandro

[Richard Barnette]

On Feb 10, 2013, at 1:55 PM, Alessandro Marani <aless....@gmail.com> wrote:

> Hi,
> this is the output:
>
> tr:missing operand after ' \\n'
> two strings must be given when translating
>

This means there was a typo in the command line.

Here's a simpler command to try:
grep cros_debug /proc/cmdline

That will either print a long line of mostly nonsense, or it
will print nothing. If it prints nothing, there's a problem with

[Alessandro Marani]

Hi,

it print nothing.

Alessandro

[Alessandro Marani]

I use the Tony Ditchfield build from http://arnoldthebat.co.uk/wordpress/chromium-os/

Alessandro

[Richard Barnette]

On Feb 11, 2013, at 12:57 PM, Alessandro Marani <aless....@gmail.com> wrote:

> I use the Tony Ditchfield build from http://arnoldthebat.co.uk/wordpress/chromium-os/
>

Right. Something in the way that image was built causes the problem. That's
not necessarily wrong; for example production Chrome OS images are built this
way. To get a fix, you'll need to build your own image, or else talk to the image
provider about the problem.

[Alessandro Marani]

Hi,

in the meantime I tried to install the build of Hexxeh but even with this, the crosh does not work.

I suppose that the problem is not due to the build at this point.

Is something wrong on my laptop hardware?

I don't know why the crosh works fine on usb but doesn't work properly on my ssd.

Alessandro

[Richard Barnette]

On Feb 12, 2013, at 1:27 AM, Alessandro Marani <aless....@gmail.com> wrote:

> Hi,

> in the meantime I tried to install the build of Hexxeh but even with this, the crosh does not work.
> I suppose that the problem is not due to the build at this point.
> Is something wrong on my laptop hardware?
> I don't know why the crosh works fine on usb but doesn't work properly on my ssd.
>

The problem isn't with the hardware; it's definitely software.
Here's the short summary of what's happening:
* The 'crosh' script uses a command called 'crossystem' to
ask whether to allow the use of debug features.
* The 'crossystem' command will allow the use of debug
features in one of two cases: 1) The kernel command line
includes the argument "cros_debug", or 2) the hardware
is Chrome OS hardware, and the developer switch is on.

The tests you reported earlier indicate that 'cros_debug' isn't
on the kernel command line, so the first condition fails. You're
not using Chrome OS hardware, so the second condition for
'crossystem' will fail, too.

I can't explain why you don't have the problem when booting
from USB. I do know that the boot procedure that constructs
the kernel command line for non-Chrome OS hardware is
different from Chrome OS hardware, so apparently there's a
bug in that flow. If you want a fix, your best bet is to talk with
whoever supplied you with the image.

[Don Garrett]

I wonder if a bug related this this flag in the kernel command line crept in recently.

+taysom

Don

[Paul Taysom]

My changes shouldn't have touched this part of the linux command line. I only changed the dm="..." part of the the command line.

[Richard Barnette]

+wfrichar

On Feb 13, 2013, at 9:05 AM, Paul Taysom <tay...@google.com> wrote:

> My changes shouldn't have touched this part of the linux command line. I only changed the dm="..." part of the the command line.
>

I just went and perused the build script sources. It seems
like for non-Chrome hardware, the kernel command line gets
set up by bootstrap configuration files that are created by
build_library/create_legacy_bootloader_templates.sh.
Nowhere in that file does it mention cros_debug; I suspect
that means it won't be there.

That said, I still don't see any reason why the command line
would wind up different between boot from a removable USB
stick and boot from internal storage...

I'm largely out of my depth here; hopefully, someone who
understands the Chromium OS syslinux magic can weigh in.

-- jrb

[Maarten]

Hi,

I just installed Chromium OS to my hard disk and I can confirm this bug. When I boot from USB, I can get to the shell in crosh, but the 'shell' command is unknown after I installed and ran Chromium OS from my hard drive. Weird stuff...

Op woensdag 13 februari 2013 19:01:08 UTC+1 schreef Richard Barnette het volgende:

[Hung-Te Lin]

This issue will be fixed once https://gerrit.chromium.org/gerrit/#/c/46117/ is merged.

Hung-Te

[Alessandro Marani]

Hi,

confirm that with the latest tonyd build the crosh works fine.

I'm really enjoy.

Alessandro

[nicholas holt]

hey guys crosh is the best

[Keith I Myers]

The "shell" command will only work when a Chrome device is set to developer mode. 

--
--
Chromium OS discuss mailing list: chromium-os-discuss@chromium.org

View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Chromium OS discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-discuss+unsub...@chromium.org.

--

Keith I Myers http://KMyers.me https://Kiddie.Networks - Cheap Web Hosting Services ran by kids Mobile : (305)-929-3475