Date: Sun, 22 Mar 2009 19:35:35 -0500 From: Robert Noland <rnoland@FreeBSD.org> To: Anonymous <swell.k@gmail.com> Cc: freebsd-x11 <freebsd-x11@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: [PREVIEW] Nouveau on FreeBSD (Take 2) Message-ID: <1237768535.1712.3.camel@balrog.2hip.net> In-Reply-To: <86ab7dxf5c.fsf@gmail.com> References: <1237680263.1938.10.camel@balrog.2hip.net> <86r60pp8c0.fsf@gmail.com> <1237763230.1694.0.camel@balrog.2hip.net> <86ab7dxf5c.fsf@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-wGi3POtlL/YO3AfzmrwC Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2009-03-23 at 03:21 +0300, Anonymous wrote: > Robert Noland <rnoland@FreeBSD.org> writes: >=20 > > On Mon, 2009-03-23 at 00:15 +0300, Anonymous wrote: > >> Robert Noland <rnoland@FreeBSD.org> writes: > >>=20 > >> > Ok, this patch should work on NV50 chips also. > >> > > >> > What you get is EXA and Xv. > >> > > >> > You still need: > >> > > >> > A recent -CURRENT or -STABLE. > >> > > >> > git master of libdrm and xf86-video-nouveau. > >> > > >> > This patch. > >> > > >> > Things I've figured out since the last patch... > >> > > >> > On NV50 class hardware you need to have a compositing manager runnin= g > >> > for Xv to work. That means xcompmgr, metacity with composite enable= d, > >> > xfce (rumored to work as well, haven't tried). If your running Gnom= e > >> > with metacity, open gconf-editor and go to apps->metacity->general a= nd > >> > check the composite box. > >> [...] > >> > > >> > http://people.freebsd.org/~rnoland/drm-nouveau-032109.patch > >> > > >> > robert. > >>=20 > >> - This error in Xorg.log is still present > >>=20 > >> (II) NOUVEAU(0): [DRI] installation complete > >> (EE) NOUVEAU(0): [dri] unable to reference front buffer: -19 > > > > Ok, update your libdrm... this was fixed in the last few days. > > > > robert. > > >=20 > Oops, looks like libdrm installed here wasn't latest. Updated and this > error is gone now. >=20 > >> Should I ignore it? > >>=20 > >>=20 > >> info: [drm] PGRAPH_ERROR - nSource:info: [drm] PROTECTION_ERRORi= nfo: [drm] DMA_R_PROTECTIONinfo: [drm] , nStatus:info: [drm]=20 > >> info: [drm] PGRAPH_ERROR - Ch 2/2 Class 0x8297 Mthd 0x15e0 Data = 0x00000000:0x00000000 > >> error: [drm:pid11:nv50_pgraph_irq_handler] *ERROR* magic set 1: > >> error: [drm:pid11:nv50_pgraph_irq_handler] *ERROR* 0x00408900: = 0x80000000 > >> error: [drm:pid11:nv50_pgraph_irq_handler] *ERROR* 0x00408904: = 0xfdb76b7b > >>=20 > >> Should I ignore them? >=20 > Looks like this one is not fixed in r190296M. Look into logs below. This is a fencing issue, I haven't ported the drm fence manager. Do you know what you are doing to trigger it? I can't seem to make it occur here... > >>=20 > >> - Launching `xcompmgr -a' is tricky. Most of the time it just leaves > >> screen in unusable state, it's not possible to switch to console or > >> move pointer. I want to help debug this one. Here are logs: > >> http://pastebin.com/m1ca3fc2f > >> http://pastebin.com/m579d358e FWIW, I don't seem to have any trouble enabling / disabling composite, so this may be a bug in git xserver or libraries. robert. > rebuild kernel, libdrm, xf86-video-nouveau, xserver just in case and > reproduced the problem again > http://pastebin.com/m2be24e75 > http://pastebin.com/m6c80e1e --=20 Robert Noland <rnoland@FreeBSD.org> FreeBSD --=-wGi3POtlL/YO3AfzmrwC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEABECAAYFAknG2VcACgkQM4TrQ4qfROMjZwCfR1X5hVIQLorYzZ95ibTJd4Xl QqQAnRQWgWEL3ghAd96hGBm21LYSgCfI =wEs0 -----END PGP SIGNATURE----- --=-wGi3POtlL/YO3AfzmrwC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1237768535.1712.3.camel>