We remerge every week, so I believe we were already using the latest zz-uenv. The error was caused by trying to match single quotes in the sed command. This can be fixed by replacing the outermost single quotes with double quotes.
Best, Alex On Fri, Sep 19, 2014 at 2:47 AM, Alexander Hayman <[email protected]> wrote: > Thanks Robert. I've started using the 3.14 kernel (although the less > bleeding edge bone8 version), and I built a custom dtb to enable both the > 4Dcape-43t and a secondary non-pin-conflicting uart using your bb-kernel > repo. It's worked beautifully. Apologies to Scott for not being able to > follow up on his 3.8 kernel patch. > > I ran into issues when using apt to install the ti-rXX kernels. The apt-get > install command fails due to single quotes in an sed command in a zz-uenv > file. We tried to get it to run by replacing the single quotes around > older_kernel and latest_kernel with ' " ' " ', but then something broke on > reset, and I forget now what errors we were seeing. It's possible these > issues have been resolved recently. I'll try installing the latest kernel > sometime when it isn't past 3am. :) it took a couple release to get all the bugs out, can you retest with the git version? https://raw.githubusercontent.com/RobertCNelson/omap-image-builder/master/target/other/zz-uenv_txt > We've been using omap-image-builder, and setup-sdcard.sh exits when a -ti- > kernel is specified. This is another reason, albeit possibly misguided, > that we shied away from using the -ti- kernels and stuck to the bone > kernels. I'm not sure what the difference is? I'll hack on this today, i have a bunch of logic for the bone's to make sure they got the "-bone" kernel at all cost, i'm going to change that to a "-bone" || "-ti". > One more comment about our adventures with omap-image-builder. We added > usbmount to the package list in omap-image-builder, and usbmount uses > /media/usbX as mount points, so it creates those directories. > The init-eMMC-flasher-v3 excludes /media/* from being rsync'ed so we added > the necessary mkdir -p's after the relevant rsync to fix this. I think we can safely enable this now. Since the flasher is running at boot in a single user environment, usbmount shouldn't mount an external device, so only the base /media/<dir> should be present while it's flashing. The whole point of disabling /media/ from rsync, when we ran after the board fully booted, there was a risk the user had a big full usb drive plugged in and was mounted to /media/, this would have overfilled the eMMC. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visithttp://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/sjJJWe2dkb4/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. For more options, visithttps://groups.google.com/d/optout. -- 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.
