C.H.I.P. rides again - maybe
Pocket Popcorn Computer — https://popcorncomputer.com/ — looks like it's relaunching the old C.H.I.P. There might even be a PocketC.H.I.P. with a proper keyboard.
Still have 2 of the CHIPs I never used sitting in my drawer On Sat., Aug. 8, 2020, 9:48 p.m. Stewart C. Russell via talk, < talk@gtalug.org> wrote:
Pocket Popcorn Computer — https://popcorncomputer.com/ — looks like it's relaunching the old C.H.I.P.
There might even be a PocketC.H.I.P. with a proper keyboard.
--- Post to this mailing list talk@gtalug.org Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
On 2020-08-08 10:48 p.m., Digiital aka David wrote:
Still have 2 of the CHIPs I never used sitting in my drawer
Something I'm discovering about mine: NextThingCo did a terrible job of managing the flash memory allocation, so running the device for any amount of time will get you warnings and errors such as: ubi0: fixable bit-flip detected at PEB 142 ubi0: scrubbed PEB 142, data moved to PEB 1796 ubi0 warning: ubi_eba_atomic_leb_change: LEB 0:1 changed from full to partially-written state! ubi0 warning: ubi_eba_atomic_leb_change: LEB 0:2 changed from full to partially-written state! Also, it seems that this is the *second* attempt for the Pocket Popcorn at a launch. They tried last year and never got off the ground. cheers, Stewart
| From: Stewart C. Russell via talk <talk@gtalug.org> | Something I'm discovering about mine: NextThingCo did a terrible job of | managing the flash memory allocation, so running the device for any amount of | time will get you warnings and errors such as: | | ubi0: fixable bit-flip detected at PEB 142 | ubi0: scrubbed PEB 142, data moved to PEB 1796 | ubi0 warning: ubi_eba_atomic_leb_change: LEB 0:1 changed from full to | partially-written state! | ubi0 warning: ubi_eba_atomic_leb_change: LEB 0:2 changed from full to | partially-written state!
"UBIFS is a flash file system for unmanaged flash memory devices. UBIFS works on top of a UBI layer, which is itself on top of a memory technology device layer." Wow. They didn't use an eMMC memory, just raw flash? That takes guts. Would this bug not be in the Linux kernel rather than due to something added by NextThingCo? Is it possible to build and install a new kernel to fix this?
participants (3)
-
D. Hugh Redelmeier -
Digiital aka David -
Stewart C. Russell