<jaeger>
After several hours, still no hang on the pi but we'll see if it does overnight
<r0ni>
so i have this odd issue on crux-arm. If i plug an external usb-c nvme drive enclosure into vmware and try to mount it, it stalls indefinately. If I do the same with the drive on slackware, it works normally. Same kernel on both VMs... what am i obviously missing?
<beerman>
If the kernel is the same, all i can suspect are differences in the userland
<r0ni>
ya it's very odd, i'll have to tail some logs and see what crux is telling me
<jaeger>
Maybe a udev difference?
<jaeger>
The rpi3 is still responsive this morning and still building updates, currently gcc
<beerman>
Cool
<pitillo>
jaeger: abput the key, arm64 should be fine, the 32b I don't know who managed it, so I can't help there
<pitillo>
about the tests, I had same results (slower die) when using nfs. Let's see your results 8)
<pitillo>
about cycle deps we saw it when building the release so we managed it removing ninja and not using upstream ports (this was the reason about all those core overlays not updated)
<beerman>
did i manage that one? I know i wanted to use armv7 on the pi4 and did because kodi ran on it flawlessly, but not on aarch64
<pitillo>
r0ni: I'd check what jaeger said, smells to something related to udev
<pitillo>
beerman: probably. if you can't find it, regen a nre key, resign ports and shsre it with me xD
<pitillo>
I can try to check locally because I remember this talk, give me some minutes to check from phone
<beerman>
i don't have a 32 bit installation anymore <_< i am checking my mails now because i remember exchanging stuff with jaeger at some point in the past
<pitillo>
ls -la /etc/ports/raspberrypi3-arm*
<pitillo>
-rw-r----- 1 root pkgmk 188 Mar 9 2021 /etc/ports/raspberrypi3-arm.sec
<pitillo>
-rw-r--r-- 1 root root 230 Oct 30 2022 /etc/ports/raspberrypi3-arm64.httpup
<pitillo>
I think we are using raspberrypi3-arm to sign arm64
<pitillo>
I don't know what happened there
<pitillo>
there is a mix in naming
<pitillo>
the raspberrypi3-arm64.pub points to raspberrypi3-arm.sec
<pitillo>
points/corresponds
<beerman>
about the circular dependencies with ninja: i think this is easily solveable
<beerman>
i'll look at that in a bit
bru-barwal has quit [Ping timeout: 260 seconds]
bru-barwal has joined #crux-arm
<jaeger>
Do you want to continue using the -arm key to sign rpi3-arm64 stuff or will that change? I'm fine either way, just curious.
<pitillo>
question is if is there a good way to don't change the key, only the name
<pitillo>
if changing the name doesn't affect, we can change it, but I'm not sure about this
<jaeger>
https://crux.ninja/tmp/rpi3-arm64-packages/ <-- here's where I'm putting the go, llvm, rust packages. Currently there's an m1 dir for the ones built on the m1 (with rpi3-optimized CFLAGS though) and I'll upload the ones built natively on the rpi3 in another 2 months when they finish :D
<jaeger>
I expect so, if I remember right they're built with generic CFLAGS
<ukky>
I know r0ni keeps his Cortex-A53 packages here: https://rekt.lngn.net/crux-arm/core/ , but I am not sure if there are all packages I might need
<ukky>
generic aarch64 should be good
<ukky>
my emmc is still empty, no bootloader yet. I need to create rootFS from your packages selectively as I have only 100MB for kernel and initial rootfs. No network driver, only jtag.