Ctrl+U does nothing under newest dev-version on ARM chromebook.

[Mats Christensen]

Pressing ctrl+u during the os verification screen does not seem do to anything at all under dev-version 3196.3.0.

Ctrl+d and ctrl+i works fine.

dev_boot_usb is set to 1.

This worked just fine a couple of days ago.

Has anyone else encountered this or am I just screwing up somehow?

Thanks!

[Ottavio Caruso]

On 25 November 2012 15:18, Ottavio Caruso
<ottavio2006...@yahoo.com> wrote:
.
>> I have experienced this problem, filed a bug report and I found a workaround:
> http://code.google.com/p/chromium-os/issues/detail?id=36609

I forgot, please add your comment to the bug report.

--
Ottavio

[Ottavio Caruso]

As usual my original post didn't get to the group. I repeat the workaround:

I had to re-configure the kernel with the 'rw' flag enabled:

echo "console=tty1 debug verbose \
root=/dev/sda2 rootwait rw" > /tmp/config.rw

vbutil_kernel --pack /home/chronos/user/Downloads/newkern.rw \
--keyblock /usr/share/vboot/devkeys/kernel.keyblock \
--version 1 \
--signprivate /usr/share/vboot/devkeys/kernel_data_key.vbprivk \
--config=/tmp/config.rw \
--vmlinuz /boot/vmlinuz-3.4.0 --arch arm

dd if=/home/chronos/user/Downloads/newkern.rw of=/dev/sda1

This way I was able to boot from usb successfully. Then i have
rebooted the Chromebook into Chrome OS and rewrote out the kernel with
the ‘ro’ flag to the first partition and rebooted again:

echo "console=tty1 debug verbose \
root=/dev/sda2 rootwait ro" > /tmp/config.ro

vbutil_kernel --pack /home/chronos/user/Downloads/newkern \
--keyblock /usr/share/vboot/devkeys/kernel.keyblock \
--version 1 \
--signprivate /usr/share/vboot/devkeys/kernel_data_key.vbprivk \
--config=/tmp/config.rw \
--vmlinuz /boot/vmlinuz-3.4.0 --arch arm

dd if=/home/chronos/user/Downloads/newkern of=/dev/sda1

[Mats Christensen]

Thanks, but that is not the issue I'm having.
In your case there is just a problem with the loader.

When I press ctrl+u nothing happens at all. Usually the screen would go black and boot something, or just go bland and then back to the dev-screen.
Installing an older recovery-image of chromeos fixed the issue, but updating to newest dev-channel image "disables" ctrl+u again.

[Jonathan Kliegman]

On Sun, Nov 25, 2012 at 10:33 AM, Mats Christensen <matschr...@gmail.com> wrote:

Thanks, but that is not the issue I'm having.
In your case there is just a problem with the loader.

When I press ctrl+u nothing happens at all. Usually the screen would go black and boot something, or just go bland and then back to the dev-screen.
Installing an older recovery-image of chromeos fixed the issue, but updating to newest dev-channel image "disables" ctrl+u again.

I believe the blue USB port (USB 3.0) doesn't work for recovery images or USB booting.  Are you seeing this with the black port?

I haven't seen this issue myself (where there would be no messages at all).   It seems odd that the version installed on the device would impact USB booting - is the bios version changing at all when you roll forward and back? 

On Sunday, November 25, 2012 4:30:09 PM UTC+1, Ottavio Caruso wrote:

As usual my original post didn't get to the group. I repeat the workaround:

I had to re-configure the kernel with the 'rw' flag enabled:

echo "console=tty1 debug verbose \
root=/dev/sda2 rootwait rw" > /tmp/config.rw

vbutil_kernel --pack /home/chronos/user/Downloads/newkern.rw \
--keyblock /usr/share/vboot/devkeys/kernel.keyblock \
--version 1 \
--signprivate /usr/share/vboot/devkeys/kernel_data_key.vbprivk \
--config=/tmp/config.rw \
--vmlinuz /boot/vmlinuz-3.4.0 --arch arm

