and, do it via software, will definitively affect performance
[Shaun Mulligan (shaunmulligan)] it would be worth asking in their forums
looks like it is indeed possible
the kernel has to be compiled with the support for that @shaunmulligan
[Shaun Mulligan (shaunmulligan)] There is a chance it could be enabled in our kernel already, so worth a try. Others you can create and issue on our asus OS repo here https://github.com/balena-os/balena-asus-tinker-board and we can get that compiled in
sudo balena ssh --host
? Select a device morning-brook (547930d)
Connecting to: 547930dc64fdd31d896673fd7d422162
gutemberg@ssh.balena-devices.com: Permission denied (publickey).
now I can't login on the host :(
I rebooted it from the portal, removed the local mode and enabled again
and it just fail to boot now
will reflash it
now I just need the freaking rotation to work on it :(
Hi @resinio, I just realized that
balenalib/intel-nuc-alpine-python:3.7-run has Python2 as default, and no python3 installation and balenalib/intel-nuc-alpine-python:3.7.2-run has Python3 as default with a python3 installation. Why the discrepancy? Is this intended? Seems very unintuitive
particularly, eglfs
I’m having troubles with the PI brcm libraries to properly work on balena inside the container
Hi there! I experience some strange issues with the intel-nuc image. I downloaded a development image, installed it on an advantec device (compareable to intel nuc) with ethernet, disconnected ethernet and instead inserted a working SIM. On the device itself I was able to check, that the host os has access to the internet (pinged a couple of servers), though the device is shown as offline in balena.io .
nmcli shows, that supervisor and cellular-modem are connected
Is this a problem of routing in the hostOS?
nmcli shows, that supervisor and cellular-modem are connected
Is this a problem of routing in the hostOS?
[Alison Davis Riddell (alisondavis17)] Hi @philippnbg our team is much more active in our forums, if you could post your question there at https://forums.balena.io/; our engineers monitor it every day and will be able to help out quickly!
@resinio any chance we have the DragonBoard supported? https://www.arrow.com/en/products/dragonboard410c/arrow-development-tools or at least any 96Boards
Qualcomm Snapdragon 410 is far supperior than PI and ASUS tinkerboard… we just got a few for test and it is ridiculously fast. Not to mention the quality of the board itself
Or, should we follow this doc https://www.balena.io/os/docs/custom-build/#supporting-your-own-board and use the BSP from here https://www.96boards.org/documentation/consumer/dragonboard/dragonboard410c/build/open-embedded.md.html and build ourselves? Would that still be officially supported by balenaCloud?
@galvesribeiro the best way to ensure production ready support is to work with our team to support the board through our custom device support program. That will ensure new OS releases are tested for compatibility and we ensure things don't break. If you are interested in that please reach out to our sales team.
ok
it is actually not a custom device
but a very common qualcomm-based board
will email Trevor now
in general we try to support boards that have a lot of community interest or if we have multiple requests from customers, because its a large process burden for us and intensive to support, so it has to have a good ROI for us. We haven't seen a lot of requests for any of the 96boards yet, so we havent supported them yet.
@galvesribeiro yup, very aware of the Dragonboard 410c, i brought one about 2 years ago ;) its a very nice board indeed
will ping trevor
but in all cases, if I do it myself following that guide, it should work, right?
@galvesribeiro yes, although the dragonboard might need changes at the meta-balena leave because i think it needs fastboot rather than uboot and currently fastboot bootloader is not supported, but I am not sure. Also note you would need to submit it as a "Community" device type in order for it to be shown in our dashboard, otherwise you would need to have it masquerade as a Generic aarch64 device (but in that case it would not have OS upgrades as our backend wouldn't know what device type it is)