From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: NVIDIA and 2.6.4?
Date: Sun, 14 Mar 2004 02:28:35 +0000 [thread overview]
Message-ID: <4053C353.6040205@blueyonder.co.uk> (raw)
In-Reply-To: <4053C22B.2090200@blueyonder.co.uk>
Sid Boyce wrote:
> Adam Jones wrote:
> >In a futile gesture against entropy, Sid Boyce wrote:
> >>/ Max Valdez wrote:/
>
> >>/ >Been using nvidia modules for quite a few 2.6.x kernels, most of
> them mmX. /
> >>/ >without problems/
>
> >I'm using it here with 2.6.4, no problems as yet.
>
> >>/ Something strange happened, I shall try 2.6.4-mm1 shortly to see
> if it /
> >>/ is still the same. I reckon though that I've suffered a filesystem /
> >>/ corruption./
>
> > A quick thought - have you got CONFIG_REGPARM enabled in the kernel
> > config? If so, disable it and try again. (It's almost certain to
> > cause crashes with binary modules.)
> I haven't had CONFIG_REGPARM set in any of the kernels. 2.6.4-rc2-mm1
> was fine until after I first booted 2.6.4-mm1, then neither would work
> with nvidia. I also got some strange stuff happening, including
> checksum errors on the driver and I had to download it again from
> nvidia.com on two occasions, the first redownload reinstalled once,
> then chksum errors, the second redownload did the same as well as
> chksum segfaulting, since then it's been fine. See also the garbage I
> get out of vi in an earlier posting.
> Regards
> Sid.
>
*** CORRECTION *** 2.6.4-rc2-mm1 is the one that caused the trouble as
stated in the first post. I'm yet to boot up 2.6.4-mm1.
Some of the files in lost+found seem to be kde settings which I noticed
were missing and had to setup again.
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.
next prev parent reply other threads:[~2004-03-14 2:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 2:23 NVIDIA and 2.6.4? Sid Boyce
2004-03-14 2:28 ` Sid Boyce [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-15 1:24 Sid Boyce
2004-03-11 15:15 Sid Boyce
2004-03-11 19:26 ` Max Valdez
2004-03-12 1:31 ` Sid Boyce
2004-03-12 18:24 ` Adam Jones
2004-03-13 5:15 ` Valdis.Kletnieks
2004-03-15 3:36 ` Steve Youngs
2004-03-16 20:49 ` Dominik Karall
2004-03-16 20:50 ` Brian Gerst
2004-03-16 21:19 ` Valdis.Kletnieks
2004-03-16 21:55 ` Dominik Karall
[not found] <1yxEK-7cw-5@gated-at.bofh.it>
2004-03-11 13:20 ` Dennis Bliefernicht
2004-03-11 15:05 ` Robert L. Harris
2004-03-11 12:31 Robert L. Harris
2004-03-11 13:07 ` Nerijus Baliunas
2004-03-11 13:23 ` Martin Zwickel
2004-03-13 14:34 ` venom
2004-03-11 14:52 ` Alistair John Strachan
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=4053C353.6040205@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--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