Skip to content
Discussion options

You must be logged in to vote

After more digging both a broken EEPROM (or missing) as well as a corrupt can cause this error. In this PR it should hopefully be fixed. Try it out and let me know the result.

Replies: 3 comments 7 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
7 replies
@matejkarasek
Comment options

@matejkarasek
Comment options

@tobbeanton
Comment options

@tobbeanton
Comment options

Answer selected by matejkarasek
@matejkarasek
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants