From owner-freebsd-stable@freebsd.org Wed Jan 30 21:24:22 2019 Return-Path: Delivered-To: freebsd-stable@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 839041319F2D for ; Wed, 30 Jan 2019 21:24:22 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [140.82.23.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.nomadlogic.org", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 64F0C86C05 for ; Wed, 30 Jan 2019 21:24:21 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from duke.gem.co (cpe-76-175-75-27.socal.res.rr.com [76.175.75.27]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 07cc47b1 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Wed, 30 Jan 2019 13:24:19 -0800 (PST) From: Pete Wright Subject: Re: X11 on Ryzen 2400G? To: Phil Norman Cc: freebsd-stable@freebsd.org References: <844971e0-1def-ce56-4c9c-369f3b0c6f3b@nomadlogic.org> Message-ID: <17f607b8-82bb-ba53-91c0-b347a2b72ec6@nomadlogic.org> Date: Wed, 30 Jan 2019 13:24:19 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-Rspamd-Queue-Id: 64F0C86C05 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 140.82.23.70 as permitted sender) smtp.mailfrom=pete@nomadlogic.org X-Spamd-Result: default: False [-4.65 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[27.75.175.76.zen.spamhaus.org : 127.0.0.10]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; DMARC_NA(0.00)[nomadlogic.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mail.nomadlogic.org]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.91)[-0.912,0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-2.43)[ip: (-8.79), ipnet: 140.82.16.0/21(-4.39), asn: 20473(1.13), country: US(-0.07)]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:20473, ipnet:140.82.16.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2019 21:24:22 -0000 On 1/30/19 12:10 PM, Phil Norman wrote: > Hi. > > First of all, thanks for the detailed instructions. Response inline. > sure thing! > > -- pay special attention to the update the /boot/loader.conf > > > Are you referring to the need to set 'hw.sysconf.disable=1', or is > there something else I'm missing? I didn't see anything else on the > wiki page, except for some debugging options (which I guess I'm going > to end up using soon). yes that is what i was referring to.  I do not have an AMDGPU system myself but have been told several times that it is required. > > - after you have configured the amdgpu.ko to load on boot verify > it is > able to load the kernel module and your console display looks > good.  if > you have issues loading the kernel module let us know, there are some > things you can try to setup to get a useful backtrace that will > help us > debug this. > > > This is where I get to. I've removed amdgpu from /etc/rc.conf, so I > don't have to boot single-user mode; when I run kldload amdgpu, the > following happens: > > 1: the 'kldload amdgpu' process doesn't return immediately, yet the > terminal is responsive; I can hit return, and have the cursor move. > The mouse pointer also moves. > 2: something around 5s later, the screen turns off, the keyboard goes > unresponsive (caps lock light doesn't toggle), and the machine no > longer responds to pings. > interesting, it looks like the kernel module and firmware modules do load.  one thing you may want to test is setting the "debug.debugger_on_panic=0" sysctl knob before loading the amdgpu.ko.  hopefully this will allow you to get into a debugger before the system locks up. cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA