From: Stuffed Crust <pizza@shaftnet.org>
To: linux-kernel@vger.kernel.org
Subject: BUG: broken I830MP AGP support in 2.4.17 and 2.4.18pre7
Date: Thu, 31 Jan 2002 00:28:55 -0500 [thread overview]
Message-ID: <20020131002855.A10415@shaftnet.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]
I'm blessed with a new Dell Inspiron 4100, which is in turn blessed with
the i830MP AGP chipset. It's identical to the i830M except it doesn't
have the on-chip graphics controller.
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.
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
So it appears not all is well with the I830MP patch.
(Yes, I have tried the 'agp_unsupported' option in both cases)
- Pizza
--
Solomon Peachy pizzaATfucktheusers.org
I ain't broke, but I'm badly bent. ICQ# 1318344
Patience comes to those who wait.
...It's not "Beanbag Love", it's a "Transanimate Relationship"...
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-01-31 5:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 5:28 Stuffed Crust [this message]
[not found] <fa.g3ut1lv.1q56hbd@ifi.uio.no>
2002-01-31 9:14 ` BUG: broken I830MP AGP support in 2.4.17 and 2.4.18pre7 Nicolas Aspert
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=20020131002855.A10415@shaftnet.org \
--to=pizza@shaftnet.org \
--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