Install ChromiumOS on Samsung ARM Chromebook (snow)

[Patrick Campbell]

Hello,

As Google support of this device has ended I am interested in installing ChromiumOS on it. Is there a specific resource for this device that someone can please point me to?

I did a ChromiumOS build of arm generic board but cannot successfully run it.

Thanks,
Patrick

[Keith I Myers]

What was the name of the board you specified in the build?

--
--
Chromium OS Discussion mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-discuss
---
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-dis...@chromium.org.

--

Keith I Myers http://KMyers.me Mobile : (305)-929-3475

[Patrick Campbell]

I used arm-generic for the build. I mainly interested in setting up the build environment and running through the tutorial I found at the time.

I have since found the power cord and would like to compile and run ChromiumOS on the native emmc if this is possible.

Thanks for your response Keith!

[Keith I Myers]

Of course this can be done. What happens when you specify "snow" as your board?

[Mike Frysinger]

i would strongly recommend not using arm-generic.  unlike x86, the arm world is heavily forked and arm-generic won't include the necessary drivers for your device.

you should use "daisy" as your board instead.

-mike

[Patrick Campbell]

Hi all,

thanks for your responses. Daisy looks to be the correct board name. thanks Mike! It is also documented below.

https://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices

The next issue I run into after trying to build chromiumos are two portage errors.

The following license changes are necessary to proceed:

 (see "package.license" in the portage(5) man page for more details)

# required by virtual/opengles-2-r5::daisy

# required by media-libs/waffle-1.6.0-r11::chromiumos[opengles]

# required by chromeos-base/autotest-tests-graphics-0.0.1-r3219::chromiumos[tests_graphics_SanAngeles]

# required by chromeos-base/autotest-all-0.0.1-r48::chromiumos[-chromeless_tests,-chromeless_tty]

# required by chromeos-base/autotest-all (argument)

>=media-libs/mali-drivers-bin-1.20_p239 Google-TOS

# required by chromeos-base/chromeos-bsp-daisy-0.0.2-r11::daisy

# required by virtual/chromeos-bsp-2::daisy

# required by virtual/target-chromium-os-1-r130::chromiumos

# required by virtual/target-os-1-r3::chromiumos

# required by virtual/target-os (argument)

>=media-libs/mfc-fw-0.0.5-r1 Google-TOS

I have tried to add these into /etc/portage/package.use/ file names that exist in the directory but get the same error.

Any suggestions on how to reslove?

thanks,

Patrick

[Mike Frysinger]

please review the documentation:

  https://dev.chromium.org/chromium-os/licensing/building-a-distro

sorry, we can't offer more advice here than just pointing at that document.

(╯°□°）╯︵ sɹǝʎʍɐl

-mike

--

[Simon Glass]

Hi,

You might find it helpful to check out an old branch from before daisy was removed - perhaps the R75 branch?

Regards,

Simon

[Patrick Campbell]

One more question please.
Encountering the errors below.
error: cros flash failed before completing.
error: device path /mnt/host/source/src/scripts/0 does not exist

This is when following:
http://www.chromium.org/chromium-os/quick-start-guide

This step:
cros_sdk -- cros flash --board=${BOARD} usb://

Thanks,
Patrick

[Patrick Campbell]

Hi Simon,

thanks for the reply.

So my reason for doing this is to have the Chromebook stay updated. Will I be unable to keep it updated in the future if support for the board is removed. Can you confirm that it has been removed as it seems to be working at the moment? Or can I confirm if it still supported? I know google has dropped its support of the Chromebook but I'd like it to live on. Would I be better served by running some Linux variant on it?

[Mike Frysinger]

that's weird.  can you run:

  cros flash --debug --board=${BOARD} usb://

-mike

[Patrick Campbell]

As far as I know the build process finishes with no errors > this command. cros_sdk -- ./build_packages --board=${BOARD}

Below is the error

~/chromiumos$ cros_sdk -- cros flash --debug --board=${BOARD} usb://0
15:38:47: DEBUG: Cache dir lookup.
15:38:47: DEBUG: Configured cache_dir to '/mnt/host/source/.cache'
15:38:47: INFO: Preparing to image the removable device /mnt/host/source/src/scripts/0
15:38:47: DEBUG: RunCommand: lsblk --pairs --output NAME,RM,TYPE,SIZE
15:38:47: ERROR: cros flash failed before completing.
cros: Unhandled exception:
Traceback (most recent call last):
  File "/mnt/host/source/chromite/bin/cros", line 175, in <module>
    DoMain()
  File "/mnt/host/source/chromite/bin/cros", line 171, in DoMain
    commandline.ScriptWrapperMain(FindTarget)
  File "/mnt/host/source/chromite/lib/commandline.py", line 961, in ScriptWrapperMain
    ret = target(argv[1:])
  File "/mnt/host/source/chromite/scripts/cros.py", line 66, in main
    code = _RunSubCommand(subcommand)
  File "/mnt/host/source/chromite/scripts/cros.py", line 51, in _RunSubCommand
    return subcommand.Run()
  File "/mnt/host/source/chromite/cli/cros/cros_flash.py", line 180, in Run
    experimental_au=self.options.experimental_au)
  File "/mnt/host/source/chromite/cli/flash.py", line 599, in Flash
    imager.Run()
  File "/mnt/host/source/chromite/cli/flash.py", line 281, in Run
    raise FlashError('Device path %s does not exist.' % self.device)
