Issue with DRI after latest update

Mon Nov 3 18:50:22 UTC 2014

I'm terribly sorry Baptiste, I missed your last post.
Some additional info
dmesg: http://pastebin.com/FJBVAJVv
pciconf -lvbce: http://pastebin.com/mCbYMZrM
devinfo -vr: http://pastebin.com/NZUBveND
pkg info: http://pastebin.com/rAWM9CaZ
and my xorg.conf: http://pastebin.com/wEVqhM9n

On Mon, Nov 3, 2014 at 8:33 PM, xtremyst inxtremo <
xtremyst.in.xtremo at gmail.com> wrote:

> Sorry to bring back an older post but since the last update of xorg-server
> and xf86-video-ati I get an even stranger behavior. Although I still have
> WITHOUT_NEW_XORG="YES" in my /etc/make.conf, It looks like it doesn't have
> any result... or almost no result. If I rebuild x11-servers/xorg-server
> before starting X and then execute startx, I always get a working X server
> with DRI and KMS, and that's fantastic. However if I reboot, my system
> starts with KMS enabled and DRI disabled (that means I can no longer use xv
> as video output driver and It's almost impossible to watch any video
> fullscreen). I can't think of a logical explanation for this kind of
> behavior...  Here's my Xorg.0.log when I start X right after rebuilding the
> xorg-server: http://pastebin.com/w2Ln3H6V
> And here's my Xorg.0.log when I reboot and DRI no longer works:
> http://pastebin.com/BijaXVka. I believe that the interesting part is in
> line 377, after reboot, instead of loading dri2 i get "GPU accel disabled
> or not working, using shadowfb for KMS".
> Any ideas will be greatly appreciated
> Best regards
>
>
> On Mon, Oct 6, 2014 at 2:56 PM, xtremyst inxtremo <
> xtremyst.in.xtremo at gmail.com> wrote:
>
>> 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 <bapt at freebsd.org>
>> 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 at 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: <Philips I2C bus> on iicbb0 addr 0xff
>> > > iic0: <I2C generic I/O> on iicbus0
>> > > iicbus1: <Philips I2C bus> on iicbb1 addr 0xff
>> > > iic1: <I2C generic I/O> on iicbus1
>> > > iicbus2: <Philips I2C bus> on iicbb2 addr 0xff
>> > > iic2: <I2C generic I/O> on iicbus2
>> > > iicbus3: <Philips I2C bus> on iicbb3 addr 0xff
>> > > iic3: <I2C generic I/O> 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 at freebsd.org mailing list
>>> > http://lists.freebsd.org/mailman/listinfo/freebsd-x11
>>> > To unsubscribe, send any mail to "freebsd-x11-unsubscribe at freebsd.org"
>>>
>>> if you have the ability to try new xorg again, can you try with the
>>> ati-ums
>>> driver?
>>>
>>> regards,
>>> Bapt
>>
>>
>