Unable to install!

[Chris J]

I have downloaded from both sites:-

http://chromeos.hexxeh.net/

http://chromium.arnoldthebat.co.uk/index.php

After unzipping with 7-zip one produces a .bin file and the other a .img both the same size

Write to USB drive with Win32 disk imager

In several different machines only boots for a few seconds to Chromium image or blank screen.

No further activity for several minutes then occasional flashes

Ctrl Alt F2 to dev console

login chronos

run /usr/sbin/chromeos-install

error message -

initctl: unknown instance

Error: can not determine destination device. specify --dst yourself

Same on several computers with different disks.

Is there supposed to be a way to boot to a live session like the original Chrome OS and other Linux?

Is it normal for the disk image to produce 12 partitions on the USB device?

What am I doing wrong?

Chris

[Kingdon Barrett]

"specify --dst yourself" is the important line to note

If you know which device is the disk you want to wipe (it should not be a removable disk), specify it carefully using the --dst option

If you didn't get a live session though, chances are not good that anything desirable will result from installing the system onto the hard disk.  (In other words, the USB is indeed supposed to boot to a live session.  You should have seen "chromium" boot screen, followed by wifi selection prompt and login screen... if not, your hardware is either not supported or not well supported.)

Yes, 12 partitions is normal.  ChromeOS has a complicated GPT disk layout to make automatic updating stateless and easily revertible.

I tried this myself today, with a Thinkpad x220, I had good results after installing ArnoldTheBat's "Special Build" -- working wifi, sound, power management, some quirks updating (it seemed to try updating every time I checked for an update, stuff broke, until I followed the instructions completely and issued a "stateful_update" command... that seemed to fix it) -- no graphical problems with the special build, except for immediately following an update, when the system glitched out a bit and crashed on me.

I tried with the nightly build for amd64 after, and predictably, I was not able to get on any wireless networks (no linux-firmware package in the nightly build, just stock chromium os).  But overall, it seemed to be working except for that.

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

[Chris J]

The three computers which failed to boot correctly from the USB drive were all AMD powered. I forgot I had a Celeron box so tried that and it fully boots to Live Chromium.

Thanks for the advice. I will give some of the Special builds a try and see if any work on my AMD boxes.

If not then there are plenty of other Linux distros to try like Lubuntu which I already use.

Chris

[Kingdon Barrett]

I came to Chromium OS because of an annoying crash bug (that, incidentally, I don't see on my AMD-powered machines... maybe I'm not using them enough)

https://bugs.chromium.org/p/chromium/issues/detail?id=381732

The crashes I've had so far on Chromium are slightly more annoying, so...

Have switched back to Debian with Gnome, this issue has affected me in Chrome and Chromium, all versions, on several different hardware platforms.  This time I tried the "garden path" non-free installer that works with my laptop available at http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/

--

[Andrew Wright]

If you're still interested, current builds of stock unmodified Chromium OS work almost perfectly on any x220 running Coreboot firmware. I'm referring to self-built Chromium OS installed on a hard drive, and not pre-made builds. The main remaining issue seems to be that if you close the lid without locking the screen it generally won't be there when you open it back up.