Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 May 2019 04:31:08 +0300
From:      Greg V <greg@unrelenting.technology>
To:        Grzegorz Junka <list1@gjunka.com>
Cc:        freebsd-x11@freebsd.org
Subject:   Re: sway and libinput initialization failed
Message-ID:  <2E74BE3C-43D2-42C4-82F7-204B30F08D9E@unrelenting.technology>
In-Reply-To: <d1d41fcc-8838-0307-c35f-8d8ac350ed91@gjunka.com>
References:  <c033f9e8-e179-86c1-6c91-5062f7ad9692@gjunka.com> <1558889689.59447.0@unrelenting.technology> <d1d41fcc-8838-0307-c35f-8d8ac350ed91@gjunka.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On May 27, 2019 3:48:33 AM GMT+03:00, Grzegorz Junka <list1@gjunka=2Ecom> w=
rote:
>
>On 26/05/2019 17:54, Greg V wrote:
>>
>>
>> On Sun, May 26, 2019 at 5:09 PM, Grzegorz Junka <list1@gjunka=2Ecom>
>wrote:
>>> When I set WLR_LIBINPUT_NO_DEVICES to 1, as suggested, sway seems to
>
>>> be starting fine, i=2Ee=2E both screens show the SWAY background, date=
s=20
>>> are displayed, etc=2E But of course neither mouse no keyboard work=2E =
My
>
>>> motherboard is Asrock X470 TaiChi Ultimate and mouse and keyboard
>are=20
>>> connected through USB3=2E
>>
>> hi,
>>
>> 12=2E0-RELEASE does not have EVDEV_SUPPORT enabled out of the box :( so
>
>> all the drivers not developed for evdev specifically (e=2Eg=2E wmt is,
>but=20
>> ums/ukbd/psm/atkbd/etc aren't) do not have evdev support=2E
>>
>> IIRC, it's on by default in -STABLE, and it will be in 12=2E1-RELEASE=
=2E
>>
>> You have to either switch to a -STABLE snapshot kernel or rebuild a=20
>> -RELEASE kernel with options EVDEV_SUPPORT=2E (or switch to -CURRENT of
>
>> course :D)
>>
>> Also it's a good idea to set sysctl kern=2Eevdev=2Ercpt_mask=3D12 to ma=
ke=20
>> sure you get events from individual devices instead of the=20
>> virtual/multiplexed things=2E
>>
>>
>Many thanks Greg=2E Would it be the same reason why I don't see=20
>mouse/keyboard enabled during normal X11 session? See my other post=2E I=
=20
>installed KDE and do startx=2E Keyboard and mouse work fine in the
>console=20
>mode but as soon as KDE launches the mouse is no longer working=2E I
>guess=20
>the X11 server uses the amdgpu driver which may somehow disable input=20
>devices because of EVDEV? Is that assumption correct? And if yes, would
>
>using a generic CPU-powered graphics solve the keyboard/mouse issue?

No, input is independent of graphics=2E

Xorg supports the legacy FreeBSD interfaces, you can check the xorg log an=
d xinput list to see if there's any mouse related error, but that's very st=
range, USB mouse under Xorg has been a very typical situation for ages=2E I=
 actually don't remember how device autodetection worked on Xorg with mouse=
d and whatnot, I've been using Wayland exclusively for over a year now=2E



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2E74BE3C-43D2-42C4-82F7-204B30F08D9E>