public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sheng Long Gradilla <skamoelf@netscape.net>
To: "Toplica Tanasković" <toptan@EUnet.yu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AGP backport from 2.5 to 2.4.21-pre4
Date: Sun, 23 Feb 2003 12:05:47 -0800	[thread overview]
Message-ID: <3E59299B.8090200@netscape.net> (raw)
In-Reply-To: 200302231921.27024.toptan@EUnet.yu

The "other kernels" I am talking about are 2.4.19 and 2.4.20 with the 
old agpgart. As I said, the new agpgart module now loads but the results 
are the same. I yet have to try some other tricks like setting the AGP 
rate manually.

I am also using the latest nvidia modules, which are 1.0-4191


- Sheng Long Gradilla

Toplica Tanasković wrote:
> Dana nedelja 23. februar 2003. 17:02 napisali ste:
> 
>>I tested on an Asus A7V8X motherboard (KT400) with a GeForce4 Ti 4200
>>AGP8X. The module loads correctly, at last! It sets the apperture size
>>correctly and all, but when I start XFree, I get do not get any
>>graphical screen, but text mode garbage. Characters of all colors, with
>>no sense at all. I had exactly the same problem in other kernels.
>>
> 
>     What kernels? Are you using old agpgart or new one with other kernels?
> 
> 
>>I played a bit with the NvAGP option on XF86Config file. According to
>>the documentation, 0 is PCI mode, 1 is NvAGP or fallback to PCI if
>>failed, 2 is AGPGART mode or fallback to PCI if failed, 3 is autodetect.
>>If I set it to 2, 3 or comment it, I got the same problem with the
>>garbage and had to reset the PC. Setting it to 0 would make it run in
>>PCI mode, and it always works. I tried setting it to 1, thinking that
>>maybe the documentation is wrong. X started successfully, but the card
>>was in PCI mode. I read the logs to confirm it, and indeed, the NvAGP
>>module fails to identify the AGP chipset and falls back to PCI.
>>
>>I tried setting NvAGP to 2 again, to read the logs and see if there is
>>something I could find out, but unfortunately the log had nothing but
>>garbage. I tried several times with no success. The log is always garbage.
>>
> 
>     Try fetching latest nVidia drivers.
> 
>     I'll try to isolate problem, and send patch if neccessery.
> 
> 
>>- Sheng Long Gradilla
> 
> 


  reply	other threads:[~2003-02-23 19:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-21  4:40 AGP backport from 2.5 to 2.4.21-pre4 Toplica Tanasković
2003-02-21 13:40 ` Dave Jones
2003-02-22  6:20   ` Toplica Tanasković
2003-02-22 23:07     ` Edward Killips
2003-02-23 13:50       ` Toplica Tanasković
2003-02-23 16:02         ` Sheng Long Gradilla
2003-02-23 18:21           ` Toplica Tanasković
2003-02-23 20:05             ` Sheng Long Gradilla [this message]
2003-02-23 20:36               ` Toplica Tanasković
2003-02-23 21:51                 ` Bryan Andersen
2003-02-24  2:01                   ` Toplica Tanasković
2003-02-23 18:46         ` Edward Killips
2003-02-24 10:42       ` Dave Jones
2003-02-24 15:45         ` Stian Jordet
  -- strict thread matches above, loose matches on Subject: below --
2003-02-21  9:20 Samium Gromoff
2003-02-21 11:36 ` Toplica Tanasković
2003-02-21 13:32 ` Dave Jones
2003-02-21 14:27 ` Edward Killips
2003-02-21 14:58   ` Dave Jones
2003-02-22 17:56   ` Toplica Tanasković
2003-02-21 16:49 ` Matthew D. Pitts
2003-02-25  7:06 SkamoElf

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=3E59299B.8090200@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