Chances are that you're running the nfs-dependent version of /kernel/fs/afs
and that you haven't modload'd the nfs driver yet. Try running the following
prior to "modload /kernel/fs/afs":

                modload /kernel/misc/nfssrv

You will need to alter your /etc/init.d/afs.rc file accordingly so that
this command is run prior to "modload /kernel/fs/afs" as well.

Alternatively, you can consider loading the non-nfs version of /kernel/fs/afs
if you're not using nfs.

Hope this helps.

        -Steven McElwee

 --
 ---------------------------------------------------------------------------
 Steven McElwee         |         Email -->      | [EMAIL PROTECTED]  
 OIT/System Adm         |   <-- US Snail Mail    |  
 Duke University        |------------------------|-------------------------
 417 North Building     |  (919) 660-6914 (Work) | (919) 660-7029 (Fax)
 Durham, NC 27706       |                        | (919) 971-0781 (Cellular)
 ---------------------------------------------------------------------------

 -- original message follows --

> From:  Andrew Mickish <[EMAIL PROTECTED]>
> To:  [EMAIL PROTECTED]
> Subject:  AFS install on Solaris 2.5
> Date:  Wed, 19 Jun 1996 11:19:20 -0500

> I'm having trouble installing AFS on a Solaris 2.5 machine.  Specifically,
> at page 3-19 of the 3.4a installation guide, I do
> 
>    /usr/sbin/modload /kernel/fs/afs
> 
> and get a screen full of error messages culminating in "panic: data fault"
> and an automatic reboot of the machine.
> 
> I checked that I copied /usr/vice/etc/modload/libafs.o to /kernel/fs/afs
> correctly.  We added "afs" in slot 105 of /etc/name_to_sysnum.
> It may be relevant that I tried to execute the modload instruction once
> before rebooting the machine, but was told that 105 was already in use.
> After rebooting the machine, the "panic: data fault" message is a consistent
> result of the modload instruction.
> 
> I get the impression from this group that a lot of people are running AFS
> on Solaris 2.5.  Did anyone else have an unusual install problem?
> 
> Thanks,
> 
> --Andrew Mickish


Reply via email to