From owner-freebsd-x11@FreeBSD.ORG Mon Mar 23 06:56:08 2009 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB9A81065673; Mon, 23 Mar 2009 06:56:08 +0000 (UTC) (envelope-from swell.k@gmail.com) Received: from mail-fx0-f167.google.com (mail-fx0-f167.google.com [209.85.220.167]) by mx1.freebsd.org (Postfix) with ESMTP id 233238FC16; Mon, 23 Mar 2009 06:56:07 +0000 (UTC) (envelope-from swell.k@gmail.com) Received: by fxm11 with SMTP id 11so1537957fxm.43 for ; Sun, 22 Mar 2009 23:56:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:references :date:message-id:user-agent:mime-version:content-type; bh=XCDBMZ3Y8+/yQjOniZyDUxOwX29gOJRGWDPDbYH2QyM=; b=kjdOAKydI1MdmIa6/DLh+82iVBgKtizoZzE2g9I6xbwEwYee4tM94ZKD2i8OzFMT+N SgTSvW/6ulSGgNdJJv6LdIjGWil76RsGDWhMcZui9it+EKIpO+Q2zWSTzfRJf6D3bW9T Mjjeqj95vAbgWqFLWYY9AHnth5vmFlq/aN3sE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:date:message-id:user-agent :mime-version:content-type; b=PERL4o7bN9EF3tY21U+6s2TlugWDWowcpcO7KCxv92WEI8YHRpYtgkGemT8MD/mAPQ 9QXShmk+KrqPASppDsOjqk7daZojASWD41V4a8fIr4A5Kghmq8MF4KZEzfUItdmvdiDD qeCZe9xsxUpeA6vTcx983bqoamLIQaKdgGPXY= Received: by 10.86.95.8 with SMTP id s8mr3321620fgb.79.1237791367063; Sun, 22 Mar 2009 23:56:07 -0700 (PDT) Received: from localhost (95-24-174-59.broadband.corbina.ru [95.24.174.59]) by mx.google.com with ESMTPS id 3sm658778fge.14.2009.03.22.23.56.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 22 Mar 2009 23:56:06 -0700 (PDT) From: Anonymous To: Robert Noland References: <1237680263.1938.10.camel@balrog.2hip.net> <86r60pp8c0.fsf@gmail.com> <1237763230.1694.0.camel@balrog.2hip.net> <86ab7dxf5c.fsf@gmail.com> <1237768535.1712.3.camel@balrog.2hip.net> Date: Mon, 23 Mar 2009 09:55:23 +0300 Message-ID: <86ljqwsp7o.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.91 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-x11 Subject: Re: [PREVIEW] Nouveau on FreeBSD (Take 2) X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Mar 2009 06:56:09 -0000 Robert Noland writes: > On Mon, 2009-03-23 at 03:21 +0300, Anonymous wrote: >> Robert Noland writes: >> >> > On Mon, 2009-03-23 at 00:15 +0300, Anonymous wrote: >> >> Robert Noland writes: >> >> >> >> > 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 running >> >> > for Xv to work. That means xcompmgr, metacity with composite enabled, >> >> > xfce (rumored to work as well, haven't tried). If your running Gnome >> >> > with metacity, open gconf-editor and go to apps->metacity->general and >> >> > check the composite box. >> >> [...] >> >> > >> >> > http://people.freebsd.org/~rnoland/drm-nouveau-032109.patch >> >> > >> >> > robert. >> >> >> >> - This error in Xorg.log is still present >> >> >> >> (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. >> > >> >> Oops, looks like libdrm installed here wasn't latest. Updated and this >> error is gone now. >> >> >> Should I ignore it? >> >> >> >> >> >> info: [drm] PGRAPH_ERROR - nSource:info: [drm] PROTECTION_ERRORinfo: [drm] DMA_R_PROTECTIONinfo: [drm] , nStatus:info: [drm] >> >> 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 >> >> >> >> Should I ignore them? >> >> 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... I can reproduce it on xserver-1.6 just by `X -config test.conf', where test.conf contains nothing but Device section which specifies to use nouveau ddx. I guess it's related to the problem with xcompmgr. They usually appear together. > >> >> >> >> - 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. It's same for xserver-1.6. I guess it's because I usually try to use vt switch when Xserver hangs on restart and then reboot. After reboot xcompmgr doesn't work fine and leaves screen unusable. Workaround is to set hw.drm.msi=0 once and next boot should work fine without it with MSI enabled. > > robert. > >> rebuild kernel, libdrm, xf86-video-nouveau, xserver just in case and >> reproduced the problem again >> http://pastebin.com/m2be24e75 >> http://pastebin.com/m6c80e1e