The Pi wasn’t appearing (with either wired or wireless IP) in Lanscan at all. It is POSSIBLE that I miss-set that instead of escaping back as-is. I did notice that (seems like an odd place to have it and is IMHO easy to miss) setting the noise to low, switches off HDMI. Turns out I had selected the worng version of HIFIBerry, but that shouldn’t matter… I ran through the settings in order on the setup menu. It depends a bid I think, sometimes the hostname is just handled visually and if it’s about IP reservation etc. Your router/DHCP server cannot see the device at all? After changing hostname, of course potentially assigned IPs can be lost and you might need to re-add the device respectively re-assign an IP to it. But this should not effect network connectivity. Especially if you choose (on RPi) screen resolution “headless” or set “CONFIG_HDMI_OUTPUT=0” to dietpi.txt, then on boot the screen will blank. This is a quite trivial and should not break any reboot.ĭid you change other settings. Indeed the new hostname is added to /etc/hostname and /etc/hosts to the default internal host IP 127.0.1.1. The script behind this is quite trivial: You used dietpi-config to change the hostname, or directly within dietpi.txt (which should just have an effect before first boot)?.Then you configured the DAC and hostname?
#GITHUB PYTHON LANSCAN UPDATE#
This is a fresh DietPi image? Just flashed, started, wait for first run setup to update to current DietPi version, reboot and finish first run dietpi-software setup.
0 kommentar(er)
