Apologies if this is a known bug, I'm slightly lost following the list,
and the only bug I can see mentioned seems to be in Alan's tree.
I've just built 2.4.22-rc1 for my PIII (via chipset, radeon 7500), and
rebuilt radeon.o from the X 4.3 release. This combination worked with
2.4.22-pre7 (although with occasional X lock-ups).
In X's log I can see that the radeon module fails to open
/dev/dri/card0 (no such device) and therefore the module load fails.
From dmesg I can see that agpgart detects the chipset and reports the
aperture, but there are zero [drm] messages following.
My .config shows
CONFIG_DRM=y
CONFIG_DRM_NEW=y
CONFIG_DRM_RADEON=m
Ken
--
Peace, love, linux
On Thu, 7 Aug 2003, Ken Moffat wrote:
> Apologies if this is a known bug, I'm slightly lost following the list,
> and the only bug I can see mentioned seems to be in Alan's tree.
>
> I've just built 2.4.22-rc1 for my PIII (via chipset, radeon 7500), and
> rebuilt radeon.o from the X 4.3 release. This combination worked with
> 2.4.22-pre7 (although with occasional X lock-ups).
>
> In X's log I can see that the radeon module fails to open
> /dev/dri/card0 (no such device) and therefore the module load fails.
>
> From dmesg I can see that agpgart detects the chipset and reports the
> aperture, but there are zero [drm] messages following.
Does the DRM module get loaded?
Whats the output of insmod drm.o ?
On Thursday 07 August 2003 22:08, Marcelo Tosatti wrote:
Hi Marcelo,
> Does the DRM module get loaded?
> Whats the output of insmod drm.o ?
drm.o? I think you mean radeon.o ;)
ciao, Marc
On Thursday 07 August 2003 22:01, Ken Moffat wrote:
Hi Ken,
> I've just built 2.4.22-rc1 for my PIII (via chipset, radeon 7500), and
> rebuilt radeon.o from the X 4.3 release. This combination worked with
> 2.4.22-pre7 (although with occasional X lock-ups).
could you please try the DRI sources from XFree cvs repo and see if it makes
any difference? (I'll bet it will)
> In X's log I can see that the radeon module fails to open
> /dev/dri/card0 (no such device) and therefore the module load fails.
Sounds like radeon.i isn't loaded.
> From dmesg I can see that agpgart detects the chipset and reports the
> aperture, but there are zero [drm] messages following.
> My .config shows
> CONFIG_DRM=y
> CONFIG_DRM_NEW=y
> CONFIG_DRM_RADEON=m
do you have radeon.o loaded? "lsmod|grep radeon"
What does dmesg say if it should autoloads the module when you start X?
(assuming you have autoload support enabled)
ciao, Marc
On Thu, 7 Aug 2003, Marcelo Tosatti wrote:
>
>
> On Thu, 7 Aug 2003, Ken Moffat wrote:
>
> > Apologies if this is a known bug, I'm slightly lost following the list,
> > and the only bug I can see mentioned seems to be in Alan's tree.
> >
> > I've just built 2.4.22-rc1 for my PIII (via chipset, radeon 7500), and
> > rebuilt radeon.o from the X 4.3 release. This combination worked with
> > 2.4.22-pre7 (although with occasional X lock-ups).
> >
> > In X's log I can see that the radeon module fails to open
> > /dev/dri/card0 (no such device) and therefore the module load fails.
> >
> > From dmesg I can see that agpgart detects the chipset and reports the
> > aperture, but there are zero [drm] messages following.
>
> Does the DRM module get loaded?
>
> Whats the output of insmod drm.o ?
>
drm is built in, only radeon.o is a module. Bizarrely (I rebooted
before the original mail, in case something was hanging on to a file and
stopping it loading), this time it loads.
insmod radeon now gives me
[drm] AGP 0.99 aperture @ 0xe8000000 64MB
[drm] Initialized radeon 1.7.0 20020828 on minor 0
It looks as if I had a problem with depmod, insmod was failing until I
reran depmod -a, and yet that is at the end of my script for rebuilding
the X modules. Sorry this turns out to be a bogus report.
Ken
--
I never wanted to be a tester. I wanted to be a lumberjack...
On Thu, 7 Aug 2003, Marc-Christian Petersen wrote:
>
> do you have radeon.o loaded? "lsmod|grep radeon"
>
> What does dmesg say if it should autoloads the module when you start X?
> (assuming you have autoload support enabled)
>
Looks as if it was some sort of error on my part, it's now running
nicely. I had to [re] run depmod -a. After a further reboot to prove
this has fixed it, radeon.o is definitely being autoloaded in startx.
Thanks anyway.
Ken
--