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 18:49:18 -0400 [thread overview]
Message-ID: <20070617224918.GC12483@redhat.com> (raw)
In-Reply-To: <20070617223649.GA31587@alinoe.com>
On Mon, Jun 18, 2007 at 12:36:49AM +0200, Carlo Wood wrote:
> On Sun, Jun 17, 2007 at 05:33:55PM -0400, Dave Jones wrote:
> > intel-agp
> >
> > Though by the looks of things, with the working kernel, you don't have
> > it loaded (it's dependant upon the 'agpgart' module, which prints the
> > "Detected" line that was missing).
>
> You are wrong.
> I don't have any agpgart module at all, in any of the kernels that I compiled.
ok, then you must have CONFIG_AGP=y
> $ find /lib/modules -name 'agpgart.ko'
> $ /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64 -name '*agp*.ko'
> /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/sis-agp.ko
> /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/intel-agp.ko
> /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/via-agp.ko
>
> 2)
>
> $ strings /lib/modules/2.6.22-rc5-master-188e1f81ba31af1b65a2f3611df4c670b092bbac-amd64/kernel/drivers/char/agp/intel-agp.ko | grep 'agpgart: Detected an Intel'
> <6>agpgart: Detected an Intel %s Chipset.
>
> 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 ?
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, but it'd be good to figure out why its so
broken on your system, even if you don't need it.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-06-17 22:49 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 [this message]
2007-06-18 0:06 ` Carlo Wood
2007-06-18 0:16 ` Dave Jones
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=20070617224918.GC12483@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