> Now I finally (cough) notice those error messages in dmesg.boot. Not > sure how critical they are, if it's referring to missing binary blobs, > and if openbsd has fallen back to acceptable/stable defaults or > something. But where it says "screen 1-5 added", that seems to connect > with 'man wsdisplay' saying that screens can be > configured with either the wsconscfg utility or a (kernel?) > compile-time parameter. I tried running things like "wsconscfg 6" (& > 7, 8), which return 0, but it didn't seem to change the behavior.
The kernel will attach WSDISPLAY_DEFAULTSCREENS virtual consoles by default, which is 6 on i386 and amd64 platforms. More virtual consoles (up to WSDISPLAY_MAXSCREEN, which is 12) can be created by using wsconscfg as you did. Your dmesg output will report something like: wsdisplay0: screen 6 added (std, vt100 emulation) Now, for X to find a proper virtual console to run on, it has to find an unused one, i.e. one where no getty(8) runs. This is controlled by /etc/ttys, and in the default congfiguration of six virtual consoles, only the fifth (ctrl-alt-F5) is left unused and available for X. If you run another X server instance, it will use the seventh virtual console (ctrl-alt-F7). But I am not sure drm-enabled X servers can run multiple instances. Miod
