MichaIng
commented
5 years ago @hyperionlevelq Many thanks for your report.
Actually the output is just misleading:
[ SUB1 ] DietPi-Set_hardware > headless (disable): It disables headless mode since you selected VNC server, which requires this.[ OK ] DietPi-Set_hardware | Comment in /DietPi/config.txt converted to setting: #hdmi_ignore_hotplug=0: This also states that that finally a commented entry is the result. If the setting would have been present in an active (not commented) way, the output would have been clearer to state that a setting was commented. The function we use is actually not really made to turn settings into comments, thus the misleading output. But the result is correct. Regardless I will change this to avoid confusion.
So actually you should have fount the three entries in a commented way, thus HDMI should have been still active.
To check the long boot time, please paste: dmesg
And check journalctl the entries until networking has been started.
Another minor:
- Was wondering why VNC4 gets configured but not installed before. Actually we do the check wrong there, checking for "marked as installed" OR "already installed". Does not hurt but should be not required. So another visual/confusing one 😄.
- And not VNC4 server is the reason for headless mode being disabled, but any desktop or desktop application (Chromium, Kodi, DietPi-Cloudshell) or camera application. Disabling headless mode here (if the related software title has already been installed before) is kinda failsafe. Although also this could be perhaps changed to only apply if you just marked any of them. I guess with an active desktop or graphics application one will quickly realise that enabled headless mode will make them useless 😄.
mtpiercey
diveyez
Information:
DietPi version: 6.24.1
Distro version: Debian Stretch
Kernel version: Linux DietPi 4.19.42+ #1219 Tue May 14 21:16:38 BST 2019 armv6l GNU/Linux
SBC device: Raspberry Pi Zero W v1.1
Power supply used: 5V 1A USB -> 120V (Generic Digipower brick with official-looking RPi USB cable)
SDcard used: Kingston 16GB (Class 10)
Software title: Certbot installation script
Steps to reproduce:
Expected behaviour
Actual behaviour
Extra details (the full log, see the bold part at bottom for unexpected behaviour)
Like I said, I was able to log back in and change back the HDMI settings, but I wasn't expecting this and figured it was worth sharing in case anybody else experienced this.