Make the kiosk autologin survive a reboot, and allow forcing a display mode

Two problems on musicdolphin, found after its first reboot.

getty@tty1 was never enabled. The role installed the autologin drop-in and the
handler restarted the unit, which works until the next boot - these images do
not enable getty@tty1 themselves, getty.target pulls in getty-static.service and
nothing else, so after a reboot nobody logs in and the kiosk never starts. Enable
it as well as starting it.

And the attached screen reads back 0 bytes of EDID on both micro-HDMI ports while
reporting "disconnected", so the kernel offers no modes, no framebuffer is
created, and X exits with "no screens found". That is the signature of a cable or
adapter whose DDC/HPD lines are broken but whose video pairs are fine. Forcing
the connector on is not enough on its own - with no EDID there is still no mode
to set - so allow a `video=` kernel parameter, which forces the output and names
the mode. hdmi_force_hotplug=1 is no use here; vc4-kms-v3d ignores it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

This commit is contained in:

Martin Bauer

2026-09-20 12:10:34 +02:00

parent 5d853cbb8f

commit a973bc8d75

4 changed files with 53 additions and 0 deletions

									
										6

roles/pi_kiosk/handlers/main.yml
									
												View File
												
				@@ -4,3 +4,9 @@

				    name: "getty@tty1"

				    state: restarted

				    daemon_reload: "yes"

				- name: Warn that a reboot is needed

				  ansible.builtin.debug:

				    msg: >-

				      /boot/firmware/cmdline.txt changed - the forced display mode only takes effect

				      after a reboot.

Make the kiosk autologin survive a reboot, and allow forcing a display mode

6 roles/pi_kiosk/handlers/main.yml Unescape Escape View File

6

roles/pi_kiosk/handlers/main.yml

View File