From: Andrew M. <amo...@st...> - 2001-05-16 18:19:36
|
I think you meant lin...@li... Thanks, I have now semi-successfully gotten the DC to boot. I used the ip= setting and it mounted the NFS root filesystem. Unfortunately, it seems to be mounting read-only, so I get a lot of errors during the boot process. The root filesystem I am using is the Debian-based one from ftp://m17n.org/pub/super-h/debian-unstable/superh/tar+gz/ . I examined the files in there, and the permissions seem normal, so I think it's an NFS problem. The distribution also seems to be missing a few files that the startup scripts are expecting. "options" : root=/dev/nfs mem=16M video=pvrdc:640x480-32 nfsroot=192.168.0.3:/mnt/dcnfs \ ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0::: "/etc/exports" : /mnt/dcnfs 192.168.0.4(rw,no_root_squash) 192.168.0.4 is the DC 192.168.0.3 is the NFS server Hardware is listed at bottom. Thanks for the help, Andrew Molloy Karl Trygve Kalleberg wrote: >As I've not had the chance to toy around with booting NFS on the DC >myself yet (Haven't got the BBA), I'm forwarding this to the list. > >However, I wouldn't think it is too different from booting with NFS >on an x86, which I've done a few times before, so here's my dollar's worth >of advice (ymmv, of course): > >In /etc/exports, I have: >/local/karltk/nfsboot pudding.local(rw,insecure,no_root_squash) > >In /etc/hosts, I have: >192.168.1.198 pudding.local pudding > >The kernel parameters I use are (on one line, remove the \): >nfsroot=192.168.1.199:/local/karltk/nfsboot \ >ip=192.168.1.198:192.168.1.199:192.168.1.199:255.255.255.0:pudding:: > >I've had a few problems with BOOTP and RARP on 2.4.3 and 2.4.4 (got the >101 error below), but when I specified all IPs explicitly in the ip= >parameter sequence, it worked. > >192.168.1.199 is the NFS server. >192.168.1.198 is the NFS client. > > >Hope this helps a bit, at least. > >Kind regards, > >Karl T > > >--Forwarded message from Andrew Molloy <amolloy1 at stevens dash tech dot edu> -- > >Hi, > >I'm trying to get my Dreamcast to run linux. I can get it to boot >successfully over the broadband adapter via dcload-ip. I've been unable >to mount the root filesystem via NFS though. This could just be that I >can't get the syntax right in my options file, or it might be or >portmapper problem, but I think the problem is on the DC side since I >can't get it to mount from two different servers. > >Thanks for any help, >Andrew Molloy > > >The error on the Dreamcast (manaully typed in): > >Looking up port of RPC 100003/2 on 192.168.0.3 >RPC: sendmsg returned error 101 >portmap: RPC call returned error 101 >Root-NFS: Unable to get nfsd port number from server, using default >Looking up port of RPC 10005/2 on 192.168.0.3 >RPC: sendmsg returned error 101 >Root-NFS: Unable to get mountd port number from server, using default >RPC: sendmsg returned error 101 >mount: RPC call returned erorr 101 >Root-NFS: Server returned error -101 while mounting /mnt/dcnfs >VFS: Unable to mount root fs via NFS, trying floppy. >VFS: Cannot open root device "nfs" or 02:00 >Please append a correct "root=" boot option >Kernel panic: VFS: Unable to mount root fs on 02:00 > >my "options" file: >root=/dev/nfs mem=16M video=pvr2dc:640x480-32 nfsroot=192.168.0.3:/mnt/dcnfs > >relevant parts from my ".config" file: >CONFIG_PCI=y >CONFIG_BLK_DEV_LOOP=y >CONFIG_BLK_DEV_NBD=y >CONFIG_BLK_DEV_RAM=y >CONFIG_BLK_DEV_RAM_SIZE=4096 >CONFIG_BLK_DEV_INITRD=y >CONFIG_PACKET=y >CONFIG_PACKET_MMAP=y >CONFIG_NETLINK=y >CONFIG_UNIX=y >CONFIG_INET=y >CONFIG_IP_PNP=y >CONFIG_NETDEVICES=y >CONFIG_NET_ETHERNET=y >CONFIG_NET_PCI=y >CONFIG_8139TOO=y >CONFIG_INPUT=y >CONFIG_INPUT_KEYBDEV=y >CONFIG_INPUT_MOUSEDEV=y >CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 >CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 >CONFIG_INPUT_JOYDEV=y >CONFIG_INPUT_EVDEV=y >CONFIG_MAPLE_KEYBOARD=y >CONFIG_MAPLE_MOUSE=y ># ># Network File Systems ># ># CONFIG_CODA_FS is not set >CONFIG_NFS_FS=y >CONFIG_NFS_V3=y >CONFIG_ROOT_NFS=y ># CONFIG_NFSD is not set >CONFIG_SUNRPC=y >CONFIG_LOCKD=y >CONFIG_LOCKD_V4=y ># CONFIG_SMB_FS is not set ># CONFIG_NCP_FS is not set > > >my hardware: >Dreamcast - 192.168.0.4 >Broadband Adapter >VGA Adapter >1 Joystick >1 Mouse >1 Keyboard >1 Mega-Memory Card (4 sets of 200 blocks if I recall correctly) > >nfs-server #1 - 192.168.0.3 >Redhat 7.0 >portmap-4.0-29 >/etc/exports = /mnt/dcnfs 192.168.0.4(rw) > >nfs-server #2 - 192.168.0.2 >Snap Server (basically a hard drive on the network, built for NFS >sharing, I have successfuly NFS-mounted other shares from this server) > > >----- End forwarded message ----- > |
From: Karl T. K. <ka...@pr...> - 2001-05-16 18:24:49
|
On Wed, May 16, 2001 at 02:19:18PM -0400, Andrew Molloy wrote: > I think you meant lin...@li... Yes of course I did. > Thanks, I have now semi-successfully gotten the DC to boot. I used the > ip= setting and it mounted the NFS root filesystem. Unfortunately, it > seems to be mounting read-only, so I get a lot of errors during the boot > process. The root filesystem I am using is the Debian-based one from > ftp://m17n.org/pub/super-h/debian-unstable/superh/tar+gz/ . > I examined the files in there, and the permissions seem normal, so I > think it's an NFS problem. Try mounting the NFS share from another machine (or from the NFS server itself, for that matter) to see if you actually can write to the directories there (I'd assume you can, but doublecheck nevertheless). Also, there might be faster, more interactive help on #linuxdc on irc.openprojects.net Karl T |
From: Karl T. K. <ka...@pr...> - 2001-05-16 20:23:20
|
On Wed, May 16, 2001 at 04:15:09PM -0400, Andrew Molloy wrote: > I mounted it from the server and I can write to it. Also, since I'm not > very familiar with NFS, is no_root_squash appropriate for the > Dreamcast? I assumed so from the man page but it wasn't a very good > explanation. no_root_squash is required if the client should be able to read files private to root on the host machine. Then mounting root over NFS, you have to specify no_root_squash. The theory from #linuxdc is that the init script that's supposed to remount / read-write is screwed up. I've not toyed around with the root image you mentioned myself, so my only advice is to look closely at the boot script(s) and find out where it's supposed to remount root, then see to it that the script actually does that. > I've tried to connect to IRC, but I'm firewalled and the proxies don't > allow it. That's a shame. If you have a squid proxy between you and the outer world, there's a little neat trick called tcp-over-squid which should work. Karl T |
From: Karl T. K. <ka...@pr...> - 2001-05-16 20:27:27
|
mrbrown's init.d/rcS #!/bin/sh # Remount root read-write mount -n -o remount,defaults / rm -f /etc/mtab~ mount -f -o remount,defaults / mount -a /etc/fstab root entry: 192.168.12.11:/home/mrbrown/dcdev/nfs/busybox / nfs \ defaults,errors=remount-ro 0 0 Kind regards, Karl T |
From: M. R. B. <mr...@li...> - 2001-05-16 20:48:34
|
* Karl Trygve Kalleberg <ka...@pr...> on Wed, May 16, 2001: > mrbrown's init.d/rcS > #!/bin/sh > # Remount root read-write > mount -n -o remount,defaults / > rm -f /etc/mtab~ > mount -f -o remount,defaults / > mount -a > > /etc/fstab root entry: > 192.168.12.11:/home/mrbrown/dcdev/nfs/busybox / nfs \ > defaults,errors=remount-ro 0 0 > The only thing I'd add to that is /etc/inittab: ::sysinit:/etc/init.d/rcS ::askfirst:/bin/sh But if you're using a debian distro, that should all be taken care of for you, those file above are from a busybox NFS mount. M. R. |
From: Andrew M. <amo...@st...> - 2001-05-17 20:33:26
|
I tried out these settings, as well as M.R. Brown's additions from the mailing list, but they seemed to have no effect. Karl Trygve Kalleberg wrote: >mrbrown's init.d/rcS >#!/bin/sh ># Remount root read-write >mount -n -o remount,defaults / >rm -f /etc/mtab~ >mount -f -o remount,defaults / >mount -a > >/etc/fstab root entry: >192.168.12.11:/home/mrbrown/dcdev/nfs/busybox / nfs \ >defaults,errors=remount-ro 0 0 > > >Kind regards, > >Karl T > |