From owner-freebsd-questions@freebsd.org Mon Jun 1 19:09:18 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4AF2633EF3D for ; Mon, 1 Jun 2020 19:09:18 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49bPqJ6vmBz4T3P for ; Mon, 1 Jun 2020 19:09:16 +0000 (UTC) (envelope-from manu@bidouilliste.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1591038548; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=RJsrX8U114335Rgi84nifua+h3pbIlMelBjJK92Y5/A=; b=QWHtm3Iuo1MZidBAo4iTtkKcl5dJM7xx5oVaS5B/uuk4lquV8FmRgoRDwVWJYwOc0L3SYg 58K8wNEdMpNlCQ/MMx3/G74whgS596aoFW4tC5rKx6RqeRVPGCwrz70MS0eIiiyCQlBAVQ q2JKxYvg2/WVG+gFRI5+ebcgFYRh+yg= Received: from skull.home.blih.net (lfbn-idf2-1-900-181.w86-238.abo.wanadoo.fr [86.238.131.181]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 13ee68bd (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Mon, 1 Jun 2020 19:09:08 +0000 (UTC) Date: Mon, 1 Jun 2020 21:09:04 +0200 From: Emmanuel Vadot To: Polytropon Cc: Tomasz CEDRO , FreeBSD Questions Subject: Re: Keyboard and mouse not working after X update Message-Id: <20200601210904.26383caf62c0cb59f4a2b68a@bidouilliste.com> In-Reply-To: <20200601205659.fac089c3.freebsd@edvax.de> References: <20200531214105.2caed717.freebsd@edvax.de> <20200531231731.85ee6d3d.freebsd@edvax.de> <20200601001117.f7075d7d.freebsd@edvax.de> <20200601205659.fac089c3.freebsd@edvax.de> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49bPqJ6vmBz4T3P X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mx header.b=QWHtm3Iu; dmarc=pass (policy=none) header.from=bidouilliste.com; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.155.74 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [-2.67 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mx]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.01)[-1.009]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; DMARC_POLICY_ALLOW(-0.50)[bidouilliste.com,none]; NEURAL_HAM_SHORT(-0.15)[-0.151]; NEURAL_HAM_MEDIUM(-1.01)[-1.010]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2020 19:09:18 -0000 On Mon, 1 Jun 2020 20:56:59 +0200 Polytropon wrote: > On Mon, 1 Jun 2020 01:01:22 +0200, Tomasz CEDRO wrote: > > On Mon, Jun 1, 2020 at 12:11 AM Polytropon wrote: > > > What is the correct driver for X for "modesetting", and how > > > can I easily verify it has been loaded? > > > > It is part of the Xorg I guess. Make sure you are in the video group. > > Verified. The user is also member of the "administrative > groups" (operator and wheel). > > > > > Use no config launch startx and it should auto configure. > > Yes, this works. I no longer need (as it seems to be unsupported( > a configuration file for keyboard language, as this has now become > a O(n) instead of O(1) operation, bah, per user. > > > > > Well thing > > changed a bit and we just need to put some time for that to work no > > other way ;-) > > I just wish it was documented in a way a simple mind like mine > could understand. :-) > > So at the moment, I have this (as explained in the documentation): > > In /boot/loader.conf: > > drm_load="YES" That won't work. > In /etc/rc.conf: > > kld_list="amdgpu" This should be enough to have drm.ko loaded as a dependency. > > In the user's ~/.xinitrc: > > setxkbmap -rules evdev -layout de > > The following related packages are installed: > > drm-kmod-g20190710 > drm-fbsd12.0-kmod-4.16.g20200221 > xf86-video-amdgpu-19.1.0_1 > libdrm-2.4.99,1 > > In /var/log/Xorg.0.log, I still get the misleading messages: > > [ 43.096] (II) LoadModule: "ati" > [ 43.098] (WW) Warning, couldn't open module ati > [ 43.098] (EE) Failed to load module "ati" (module does not exist, 0) > > As I seaid, when the xf86-video-ati package was installed, I > just got a black screen in X. However, with xf86-video-amdgpu > installed, there is no indication in the log file that a driver > named "amdgpu" (or the like) has been loaded. Bit I get the > message saying > > Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so > > Followd by those errors: > > [ 43.111] (EE) open /dev/dri/card0: No such file or directory > [ 43.111] (WW) Falling back to old probe method for modesetting > [ 43.111] (EE) open /dev/dri/card0: No such file or directory > [ 43.111] (WW) Falling back to old probe method for scfb > ... > [ 43.111] (II) UnloadModule: "modesetting" > > And later on, it's still pointing to VESA being used. Strange thing, > with "glxgears", I now get approx. 260 FPS, which is 5 times as > much as before. > > No directory /dev/dri does exist. If you have no /dev/dri and no /dev/drm it means that the drm modules wasn't loaded. Look in dmesg for errors and also try to "kldload amdgpu" or "kldload radeonkms" depending on your GPU. > I have installed the MESA packages (mesa-demos, mesa-libs, and > mesa-dri), but that's the software renderer. The "driinfo" program > reports an error, obviously. > > So it still seems that there's something missing for DRI? > > Or is this something to enable somewhere else? > > > > > BSD still seems to be "the rational island" in this "sand castle > > world" and I can clearly see that I also need to add my bricks to make > > it work well thus my focus here :-) > > From all the sand that is blewn over from Linux world, it > becomes a bit harder to see _which_ solution is the suggested > one, at least for the moment... > > > > > > > I > > > > also use hald and dbus. > > > > > > Accepting outdated Linux stuff to make FreeBSD graphics > > > work again doesn't sound as if it was the right thing to > > > do... ;-) > > > > Yea, but this is my _work_station_ so my main focus is to get the > > results in a shorter and shorter time spans.. not always I have lots > > of time to play and fix things anymore.. the world gone mad :-( > > I have systems running MATE which also have HAL and DBus for > whatever reason, and this works. > > > > > > Many many moving parts. :-) > > > > "Change is good" man "root is obsolete" why do we even need those > > computers ;-) ;-) > > I don't know I'm no good with computering. :-) > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" -- Emmanuel Vadot