Hi Robert You're just the guy I'd like to talk to. Do you have any thoughts on why the mounting of /dev/mmcblk0p1 to serve as a virtual mass storage partition might have been disrupted? Does adding a cape - specifically for an LCD screen - change the set of files that are generated or run during boot? For sure. on the board without LCD if I type "mount" I get
/dev/mmcblk0p1 on /media/BEAGLEBONE type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf whereas on a board with the LCD I do not see this. Or rather, sometimes I do see it even with an LCD screen but we are not sure what conditions might make it vanish? Could we simply mount it manually by editing fstab? Regards Julian On Friday, 22 January 2016 15:12:18 UTC, RobertCNelson wrote: > > On Fri, Jan 22, 2016 at 7:30 AM, Julian Gold > <[email protected] <javascript:>> wrote: > > If anyone can explain exactly where and how the mass storage is mounted > at > > boot time (it isn't in /etc/fstab) that would be helpful? > > It's exported by an init script that calls: > > /opt/scripts/boot/am335x_evm.sh > > The current git master version of that file looks like: > > > https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L139-L157 > > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
