Open gb-dursley opened 5 years ago
UPDATE: Finally got both the old B+ and a Zero HW working perfectly with a pcf8523 RTC apparently installed (Hardware and System Clocks successfully synced) on my normal router. Then on the Zero, changed the wireless network (a different router with a different Gateway IP and NO Internet connection and static IP) via the browser interface. Although this was working on with these network settings before I cracked the problem of installing an RTC, Zero won’t boot successfully:- The Zero did repeated reboots/crashes. Searching the SD card’s 3 Partitions on a Linux laptop for ‘wpa_supplicant’ reveals: Partition 1 (/boot) no longer contains my original wpa_supplicant.conf (or any other) Partition 2 (/root) /etc contains the mEOS default (skeleton) wpa_supplicant.conf Partition 3 (/data) /etc contains a modified version of my wpa_supplicant.conf with the original network settings overwritten with the new network, but wpa_supplicant.log shows 10 identical lines - Successfully initialized wpa_supplicant – pretty pointless. /data/etc/wpa_supplicant.conf copied to /boot (Partition), refit SD card, and power-up Zero (camera Led not lit), Zero unresponsive. Power off, re-examine SD card: Partition 1 – as above Partition 2 – as above Partition 3 now contains my modified version. Looking at the log files:- boot.log shows that motionEyeOS is looping, unsuccessfully attempting to boot messages contains large blocks of - Jan 1 00:01:29 meye-c16e4894 user.notice date: failed to set current system date/time via HTTP Copied my original (1st boot) wpa_supplicant.conf to /boot (partition), edited /etc/static_ip.conf to match 1st Network/router. and powered up the Zero. Doesn’t work – Zero still loops repeatedly booting and inaccessible. Posting with logs before I go back to square one and re-flash the SD card (quickest solution). I’ll avoid static IP addresses for now.
boot.log dmesg.log messages.txt motion.log motioneye.log wpa_supplicant.log
Can anyone tell me how to disable Internet clocks.
1717 # motionEyeOS Versions: motioneyeos-raspberrypi-20190427 & motioneyeos-raspberrypi-20190911
Board Model: Raspberry Pi B+ and Raspberry Pi B+ respectively
Camera: MMAL
Raspberry Pi V1.3 (8mpx) & ZeroCam (5mpx)
Network Connection: WiFi
I've spent many hours trying to get an pcf8523 RTC module to work; starting by religiously following the skeletal Tweak. Despite hours of research, I still can't work out what should fill the gaps in the Tweak. Looking at how to setup an RTC for Raspbian gives an idea of some of what's missing, but there are clearly big differences between how Raspbian and ThingOS work.
hwclock
fails with the message‘/dev/misc/rtc’ : No such file or directory
- evidently it forms a link to an RTC but what should it contain is a complete mystery (though a common problem). So, while I have no trouble setting the System Clock withdate
, the Hardware Clock (RTC) is completely useless. Similarly while/sys
exists, it's empty; so the command (via putty)echo rtc-pcf8523 0x68 > /sys/class/i2c-adapter/i2c-1/new_device
fails. Isnew _device
a file or a directory? Has anyone else cracked this nut?