From owner-freebsd-x11@FreeBSD.ORG Mon Oct 6 11:56:52 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 A3A16F0E for ; Mon, 6 Oct 2014 11:56:52 +0000 (UTC) Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 62FADE6B for ; Mon, 6 Oct 2014 11:56:52 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id i13so3378954qae.13 for ; Mon, 06 Oct 2014 04:56:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=LCVkegnLJC1T33IGBgW/ghnllSXt5LHBjTOvaUags8U=; b=C35aCb132rtYevgcETlcDXjLhfLpDe+gms9UdjpykjcmJQPru7aSxnNhUrAVhvfDXr qYlspB4H9qm8jCJjMfpF8MAR55cu49LDEzCy3su2GUIS6Teas/agXmC6R0PAGzUCd3Uq P5HdeA34D9oY7WqctCNjzC3vF0NaEJlVr96v694cpTQlijiFQ+m71ob2CHtYzn8ldUNH +NEbdJ3lSHu9/n96wJ56EABj718mQDfV7+pRM4epntIfDriV1Uiy3DXYYTEoCkNwpTzG PkF7bluDis0/oiZXSOXefPYSRKIgTMsbSUDWP8CtKvCp6EVuTDOFRe9zX1eNwPhOS17e 0dTg== MIME-Version: 1.0 X-Received: by 10.140.33.230 with SMTP id j93mr3734713qgj.95.1412596611473; Mon, 06 Oct 2014 04:56:51 -0700 (PDT) Received: by 10.229.231.131 with HTTP; Mon, 6 Oct 2014 04:56:51 -0700 (PDT) In-Reply-To: <20141004120652.GF53855@ivaldir.etoilebsd.net> References: <20141004120652.GF53855@ivaldir.etoilebsd.net> Date: Mon, 6 Oct 2014 14:56:51 +0300 Message-ID: Subject: Re: Issue with DRI after latest update From: xtremyst inxtremo To: freebsd-x11@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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: Mon, 06 Oct 2014 11:56:52 -0000 I used WITH_NEW_XORG and rebuild xorg-server and its dependencies, uninstalled xf86-video-ati and build xf86-video-ati-ums but X failed to start, I tried again with Section "DRI" Mode 066 EndSection in my xorg.conf in order to make it work. I got X-server to start but the resolution was much lower (1280*1024 from 1920*1280 that i normally have). I also tried to watch a video on mplayer with xv as video output driver but I couldn't watch the video. It's pretty much the same thing, it acts as if DRI is disabled. PS: When I have KMS disabled and startx fails I have two options, reset again and again until I get it to start or I can disable DRI from xorg.conf and then the issue goes away but cant use xv anymore. What i don't understand is why having DRI enabled makes startx sometimes fail and other times work without me making any changes. If you're interested you can read about this weird behavior on this FreeBSD forum post i started a few months back: https://forums.freebsd.org/viewtopic.php?f=38&t=45545 On Sat, Oct 4, 2014 at 3:06 PM, Baptiste Daroussin wrote: On Sat, Oct 04, 2014 at 02:50:55PM +0300, xtremyst inxtremo wrote: > I think I solved it, I added WITHOUT_NEW_XORG=yes at my /etc/make.conf, > rebuild xorg-server and the xorg-drivers I needed and DRI is enabled again. > With this configuration xorg-server fails to start some times (after startx > I get a blank screen and my monitor turns off so I have to reset my > computer) but that's an old issue I've been dealing with > from the first day I installed FreeBSD. Anyway, I hope this might help > someone else with the same problem. > Best regards! > > On Fri, Oct 3, 2014 at 8:18 PM, xtremyst inxtremo < > xtremyst.in.xtremo@gmail.com> wrote: > > > Hello everyone, I'm fairly new to FreeBSD but really excited about this > > OS. I currently have FreeBSD 10 p9 running on my AMD desktop with ATI 2100 > > as my graphics card. After the latest update (packages updated were > > xf86-video-ati, xorg-server, dri libGL, dri3proto, libglapi, presentproto, > > linxsshmference, xf86-inpu-mouse and xf86-input-keyboard) DRI is disabled > > and I can no longer use xv as video output driver with mplayer. > > > > Running dmesg gives me some errors: > > drmn0: info: WB enabled > > drmn0: info: fence driver on ring 0 use gpu addr 0x0000000060000000 and > > cpu addr 0x0xfffff80007750000 > > info: [drm] Loading RS690/RS740 Microcode > > info: [drm] radeon: ring at 0x0000000060001000 > > error: [drm:pid1976:r100_ring_test] *ERROR* radeon: ring test failed > > (scratch(0x15E4)=0xCAFEDEAD) > > error: [drm:pid1976:r100_cp_init] *ERROR* radeon: cp isn't working (-22). > > drmn0: error: failed initializing CP (-22). > > drmn0: error: Disabling GPU acceleration > > error: [drm:pid1976:r100_cp_fini] *ERROR* Wait for CP idle timeout, > > shutting down CP. > > error: [drm:pid1976:r100_cp_disable] *ERROR* Failed to wait GUI idle while > > programming pipes. Bad things might happen. > > info: [drm] radeon: cp finalized > > info: [drm] radeon_device_init: Taking over the fictitious range > > 0xf0000000-0xf8000000 > > iicbus0: on iicbb0 addr 0xff > > iic0: on iicbus0 > > iicbus1: on iicbb1 addr 0xff > > iic1: on iicbus1 > > iicbus2: on iicbb2 addr 0xff > > iic2: on iicbus2 > > iicbus3: on iicbb3 addr 0xff > > iic3: on iicbus3 > > info: [drm] Radeon Display Connectors > > info: [drm] Connector 0: > > info: [drm] VGA-1 > > info: [drm] DDC: 0x7e50 0x7e40 0x7e54 0x7e44 0x7e58 0x7e48 0x7e5c 0x7e4c > > info: [drm] Encoders: > > info: [drm] CRT1: INTERNAL_KLDSCP_DAC1 > > error: [drm:pid1976:rs600_irq_set] *ERROR* Can't enable IRQ/MSI because no > > handler is installed > > info: [drm] Initialized radeon 2.29.0 20080528 > > > > Also cat /var/log/Xorg.0.log | grep DRI gives me: > > [ 75.845] (II) Loading extension DRI2>> DRI > > [ 75.903] (II) Loading extension XFree86-DRI > > [ 80.166] (II) AIGLX: Screen 0 is not DRI2 capable > > [ 80.166] (II) AIGLX: Screen 0 is not DRI capable > > [ 80.825] (II) GLX: Initialized DRISWRAST GL provider for screen 0 > > > > And finally cat /var/log/Xorg.1.log | grep DRI: > > (II) Loading extension XFree86-DRI > > (II) Loading extension DRI2 > > (II) RADEON(0): [dri] Found DRI library version 1.3.0 and kernel module > > version 1.31.0 > > (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. > > (II) GLX: Initialized DRISWRAST GL provider for screen 0 > > > > Is there anyway to get DRI back? Without it I can't watch any videos > > fullscreen because audio and video get out of sync. > > > ______________________________ > > _________________ > > freebsd-x11@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" > > if you have the ability to try new xorg again, can you try with the ati-ums > driver? > > regards, > Bapt