On 03/14/15 15:22, luke...@onemodel.org wrote:
[....]
The goal: I'd like to run multiple simultaneous X sessions and switch
among them with Ctrl-Alt-F8, Ctrl-Alt-F9, etc, each one as a different
[....]
Here is the output I get when I have one X session running ....
and I then run "startx -- :1"
...
$ startx -- :1
[xauth: file /home/myusername/.serverauth.5199 does not exist]
xauth: (stdin):1:
[bad display name "myhostname.mydomain-sans-toplevel.org:1" in "add"
command]
(EE) server terminated with error (1). [Closing log file.]
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
[xauth: (argv):1: bad display name
"myhostname.mydomain-sans-toplevel.org:1" in "remove" command]
[....]
Here is the full content of /var/run/dmesg.boot:
[....]
drm: initializing kernel modesetting (RV515 0x1002:0x7145 0x1028:0x2002).
radeondrm0: VRAM: 256M 0x0000000000000000 - 0x000000000FFFFFFF (128M
used)
radeondrm0: GTT: 512M 0x0000000010000000 - 0x000000002FFFFFFF
drm: PCIE GART of 512M enabled (table at 0x0000000000040000).
error: [drm:pid0:r100_cp_init_microcode] *ERROR* radeon_cp: Failed to
load firmware "radeon-r520_cp"
error: [drm:pid0:r100_cp_init] *ERROR* Failed to load firmware!
error: [drm:pid0:rv515_startup] *ERROR* failed initializing CP (-2).
error: [drm:pid0:rv515_init] *ERROR* Disabling GPU acceleration
drm: radeon: cp finalized
error: [drm:pid0:radeon_bo_unpin] *ERROR* 0xd91c5190 unpin not necessary
radeondrm0: 1920x1200
wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using
wskbd0
wsdisplay0: screen 1-5 added (std, vt100 emulation)
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.
Is there anything short of customizing my (kernel build with that
WSDISPLAY_DEFAULT_SCREENS=N setting?
Or, does bootup somehow call wsconscfgN in a way that I can configure
for more screens (that I haven't found yet)?
Is doing either one of those things known to be safe/stable?
And, how does the system know that some of the already-configured
screens are for console use, and one (ctrl-alt-f5 at least) for X?
Thanks.
-Luke
