...basically, I have "nerd cred" and run linux on my desktop, but for my laptop I wanted: disposable (no leaky hard drive), zero maintenance (no kernel modules for sound drivers), battery-portable.
90% of the time I'm wanting `vim` + `git` + `ssh`, and 20% of the time i'm wanting to run some random stuff locally. Chromebook is basically zero friction and 1/10th the price (and 1/10th the capabilities) of a "very nice mac laptop", plus you can pop into a very capable linux VM (w/ passthrough GUI support) without a lot of ceremony.
Windows laptops are out of the question, and pure linux laptops (until only very recently) were of marginal support and low battery capabilities (especially "close it and stuff it in a backpack for 3 days").
"""last week: Pop!_OS 22.04: kernel 6.17.9-76061709 — module BTF validation cascade boots system to emergency mode #3961
Thanks for taking a look,
Quick update — I'd already recovered before seeing this comment. The path that worked: boot Pop_OS-oldkern, run sudo apt install --reinstall linux-image-6.17.9-76061709-generic linux-modules-6.17.9-76061709-generic && sudo kernelstub, reboot. 6.17.9 came up clean. The reinstall's postinst hooks ran update-initramfs automatically; /boot/initrd.img-6.17.{4,9}-* are both freshly dated 2026-05-06 (~11:44 / 11:46), and kernelstub copied them to the EFI partition. Verified: journalctl -k -b 0 | grep -iE 'btf|failed to validate' | wc -l → 0.
"""
In the year 2026, on my Linux laptop (T14, Linux 6.18.26) I ran the following:
lsmod | cut -f 1 -d ' ' | grep snd | wc -l
And it responded: 53. Fifty three kernel modules are dedicated to sound. I, of course, never had to install any of them by hand, or take any other direct care.
> Windows laptops are out of the question, and pure linux laptops (until only very recently) were of marginal support and low battery capabilities (especially "close it and stuff it in a backpack for 3 days").
Dell has sold laptops with first-party Linux support for nearly fifteen years, to say nothing of other smaller OEMS.
As for the battery issues during sleep: that actually has to do with a combination of the BIOS settings + downstream ramifications of secure boot (and how the old-fashioned "hibernate" used to work). Unfortunately, that isn't specific to Linux. My MBP has the same problem, and so do the same laptops running Windows.
Chromebooks make a pretty nice, Linux friendly machine. They're usually cost optimized given the market they address, but that's fine if it fits your needs. Sometimes they have "weird" hardware, keyboard/mouse controllers and stuff at least wasn't always "pc standard", audio controllers seem to be commonly outside mainstream as well.
It's nice to run Linux on a machine that was built to run Linux. No silly windows key, no fighting with firmware that was built for windows first. I have a Chromebox that was a great mini desktop and the pricing was nice. My first Chromebook ran FreeBSD pretty well once it was no longer needed for ChromeOS, etc.
You have to shop carefully, you want something that's easy to put a MrChromebox firmware on and doesn't have any known issues with the OS you want to run. It's been a while since I purchased a ChromeOS device and the current state is different than it was then; I'm not sure how easy it is to find reasonable options now, but there were plenty of good options in the past. You also want to be sure that it has enough ram and storage for you needs or that those are expandable, but I think soldering ram and storage is pretty common across the range.
The number of people who have "installed linux" other than ChromeOS on a Chromebook is probably in the low single digits, while the ChromeOS installed user base is in the hundreds of millions. For any given thing someone is going to try to put linux on that thing, but it is not a common use case for Chromebooks that we need to discuss.
This is actually the perfect detail to discuss. ChromeOS printing is literally just CUPS, so it has the same functionality as any other Linux distro. If you have a modern IPP printer on a normal home Wi-Fi, you can expect it to just work. This covers most people's needs.
Where ChromeOS shines is that it has never been affected by severe and numerous CUPS security vulnerabilities like CVEs 2024-47175 through 2024-47177, which were unauthenticated remote vulnerabilities, while Ubuntu and Fedora (and all other major distros) were affected. Why? ChromeOS sandboxes the hell out of these kinds of subsystems. CUPS runs in a PID namespace, network namespace, mount namespace, on a read-only filesystem, with seccomp filters. It cannot use the network, ever. It can only communicate over a pipe with a network proxy. The proxy is only active if and when a user tries to print. The proxy is also in a seccomp jail that prevents it from doing anything except enumerated network traffic and the pipe. The proxy is written in a safer language than CUPS itself, and protects CUPS from malformed, malicious inputs by validating both PPDs and print requests.
With ChromeOS you get both.
I have used Linux for 20 years, but only for development, and I will only develop on Linux.
For everything else (email, files, photos), I want a browser. Used to be Mac/Osx, but got tired of being managed by it.
Just my preference. You can do everything on Linux, just never felt comfortable with it.
You want a browser for files?
b/c you don't have to think about the operating system and updates. I posted about my experience here: https://news.ycombinator.com/item?id=48051902
...basically, I have "nerd cred" and run linux on my desktop, but for my laptop I wanted: disposable (no leaky hard drive), zero maintenance (no kernel modules for sound drivers), battery-portable.
90% of the time I'm wanting `vim` + `git` + `ssh`, and 20% of the time i'm wanting to run some random stuff locally. Chromebook is basically zero friction and 1/10th the price (and 1/10th the capabilities) of a "very nice mac laptop", plus you can pop into a very capable linux VM (w/ passthrough GUI support) without a lot of ceremony.
Windows laptops are out of the question, and pure linux laptops (until only very recently) were of marginal support and low battery capabilities (especially "close it and stuff it in a backpack for 3 days").
> (no kernel modules for sound drivers)
What century did you write this in?
https://github.com/pop-os/pop/issues/3961
"""last week: Pop!_OS 22.04: kernel 6.17.9-76061709 — module BTF validation cascade boots system to emergency mode #3961
Thanks for taking a look,
Quick update — I'd already recovered before seeing this comment. The path that worked: boot Pop_OS-oldkern, run sudo apt install --reinstall linux-image-6.17.9-76061709-generic linux-modules-6.17.9-76061709-generic && sudo kernelstub, reboot. 6.17.9 came up clean. The reinstall's postinst hooks ran update-initramfs automatically; /boot/initrd.img-6.17.{4,9}-* are both freshly dated 2026-05-06 (~11:44 / 11:46), and kernelstub copied them to the EFI partition. Verified: journalctl -k -b 0 | grep -iE 'btf|failed to validate' | wc -l → 0. """
In the year 2026, on my Linux laptop (T14, Linux 6.18.26) I ran the following:
And it responded: 53. Fifty three kernel modules are dedicated to sound. I, of course, never had to install any of them by hand, or take any other direct care.
1 reply →
> Windows laptops are out of the question, and pure linux laptops (until only very recently) were of marginal support and low battery capabilities (especially "close it and stuff it in a backpack for 3 days").
Dell has sold laptops with first-party Linux support for nearly fifteen years, to say nothing of other smaller OEMS.
As for the battery issues during sleep: that actually has to do with a combination of the BIOS settings + downstream ramifications of secure boot (and how the old-fashioned "hibernate" used to work). Unfortunately, that isn't specific to Linux. My MBP has the same problem, and so do the same laptops running Windows.
ChromeOS is linux. It's a Linux distro that works correctly out of the box, setting it apart quite strongly from all other Linux distros.
Then why do people install Linux in Chrome books?
Chromebooks make a pretty nice, Linux friendly machine. They're usually cost optimized given the market they address, but that's fine if it fits your needs. Sometimes they have "weird" hardware, keyboard/mouse controllers and stuff at least wasn't always "pc standard", audio controllers seem to be commonly outside mainstream as well.
It's nice to run Linux on a machine that was built to run Linux. No silly windows key, no fighting with firmware that was built for windows first. I have a Chromebox that was a great mini desktop and the pricing was nice. My first Chromebook ran FreeBSD pretty well once it was no longer needed for ChromeOS, etc.
You have to shop carefully, you want something that's easy to put a MrChromebox firmware on and doesn't have any known issues with the OS you want to run. It's been a while since I purchased a ChromeOS device and the current state is different than it was then; I'm not sure how easy it is to find reasonable options now, but there were plenty of good options in the past. You also want to be sure that it has enough ram and storage for you needs or that those are expandable, but I think soldering ram and storage is pretty common across the range.
Crostini is kind of a joke, but I use it to remote into real Linux boxes. For me, best of both worlds.
The number of people who have "installed linux" other than ChromeOS on a Chromebook is probably in the low single digits, while the ChromeOS installed user base is in the hundreds of millions. For any given thing someone is going to try to put linux on that thing, but it is not a common use case for Chromebooks that we need to discuss.
11 replies →
"Works" is kind of generous. Try connecting a printer for example.
Having very recently (and unsuccessfully) tried to connect a printer to "real" Linux, that's not really a relevant point against ChromeOS.
In the end, after hours of frustration, my solution was to print the document from my (amusingly, Google Pixel Android) phone.
This is actually the perfect detail to discuss. ChromeOS printing is literally just CUPS, so it has the same functionality as any other Linux distro. If you have a modern IPP printer on a normal home Wi-Fi, you can expect it to just work. This covers most people's needs.
Where ChromeOS shines is that it has never been affected by severe and numerous CUPS security vulnerabilities like CVEs 2024-47175 through 2024-47177, which were unauthenticated remote vulnerabilities, while Ubuntu and Fedora (and all other major distros) were affected. Why? ChromeOS sandboxes the hell out of these kinds of subsystems. CUPS runs in a PID namespace, network namespace, mount namespace, on a read-only filesystem, with seccomp filters. It cannot use the network, ever. It can only communicate over a pipe with a network proxy. The proxy is only active if and when a user tries to print. The proxy is also in a seccomp jail that prevents it from doing anything except enumerated network traffic and the pipe. The proxy is written in a safer language than CUPS itself, and protects CUPS from malformed, malicious inputs by validating both PPDs and print requests.
1 reply →