Also why do we have device specific options on the core snap? What does happen if I set pi-config.disable-overscan on a device not a pi? Will I see default values for those?
@morphis This page should be removed and link here instead. This is a pattern we should try to replicate with other pages in the documentation. We’ll have many more contributing eyes here, and everyone is able to immediately fix broken documentation, take feedback, and improve it right then.
@ogra Before we move this out of core, we need to have a better picture of how gadget updates are taking care of boot assets, etc. We don’t want to hand off control of these sensitive configuration files before we do that as depending on how we do these updates we might brick devices in the field. Note that having it in core already allows gadgets to tune these options nevertheless.
yup, fully agreed, but what will the migration path for vendors that start using this in their images today be ?
if we move it later we somehow need to move their products too, to not break them with a core update that suddenly does not have that feature anymore …
Can someone document ‘timer’ as well with the complete syntax and representative cron/anacron replacement examples? (eg, hourly, daily at midnight, etc)
I was trying to set the refresh timer to 1st Wednesday of the month at 13:00 and used the convention wed1,13:00. I was expecting the next refresh timer to be set to 1st August which is two days from today (30th of July 2018) but it is set to Wednesday of the second week of August . Is this a bug or am I doing something wrong ?
Here is my commands
$ sudo snap set system refresh.timer=wed1,13:00
$ sudo snap get system refresh.timer
wed1,13:00
$ sudo snap refresh --time
timer: wed1,13:00
last: 11 days ago, at 12:33 IST
next: in 9 days, at 13:00 IST
Using the latest Edge image for Core, setting pi-config.display-rotate=1 (or manually editing /boot/uboot/config.txt) results in a dysfunctional system. According to the official documentation for config.txt video options, display_rotate is deprecated and one should use display_hdmi_rotate or display_lcd_rotate. Setting either manually in /boot/uboot/config.txt seems to have no effect.
Do I need to change any of the HDMI-related parameters as well, or is this a known issue in Edge? When I use Core stable, using the snap configuration hook for display_rotate works as expected.
AFAIK the rotate options only apply to the raw framebuffer that the Pi firmware initalizes.
we default to use the kms/drm framebuffer driver in our pi gadgets though, can you try commenting dtoverlay=vc4-kms-v3d in config.txt and see if the rotation options work then …
if this fixes it, we probably need to make sure the snapd code disables the overlay (at the cost of any accelerated graphics support) in case one of these rotate options gets set.
Will try out disabling the overlay as you suggested, but I’d be happy to use other methods if they preserve accelerated graphics support. Do you happen to have a solution for display rotation with kms/drm, preferably one that can be changed without a reboot?
The timer string format link isn’t getting rendered properly, though I can’t see why. When it’s converted to HTML, it’s generated as an anchor tag with no href property.