I ran into a similar issue when I upgraded my kernel on an existing BB-X15 
image and then attempted to run the flasher script from the SD card on a 
BB-X15:

http://beagleboard.org/discuss?place=msg%2Fbeagleboard%2Fx1mxG7c-ilg%2F2Q8OROMCAwAJ

Where Robert indicated to do:

(1) depmod -a

(2)  sudo update-initramfs -ck `uname -r`  (or update-initramfs -uk 'uname 
-r')


Not sure if updating the module dependency db is needed, but something to 
consider..



On Wednesday, May 16, 2018 at 4:05:31 PM UTC-5, RobertCNelson wrote:
>
> On Wed, May 16, 2018 at 3:56 PM, John B <[email protected] <javascript:>> 
> wrote: 
> > I found that the eMMC flasher 
> > (/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh) no longer appears to 
> work 
> > after I upgraded to Kernel 4.14.x.  I traced this to 
> > /opt/scripts/tools/eMMC/functions.sh in prepare_environment().  It seems 
> > that /proc and /sys are not mounted when the flasher script is executed 
> from 
> > init.  Needless to say, this caused agita for the rest of the script. 
>  I'm 
> > not sure if this has been addressed someplace else (maybe it has to do 
> with 
> > the fact I am using initrd.img-4.9.82-ti-r102? I doubt it though.) 
> > 
> > In any event, in case someone is running into the same issue, I have 
> > attached my updated functions.sh which addresses the issue by mounting 
> /proc 
> > and /sys just after the script does /tmp.  This seems to work fine; it 
> > should even work on a system where /proc and /sys are already mounted. 
>
>
> before you run that script, just make sure you run: 
>
> sudo update-initramfs -ck `uname -r` 
>
> 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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/3a76824b-02bb-46a6-bad7-eb41a4fb482d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to