From owner-freebsd-x11@FreeBSD.ORG Mon Mar 11 14:10:21 2013 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 58D2238A for ; Mon, 11 Mar 2013 14:10:21 +0000 (UTC) (envelope-from akirchhoff135014@comcast.net) Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by mx1.freebsd.org (Postfix) with ESMTP id 0B1B060D for ; Mon, 11 Mar 2013 14:10:20 +0000 (UTC) Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta02.westchester.pa.mail.comcast.net with comcast id ABaf1l0061YDfWL51EALSn; Mon, 11 Mar 2013 14:10:20 +0000 Received: from unknown ([50.78.52.49]) by omta20.westchester.pa.mail.comcast.net with comcast id AEAK1l01J13hoka3gEALV4; Mon, 11 Mar 2013 14:10:20 +0000 Date: Mon, 11 Mar 2013 10:10:05 -0400 From: Adam K Kirchhoff To: "J.R. Oldroyd" Subject: Re: New AMD drm code Message-ID: <20130311101005.000007d1@unknown> In-Reply-To: <20130311001858.61224bf6@shibato> References: <20130311001858.61224bf6@shibato> X-Mailer: Claws Mail 3.8.0cvs30 (GTK+ 2.16.6; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1363011020; bh=A5v1O2Rw+0ghJX7MXRhvy+JqD4zxo8F61VaFSvHwBWw=; h=Received:Received:Date:From:To:Subject:Message-ID:Mime-Version: Content-Type; b=chCBPkc4qbp0iE0RJwfAlAb7GR4tgb61PnXj54smwlXLIub5c5DRfpiQoNXyuhHAO OkHGZ1F9ErcGrDIhNa1lk5EtsJmPWqry75ImD6oAo5QXk2URwroBC5LpOww+HiMBOF afEVabWJFj0kJS5uzXicmoDztclx8sc3TdCIVwGKc1MWPJeNx9waXPoDFqCKdVPBV2 Ckra73IaXGAXexREoZ8RClEv5yBk066undTWpLmiXB2usznc3Y35viwmZuF1VsWcvU KTf8wQ/E5Dhsk1RCgpk2XIX1tbMe9fBOqiIktJRh/0pNnBTL1cE8uUO5NhFZkwNbCv QMnRMkhZSQAqw== Cc: "freebsd-x11@freebsd org" , =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 14:10:21 -0000 On Mon, 11 Mar 2013 00:18:58 -0400 "J.R. Oldroyd" wrote: > On Sun, 10 Mar 2013 20:39:46 -0400 Adam K Kirchhoff > wrote: > > > >=20 > > I'm wondering if there is some secret to getting the new radeon drm > > code up and running. I realize it's currently very experimental, > > but I have a number of machines and cards I can test with.=20 > >=20 > > I've tried using both a standard -CURRENT kernel and one built from > > here:=20 > >=20 > > https://github.com/dumbbell/freebsd > >=20 > > However, in both cases, the radeon kernel module does not attach to > > my HD6950 when I load it. In fact, a quick look at > > ways/dev/drm2/drm_pciids.h doesn't seem to show any newer Radeon HD > > gpus. > >=20 > > I have the feeling I'm missing something obvious.. > >=20 > > Thanks. > >=20 > > Adam >=20 > Jean-S=E9bastien has the code working on -current, and I just about > have it working on 9.1-release. >=20 > For both, you'll need the sys/dev/drm2 code from his git (at the > URL you gave above), not the code in head. >=20 > For 9.x, you'll also need a handful of changes to sys/vm and > sys/dev/iicbus and probably another bugfix or two that we haven't > worked out yet. I can send this as a diff to anyone who's > interested. >=20 > Your Cayman PRO is there in the drm_pciids.h file (line 491), so > it is supported in the original Linux code. There's a lot of code > specific to the cayman cards, however not all of it may have been > ported yet. If you see lots of "#ifdef DUMBBELL_WIP"s in the > cayman code, that means work is still to be done. OK, I am definitely missing something, because https://github.com/dumbbell/freebsd/blob/master/sys/dev/drm2/drm_pciids.h shows that line 491 is blank, which is the same thing I'm seeing on my checked out version. > You could post your dmesg to show what's happening when you load > the module. Nothing happens. kldstat shows that the radeon module gets loaded, but nothing shows up in dmesg. > Note that if the module loads ok, syscons goes blank because there > is no support in it for KMS yet. You'll need to ssh in to start > an X server or run a script to both load the module and start X. Yeah, the screen never goes blank here. Is there something that has to be done with the code in sys/dev/drm2/ before it can be used? Adam