Trying to boot from USB on Acer chromebook

[Kristov]

I'm trying to boot into Linux off a USB drive, but having no luck. I just
purchased the computer today.

I followed this
tutorial: http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/acer-c7-chromebook

Here's some of the output from crossystem:
arch = x86
clear_tpm_owner_request = (error)
clear_tpm_owner_done = (error)
cros_debug = 1
dbg_rest = (error)
disable_dev_request = (error)
dev_boot_usb = (error)
dev_boot_legacy = (error)
dev_boot_signed)only = (error)
devsw_boot = 1
devsw_cur =1
fwid = Google_Parrot.2685.54.0
wpsw_boot = 1
wpsw_cur = 1

I tried setting dev_boot_usb to 1, but for whatever reason it seems to be
set to (error). When I'm in recovery mode and press Tab, it prints:

HWID: PARROT ARUANA A-E 8667
recovery_reason: 0x02 recovery button pressed
VbSD.flags: 0x0000670
VbNv.raw: 70 20 00 00 01 00 00 00 00 00 00 00 00 00 00 cb
dev_boot_usb: 1
dev_boot_signed_only: 0
TPM: fwver=0x00010003 kernver=0x00020001
gbb.flags: 0x00000000
gbb.rootkey: ...
gbb.recovery_key: ...
read-only firmware id: Google_Parrot.2685.54.0
active firmware id: Google_Parrot.2685.54.0

When I get to the OS verification screen and press Ctrl+U, the screen
sometimes flashes black briefly and returns to the same screen, and makes a
few beeps, but it does not boot from a valid linux USB image.

Thanks in advance for your help
-Kristov

[Mike Frysinger]

Post by Kristov
When I get to the OS verification screen and press Ctrl+U, the screen
sometimes flashes black briefly and returns to the same screen, and makes a
few beeps, but it does not boot from a valid linux USB image.

what exactly are you defining as a "valid linux USB image" ? the CrOS
firmware won't boot USB images off the shelf like you download from
ubuntu.com. you have to format it with a CrOS formatted disk.
-mike

[Kristov]

Post by Mike Frysinger

Post by Kristov
When I get to the OS verification screen and press Ctrl+U, the screen
sometimes flashes black briefly and returns to the same screen, and makes a
few beeps, but it does not boot from a valid linux USB image.

what exactly are you defining as a "valid linux USB image" ? the CrOS
firmware won't boot USB images off the shelf like you download from
ubuntu.com. you have to format it with a CrOS formatted disk.
-mike

Interesting. I used http://www.linuxliveusb.com/ to create the images.

[Mike Frysinger]

Post by Kristov

Post by Mike Frysinger

Post by Kristov
When I get to the OS verification screen and press Ctrl+U, the screen
sometimes flashes black briefly and returns to the same screen, and makes a
few beeps, but it does not boot from a valid linux USB image.

what exactly are you defining as a "valid linux USB image" ? the CrOS
firmware won't boot USB images off the shelf like you download from
ubuntu.com. you have to format it with a CrOS formatted disk.

Interesting. I used http://www.linuxliveusb.com/ to create the images.

yeah i doubt that'll produce images that will work
-mike

[Kristov]

Post by Mike Frysinger

Post by Kristov
When I get to the OS verification screen and press Ctrl+U, the screen
sometimes flashes black briefly and returns to the same screen, and makes a
few beeps, but it does not boot from a valid linux USB image.

what exactly are you defining as a "valid linux USB image" ? the CrOS
firmware won't boot USB images off the shelf like you download from
ubuntu.com. you have to format it with a CrOS formatted disk.
-mike

Any idea where I could find instructions for creating a CrOS formatted
disk? Would the instructions in the first answer to this question work?
http://askubuntu.com/questions/278403/how-do-you-make-usb-bootable-on-chromebook

[Mike Frysinger]

Post by Kristov

Post by Mike Frysinger

Post by Kristov
When I get to the OS verification screen and press Ctrl+U, the screen
sometimes flashes black briefly and returns to the same screen, and makes a
few beeps, but it does not boot from a valid linux USB image.

what exactly are you defining as a "valid linux USB image" ? the CrOS
firmware won't boot USB images off the shelf like you download from
ubuntu.com. you have to format it with a CrOS formatted disk.

Any idea where I could find instructions for creating a CrOS formatted
disk?

you might be able to try this:
http://dev.chromium.org/chromium-os/developer-information-for-chrome-os-devices/cr-48-chrome-notebook-developer-information#TOC-How-to-boot-your-own-non-Chromium-OS-image-from-USB

it's not specific to the CR-48. that page just gathered a lot of details
as we sent out the CR-48 long before any other device, so a lot of details
gathered there.

Would the instructions in the first answer to this question work?

Post by Kristov
http://askubuntu.com/questions/278403/how-do-you-make-usb-bootable-on-chromebook

