cobraPA
cobraPA
I've been going through the same build for a pi zero W here and had some problems with the GO setup as well. At least with the current version of...
I was wondering about those paths as well. I suspect /root/go_path/... is not correct? But I'm new to go, maybe that worked in older versions. In 1.10 is seems to...
-U only overrides version checks, not the locked eeprom, from what I tried yesterday. Using the unlock and wipe eeprom by itself, followed by a new install works here.
Additional observations, I see that the pip install uses clang and names both arch's x86_64 and arm64 at the same time. The failing toolchain build seems to setup a tmp...
Wow, 50 and 100 max peers? That seems like a lot. Are you attached to the testnet? I see 63 peers in the first posts logs... The testnet seems to...
Only one failure machine on first install. Do you know if anything besides .config, .kivy and .sideband is created? I moved those away and tried to repeat, and it started...
Sounds good, no problem marking this 'can't reproduce' or something. If I find a case for that I can add details and reopen.