Issue with DRI after latest update

[xtremyst inxtremo]

I honestly don't know what to say anymore. My last mail describes all the
steps I followed and the results. Since the last hard reset, I booted to my
arch linux installation for a few hours (and sent the previous mail), I
just switched back to FreeBSD, replaced xf86-video-ati-ums with
xf86-video-ati and started X. Everything works great now. When I execute
startx I see the cursor and the square on top left corner for a second,
then they get really small  and X starts normally. I have absolutely no
idea why or how. I rebooted a few times and I still have DRI enabled.

(xtremyst at FreeBSD)~ % pkg info | grep
xf86-video-ati

xf86-video-ati-7.2.0_4         X.Org ati display driver

(xtremyst at FreeBSD)~ % cat /var/log/Xorg.0.log | grep DRI
[    26.792] (II) Loading extension XFree86-DRI
[    26.803] (II) Loading extension DRI2
[    30.832] (II) RADEON(0): [DRI2] Setup complete
[    30.832] (II) RADEON(0): [DRI2]   DRI driver: r300
[    30.832] (II) RADEON(0): [DRI2]   VDPAU driver: r300
[    32.191] (II) GLX: Initialized DRI2 GL provider for screen 0


I updated my ports with portsnap fetch update and I noticed there's an
update on xf86-video-ati but I don't know whether I should update to the
newest version or just keep my system as it is now... because who knows if
I'll have a working DRI after that. I'm trying really hard to find a
logical explanation for all this but I can't think of anything. Is it
possible that building  xf86-video-ati last this time changed something?
It's an issue I've been having for months. I thought I had solved it again
in the past only to find out that the same problem was coming back some
time later.

On Wed, Nov 5, 2014 at 2:50 PM, xtremyst inxtremo <
xtremyst.in.xtremo at gmail.com> wrote:

> I removed xorg.conf and /root/xorg.conf.new, replaced xf86-video-ati with
> xf86-video-ati-ums, rebooted and tried to startx, I could see a cursor in
> the middle of the screen and a white square on the top left corner for a
> couple of seconds and then screen goes blank (sometimes turning off and
> sometimes stays on but completely blank), so I had to reset every time
> (alt+ctrl+del didn't work most of the times).
>
> I also tried to use my old xorg.conf with Driver  "radeon-ums" (no screen
> found), and with Driver "radeon" but got the same behavior.
> I also tried with vesa but resolution was low and DRI seemed again
> disabled (no xv).
> Finally I tried to run Xorg -configure but i got "Configuration failed:
> Number of created screens does not match number of devices detected".
> however it created a xorg.conf.new file in /root with two DevicesSection
> parts, one that stated Driver "radeon" and one with Driver "vesa", I used
> this to startx and it used vesa with the results I mentioned earlier.
>
> On Wed, Nov 5, 2014 at 1:20 PM, Jean-Sébastien Pédron <
> jean-sebastien.pedron at dumbbell.fr> wrote:
>
>> On 04.11.2014 19:00, xtremyst inxtremo wrote:
>> > Don't know how i missed this, running dmesg | grep RADEON_IS gives me:
>> > info: [drm] RADEON_IS_PCI
>>
>> Could you please try with xf86-video-ati-ums? You need to deinstall
>> xf86-video-ati first.
>>
>> I know that the last time you tried it, X failed to start. I think it's
>> because the KMS driver was already loaded and currently, it can't be
>> unloaded when vt(4) is used. You need to reboot then start X.
>>
>> --
>> Jean-Sébastien Pédron
>>
>>
>