Linux Firmware

[ryansch]

How is the underlying firmware built? Are there plans to open source that?

/etc/os-release is a symlink to /usr/lib/os-release but /usr/lib is empty.

The dev_deploy.sh script is able to replace the golang binary but it doesn't seem like we're able to dig into the linux bits.

[Nevexo]

The build scripts aren't open sourced yet, they will be eventually.

You can build it yourself by building a fairly standard Buildroot image from the guides on the Luckfox website.

[Poopi]

So until it is going to open there is a limited trust that there is no backdoor or trojan of any kind....Any ETA for open sourcing the firmware?

[Nevexo]

No. More important tasks to do. All I can say is "soon", but I think most of us want jetkvm_native more lol.

If it's a huge problem then you can build your own image and put the jetkvm-app on there.

[Poopi]

I see. But what happened to the commitment: "The complete source code will be made available when the first JetKVM units ship in early December."?

[Nevexo]

Not sure, with all the holds up and irate support@/shipping@ emails the team are rushed off their feet at the minute. I'll ask the team to include a section about it in the next KS update.

[miguemely]

Couldn't find anything else for the FW, so I guess this is probably the best place to ask.

Based on /oem/usr/bin/RkLunch.sh, I don't see any other place sysctl stuff is handled. Can I just safely... put something like sysctl -w "net.ipv4.ping_group_range=0 1" on the last line of the network_init function?

[tutman96]

The system build has been published here: https://github.com/jetkvm/rv1106-system. You can see from the Github Actions run exactly how it is built or follow along with the steps in the README. I am currently trying to reproduce the build locally, but am confident since the GHA ran it it should be reproducible.