CC becomes unauthorized?

[doc-hex]

from @tehelsper

I've also noticed that the CC can lose connection with CKBunker after a while and need to be reset. This seemed to fix it. The ColdCard was still running and appeared to be in the expected state.

echo 0 > /sys/bus/usb/devices//authorized
echo 1 > /sys/bus/usb/devices//authorized

[doc-hex]

Can you share more details about this? Like what Linux did this to you?
Your workaround there looks easy to execute inside CKBunker itself.

[mynode-dev]

Raspbian on a Raspi 4. When I had printed the contents on the the device's "authorized" file it was 1 originally, but toggling it triggered it to reconnect for some reason. At first I thought it was a power issue, but it didn't seem be power related. All power save / autosuspend options looked off.

It took maybe 2-3 hours before dropping and I reproduced the issue several times. It seemed very consistent to reproduce.