DietPi / Fuzon

Ah jep, the EEPROM implementation comes with v6.27
Everything else went fine.

Just in case, please do not apply to beta until I merged v6.27.1 to have the fixed RPi4 implementation inside .

@ldg346
Indeed you own a new revision that has not been listed anywhere so far. I just added support for it to dev code: https://github.com/MichaIng/DietPi/issu ... -565410350
To apply now:
https://github.com/MichaIng/DietPi/issu ... -565440203

Thanks for reporting. Yeah there is an issue with our hosting providers network currently: https://github.com/MichaIng/DietPi/issues/3260

Ticket is opened, I hope it is solved soon. Since it depends on the location/host IP, a VPN or similar can workaround the issue meanwhile.

Thanks for reporting. Interesting, actually we estimate the model by revision code. Could you paste the following: cat /proc/cpuinfo

Is your system clock correct?

You could temporarily switch to a different APT mirror or replace https by http to reinstall e.g. ca-certificates package, probably this helps.

Yeah something seems to have mixed up with prior Nginx install. The raw PHP file view indicates that PHP was not running correctly, e.g. the Apache PHP module missing. Possible path: 1. Nginx installed, which installs php-fpm 2. Nginx uninstalled, but PHP left 3. Apache installed, which did not (re)...

co2 Ah yeah I didn't think about dietpi-postboot needs to finish, to allow further logins, hence postboot.d is not useful for background jobs, only for oneshot scripts. Sorry for this wrong suggestion :roll:. Okay then dietpi-autostart > 14 : Custom should do it. Move your script to /var/lib/dietpi...

@jhorv
This depends on the systemd version, hence Stretch vs Buster, not sure if this is new or exist for long already. Easy to check:
systemctl status systemd-journal-remote
In case:
systemctl enable --now systemd-journal-remote
to start it.

Thanks for sharing. Looks like a generic method for putting the device it into sleep mode, only finding the correct power/wakeup connector of course differs .

dietpi-services start <service> is more something meant to be used from console and within our scripts, to have consistent output and error handling. To start/stop/control services in cron jobs, I would use systemctl start/stop <service> directly to avoid overhead and color codes in outputs. Hence:...