dont use the stable image until gadget upgrades work …
@ogra ouch, really? I literally just installed this image though. Should I create a new one based on another channel?
Also, while I’m unclear how this could be due to an old gadget since i2c was working back in the 15.04 days, does that mean we should be rolling new stable Ubuntu Core images more regularly?
the frequency of image generation does not matter, as long as gadget (and along with that the kernel snap) can not be moved to the stable channel for the pi2/3, we are stuck with the status quo … both snaps need to move over …
Surely there’s something more stable than edge that has this issue fixed? I’m trying to create another series here, I don’t want to recommend people use edge images.
sorry, there is only edge … due to the nature of the pi’s, there is a tie between kernel and gadget and they can only be moved together … but since gadget upgrades do not work (yet ?) installed images might break due to a wrong dtb (old dtb with newer kernel)… this can only move forward once the gadget can be updated on the device…
Yikes. So we just have broken pi2/3 images and have to live with it? I remember talking about gadget updates in London, do you know the priority of this work (that’s snapd, right?)?
@kyrofa@ogra We’ve recently investigated this case and there’s actually no real reason to hold these upgrades back. We just need to do the work and cook new images that have a kernel approved by the kernel team.
Well, they work, but are missing features …
Not sure where in the core teams schedule gadget/bootloader upgrades are … i know they have been scheduled multiple times over the last year but fell off the schedule due to more urgent bits …
@kyrofa We’re working together with the kernel team on this, but things changed hands recently in this exact area, so I need to go after it and make sure we have a champion that will take it all the way.
.