<urjaman>
(Running ARC that i pulled from a veyron-tiger rootfs actually... and like most of that rootfs itself, because i lazie'd out and copied everything that was different and that wasnt obviously not right for speedy... and then in my copying i think i still effed up selinux somehow, so ... SELINUX=permissive and hi play store.. i'll need to figure that out)
<macc24>
:O
<urjaman>
not C100 because the recovery image is one step out from what they serve the devices over auto-updates... so i found this site where i could get a Chrome 84 (same version the last C201 fw) recovery image for the tiger https://cros-updates-serving.appspot.com/
<urjaman>
But also the tiger is even currently getting updates ... (and my grep says the kernel partition still has the dtb for all veyrons, incl. speedy and minnie...)
<macc24>
interesting
<urjaman>
so i'm kinda *thunk* that maybe i could s/tiger/speedy/ to the rootfs and install a newer chromeos on it ... not for too long tho (Feb 2022)
<macc24>
IMO chromeos is less useful than linux on those devices
<macc24>
other than for hardware accelerated video playback
<urjaman>
yeah only for media playback and comms (the webcam and audio) chromeos is pretty good
<macc24>
is webcam better on chromeos?
<macc24>
urjaman: do you want to test some linux stuff on c201pa Soon™?
<urjaman>
well i had trouble with firefox+linux+webcam, but that's mostly a firefox problem
<urjaman>
(that is chromium+linux+webcam worked... but then i need to run a second browser...)
<macc24>
>imagine having a working webcam
<macc24>
this message was brought to you by lenovo chromebook duet gang
<urjaman>
what kind of linux stuff?
<macc24>
cadmium
* urjaman
hasnt googled that yet, tho i've seen you talk about it endlessly
<macc24>
hehe
<macc24>
tldr: a competition for everything else that runs on arm chromebooks with blobs
<urjaman>
but yeah if its an image i can boot with depthcharge off usb (or sd) you can get a test on the 2GB C201
<macc24>
okay
<urjaman>
if i can boot it with u-boot syslinux configuration then i can test with the 4GB "linux" C201 :P
<macc24>
that'd be available in cadmium Soon-ish
<urjaman>
(depthcharge is ... i was gonna say not user-friendly but mostly almost lacks an user-interface..)
<urjaman>
user interface for dummies, but is only enough for dummies
<macc24>
depthcharge is nice for me because it restricts user options so they can't mess up their installation
<macc24>
and it has built-in support for Unbrickable™ kernel updates
<urjaman>
yes that works nice
<macc24>
it only needs some glue to have automatic kernel updates in cadmium :D
<urjaman>
i actually tried to put the '87 chromeos image onto my other partition and boot it (did the prio=highish, tries=1, success=0, so only one try automatically) but i think i forgot to run their post-install thing...
<urjaman>
so the boot failed, but i was able to just turn it off and boot back to the old chromeos
<urjaman>
but yeah why exactly it failed? who knows
<urjaman>
(i know there's some logging internally but still...)
<icecream95>
It's only Unbrickable™ if you read the documentation before using cgpt (source: experience)
<macc24>
icecream95: there's cgpt documentation?
<urjaman>
yeah that part i already remembered :P
<urjaman>
i dunno, there's some random websites that explain the flags ...
<urjaman>
but yeah ChromeOS without ARC is also ChromeOS without selinux which means that to "upgrade" the C201 image needed everything from session_manager, sbin/init, coreutils... and at that point i was like ok everything different
<urjaman>
atleast the kernel config is identical (pulled configs.ko from the tiger image and binwalked the gz out of it to compare lol)
<macc24>
by the way, does anyone know how to piece together and separate a kernel defconfig?
<urjaman>
what do you mean exactly?
<macc24>
i want to be able to separate defconfig into parts that are machine specific, arch specific and distro specific