Skip to contentSkip to conversation

DRM, radeon, and X 4.3

DISCUSSION Andrew S. Johnson 5 participants 7 messages Jul 17, 2003 – Jul 19, 2003

lore
Share & tools
lore

Andrew S. Johnson

author
#0 lore raw

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

#2 lore raw
In reply to Andrew S. Johnson
Quoted 9 lines · 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?

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

author
#3 lore raw
Quoted 9 lines · Dave Jones
Quoted 8 lines · 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

Quoted 8 lines
Quoted 1 line

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

#4 lore raw
In reply to Dave Jones
Quoted 9 lines · Dave Jones
Quoted 6 lines

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

#5 lore raw
Quoted 7 lines · Alan Cox
Quoted 5 lines · Dave Jones
Quoted 5 lines

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

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

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

author
#6 lore raw
Quoted 8 lines · Rahul Karnik
Quoted 7 lines · Alan Cox
Quoted 5 lines · Dave Jones
Quoted 5 lines

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

Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Quoted 1 line

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.

Quoted 5 lines

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