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 has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC> [Discord] <Werner> Since blobs have been bumped is it necessary or recommended to reflash SPI?
<DC-IRC> [Discord] <mecoblock> Anybody an idea why armbian rockchip64 can’t compile kernel modules? What is missing here:
<DC-IRC> [Discord] <mecoblock> ```
<DC-IRC> [Discord] <mecoblock> make[1]: *** /lib/modules/6.6.32-current-rockchip64/build : no file or directory of this type. Halt.
<DC-IRC> [Discord] <mecoblock> ```
<DC-IRC> [Discord] <amazingfate> install linux-headers
<DC-IRC> [Discord] <rpardini> Well to get the updates, yes. I'm usually afraid of testing stuff directly on SPI, so if I've the patience I first install to eMMC, wipe MTD, check it out, and if all is good install to MTD. (Most of the times I just hail-mary it.)
<DC-IRC> [Discord] <rpardini> I guess there's ADC stuff that tells the bootrom where to boot from, no?
<DC-IRC> [Discord] <Werner> I managed to get zero 3e running mainline, both Linux and uboot. Woohoo
<DC-IRC> [Discord] <Werner> If anyone wants to pick it up and create a PR in a why it does not mess up everything like I did feel free to steal from here: https://github.com/EvilOlaf/build
<DC-IRC> [Discord] <Werner> If anyone wants to pick it up and create a PR in a way it does not mess up everything like I did feel free to steal from here: https://github.com/EvilOlaf/build
<DC-IRC> [Discord] <rpardini> Looks pretty good. You've 3 DT-related null-patches there; you should be able to drop the .dts./.dtsi (sans Makefile) directly into the `dt` folder and achieve the same
<DC-IRC> [Discord] <Werner> A person who actually knows what they are doing would have probably done so 😅
<DC-IRC> [Discord] <Werner> While I did not test im pretty confident his breaks vendor and legacy
<DC-IRC> [Discord] <Werner> While I did not test im pretty confident this breaks vendor and legacy
<DC-IRC> [Discord] <rpardini> "bare-DT" patching is relatively recent addition. It would have saved you from handling patches....
<DC-IRC> [Discord] <rpardini> Oh, yes -- because of the `BOOT_FDT_FILE` change (as vendor/legacy would still have the old DTB name).
<DC-IRC> [Discord] <rpardini> You can leave that as original, and put the new one in a `post_family_config_branch_edge__use_mainline_dtb_name()` hook
<DC-IRC> [Discord] <Werner> Hm yes. Maybe I dig a bit further later
<DC-IRC> [Discord] <rpardini> actually, same is true of BOOTCONFIG; you can leave the previous code as is, and add `post_family_config_branch_edge__radxa-zero3_use_kwikboo_uboot` which _also_ changes `BOOTCONFIG`.
<DC-IRC> [Discord] <Werner> Im still amazed that this actually worked 🙈
<DC-IRC> [Discord] <rpardini> so legacy/vendor keep using vendor u-boot, and edge would use new DTB name and Kwiboo's u-boot.
<DC-IRC> [Discord] <mecoblock> they were installed in this case.
<DC-IRC> [Discord] <kwiboo> I am guessing armbian must use an external dtb? mainline u-boot should load correct DT for zero 3e/3w and set fdtfile env variable accordingly
<DC-IRC> [Discord] <rpardini> indeed -- if that is the case, then `BOOT_FDT_FILE` can be `unset` and the bootscript will take whatever `fdtfile` is set to when it runs.
<DC-IRC> [Discord] <rpardini> also makes the same "Armbian board" work for both variants
<DC-IRC> [Discord] <kwiboo> yep, have done something similar for orangepi-3b, one u-boot target that will load correct DT for v1.1/v2.1 hw revision, hoping upstream DTs land in time for v6.11-rc1, will send the orangepi-3b (and the other boards) to upstream u-boot after that
<DC-IRC> [Discord] <rpardini> nice. I love the new `OF_UPSTREAM` stuff
<DC-IRC> [Discord] <Werner> I made a few fixes so legacy and vendor should work again.
<DC-IRC> [Discord] <amazingfate> Drop of nmtui has caused opi3b's first login wifi connection failed.
<DC-IRC> [Discord] <igorpec> huh, latest build i assume? I tested it several times ... huh
<DC-IRC> [Discord] <igorpec> what userspace is this?
<DC-IRC> [Discord] <amazingfate> Noble gnome.
<DC-IRC> [Discord] <amazingfate> Kernel is edge 6.9.6.
<DC-IRC> [Discord] <rpardini> hmm, but `nmcli` is installed, no?
<DC-IRC> [Discord] <rpardini> looks to me it's armbian-firstrun's parsing of nmcli output might be.... lacking
<DC-IRC> [Discord] <rpardini> maybe `nmcli dev status` output format changed in noble... etc
<DC-IRC> [Discord] <igorpec> it is done without nmcli now
<DC-IRC> [Discord] <igorpec> ok, will check and fix
<DC-IRC> [Discord] <rpardini> nope, you're still using `nmcli` to find the `WIFI_DEVICE`
<DC-IRC> [Discord] <rpardini> edge/current mismatch between image and headers? `/lib/modules/6.9.7-edge-rockchip64/build -> /usr/src/linux-headers-6.9.7-edge-rockchip64` just tested on edge
<DC-IRC> [Discord] <alexl83> Hello Guys!
<DC-IRC> [Discord] <alexl83> Is there a specific kernel configuration option in rockchip-rk3588-vendor kernel to turn off the dmesg disclaimer "This is a debug kernel etc etc " ??
<DC-IRC> [Discord] <rpardini> stumbled upon it now. on 3588, it's `BOOT_SARADC_IN0` -- voltage determines boot order. Some boards have DIP switches controlling resistors to allow changing boot order. Not sure if applies to RK3328 -- ask Paolo?
<DC-IRC> [Discord] <c133> hmmm, I don't _see_ any DIP switches on my Rock64
<DC-IRC> [Discord] <c133> unless they're real tiny
<DC-IRC> [Discord] <rpardini> does it have a Maskrom button?
<DC-IRC> [Discord] <rpardini> cos you could solder a resistor there 😉
<DC-IRC> [Discord] <rpardini> I mean, if any of this even remotely applies to a 10-year older 3328
<DC-IRC> [Discord] <rpardini> @mackahan 👆
<DC-IRC> [Discord] <rpardini> Rock64 has a suspicious resistor there
<DC-IRC> [Discord] <alexl83> hey guys, I'm trying to flash an image to emmc using rkdeveloptool - Idid it already a couple weeks ago - but cannot remember which 3588 loader I have to use
<DC-IRC> [Discord] <alexl83> can anyone point me in the right direction please?
<DC-IRC> [Discord] <alexl83> everyfile I have in my rkbin/bin folder is rejected
<DC-IRC> [Discord] <alexl83> I tried rk3588_usbplug_v1.11.bin rk3588_spl_v1.13.bin
<DC-IRC> [Discord] <alexl83> Found it - cache dir in armbian framweork holds the spiloader
<DC-IRC> [Discord] <alexl83> I was searching in rkbin repo
<DC-IRC> [Discord] <narga_64> It is in the Armbian rkbin repo.
<DC-IRC> [Discord] <alexl83> great, thanks @narga - I was missing that piece
<DC-IRC> [Discord] <alexl83> so I can rebuild it should I need to
<DC-IRC> [Discord] <narga_64> Yes 👍
<DC-IRC> [Discord] <rpardini> if you're _not_ using Docker, `EXT=rkdevflash` should do all the dance for you
<DC-IRC> [Discord] <alexl83> never tried out of docker, would love to build directly on host
<DC-IRC> [Discord] <rpardini> `export PREFER_DOCKER=no` before calling `./compile.sh` -- _at your own risk_
<DC-IRC> [Discord] <alexl83> will try for sure as I have a wild experiment to run - which will likely not work but I HAVE TO try
<DC-IRC> [Discord] <alexl83> thanks!
<DC-IRC> [Discord] <rpardini> recommend using a separate git clone
<DC-IRC> [Discord] <rpardini> as sharing directories et will cause insanity
<DC-IRC> [Discord] <rpardini> between docker and non-docker I mean
<DC-IRC> [Discord] <alexl83> Yep, I'm using a different ssd - so when I break everything I can reformat/hide it and pretend I didn't fail 😄
<DC-IRC> [Discord] <rpardini> running outside of Docker will install packges etc on host so beware
<DC-IRC> [Discord] <rpardini> but that said that's how I run 50% of the time
<DC-IRC> [Discord] <narga_64> I only build directly on host. If your host is the latest Ubuntu or Debian, you shouldn't have any problem. At least I haven't. Unfortunately if you're using something like Arch or Fedora, it likely won't work
<DC-IRC> [Discord] <alexl83> ubuntu 22.04
<DC-IRC> [Discord] <rpardini> someone smarter than me will know how to run rkdeveloptool on docker?
<DC-IRC> [Discord] <rpardini> cos that would be ideal
<DC-IRC> [Discord] <narga_64> That'll work perfectly fine. I use 24.04 as build host since I don't like outdated stuff, but it will definitely work on 22.04
<DC-IRC> [Discord] <narga_64> Not worth the effort because you'd have to pass through USB which I think needs to run privileged, so security risky. And also it'll be a completely different USB on every machine
<DC-IRC> [Discord] <rpardini> hmm sorry to inform, but it already runs privileged.
<DC-IRC> [Discord] <narga_64> Oh no. Good thing I don't use it 😂
<DC-IRC> [Discord] <rpardini> can't do loops etc without it
<DC-IRC> [Discord] <rpardini> the non-Docker version also `sudo`'s almost immediately so...
<DC-IRC> [Discord] <rpardini> since I last considered the whole subject, `systemd-mkosi` has come up with ingenious stuff using user namespaces
<DC-IRC> [Discord] <rpardini> one day I shall ~~steal~~ be inpired by it
<DC-IRC> [Discord] <narga_64> Yes, but that's different if you've got an up to date system and your build host is just a VM 😄
<DC-IRC> [Discord] <narga_64> The layers in many containers are ridden with security vulnerabilities unfortunately.
<DC-IRC> [Discord] <narga_64> Podman is much better than Docker in that regard by the way since it doesn't even require root.
<DC-IRC> [Discord] <narga_64> I can recommend trying out Podman if you haven't so far
<DC-IRC> [Discord] <rpardini> I did. rootless makes little sense if the containerized app _needs_ root
<DC-IRC> [Discord] <c133> has maskrom pins
<DC-IRC> [Discord] <c133> and a jumper that seems to make it do the thing
<DC-IRC> [Discord] <rpardini> !!!!!! 👍
<DC-IRC> [Discord] <narga_64> No, you can still run the container rootless, but then you run something *inside* the container as root.
<DC-IRC> [Discord] <narga_64> This is a scenario where Podman shines against Docker imo.
<DC-IRC> [Discord] <c133> well, by "do the thing" I mean, it makes Maskrom mode work, and from maskrom mode, I can't do anything because I can't find any rk3328 SPI loader
<DC-IRC> [Discord] <narga_64> It's for rk3588 but you'll find the same stuff in the rockchip-linux/rkbin repo