From owner-freebsd-x11@freebsd.org Fri Apr 24 15:42:15 2020 Return-Path: Delivered-To: freebsd-x11@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 8A8452B9003 for ; Fri, 24 Apr 2020 15:42:15 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 497z1y6sKPz4XhX for ; Fri, 24 Apr 2020 15:42:14 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: by mailman.nyi.freebsd.org (Postfix) id EB6802B9002; Fri, 24 Apr 2020 15:42:14 +0000 (UTC) Delivered-To: x11@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 EB2D12B9001 for ; Fri, 24 Apr 2020 15:42:14 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mxt.nsu.ru (mxt.nsu.ru [84.237.50.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 497z1x0X5Rz4XhS; Fri, 24 Apr 2020 15:42:11 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from zimbra.nsu.ru ([84.237.50.42]) by mxt.nsu.ru with esmtp (Exim 4.89) (envelope-from ) id 1jS0St-00068B-T1; Fri, 24 Apr 2020 22:42:07 +0700 Received: from localhost (localhost [127.0.0.1]) by zimbra.nsu.ru (Postfix) with ESMTP id CF3F0AC131B; Fri, 24 Apr 2020 22:42:07 +0700 (+07) Received: from zimbra.nsu.ru ([127.0.0.1]) by localhost (zimbra.nsu.ru [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id WnPnTZBQtJgb; Fri, 24 Apr 2020 22:42:07 +0700 (+07) Received: from localhost (localhost [127.0.0.1]) by zimbra.nsu.ru (Postfix) with ESMTP id 8B5E9AC1320; Fri, 24 Apr 2020 22:42:07 +0700 (+07) X-Virus-Scanned: amavisd-new at zimbra.nsu.ru Received: from zimbra.nsu.ru ([127.0.0.1]) by localhost (zimbra.nsu.ru [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id QLuyGJVBgrmN; Fri, 24 Apr 2020 22:42:07 +0700 (+07) Received: from regency.nsu.ru (unknown [84.237.50.47]) by zimbra.nsu.ru (Postfix) with ESMTPS id 5E30CAC131B; Fri, 24 Apr 2020 22:42:07 +0700 (+07) Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id 03OFgZhp022665; Fri, 24 Apr 2020 22:42:35 +0700 (+07) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id 03OFgTto022622; Fri, 24 Apr 2020 22:42:29 +0700 (+07) (envelope-from danfe) Date: Fri, 24 Apr 2020 22:42:29 +0700 From: Alexey Dokuchaev To: Niclas Zeising Cc: x11@freebsd.org Subject: Re: GPU firmware naming and problems with loading Message-ID: <20200424154229.GA11678@regency.nsu.ru> References: <20200421090909.GB13384@regency.nsu.ru> <8990dbd6-65b7-81f4-e0c5-4541e34afee2@freebsd.org> <20200421130955.GA8165@regency.nsu.ru> <749e8db2-8dd8-3ad8-dbee-332bb2a7742b@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <749e8db2-8dd8-3ad8-dbee-332bb2a7742b@freebsd.org> User-Agent: Mutt/1.4.2.1i X-KLMS-Rule-ID: 3 X-KLMS-Message-Action: skipped X-KLMS-AntiSpam-Status: not scanned, whitelist X-KLMS-AntiPhishing: not scanned, whitelist X-KLMS-AntiVirus: Kaspersky Security for Linux Mail Server, version 8.0.3.30, not scanned, whitelist X-Rspamd-Queue-Id: 497z1x0X5Rz4XhS X-Spamd-Bar: / X-Spamd-Result: default: False [0.21 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.62)[-0.616,0]; R_DKIM_ALLOW(-0.20)[nsu.ru:s=email]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mxt.nsu.ru]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-0.44)[-0.436,0]; IP_SCORE(1.46)[ip: (4.27), ipnet: 84.237.48.0/21(1.68), asn: 3335(1.34), country: RU(0.01)]; DKIM_TRACE(0.00)[nsu.ru:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[40.50.237.84.list.dnswl.org : 127.0.11.0]; DMARC_POLICY_ALLOW(-0.50)[nsu.ru,quarantine]; FORGED_SENDER(0.30)[danfe@nsu.ru,danfe@regency.nsu.ru]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:3335, ipnet:84.237.48.0/21, country:RU]; FROM_NEQ_ENVFROM(0.00)[danfe@nsu.ru,danfe@regency.nsu.ru]; RCVD_COUNT_SEVEN(0.00)[8]; DWL_DNSWL_NONE(0.00)[nsu.ru.dwl.dnswl.org : 127.0.11.0] 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: Fri, 24 Apr 2020 15:42:15 -0000 On Thu, Apr 23, 2020 at 10:42:22PM +0200, Niclas Zeising wrote: > On 2020-04-21 15:09, Alexey Dokuchaev wrote: > > ... > >Why is it trying to load TAHITI modules is another question. > > I don't know why it tries to load TAHITI, I'll try to figure more > out, but in general, the firmware selection code is from the original > source, so it should be the same elsewhere. Does TAHITI load with > drm-legacy-kmod? Nope. This is for legacy (kldstat | grep radeon_): 41 1 0xffffffff81b31000 2385 radeon_ARUBA_pfp_bin.ko 42 1 0xffffffff81b34000 2383 radeon_ARUBA_me_bin.ko 43 1 0xffffffff81b37000 1985 radeon_ARUBA_rlc_bin.ko This is for drm-{current,devel}-kmod (surprisingly, couple of my later attempts to "kldload radeonkms" did not hang the laptop, but the very latest still did): 48 1 0xffffffff819d3000 2385 radeon_ARUBA_pfp_bin.ko 49 1 0xffffffff819d6000 2383 radeon_ARUBA_me_bin.ko 50 1 0xffffffff819d9000 1985 radeon_ARUBA_rlc_bin.ko 51 1 0xffffffff819db000 35ba7 radeon_TAHITI_uvd_bin.ko 52 1 0xffffffff81a11000 beb7 radeon_TAHITI_vce_bin.ko Both drm-fbsd{11.2,12.0}-kmod still lock up the laptop, but the logs show they do load TAHITI modules as well. > If you have the opportunity, can you check which firmwares are loaded on > a Linux system with the same hardware? I've booted Ubuntu 18.04, lsmod(8) output is too cluttered on Linux so perhaps we should look elsewhere, but per dmesg(8) it seems that only ARUBA firmware is loaded. Is there some special command on GNU/Linux that shows exactly which firmware files were loaded? > Does it work if you remove the TAHITI modules before loading the > graphics ko? Looks like it loads TAHITI ok though. It does not seem to make any noticeable difference. I'm starting to think that it might not be related to the firmware. I'll continue my investigations. Another thing is, that even if "kldload radeonkms" succeeds, glxinfo -B still reports software mode. In the /var/log/Xorg.0.log, I see these lines, does it ring any bell? (II) AIGLX: Screen 0 is not DRI2 capable (EE) AIGLX: reverting to software rendering ./danfe