GalliumOS – Lightweight Linux for Chromebooks
galliumos.org
galliumos.org
The 11GB hard drive space I had left after installation was plenty big enough for all the tools and libraries I need, and I added a 64GB SD card for archiving and media.
Since the chromebook (a CB3-131) is so cheap and compact, I take it everywhere, and I wouldn't really care if I lost it or dropped it down the stairs. This confirms my belief that when it comes to buying laptops, one should either go really cheap (<$250) or really expensive ($1000+). There is a no-mans-land between the two where the quality is generally poor but the price is still too high to be blase about your kit.
This contradicts the entry in the HCL. Is this true? Were you able to get your CB3-131 to dual boot?
From the links you provide, it seems there may be a way to use chrx to get dual boot working. Perhaps ask on the reddit? [0]
Honestly though, the limited hard drive space is better given to Linux than ChromeOs.
https://wiki.galliumos.org/Hardware_Compatibility is correct.
https://wiki.galliumos.org/Firmware and https://chrx.org/ have more detailed information.
Make sure you get an Intel chipset chromebook. That's most of them. You won't find much difference in them, other than that.
Here's a life pro tip: This applies to pretty much every product.
what would those be, and why are they specific to this distro?
EDIT: found info at https://wiki.galliumos.org/About_GalliumOS , probably this should be linked in the homepage.
I've used crouton/XUbuntu as my main laptop OS for a couple of years. I've pushed it pretty far, running Steam with a removable SD card to play things like DotA 2 - http://www.aaronbell.com/how-to-run-dota-on-a-chromebook/
Chromebooks are amazingly capable once you add a little storage and update the video drivers.
Not so good when you hand the computer to your brother-in-law to check out a web page, he opens it up
OS VERIFICATION OFF PRESS SPACE TO RE-ENABLE
and of course presses space and wipes your whole environment :(
Yes this was me :(
I actually once built a custom chromiumOS build with kvm enabled and was able run both Android emulator as well as Windows 7 for Office :-) But it proved to be too much of a hassle to rebuild updates over time.
If anyone has had luck with a fully functioning non/ChromeOS let me know what distribution you prefer. Currently I am also considering GalliumOS / NayuOS.
I've read some mixed reviews about using crouton and was curious if it's better to use crouton or to install/flash Linux?
It seems as though crouton could break with ChromeOS updates.
Crouton works just fine with ChromeOS updates it doesn't break anything. Personally I ran into some performance issues as well as native hardware compatibility issues (eg you can only adjust volume in ChromeOS.)you also might not enjoy having to boot ChromeOS before you can get to your Linux environment.
For making a fully functioning desktop, Gallium looks the most promising for your needs.
To get Linux Mint's Debian Edition running on a chromebox. I went that direction because I'm used to Debian on servers, but Mint does a fair amount of work to get a functional/nice desktop.
I did upgrade the Chromebox to 8GB memory and a 128GB SSD. I also had to upgrade the kernel to get a video driver that was stable on the built-in Intel HD graphics.
I recovered ChromeOS and gave the machine away.
If I had to use Chromebook hardware, I'd use crouton.
I personally owe Hugh a debt of gratitude for all the hard work he has done.
Only thing I would like really is better battery life - I get somewhere in the region of 3 hours, but my chromebook is pretty old so...
Once Intel rolled out Atom with the limited hardware mix rules, and MS put XP on life support under a restrictive license, the netbook was basically dead (or at least a shell of its former self).
-It only has 4GB of RAM, but that's been enough up to now. Most builds are I/O bound anyway, and the SSD is fast.
-I don't use an external monitor, as the high pixel density of the screen more than makes up for the small size.
-The 64GB can be limiting, but in some ways its been beneficial, as its forced me to actually pay attention to backups.
-These days, if I have a long-running/high-resource process, I just spin up a VPS and run it there.
I think Google was pretty prescient with the Pixel laptops. When this one isn't enough, I'll be upgrading to the 2015 model.
What's your experience?
If you're on the fence about going native, you should do what I do: install arch on an SD card and boot from that. Good SD cards these days are plenty fast too, and if you like the native system, you can keep using it from the SD card, or use it to install Arch on the SSD. Just make sure you get an SD card with TRIM, and it'll work fine for long-term use.
Resources were pretty limited (dual core Celeron, 2Gb RAM, 32Gb SSD) but it ran fine for most of the things (like normal browsing, js and Python development).
Things you CAN'T do on it:
- Java. Just don't even think about it.
- the former point implies all the Java IDEs (Eclipse, Intellij)
- Android, because of disk space and everything else.
- Games.
Why I loved it: - really small and light
- AMAZING battery life
- having so little disk space made me pay attention to my usage of it, make backups, and move on a server things I didn't really need.
However I upgraded to a Dell XPS 13 since then, life is much much better now :)However, since it's based on Ubuntu 14.04 the kernel and the software versions are a bit old.
In the next months I will switch to Arch or Nix or Void (to have more recent versions) and I may try to port Pantheon on them.
I have a acer c720 with arch installed alongside chromeos on a $50 128GB ssd: http://www.amazon.com/MyDigitalSSD-Super-Cache-Solid-State/d...
All together I spent $150 for a surprisingly performant on the go machine. The battery life is pretty great as well.
There are still a few hiccups with hibernation. Using a tiling WM meant I needed to remap all of the chrome keys to get stuff like brightness and volume working.
I got it refurbished for £120 (~$170) before I set off backpacking in Asia and it's been the perfect laptop. Lightweight and decent battery life.
I do a lot of vector drawing and the trackpad fidelity isn't great, but that's hardly something you can ask for on such a cheap little machine.
http://www.amazon.com/PNY-Elite-Performance-256GB-Speed/dp/B...)
Not a huge UX fail, but something I hoped would be easier
If the computer industry hadn't dropped the ball so badly on laptops I don't think developers would even bother looking at Chromebooks. Ironically written by a part-time dev on a Chromebook.
The Surface Book looks very good. I have stopped laughing at the Surface line of products. If I wasn't so attached to unixy tools and environment I might be tempted. They are a bit pricey here and likely a big risk as far as linux driver support. Apple and Android tablets have also avoided 16:9 though don't enter consideration. Not sure what I could do with a Pixel C or iPad Pro apart from playing Minecraft PE.
You have to wonder what all the laptop makers know that Google, Apple and Microsoft don't. They still insist on putting shiny widescreen television panels in laptops.
I mostly use my chromebook as intended - all chrome apps, even though I have crouton installed. It is quite nice for what it is. I would prefer something more powerful for a daily driver and I think the fact people are looking at linux on chromebooks has a lot to do with the failures of manufacturers to produce what many customers want.
Is this any better? Anyone have experience with both?
Can someone this explain this more?
I was hoping to blow the dust off my original Samsung Chromebook.
People have problems on non-x86 because there's no default replacement for depthcharge that can be made to work with ~0 effort.
Crouton works perfectly, but it would be nice if I could give a Linux distro the full 16GB of eMMC instead of X gigabytes of disk image within the 16GB.
Bonus points if I could dual-boot Android and GalliumOS on an ARM laptop. That would be killer.
I know Google snoops on me, but Google was already snooping on me.
I'd love to be wrong though, so I'd appreciate pointers to any sources.
When it comes to coreboot and libpayload (same tree, really), everything on ChromeOS' main development branches is pushed upstream. depthcharge is a Chrome OS project, so it is its own upstream. Same for ChromeEC.
There are boards that never make it to the main branches - but that doesn't mean that stuff is kept secret, it's just that for firmware, Chrome OS uses separate branches (because things shouldn't change too much in firmware that's in the field). So at some point when the reference design stabilized, a firmware branch is created. Any support for spin-off devices happens in that branch only (because who knows what happened to master in the meantime?).
In general, the branch naming scheme is {firmware,factory}-$board_name-$some_version_number.
For coreboot on veyron (ARM, Rockchip RK3288, firmware all open source with _no_ blobs), the configuration is in https://chromium.googlesource.com/chromiumos/third_party/cor..., for example. Compared to the master branch, they're at a different location - but that's because things moved in master in the meantime (third_party/coreboot/configs used to be the canonical location).
If stuff seems missing, a good place to ask for pointers is #chromium-os on Freenode (but it's a low-volume channel, so please wait for an answer, and maybe repeat the question after a couple of hours).
Disclosure: I work on upstream coreboot and Chrome OS firmware.
The work on third-party firmware is not directly a part of GalliumOS, but the projects are symbiotic. You've probably encountered the folks who focus on firmware in other venues as well.
I know booting arbitrary Linux distros is not a goal of factory firmware builds, but often it's almost there -- just not fully implemented, or not fully tested. If you're in any way involved in keeping that functionality alive, we appreciate it.
It would be interesting to have more information on what exactly it does (regarding the touchpad, at least). Wiki's a bit light on details (or screenshots, by that matter).
That said, it's nice to know this exists - I might try it before upgrading to 16.04 in a couple of months.