From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C8034138247 for ; Mon, 11 Nov 2013 16:42:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3D796E0B9B; Mon, 11 Nov 2013 16:41:52 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0E223E0B72 for ; Mon, 11 Nov 2013 16:41:50 +0000 (UTC) Received: from marcec ([178.25.242.3]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0M3vCA-1VP4Od1pre-00raiE for ; Mon, 11 Nov 2013 17:41:49 +0100 Date: Mon, 11 Nov 2013 17:41:55 +0100 From: Marc Joliet To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Which Radeon Firmware? Message-ID: <20131111174155.43073a96@marcec> In-Reply-To: <20131111150323.GA1899@hp-workstation.v.cablecom.net> References: <20131111125941.GA1978@hp-workstation.v.cablecom.net> <20131111142812.GC32524@server> <20131111150323.GA1899@hp-workstation.v.cablecom.net> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.17; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/Zye94V9PkfuVCRgxYYtAYwz"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:6krttCc8NWOuRpq3mhxhLvjKspzul9U7SQ4ysZ5o5HQbmvTUsP5 GwMeH7IbV0uwWciZooFhQXpthG/x5gtp1zHU0mJ8sBDvetFl92FuYSwS7C1ZeQ1JrXifMOE EiQrPKGMJ0ObHrbx+r2aoUi1FAlCXzaUap6WweUOqUGNmGltMz1M1OtEwjM3UM7HIoev009 mBLrG7s6YSTo3sUy9PYXg== X-Archives-Salt: b29ab1a1-2b18-4931-a023-4beee989f1e3 X-Archives-Hash: a31187f9c13caa12428c763d4ed0ccd2 --Sig_/Zye94V9PkfuVCRgxYYtAYwz Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Mon, 11 Nov 2013 16:03:23 +0100 schrieb Elias Diem : > Hi Bruce >=20 > On 2013-11-11, Bruce Hill wrote: >=20 > > If you have CONFIG_DRM_RADEON=3Dm, and > > CONFIG_EXTRA_FIRMWARE_DIR=3D"/lib/firmware/", then the kernel will pick= the > > right firmware automatically, without having to name the microcode in > > CONFIG_EXTRA_FIRMWARE at all. >=20 > Yes, thank you. It worked. >=20 > > Build your kernel that way and see which firmware shows up issuing: > > dmesg | grep -i firmware >=20 > Unfortunately I can't figure it out. >=20 > 'dmesg | grep -i firmware' doesn't return anything. You need to grep for "microcode", not "firmware". On my system I see: % dmesg |grep -i microcode [ 18.890581] [drm] Loading RV730 Microcode > 'dmesg | grep -i radeon' returns: >=20 > > [ 0.030492] smpboot: CPU0: AMD A8-5500B APU with Radeon(tm) HD Graphic= s (fam: 15, model: 10, stepping: 01) > [ 4.600599] [drm] radeon kernel modesetting enabled. > [ 4.601157] radeon 0000:00:01.0: VRAM: 768M 0x0000000000000000 - 0x000= 000002FFFFFFF (768M used) > [ 4.601159] radeon 0000:00:01.0: GTT: 512M 0x0000000030000000 - 0x0000= 00004FFFFFFF > [ 4.601693] [drm] radeon: 768M of VRAM memory ready > [ 4.601694] [drm] radeon: 512M of GTT memory ready. > [ 4.881482] radeon 0000:00:01.0: WB enabled > [ 4.881485] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0= x0000000030000c00 and cpu addr 0xffff880223f0dc00 > [ 4.882218] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0= x0000000000075a18 and cpu addr 0xffffc900114b5a18 > [ 4.882220] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0= x0000000030000c04 and cpu addr 0xffff880223f0dc04 > [ 4.882222] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0= x0000000030000c08 and cpu addr 0xffff880223f0dc08 > [ 4.882223] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0= x0000000030000c0c and cpu addr 0xffff880223f0dc0c > [ 4.882225] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0= x0000000030000c10 and cpu addr 0xffff880223f0dc10 > [ 4.882245] radeon 0000:00:01.0: irq 45 for MSI/MSI-X > [ 4.882255] radeon 0000:00:01.0: radeon: using MSI. > [ 4.882534] [drm] radeon: irq initialized. > [ 5.023269] [drm] Radeon Display Connectors > [ 5.044982] [drm] radeon: power management initialized > [ 5.165005] fbcon: radeondrmfb (fb0) is primary device > [ 5.231602] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device > [ 5.231604] radeon 0000:00:01.0: registered panic notifier > [ 5.231608] [drm] Initialized radeon 2.33.0 20080528 for 0000:00:01.0 = on minor 0 > That doesn't look too different from my dmesg output. Your last line is alm= ost identical to my system. However, if Bruce is correct, you'll have to try the proprietary drivers (at least for 3D support, I suspect it'll work fine otherwise). HTH --=20 Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup --Sig_/Zye94V9PkfuVCRgxYYtAYwz Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlKBCN8ACgkQBsMBz3L8+WM3awCfaAdAIVpYnM7kCIhFSEB8YOEe iQ0An1/2Df6xACttZRHtyq5HZPgWBiPa =Zo1H -----END PGP SIGNATURE----- --Sig_/Zye94V9PkfuVCRgxYYtAYwz--