On 10/04/18(Tue) 11:57, Mark Kettenis wrote:
> > Date: Tue, 27 Mar 2018 13:40:02 +0200
> > From: Martin Pieuchot
> >
> > On 05/02/18(Mon) 18:31, Artturi Alm wrote:
> > > On Mon, Feb 05, 2018 at 02:51:48PM +0100, Martin Pieuchot wrote:
> > > > On 04/02/18(Sun) 11:28, Artturi Alm
> Date: Tue, 27 Mar 2018 13:40:02 +0200
> From: Martin Pieuchot
>
> On 05/02/18(Mon) 18:31, Artturi Alm wrote:
> > On Mon, Feb 05, 2018 at 02:51:48PM +0100, Martin Pieuchot wrote:
> > > On 04/02/18(Sun) 11:28, Artturi Alm wrote:
> > > > Hi,
> > > >
> > > > machdep.forceukbd=1
On 05/02/18(Mon) 18:31, Artturi Alm wrote:
> On Mon, Feb 05, 2018 at 02:51:48PM +0100, Martin Pieuchot wrote:
> > On 04/02/18(Sun) 11:28, Artturi Alm wrote:
> > > Hi,
> > >
> > > machdep.forceukbd=1 feels broken to me, as i use "sv", and it doesn't
> > > respect
> > > /etc/kbdtype.
> >
> > If
On Mon, Feb 05, 2018 at 02:51:48PM +0100, Martin Pieuchot wrote:
> On 04/02/18(Sun) 11:28, Artturi Alm wrote:
> > Hi,
> >
> > machdep.forceukbd=1 feels broken to me, as i use "sv", and it doesn't
> > respect
> > /etc/kbdtype.
>
> If you unplug/replug your USB keyboard after having booted does
On 04/02/18(Sun) 11:28, Artturi Alm wrote:
> Hi,
>
> machdep.forceukbd=1 feels broken to me, as i use "sv", and it doesn't respect
> /etc/kbdtype.
If you unplug/replug your USB keyboard after having booted does it
respect /etc/kbdtype?
On Sun, Feb 04, 2018 at 09:32:41AM +, Jason McIntyre wrote:
> On Sun, Feb 04, 2018 at 11:28:31AM +0200, Artturi Alm wrote:
> > Hi,
> >
> > machdep.forceukbd=1 feels broken to me, as i use "sv", and it doesn't
> > respect
> > /etc/kbdtype.
> > caused nothing but my time being
On Sun, Feb 04, 2018 at 11:28:31AM +0200, Artturi Alm wrote:
> Hi,
>
> machdep.forceukbd=1 feels broken to me, as i use "sv", and it doesn't respect
> /etc/kbdtype.
> caused nothing but my time being (not-so-well-)wasted, because i forgot having
> just added forceukbd=1 && this 'quirk' being