justin = {
main feed
,
music
,
code
= {
cockos
,
reaper
,
wdl
,
ninjam
,
jsfx
,
more
}
,
askjf
,
pubkey
};
Ask Justin Frankel
No reasonable question unanswered since 2009!
Suggested topics: programming, music, sleep, coffee, etc.
Note: please do not ask questions about REAPER features, bugs or scheduling, use the
forums
instead.
Name:
Ask:
Human (enter yes):
[
back to index
] | [
unreplied
] | [
replied
] | [
recent comments
] | [
all
]
Question:
What was the last thing that frustrated you?
Asked by Will (99.100.219.x) on May 24 2026, 2:11am
Reply on May 24 2026, 3:05am:
I have an old arm chromebook. At some point I was annoyed that google stopped updating chromeOS for it, so a couple of years ago I opened it up to enable firmware writing, put libreboot on it. then getting a working mainline linux kernel working on it was a pain, ended up using postmarketOS for a bit. but it sucked. and it was a lot slower (to build a debug build of reaper was like 6 minutes, vs 3 minutes on chromeos/crouton). the other day I decided I would put chromeos back, so I rewrote the firmware with the default depthcharge one I had saved. (turns out, side note, that the hardware switch to enable firmware writing actually enables toggling of write-protect... so even though I put the hardware switch back on, my firmware was left not write protected. but anyway). I went to go restore the chromeos with the default boot loader, but it failed "unexpected error" every time. I tried all of the troubleshooting steps the web could give me. no worky. I figured it might be due to my firmware not being write protected. but I couldn't change the write protection without booting, even if I opened the laptop up. so I kept playing with it again today, and realized while it was restoring the system, you could switch virtual terminals and see what was happening. anyway, at some point, it detects that it can write firmware, and then tries to update the firmware. and then fails, and restores the system back to the state it found it (even thought it had successfully written all of the partitions). so, I finally got it it work by turning the system off right as it was about to update the firmware. Was pretty frustrating for a while, but I avoided having to toss this thing, which is still useful (small light laptop that I can toss around without having to worry about, etc).
Comment:
Your Name:
-- Site Owner's Name:
(for human-verification) Comment:
[
back to index
] | [
unreplied
] | [
replied
] | [
recent comments
] | [
all
]
Copyright 2026 Justin Frankel
.
|
RSS