From owner-freebsd-stable@freebsd.org Wed Jan 30 19:14:24 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 40D3B14CA14B for ; Wed, 30 Jan 2019 19:14:24 +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 2805F8141B for ; Wed, 30 Jan 2019 19:14:23 +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 addf0d34 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Wed, 30 Jan 2019 11:07:40 -0800 (PST) Subject: Re: X11 on Ryzen 2400G? To: Phil Norman , freebsd-stable@freebsd.org References: From: Pete Wright Message-ID: <844971e0-1def-ce56-4c9c-369f3b0c6f3b@nomadlogic.org> Date: Wed, 30 Jan 2019 11:07:40 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 2805F8141B 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]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MX_GOOD(-0.01)[mail.nomadlogic.org]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.88)[-0.882,0]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20473, ipnet:140.82.16.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[27.75.175.76.zen.spamhaus.org : 127.0.0.10]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; DMARC_NA(0.00)[nomadlogic.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-2.46)[ip: (-8.89), ipnet: 140.82.16.0/21(-4.45), asn: 20473(1.13), country: US(-0.07)]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] 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 19:14:24 -0000 On 1/30/19 9:57 AM, Phil Norman wrote: > Hi. > > I recently got a Ryzen 2400G, which has on-board AMD Vega 11 graphics. I > can get a console to display via the motherboard's on-board HDMI, but > haven't been able to get Xorg working yet. I'm trying the 'amdgpu' driver, > and am using an xorg.conf file generated with 'Xorg -configure' (albeit > hand-tweaked to get rid of the nonexistent second screen it added, and fix > a few more things). > > My understanding is that the driver is likely borrowed from linux, and > (from http://forum.mxlinux.org/viewtopic.php?t=46887) Vega support only > started working with linux kernel 1.19. The /var/log/Xorg.0.log file says > that the amdgpu module was 'compiled for 1.18.4, module version = 18.1.0'. > Does the 1.18.4 refer to a linux kernel version? If so, what's my best > solution here? Should I just wait until the FreeBSD drivers are updated? Is > there anything I can do in the meantime? I believe there may be some previous success running Vega graphics on FreeBSD.  Couple things to note: - If possible run 12.0-RELEASE - install the drm-kmod package, then closely follow the instructions printed on your console.  This wiki section should offer some help: https://wiki.freebsd.org/Graphics#AMD_Graphics -- pay special attention to the update the /boot/loader.conf - 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. - try moving your Xorg.conf out of the way then try starting X. -- If that fails try dropping your custom config in there which is using the amdgpu Xorg driver. Hope this helps! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA