![]() ![]() Updates on the ARM with this boot_signed_only off, at least in the devĬhannel. On Mon, at 5:34 PM, tedm I also get regular To use a couple of different people's images in the early days with myĬr-48, mostly Todd Vierling's builds which were pretty nice but I haven'tĮxperimented with anything since those went away. Most success using the Chromebook imageburner - chrome://imageburner/. Don't know which method you're using but I've had the Using anything bigger or more expensive since it's only good for one thing Inexpensive 4GB usb sticks I picked up at Microcenter, there's no sense in Great for ChrUbuntu, but it would totally break Chromium - I've had problems with SD cards also and have just reverted to some Ksplice works well for tiny changes like security updates, but the kernels for Chromium OS and Ubuntu are quite The linux-chromebook package in Ubuntu provides a kernel for the ARM Chromebook. Ksplice is a good idea, but probably not feasible for crouton. This will open the Chrome OS Image Burner. Once the SD card is inserted, you need to open the Chrome browser and type chrome://imageburner into the address bar. Maybe it could even be automated in the future! Those newfangled computers, they can do anything. The first thing you need to do is insert the SD card into the Chromebook. I think I'm going to write a wiki page sometime soon that provides a guide to building modules for advanced users. Still, there are lots of good reasons to want to mess with the kernel. And if the rootfs is modified in any way, the only way to get back to normal Chrome OS with autoupdates is to go through the recovery process. Disabling rootfs verification means that any remaining shred of security is gone, and, more annoyingly, no more Chrome OS autoupdates. This has been a big pain for a lot of people (myself included), and there's been some discussion of how to do this properly (see #266)Ĭhromium OS won't allow kernel module loading without disabling rootfs verification. ![]()
0 Comments
Leave a Reply. |