From: Ken Moffat <ken@kenmoffat.uklinux.net>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-rc1 breaks dri in X-4.3.0
Date: Thu, 7 Aug 2003 22:22:30 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.56.0308072211060.9722@ppg_penguin> (raw)
In-Reply-To: <Pine.LNX.4.44.0308071708390.4303-100000@logos.cnet>
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...
next prev parent reply other threads:[~2003-08-07 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 20:01 Ken Moffat
2003-08-07 20:08 ` Marcelo Tosatti
2003-08-07 20:15 ` Marc-Christian Petersen
2003-08-07 21:22 ` Ken Moffat [this message]
2003-08-07 20:15 ` Marc-Christian Petersen
2003-08-07 21:31 ` Ken Moffat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.56.0308072211060.9722@ppg_penguin \
--to=ken@kenmoffat.uklinux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®