Would you please add a note in the following location (and/or other
applicable pages) about running init-ramfs when updating the kernel? And
maybe even a blurb about why this is needed?
On Wednesday, May 16, 2018 at 5:12:40 PM UTC-5, Jeff Andich wrote:
> 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
> Where Robert indicated to do:
> (1) depmod -a
> (2) sudo update-initramfs -ck `uname -r` (or update-initramfs -uk 'uname
> Not sure if updating the module dependency db is needed, but something to
> 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 <john...@gmail.com> wrote:
>> > I found that the eMMC flasher
>> > (/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh) no longer appears to
>> > after I upgraded to Kernel 4.14.x. I traced this to
>> > /opt/scripts/tools/eMMC/functions.sh in prepare_environment(). It
>> > that /proc and /sys are not mounted when the flasher script is executed
>> > init. Needless to say, this caused agita for the rest of the script.
>> > not sure if this has been addressed someplace else (maybe it has to do
>> > 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
>> > 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`
>> Robert Nelson
For more options, visit http://beagleboard.org/discuss
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.