chromite.cli.flash.FlashError: Device path /mnt/host/source/src/scripts/0 does not exist.

On Monday, August 19, 2019 at 11:14:25 AM UTC-6, Patrick Campbell wrote:

[Mike Frysinger]

the first command you showed earlier said "usb://" which is what our guide shows, but here you're using "usb://0".  why the 0 ?

-mike

--

[Patrick Campbell]

The usb://0 as opposed to usb:// is because without I am prompted for a number. As I only have one usb plugged in at the moment it is labeled 0 when the selection is presented. I added it as a time saver. Taking it out does not change the result much

~/chromiumos$ cros_sdk -- cros flash --debug --board=${BOARD} usb://

19:51:47: DEBUG: Cache dir lookup.

19:51:47: DEBUG: Configured cache_dir to '/mnt/host/source/.cache'

19:51:47: INFO: Preparing to image the removable device 

19:51:47: DEBUG: RunCommand: lsblk --pairs --output NAME,RM,TYPE,SIZE

19:51:47: DEBUG: RunCommand: lsblk --pairs /dev/sdb --output NAME,RM,TYPE,SIZE

Removable device(s) found. Please select/confirm to continue:

  [0]: SanDisk Firebird USB Flash Drive 14.9G (/dev/sdb)

Please choose an option [0-0]: 0

19:51:50: INFO: [21/Aug/2019:19:51:50] XBUDDY Using shadow config file stored at /mnt/host/source/src/platform/dev/shadow_xbuddy_config.ini

19:51:50: DEBUG: Assuming latest is an xbuddy path.

19:51:50: INFO: [21/Aug/2019:19:51:50] XBUDDY Cannot find /mnt/host/source/src/build/images; skip syncing image registry.

19:51:50: INFO: [21/Aug/2019:19:51:50] XBUDDY Path is latest, location suffix is -release

19:51:50: INFO: [21/Aug/2019:19:51:50] XBUDDY Get artifact 'ANY' with board daisy and version latest'. Locally? True

19:51:50: ERROR: Locating image "latest" failed. The path might not be valid or the image might not exist.

19:51:50: ERROR: To get the latest remote image, please run:

cros flash --board=daisy usb:// remote/latest

19:51:50: ERROR: cros flash failed before completing.

cros: Unhandled exception:

Traceback (most recent call last):

  File "/mnt/host/source/chromite/bin/cros", line 175, in <module>

    DoMain()

  File "/mnt/host/source/chromite/bin/cros", line 171, in DoMain

    commandline.ScriptWrapperMain(FindTarget)

  File "/mnt/host/source/chromite/lib/commandline.py", line 961, in ScriptWrapperMain

    ret = target(argv[1:])

  File "/mnt/host/source/chromite/scripts/cros.py", line 66, in main

    code = _RunSubCommand(subcommand)

  File "/mnt/host/source/chromite/scripts/cros.py", line 51, in _RunSubCommand

    return subcommand.Run()

  File "/mnt/host/source/chromite/cli/cros/cros_flash.py", line 180, in Run

    experimental_au=self.options.experimental_au)

  File "/mnt/host/source/chromite/cli/flash.py", line 599, in Flash

    imager.Run()

  File "/mnt/host/source/chromite/cli/flash.py", line 300, in Run

    image_path = self._GetImagePath()

  File "/mnt/host/source/chromite/cli/flash.py", line 267, in _GetImagePath

    self.image, self.board, static_dir=DEVSERVER_STATIC_DIR)

  File "/mnt/host/source/chromite/lib/dev_server_wrapper.py", line 161, in GetImagePathWithXbuddy

    raise ImagePathError('Cannot locate image %s: %s' % (path, e))

chromite.lib.dev_server_wrapper.ImagePathError: Cannot locate image latest: No builds found for daisy. Did you run build_image?

~/chromiumos$ cros_sdk -- cros flash --board=daisy usb:// remote/latest

Removable device(s) found. Please select/confirm to continue:

  [0]: SanDisk Firebird USB Flash Drive 14.9G (/dev/sdb)

Please choose an option [0-0]: 0

20:22:04: WARNING: GS_ERROR: ServiceException: 401 Anonymous caller does not have storage.objects.get access to chromeos-releases/stable-channel/daisy.

 

20:22:04: ERROR: cros flash failed before completing.

20:22:04: ERROR: return code: 1; command: /mnt/host/source/.cache/common/gsutil_4.41.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' ls -- gs://chromeos-releases/stable-channel/daisy/

ServiceException: 401 Anonymous caller does not have storage.objects.get access to chromeos-releases/stable-channel/daisy.

cmd=['/mnt/host/source/.cache/common/gsutil_4.41.tar.gz/gsutil/gsutil', '-o', 'Boto:num_retries=10', 'ls', '--', 'gs://chromeos-releases/stable-channel/daisy/']

20:22:04: ERROR: (Re-run with --debug for more details.)

I appreciate any help resolving these issues.

thanks,

Patrick

On Monday, August 19, 2019 at 11:14:25 AM UTC-6, Patrick Campbell wrote:

[Mike Frysinger]

if you look at `cros flash --help` you'll see that the URI specification for usb:// is not to enter the numeric position of the discovered devices (which can be dynamic and thus the numbers would change meaning).  you need to pass it the full path to your USB device.

as for the new failure, it is significantly different:

chromite.lib.dev_server_wrapper.ImagePathError: Cannot locate image latest: No builds found for daisy. Did you run build_image?

has build_image finished ?  look under src/build/images/daisy/latest/ and make sure the final image is there.

-mike

--

[Patrick Campbell]

I had not run build_image but thought that i had...Running ChromiumOS 78 from usb. Seems to be working well with the Exception of wifi no wpa2. does not seem to be an option.

Thanks for all the help getting this far!

Patrick

[Mike Frysinger]

no wifi is weird.  i double checked the private overlay and there doesn't seem to be anything missing.

if you get a shell, does `ip a s` show a wifi interface ?  i vaguely recall it being named "mlan0" on that system.  you can check `dmesg` to see if the wifi part was detected correctly.

-mike

--

[Patrick Campbell]

Hey all,

So no wifi issue after all. My pihole was stopping some traffic at the initial login but only when the image was written to the chrome book itself. I dunno it was odd.

So a big thank you for all the help and getting pointed in the right direction. Such great help especially when I've become used to rtfm answers I we the years...

There are still some issues that I don't understand. Mainly getting the image written to the USB as it is in documentation but was able to from the chroot.

Maybe I can figure that out in subsequent builds.

Thanks, 

Patrick

On Monday, August 19, 2019 at 11:14:25 AM UTC-6, Patrick Campbell wrote:

[Mike Frysinger]

glad to hear things are working for you

i just pushed a change to make bluetooth settings public for daisy to ToT, but if you don't use BT, you prob won't care

-mike

--