Hey thanks again Robert for going out of your way to provide a procedure for 3.14.x , and especially for replying while away on your holiday!
Following the procedure for the dpkg method, in which the file "0001-mmc-Allow-forwar-compatibility-for-eMMC.patch" in placed in /yakbuild/patches/local_patches/ and then running ."/build_sh" seems to work ok on my Ubuntu 19.10 VM, it yielded me the following files in the /yakbuild/deploy/ linux-firmware-image-3.14.77-ti-r90_1xross_armfhf.deb linux-headers-3.14.77-ti-r90_1xross_armhf.deb *linux-image-3.14.77-ti-r90_1xross_armhf.deb* linux-libc-dev_1xross_armhf.deb Placing the file "linux-image-3.14.77-ti-r90_1xross_armhf.deb" on my BBB attempting to run the command "sudo dpkg -i linux-image-3.14.77-ti-r90_1xross_armhf.deb" however gave me the following error: dpkg-deb error: archive 'linux-image-3.14.77-ti-r90_1xross_armhf.deb" contains not understood data member control.tar.xz, giving up dpkg: error processing linux-image-3.14.77-ti-r90_1xross_armhf.deb (--install): subprocess dpkg-deb --control returned error exit status 2 Errors were encountered while processing: linux-image-3.14.77-ti-r90_1xross_armhf.deb Some googling makes me think this is an issue with my version of dpkg on the BBB (although I never recieved any errors when using dpkg, with other 3.14.x linux-image deb files obtained from http://repos.rcn-ee.net/debian/pool/main/l/linux-upstream/) The most commonly suggested fix was to run the following commands on my BBB sudo apt-get clean sudo apt-get update sudo apt-get install dpkg But I since Wheezy is EOL, I wasn't able to update dpkg. I know that the version on my BBB is 1.16.18 (armhf) and apparently since the release of dpkg 1.19.0 control.tar* files will be compressed using xz, as mentioned here: https://github.com/aptly-dev/aptly/issues/655 On Wednesday, 19 February 2020 03:07:50 UTC+11, RobertCNelson wrote: > > > So following the instructions seen here: > https://gist.github.com/RobertCNelson/39faf80ddc9fcefae74dce2c6ca2eb45 > > In my case I'm using Ubuntu 19.10 through a VM, I noticed that after > cloning the repo and placing both patches in > /yakbuild/patches/local_patches/ > > > > and editting recipe.sh to use toolchain "gcc_linaro_gnueabihf_4_8" and > kernel_tag="3.14.77-ti-r90", then running build_kernel.sh, I noticed the > following lines in the terminal: > > > > > > Applying: mmc: core: Update the ext-csd.rev check for eMMC5.1 > > error: patch failed: drivers/mmc/core/mmc.c:292 > > error: drivers/mmc/core/mmc.c: patch does not apply > > Patch failed at 0001 mmc: core: Update the ext-csd.rev check for eMMC5.1 > > hint: Use 'git am --show-current-patch' to see the failed patch > > When you have resolved this problem, run "git am --continue". > > If you prefer to skip this patch, run "git am --skip" instead. > > To restore the original branch and stop patching, run "git am --abort". > > fatal: previous rebase directory .git/rebase-apply still exists but mbox > given. > > patch.sh ran successfully > > > > In any case the script continues to run for another ~30-40 mins and > yielded the following files: > > 3.14.77-ti-r90.zImage, 3.14.77-ti-r90-dtbs.tar.gz, > 3.14.77-ti-r90-firmware.tar.gz, 3.14.77-ti-r90-modules.tar.gz and > config-3.14.77-ti-r90 > > > > Of course placing the files in their corresponding locations on my BBB, > didn't work. I also attempted the process with other 3.14.x kernel_tags but > the same error occured. Just wondering if there's something I am > overlooking? > > Okay, gist/repo is now updated.. > > > https://gist.github.com/RobertCNelson/39faf80ddc9fcefae74dce2c6ca2eb45#file-procedure-3-14-x > > > > https://github.com/RobertCNelson/yakbuild/commit/f69aa1dbf1347cce2dc6b19de33c8bc4f3af3226 > > > Based on your current seria logs, you should just do the > "./build_deb.sh" route, and install the file via dpkg on your microsd > card.. > > > 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/14ff5a15-81d8-4e66-80d6-7b8440e76e2f%40googlegroups.com.
