(Odd. I can't find my own original message in the mailing list archive.
Obviously someone read it, though...)
Homme R. Bitter wrote:
> Are you sure your drm isn't disabled?
When it comes to X, there is very little of which I'm sure. ;-)
However, I don't think it's disabled. My X server log has the
following lines in it:
(0): [drm] installed DRM signal handler
(0): [DRI] installation complete
(II) MGA(0): direct rendering enabled
I can have one instance of "gears" and one instance of "lament"
running at the same time. Gears is running much faster than it ever
did with software rendering. At the same time, lament is slowing to a
crawl - comparatively speaking - as soon as the shape changes from the
> I haven't seen any WindowMaker glitches, could you be more elaborate
> on this? I'd like to see if they appear in my setup too.
The problem was with the WindowMaker menus. Particularly when
right-clicking on icons in the dock. The menu items would use some
part of whatever was on the screen as background, rather than the
gradient specified in the configuration. Highlighting the menu items
would bring them back to normal again.
(The problem with xsnow was that the tree bitmaps looked more like
random data than trees.)
I only saw these problems when DRI was enabled and, as I said, they
appear to be fixed now.
> Well, this being a digital thing, everyone *should* have the same
Assuming everyone has the exact same hardware, I guess...
Anyway, it looks like I was celebrating too early. I woke up at some
horrible hour in the morning to find that X had frozen while displaying
one of the OpenGL screen savers. The only oddity I could find in
kern.log after rebooting was this:
Oct 5 01:45:20 Frihet kernel: [drm] Process 12140 dead (ctx 3, d_s = 0x00)
I don't know how to repeat this, but before I went back to sleep I
noticed that if I start enough instances (somewhere between five and
ten seems to be enough) of "gears" X will lock up. I tried it three
times, and the last messages in kern.log were similar on all three
Oct 5 03:02:43 Frihet kernel: [drm:mga_fire_primary] *ERROR* num_dwords == 0 when dispatched
Oct 5 03:02:45 Frihet last message repeated 89 times
Oct 5 03:24:09 Frihet kernel: [drm:mga_fire_primary] *ERROR* num_dwords == 0 when dispatched
Oct 5 03:24:13 Frihet last message repeated 162 times
Oct 5 03:31:06 Frihet kernel: [drm:mga_fire_primary] *ERROR* num_dwords == 0 when dispatched
Oct 5 03:31:18 Frihet last message repeated 244 times
I guess I should write up a proper bug report for that. Thank heavens
for the magic SysRq key...
I'd say it's still a *lot* better than just a few months ago, though.