First - I’d like to say the work done by Robert C Nelson, and others in this group is fantastic.
I created an SD card from Roberts site that looks something like this:
Linux arm 3.14.22-ti-r31 #1 SMP PREEMPT Fri Oct 24 20:50:46 UTC 2014 armv7l GNU/Linux
Is that PREEMPT_RT patched by default? Excellent.
The problem I’m having, is that I want to build a new kernel (3.14.4-bone4) from Robert’s git repo.
I followed the instructions to get it, build it, modify system.sh, and install it to the SD card I’ve got.
It looks like it’s all working… here’s the output:
Partition: [/dev/sdb1] trying: [vfat], [ext4]
Installing 3.14.4-bone4 to /dev/sdb1
Installing 3.14.4-bone4-dtbs.tar.gz to /dev/sdb1
Installing 3.14.4-bone4-modules.tar.gz to /dev/sdb1
Installing 3.14.4-bone4-firmware.tar.gz to /dev/sdb1
This script has finished…
For verification, always test this media with your end device…
But, when I put the card in and boot holding down the button, it still boots with the original kernel on the card.
Anybody got a guess at why?
I mounted the SD Card on my #! machine and the file system isn’t what I expected.
/dev/sdb1 ← some small vfat with boot/uboot
/dev/sdb2 ← everything else
It looks like it’s all on /dev/sdb1 as ext4.
and inside /boot, I see the zImage file that was copied over by install_kernel.sh, but there’s also a vmlinuz file.
I’m guessing the “install_me.sh” for the 3.x.x-ti kernel types sets up a different boot structure, and that’s why zImage is getting ignored.
Can somebody please clarify?