Re: [Gumstix-users] NFS mount problem

[Craig H. <cr...@hu...>]

I don't think I've tried recently doing NFS over usbnet, but I have 
been booting my ethernet gumstix using an NFS root_fs for the last day 
or so, and it works fine.  You might try taking a look at the 
branches/ether-lan91c111 tree in SVN to see if there are any useful 
differences between how it's doing busybox and how the trunk is set up.

I don't know what that error message might mean -- can you successfully 
load other modules?  What does the output of the "free" command say -- 
do you actually just have no RAM available?

C

On Dec 6, 2004, at 12:24 PM, Philip White wrote:

>
> Craig,
>
> As I experienced the same "Error while 'make clean'" problem that was
> reported last week, I actually in desperation did a 'rm -R' to the 
> whole
> buildroot tree and started again from scratch - So the root_fs I ended 
> up
> with was the product of this was in absolute virgin condition.
>
> The only change to how it arrived via svn was the change made to set
> CONFIG_ARCH_GUMSTIX_ORIG=y in source/linux.conf
>
> Maybe I will try a monolithic kernel next. I'll get back to you if it 
> works.
>
> Incidentally I just peeked at the busybox .config.  It has
>
> CONFIG_NFSMOUNT=y
>
> So I guess that means that's ok.
>
> Besides given the first error happens after modprobe nfs, before I even
> issue a mount command I suspect it's a kernel / modules issue, not 
> busybox.
>
> Do you know what
>
> "insmod: cannot insert
> `/lib/modules/2.6.9-rc1gum/kernel/fs/lockd/lockd.ko':
>  Cannot allocate memory (-1): Cannot allocate memory"
>
> means? Has anyone else seen this before?  Is anyone else successfully 
> using
> NFS over usb networking with the current stock root_fs?
>
>
> Phil
> -----Original Message-----
> From: gum...@li...
> [mailto:gum...@li...] On Behalf Of Craig 
> Hughes
> Sent: 06 December 2004 19:27
> To: gum...@li...
> Subject: Re: [Gumstix-users] NFS mount problem
>
> Phil,
>
> probably a couple things to check -- first, if you've built a new
> kernel on top of an older buildroot, you might need to clear out the
> build_arm/root to make sure it doesn't have anything stale in there.
> The buildroot is pretty good about adding new stuff in there, but not
> so good about removing old stuff.  This can show up particularly when
> you have a new kernel (ie uImage) and an old module or two (maybe you
> turned those modules off in the new kernel, but they used to be on).
> Just rm -rf build_arm/root then make in the top-level again, and it'll
> reconstruct the root directory, then re-build the root_fs_arm.  You
> might actually want to not use a modular kernel -- to just go through
> and just build everything into a monolithic kernel instead to remove
> that degree of freedom from your debugging.  Once everything's working,
> you can break out to modular again.
>
> Second thing to check is that you have the NFS stuff turned on in
> busybox.  I think the default busybox mount command doesn't include NFS
> support to keep size down.
>
> C
>
> On Dec 6, 2004, at 10:24 AM, Philip White wrote:
>
>> I'm using the latest buildroot generated root_fs on a original gumstix
>> (Thanks to craig for advising on how to set the make options for the
>> original stix)
>>
>> Now, the RNDIS usb networking 'just worked' when I connected it to my
>> windows xp box and bridged it onto my home lan - Fantastic!
>>
>> However I wanted to do a nfs mount to exported directory on my debian
>> PC
>> box, and couldn't get it to work.  I know the nfs server is Ok.
>>
>> Initially I did a "mount -t nfs 10.0.3.52:/home/nfs /mnt/nfs", and got
>> a
>> "mount: Mounting 10.0.3.52:/home/nfs on /mnt/nfs failed: No such
>> device"
>>
>> I thought I might need to do a "modprobe nfs" first, but this resulted
>> in a:
>>
>>
>> modprobe nfs
>> insmod: cannot insert
>> `/lib/modules/2.6.9-rc1-gum/kernel/fs/lockd/lockd.ko':
>> Can
>> not allocate memory (-1): Cannot allocate memory
>> nfs: Unknown symbol nlmclnt_proc
>> nfs: Unknown symbol lockd_down
>> nfs: Unknown symbol lockd_up
>> insmod: cannot insert
>> `/lib/modules/2.6.9-rc1-gum/kernel/fs/nfs/nfs.ko':
>> Unknown
>>  symbol in module (-1): No such file or directory
>> modprobe: failed to load module nfs
>>
>>
>> Checking dmesg I noticed:
>>
>> nfs: Unknown symbol nlmclnt_proc
>> nfs: Unknown symbol lockd_down
>> nfs: Unknown symbol lockd_up
>>
>> Am I doing something daft, or not doing something I should?
>>
>> TIA
>> Phil
>>
>>
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real
>> users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://productguide.itmanagersjournal.com/
>> _______________________________________________
>> gumstix-users mailing list
>> gum...@li...
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users