From: Jesse Pollard <jesse@cats-chateau.net>
To: I Am Falling I Am Fading <skuld@anime.net>,
Dave Jones <davej@codemonkey.org.uk>
Cc: John Bradford <john@grabjohn.com>, <gregor.essers@web.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: Via KT400 and AGP 8x Support
Date: Fri, 13 Jun 2003 07:52:57 -0500 [thread overview]
Message-ID: <03061307525700.13701@tabby> (raw)
In-Reply-To: <Pine.LNX.4.44.0306120633490.14263-100000@inconnu.isu.edu>
On Thursday 12 June 2003 07:36, I Am Falling I Am Fading wrote:
> On Thu, 12 Jun 2003, Dave Jones wrote:
> > > Tried it already... The pins are too small to get adequate purchase
> > > for the tape -- the friction just causes it to slide around in the
> > > slot and gets goo around.
> > >
> > > Superglue might be a better solution....
> > > ...but I think the solder method is better.
> >
> > So rather than experiment with backporting the 2.5 code to 2.4,
> > you'd rather risk damaging your hardware ?
> >
> > I think this way is madness.
>
> Unfortunately even a perfect backport seems to be only a partial solution
> -- the ATI binary only drivers don't seem to know how to talk to the 2.5
> AGP 3.0 stuff anyway (well, at least they didn't work at all when I tried
> them under the 2.5 kernel :-/), and as they are lame binary-only drivers
> there is no way to fix that.
>
> There are also no other drivers for the R300-series Radeon GPUs. :-(
>
> This absolutely sucks, but turning the card into an AGP 2.0 card seems to
> be the only surefire way to get it to work properly under Linux. :-(
I'm not sure this will help the hardware situation, but you could try a
bus extender (it will make the board stick out of the slot a couple of
inches).
It should allow you the option of either cutting the extender wire traces
or pull jumpers to see if things do work.
next prev parent reply other threads:[~2003-06-13 12:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 8:27 Via KT400 and AGP 8x Support John Bradford
2003-06-12 11:15 ` I Am Falling I Am Fading
2003-06-11 12:19 ` Gregor Essers
2003-06-11 13:18 ` Gregor Essers
2003-06-12 14:50 ` Dave Jones
2003-06-12 12:30 ` I Am Falling I Am Fading
2003-06-12 12:30 ` Dave Jones
2003-06-12 12:36 ` I Am Falling I Am Fading
2003-06-13 12:52 ` Jesse Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-12 14:02 Alex Deucher
2003-06-11 15:06 Alex Deucher
2003-06-11 15:56 ` Dave Jones
2003-06-11 21:26 ` Alex Deucher
2003-06-11 22:36 ` Toplica Tanasković
2003-06-11 22:53 ` Dave Jones
2003-06-12 0:44 ` Toplica Tanasković
2003-06-12 5:53 ` Dave Jones
2003-06-11 8:28 I Am Falling I Am Fading
2003-06-11 9:44 ` Dave Jones
2003-06-12 1:34 ` I Am Falling I Am Fading
2003-06-11 1:14 Gregor Essers
2003-06-11 9:41 ` Dave Jones
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=03061307525700.13701@tabby \
--to=jesse@cats-chateau.net \
--cc=davej@codemonkey.org.uk \
--cc=gregor.essers@web.de \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skuld@anime.net \
/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