dd if=/home/chronos/user/Downloads/newkern.rw of=/dev/sda1

This way I was able to boot from usb successfully. Then i have
rebooted the Chromebook into Chrome OS and rewrote out the kernel with
the ‘ro’ flag to the first partition and rebooted again:

echo "console=tty1 debug verbose \
root=/dev/sda2 rootwait ro" > /tmp/config.ro

vbutil_kernel --pack /home/chronos/user/Downloads/newkern \
--keyblock /usr/share/vboot/devkeys/kernel.keyblock \
--version 1 \
--signprivate /usr/share/vboot/devkeys/kernel_data_key.vbprivk \
--config=/tmp/config.rw \
--vmlinuz /boot/vmlinuz-3.4.0 --arch arm

dd if=/home/chronos/user/Downloads/newkern of=/dev/sda1

--
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

[Ottavio Caruso]

On 25 November 2012 15:33, Mats Christensen <matschr...@gmail.com> wrote:
> Thanks, but that is not the issue I'm having.
> In your case there is just a problem with the loader.
>
> When I press ctrl+u nothing happens at all. Usually the screen would go
> black and boot something, or just go bland and then back to the dev-screen.
> Installing an older recovery-image of chromeos fixed the issue, but updating
> to newest dev-channel image "disables" ctrl+u again.

Well, whatever it is, it must have been introduced by the latest
update, although to be honest I have found nothing new in the
timestamps.


--
Ottavio

[Mats Christensen]

I'm using SD-cards, so the ports should not be an issue.

Does CrOS call uboot 'firmware' and has versioning for it?

It's pretty common to bundle newer/different uboot-versions with OS-updated nowadays.

I can't check for version differences right now since it says I'm up to date on the dev channel while I'm only running beta (dev-server down?).

[Sonny Rao]

Mats, can you navigate to chrome:system and look at the output for
"crossystem" or run that command in the shell to see what firmware
you're using?

Simon, I know there was a different issue with being stuck in dev-mode
on the dev-channel version of the RW firmware, but is there also an
issue with booting from USB?

On Sun, Nov 25, 2012 at 10:09 AM, Mats Christensen

<matschr...@gmail.com> wrote:
> I'm using SD-cards, so the ports should not be an issue.
>
> Does CrOS call uboot 'firmware' and has versioning for it?
> It's pretty common to bundle newer/different uboot-versions with OS-updated
> nowadays.
>
> I can't check for version differences right now since it says I'm up to date
> on the dev channel while I'm only running beta (dev-server down?).
>
> On Sunday, November 25, 2012 5:57:09 PM UTC+1, Jonathan Kliegman wrote:
>>
>>
>>
>>
>> On Sun, Nov 25, 2012 at 10:33 AM, Mats Christensen <matschr...@gmail.com>
>> wrote:
>>>
>>> Thanks, but that is not the issue I'm having.
>>> In your case there is just a problem with the loader.
>>>
>>> When I press ctrl+u nothing happens at all. Usually the screen would go
>>> black and boot something, or just go bland and then back to the dev-screen.
>>> Installing an older recovery-image of chromeos fixed the issue, but
>>> updating to newest dev-channel image "disables" ctrl+u again.
>>>
>> I believe the blue USB port (USB 3.0) doesn't work for recovery images or
>> USB booting. Are you seeing this with the black port?
>>
>> I haven't seen this issue myself (where there would be no messages at
>> all). It seems odd that the version installed on the device would impact
>> USB booting - is the bios version changing at all when you roll forward and
>> back?
>

[Olof Johansson]

Another thing to try is to hit <tab> at the "dev mode" screen and make sure it reports that USB booting is set to 1.

-Olof

2012/11/25 Sonny Rao <sonn...@chromium.org>

[Ottavio Caruso]

On 26 November 2012 06:25, Olof Johansson <ol...@chromium.org> wrote:
> Another thing to try is to hit <tab> at the "dev mode" screen and make sure
> it reports that USB booting is set to 1.
>

