Prev: Assigning USB devices fixed mountable details (udev rules?)
Next: minor tcl/tk breakage
From: Peter Chant on 18 Apr 2010 17:58
Any thoughts:

when nfsd gets a request for a directory mount it fails and this shows up in
/var/log/messages

Apr 18 22:56:38 phoenix modprobe: FATAL: Error inserting nfsd
(/lib/modules/2.6.33.1/kernel/fs/nfsd/nfsd.ko): Invalid module format

This is the standard kernel that came with Slackware64-current on 31 March.

Presume recompiling the kernel would fix this?

Pete





--
http://www.petezilla.co.uk
From: Grant on 20 Apr 2010 02:00
On Mon, 19 Apr 2010 18:56:10 +0100, Peter Chant <peteRE(a)MpeteOzilla.Vco.ukE> wrote:

>Grant wrote:
>
>> On Sun, 18 Apr 2010 22:58:27 +0100, Peter Chant
>> <peteRE(a)MpeteOzilla.Vco.ukE> wrote:
>>
>>>Any thoughts:
>>>
>>>when nfsd gets a request for a directory mount it fails and this shows up
>>>in /var/log/messages
>>>
>>>Apr 18 22:56:38 phoenix modprobe: FATAL: Error inserting nfsd
>>>(/lib/modules/2.6.33.1/kernel/fs/nfsd/nfsd.ko): Invalid module format
>>>
>>>This is the standard kernel that came with Slackware64-current on 31
>>>March.
>>>
>>>Presume recompiling the kernel would fix this?
>>
>> I'd think so, doesn't take long these days
>
>Don't think I'd need make oldconfig - just make ; make modules ; make
>modules_install.

If it was me I'd copy over the wanted config from /boot and make oldconfig,
just to be sure.
>
>BTW - you are wrong, it is getting longer. Back in the day my shiny new
>K6-233 could compile a kernel in 4 minutes flat!

Oh well, faulty memory? Unless you were on 2.0 or 2.2 back then? I was
tracking 2.3.latest then 2.4.latest back then. Think they took longer.

Grant.
--
http://bugs.id.au/
From: Grant on 19 Apr 2010 06:34
On Sun, 18 Apr 2010 22:58:27 +0100, Peter Chant <peteRE(a)MpeteOzilla.Vco.ukE> wrote:

>Any thoughts:
>
>when nfsd gets a request for a directory mount it fails and this shows up in
>/var/log/messages
>
>Apr 18 22:56:38 phoenix modprobe: FATAL: Error inserting nfsd
>(/lib/modules/2.6.33.1/kernel/fs/nfsd/nfsd.ko): Invalid module format
>
>This is the standard kernel that came with Slackware64-current on 31 March.
>
>Presume recompiling the kernel would fix this?

I'd think so, doesn't take long these days

Grant.
--
http://bugs.id.au/
From: Peter Chant on 19 Apr 2010 13:56
Grant wrote:

> On Sun, 18 Apr 2010 22:58:27 +0100, Peter Chant
> <peteRE(a)MpeteOzilla.Vco.ukE> wrote:
>
>>Any thoughts:
>>
>>when nfsd gets a request for a directory mount it fails and this shows up
>>in /var/log/messages
>>
>>Apr 18 22:56:38 phoenix modprobe: FATAL: Error inserting nfsd
>>(/lib/modules/2.6.33.1/kernel/fs/nfsd/nfsd.ko): Invalid module format
>>
>>This is the standard kernel that came with Slackware64-current on 31
>>March.
>>
>>Presume recompiling the kernel would fix this?
>
> I'd think so, doesn't take long these days

Don't think I'd need make oldconfig - just make ; make modules ; make
modules_install.

BTW - you are wrong, it is getting longer. Back in the day my shiny new
K6-233 could compile a kernel in 4 minutes flat!

--
http://www.petezilla.co.uk
From: Peter Chant on 21 Apr 2010 02:17
Grant wrote:

>>BTW - you are wrong, it is getting longer. Back in the day my shiny new
>>K6-233 could compile a kernel in 4 minutes flat!
>
> Oh well, faulty memory? Unless you were on 2.0 or 2.2 back then? I was
> tracking 2.3.latest then 2.4.latest back then. Think they took longer.

That was 12 or 13 years back. Can't remember, one of those two, probably
the former. Kernel was a lot smaller then. Small enough I could remember
all the important settings (to me) in a kernel config and set the options in
about 10 mins - without copying the Slackware config and tweeking. Can't do
that now.

Pete

--
http://www.petezilla.co.uk
 |  Next  |  Last
Pages: 1 2
Prev: Assigning USB devices fixed mountable details (udev rules?)
Next: minor tcl/tk breakage