Re: Pinebook14/Pro xenodm(1) initially fails [Re: Pinebook Pro]

2020-03-31 Thread Mark Kettenis
> Date: Tue, 31 Mar 2020 16:48:39 +0200 > From: Patrick Wildt > Cc: Marcus MERIGHI , arm@openbsd.org, > kette...@openbsd.org > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > > On Wed, Mar 25, 2020 at 01:15:03PM +0100, Otto Moerbeek wrote: > > On Wed, Mar 25,

Re: Pinebook14/Pro xenodm(1) initially fails [Re: Pinebook Pro]

2020-03-31 Thread Patrick Wildt
On Wed, Mar 25, 2020 at 01:15:03PM +0100, Otto Moerbeek wrote: > On Wed, Mar 25, 2020 at 01:02:24PM +0100, Marcus MERIGHI wrote: > > > Hello, > > > > as I spend a lot of time with my Pinebook14/Pro there's things to report > > and even more things to ask. > > > > Should I file bug reports to

Re: Pinebook14/Pro xenodm(1) initially fails [Re: Pinebook Pro]

2020-03-31 Thread Matthieu Herrb
On Tue, Mar 31, 2020 at 08:49:59PM +0200, Matthieu Herrb wrote: > On Tue, Mar 31, 2020 at 05:33:24PM +0200, Mark Kettenis wrote: > >> > > I didn't write *that* code. Just the code that figures out which > > /dev/tty[C-J]0 is the actual console corresponding to /dev/console. > > > > What seems

Re: Pinebook14/Pro xenodm(1) initially fails [Re: Pinebook Pro]

2020-03-31 Thread Matthieu Herrb
On Tue, Mar 31, 2020 at 05:33:24PM +0200, Mark Kettenis wrote: >> > I didn't write *that* code. Just the code that figures out which > /dev/tty[C-J]0 is the actual console corresponding to /dev/console. > > What seems to be happening here is that xenodm(1) and getty(8) are > racing eachother.