From: Abraham vd Merwe <abraham@2d3d.co.za>
To: Didier Moens <Didier.Moens@dmb001.rug.ac.be>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: Re: OOPS in agpgart (2.4.13, 2.4.15pre7)]
Date: Tue, 27 Nov 2001 11:10:22 +0200 [thread overview]
Message-ID: <20011127111022.B881@crystal.2d3d.co.za> (raw)
In-Reply-To: <linux.kernel.3C021570.4000603@dmb.rug.ac.be> <3C022BB4.7080707@epfl.ch> <1006808870.817.0.camel@phantasy> <3C02BF41.1010303@xs4all.be> <20011127101148.C5778@crystal.2d3d.co.za> <3C034CAE.2090103@dmb.rug.ac.be>
In-Reply-To: <3C034CAE.2090103@dmb.rug.ac.be>; from Didier.Moens@dmb001.rug.ac.be on Tue, Nov 27, 2001 at 09:19:58 +0100
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
Hi Didier!
I misunderstood. I thought you have an on-board 830M video card :P
So you have an 830M motherboard, with a Radeon display card?
> >
> >
> > VideoRam "65536"
> >
>
> Are you sure about this ? I only have 32 MB.
As I said, I misunderstood. I thought you were using the i810 display driver
and I wanted to see what happens if you force the GART module to allocate
some additional system memory.
> Should this be tested with both patches ? I'm getting several
> suggestions about this problem : the possible permutations are
> augmenting, and I have some work to do too ... :)
If you have a Radeon display card and an 830M motherboard chipset, it might
be that the agpgart module is trying to use the 830M display chipset code.
that would definitely cause problems.
Before applying any patches, make sure that you have selected the following
[*] Intel 440LX/BX/GX and I815/I830M/I840/I850 support
(i.e. CONFIG_AGP_INTEL=y)
when compiling the kernel, but NOT!!!!! the following:
[ ] Intel I810/I815/I830M (on-board) support
(i.e. CONFIG_AGP_I810=n)
If the agpgart module then crashes when you load it, there is a bug and you
should send me/kernel mailinglist the oops.
As for display problems, you should ask on the dri-devel mailinglist which
is the proper place to post display driver bugs. (If it we're the i810
display driver I could help you)
--
Regards
Abraham
Don't drink when you drive -- you might hit a bump and spill it.
__________________________________________________________
Abraham vd Merwe - 2d3D, Inc.
Device Driver Development, Outsourcing, Embedded Systems
Cell: +27 82 565 4451 Snailmail:
Tel: +27 21 761 7549 Block C, Antree Park
Fax: +27 21 761 7648 Doncaster Road
Email: abraham@2d3d.co.za Kenilworth, 7700
Http: http://www.2d3d.com South Africa
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-11-27 9:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <linux.kernel.3C021570.4000603@dmb.rug.ac.be>
2001-11-26 11:47 ` Nicolas Aspert
2001-11-26 12:43 ` [PATCH]Re: " Nicolas Aspert
2001-11-26 21:07 ` Robert Love
2001-11-26 22:16 ` Didier Moens
2001-11-27 7:57 ` Nicolas Aspert
[not found] ` <20011127101148.C5778@crystal.2d3d.co.za>
[not found] ` <3C034CAE.2090103@dmb.rug.ac.be>
2001-11-27 9:10 ` Abraham vd Merwe [this message]
2001-11-27 9:52 ` Didier Moens
2001-11-27 10:05 ` Nicolas Aspert
2001-11-27 10:48 ` Didier Moens
2001-11-27 12:10 ` Stephan von Krawczynski
2001-11-27 11:12 ` Stephan von Krawczynski
2001-11-27 11:43 ` Nicolas Aspert
2001-11-27 12:49 ` Didier Moens
2001-11-27 10:51 ` Stephan von Krawczynski
2001-11-26 10:12 Didier Moens
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=20011127111022.B881@crystal.2d3d.co.za \
--to=abraham@2d3d.co.za \
--cc=Didier.Moens@dmb001.rug.ac.be \
--cc=linux-kernel@vger.kernel.org \
/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®