Board index Linux Kernel

2.4.13-pre6 breaks Nvidia's kernel module

2.4.13-pre6 breaks Nvidia's kernel module

Post by jarau.. » Wed, 24 Oct 2001 03:50:11



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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 
Top

2.4.13-pre6 breaks Nvidia's kernel module

Post by Christopher Friese » Wed, 24 Oct 2001 04:50:11




> > 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.

> So get NVIDIA to release the source code for their driver,
> this would allow you to recompile the driver and make it
> work again.

> Note that once NVIDIA stops selling this model video card
> you're stuck with the last supported version of Linux anyway
> and won't be able to upgrade.

Actually, NVIDIA has a HAL-type thing going on and their drivers will support all of their cards from the TNT on up to
the GeForce 3.  The only unsupported models are the Riva128 and Riva128ZX.

--
Chris Friesen                    | MailStop: 043/33/F10  
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 
Top

2.4.13-pre6 breaks Nvidia's kernel module

Post by Alan Co » Wed, 24 Oct 2001 07:50:11


Quote:> > Only Nvidia can help you

> With a problem caused by someone else and not them? Interesting viewpoint. I
> also find it interesting that people think NVidia is the sole company in control
> of whether or not ther drivers are opened considering SGI and other 3rd parties
> own code in the 'driver pie'. This is a simplistic naive view IMHO....

I can't debug Nvidia's code even to see why it might have broken. Its as
simple as that - no politics, no agenda on them opening it, simple technical
statement of fact.

I really doubt Nvidia will open their driver code. I've heard them explain
some of the reasons they don't and in part they make complete sense.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 
Top

1. Deadlock in kernel > 2.4.13-pre6

Hi everyone,

I've recently compiled and tested each kernel since 2.4.13-pre6[0], and
I've noticed a recurrent (and reproducible[1]) deadlock on my system
when I try to play an mp3[2].

It occurs randomly, i.e. not after a precise amount of time the mp3 is
playing, but each and every time I try to play an mp3 file, my box
suddenly ``freeze'': no life signs at all (SysRq keys, network, even via
a serial terminal), no Oops, no trace in logs. The box simply `dies'.

I've tried hundreds of combinations, trying to understand where the
problem lies, and I've come up with... er... nothing...

o       it's not ext3: even vanilla kernels lock up;
o       it's not an hardware problem: I've tested my RAM and compiled
        kernels over kernels with (and without) optimization;
o       kernels <= 2.4.13-pre6 works properly;
o       it's not the player/library fault: I've tried many players, on
        different libraries; besides, a user-level program shouldn't
        cause such deadlocks;
o       every other operation on kernels > 2.4.13-pre6 works quite well
        (this new VM is *great*), *except* when I try to listen a
        mp3[3]: that always leads to disaster.

So far, I've excluded everything but a bug in the OSS sound drivers,
but, according to the ChangeLogs, they did not change from 2.4.13-pre6
(the last working kernel) to 2.4.13.

+++

[0] Mainly, because it was the first kernel with the new VM and with the
ext3 patch available, excluding 2.4.10.

[1] At least, on my box.

[2] I use a SoundBlaster AWE64 (ISA) perfectly recognized both by isapnp
and 2.4.x kernels, using OSS modules. Yes, I've also tried not to use
modules. No, I did not try ALSA. Yes, the card works perfectly.

[3] Any other format, except .MOD files, works perfectly. And that's why
I suspect the sequencer code.

Bye,
 Emmanuele.

--
Emmanuele Bassi (Zefram)               [ http://digilander.iol.it/ebassi ]
GnuPG Key fingerprint = 4DD0 C90D 4070 F071 5738  08BD 8ECC DB8F A432 0FF4

2. Please take minute to read this.

3. Deadlock on kernels > 2.4.13-pre6

4. Wordperfect Suite 2K for Linux on FreeBSD 4.0??

5. OOPS on boot in 2.4.13-ac5 & 2.4.14-pre6

6. Telnet Keymapping

7. Kernel 2.4.13: no modules

8. Change mouse to CUA0???

9. O_DIRECT broken in stock 2.4.13

10. Problems with 2.4.13 - modules

11. aic7xxx freezes with kernel 2.4.13

12. aic7xxx freezes with kernel 2.4.13 - solved

13. Kernel panic: Loop 1 (aic7xxx under 2.4.13-ac[246])


All times are UTC
Board index