It _did_ report crossystem dev_boot_usb=1 when I couldn't boot from
USB and CTRL_U did nothing either, same as with Mats. Out of
desperation I tried all methods until I came out with repackaging the
kernel with the 'rw' flag in the config file and -bang- it worked.

Mats, what image are you booting and can you try this hack?

[Ottavio Caruso]

Yeeeesssss, at least I'm not the only one! I was going mad.

I have experienced this problem, filed a bug report and I found a workaround:
http://code.google.com/p/chromium-os/issues/detail?id=36609

I repeat the steps: I had to re-configure the kernel with the 'rw' flag enabled:

echo "console=tty1 debug verbose \
root=/dev/sda2 rootwait rw" > /tmp/config.rw

vbutil_kernel --pack /home/chronos/user/Downloads/newkern.rw \
--keyblock /usr/share/vboot/devkeys/kernel.keyblock \
--version 1 \
--signprivate /usr/share/vboot/devkeys/kernel_data_key.vbprivk \
--config=/tmp/config.rw \
--vmlinuz /boot/vmlinuz-3.4.0 --arch arm

dd if=/home/chronos/user/Downloads/newkern.rw of=/dev/sda1

This way I was able to boot from usb successfully. Then i have
rebooted the Chromebook into Chrome OS and rewrote out the kernel with
the ‘ro’ flag to the first partition and rebooted again:

echo "console=tty1 debug verbose \
root=/dev/sda2 rootwait ro" > /tmp/config.ro

vbutil_kernel --pack /home/chronos/user/Downloads/newkern \
--keyblock /usr/share/vboot/devkeys/kernel.keyblock \
--version 1 \
--signprivate /usr/share/vboot/devkeys/kernel_data_key.vbprivk \
--config=/tmp/config.rw \
--vmlinuz /boot/vmlinuz-3.4.0 --arch arm

dd if=/home/chronos/user/Downloads/newkern of=/dev/sda1




--

Ottavio

[Mats Christensen]

I was finally able to install from the dev-channel again today, and that gave me an newer firmware-version.

Someone probably noticed that something was wrong and fixed it.

Thank you for all the answers. :)

[Ottavio Caruso]

On 29 November 2012 19:56, Mats Christensen <matschr...@gmail.com> wrote:
> I was finally able to install from the dev-channel again today, and that
> gave me an newer firmware-version.
> Someone probably noticed that something was wrong and fixed it.

I'm still finding my feet on this device but, anybody correct me if
I'm wrong, if:
- I am in dev mode and
- I have dev_boot_usb=1 , but:
- chromeos-firmwareupdate=tonormal

then every time there's a system update all kernel flags will be reset
to normal (verified boot and disable usb boot)?

In other words do I have to "chromeos-firmwareupdate=todev" if I want
to keep my configuration intact?

--
Ottavio

[Hung-Te Lin]

On Fri, Nov 30, 2012 at 4:24 AM, Ottavio Caruso <ottavio2006...@yahoo.com> wrote:

On 29 November 2012 19:56, Mats Christensen <matschr...@gmail.com> wrote:
> I was finally able to install from the dev-channel again today, and that
> gave me an newer firmware-version.
> Someone probably noticed that something was wrong and fixed it.

I'm still finding my feet on this device but, anybody correct me if
I'm wrong, if:
- I am  in dev mode and
- I have  dev_boot_usb=1  , but:
- chromeos-firmwareupdate=tonormal

 

    tonormal makes dev_boot_usb=0.

 

then every time there's a system update all kernel flags will be reset
to normal (verified boot and disable usb boot)?

 

    Only if you leave developer mode. Firmware AU by default don't change dev_boot_usb settings.

 

In other words do I have to "chromeos-firmwareupdate=todev" if I want
to keep my configuration intact?

    Only if you change it (tonormal, or crossystem dev_boot_usb=0) or manually leave developer mode (press SPACE on boot).

 

--
Ottavio