sway and libinput initialization failed
Greg V
greg at unrelenting.technology
Tue May 28 10:35:26 UTC 2019
On May 28, 2019 2:40:45 AM GMT+03:00, Grzegorz Junka <list1 at gjunka.com> wrote:
>
>> No, input is independent of graphics.
>>
>> Xorg supports the legacy FreeBSD interfaces, you can check the xorg
>log and xinput list to see if there's any mouse related error, but
>that's very strange, USB mouse under Xorg has been a very typical
>situation for ages. I actually don't remember how device autodetection
>worked on Xorg with moused and whatnot, I've been using Wayland
>exclusively for over a year now.
>>
>
>Many thanks for help. I managed to get the mouse and keyboard working.
>KDE is working fine too, on both monitors, which is great!
>
>However, the graphics seems to be not-accelerated (there is noticeable
>"drag" when moving windows around). I am running generic kernel
>12-RELEASE and up to date port (kld_list="amdgpu" in rc.conf). The
>graphics card is Radeon RX Vega 64. Should the hardware acceleration
>work, and if yes, is there any way to verify hardware acceleration is
>working as expected in either waylaynd or xorg?
Sway does not have software rendering at all, IIRC llvmpipe software OpenGL wouldn't work either. So if sway is running, it's accelerated. Run sway with the --verbose flag and read the output, it will show the used renderer. (In the virtual console… but you'll see it after quitting sway)
In xorg, compositing is external and done by your WM/DE. I'm not sure if KDE does it out of the box, maybe you need to turn it on. Though it would be odd if it didn't do it by default, it's 2019…
More information about the freebsd-x11
mailing list