From: PVotruba@Chemoprojekt.cz
To: linux-kernel@vger.kernel.org
Subject: RE: 2.4.13-pre6 breaks Nvidia's kernel module
Date: Tue, 23 Oct 2001 11:52:14 +0200 [thread overview]
Message-ID: <35E64A70B5ACD511BCB0000000004CA1043861@NT_CHEMO> (raw)
Exactly... read supplier's manuals pays well. 2.4.13-pre6+nvidia drvs
1541+GeForce2MX400 works for me perfectly.
But some other problem appeared - there's something strange probably in
nvidia framebuffer console code. Starts up nicely, X works too, including
"openuniverse", but after returning to console (regularly or by
Ctrl+Alt+Backspace), I see few standard messages and box gets frozen.
Background sound playing also stops (it repeats playing last data in
buffer). Keyboard driver works (num+scr+caps locks are reacting at least),
but is ignored by the system. Command line also doesn't appear.
I didn't try to log into via network, cause my second box is presently not
complete, anyway I wouldn't expect any reaction from such frozen box.
Well, I stopped using nvidia framebuffer console driver and all works
nicely.
---
Some time ago I had BIG troubles with AGP working at 4X - I had to degrade
AGP to 2X (in BIOS) and all works fine now (but slower, of course).Also
kernel compilation in X terminal made system freezed, but not so badly as
the console driver did - I was still able to login via network, just to see
that X server makes 100% load, is not killable and the system ignores
shutdown commands...
My GeForce card is manufactured by some Manli company, and I use it with ECS
K7VZA board (older 686A model).
Hard to say if problem is in card or motherboard. 250VA power source could
be strong enough to drive everything...
bye
Petr
>
>
> -----Původní zpráva-----
> Od: Jesper Juhl [SMTP:juhl@eisenstein.dk]
> Odesláno: 23. října 2001 11:06
> Komu: jarausch@belgacom.net
> Kopie: linux-kernel@vger.kernel.org
> Předmět: Re: 2.4.13-pre6 breaks Nvidia's kernel module
>
>
> 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
>
> I use the same version of the driver with my Geforce3 and I am also
> running 2.4.13-pre6 and it works just fine so I don't agree with you
> that it breaks...
> You do know that there are a few files that need to be recompiled every
> time you build a new kernel - right?
>
> See "http://www.nvidia.com/docs/lo/1021/SUPP/README.txt" for details.
>
> Here's a quote from that file explaining what I do myself - that should
> work for you:
>
> "
> INSTALLING/UPGRADING BY TAR FILE Instructions for the Impatient:
>
> $ tar xvzf NVIDIA_kernel.tar.gz
> $ tar xvzf NVIDIA_GLX.tar.gz
> $ cd NVIDIA_kernel
> $ make install
> $ cd ../NVIDIA_GLX
> $ make install
>
> Instructions:
>
> To install from tar file, unpack each file:
> $ tar xvzf NVIDIA_kernel.tar.gz
> $ tar xvzf NVIDIA_GLX.tar.gz
>
> cd into the NVIDIA_kernel directory. Type 'make install'. This will
> compile the kernel interface to the NVdriver, link the NVdriver, copy
> the NVdriver into place, and attempt to insert the NVdriver into the
> running kernel:
>
> $ cd NVIDIA_kernel
> $ make install
>
> Next, move into the NVIDIA_GLX directory. Type 'make install' -- this
> will copy the needed OpenGL and XFree86 files into place:
> $ cd ../NVIDIA_GLX
> $ make install
>
> Note that the "make install" for each package will remove any previously
> installed NVIDIA drivers.
> "
>
>
> Best regards,
> Jesper Juhl
>
>
> -
> 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/
next reply other threads:[~2001-10-23 9:52 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 9:52 PVotruba [this message]
[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
-- strict thread matches above, loose matches on Subject: below --
2001-10-23 12:37 Jesse Pollard
2001-10-23 1:50 BH
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:51 ` Benjamin LaHaise
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 20:24 ` 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
2001-10-22 18:45 jarausch
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=35E64A70B5ACD511BCB0000000004CA1043861@NT_CHEMO \
--to=pvotruba@chemoprojekt.cz \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®