From owner-freebsd-x11@FreeBSD.ORG Sat Nov 15 21:46:05 2014 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6DACECB2 for ; Sat, 15 Nov 2014 21:46:05 +0000 (UTC) Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 37B79BDA for ; Sat, 15 Nov 2014 21:46:05 +0000 (UTC) Received: from dutch.freebsd.net ([172.15.184.248]) by mail.gmx.com (mrgmxus002) with ESMTPSA (Nemesis) id 0M4HBd-1Y6KPg1qzr-00rsRl; Sat, 15 Nov 2014 22:46:04 +0100 Date: Sat, 15 Nov 2014 16:47:11 -0500 From: Dutch Ingraham To: Jan =?ISO-8859-1?Q?Kokem=FCller?= Subject: Re: Xorg configure failure with Radeon card Message-Id: <20141115164711.dc9f2b0b219c604ceff307cf@gmx.us> In-Reply-To: <5467AD77.9060408@gmail.com> References: <5466DD69.5000205@gmx.us> <54673C5D.6040900@gmail.com> <54676567.8090200@gmx.us> <5467A3BE.2060207@gmail.com> <5467A75D.9000605@gmx.us> <5467AD77.9060408@gmail.com> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd10.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K0:ueRoMG31aLYJOkVDwQtvloVwlbgSUaW5D1CaEa4ZBeUoSY7BCov F+FYGmXKtEyBG/uKwYu3zJRzD4uT4gIbIScT+92I07yILFxwlN3F67C1BwdV8WVfexS76G9 btVHeWggYI+hEfyjY4Qkusr/eo/0sHjp5fqJ6xqHiDEBfgEe1je1f3Y7LHk16sim9/a5+ZS n7rh+TW2MvSQOUHfGdhYg== X-UI-Out-Filterresults: notjunk:1; Cc: freebsd-x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2014 21:46:05 -0000 On Sat, 15 Nov 2014 20:45:59 +0100 Jan Kokem=FCller wrote: > > Thanks again, Jan. I already had that there (from the 10.1-RELEASE > > notes), so the error is with that tuner set. >=20 > Does "kldload radeonkms" as root work, as in gives you a nice looking=20 > console in native screen resolution? If that works, at least the KMS=20 > driver does something correctly. >=20 > Another idea is to try to rebuild the "x11-drivers/xf86-video-ati" port,= =20 > if you haven't done that already. >=20 > Can you post the complete contents of /var/log/Xorg.0.log and the output= =20 > of dmesg after a failed attempt to start the X server? >=20 > -Jan Jan!! That's just the wake-up I needed! I went back to the last section o= f the wiki on graphics referred to above and re-read it. For some reason, = I was under the impression that loading the radeon firmware in the method d= escribed in that section was only if I wanted/needed kms to be loaded early= ; I assumed it would be loaded later in the boot process on its own, though= . =20 I was wrong. After issuing a # as you suggested, the fb= graphical resolution loaded. Then, taking wblock@'s advice (elsewhere) th= at Xorg -config is now generally unnecessary, just issued a and th= ings were working properly. A little xrandr action and both monitors are w= orking as desired. For the record, if anyone else is having this radeon issue, here is a summa= ry specific to the 5450 card (note some of this may be unnecessary, I haven= 't tested each yet): In loader.conf kern.vty=3Dvt radeonkmsfw_CEDAR_pfp_load=3D"YES" radeonkmsfw_CEDAR_me_load=3D"YES" radeonkmsfw_CEDAR_rlc_load=3D"YES" radeonkms_load=3D"YES" In make.conf: WITH_NEW_XORG=3DYES WITH_KMS=3DYES OPTIONS_SET=3DGALLIUM (or WITH_GALLIUM=3DYES, but the compiler will warn on= this when building dri) Thanks again for all your help, Jan. --=20 Dutch Ingraham