For current releases of ChromeOS, crouton cannot be installed. It has been broken for me since 126.0.6478.252. There appears to be no fix for this. I suggest you move to Crostini or dual boot.
You can revert back to an earlier version of ChromeOS, but when your Chromebook updates, crouton will be broken again.
And now, even attempting to install crouton will mess up your Chromebook so that the brightness keys no longer work, and the power settings are lost, requiring a powerwash to set things aright again.
I have been quite happy with Crostini to be honest, despite its limitations. For the long term I bougt a Suzy-Q cable and will consider dual boot at some point.
Why do you care? Crouton was useful to lots of people in the past. Now we have Crostini, but it has some severe limitations. At least you can still dual boot using the MrChromebox BIOS patch.
My bad, I didn't meant to offend you... I'm actually care, like a lot... The reason I asked so rude is because for long time I can't get clear understanding what was so special in crouton that everyone craves it after years of being stale.
So why it's important for me and why I care... when I got my first chromebook (aarch64)
I quickly realised two things: linux subsystem is very limited for anything beyond fiddling, it's very barebones and unoptimized which I consider a crime when laptop is only 4GB worth of memory (termina itself just eats 1.2gb even without penguin running/existing)
So I started looking for ways of using linux more natively, I
I checked how crouton works, it failed on my device..
I started learning how things are operating in chromeos and made a few working prototypes which are a ton better than official solution, but not crouton because I don't know the use-case...
My solutions are:
==USING VM==
create your personal container and run it in crosvm directly or run penguin directly (it will boot in 7 second and consume only 100mb of ram)
It's probably the most reliable and potentially require less maintenance in the future.
==USING LIGHTWEIGHT CONTAINER RUNTIME==
(docker, etc is out of the game as kernel is modified in the way all container runtimes fail due to security patches or incorrect setup of cgroups)
implement lightweight command like bubblewrap to run container in isolation from the host, the isolation is minimal and mostly for convinience (like you don't need to cleanup chroot mounts). user/processes/network/ipc is shared with host, only filesystem is unshared
No performance overhead, can be done in a way that it require 0 processes running in background.
Someone may say it insecure, I think it's fine.
That way I was able to run alpine and use it like a full blown dev toolkit, I even compiled my own sommelier that way.
Minuses also you are forced to be with chromeos kernel.
Bootstraps in 10 seconds!
SO...
My question how gui is important in crouton? How full desktop gui is important? (I assume crouton run whole desktop environment) How was the performance? Why it's important if it's important :)
I wish I understood more about containers. It's frustrating to me that a Chromebook has so much potential, yet there is limited documentation about what you're doing. Installing Crostini is easy, but it's not the only thing you can do. Thanks for your feedback.
Back in the day, when crouton actually worked, I could setup a MIDI workstation and rip CDs and DVDs, neither of which you can do in Crostini.
It's been dead for a bit dude.
Well, for awhile, there were some work-arounds, but now I can't even install the core target.
Damn this is sad, this used to be the best way to use my pixel book
I know. There used to be some work-arounds but now you can't even install the core target.
that is sad, i was just about to breathe new life in my EOL chromebook without resorting to https://docs.mrchromebox.tech/docs/supported-devices.html
You can revert back to an earlier version of ChromeOS, but when your Chromebook updates, crouton will be broken again.
And now, even attempting to install crouton will mess up your Chromebook so that the brightness keys no longer work, and the power settings are lost, requiring a powerwash to set things aright again.
You can install Linux on a thumb drive and dual boot. It won't run as fast, but it's pretty good.
I have been quite happy with Crostini to be honest, despite its limitations. For the long term I bougt a Suzy-Q cable and will consider dual boot at some point.
Can you explain the purpose of a Suzy-Q cable? I've read that they're really hard to find online.
The SuzyQ cable can be used to remove the write protection on the bootloader and install a custom BIOS/UEFI. See: https://docs.mrchromebox.tech/docs/firmware/wp/disabling.html
Thanks
why do you need this crap?
Why do you care? Crouton was useful to lots of people in the past. Now we have Crostini, but it has some severe limitations. At least you can still dual boot using the MrChromebox BIOS patch.
My bad, I didn't meant to offend you... I'm actually care, like a lot... The reason I asked so rude is because for long time I can't get clear understanding what was so special in crouton that everyone craves it after years of being stale.
So why it's important for me and why I care... when I got my first chromebook (aarch64)
I quickly realised two things: linux subsystem is very limited for anything beyond fiddling, it's very barebones and unoptimized which I consider a crime when laptop is only 4GB worth of memory (termina itself just eats 1.2gb even without penguin running/existing)
So I started looking for ways of using linux more natively, I
I checked how crouton works, it failed on my device..
I started learning how things are operating in chromeos and made a few working prototypes which are a ton better than official solution, but not crouton because I don't know the use-case...
My solutions are:
==USING VM== create your personal container and run it in crosvm directly or run penguin directly (it will boot in 7 second and consume only 100mb of ram)
It's probably the most reliable and potentially require less maintenance in the future.
==USING LIGHTWEIGHT CONTAINER RUNTIME== (docker, etc is out of the game as kernel is modified in the way all container runtimes fail due to security patches or incorrect setup of cgroups)
implement lightweight command like bubblewrap to run container in isolation from the host, the isolation is minimal and mostly for convinience (like you don't need to cleanup chroot mounts). user/processes/network/ipc is shared with host, only filesystem is unshared
No performance overhead, can be done in a way that it require 0 processes running in background.
Someone may say it insecure, I think it's fine.
That way I was able to run alpine and use it like a full blown dev toolkit, I even compiled my own sommelier that way.
Minuses also you are forced to be with chromeos kernel.
Bootstraps in 10 seconds!
SO...
My question how gui is important in crouton? How full desktop gui is important? (I assume crouton run whole desktop environment) How was the performance? Why it's important if it's important :)
Crouton had really good performance and integrated really well into ChromeOS despite basically being a full distro
Crouton had really good performance and integrated really well into ChromeOS despite basically being a full distro
I wish I understood more about containers. It's frustrating to me that a Chromebook has so much potential, yet there is limited documentation about what you're doing. Installing Crostini is easy, but it's not the only thing you can do. Thanks for your feedback.
Back in the day, when crouton actually worked, I could setup a MIDI workstation and rip CDs and DVDs, neither of which you can do in Crostini.
here is first attempt to run chroot in isolated environment https://github.com/s1gnate-sync/sideroot
Interesting!
running minimal docker os in crosvm
https://gist.github.com/s1gnate-sync/2b17ffb4cfc21a764f784370c61c4fb2
I'm interested in what you're doing, but this is way over my head at this time.
here is #2 https://github.com/s1gnate-sync/chromeos-devsuite
it also fixes issue with sudo and crosh