After the fix for the syntax error the following has happened and does not resolve until the unit is accessed via SSH:
After accessing SSH these 2 screens populate their information. Notice how the name of the Adapter name changes from eth0 to eth1. The IP and MAC also populate.
These are the only 2 screens affected. All other screens show info/activity right away. Once I have accessed it (I simply open the SSH command window, that’s it) the data continues to update. However if I reboot (or lose power) those 2 screens do not populate correctly upon reboot. I do have PlexMedia Server that auto-starts on this server also. It would be well to note that even watching a movie, those 2 screens will not populate network data. Nor do they populate when accessing an SFTP session and transferring files, which should show something.
I’ll run a test tomorrow with DHCP (instead of static) and see if I can replicate the issue.
In the mean time, if your comfortable, could you try setting your eth1 adapter to STATIC. You can do this by running dietpi-config 8 1 . Reboot the system and see if the issue still occurs.
Ok, so even with DHCP, i’am still unable to replicate the missing data. Works everytime, for me at least.
Notice how the name of the Adapter name changes from eth0 to eth1. The IP and MAC also populate.
Unable to do the second part because as soon as I open the command prompt, all the missing data populates.
Very strange.
I’d imagine DietPi is detecting the eth0 device as your default adapter during boot. This data is provided by the kernel, so at this point, eth0 is correct.
I’am not sure why its changing to eth1. Its also strange that the eth0 device is then disappearing from the system. I’ve seen eth1 on some Odroid boards from our users, but its mostly eth0. Maybe a slight change in network hardware/chip on some boards? not sure.
Either way, lets get dmesg log, might tell us more. Please paste the results:
I’ve updated the init code for DietPi-Cloudshell. It will update the DietPi active network adapter file during 1st run. Please can you test it and let me know if the issue reoccurs:
Ran dietpi-config. Changed the adapter to “static” from “dhcp”. Copied the current IP so I wouldn’t have to configure one. Rebooted and all the data populated right away. No issues. I did another reboot and even did a cold boot to see if the info would clear and be empty, info still populated like it should. The issue appears to be on the DHCP side.
Update
As of today, those 2 screens are still working great. I did another “cold boot” and a separate reboot and the data still populated right away. For DHCP, it’s still blank until I initiate an SSH session. I’m leaving it on static as it is not causing any issues.
We’ve made some core changes to the networking in DietPi v120 which should prevent these missing details. v120 should be released within a week.
If you experience any missing details in v120, please let me know and reopen the ticket if possible: https://github.com/Fourdee/DietPi/issues/359.