Looking at linux-imx - Git at Google we see it already have those fixes, but balena is not using it yet (it’s using release-day instead of latest master commit).
We just went ahead and baked an image with the new stuff, updating the layers/meta-balena-coral/recipes-kernel/linux/linux-imx_4.18.98.bb to the new commit.
Can you guys provide an estimate of when that change can make to the dashboard so I can deploy to the faulty devices? It’s very important for us. I’m also available to provide more info and even enable balena support access on some devices (faulty and fixed) if that would make things quicker.
Thank you for your message, summary and pull request. I contacted the balenaOS team in order to double-check your PR and see how we can solve this issue.
Also a quick heads up that we don’t currently have this device type in our automated testing rig, so we will be unable to accelerate the release and it will need to be prioritized among other manual testing tasks if your PR is merged.
Hey, @klutchell. Thanks for reviewing the PR. I did update it
Can you guys provide an estimate on when it can make it to the dashboard OS update?
Or alternatives of how we can update the devices until it’s there?
Devices keep falling apart, which is hurting our experience.
Hey, @acostach. Thanks for reviewing.
I change the PR. Not sure why it is failing the “Is PR open” check, tho.
Let me know if you need me to change anything else
Thanks for the support, guys
Thanks @jairo, I opened another PR with your change in the meantime and will check if everything’s fine on that one, merge it there if it’s quicker. Once it’s merged we’ll run the manual testing suite on the build to see if everything works as expected and then release the image in the cloud. We’ll keep you updated on the progress
Hi, @acostach! Excellent! I already applied the OS update and the devices are working nicely!
Thank you all for the support and quick action! Kudos @klutchell@mpous@acostach