pretty sure those instructions are for "how do i create a bootable USB
image on a Chromebook for use on a non-chromebook". i don't see anything
in their answer that'd make it bootable on a Chromebook system.
-mike

[Julian Bond]

Sender: chromium-os-discuss-F7+***@public.gmane.org
X-Gm-Message-State: ALoCoQn0i8gp2XypUe9/+E3p+mviw+GJZUuH22e0AIM4bMtOfNQxwGUf0E+BK6puLYUChKtm1KMT
X-Received: by 10.180.8.70 with SMTP id p6mr5066779wia.5.1385795392950;
Fri, 29 Nov 2013 23:09:52 -0800 (PST)
X-BeenThere: chromium-os-discuss-F7+***@public.gmane.org
Received: by 10.180.13.106 with SMTP id g10ls374299wic.50.canary; Fri, 29 Nov
2013 23:09:49 -0800 (PST)
X-Received: by 10.14.179.130 with SMTP id h2mr23951945eem.34.1385795389474;
Fri, 29 Nov 2013 23:09:49 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de. [212.227.17.10])
by mx.google.com with ESMTPS id f8si37466957eep.225.2013.11.29.23.09.49
for <chromium-os-discuss-F7+***@public.gmane.org>
(version=TLSv1 cipher=RC4-SHA bits8/128);
Fri, 29 Nov 2013 23:09:49 -0800 (PST)
Received-SPF: neutral (google.com: 212.227.17.10 is neither permitted nor denied by best guess record for domain of julian.bond-/Fkc1E/MbsFWk0Htik3J/***@public.gmane.org) client-ip!2.227.17.10;
Received: from jblaptop.voidstar.com (cpc19-ware5-2-0-cust966.9-1.cable.virginm.net [80.2.3.199])
by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis)
id 0MCOfZ-1VvDFw2sHx-009LOk; Sat, 30 Nov 2013 08:09:45 +0100
In-Reply-To: <CAAbOSc=oF8KRZoGwF8bYgX7Sm7ssLV2hv-K-svh=jjidB7SEDw-JsoAwUIsXosN+***@public.gmane.org>
User-Agent: Turnpike/6.07-M (<kLxGNhEIkwXYl+9NGfdv97dtzX>)
X-Provags-ID: V02:K0:sSIyEf1ZXjT3CyFRviJp3AcyoNddQBT45wx2DcF5Rue
8efjLHVt2DZRjg5DvSycePsnCPSoZ3tDOPUSjX9QcgPPz4JHd9
6A7VYeE1ae727unVLYCqCy3bfFDNFDLTVEvIt1R2+oQ3mXILXa
4Bk7R2JzO+ZVxzTThxyu+y5HWIU6V6XR9kWP1jmX5F5Ja8EeT0
dLz8A2w3O7IGvrEg7LE3IglDnAJI9dYhu7iIxe55kRsnZFON05
4aH3tezdYJRrRadPj7cAbl3k5ucMZodCvzOukbdO3lI0uwwkTZ
aJfXD6mpdhLsVryVcTbCgDMqSV+AkkwFy13lGlCRbrtJ/UQdjO
IzolpvE9A0IzsYlHscMy/RD4XigXmQ6YDlvzjv2/Nu8VmFupsQ
qMkewDQgimf6Q=X-Original-Sender: julian.bond-/Fkc1E/MbsFWk0Htik3J/***@public.gmane.org
X-Original-Authentication-Results: mx.google.com; spf=neutral
(google.com: 212.227.17.10 is neither permitted nor denied by best guess
record for domain of julian.bond-/Fkc1E/MbsFWk0Htik3J/***@public.gmane.org) smtp.mail=julian.bond-/Fkc1E/MbsFWk0Htik3J/***@public.gmane.org
Precedence: list
Mailing-list: list chromium-os-discuss-F7+***@public.gmane.org; contact chromium-os-discuss+owners-F7+***@public.gmane.org
List-ID: <chromium-os-discuss.chromium.org>
X-Google-Group-Id: 29215888310
List-Post: <http://groups.google.com/a/chromium.org/group/chromium-os-discuss/post>,
<mailto:chromium-os-discuss-F7+***@public.gmane.org>
List-Help: <http://support.google.com/a/chromium.org/bin/topic.py?topic%838>,
<mailto:chromium-os-discuss+help-F7+***@public.gmane.org>
List-Archive: <http://groups.google.com/a/chromium.org/group/chromium-os-discuss/>
List-Subscribe: <http://groups.google.com/a/chromium.org/group/chromium-os-discuss/subscribe>,
<mailto:chromium-os-discuss+subscribe-F7+***@public.gmane.org>
List-Unsubscribe: <http://groups.google.com/a/chromium.org/group/chromium-os-discuss/subscribe>,
<mailto:googlegroups-manage+29215888310+unsubscribe-/***@public.gmane.org>
Archived-At: <http://permalink.gmane.org/gmane.os.chromium.general/3212>

what exactly are you defining as a "valid linux USB image" ?  the CrOS
firmware won't boot USB images off the shelf like you download from ubuntu.com.  you have to format it with a CrOS formatted disk.

Really? Could you explain a bit more or point at an explanation.

So the BIOS won't boot from a conventional boot disk or USB boot device?
Is there the equivalent of the usual BIOS boot choice where you get to
choose which device to boot from?

And what does "a CrOS formatted disk" mean? Does the boot device have to
be EXT4 or a full CrOS set of 12 partitions or what?
--
Julian Bond E: julian.bond at voidstar.com
M: [phone] T: [phone]
W: http://www.voidstar.com/ skype:julian.bond?chat
Follow Dosage Below

[Mike Frysinger]

Post by Julian Bond

Post by Mike Frysinger
what exactly are you defining as a "valid linux USB image" ? the CrOS
firmware won't boot USB images off the shelf like you download from
ubuntu.com. you have to format it with a CrOS formatted disk.

Really? Could you explain a bit more or point at an explanation.
So the BIOS won't boot from a conventional boot disk or USB boot device?
Is there the equivalent of the usual BIOS boot choice where you get to
choose which device to boot from?

certainly not. the CrOS firmware is designed to be fast which means there
is no GUI for the user to interact with. the "usual BIOS" is bloated and
slow and does way more than we would ever need or want on a CrOS system.

And what does "a CrOS formatted disk" mean? Does the boot device have to be

Post by Julian Bond
EXT4 or a full CrOS set of 12 partitions or what?

the partition marked as bootable must have an image the firmware knows how
to parse (have a valid verified boot header at the start). the
dev.chromium.org wiki has a page or two on the topic.
-mike

[Julian Bond]

Sender: chromium-os-discuss-F7+***@public.gmane.org
X-Gm-Message-State: ALoCoQkxjTmpNiDJyuH17cL2NZZ5YUPO2ZRLmqdlhgM0zgQXHkn8VCjfET5Z/5ZVxQv8j8IuRNB8
X-Received: by 10.15.51.132 with SMTP id n4mr23349800eew.3.1385836040652;
Sat, 30 Nov 2013 10:27:20 -0800 (PST)
X-BeenThere: chromium-os-discuss-F7+***@public.gmane.org
Received: by 10.180.80.163 with SMTP id s3ls465229wix.43.gmail; Sat, 30 Nov
2013 10:27:18 -0800 (PST)
X-Received: by 10.15.91.3 with SMTP id r3mr58111460eez.18.1385836038437;
Sat, 30 Nov 2013 10:27:18 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de. [212.227.17.10])
by mx.google.com with ESMTPS id p1si32040011eey.277.2013.11.30.10.27.18
for <chromium-os-discuss-F7+***@public.gmane.org>
(version=TLSv1 cipher=RC4-SHA bits8/128);
Sat, 30 Nov 2013 10:27:18 -0800 (PST)
Received-SPF: neutral (google.com: 212.227.17.10 is neither permitted nor denied by best guess record for domain of julian.bond-/Fkc1E/MbsFWk0Htik3J/***@public.gmane.org) client-ip!2.227.17.10;
Received: from jblaptop.voidstar.com (cpc19-ware5-2-0-cust966.9-1.cable.virginm.net [80.2.3.199])
by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis)
id 0MBo5j-1VwPVy2eIx-00AWhw; Sat, 30 Nov 2013 19:27:17 +0100
In-Reply-To: <CAAbOScn-050ikS4STA8Ps5tMrwVFPëhg3uU1R3OSRU4Q_hjg-JsoAwUIsXosN+***@public.gmane.org>
User-Agent: Turnpike/6.07-M (<1h$GNJ25kwX7e+9N4eXv9$0X9C>)
X-Provags-ID: V02:K0:aVsVxQ/JbrsxTCdAh4EgYETi1TU2orFK1I3lFfjlBT/
v69EkzmDxta9mDUvhyU5LfLDW13k7Mz1Il/6VLc3zT0ft15lEV
WZIvXrTiw6C3IS5wvUt0QfGKjZN1Gmdrwev04rp5OIn2qcA9VT
VAqIZt9JjKZuk1zhXdKdJSNFZdii0C+VsJVBazqoLyafe6Dt0A
+1+jkj+kNqg70YxivBYRO22aSBp9QYWr9y3hrscIXVmwTCtOTx
0zIquewkqLLfBd4yTM8p1zRaYABrinv8FdjvonvVO966xK8vmR
PLUn2G/AuAC4cCKTtd/IEC1YeL4QD6d6e9dAkYMf1phgL2GrMU
U/7n4m460hHZlQeOVxPJveizeGV1UigNG3k0vGTBv9oMJWiSY2
9OclhksMvWwMw=X-Original-Sender: julian.bond-/Fkc1E/MbsFWk0Htik3J/***@public.gmane.org
X-Original-Authentication-Results: mx.google.com; spf=neutral
(google.com: 212.227.17.10 is neither permitted nor denied by best guess
record for domain of julian.bond-/Fkc1E/MbsFWk0Htik3J/***@public.gmane.org) smtp.mail=julian.bond-/Fkc1E/MbsFWk0Htik3J/***@public.gmane.org
Precedence: list
Mailing-list: list chromium-os-discuss-F7+***@public.gmane.org; contact chromium-os-discuss+owners-F7+***@public.gmane.org
List-ID: <chromium-os-discuss.chromium.org>
X-Google-Group-Id: 29215888310
List-Post: <http://groups.google.com/a/chromium.org/group/chromium-os-discuss/post>,
<mailto:chromium-os-discuss-F7+***@public.gmane.org>
List-Help: <http://support.google.com/a/chromium.org/bin/topic.py?topic%838>,
<mailto:chromium-os-discuss+help-F7+***@public.gmane.org>
List-Archive: <http://groups.google.com/a/chromium.org/group/chromium-os-discuss/>
List-Subscribe: <http://groups.google.com/a/chromium.org/group/chromium-os-discuss/subscribe>,
<mailto:chromium-os-discuss+subscribe-F7+***@public.gmane.org>
List-Unsubscribe: <http://groups.google.com/a/chromium.org/group/chromium-os-discuss/subscribe>,
<mailto:googlegroups-manage+29215888310+unsubscribe-/***@public.gmane.org>
Archived-At: <http://permalink.gmane.org/gmane.os.chromium.general/3214>

Post by Julian Bond
Is there the equivalent of the usual BIOS boot choice where
you get to choose which device to boot from?
certainly not.  the CrOS firmware is designed to be fast which means
there is no GUI for the user to interact with.  the "usual BIOS" is
bloated and slow and does way more than we would ever need or want on a
CrOS system.

Hrmph! I don't recall ever seeing a GUI based BIOS screen but perhaps
there is one out there somewhere. And Coreboot+SeaBios (or an OEM
equivalent from Phoenix say) is not exactly bloated and slow.

Reading a bit more, it seems that Chrome-OS on an official Chromebook
uses a locked down coreboot, U-Boot, boot code sequence that really
doesn't want to allow you to boot from a USB stick; Mainly for security
reasons.

There may be a way to trick this to launch another linux based OS but
you'll be in dev mode and have a 5 minute lockout during the boot
process. As described here
http://dev.chromium.org/chromium-os/developer-information-for-chrome-os-d
evices/cr-48-chrome-notebook-developer-information/how-to-boot-ubuntu-on-
a-cr-48
and
http://dev.chromium.org/chromium-os/developer-information-for-chrome-os-d
evices/cr-48-chrome-notebook-developer-information#TOC-How-to-boot-your-o
wn-non-Chromium-OS-image-from-USB

Basically you're starting Chrome but early in the boot process switching
to another OS.

In the second answer here
http://askubuntu.com/questions/278403/how-do-you-make-usb-bootable-on-chr
omebook he says:-
"reboot your computer and spam F12 while it's booting up - it should ask
you what you want to boot from." From your answer, and what I've read I
don't think this will work. Because coreboot and U-Boot are never going
to give you that option.

----------
Please correct me if I'm wrong, but ISTM that Chromebooks are NOT
general purpose laptops pre-loaded with a Google OEM version of
Chromium-OS. They are locked down laptops that are designed to ONLY run
Chrome-OS. It's just about possible to persuade them to run another
Linux but with limitations.

That's not necessarily a bad thing. In fact it could be viewed as a good
thing. As long as we're all clear that that's what they are.

So to get back to Kristov's original query, we're into this territory.
"You can't do that, why would you want to?"
--
Julian Bond E: julian.bond at voidstar.com
M: [phone] T: [phone]
W: http://www.voidstar.com/ skype:julian.bond?chat
Don't Touch That Dial

[Mike Frysinger]

Post by Julian Bond

Post by Julian Bond
Is there the equivalent of the usual BIOS boot choice where
you get to choose which device to boot from?
certainly not. the CrOS firmware is designed to be fast which means
there is no GUI for the user to interact with. the "usual BIOS" is
bloated and slow and does way more than we would ever need or want on a
CrOS system.

Hrmph! I don't recall ever seeing a GUI based BIOS screen but perhaps
there is one out there somewhere. And Coreboot+SeaBios (or an OEM
equivalent from Phoenix say) is not exactly bloated and slow.

anything that shows graphics or looks for user input is slow.
coreboot+seabios is better than most to be sure in terms of bloat, but
it's still more than we need.

Reading a bit more, it seems that Chrome-OS on an official Chromebook uses

Post by Julian Bond
a locked down coreboot, U-Boot, boot code sequence that really doesn't want
to allow you to boot from a USB stick; Mainly for security reasons.

when you're not in developer mode, everything is locked down by design.
it's fast and secure.

if you want to do anything else, you enable developer mode, and then you
can boot whatever you want (including off USB). the limitation is that the
thing you want to boot has to be formatted in the way the CrOS firmware
expects.

or you can build & install your own firmware, although that can be risky.

There may be a way to trick this to launch another linux based OS but

Post by Julian Bond
you'll be in dev mode and have a 5 minute lockout during the boot process.
As described here

the 5 min lockout is just once when you transition to dev mode for the
first time. it clears all the local state. once that has happened, there
is no 5 min delay.

In the second answer here

Post by Julian Bond
http://askubuntu.com/questions/278403/how-do-you-make-usb-bootable-on-chr
omebook he says:-
"reboot your computer and spam F12 while it's booting up - it should ask
you what you want to boot from." From your answer, and what I've read I
don't think this will work. Because coreboot and U-Boot are never going to
give you that option.
----------
Please correct me if I'm wrong, but ISTM that Chromebooks are NOT general
purpose laptops pre-loaded with a Google OEM version of Chromium-OS. They
are locked down laptops that are designed to ONLY run Chrome-OS. It's just
about possible to persuade them to run another Linux but with limitations.

they are *designed* to only run ChromeOS, but they aren't *restricted* to
only run ChromeOS. we provide a dev mode switch so that, if you really
want to own the hardware, you can. that includes running anything you want.
-mike

[Julian Bond]

Sender: chromium-os-discuss-F7+***@public.gmane.org
X-Gm-Message-State: ALoCoQn7rwHfLsAsjt1QNeUHOjYEBRmj/UW9huWs2kPuT94oY+5DDd/oqpc2CpSvEnJXWyrnAjzu
X-Received: by 10.112.17.67 with SMTP id m3mr3149629lbd.8.1386143724452;
Tue, 03 Dec 2013 23:55:24 -0800 (PST)
X-BeenThere: chromium-os-discuss-F7+***@public.gmane.org
Received: by 10.181.13.11 with SMTP id eu11ls945940wid.34.canary; Tue, 03 Dec
2013 23:55:21 -0800 (PST)
X-Received: by 10.14.208.199 with SMTP id q47mr6197644eeo.77.1386143721710;
Tue, 03 Dec 2013 23:55:21 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de. [212.227.17.10])
by mx.google.com with ESMTPS id g5si363683eev.91.2013.12.03.23.55.21
for <chromium-os-discuss-F7+***@public.gmane.org>
(version=TLSv1 cipher=RC4-SHA bits8/128);
Tue, 03 Dec 2013 23:55:21 -0800 (PST)
Received-SPF: neutral (google.com: 212.227.17.10 is neither permitted nor denied by best guess record for domain of julian.bond-/Fkc1E/MbsFWk0Htik3J/***@public.gmane.org) client-ip!2.227.17.10;
Received: from jblaptop.voidstar.com (cpc19-ware5-2-0-cust966.9-1.cable.virginm.net [80.2.3.199])
by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis)
id 0MMJjd-1Vgf3M0M3B-007uSO; Wed, 04 Dec 2013 08:55:21 +0100
In-Reply-To: <CAAbOSc=UGoS_adZFBkkwoXDBHnddE=PFT83qKy8e1TqwtdQUig-JsoAwUIsXosN+***@public.gmane.org>
User-Agent: Turnpike/6.07-M (<dd0GN5YVkwnN889NzmZv9fG4ij>)
X-Provags-ID: V02:K0:kxrbcyR1jTPN3TWuNRRgD37iNH/ViJA38tvE+oHGtoF
SalZgmoHp1wyYduPeYILEM48HY2RUgsguoDfAQVlSlmn0HpuTU
wjBlchGGg//lcTSW8cwAH1Z7/K0Fe9ZwOS5U9AxkKzVWOGYjVd
McXuuMFuGE2Bae5NKJ1vxk8sADi6PDcEJkDP+Zc9tUNxIkPSDL
XNKscHxsJBCj4kVR5+7PJGiDazeBiHEBjumE4xOOcwVb/vnYfb
INQONvjkgrT6gOjlqhb4dYaiJAcW6z6uTgmw9sqrsS5MT7MM1q
epzpRdU0q8U7mjMpS5is2hBu0UBADmXdP6gr6tsFtMKbJFDLzW
2yFAv/fODzFJPv2Mej0EAvYjiqf7OEAfM1MyPzzM6LW/9HMhsd
T/sgIlsWGqLvQ=X-Original-Sender: julian.bond-/Fkc1E/MbsFWk0Htik3J/***@public.gmane.org
X-Original-Authentication-Results: mx.google.com; spf=neutral
(google.com: 212.227.17.10 is neither permitted nor denied by best guess
record for domain of julian.bond-/Fkc1E/MbsFWk0Htik3J/***@public.gmane.org) smtp.mail=julian.bond-/Fkc1E/MbsFWk0Htik3J/***@public.gmane.org
Precedence: list
Mailing-list: list chromium-os-discuss-F7+***@public.gmane.org; contact chromium-os-discuss+owners-F7+***@public.gmane.org
List-ID: <chromium-os-discuss.chromium.org>
X-Google-Group-Id: 29215888310
List-Post: <http://groups.google.com/a/chromium.org/group/chromium-os-discuss/post>,
<mailto:chromium-os-discuss-F7+***@public.gmane.org>
List-Help: <http://support.google.com/a/chromium.org/bin/topic.py?topic%838>,
<mailto:chromium-os-discuss+help-F7+***@public.gmane.org>
List-Archive: <http://groups.google.com/a/chromium.org/group/chromium-os-discuss/>
List-Subscribe: <http://groups.google.com/a/chromium.org/group/chromium-os-discuss/subscribe>,
<mailto:chromium-os-discuss+subscribe-F7+***@public.gmane.org>
List-Unsubscribe: <http://groups.google.com/a/chromium.org/group/chromium-os-discuss/subscribe>,
<mailto:googlegroups-manage+29215888310+unsubscribe-/***@public.gmane.org>
Archived-At: <http://permalink.gmane.org/gmane.os.chromium.general/3219>

Post by Mike Frysinger
they are *designed* to only run ChromeOS, but they aren't *restricted*
to only run ChromeOS.  we provide a dev mode switch so that, if you
really want to own the hardware, you can.  that includes running
anything you want.

I'm tempted to say, "As long as what you want can use the Chromium
kernel instead of it's own.".

However, I've just come across this:-
http://chromeos-cr48.blogspot.co.uk/2013/10/chrubuntu-for-new-chromebooks
-now-with.html

Note the first para:-
"Since I started ChrUbuntu back in December of 2010, it's always been
necessary to utilize the Chrome OS Linux kernel with Ubuntu in order to
solve some compatibility issues with the Chromebook architecture. That's
changed with the Chromebook Pixel and the newer Haswell-based
Chromebooks like the Acer C720 and HP Chromebook 14. Each of these
models supports booting from a more traditional PC BIOS mode which makes
it simple to use stock Ubuntu kernels on them."

So the Pixel, C720 and HP14 DO have a traditional BIOS on board and it's
possible to boot $arbitraryLiveDistroOs from a USB stick. Probably.

So back to Kristov. Which Acer Chromebook is it? And after putting it
into dev mode, perhaps you need CTRL-L instead of CTRL-U.
--
Julian Bond E: julian.bond at voidstar.com
M: [phone] T: [phone]
W: http://www.voidstar.com/ skype:julian.bond?chat
Void Where Prohibited

[Mike Frysinger]

Post by Mike Frysinger
they are *designed* to only run ChromeOS, but they aren't *restricted*
to only run ChromeOS. we provide a dev mode switch so that, if you
really want to own the hardware, you can. that includes running
anything you want.

I'm tempted to say, "As long as what you want can use the Chromium kernel
instead of it's own.".

that's not what i said. you have to add a proper header (which is pretty
small, and can be generated with our open source verified boot tools, and
is all documented in our wiki), and then you can boot any image you want.

However, I've just come across this:-

http://chromeos-cr48.blogspot.co.uk/2013/10/chrubuntu-for-new-chromebooks
-now-with.html
Note the first para:-
"Since I started ChrUbuntu back in December of 2010, it's always been
necessary to utilize the Chrome OS Linux kernel with Ubuntu in order to
solve some compatibility issues with the Chromebook architecture. That's
changed with the Chromebook Pixel and the newer Haswell-based Chromebooks
like the Acer C720 and HP Chromebook 14. Each of these models supports
booting from a more traditional PC BIOS mode which makes it simple to use
stock Ubuntu kernels on them."
So the Pixel, C720 and HP14 DO have a traditional BIOS on board and it's
possible to boot $arbitraryLiveDistroOs from a USB stick. Probably.

yes & no. they have the ChromeOS firmware like normal, but we additionally
included a SeaBIOS payload in the flash. when you're in normal mode (not
dev mode), the CrOS firmware runs like every other system -- it's tiny &
fast & just boots signed images, and does not read let alone execute
SeaBIOS. when you're in dev mode, the CrOS firmware shows you the scary
warning screen like every other system. but at this point, if you hit
CTRL+L, that tells the firmware to chainload the SeaBIOS and then you have
a more traditional PC BIOS resident.
-mike

[Ron]

All

It is my understanding the Acer 710 models have the additional space in the
BIOS/ROM to potentially support the official Google provided Seabois. There
are UN-official versions of Seabios available on the WEB that can be
installed on the Acer C710 Chromebook models that allow the CTRL-L option.
This allows booting many Linux distros via the USB ports on the Acer C710
models; however, since the un-official Seabios is not Digitally Signed by
Google, the Acer C710 can NOT boot to the super secure Google Stable
ChromeOS. If the original/official backed up BIOS/ROM version were
restored, then one could boot into the secure (Factory delivered) stable
mode. The Acer C720 models do support the Control-L option (ONLY while in
developer mode) which is a step in the right direction.

Comments/Questions regarding above:

Will Google ever supply Official Digitally Signed versions of the SeaBios
to Acer C710 owners? or is this even possible given the security model?

Could it be possible (on the C720 models/C710 models with an Signed SeaBios)
to allow booting from USB without reverting to developer mode? One possible
method: Require the Owner (ONLY) of the Chromebook to Authenticate to the
device prior to performing a soft boot which could potentially allow booting
many Linux xyz distros via USB. Again, would doing so, weaken the strong
security model?

It would be fantastic if I could boot from a Puppy Linux hardware write
locked USB flash drive (which runs entirely from RAM ie.. no hard drive
required/mounted), then simply power cycle the ChromeBook to revert back to
the super secure factory delivered official Google ChromeOS mode.

Regards, Ron


--

[Mike Frysinger]

Post by Ron
models; however, since the un-official Seabios is not Digitally Signed by
Google, the Acer C710 can NOT boot to the super secure Google Stable
ChromeOS.

i don't believe this is true. the R/O firmware isn't signed. the R/W
firmware is signed, but only so that the R/O firmware will boot it.
the signing of the firmware itself has nothing to do with its ability
to boot something like CrOS.

maybe you're confusing the ability of the firmware to verify the CrOS kernel ?

Post by Ron
Will Google ever supply Official Digitally Signed versions of the SeaBios
to Acer C710 owners? or is this even possible given the security model?

most likely not for the foreseeable future

Post by Ron
Could it be possible (on the C720 models/C710 models with an Signed SeaBios)
to allow booting from USB without reverting to developer mode?

not with the official firmware by design
-mike

--

[Kristov]

Post by Julian Bond
So back to Kristov. Which Acer Chromebook is it? And after putting it
into dev mode, perhaps you need CTRL-L instead of CTRL-U.

Thanks for the suggestion. I'm using an Acer C710-2834. When I boot up,
Ctrl-L doesn't do anything. Ctrl-U causes the screen to go to black
briefly, followed by a lower pitched beep, and then two higher pitched
beeps. I don't know where the beep codes are documented, but it "sounds"
like it's rejecting the USB drive I have inserted due to being improperly
formatted.

Earlier in the thread, someone linked
to: http://dev.chromium.org/chromium-os/developer-information-for-chrome-os-devices/cr-48-chrome-notebook-developer-information#TOC-How-to-boot-your-own-non-Chromium-OS-image-from-USB

This provides instructions for "Creating a USB disk that will boot a simple
script", but the "Create a USB disk that will boot another operating
system" instructions are not filled out at all. I don't have the skills or
time to develop said skills to figure that out, unfortunately. Looks like I
will not be able to use this Chromebook for what I want to use it for.

[deus]

The only way is to dual boot using crouton. The process is found here
https://tr1t.wordpress.com/2015/04/21/installing-mint-cinnamon-in-crouton/

02:15:39
<javascript:>>

Post by Julian Bond
Is there the equivalent of the usual BIOS boot choice where
you get to choose which device to boot from?
certainly not. the CrOS firmware is designed to be fast which means
there is no GUI for the user to interact with. the "usual BIOS" is
bloated and slow and does way more than we would ever need or want on a
CrOS system.

Hrmph! I don't recall ever seeing a GUI based BIOS screen but perhaps
there is one out there somewhere. And Coreboot+SeaBios (or an OEM
equivalent from Phoenix say) is not exactly bloated and slow.
Reading a bit more, it seems that Chrome-OS on an official Chromebook
uses a locked down coreboot, U-Boot, boot code sequence that really
doesn't want to allow you to boot from a USB stick; Mainly for security
reasons.
There may be a way to trick this to launch another linux based OS but
you'll be in dev mode and have a 5 minute lockout during the boot
process. As described here
http://dev.chromium.org/chromium-os/developer-information-for-chrome-os-d
evices/cr-48-chrome-notebook-developer-information/how-to-boot-ubuntu-on-
a-cr-48
<http://dev.chromium.org/chromium-os/developer-information-for-chrome-os-devices/cr-48-chrome-notebook-developer-information/how-to-boot-ubuntu-on-a-cr-48>
and
http://dev.chromium.org/chromium-os/developer-information-for-chrome-os-d
evices/cr-48-chrome-notebook-developer-information#TOC-How-to-boot-your-o
wn-non-Chromium-OS-image-from-USB
<http://dev.chromium.org/chromium-os/developer-information-for-chrome-os-devices/cr-48-chrome-notebook-developer-information#TOC-How-to-boot-your-own-non-Chromium-OS-image-from-USB>
Basically you're starting Chrome but early in the boot process switching
to another OS.
In the second answer here
http://askubuntu.com/questions/278403/how-do-you-make-usb-bootable-on-chr
omebook he says:-
"reboot your computer and spam F12 while it's booting up - it should ask
you what you want to boot from." From your answer, and what I've read I
don't think this will work. Because coreboot and U-Boot are never going
to give you that option.
----------
Please correct me if I'm wrong, but ISTM that Chromebooks are NOT
general purpose laptops pre-loaded with a Google OEM version of
Chromium-OS. They are locked down laptops that are designed to ONLY run
Chrome-OS. It's just about possible to persuade them to run another
Linux but with limitations.
That's not necessarily a bad thing. In fact it could be viewed as a good
thing. As long as we're all clear that that's what they are.
So to get back to Kristov's original query, we're into this territory.
"You can't do that, why would you want to?"
--
Julian Bond E: julian.bond at voidstar.com
M: [phone] T: [phone]
W: http://www.voidstar.com/ skype:julian.bond?chat
Don't Touch That Dial

[DennisLfromGA]

@Mike, Quick question: I just bought the HP Chromebook 14 from Walmart (4GB
RAM / 16GB SSD) for my son for Christmas and was wondering about Developer
mode on the Haswell Chromebooks. In developer mode I know you can press
Ctrl-D or wait and get into ChromeOS and I know you can press Ctrl-L and
access SeaBIOS and boot different partitions but can you also press Ctrl-U
like on my Acer C710 and boot directly off a usb stick?

Curious,
-DennisL

P.S. I'm not sure where to find this info., I have looked around a bit but
haven't come up with this answer yet.

[Mike Frysinger]

yes

all dev info can be found here:

http://dev.chromium.org/chromium-os/developer-information-for-chrome-os-devices

if there's device-specific info you think is missing, you could request an
update via http://crbug.com/new
-mike

Post by DennisLfromGA
@Mike, Quick question: I just bought the HP Chromebook 14 from Walmart
(4GB RAM / 16GB SSD) for my son for Christmas and was wondering about
Developer mode on the Haswell Chromebooks. In developer mode I know you can
press Ctrl-D or wait and get into ChromeOS and I know you can press Ctrl-L
and access SeaBIOS and boot different partitions but can you also press
Ctrl-U like on my Acer C710 and boot directly off a usb stick?
Curious,
-DennisL
P.S. I'm not sure where to find this info., I have looked around a bit but
haven't come up with this answer yet.
--
--
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

[DennisLfromGA]

@Mike, Thanx for the quick reply and info., that's good to know.

I may take you up on requesting an update on device-specific info. though,
the link you provided me for the HP Chromebook 14 makes no mention of
setting up dev_boot_legacy or using Ctrl-L at the scary screen and I think
it's pretty important.

Thanx again,
-DennisL

[DennisLfromGA]

@Mike, I reported the issue here<https://code.google.com/p/chromium/issues/detail?id=325904>,
if you or anyone else would like to *star* it, please do.

[DennisLfromGA]

@Kristov - The Acer C710 doesn't support 'legacy bios' via Ctrl-L like the
Pixel and the newer Haswell Chromebooks, only the 'usb boot' option in Dev
mode via Ctrl-U which needs a signed image as @Mike mentioned previously.
You may be familiar with a Googler by the name of Jay Lee who has provided
a way to create these 'signed' images and boot 'Chrubuntu<http://chromeos-cr48.blogspot.com/2013/05/chrubuntu-one-script-to-rule-them-all_31.html>'
which you can now use to load any one of several Ubuntu desktops - Kubuntu,
Xubuntu, EdUbuntu, etc. These can be loaded on your internal drive or an
external USB drive which I think is what you're interested in. Take a look
at "ChrUbuntu: One Script to Rule Them All!''<http://chromeos-cr48.blogspot.com/2013/05/chrubuntu-one-script-to-rule-them-all_31.html>for more info. I've done this on my Acer C710-2847 - both internally and
externally and it works great. It's a good option for these older
Chromebooks and bypasses the need to 'have the skills or time' to figure
this stuff out.

-DennisL

Post by Julian Bond
So back to Kristov. Which Acer Chromebook is it? And after putting it
into dev mode, perhaps you need CTRL-L instead of CTRL-U.

Thanks for the suggestion. I'm using an Acer C710-2834. When I boot up,
Ctrl-L doesn't do anything. Ctrl-U causes the screen to go to black
briefly, followed by a lower pitched beep, and then two higher pitched
beeps. I don't know where the beep codes are documented, but it "sounds"
like it's rejecting the USB drive I have inserted due to being improperly
formatted.