From: Sheng Long Gradilla <skamoelf@netscape.net>
To: Toplica Tanaskovic <toptan@EUnet.yu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AGP 3.0 for 2.4.21-pre5
Date: Mon, 17 Mar 2003 00:21:04 -0800 [thread overview]
Message-ID: <3E758570.5090003@netscape.net> (raw)
In-Reply-To: 200303170008.41525.toptan@EUnet.yu
I did. If I patch the kernel, my compiling procedure is always as follows:
==================
make clean
make mrproper
make menuconfig
make dep
make modules
make bzlilo
make modules_install
shutdown -r now
==================
The module loads fine. In /var/log/messages there are reports of
detecting AGP 3.5 compatible hardware, but as I said, X just won't start
properly and will report AGP 4X mode.
I checked /proc/driver/nvidia, and it reports AGP 8X hardware and
everything.
I was thinking, I have not tested the nvidia kernel module with the 2.5
kernel. There is an unofficial patch for getting it to compile. I might
give it a try to see if it works, but that won't happen soon.
If anyone wants to give it a try, visit:
http://www.minion.de/nvidia.html
Toplica Tanaskovic wrote:
> Dana nedelja 16. mart 2003. 17:54 napisali ste:
>
>>I tested it with my NVidia GeForce 4 Ti4200 with AGP8X. No luck for me
>>yet. X is still reporting AGP 4X in the log, I get garbage on the screen
>>and my PC locks up.
>>
>>I am not sure if this has something to do with the NVidia driver for X,
>>or just a bug in your module/backport.
>>
>
> You have to run make clean first, or faster way go to
drivers/char/agp/ and
> delete any .o files, and then do make modules...
>
> I'll have to figure out way to force compilation of agpgart if
only agp 3.0
> menu item was changed.
prev parent reply other threads:[~2003-03-17 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-15 17:17 AGP 3.0 for 2.4.21-pre5 Toplica Tanasković
[not found] ` <3E74AC3B.6070404@netscape.net>
2003-03-16 23:08 ` Toplica Tanaskovic
2003-03-17 5:57 ` Willy Tarreau
2003-03-17 8:21 ` Sheng Long Gradilla [this message]
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=3E758570.5090003@netscape.net \
--to=skamoelf@netscape.net \
--cc=linux-kernel@vger.kernel.org \
--cc=toptan@EUnet.yu \
/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