linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@redhat.com>
To: jarausch@belgacom.net, support@nvidia.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.13-pre6 breaks Nvidia's kernel module
Date: Mon, 22 Oct 2001 14:51:01 -0400	[thread overview]
Message-ID: <20011022145101.H23213@redhat.com> (raw)
In-Reply-To: <200110221846.f9MIkE416013@riker.skynet.be>
In-Reply-To: <200110221846.f9MIkE416013@riker.skynet.be>; from jarausch@belgacom.net on Mon, Oct 22, 2001 at 08:45:22PM +0200

Please take this issue up with the provider of that driver.  If they 
were to provide source for the driver, we'd be glad to help you, but 
unfortunately that is not the case.

		-ben

On Mon, Oct 22, 2001 at 08:45:22PM +0200, jarausch@belgacom.net wrote:
> Hello,
> 
> yes I know, you don't like modules without full sources available.
> But Nvidia is the leading vendor of video cards and all 2.4.x
> kernels up to 2.4.13-pre5 work nice with this module.
> 
> Running pre6 I get
> (==) NVIDIA(0): Write-combining range (0xf0000000,0x2000000)
> (EE) NVIDIA(0): Failed to allocate LUT context DMA
> (EE) NVIDIA(0):  *** Aborting ***
> 
> 
> This is Nvidia's 1.0-1541 version of its Linux drivers
> 
> Please keep this driver going during the 2.4.x series of the
> kernel if at all possible.
> 
> Thanks for looking into it,
> 
> Helmut Jarausch
> 
> Inst. of Technology
> RWTH Aachen
> Germany
> 
> 
> Please CC to my private email
> 
> jarausch@belgacom.net
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
"I can't tell you how many bridges I've jumped off of -- all I get is wet."

  reply	other threads:[~2001-10-22 18:50 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22 18:45 2.4.13-pre6 breaks Nvidia's kernel module jarausch
2001-10-22 18:51 ` Benjamin LaHaise [this message]
2001-10-22 18:51 ` Alexander Viro
2001-10-22 19:35 ` Rik van Riel
2001-10-22 19:46   ` Christopher Friesen
2001-10-22 19:53     ` Daniel T. Chen
2001-10-22 19:53 ` 2.4.13-pre6 breaks Nvidia's kernel module, or not? Stephan von Krawczynski
2001-10-22 20:24 ` 2.4.13-pre6 breaks Nvidia's kernel module Alan Cox
2001-10-22 22:27   ` drevil
2001-10-22 22:43     ` Charles Cazabon
2001-10-22 22:46     ` Doug McNaught
2001-10-22 22:50     ` Alan Cox
2001-10-23  1:31       ` drevil
2001-10-23  1:43         ` Michael H. Warfield
2001-10-23  2:16           ` drevil
2001-10-23  4:44             ` Nicholas Knight
2001-10-23  5:06               ` Cort Dougan
2001-10-23 11:36                 ` Rik van Riel
2001-10-23 16:13                 ` Alan Cox
2001-10-23  5:08               ` drevil
2001-10-23  5:18                 ` J Sloan
2001-10-23  5:59                 ` Nicholas Knight
2001-10-23  7:21                 ` Helge Hafting
2001-10-23  5:35           ` Matt D. Robinson
2001-10-23 16:16             ` Alan Cox
2001-10-23  9:50           ` David Woodhouse
2001-10-23 23:45             ` Ragnar Hojland Espinosa
2001-10-23  7:57         ` Alan Cox
2001-10-23 14:18           ` drevil
2001-10-23 16:01         ` Geert Uytterhoeven
2001-10-22 23:48     ` Jeff Golds
2001-10-22 23:53 ` Horst von Brand
2001-10-23  9:05 ` Jesper Juhl
2001-10-23 18:07   ` Josh McKinney
2001-10-23 22:51     ` J . A . Magallon
2001-10-24 21:06       ` Reid Hekman
2001-10-25  0:19         ` J . A . Magallon
2001-10-22 18:45 jarausch
2005-01-13 16:19 ` Arjan van de Ven
2005-01-13 16:50 ` Valdis.Kletnieks
2005-01-13 17:25 ` Zan Lynx
2005-01-13 17:38 ` Zwane Mwaikambo
2001-10-22 18:45 jarausch
2001-10-22 18:45 jarausch
2001-10-23  1:50 BH
2001-10-23  9:52 PVotruba
2001-10-23 12:37 Jesse Pollard
     [not found] <fa.fm7f5dv.1cn8eg6@ifi.uio.no>
     [not found] ` <fa.hbvlhav.v369au@ifi.uio.no>
     [not found]   ` <023001c15cf4$4fd5ecc0$1a01a8c0@allyourbase>
2001-10-25  4:15     ` Reid Hekman

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=20011022145101.H23213@redhat.com \
    --to=bcrl@redhat.com \
    --cc=jarausch@belgacom.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=support@nvidia.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;
as well as URLs for NNTP newsgroup(s).