From: David S. <dav...@nt...> - 2006-05-01 10:51:48
|
Hi, I've been trying to get my mmc card to automount on startup of the gumstix by changing noauto in fstab to defaults. This seems to make no difference unfortunately. Once the gumstix has started if I enter "mount /mnt/mmc" or "mount -a" the mmc mount is brought up no problems. I'm using the 2.6.15 kernel on basix 200 bt. I've read in other posts about modules needing to be loaded first but I thought that was with older versions of the kernel and the fstab method should work regardless here. Any ideas? Cheers Dave |
From: Craig H. <cr...@gu...> - 2006-05-01 11:48:18
|
On May 1, 2006, at 3:51 AM, David Scanlan wrote: > I=92ve been trying to get my mmc card to automount on startup of the =20= > gumstix by changing noauto in fstab to defaults. This seems to =20 > make no difference unfortunately. Once the gumstix has started if =20 > I enter =93mount /mnt/mmc=94 or =93mount =96a=94 the mmc mount is = brought up =20 > no problems. I=92m using the 2.6.15 kernel on basix 200 bt. I=92ve =20= > read in other posts about modules needing to be loaded first but I =20 > thought that was with older versions of the kernel and the fstab =20 > method should work regardless here. Any ideas? Cheers the "mount -a" is run from /etc/inittab before the rc.modules script =20 is run -- so the mmc driver and the mmc block driver have not yet =20 been loaded, so there is no /dev/mmcblk* to mount, so mount -a in /=20 etc/inittab doesn't mount it. You can add a manual "/sbin/modprobe =20 mmc_block; /sbin/modprobe pxamci" in /etc/inittab ahead of the "mount =20= -a" command to ensure that the right modules are already loaded =20 before the mount is attempted. Or easier, just compile the MMC stuff =20= into the kernel instead of building it as modules, then it'll be =20 there for sure. C |
From: John G. C. <co...@lg...> - 2006-05-01 12:19:17
|
David, another choice is to put the MMC mount stuff in /etc/init.d. Name it S50mountMMC and make sure that it is executable: Here is some that will work for a default vfat. Copy and paste it into a file, name it as above (or anything that starts with a capital S and move it to the gumstix /etc/init.d/. This particular version, tries to guarantee that the MMC is mounted for read and write John #!/bin/sh # See how we were called. prog="mmc" start() { echo $"Mounting $prog: " mount /mnt/mmc tmp=`mount | grep "/mnt/mmc" | grep "(rw," | wc -l | awk ' {print $1}; ' ` if [ $tmp = "0" ]; then echo "mmc mounted readonly - remounting rw" umount /mnt/mmc mount /mnt/mmc fi } stop() { umount /mnt/mmc } case "$1" in start) start ;; stop) stop ;; *) echo $"Usage: $0 {start|stop}" exit 1 esac Craig Hughes wrote: > On May 1, 2006, at 3:51 AM, David Scanlan wrote: > >> I’ve been trying to get my mmc card to automount on startup of the >> gumstix by changing noauto in fstab to defaults. This seems to make >> no difference unfortunately. Once the gumstix has started if I enter >> “mount /mnt/mmc” or “mount –a” the mmc mount is brought up no >> problems. I’m using the 2.6.15 kernel on basix 200 bt. I’ve read in >> other posts about modules needing to be loaded first but I thought >> that was with older versions of the kernel and the fstab method >> should work regardless here. Any ideas? Cheers >> > > the "mount -a" is run from /etc/inittab before the rc.modules script > is run -- so the mmc driver and the mmc block driver have not yet been > loaded, so there is no /dev/mmcblk* to mount, so mount -a in > /etc/inittab doesn't mount it. You can add a manual "/sbin/modprobe > mmc_block; /sbin/modprobe pxamci" in /etc/inittab ahead of the "mount > -a" command to ensure that the right modules are already loaded before > the mount is attempted. Or easier, just compile the MMC stuff into > the kernel instead of building it as modules, then it'll be there for > sure. > > C > |
From: David S. <dav...@nt...> - 2006-05-01 12:33:07
|
Cheers fellas...I'll give it a try later today. Dave -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of John G. Cole Sent: 01 May 2006 13:19 To: gum...@li... Subject: Re: [Gumstix-users] Can't automount mmc card (using fstab - 2.6.15 kernel) David, another choice is to put the MMC mount stuff in /etc/init.d. Name it S50mountMMC and make sure that it is executable: Here is some that will work for a default vfat. Copy and paste it into a file, name it as above (or anything that starts with a capital S and move it to the gumstix /etc/init.d/. This particular version, tries to guarantee that the MMC is mounted for read and write John #!/bin/sh # See how we were called. prog="mmc" start() { echo $"Mounting $prog: " mount /mnt/mmc tmp=`mount | grep "/mnt/mmc" | grep "(rw," | wc -l | awk ' {print $1}; ' ` if [ $tmp = "0" ]; then echo "mmc mounted readonly - remounting rw" umount /mnt/mmc mount /mnt/mmc fi } stop() { umount /mnt/mmc } case "$1" in start) start ;; stop) stop ;; *) echo $"Usage: $0 {start|stop}" exit 1 esac Craig Hughes wrote: > On May 1, 2006, at 3:51 AM, David Scanlan wrote: > >> I've been trying to get my mmc card to automount on startup of the >> gumstix by changing noauto in fstab to defaults. This seems to make >> no difference unfortunately. Once the gumstix has started if I enter >> "mount /mnt/mmc" or "mount -a" the mmc mount is brought up no >> problems. I'm using the 2.6.15 kernel on basix 200 bt. I've read in >> other posts about modules needing to be loaded first but I thought >> that was with older versions of the kernel and the fstab method >> should work regardless here. Any ideas? Cheers >> > > the "mount -a" is run from /etc/inittab before the rc.modules script > is run -- so the mmc driver and the mmc block driver have not yet been > loaded, so there is no /dev/mmcblk* to mount, so mount -a in > /etc/inittab doesn't mount it. You can add a manual "/sbin/modprobe > mmc_block; /sbin/modprobe pxamci" in /etc/inittab ahead of the "mount > -a" command to ensure that the right modules are already loaded before > the mount is attempted. Or easier, just compile the MMC stuff into > the kernel instead of building it as modules, then it'll be there for > sure. > > C > ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.5.1/327 - Release Date: 4/28/2006 |
From: Dave H. <dhy...@gm...> - 2006-05-01 13:45:07
|
> David, another choice is to put the MMC mount stuff in /etc/init.d. > Name it S50mountMMC and make sure that it is executable: And yet another choice. I added the mount of mmc in my inittab after rcS (although it could also go after the rc.modules) null::sysinit:/bin/mount -a null::sysinit:/bin/hostname -F /etc/hostname # load up the modules ::sysinit:/etc/init.d/rc.modules # now run any rc scripts ::sysinit:/etc/init.d/rcS start null::sysinit:/bin/mount /mnt/mmc -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: David S. <dav...@nt...> - 2006-05-01 13:55:48
|
Hmm...thought I'd tried this atually...obviously didn't have something = in the right place! Ta -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Dave = Hylands Sent: 01 May 2006 14:45 To: gum...@li... Subject: Re: [Gumstix-users] Can't automount mmc card (using fstab - = 2.6.15 kernel) > David, another choice is to put the MMC mount stuff in /etc/init.d. > Name it S50mountMMC and make sure that it is executable: And yet another choice. I added the mount of mmc in my inittab after rcS (although it could also go after the rc.modules) null::sysinit:/bin/mount -a null::sysinit:/bin/hostname -F /etc/hostname # load up the modules ::sysinit:/etc/init.d/rc.modules # now run any rc scripts ::sysinit:/etc/init.d/rcS start null::sysinit:/bin/mount /mnt/mmc -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, = security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache = Geronimo http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=120709&bid&3057&dat=121642 _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users --=20 No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.5.1/327 - Release Date: 4/28/2006 |
From: David S. <dav...@nt...> - 2006-05-05 18:05:23
|
Hi can you just confirm that these are the only modules which would need to be changed to be compiled into the kernel to get this working: File systems -> DOS/FAT/NT Filesystems -> VFAT Device drivers -> MMC/SD Card support -> MMC support Device drivers -> MMC/SD Card support -> MMC block device driver Device drivers -> MMC/SD Card support -> Intel PXA255 Multimedia Card Interface support Then change noauto to defaults for the mmc line in fstab? Cheers Dave _____ From: gum...@li... [mailto:gum...@li...] On Behalf Of Craig Hughes Sent: 01 May 2006 12:48 To: gum...@li... Subject: Re: [Gumstix-users] Can't automount mmc card (using fstab - 2.6.15 kernel) On May 1, 2006, at 3:51 AM, David Scanlan wrote: I've been trying to get my mmc card to automount on startup of the gumstix by changing noauto in fstab to defaults. This seems to make no difference unfortunately. Once the gumstix has started if I enter "mount /mnt/mmc" or "mount -a" the mmc mount is brought up no problems. I'm using the 2.6.15 kernel on basix 200 bt. I've read in other posts about modules needing to be loaded first but I thought that was with older versions of the kernel and the fstab method should work regardless here. Any ideas? Cheers the "mount -a" is run from /etc/inittab before the rc.modules script is run -- so the mmc driver and the mmc block driver have not yet been loaded, so there is no /dev/mmcblk* to mount, so mount -a in /etc/inittab doesn't mount it. You can add a manual "/sbin/modprobe mmc_block; /sbin/modprobe pxamci" in /etc/inittab ahead of the "mount -a" command to ensure that the right modules are already loaded before the mount is attempted. Or easier, just compile the MMC stuff into the kernel instead of building it as modules, then it'll be there for sure. C |
From: Craig H. <cr...@gu...> - 2006-05-05 18:18:21
|
You'll need the NLS stuff too, since vfat needs it. It's under =20 filesystems in menuconfig. And you don't need to compile them into =20 the kernel, you need only modprobe them before you try to do the =20 mount -a. C On May 5, 2006, at 11:04 AM, David Scanlan wrote: > Hi can you just confirm that these are the only modules which would =20= > need to be changed to be compiled into the kernel to get this working: > > > > File systems -> DOS/FAT/NT Filesystems -> VFAT > > > > Device drivers -> MMC/SD Card support -> MMC support > > Device drivers -> MMC/SD Card support -> MMC block device driver > > Device drivers -> MMC/SD Card support -> Intel PXA255 Multimedia =20 > Card Interface support > > > > Then change noauto to defaults for the mmc line in fstab? > > > > Cheers > > > Dave > > > > > > From: gum...@li... [mailto:gumstix-=20 > use...@li...] On Behalf Of Craig Hughes > Sent: 01 May 2006 12:48 > To: gum...@li... > Subject: Re: [Gumstix-users] Can't automount mmc card (using fstab =20 > - 2.6.15 kernel) > > > > On May 1, 2006, at 3:51 AM, David Scanlan wrote: > > > > > I=92ve been trying to get my mmc card to automount on startup of the =20= > gumstix by changing noauto in fstab to defaults. This seems to =20 > make no difference unfortunately. Once the gumstix has started if =20 > I enter =93mount /mnt/mmc=94 or =93mount =96a=94 the mmc mount is = brought up =20 > no problems. I=92m using the 2.6.15 kernel on basix 200 bt. I=92ve =20= > read in other posts about modules needing to be loaded first but I =20 > thought that was with older versions of the kernel and the fstab =20 > method should work regardless here. Any ideas? Cheers > > > > the "mount -a" is run from /etc/inittab before the rc.modules =20 > script is run -- so the mmc driver and the mmc block driver have =20 > not yet been loaded, so there is no /dev/mmcblk* to mount, so mount =20= > -a in /etc/inittab doesn't mount it. You can add a manual "/sbin/=20 > modprobe mmc_block; /sbin/modprobe pxamci" in /etc/inittab ahead of =20= > the "mount -a" command to ensure that the right modules are already =20= > loaded before the mount is attempted. Or easier, just compile the =20 > MMC stuff into the kernel instead of building it as modules, then =20 > it'll be there for sure. > > > > C > > > > |