boot ubuntu on chromebook from USB

[megha dey]

I am trying to boot an ubuntu ISO image on a Intel Acer chromebook through a USB stick.

I have dev_boot_usb=1 and dev_boot_legacy=1 dev_boot_signed=0.

When I reboot into the developer screen and do ctrl+U, I just hear a beep. When I do a ctrl +L, I do not enter the legacy SEABIOS screen .This chromebook uses depthcharge payload. Does it mean it does not support seabios?

Also, I see the message when I try to boot from the recovery mode: Device does not contain a chrome OS image. 

Does chromebook book only chromeos images? If I sign my ubuntu kernel with the vbutil_kernel tool, will I be able to boot?

 

[Mike Frysinger]

CTRL+U is only for booting USB images that are formatted as the CrOS firmware expects.  that means GPT and partitions with the right UUIDs & flags & CrOS verified kernels.  if you don't have that, then CTRL+U is not what you want.

CTRL+L is for loading SeaBIOS.  if your system doesn't have it, you'll need to install it (assuming your device supports legacy mode -- you didn't say what the board name is).  depthcharge doesn't matter here.

same goes for recovery mode as CTRL+U: only properly formatted recovery images are accepted there.  you can't boot random media by design.

-mike

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

[megha dey]

Thanks! Understood.

So is there any way I can convert the ubuntu image to what the CrOS firmware expects??

On Thu, Jun 15, 2017 at 6:08 PM Mike Frysinger <vap...@chromium.org> wrote:

CTRL+U is only for booting USB images that are formatted as the CrOS firmware expects.  that means GPT and partitions with the right UUIDs & flags & CrOS verified kernels.  if you don't have that, then CTRL+U is not what you want.

CTRL+L is for loading SeaBIOS.  if your system doesn't have it, you'll need to install it (assuming your device supports legacy mode -- you didn't say what the board name is).  depthcharge doesn't matter here.

same goes for recovery mode as CTRL+U: only properly formatted recovery images are accepted there.  you can't boot random media by design.

-mike

On Thu, Jun 15, 2017 at 6:04 PM, megha dey <meg1...@gmail.com> wrote:

I am trying to boot an ubuntu ISO image on a Intel Acer chromebook through a USB stick.

I have dev_boot_usb=1 and dev_boot_legacy=1 dev_boot_signed=0.

When I reboot into the developer screen and do ctrl+U, I just hear a beep. When I do a ctrl +L, I do not enter the legacy SEABIOS screen .This chromebook uses depthcharge payload. Does it mean it does not support seabios?

Also, I see the message when I try to boot from the recovery mode: Device does not contain a chrome OS image. 

Does chromebook book only chromeos images? If I sign my ubuntu kernel with the vbutil_kernel tool, will I be able to boot?

 

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

[Mike Frysinger]

there is, but it requires a bit of low level manipulation of the image

if you have a board that supports legacy boot, you might want to check out this guys site:

  https://johnlewis.ie/

he provides SeaBIOS images for a variety of boards.  that'd prob be easier than trying to reformat the USB image.

-mike

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

[Hara Acharya]

Or you can install via crouton which will give you dual boot option as in ctrl + L to boot from Linux.

In that way both chromeos and ubuntu will co-exist.

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

[megha dey]

My ultimate aim is to boot my custom linux distro through USB on the chromebook without having to reflash the firmware.

Can u let me know what "low level manipulation" is requied for this?

Thanks!

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

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

---
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-dis...@chromium.org.

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

---
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-dis...@chromium.org.

[Mike Frysinger]

please see the site i posted earlier

-mike

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

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

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

[Robert Boerner]

Another useful site for info is here -> https://mrchromebox.tech/

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-discuss+unsub...@chromium.org.

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

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

[megha dey]

Thanks for the info! 

I am using an acer chromebook R11(cyan) based on the braswell x86 platform. Does this support legacy bios? if there some way to find out?

(I have the dev_boot_legacy=1, but when I do a ctrl+L, I only hear 2 beeps, so not sure if this device supports legacy boot or not)

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-discuss+unsubscribe...@chromium.org.

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

---
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+unsubscribe...@chromium.org.

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

[Robert Boerner]

On Friday, June 16, 2017 at 10:43:23 AM UTC-7, megha dey wrote:

Thanks for the info! 

I am using an acer chromebook R11(cyan) based on the braswell x86 platform. Does this support legacy bios? if there some way to find out?

(I have the dev_boot_legacy=1, but when I do a ctrl+L, I only hear 2 beeps, so not sure if this device supports legacy boot or not)

If you look at the link I provided, they speak to this directly here -> https://mrchromebox.tech/#chromeos at the bottom of the page. Quoting from the external site:

"Note: If you hear two beeps after pressing [CTRL+L], then either your device doesn't have a valid Legacy Boot Mode / RW_LEGACY firmware, or legacy boot capability has not been been enabled via crossystem.

Using the ChromeOS Firmware Utility Script to update your device's RW_LEGACY firmware region will address both of these issues, as it not only provides an updated, fully functional RW_LEGACY firmware, but also sets the required boot flag. "

[Mike Frysinger]

cyan's firmware supports legacy booting.  so you'll want to install a seabios into the legacy partition.

-mike

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-discuss+unsubscribe...@chromium.org.

[megha dey]

I am able to enter legacy mode now. But when I choose the boot from USB option, its just stuck there.

I read that any non chrome kernel can be signed by the user using vbutil_kernel tool. This requires the user to provide keys. Most examples use the default keys from the chromebook itself. Can I use my own key instead? If yes, how can I generate them?

Asuuming I do manage to use my own key to sign my image, will this be enough to trick the CrOS firmware that it is booting a valid image?

[Mike Frysinger]

in dev mode, the firmware doesn't care what keys you use, nor is there any real way for you to check them at runtime, so it's not like making your own keys will make things more secure.  the only way to do that would be to enable writing to the RO firmware and updating the root keys there.  which you don't want to do.

-mike

[brewster slickers]

none of these strategies work. my Chromebook is an Acer c201p and is ARM based. I get the message saying "this program does not support ARM devices, only intel devices" What should I do?

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-discuss+unsub...@chromium.org.

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

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

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

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

[Mark Resing]

[James Parsons]

RE: 

CTRL+U is only for booting USB images that are formatted as the CrOS firmware expects.  that means GPT and partitions with the right UUIDs & flags & CrOS verified kernels

Right now I'm using Crouton and my CTRL+L does not work.

With Bionic Beaver due out soon, being able to run BB from a flash drive with CTRL+U is appealing.

I can certainly format a flash drive to GPT, but what are the required UUID's and flags?

Is the Bionic kernel CrOS verified?

If it's possible, would I install to a flash drive or use the installation flash drive with persistence?

More generally, can CTRL+U be used a substitute for CTRL-L?  My croutons mostly work, but I always heave a sigh of relief when they actually start.

Thank you in advance

On Friday, June 16, 2017 at 9:04:34 AM UTC+8, megha dey wrote:

I am trying to boot an ubuntu ISO image on a Intel Acer chromebook through a USB stick.

I have dev_boot_usb=1 and dev_boot_legacy=1 dev_boot_signed=0.,