Was going to title that the install was broken, but I'm a complete newbie, so that might be a bit pretentious. I've been trying to use arch linux on my chromebook with a desktop environment, but I can't the install to properly boot. Some problems I've been having with the provided instructions (apologize for my bad forum etiquette and organization):
https://archlinuxarm.org/platforms/armv ... ebook-plus
1. Tar/BSDtar - the instructions use the tar command, which throws some nonfatal errors in crosh shell, but I read elsewhere that the bsdtar command should be used, and it extracts without the errors. Is this necessary/correct?
2. With the default tarball (http://os.archlinuxarm.org/os/ArchLinux ... est.tar.gz), the kernel is too large. There are some other posts from last year about this, but following the instructions, copying the kernel brings up a storage error, leaving it incomplete and unbootable (using control-u). I think it is a 32 mb limit. I saw some fixes for users who were updating their installs, but I couldn't really understand how to apply/patch to the install.
3. Trouble with gru-latest - with the tarball (http://os.archlinuxarm.org/os/ArchLinux ... est.tar.gz) used with the Asus Chromebook Flip C101PA (https://archlinuxarm.org/platforms/armv ... lip-c101pa), which has the same rockchip cpu and gpu, control-U works, but I get an unchanging blank screen and have to shut down and restart chrome os with the power button. I checked vmlinux.kpart, which was 21.9 mb, and I don't get the size error with the dd command. I don't know if it's frozen, or something's wrong with the display driver, but from other posts I've seen, it's probably the latter, hence the different tarballs for the Asus and Samsung.
Maybe the kernel trimming was only applied to the Asus and hasn't been for the Samsung download? I'm sorry, but I'm stumped. I also had some trouble with the USB, and only ended up passing control-u boot with my microsd, but I think that's down to using the default tarball.