Thank you and snija for the help.I followed your instructions into my SD card and it is working great. However, a few questions: Can I use cgpt in my Archlinux machine instead of the chromebookOS? I am going to follow the instructions again from my sd card into the emmc, and I was wondering about how to run cgpt from the archlinux build.

tkjacobsen wrote:

snija wrote:There's alignment requirement for the rootfs, does anyone knows the details? I've a 32GB SD card, each time after i tried to change the partition size, it would not boot anyway.

20. The last step is to mark the kernel partitions as known to be god so that the firmware will attempt to use them when you boot up. This marks both partitions as successful, and gives the first partition a priority of 10 and the second a priority of 5. Technically both creating a label and marking as successful aren’t needed but it is good practice.cgpt add -i 1 -S 1 -T 5 -P 10 -l KERN-A /dev/mmcblk1cgpt add -i 2 -S 1 -T 5 -P 5 -l KERN-B /dev/mmcblk1

dutra wrote:Can I use cgpt in my Archlinux machine instead of the chromebookOS? I am going to follow the instructions again from my sd card into the emmc, and I was wondering about how to run cgpt from the archlinux build.

Copy the cgpt binary from the chromeos partition to /usr/bin/ in arch. It's a static executable, there are no external dependencies, so it "just works".

stronnag wrote:Copy the cgpt binary from the chromeos partition to /usr/bin/ in arch. It's a static executable, there are no external dependencies, so it "just works".

Awesome, thank you for the help! And correction: After following the steps, generating chromeos kernel and using it together with archlinuxarm chrome rootfs, mlan0 is not recognized.

Is there a way I can run this command and generate the kernel from archlinux arm chrome instead of chromeos? (Or how else could I fix mlan0?)All I need is to be able to generate an archlinux kernel image by saying /dev/mmcblk0p3 instead of /dev/mmcblk1p3

Edit: I was able to fix it. First I generated the kernel with the above command, but using the vmlinuz obtained from /boot in the package linux-chromebook. Wifi still wasn't recognized, so I manually downloaded and upgraded linux-chromebook and linux-headers-chromebook with pacman -U. After reboot, my mlan0 was up again. I now have a working system with i3. In order to get the battery info working in the i3statusbar, I had to add

I still haven't managed to set up alsa. I copied the files and told it to use the DAISY-I2S profile. I am sure I just have to bring up the volume in some channels in alsamixer, but I am afraid of doing so. Can anyone share what channels are up and what volume?

Can anyone clarify the differences between the image in here under devices/install for the Samsung Chromebook, and the one with imx6 in the filename used in installs referenced here: https://gist.github.com/macton/4632677 and elsewhere? Thanks.

Quick update, the image here under devices/chromebook/install here is just a tad big for a sandisk 8GB SD card. It gunzips to: 8068792320 bytes, a few more than my 79... Sandisk 8GB holds. Hope this helps someone.

[update] dd works, zcat fails (with my card)

dd if=ArchLinuxARM-chromebook-latest.img of=/dev/mmcblkx bs=1M

replace mmcblkx above with your specific device you're writing to - in my dedicated linux notebook it is 0, but in the chromebook, that is internal emmc, so take great care there.

tedm wrote:Can anyone clarify the differences between the image in here under devices/install for the Samsung Chromebook, and the one with imx6 in the filename used in installs referenced here: https://gist.github.com/macton/4632677 and elsewhere? Thanks.

Gary13579 wrote:Can someone please post step by step instructions for getting nv-u-boot working on the SD card? I cannot get it working after spending hours messing with it.

It's still in the works. A few of us have been running eMMC installs with nv-U-boot but I don't know when.

Here is a rough method:

1. Remove the bottom cover (remember there are screws underneath the rubber feet)2. If there is a metallic ring-shaped sticker around the screw hole closest to the USB3 port, remove it.3. Boot Arch from the SD card using the already established method.4. install the flashroom-google package.5. download this file: https://www.dropbox.com/s/6pzvraf3ko14s ... now.bin.gz6. gunzip nv_image-snow.bin.gz7. flashrom -p linux_spi:dev=/dev/spidev1.0 -r original_image-snow.bin8. flashrom -p linux_spi:dev=/dev/spidev1.0 -w nv_image-snow.bin.gz9. Powercycle. Hold down 'a' while powering up to get into a u-boot prompt.

Once you are flashed with u-boot, you will need to create a SD card that boots.I used cgdisk (from gptfdisk package) and created a 16MB ext2 followed by a jfs root.then mkfs.ext2 and mkfs.jfs them. Put vmlinux.uimg from linux-chromebook on the ext2 partition and untar your rootfs to the jfs.Make sure you copy the modules and firmware from linux-chromebook in the proper place on the rootfs.

I'd really prefer not to disable write protection, or overwrite the stock BIOS. But also not sure how to get it working otherwise, as the process is pretty vague in that page.

The chained method is the safest way. But it would make doing an eMMC installation a little bit tricky. Easiest way would be to replace one of the ROOT-X's with an ext2 that contains the kernel, then overwrite the ~12GB private data with an Arch root. That worked for me.

And I agree that flashing over the stock bios is dangerous. However, a bad flash is very inexpensive to fix.