You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have done a number of PicoBoot installs and this issue crops up about 20% of the time. Swiss gets stuck on loading settings and requires removal of the SD card to bypass.
Would welcome any thoughts.
Steps to reproduce
If I use SD card in the memory card slot (2) and set "configuration device" to the memory card slot and save the settings and then restart the cube, it gets stuck on loading settings until I pop out the SD card and reinsert. Then Swiss and content will launch properly.
If I use the SD card in the SP2 slot and set "configuration device" to SP2 and save, the same thing will happen upon restart.
However if I save settings as above and then insert the card into the opposite slot, it will load just fine (but without the saved configuration).
Expected behavior
save and load settings properly
Relevant log output
No response
Add screenshots
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
I have done a number of PicoBoot installs and this issue crops up about 20% of the time. Swiss gets stuck on loading settings and requires removal of the SD card to bypass.
Would welcome any thoughts.
Steps to reproduce
If I use SD card in the memory card slot (2) and set "configuration device" to the memory card slot and save the settings and then restart the cube, it gets stuck on loading settings until I pop out the SD card and reinsert. Then Swiss and content will launch properly.
If I use the SD card in the SP2 slot and set "configuration device" to SP2 and save, the same thing will happen upon restart.
However if I save settings as above and then insert the card into the opposite slot, it will load just fine (but without the saved configuration).
Expected behavior
save and load settings properly
Relevant log output
No response
Add screenshots
No response
The text was updated successfully, but these errors were encountered: