From: Dave Jones <davej@redhat.com>
To: Carlo Wood <carlo@alinoe.com>,
linux-kernel@vger.kernel.org, eric@anholt.net,
zhenyu.z.wang@intel.com
Subject: Re: [AGPGART] intel_agp: use table for device probe
Date: Sun, 17 Jun 2007 20:16:27 -0400 [thread overview]
Message-ID: <20070618001627.GA18598@redhat.com> (raw)
In-Reply-To: <20070618000643.GA1375@alinoe.com>
On Mon, Jun 18, 2007 at 02:06:43AM +0200, Carlo Wood wrote:
> On Sun, Jun 17, 2007 at 06:49:18PM -0400, Dave Jones wrote:
> > ok, then you must have CONFIG_AGP=y
>
> I do - not voluntary however. For some mysterious reason I am
> unable to set it to n or m.
You likely have CONFIG_IOMMU set. This makes AGP non-optional.
> I am also not able to set CONFIG_AGP_INTEL
> to n, only to y or m.
> (using make 'menuconfig' for example).
Can't explain that one.
> > > Hence, in the case that the kernel works, intel-agp is loaded
> > > WITHOUT printing this Detected line
> >
> > That doesn't make much sense. The hardware doesn't change between
> > a working & not-working kernel, and somehow the PCI probing fails.
> > Hmm, do you have CONFIG_EDAC set ?
>
> CONFIG_EDAC=m
>
> $ lsmod | grep edac
ok, red herring.
> > There's an outstanding bug (well, lack of feature) , where it claims
> > the PCI device before AGP gets a chance to.
> > This is unrelated to your hang however, but would at least explain
> > the inconsistent probing.
> >
> > > Perhaps my "solution" is to remove this module completely?
> > > I don't seem to need it.
> >
> > It's needed only for 3d,
>
> Nope - I just played UT2004 without problems, and without intel-agp loaded.
Using the nvidia driver? It has its own built-in AGP support which will
get used if the kernel AGP support is missing.
> > but it'd be good to figure out why its so
> > broken on your system, even if you don't need it.
>
> Please tell me what to do / try.
> I'm an experienced coder - but I never really played with the
> kernel before - so you'll have to spell out how to turn on debugging etc.
Right now, I'm at a loss to explain the corruption, so it's
difficult to suggest what to try.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-06-18 0:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 8:02 DRI/AGP on AMD64 based machine Alex Bennee
2007-06-13 16:29 ` Dave Jones
2007-06-14 1:15 ` Carlo Wood
2007-06-14 1:17 ` Dave Airlie
2007-06-14 4:36 ` Carlo Wood
2007-06-14 4:40 ` Dave Airlie
2007-06-17 16:22 ` [AGPGART] intel_agp: use table for device probe Carlo Wood
2007-06-17 19:07 ` Dave Jones
2007-06-17 19:59 ` Carlo Wood
2007-06-17 20:49 ` Dave Jones
2007-06-17 21:13 ` Carlo Wood
2007-06-17 21:33 ` Dave Jones
2007-06-17 21:55 ` Carlo Wood
2007-06-17 22:19 ` Carlo Wood
2007-06-17 22:36 ` Carlo Wood
2007-06-17 22:49 ` Dave Jones
2007-06-18 0:06 ` Carlo Wood
2007-06-18 0:16 ` Dave Jones [this message]
2007-06-18 0:57 ` Dave Airlie
2007-06-18 1:56 ` Carlo Wood
2007-06-18 2:18 ` Dave Airlie
2007-06-18 17:37 ` Carlo Wood
2007-06-18 2:37 ` Wang Zhenyu
2007-06-18 17:42 ` Chuck Ebbert
2007-06-18 18:06 ` Dave Jones
2007-06-18 20:13 ` Carlo Wood
2007-06-18 19:58 ` Carlo Wood
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=20070618001627.GA18598@redhat.com \
--to=davej@redhat.com \
--cc=carlo@alinoe.com \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenyu.z.wang@intel.com \
/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