From owner-freebsd-x11@freebsd.org Mon May 27 00:48:42 2019 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CA4F15B569D for ; Mon, 27 May 2019 00:48:42 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6807175690 for ; Mon, 27 May 2019 00:48:41 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from [10.70.7.24] ([10.70.7.24]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id x4R0mcnK010787 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 27 May 2019 00:48:39 GMT (envelope-from list1@gjunka.com) Subject: Re: sway and libinput initialization failed To: Greg V Cc: freebsd-x11@freebsd.org References: <1558889689.59447.0@unrelenting.technology> From: Grzegorz Junka Message-ID: Date: Mon, 27 May 2019 01:48:33 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <1558889689.59447.0@unrelenting.technology> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB X-Rspamd-Queue-Id: 6807175690 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of list1@gjunka.com designates 88.98.225.149 as permitted sender) smtp.mailfrom=list1@gjunka.com X-Spamd-Result: default: False [-6.94 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:88.98.225.149]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[gjunka.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: gjunka.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.99)[-0.985,0]; IP_SCORE(-3.64)[ip: (-9.53), ipnet: 88.98.192.0/18(-4.77), asn: 56478(-3.81), country: GB(-0.09)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:56478, ipnet:88.98.192.0/18, country:GB]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2019 00:48:42 -0000 On 26/05/2019 17:54, Greg V wrote: > > > On Sun, May 26, 2019 at 5:09 PM, Grzegorz Junka wrote: >> When I set WLR_LIBINPUT_NO_DEVICES to 1, as suggested, sway seems to >> be starting fine, i.e. both screens show the SWAY background, dates >> are displayed, etc. But of course neither mouse no keyboard work. My >> motherboard is Asrock X470 TaiChi Ultimate and mouse and keyboard are >> connected through USB3. > > hi, > > 12.0-RELEASE does not have EVDEV_SUPPORT enabled out of the box :( so > all the drivers not developed for evdev specifically (e.g. wmt is, but > ums/ukbd/psm/atkbd/etc aren't) do not have evdev support. > > IIRC, it's on by default in -STABLE, and it will be in 12.1-RELEASE. > > You have to either switch to a -STABLE snapshot kernel or rebuild a > -RELEASE kernel with options EVDEV_SUPPORT. (or switch to -CURRENT of > course :D) > > Also it's a good idea to set sysctl kern.evdev.rcpt_mask=12 to make > sure you get events from individual devices instead of the > virtual/multiplexed things. > > Many thanks Greg. Would it be the same reason why I don't see mouse/keyboard enabled during normal X11 session? See my other post. I installed KDE and do startx. Keyboard and mouse work fine in the console mode but as soon as KDE launches the mouse is no longer working. I guess the X11 server uses the amdgpu driver which may somehow disable input devices because of EVDEV? Is that assumption correct? And if yes, would using a generic CPU-powered graphics solve the keyboard/mouse issue?