Resolution is set at max on install on x86 - should be set to a decent low resolution

[fribse]

Describe the issue you are experiencing

When installing a Home Assistant on x86, the resolution is set to max, even though it doesn't make any sense.
There is no need for at huge resolution when all you get is text, during install of new HA's, I often have a capture card connected, as it's much easier to have it on my work monitor in a window, but the capture card runs 4K, and then the resolution is maxed to that, making the window unreadable.
It would make much better sense to just set it to max 1920x1080 or even lower for the console, or make it user selectable, to satisfy all needs.

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

6.6.66-haos

Did the problem occur after upgrading the Operating System?

No

Hardware details

It's a Nucbox from GMKtec, Gen 3 (not plus).
Intel N100, 4Core
Intel UHD Graphics

Odd thing is, it says in the host log:
2025-01-21 15:27:05.457 homeassistant kernel: Console: switching to colour dummy device 80x25

But it doesn't do it.

Steps to reproduce the issue

1. Follow the x86 guide, method 1 for install

Anything in the Supervisor logs that might be useful for us?

Nothing

Anything in the Host logs that might be useful for us?

2025-01-21 15:27:05.435 homeassistant systemd[1]: Finished Apply Kernel Variables.
2025-01-21 15:27:05.435 homeassistant systemd[1]: Mounted Hosts persistent configuration.
2025-01-21 15:27:05.435 homeassistant systemd[1]: Mounted Timesyncd persistent configuration.
2025-01-21 15:27:05.444 homeassistant systemd[1]: HAOS data disk detach was skipped because of an unmet condition check (ConditionFirstBoot=yes).
2025-01-21 15:27:05.446 homeassistant systemd[1]: Home Assistant OS data partition migration was skipped because of an unmet condition check (ConditionPathExists=/mnt/overlay/move-data).
2025-01-21 15:27:05.453 homeassistant systemd[1]: Starting HassOS data resizing...
2025-01-21 15:27:05.457 homeassistant kernel: Console: switching to colour dummy device 80x25
2025-01-21 15:27:05.457 homeassistant kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
2025-01-21 15:27:05.642 homeassistant kernel: i915 0000:00:02.0: [drm] Transparent Hugepage support is recommended for optimal performance on this platform!
2025-01-21 15:27:05.642 homeassistant kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io+mem

System information

System Information

version	core-2025.1.2
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.13.1
os_name	Linux
os_version	6.6.66-haos
arch	x86_64
timezone	Europe/Copenhagen
config_dir	/config

Home Assistant Cloud

logged_in	false
can_reach_cert_server	pending
can_reach_cloud_auth	pending
can_reach_cloud	pending

Home Assistant Supervisor

host_os	Home Assistant OS 14.1
update_channel	stable
supervisor_version	supervisor-2024.12.3
agent_version	1.6.0
docker_version	27.2.0
disk_total	234.0 GB
disk_used	5.2 GB
healthy	true
supported	true
host_connectivity	false
supervisor_connectivity	false
ntp_synchronized	false
virtualization
board	generic-x86-64
supervisor_api	ok
version_api	pending
installed_addons

Dashboards

dashboards	2
resources	0
views	0
mode	storage

Recorder

oldest_recorder_run	January 20, 2025 at 11:05 AM
current_recorder_run	January 21, 2025 at 4:27 PM
estimated_db_size	0.23 MiB
database_engine	sqlite
database_version	3.47.1

Additional information

Lovely cheap machine for HA :-)

[sairon]

The resolution is set to the native resolution which is indicated by the connected display - if the DRM driver can support it, it sticks to that resolution. If we had to pick a resolution, we could end up with a value that's not supported by some displays and that would cause bigger trouble. If it bothers you, you can specify the resolution by editing cmdline.txt in the boot partition and adding video=... parameter per this document that suits you, AFAIK it should be respected by the driver handling the tty on HDMI output. Since the HDMI output only serves debugging purposes, adding any modesetting capabilites throughout the whole stack would be an overkill in my opinion.