From: "Markus Hästbacka" <midian@ihme.org>
To: Rahul Karnik <rahul@genebrew.com>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Nforce2
Date: Tue, 09 Sep 2003 21:50:52 +0300 [thread overview]
Message-ID: <1063133451.965.4.camel@midux> (raw)
In-Reply-To: <35272.165.89.84.86.1063127412.squirrel@www.genebrew.com>
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
On Tue, 2003-09-09 at 20:10, Rahul Karnik wrote:
> > Still problems with nvidia-agp on 2.6.0-test5(-mm1). I can't track down
> > the problem because my box needs a hard reboot.
>
> Did it work in previous 2.5/2.6 kernels? Does it work with the built-in
> AGP drivers? (NvAGP=1 I think)
>
> Thanks,
> Rahul
> --
> Rahul Karnik
> rahul@genebrew.com
> http://www.genebrew.com/
Hello Rahul,
No, it havent worked atleast since -test2, because that's when I bought
the new CPU, board and RAM. I'll try to come up with something. This 2.4
is a bit slow with these things, that's why I want to use 2.6, with old
computer there was a noticeable differnce in speed from 2.4 to 2.6. And
for others, I have the patch for nvidia drivers from minion.de. The card
worked _GREAT_ with my old board, untill test2, when I bought my new
board.
Thanks.
--
----
Markus Hästbacka <midian@ihme.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-09 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 13:34 Nforce2 Markus Hästbacka
2003-09-09 17:01 ` Nforce2 Alistair J Strachan
2003-09-09 19:40 ` Nforce2 Markus Hästbacka
2003-09-09 17:10 ` Nforce2 Rahul Karnik
2003-09-09 18:50 ` Markus Hästbacka [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-09 13:46 Nforce2 Jose Luis Alarcon Sanchez
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=1063133451.965.4.camel@midux \
--to=midian@ihme.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rahul@genebrew.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