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
<DC-IRC>
[Discord] <microlinux> Yeah, same psu. Doesn't look great.
<DC-IRC>
[Discord] <t1msu_87222> It says " HDMIRX driver now only works with the opensource TF-A" Is this the case for armbian images?
<DC-IRC>
[Discord] <.cicatrix> could someone help me with installing the RKNPU driver on my CM3588 installed with this armbian build?
<DC-IRC>
[Discord] <amazingfate> armbian is using close source TF-A
<DC-IRC>
[Discord] <shivansps> but how it is broken if mesa matrix report all 1.0 features are in and just 1 away from full 1.1?
<DC-IRC>
[Discord] <zwillx> Hey guys got the docker working on MacOS with the build script by modifying partitioning.sh.. have to create a dummy loop device after initial loop creation to force refresh of block devices. Works with existing "CONTAINER_COMPAT" variable
<DC-IRC>
[Discord] <igorpec> software features breaks all the time
troglodito has quit [Ping timeout: 248 seconds]
troglodito has joined #armbian-rockchip
<DC-IRC>
[Discord] <menu> does the docker build not actually work on mac?
<DC-IRC>
[Discord] <zwillx> no it's a nightmare lol. It used to work, last year (possibly changed via Mac update or Docker). Now the loop devices don't populate correctly even with --privileged and cap_add SYSADMIN etc
<DC-IRC>
[Discord] <zwillx> But, in my case, it was even *more of a nightmare my experience with UTM and VMs which just crash and you lose everything. So, very glad to get it working 🙂
<DC-IRC>
[Discord] <mecoblock> does the change break regular linux environments? Else you should PR that. Would like to try it out on my mac too
<DC-IRC>
[Discord] <mecoblock> Never had an UTM VM crash on me though (not counting putting my mac to sleep and back with vm running)
<DC-IRC>
[Discord] <zwillx> I doubt it because the way loop devices are handled are totally dif. I'm sure it works fine on linux but haven't installed Asahi on my Mac yet
<DC-IRC>
[Discord] <zwillx> docker is basically managing the loop devices synthetically and I think that's why the partition table isn't responding appropriately. Like it won't populate /dev/loop0p1
<DC-IRC>
[Discord] <menu> i need to look into how this works, there's probably some mac-specific nonsense
<DC-IRC>
[Discord] <zwillx> yeah could be specific to docker app on Mac, seems accurate. Dammit after a reboot I still didn't fix it XD
<DC-IRC>
[Discord] <zwillx> I actually did *not fix it from a cold start, as I just discovered 😅 I might try a bit more but I know the issue - in loop.sh there's function check_loop_device_internal(). In it there's a check for CONTAINER_COMPAT and it ultimately tries to make a node, but the code here is busted- wrong references, doesn't pass the if statement anyway, etc. My solution (for now) is to run
<DC-IRC>
[Discord] <zwillx> previously, the blockdev command would report invalid device or size 0 or something, and without the blockdev registering the partition, no mkfs, no img
<DC-IRC>
[Discord] <zwillx> yeah could be specific to docker app on Mac, seems accurate. Dammit after a reboot I still didn't fix it XD
<DC-IRC>
[Discord] <zwillx> I actually did *not fix it from a cold start, as I just discovered 😅 I might try a bit more but I know the issue - in loop.sh there's function check_loop_device_internal(). In it there's a check for CONTAINER_COMPAT and it ultimately tries to make a node, but the code here is busted- wrong references, doesn't pass the if statement anyway, etc. My solution (for now) is to run
<DC-IRC>
[Discord] <zwillx> previously, the blockdev command would report invalid device or size 0 or something, and without the blockdev registering the partition, no mkfs, no img
<DC-IRC>
[Discord] <zwillx> so if you do a 2 mknod commands in an init script,
<DC-IRC>
[Discord] <zwillx> `mknod -m 660 /dev/loop0p1 b 7 1
<DC-IRC>
[Discord] <zwillx> mknod -m 660 /dev/loop1p1 b 7 2`
<DC-IRC>
[Discord] <zwillx> then my patch works
<DC-IRC>
[Discord] <zwillx> yeah could be specific to docker app on Mac, seems accurate.
<DC-IRC>
[Discord] <zwillx> I actually did *not fix it from a cold start, as I just discovered 😅 I might try a bit more but I know the issue - in loop.sh there's function check_loop_device_internal(). In it there's a check for CONTAINER_COMPAT and it ultimately tries to make a node, but the code here is busted- wrong references, doesn't pass the if statement anyway, etc. My solution (for now) is to run
<DC-IRC>
[Discord] <zwillx> previously, the blockdev command would report invalid device or size 0 or something, and without the blockdev registering the partition, no mkfs, no img
<DC-IRC>
[Discord] <beohoff3174> I'm leveraging my two rk3588's for my and my wife's daily driver, so I haven't had a chance to mess around with the bootloader
<DC-IRC>
[Discord] <mecoblock> no idea maybe that’s something to ask kwiboo
<DC-IRC>
[Discord] <kwiboo> I have not used mainline TF-A on my rk35xx boards, what I do know is that for rk356x important scmi clock support is not yet merged, for rk3588 I think most important parts have landed in mainline TF-A
<DC-IRC>
[Discord] <beohoff3174> where are you watching that at, U-Boot?