From: Nicolas Aspert <Nicolas.Aspert@epfl.ch>
To: Stuffed Crust <pizza@shaftnet.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: broken I830MP AGP support in 2.4.17 and 2.4.18pre7
Date: Thu, 31 Jan 2002 10:14:00 +0100 [thread overview]
Message-ID: <3C590AD8.2050908@epfl.ch> (raw)
In-Reply-To: <fa.g3ut1lv.1q56hbd@ifi.uio.no>
Stuffed Crust wrote:
> When trying to load up the agpgart module under 2.4.17, I get:
>
>
>>Linux agpgart interface v0.99 (c) Jeff Hartmann
>>agpgart: Maximum main memory to use for agp memory: 262M
>>agpgart: Detected an Intel 830M, but could not find the secondary device.
>>
This is normal. 2.4.17 does not support i830MP.
> Fine, I see that 2.4.18pre supposedly has fixes for the I830MP. So I
> compile it, slap it in place.. and get: (with 2.4.17pre7)
>
>
>>Linux agpgart interface v0.99 (c) Jeff Hartmann
>>agpgart: Maximum main memory to use for agp memory: 262M
>>agpgart: unsupported bridge
>>agpgart: no supported devices found.
>>
>
> lspci yields:
>
>>00:00.0 Host bridge: Intel Corporation: Unknown device 3575 (rev 02)
>> Flags: bus master, fast devsel, latency 0
>> Memory at d0000000 (32-bit, prefetchable) [size=256M]
>> Capabilities: [40] #09 [0105]
>> Capabilities: [a0] AGP version 2.0
>>
>
This is much stranger... And even if the 830mp stuff does not work
(several people have been able to use it), loading the agpgart module
with the 'try_unsupported=1' option should do the trick (at least in
2.4.18-pre7)... Can you send the full output of lspci ?
Best regards.
Nicolas.
--
Nicolas Aspert Signal Processing Institute (ITS)
Swiss Federal Institute of Technology (EPFL)
next parent reply other threads:[~2002-01-31 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.g3ut1lv.1q56hbd@ifi.uio.no>
2002-01-31 9:14 ` Nicolas Aspert [this message]
2002-01-31 5:28 BUG: broken I830MP AGP support in 2.4.17 and 2.4.18pre7 Stuffed Crust
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=3C590AD8.2050908@epfl.ch \
--to=nicolas.aspert@epfl.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=pizza@shaftnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.