Hello erwin,
It seems that there is some misconfiguration that iterates every time the restart of the unit. It is indeed a very strange behavior.
I would recommend, then, to re-burn the microSD card to start again with a freshly installed OS, and see if the unit manages to connect with no modifications. I will post the burning instructions here for your convenience:
- Please take the microSD card you have and format it before burning the new Shake OS image
- Make sure, when you format it, that the shown capacity is the maximum (i.e. if the SD card is 32GB like yours, then the capacity should be near or equal to that value). This is to check that no partitions have been involuntarily and erroneously created. They could be the cause of the error we see now
- Take care to format the SD card in a FAT32 File System (or exFAT if the SD card is 64GB or larger)
- Download the new Shake OS image from here: https://gitlab.com/raspberryShake-public/raspshake-sd-img/-/raw/main/raspishake-release.zip
- And follow the microSD burning instructions from here: raspishake-microSD-card-software-Instructions.txt · main · raspberryShake-public / Raspshake Sd Img · GitLab
I followed the numbered list points to burn the files on my SD cards, and I have not used Etcher or similar software.
If, even after this, the Shake is still displaying a “Not Connected” status, then please retry the following procedure to see if it solves the connectivity issue?
Please access your
rs.local/page, go toSettings(the gear icon high on the left), and then theDatatab. Try unchecking theForward Databox and, after ~30 seconds, recheck it. Then,click save and restart.
If no procedure works, then please download the log files again and attach them to your answer, together with a screenshot of both dhcpcd.conf and resolv.conf files.
Thank you.