02-19-2020, 01:34 AM
(This post was last modified: 02-19-2020, 02:06 AM by rogerroger.)
One last comment for the night: bizarrely, `startx` fails with
However, following @elewarr's tracks, `rcctl -f start xenodm` or `rcctl enable xenodm; reboot` Just Works. What gives? What's that about?
EDIT: answered my own question: it's a perms thing. `doas startx` works but `startx` under my regular user account doesn't. xenodm is started as root. I ran
and scrolled down until I saw that it was trying to open /dev/ttyC0.
I did
because that's what my amd64 machine has (at least while I'm logged in on that tty?). Then `startx` gave a new error: "/dev/ttyC1: Permission Denied", so I did
too, and after that `startx` worked.
..weird. I don't understand why.
Oh but the mouse is broken. argh.
Quote:xf86OpenConsole: No console driver found
However, following @elewarr's tracks, `rcctl -f start xenodm` or `rcctl enable xenodm; reboot` Just Works. What gives? What's that about?
EDIT: answered my own question: it's a perms thing. `doas startx` works but `startx` under my regular user account doesn't. xenodm is started as root. I ran
Code:
ktrace X # let it crash
kdump | less
and scrolled down until I saw that it was trying to open /dev/ttyC0.
I did
Code:
chown $USER:tty /dev/ttyC0
because that's what my amd64 machine has (at least while I'm logged in on that tty?). Then `startx` gave a new error: "/dev/ttyC1: Permission Denied", so I did
Code:
chown $USER /dev/ttyC1
too, and after that `startx` worked.
..weird. I don't understand why.
Oh but the mouse is broken. argh.