Caliban
10-27-2003, 11:28 PM
I'm trying to mount an NFS drive from my Philips DSR7000 and it gives the following error:
bash-2.02# mount 192.168.0.254:/data /var/hack/nfsmount
mount: fs type nfs not supported by kernel
Also tried it with mount -t nfs and it returned the same thing.
So I went browsing at tivoutils.sourceforge.net and found that as with the devbin-s2, there were binaries for series 2 mips processors for the nfs.o ( s2-2.4.4-modules.tgz ). So I got it, extracted it, and copied it to /var/hack/lib. Next I tried this command:
insmod /var/hack/lib/nfs.o
which returned this error:
bash-2.02# insmod /var/hack/lib/nfs.o
/var/hack/lib/nfs.o: unresolved symbol rpc_wake_up_task
/var/hack/lib/nfs.o: unresolved symbol rpc_killall_tasks
/var/hack/lib/nfs.o: unresolved symbol rpc_init_task
/var/hack/lib/nfs.o: unresolved symbol nlmclnt_proc
/var/hack/lib/nfs.o: unresolved symbol rpc_shutdown_client
/var/hack/lib/nfs.o: unresolved symbol rpciod_up
/var/hack/lib/nfs.o: unresolved symbol rpc_new_task
/var/hack/lib/nfs.o: unresolved symbol rpciod_down
/var/hack/lib/nfs.o: unresolved symbol lockd_down
/var/hack/lib/nfs.o: unresolved symbol rpc_wake_up_status
/var/hack/lib/nfs.o: unresolved symbol rpc_clnt_sigmask
/var/hack/lib/nfs.o: unresolved symbol rpcauth_releasecred
/var/hack/lib/nfs.o: unresolved symbol lockd_up
/var/hack/lib/nfs.o: unresolved symbol rpc_proc_unregister
/var/hack/lib/nfs.o: unresolved symbol rpc_release_task
/var/hack/lib/nfs.o: unresolved symbol xdr_encode_array
/var/hack/lib/nfs.o: unresolved symbol nfs_debug
/var/hack/lib/nfs.o: unresolved symbol rpc_create_client
/var/hack/lib/nfs.o: unresolved symbol rpc_sleep_on
/var/hack/lib/nfs.o: unresolved symbol rpcauth_lookupcred
/var/hack/lib/nfs.o: unresolved symbol rpc_clnt_sigunmask
/var/hack/lib/nfs.o: unresolved symbol rpc_call_setup
/var/hack/lib/nfs.o: unresolved symbol rpc_call_sync
/var/hack/lib/nfs.o: unresolved symbol xprt_destroy
/var/hack/lib/nfs.o: unresolved symbol rpc_execute
/var/hack/lib/nfs.o: unresolved symbol rpc_proc_register
/var/hack/lib/nfs.o: unresolved symbol xdr_zero_iovec
/var/hack/lib/nfs.o: unresolved symbol xprt_create_proto
bash-2.02#
Tried this before doing a chmod 777 and after, but it still does the same thing. Tried searching the forum but I wasn't able to find anything on point, although I'm sure its out there. Do I need to insmod all the other contents of the archive to get nfs to work? is there a specific order required?
I don't think its getting close to that point anyway, but I have a functioning Linux server on my network running NFS, and none of the clients have problem mounting the drive.
Any help would be greatly appreciated.
bash-2.02# mount 192.168.0.254:/data /var/hack/nfsmount
mount: fs type nfs not supported by kernel
Also tried it with mount -t nfs and it returned the same thing.
So I went browsing at tivoutils.sourceforge.net and found that as with the devbin-s2, there were binaries for series 2 mips processors for the nfs.o ( s2-2.4.4-modules.tgz ). So I got it, extracted it, and copied it to /var/hack/lib. Next I tried this command:
insmod /var/hack/lib/nfs.o
which returned this error:
bash-2.02# insmod /var/hack/lib/nfs.o
/var/hack/lib/nfs.o: unresolved symbol rpc_wake_up_task
/var/hack/lib/nfs.o: unresolved symbol rpc_killall_tasks
/var/hack/lib/nfs.o: unresolved symbol rpc_init_task
/var/hack/lib/nfs.o: unresolved symbol nlmclnt_proc
/var/hack/lib/nfs.o: unresolved symbol rpc_shutdown_client
/var/hack/lib/nfs.o: unresolved symbol rpciod_up
/var/hack/lib/nfs.o: unresolved symbol rpc_new_task
/var/hack/lib/nfs.o: unresolved symbol rpciod_down
/var/hack/lib/nfs.o: unresolved symbol lockd_down
/var/hack/lib/nfs.o: unresolved symbol rpc_wake_up_status
/var/hack/lib/nfs.o: unresolved symbol rpc_clnt_sigmask
/var/hack/lib/nfs.o: unresolved symbol rpcauth_releasecred
/var/hack/lib/nfs.o: unresolved symbol lockd_up
/var/hack/lib/nfs.o: unresolved symbol rpc_proc_unregister
/var/hack/lib/nfs.o: unresolved symbol rpc_release_task
/var/hack/lib/nfs.o: unresolved symbol xdr_encode_array
/var/hack/lib/nfs.o: unresolved symbol nfs_debug
/var/hack/lib/nfs.o: unresolved symbol rpc_create_client
/var/hack/lib/nfs.o: unresolved symbol rpc_sleep_on
/var/hack/lib/nfs.o: unresolved symbol rpcauth_lookupcred
/var/hack/lib/nfs.o: unresolved symbol rpc_clnt_sigunmask
/var/hack/lib/nfs.o: unresolved symbol rpc_call_setup
/var/hack/lib/nfs.o: unresolved symbol rpc_call_sync
/var/hack/lib/nfs.o: unresolved symbol xprt_destroy
/var/hack/lib/nfs.o: unresolved symbol rpc_execute
/var/hack/lib/nfs.o: unresolved symbol rpc_proc_register
/var/hack/lib/nfs.o: unresolved symbol xdr_zero_iovec
/var/hack/lib/nfs.o: unresolved symbol xprt_create_proto
bash-2.02#
Tried this before doing a chmod 777 and after, but it still does the same thing. Tried searching the forum but I wasn't able to find anything on point, although I'm sure its out there. Do I need to insmod all the other contents of the archive to get nfs to work? is there a specific order required?
I don't think its getting close to that point anyway, but I have a functioning Linux server on my network running NFS, and none of the clients have problem mounting the drive.
Any help would be greatly appreciated.