DRM, radeon, and X 4.3

DRM, radeon, and X 4.3

[Andrew S. Johnson]

I start X but it says DRM is disabled, even though the
radeon and agpgart modules are loaded.  Here is the dmesg tail:

Linux agpgart interface v0.100 (c) Dave Jones
[drm] Initialized radeon 1.9.0 20020828 on minor 0
[drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
[drm:radeon_unlock] *ERROR* Process 1929 using kernel context 0

There is something X doesn't like.  How do I fix this?

Andy Johnson

Re: DRM, radeon, and X 4.3

[Damian Kolkowski]

On Thu, Jul 17, 2003 at 05:39:25AM -0500, Andrew S. Johnson wrote:
> There is something X doesn't like.  How do I fix this?

Simply download the:

http://visualisation.tudelft.nl/~cpbotha/files/dri_resume/\
radeon-cpbotha-20030405-linux.DRI.i386.tar.bz2

-- 
# Damian *dEiMoS* Kołkowski # http://deimos.one.pl/ #

Re: DRM, radeon, and X 4.3

[Dave Jones]

On Thu, Jul 17, 2003 at 05:39:25AM -0500, Andrew S. Johnson wrote:
 > I start X but it says DRM is disabled, even though the
 > radeon and agpgart modules are loaded.  Here is the dmesg tail:
 > 
 > Linux agpgart interface v0.100 (c) Dave Jones
 > [drm] Initialized radeon 1.9.0 20020828 on minor 0
 > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
 > [drm:radeon_unlock] *ERROR* Process 1929 using kernel context 0
 > 
 > There is something X doesn't like.  How do I fix this?

Looks like there isn't an agp chipset module also loaded
(via-agp.o, intel-agp.o etc...)

You should have additional text after the first AGP line.

		Dave

Re: DRM, radeon, and X 4.3

[Andrew S. Johnson]

On Thursday 17 July 2003 12:26 pm, Dave Jones wrote:
> On Thu, Jul 17, 2003 at 05:39:25AM -0500, Andrew S. Johnson wrote:
>  > I start X but it says DRM is disabled, even though the
>  > radeon and agpgart modules are loaded.  Here is the dmesg tail:
>  > 
>  > Linux agpgart interface v0.100 (c) Dave Jones
>  > [drm] Initialized radeon 1.9.0 20020828 on minor 0
>  > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
>  > [drm:radeon_unlock] *ERROR* Process 1929 using kernel context 0
>  > 
>  > There is something X doesn't like.  How do I fix this?
> 
> Looks like there isn't an agp chipset module also loaded
> (via-agp.o, intel-agp.o etc...)
> 
> You should have additional text after the first AGP line.
> 
> 		Dave

In the 2.4 kernels, the chipset was compiled in with the agpgart
module.  Now they are separate.  So, yes, modprobe via-agp
did the trick.

How can get the modprobe.conf file to load this module after
agpgart and not crash the system?  My attempts to make this
work using the install command example from the manpage
have been generally disasterous.

Thanks,

Andy Johnson

Re: DRM, radeon, and X 4.3

[Alan Cox]

On Iau, 2003-07-17 at 18:26, Dave Jones wrote:
>  > Linux agpgart interface v0.100 (c) Dave Jones
>  > [drm] Initialized radeon 1.9.0 20020828 on minor 0
>  > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
>  > [drm:radeon_unlock] *ERROR* Process 1929 using kernel context 0
>  > 
>  > There is something X doesn't like.  How do I fix this?
> 
> Looks like there isn't an agp chipset module also loaded
> (via-agp.o, intel-agp.o etc...)

Still shouldnt do that - also the radeon doesn't require AGP

Re: DRM, radeon, and X 4.3

[Rahul Karnik]

Alan Cox wrote:
> On Iau, 2003-07-17 at 18:26, Dave Jones wrote:
> 
>> > Linux agpgart interface v0.100 (c) Dave Jones
>> > [drm] Initialized radeon 1.9.0 20020828 on minor 0
>> > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
>> > [drm:radeon_unlock] *ERROR* Process 1929 using kernel context 0
>> > 
>> > There is something X doesn't like.  How do I fix this?
>>
>>Looks like there isn't an agp chipset module also loaded
>>(via-agp.o, intel-agp.o etc...)
> 
> 
> Still shouldnt do that - also the radeon doesn't require AGP

FWIW, I can reproduce the "problem" here. Perhaps a less cryptic error 
message could be printked.

Thanks,
Rahul

Re: DRM, radeon, and X 4.3

[Andrew S. Johnson]

On Friday 18 July 2003 09:08 am, Rahul Karnik wrote:
> Alan Cox wrote:
> > On Iau, 2003-07-17 at 18:26, Dave Jones wrote:
> > 
> >> > Linux agpgart interface v0.100 (c) Dave Jones
> >> > [drm] Initialized radeon 1.9.0 20020828 on minor 0
> >> > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
> >> > [drm:radeon_unlock] *ERROR* Process 1929 using kernel context 0
> >> > 
> >> > There is something X doesn't like.  How do I fix this?
> >>
> >>Looks like there isn't an agp chipset module also loaded
> >>(via-agp.o, intel-agp.o etc...)
> > 
> > 
> > Still shouldnt do that - also the radeon doesn't require AGP

The radeon module shouldn't require agpgart, as it is supposed
to work with pcigart for PCI versions, but for DRI to work some sort of
hardware module(s) need to be loaded.

> FWIW, I can reproduce the "problem" here. Perhaps a less cryptic error 
> message could be printked.
> 
> Thanks,
> Rahul

I added the modprobe for via-agp to this line in modprobe.conf:

install radeon { /sbin/modprobe agpgart; /sbin/modprobe/via-agp; }; /sbin/modprobe --ignore-install radeon

which works well enough.  However, this line only removes the
radeon module:

remove radeon /sbin/modprobe -r --ignore-remove radeon && { /sbin/modprobe -r via-agp; /sbin/modprobe -r agpgart; /bin/true; }

Even after the radeon module is unloaded, the via-agp module
won't unload because it claims to be in use.  I have to force
unload it.  What could it be hanging on?

Thanks,

Andy Johnson