<Armbian-Discord> <T​enkawa> the module is there but yeah no binding
<Armbian-Discord> <A​oyfe> Let me find the one unit I haven't destroy pboot on
<Armbian-Discord> <r​pardini> yep, see if you can get find the jedec id from petitboot dmesg
<Armbian-Discord> <A​oyfe> Ok how do I get this out of pboot?
<Armbian-Discord> <A​oyfe> It's busybox.
<Armbian-Discord> <r​pardini> make it drop to a shell
<Armbian-Discord> <r​pardini> dmesg | grep nor and such
<Armbian-Discord> <A​oyfe> Yeah already there. 😛
<Armbian-Discord> <r​pardini> or dmesg | grep jedec
<Armbian-Discord> <r​pardini> etc
<Armbian-Discord> <A​oyfe> Wait, pboot is vanilla unmodified 4.9?
<Armbian-Discord> <r​pardini> grep -i maybe
<Armbian-Discord> <r​pardini> oh god, no, I will repeat. petitboot == vendor kernel
<Armbian-Discord> <r​pardini> can't stress enough.
<Armbian-Discord> <A​oyfe> Then they suck at versioning.
<Armbian-Discord> <r​pardini> dmesg | grep -C 5 spi-nor
<Armbian-Discord> <r​pardini> get that ID, man.
<Armbian-Discord> <A​oyfe> xt25f128b
<Armbian-Discord> <r​pardini> that's what I already had in before.
<Armbian-Discord> <r​pardini> { "xt25f128b", INFO(0x0b4018, 0, 64 * 1024, 256) } since years ago.
<Armbian-Discord> <A​oyfe> ¯_(ツ)_/¯
<Armbian-Discord> <A​oyfe> Would this potentially get caused if I only partly wiped pboot?
<Armbian-Discord> <A​oyfe> Though I'm pressing that stupid button, so bypassing the SPI must be working
<Armbian-Discord> <A​oyfe> Because it just hangs there forever on the other units where I erased SPI.
<Armbian-Discord> <r​pardini> again, I'm anti-Petitboot, so, no idea.
<Armbian-Discord> <A​oyfe> You want me to try to boot HK Ubuntu and see what's up?
<Armbian-Discord> <r​pardini> HK Ubuntu will be the same. You might just be able to flash mtd1 from there and be done with it
<Armbian-Discord> <A​oyfe> The u-boot image doesn't fit because of the partitioning
<Armbian-Discord> <r​pardini> still, Armbian-wise, I'm still left with "non-working mtd in some machines" which makes me unhappy
<Armbian-Discord> <r​pardini> that said, I've wasted enough time 😉
<Armbian-Discord> <r​pardini> I just copied ID's from vendor kernel, while the driver proper is completely different.
<Armbian-Discord> <A​oyfe> Should I be safe to assume that the mtd partitions exposed by pboot are adjacent and that I can just write the max # of bytes to each partition or is that a bad assumption?
<Armbian-Discord> <r​pardini> the (hex) math is right there on screen.
<Armbian-Discord> <r​pardini> using some utility will also let you write and ignore the partitions, I think.
<Armbian-Discord> <A​oyfe> I suppose I can also just write using dd and hex math for 4Ki blocks
<Armbian-Discord> <M​anoftheSea> Might want to check that dtb doesn't have (now wrong) partitioning ingot
<Armbian-Discord> <A​oyfe> So I think the problem here is that the momentary switch actually "turns off" or masks the SPI
<Armbian-Discord> <A​oyfe> Because I was able to boot the pboot from an sdcard and it came up with no mtd
<Armbian-Discord> <r​pardini> heh. that makes sense.
<Armbian-Discord> <r​pardini> so NO BUTTON then
<Armbian-Discord> <A​oyfe> Right but I can't boot Armbian from pboot?
<Armbian-Discord> <r​pardini> no, but you can wipe pboot from itself
<Armbian-Discord> <A​oyfe> So I guess I'm stuck flashing u-boot from HK Ubuntu or pboot
<Armbian-Discord> <A​oyfe> If I wipe pboot from itself, then it just hangs forever, I think.
<Armbian-Discord> <A​oyfe> Lemme try it now
<Armbian-Discord> <r​pardini> no, wipe it from itself, then boot Armbian from SD, sans-button.
<Armbian-Discord> <r​pardini> what a gigantic waste of time if it boils down to button. it's my fault -- a true thinko.
<Armbian-Discord> <r​pardini> 🤦‍♂️
<Armbian-Discord> <A​oyfe> lol, every guide everywhere says to do it.
<Armbian-Discord> <r​pardini> no, the sole purpose of the button is to mask the MTD
<Armbian-Discord> <r​pardini> of course it doesn't work.
<Armbian-Discord> <A​oyfe> Ok, doing flash_eraseall /dev/mtd{0,1,2,3}
<Armbian-Discord> <A​oyfe> Which is theoretically supposed to zero out each of the mtd partitions
<Armbian-Discord> <r​pardini> yep, official method.
<Armbian-Discord> <A​oyfe> I'm pretty sure we're here because of "official methods" and "official documentation".
<Armbian-Discord> <A​oyfe> Hence "theoretically" 😛
<Armbian-Discord> <A​oyfe> My cynicism setting is currently at medium. Feel free to tell me to turn it down. 😉
<Armbian-Discord> <r​pardini> lol don't worry
<Armbian-Discord> <A​oyfe> OK, looks like it's booting from the from the sdcard
<Armbian-Discord> <A​oyfe> Stuck on blinking cursor.
<Armbian-Discord> <A​oyfe> But I assume that's because emmc is slowwwwW
<Armbian-Discord> <r​pardini> my builds spew console on ttyAML0
<Armbian-Discord> <r​pardini> not HDMI etc
<Armbian-Discord> <r​pardini> did you buy the HK UART thingy yet ?
<Armbian-Discord> <A​oyfe> No. I'm hoping to never need to do that. 😛
<Armbian-Discord> <A​oyfe> Yep, I get the option for mtd flash
<Armbian-Discord> <r​pardini> 🤦‍♂️
<Armbian-Discord> <A​oyfe> Mystery solved.
<Armbian-Discord> <r​pardini> !@&&!*#!@
<Armbian-Discord> <r​pardini> damn
<Armbian-Discord> <r​pardini> so sorry man, was a real thinko.
<Armbian-Discord> <A​oyfe> What's to be sorry about? I learned a shitload.
<Armbian-Discord> <r​pardini> this could've been a 5-minute thing. instead:
<Armbian-Discord> <r​pardini> - "is official jammy image borked?"
<Armbian-Discord> <r​pardini> - "is petitboot decent?"
<Armbian-Discord> <r​pardini> - "is kernel missing JEDEC ID?"
<Armbian-Discord> <r​pardini> - etc.
<Armbian-Discord> <A​oyfe> 😄 It's all good.
<Armbian-Discord> <A​oyfe> Frankly, a good lesson to learn and hopefully between that and figuring out that the SPI chip did change, you fix all the related HC4 problems. 😄
<Armbian-Discord> <r​pardini> there's 02 problems with the HC4:
<Armbian-Discord> <r​pardini> - HC4 has an OLED variant, that has OLED and RTC via i2c, but RTC is "assumed" present in the device tree, when it shouldnt.
<Armbian-Discord> <r​pardini> - HC4 needs a cooling map in the DT for driving the fan instead of using userspace fancontrol
<Armbian-Discord> <r​pardini> Otherwise it's perfect.
<Armbian-Discord> <r​pardini> hope you have a fruitful time with it and Talos, may the u-boot provided DTB and Talos' EFI be kind.
<Armbian-Discord> <M​anoftheSea> Just don't uncork the heel
<Armbian-Discord> <A​oyfe> Now to unwind how Talos gets the bundled u-boot to chainload Grub normally. I don't see a boot script around anywhere. Oh well, time to go bug folks. Thanks again all!
<Armbian-Discord> <M​anoftheSea> Tell them to modernize and use systemd-boot
<Armbian-Discord> <r​pardini> They probably depend on grub trickery to do their in-place updates.
<Armbian-Discord> <r​pardini> CoreOS sure did, and so does AWS's Bottlerocket, I think
<Armbian-Discord> <r​pardini> You're gonna buy that HK UART thing very soon
<Armbian-Discord> <n​armstrong> I'm having a look for the cooling map
<Armbian-Discord> <I​doLi> Hey, how do I install armbian on an Amlogic S905X3 android tv? after etching the OS to a usb stick and putting it in and entering recovery mode it says I need a zip file but there isn't... Did I do somthing wrong?
<Armbian-Discord> <W​erner> Probably. Better check tvboxes forum since close to nobody here in chat is dealing with such devices. They are unsupported in general anyways.
<Armbian-Discord> <M​anoftheSea> Put it in the trash.
<Armbian-Discord> <I​doLi> why would I do that?
<Armbian-Discord> <I​doLi> ok ill look in the forums thx
<Armbian-Discord> <W​erner> Tvboxes are like cancer. Won't elaborate because typing on phone is annoying 😂
<Armbian-Discord> <T​enkawa> tvbox says enough to those who have had to code/develop on them
<Armbian-Discord> <r​pardini> IdoLi has been warned already about asking for TVBox shit here yesterday.
<Armbian-Discord> <W​erner> I think they understood now 😉