From: Robert Love <rml@ufl.edu>
To: Peter Jay Salzman <p@dirac.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: report: success with agp_try_unsupported=1
Date: 24 Sep 2001 17:50:38 -0400 [thread overview]
Message-ID: <1001368244.1194.27.camel@phantasy> (raw)
In-Reply-To: <20010924144006.A13695@dirac.org>
In-Reply-To: <20010924144006.A13695@dirac.org>
On Mon, 2001-09-24 at 17:40, Peter Jay Salzman wrote:
> i just built a system:
>
> 1.3GHz amd athlon
> epox 8kha ddr motherboard
> via kt266 (vt8366, vt8233)
> 768MB ddr ram
> radeon QD with 64MB video buffer, tvio
>
> i enabled agpgart, and got the message:
>
>
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory: 690M
> agpgart: Unsupported Via chipset (device id: 3099), you might want to try
> agp_try_unsupported=1.
> agpgart: no supported devices found.
> [drm] Initialized radeon 1.1.1 20010405 on minor 0
I will write a patch for this to add VIA KT266 support (so you don't
need to do the agp_try_unsupported=1 mess, it will be supported
natively). Although, the patch is going to be against 2.4.10.
I'll send it out in a sec, start downloading 2.4.10 :)
> 2. i recompiled the kernel but built agpgart in rather than loading it as a
> module. i then inserted the following line into /etc/lilo.conf:
>
> append="agp_try_unsupported=1"
>
> but it didn't seem to work. someone told me that to get agp work to work
> for my system, agpgart MUST be built as a module and you MUST pass it the
> argument agp_try_unsupported=1. in other words, you can't build it into
Yes, I believe this is a bug. Maybe I should take a look at it...
agpgart doesn't read the command line, or not correctly, or something.
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next prev parent reply other threads:[~2001-09-24 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-24 21:40 report: success with agp_try_unsupported=1 Peter Jay Salzman
2001-09-24 21:50 ` Robert Love [this message]
2001-09-24 21:59 ` Robert Love
2001-09-25 3:50 ` Keith Owens
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=1001368244.1194.27.camel@phantasy \
--to=rml@ufl.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=p@dirac.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