I've seen people talking about a similar freeze in IRC, and reporting it gets better in latest master. However! I don't know if the symptoms for that were the same root cause as what you had - they may have been related to the callout changes that happened after the 4.0 release that you were running. If you feel lucky, jump to the bleeding edge, and see what happens.
On Sat, Dec 13, 2014 at 1:18 AM, kyuupichan <[email protected]> wrote: > Thanks. Would you say the freezing I experience is down to something wrong > in the Dragonfly kernel module(s), or issues with the X driver itself? > > As I said, the kernel didn't freeze and I could log in remotely, just X froze > (clock not updating, mouse, keyboard unresponsive). Killing X didn't help. > > Neil. > > ---- On Thu, 11 Dec 2014 00:53:54 -0800 Francois Tigeot wrote ---- >>On Wed, Dec 10, 2014 at 08:08:23PM -0800, kyuupichan wrote: >>> Option "NoAccel" in xorg.conf seems to have fixed it as I've now been using >>> X for 20 mins. 2D is noticeably faster than prior kernels; I assume that's >>> a DRI / KMS advantage. >> >>With DragonFly 4.0, radeon KMS support is now enabled by default. The kernel >>driver is similar to the Linux 3.8 version. >> >>The old userland 2D Xorg driver is still available under the name of >>xf86-video-ati-ums if somehow using KMS is more trouble than it's worth >>with a particular graphic chip. >> >>-- >>Francois Tigeot >> >
