From owner-freebsd-current@freebsd.org Tue Oct 9 23:14:41 2018 Return-Path: Delivered-To: freebsd-current@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 18EDA10C1423 for ; Tue, 9 Oct 2018 23:14:41 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (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 9EB4083925 for ; Tue, 9 Oct 2018 23:14:40 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 5B7BFD17; Tue, 9 Oct 2018 19:14:39 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 09 Oct 2018 19:14:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm3; bh=Q KMvHRgEizhJiG3RoPOCpasISU9h4ONVWPOVks/TDuw=; b=Kv356nuW7BbNMHYq+ s0a4kZEfvks3y8yrxwvFo99cXccs6ppvnoDdc/JOsMVcCUOeyqKMCo8LlE5Y3hca zex+iGHbiy1JEm91775X2nRcFVmaeC++5ROXKTG4WiOqdZBllAJNCHzWTQYVbVaz xCvcL0meVHNq0TABz/t8TgtGE9x5RKfCoTB01MVuSDid+kOiYp64qqyz383mqm3R /4dBdef9HOQSQQCbXEaSBo/+hNexb4Vo1gV5TbwbeyyJ0KcmTkrW30tgD1W/dRkv lQdjlm759seBLypeW/x3D+Q0DQk5ZMLUZIkGbLOOaBu6WqNENBGlH/tO6A6wH7Ps KGnng== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=QKMvHRgEizhJiG3RoPOCpasISU9h4ONVWPOVks/TD uw=; b=rM4Nm+mXqvS+yBYsS4tDjhAhWGbhatXxIhkf4LqIY/+Hpc756DurZYwal Z7fndiwHGwhbmsbWo6A/8BbNdNyRwmosqwFS4mj5b8APLctFfjI9iSLNz9VR0ov/ HyRQW+2w7uSlyvjeCr35n2tF2Ohz5S+1uEmJaV6pTn8VOguAVrKlcW6eqXfoA4wK x7mSkGtzi4VQR8S/iRfS5Jyqjk4fgivJ40tUuqt1ijsFRxw5g0f9roiUht+yu+L4 gkU1VBBTt1aivdx+dPK5ecMjAcIk83akRMlk0UWUP1D0TE/oHBxPbkXLlAzlVrHa 89kNQRz4enVChLLgOB9lkAmlhk0bg== X-ME-Sender: X-ME-Proxy: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 555E5102EB; Tue, 9 Oct 2018 19:14:38 -0400 (EDT) Subject: Re: drm confusion / xorg / AMD RX580 GPU To: Johannes Lundberg Cc: freebsd-current References: <365a9257-6858-f386-56d2-5dedb0883670@zyxst.net> From: tech-lists Organization: none Message-ID: <42658ef5-2480-fec1-e143-ebf78b6908cf@zyxst.net> Date: Wed, 10 Oct 2018 00:14:37 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2018 23:14:41 -0000 On 09/10/2018 14:33, Johannes Lundberg wrote: > Hi > > Let me know if you manage to get GPU processing working. I haven't > explored the option so much but from what I've seen so far, there > doesn't seem to be much GPU work available for *nix systems. I'm also on > WCG. Hi, OK the error message for missing firmware has gone from the X.org.0.log but I see "could not load firmware image" in /var/log/messages and unfortunately the GPU still isn't available to crunch from boincmgr: Oct 8 22:51:08 asrock kernel: amdgpu/polaris10_pfp.bin: could not load firmware image, error 2 Oct 8 22:51:08 asrock syslogd: last message repeated 1 times Oct 8 22:51:08 asrock kernel: amdgpu/polaris10_me.bin: could not load firmware image, error 2 Oct 8 22:51:08 asrock syslogd: last message repeated 1 times Oct 8 22:51:08 asrock kernel: amdgpu/polaris10_ce.bin: could not load firmware image, error 2 Oct 8 22:51:08 asrock syslogd: last message repeated 1 times Oct 8 22:51:08 asrock kernel: amdgpu/polaris10_rlc.bin: could not load firmware image, error 2 Oct 8 22:51:08 asrock syslogd: last message repeated 1 times Oct 8 22:51:08 asrock kernel: amdgpu/polaris10_mec.bin: could not load firmware image, error 2 Oct 8 22:51:08 asrock syslogd: last message repeated 1 times Oct 8 22:51:08 asrock kernel: amdgpu/polaris10_mec2.bin: could not load firmware image, error 2 Oct 8 22:51:08 asrock syslogd: last message repeated 1 times Oct 8 22:51:08 asrock kernel: drmn0: fence driver on ring 0 use gpu addr 0x0000000200000008, cpu addr 0x0xfffff8002f4f1008 [snip] Oct 8 22:51:08 asrock kernel: drmn0: fence driver on ring 9 use gpu addr 0x0000000200000098, cpu addr 0x0xfffff8002f4f1098 Oct 8 22:51:08 asrock kernel: i_size_write unimplemented Oct 8 22:51:08 asrock kernel: amdgpu/polaris10_sdma.bin: could not load firmware image, error 2 Oct 8 22:51:08 asrock syslogd: last message repeated 1 times Oct 8 22:51:08 asrock kernel: amdgpu/polaris10_sdma1.bin: could not load firmware image, error 2 Oct 8 22:51:08 asrock syslogd: last message repeated 1 times Oct 8 22:51:08 asrock kernel: drmn0: fence driver on ring 10 use gpu addr 0x00000002000000a8, cpu addr 0x0xfffff8002f4f10a8 Oct 8 22:51:08 asrock kernel: i_size_write unimplemented Oct 8 22:51:08 asrock kernel: drmn0: fence driver on ring 11 use gpu addr 0x00000002000000b8, cpu addr 0x0xfffff8002f4f10b8 Oct 8 22:51:08 asrock kernel: i_size_write unimplemented Oct 8 22:51:08 asrock kernel: amdgpu/polaris10_uvd.bin: could not load firmware image, error 2 [etc] and then this: Oct 8 22:51:08 asrock kernel: amdgpu: [powerplay] [AVFS] Something is broken. See log! Unfortunately it doesn't say which log. [snip] Oct 8 22:51:08 asrock kernel: amdgpu: [powerplay] Can't find requested voltage id in vdd_dep_on_sclk table! Oct 8 22:51:08 asrock kernel: amdgpu: [powerplay] VDDCI is larger than max VDDCI in VDDCI Voltage Table! Oct 8 22:51:08 asrock kernel: [drm] ring test on 1 succeeded in 25 usecs [snip] >> PS. A tip for not having your custom Linux-enabled boinc-client pkg >> overwritten every time you run pkg upgrade, do 'pkg lock boinc-client' :) I build/update from ports, partly because of things like that ;) -- J.