Few issues with Odroid XU4

After having issues with HDMI output an my monitor, I have dietpi up and running on my Odroid XU4. I didn’t find a way to fix the HDMI output yet so I plugged the XU4 into my TV and the display was functioning.

Issue #1 - When I reboot, the XU4 shutdown (solid red light, blue is off).

Issue #2 - While checking my logs to troubleshoot #1, I discovered that /var/log/syslog is overwritten on boot, I only see logs since the boot. I verified I am setup for Full logging to disk.

Issue #3 - I didn’t do any research yet but I expect the HDMI output issue is a minor one.

Any hints on the above items?

root@XU4:/DietPi/dietpi# cat /DietPi/dietpi/.installed | grep ‘INDEX_LOGGING’
root@XU4:/DietPi/dietpi# uname -a
Linux XU4 4.14.66+ #1 SMP PREEMPT Thu Aug 23 05:59:33 UTC 2018 armv7l GNU/Linux
root@XU4:/DietPi/dietpi# cat /DietPi/dietpi/.version

If it helps, I just noticed that /var/log is still mount on tmpfs rather than under / (and on disk)

root@XU4:~# df -h | grep var
tmpfs 50M 3.2M 47M 7% /var/log
root@XU4:~# more /etc/fstab | grep var
tmpfs /var/log tmpfs defaults,size=50m,noatime,nodev,nosuid,mode=1777 0 0

Many thanks for your report.

Although we did not do much changes to the RAMlog system, since v6.23 was released yesterday, you might want to update before going through the below steps.

Could you please paste (if it exists):
cat /var/tmp/dietpi/logs/dietpi-ramlog_disable_debug.log

And is the dietpi-ramlog service still active:
systemctl status dietpi-ramlog

In case try to redo RAMlog uninstall by manually marking it as installed first:
sed -i ‘/aSOFTWARE_INSTALL_STATE[103]/c\aSOFTWARE_INSTALL_STATE[103]=2’ /DietPi/dietpi/.installed
Then start dietpi-software and choose DietPi-RAMlog for uninstall. After a reboot /var/log should be not mounted as tmpfs any more and the dietpi-ramlog service should be disabled. cat /var/tmp/dietpi/logs/dietpi-ramlog_disable_debug.log should in case give a hint if it did not succeed.

This is getting a little more interesting, I also upgraded to the latest beta version.

root@XU4:~# cat /var/tmp/dietpi/logs/dietpi-ramlog_disable_debug.log
cat: /var/tmp/dietpi/logs/dietpi-ramlog_disable_debug.log: No such file or directory

root@XU4:~# systemctl status dietpi-ramlog
● dietpi-ramlog.service - DietPi-RAMlog
Loaded: loaded (/etc/systemd/system/dietpi-ramlog.service; enabled; vendor preset: enabled)
Active: active (exited) since Sat 2019-05-11 23:26:10 ADT; 1 day 21h ago
Process: 381 ExecStart=/bin/dash -c /boot/dietpi/func/dietpi-ramlog 0 2>&1 >> /var/tmp/dietpi/logs/dietpi-ramlog.log (code=exited, status=0/SUCCESS)
Process: 376 ExecStartPre=/bin/mkdir -p /var/tmp/dietpi/logs (code=exited, status=0/SUCCESS)
Main PID: 381 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/dietpi-ramlog.service

Running the uninstaller did the trick, I now have persistent logs in /var/log. Both RAMlog and rsyslog were installed. Looks better.

The odd part now is that I have logs that are not mine, I am guessing from your builds, Nov 3rd, then March 24th, then Nov 3rd, then Aug 27th and then my logs start. I still have the reboot issue were the device powers down (firmware issue vs diet issue???).

When I look at the logs I see:
ay 13 21:36:51 XU4 python2.7[931]: 2019-05-13 21:36:51,568::warning::[init:182] Signal 15 caught, saving and exiting…
May 13 21:36:51 XU4 systemd[1]: Stopped target RPC Port Mapper.
May 13 21:36:53 XU4 systemd-udevd[271]: Network interface NamePolicy= disabled on kernel command line, ignoring.
May 13 21:36:53 XU4 systemd[1]: Starting Flush Journal to Persistent Storage…
May 13 21:36:53 XU4 kernel: [ 0.000000] Booting Linux on physical CPU 0x100
May 13 21:36:53 XU4 fake-hwclock[234]: Tue 14 May 00:36:52 UTC 2019
May 13 21:36:53 XU4 kernel: [ 0.000000] Linux version 4.14.66+ (root@loki) (gcc version 4.9.2 (Debian 4.9.2-10+deb8u1)) #1 SMP PREEMPT Thu Aug 23 05:59:3
3 UTC 2018
May 13 21:36:53 XU4 kernel: [ 0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d

lots of normal boot messages…

Followed by what looks like a normal startup. However, the blue LED inside the XU4 never lights and the network never responds. Since I am still having the HDMI issue, I don’t have a display located close to my XU4 (switch is in one location and TV that has display working is in another), I need to get a long ethernet cable then I can watch the messages on shutdown.

More details to follow…

Thanks for the first tip!

Actually the logs from image build process should be removed, but perhaps that was not yet the case when we created the XU4 image or something failed or in earlier versions some logs during early boot where written to persistent dir before ramlog tmpfs mounted over, not sure. However not a real issue.

About display and LED:
Did you try to update the kernel/firmware: G_AGI linux-image-4.14-armhf-odroid-xu4, apt full-upgrade