peterm6881 has joined #Speedsaver
<peterm6881> hey team
<peterm6881> [ 268.341592] FAT-fs (mmcblk0p1): error, clusters badly computed (4618 != 4614)
<peterm6881> thats gonna be damaged or corrupted sd card right?
<Xogium> peterm6881: yes
<peterm6881> hi Xogium
<Xogium> hello
<peterm6881> whats happening in your world?
<Xogium> trying to figure out why my tascam doesn't show up as usb mass storage
<peterm6881> did it show up that way before?
<peterm6881> by the way, did the oled spam killer ever touch the OPi0 repo?
<peterm6881> or was that only ever MangoPi-R3c
<Xogium> only mangopi
<peterm6881> so just need a pull on buildroot-speedsaver-mangopi
<peterm6881> not that it matters, since we had to abandon the F1C200s
<Xogium> mhm
<peterm6881> but it might as well be right
<peterm6881> has our MOS Technology friend appeared?
<Xogium> who's that ?
<Xogium> ah ! Firmware update makes it so you have to go in system then select usb mass storage, select yes, then it shows up. Okay then, if that's how you wanna play it tascam
<peterm6881> :)
<peterm6881> they designed the 6502 microprocessor
<Xogium> ahah
<Xogium> haven't seen him around
<peterm6881> pretty sure its still in production
<peterm6881> question: how is possible that Navit keeps working after the micro sd card is removed?
<Xogium> frankly ? I have no freaking idea. It shouldn't even be possible
<Xogium> maybe because its loaded into ram but the moment it would try ato access files on disk, it would blow up, is my guess
<peterm6881> I'll test it some more tomorrow, on the road
<peterm6881> but yeah, I still got a fix and the screesaver still kicks in after 10 minutes
<peterm6881> screensaver
<Xogium> unless it somehow loads all the maps into memory all at once, but I doubt it, it would consume way too much ram if it did that
<peterm6881> yeah it may be that its garbage
<peterm6881> it just LOOKS like its working. It cant possibly work on the road
<peterm6881> like you said, there's no map
<Xogium> honestly linux shouldn't even let you remove the card lol
<peterm6881> wow sd card is burning at 1.7 Mbps, thats one fucked card
<Xogium> or well it can't help itself if you do that, but… Your whole system should go up like a firework
<peterm6881> thats the first time thats ever happened in years of testing
<Xogium> yep, most likely dying
<Xogium> first sign of dying flash is just that, insanely low speed out of nowhere
<peterm6881> I believe the eMMC will simply connect to the SDC1 header
<peterm6881> since the micro sd card reader slot is physically connected to SDC0
<Xogium> yes it could
<peterm6881> mind you SDC0 is exposed to a pin header as well
<peterm6881> so maybe we could just use that too?
<peterm6881> what do you think?
<peterm6881> keep SDC1 free for tinkering
<Xogium> hmm
<Xogium> I'm not sure
<sc6502> Hey all
<Xogium> oh, hello Steve
<peterm6881> sc6502, my man
<peterm6881> sc6502's ears are burning
<Xogium> hehe
<peterm6881> sc6502, we got our first properly corrupted micro sd card today
<peterm6881> it was crashing constantly. On a positive note, something was smart enough to decide to reboot when it froze
<Xogium> yes, that would be the watchdog
<peterm6881> which i ddint expect
<peterm6881> nice
<peterm6881> Xogium, I used a usb card reader there, instead of the onboard reader built into the NEC, and it burned at normal speed
<Xogium> ah
<sc6502> Bad burn, or bad power cycling when it was being written to ?
<peterm6881> so could be an issue with my 2 usd 3.5" card reader bay
<Xogium> then I'm guessing the corruption was due to the brutal cutting of power. Like I said many times before
<peterm6881> Xogium, if it is that, it took about 4 years :)
<Xogium> then, you got very, very, very lucky in those 4 years
<peterm6881> anyway the moral of this story is, the sooner we can move away from sd cards the better
<Xogium> well there's not just that
<sc6502> To what? Any writing to any medium is liable to trash something in a power fail
<Xogium> eMMC isn't a magic bullet. You need proper handling to avoid data corruption no matter what storage you use
<Xogium> though, I'll say this, eMMC themselves are more reliable than micro sd
<peterm6881> besides, the brutal cutting of power doesnt explain why it was slow to burn. Im confident there was something else going on with that particular card. Besides, brutal cutting of power is inevitable
<peterm6881> errors have gone away. Back on the road tomorrow
<Xogium> yes, which is why I told you many times before that a read-only filesystem combined with protections offered by the eMMC is the only safe way to ensure that data doesn't corrupt
<peterm6881> we now have an opportunity to move to eMMC, at last
<peterm6881> you guys chat, I'll shut up
<Xogium> sc6502: so… if I gave you my work that I did on the lichee pi so far, so you can understand how I did it, would that be useful ? Its based on a similar structure to the orange pi external buildroot tree
<sc6502> Yes, that would be extremely useful - thank you Xogium
<Xogium> sc6502: alright. Would a tarball be good for you ?
<sc6502> Yeah, that should be fine.
<Xogium> sc6502: m'kay, stand by
<peterm6881> let me grab the boot log
<peterm6881> Xogium thinks the partitions may be overlapping and need resized
<Xogium> sc6502: sent via mail
<peterm6881> U-Boot SPL 2022.01 (Apr 21 2022 - 01:20:28 -0400)
<peterm6881> Trying to boot from MMC1
<peterm6881> DRAM: 64 MiB
<peterm6881> U-Boot 2022.01 (Apr 21 2022 - 01:20:28 -0400) Allwinner Technology
<peterm6881> CPU: Allwinner V3s (SUN8I 1681)
<peterm6881> Model: Lichee Pi Zero
<peterm6881> DRAM: 64 MiB
<peterm6881> WDT: Not starting watchdog@1c20ca0
<peterm6881> MMC: mmc@1c0f000: 0
<peterm6881> Loading Environment from FAT... Unable to read "uboot.env" from mmc0:2... In: serial@1c28000
<peterm6881> Out: serial@1c28000
<peterm6881> Err: serial@1c28000
<peterm6881> Net: No ethernet found.
<peterm6881> Hit any key to stop autoboot: 0
<peterm6881> switch to partitions #0, OK
<peterm6881> mmc0 is current device
<peterm6881> Scanning mmc 0:2...
<peterm6881> Found U-Boot script /boot.scr
<peterm6881> 292 bytes read in 1 ms (285.2 KiB/s)
<peterm6881> ## Executing script at 41900000
<peterm6881> Failed to load 'zImage'
<peterm6881> Failed to load 'sun8i-v3s-licheepi-zero-dock.dtb'
<peterm6881> zimage: Bad magic!
<peterm6881> SCRIPT FAILED: continuing...
<peterm6881> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
<peterm6881> Scanning disk mmc@1c0f000.blk...
<peterm6881> Found 4 disks
<peterm6881> No EFI system partition
<peterm6881> BootOrder not defined
<peterm6881> EFI boot manager: Cannot load any image
<peterm6881> No ethernet found.
<peterm6881> missing environment variable: pxeuuid
<peterm6881> Retrieving file: pxelinux.cfg/00000000
<peterm6881> No ethernet found.
<peterm6881> Retrieving file: pxelinux.cfg/0000000
<peterm6881> No ethernet found.
<peterm6881> Retrieving file: pxelinux.cfg/000000
<peterm6881> No ethernet found.
<peterm6881> Retrieving file: pxelinux.cfg/00000
<peterm6881> No ethernet found.
<peterm6881> Retrieving file: pxelinux.cfg/0000
<peterm6881> No ethernet found.
<peterm6881> Retrieving file: pxelinux.cfg/000
<peterm6881> No ethernet found.
<peterm6881> Retrieving file: pxelinux.cfg/00
<peterm6881> No ethernet found.
<peterm6881> Retrieving file: pxelinux.cfg/0
<peterm6881> No ethernet found.
<peterm6881> Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi
<peterm6881> No ethernet found.
<peterm6881> Retrieving file: pxelinux.cfg/default-arm-sunxi
<peterm6881> No ethernet found.
<peterm6881> Retrieving file: pxelinux.cfg/default-arm
<peterm6881> No ethernet found.
<peterm6881> Retrieving file: pxelinux.cfg/default
<peterm6881> No ethernet found.
<peterm6881> Config file not found
<peterm6881> No ethernet found.
<peterm6881> No ethernet found.
<peterm6881> =>
<peterm6881> this is the boot log for Xogiums current image
<peterm6881> exciting times
<peterm6881> heavy, my favourite kind of development
<sc6502> Cheers Xogium :)
<Xogium> sc6502: hope you have fun with it
<peterm6881> Xogium, let me know if you decide to open that box, before you open it. It requires a certain amount of explanation
<peterm6881> and its very fragile
<Xogium> aye, so Simon said
<Xogium> said you had written fragile on the box
<peterm6881> :)
<peterm6881> its more the way I wired it up thats fragile, writing Fragile on the box was primarily so they dont play Pétanque with it
<Xogium> scary
<peterm6881> :)
<peterm6881> sc6502 has gone off to digest your tarball
<peterm6881> is that like a hairball, that cats get?
<peterm6881> I like hairball tea
<Xogium> hehe
<peterm6881> with a nice Paris pun
peterm6881 has quit [Remote host closed the connection]
peterm6881 has joined #Speedsaver