jaeger changed the topic of #crux-arm to: CRUX-ARM 3.6 Released! - http://crux-arm.nu/Documentation/ReleaseNotes3-6 | Logs: https://libera.irclog.whitequark.org/crux-arm/
<jaeger> Good point, I didn't think to mention that. A generic release would work just fine for all pis.
<beerman> ok, i pulled jaegers exisiting kernel to spare me the rebuild time of that and booted into rc3, looks good so far
<beerman> pkmk.confs cflags are missing the pi optimization flags
<pitillo> rc3 should be the generic one beerman , so generic cflags used. jaeger optimization must have rpi4 optimiced cflags
<beerman> ah, gotcha, no worries
<pitillo> np
<beerman> i plan on rebuilding everything over here as well 🙂
<pitillo> no no!!!
<beerman> i am on my way to move the installation to an ssd
<beerman> no no? q?
<pitillo> don't rebuild everything when it's done on jaeger optimization
<pitillo> you can avoid that step
<beerman> mh
<beerman> would need to repull jaegers rootfs then i guess
<pitillo> yes, if you plan to keep it
<beerman> 😆 ok
<beerman> well, ok then, guess i can just process with creating a bootable ssd for it then
<beerman> brb ☕️
<pitillo> if you wanna play with the generic (look for bugs, wrong things...) it's fine, but if you plan to keep and maintain (and look for wrong things too) put the opti one
<beerman> who took my last usb-a/usb-c cable <.<
<beerman> (i did, i have not enough of those)
<pitillo> ummmm is the boot partition bootable?
<pitillo> and it should be fat32 LBA if I'm right
<beerman> just booted 😄
<beerman> my oversight, i didn't have the cmdline.txt and config.txt in boot lmao
<beerman> but now booted from ssd without the sd card even inserted
<pitillo> nice, it boots directly from the sdd
<pitillo> I'd like to test rc 3.7 for the cb2 booting from ssd too
<pitillo> from the cb2/on the cb2
<beerman> yep, i just updated the firmware to the latest stable, it was introduced a long time ago, pretty neat. i used to run my armv7 rpi4 from ssd too, but this is another unit. I plan to move both pis to use arm64 and then, from there, try to get the pinephone up and running as well
<beerman> with firmware i mean the specific pi eeprom updates
<beerman> currently on my way to setup my specific userland with zsh, neovim, doas etc 🙂
<pitillo> nice nice
<beerman> next i can make it crunch on llvm again 🤓
<beerman> i kinda made it choke with 4 make jobs on llvm and its been unresponsive for 20 minutes, no idea if its going on still.. so far it hasn't crashed, i'll let it run and see where this ends
<beerman> c++: fatal error: Killed signal terminated program cc1plus
<beerman> this is where it ends ;D
<pitillo> you you have swap?
<pitillo> with those kind of ports swap is needed or you'll get sigkill
<beerman> nah, no swap so far. llvm with 3 jobs seems to work better
<beerman> we'll see if it finishes, after that, i still has to survive rust