lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
<Armbian-Discord> <I​daho 🌴> That shit ain't open source?
<Armbian-Discord> <r​pardini> partitioning-wise, this gets you started. UEFISIZE is the size of the EFI partition, that ends up in /boot/efi
<Armbian-Discord> <r​pardini> ```
<Armbian-Discord> <r​pardini> IMAGE_PARTITION_TABLE="gpt"
<Armbian-Discord> <r​pardini> UEFISIZE=256
<Armbian-Discord> <r​pardini> BOOTSIZE=0
<Armbian-Discord> <r​pardini> ```
<Armbian-Discord> <r​pardini> but look at extensions/grub.sh for a lot more, but that disables u-boot. grub-sbc-media.sh is Oleg's, dunno how that goes.
<Armbian-Discord> <M​anoftheSea> Disable uboot?
<Armbian-Discord> <M​anoftheSea> That doesn't sound good
<Armbian-Discord> <J​glover99721> @ManoftheSea to answer your question about the helm i did not originally buy it for the hardware specs but for the self hosting email aspect that is now shutting down so instead of letting it be a useless brick i am going to do the conversion to Armbian and find a use for it. Thinking a RSS/torrent client. I have emailed the creator to see if he will release any more details of the board for those of us
<Armbian-Discord> planning to repurpose or hack the hardware.
<Armbian-Discord> <M​anoftheSea> Run postfix?
<Armbian-Discord> <J​glover99721> also the helm runs a Rockchip rk3399 SoC
<Armbian-Discord> <J​glover99721> thats all i know so far
<Armbian-Discord> <M​anoftheSea> Nailed it
<Armbian-Discord> <M​anoftheSea> Well, if it has a functional device tree, it might just work
<Armbian-Discord> <M​anoftheSea> Can you get serial access to uboot on it?
<Armbian-Discord> <J​glover99721> we shall see what the creator says if/when he gets back to me
<Armbian-Discord> <r​pardini> had insomnia. https://github.com/armbian/build/pull/4582 @amazingfate
<Armbian-Discord> <X​yne> @Idaho 🌴 Bluetooth is currently broken on Armbian for Rock 4b, Kernel > 5.15.75 see https://forum.armbian.com/topic/24869-bluetoothap6256-with-kernel-6011-dose-not-work/ . I had to go back to Armbian 20220801-0227 then upgrade to 5.15.74 and use apt-mark hold linux-image-current-rockchip64 and now im Stuck with this Kernel until the problem gets fixed
<Armbian-Discord> <M​anoftheSea> ```static inline int is_valid_header(void)
<Armbian-Discord> <M​anoftheSea> {
<Armbian-Discord> <M​anoftheSea> if ((otp.magic[0] == 'H') || (otp.magic[1] == '6') ||
<Armbian-Discord> <M​anoftheSea> (otp.magic[2] == '4') || (otp.magic[3] == 'N') ||
<Armbian-Discord> <M​anoftheSea> (otp.magic[4] == 'P') || (otp.magic[5] == 'V') ||
<Armbian-Discord> <M​anoftheSea> (otp.magic[6] == '1') || (otp.magic[7] == 0))
<Armbian-Discord> <M​anoftheSea> return 1;
<Armbian-Discord> <M​anoftheSea> return 0;
Armbian-Discord has quit [Remote host closed the connection]
Armbian-Discord has joined #armbian-rockchip
<Armbian-Discord> <T​onymac32> lol
<Armbian-Discord> <T​onymac32> where is that from
<Armbian-Discord> <T​enkawa> Note though that its positionally looking if those spots are those characters "or"
<Armbian-Discord> <T​enkawa> so it still has to be in a position
<Armbian-Discord> <T​enkawa> but that "is" some wildly complex header logic
<Armbian-Discord> <M​anoftheSea> Helios 64
<Armbian-Discord> <M​anoftheSea> I feel like this should just be a strcmp
<Armbian-Discord> <M​anoftheSea> If strcmp == 0, right?
<Armbian-Discord> <M​anoftheSea> I gotta learn how to debug uboot. It is crashing in uboot proper, after reading otp