Bug#587999: further info

[Michel Dänzer]

On Mon, 2010-07-05 at 23:14 +0200, Ulrich Eckhardt wrote: 
> On Monday 05 July 2010 09:03:53 you wrote:
> > On Sam, 2010-07-03 at 23:58 +0200, Ulrich Eckhardt wrote:
> > > (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
> > > [dri] Disabling DRI.
> > 
> > It should work better with the DRI enabled.
> 
> Good catch, but shouldn't it work even without DRI?

It should, if someone were to fix the problem(s) with the non-DRI big
endian XVideo code paths. DRI is generally desirable anyway though as it
provides significantly better performance across the board.


> > If so, please post the output of running
> > 
> > sudo modprobe radeon
> > 
> > as well as the messages appearing in the dmesg output after it.
> 
> The module is already loaded. I can unload it though, even with a running X11 
> session, "lsmod" shows that its refcount is zero. When loading it, it outputs 
> "[drm] radeon kernel modesetting enabled." in dmesg. However, when starting 
> the X server, it outputs "radeonfb 0000:00:10.0: Invalid ROM contents" there.

Looks like radeonfb is preventing the radeon kernel module from working
with kernel modesetting (KMS). Disable radeonfb or load radeon with
modeset=0.


P.S. To fellow upstream radeon developers: In this case it would
probably be more useful to initialize the DRM without KMS?

-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer