From: "J . A . Magallon" <jamagallon@able.es>
To: linux-kernel@vger.kernel.org
Subject: Re: XFree 4.0.1/NVIDIA 0.9-5/2.4.0-testX/11 woes [solved]
Date: Wed, 29 Nov 2000 02:10:25 +0100 [thread overview]
Message-ID: <20001129021025.A768@werewolf.able.es> (raw)
In-Reply-To: <E140urK-0005FZ-00@the-village.bc.nu> <Pine.LNX.4.30.0011281639180.27174-100000@anime.net>
In-Reply-To: <Pine.LNX.4.30.0011281639180.27174-100000@anime.net>; from goemon@anime.net on Wed, Nov 29, 2000 at 01:39:56 +0100
On Wed, 29 Nov 2000 01:39:56 Dan Hollis wrote:
>
> Dont forget the nvidia driver is completely SMP broken. As in, trash your
> filesystems broken.
>
Not so broken. I use it under SMP 2.2.18-pre23 and works fine. But under 2.4
hangs. So I think it is something that changed between 2.2 and 2.4 (locking
granularity???). And just hangs your box, does not corrupt anything.
It is a pitty that any piece of copylefted code prevents nVivia of giving all
of the drivers in source form.
--
Juan Antonio Magallon Lacarta #> cd /pub
mailto:jamagallon@able.es #> more beer
Linux 2.2.18-pre23-vm #3 SMP Wed Nov 22 22:33:53 CET 2000 i686 unknown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-29 1:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 0:02 XFree 4.0.1/NVIDIA 0.9-5/2.4.0-testX/11 woes [solved] Petter Sundlöf
2000-11-29 0:12 ` Alan Cox
2000-11-29 0:22 ` Petter Sundlöf
2000-11-29 0:39 ` Dan Hollis
2000-11-29 1:10 ` J . A . Magallon [this message]
2000-11-29 1:29 ` Dan Hollis
2000-11-29 1:48 ` J . A . Magallon
2000-11-29 2:01 ` Kiril Vidimce
2000-11-29 2:08 ` Alan Cox
2000-11-29 2:24 ` Kiril Vidimce
2000-11-29 2:32 ` Alan Cox
2000-11-29 2:48 ` Kiril Vidimce
2000-11-29 9:37 ` Yoann Vandoorselaere
2000-11-29 3:12 ` Kiril Vidimce
2000-11-29 13:13 ` Android
2000-11-29 14:34 ` Eric W. Biederman
2000-11-29 16:57 ` James Simmons
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=20001129021025.A768@werewolf.able.es \
--to=jamagallon@able.es \
--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