Skip to contentSkip to conversation

any kernel changes break module sysmtable

yocto Rob Prowel 1 participant 1 message Aug 3, 2020 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Rob Prowel

author
#1 lore raw
Quoted 7 lines · Rob Prowel

More hassle dealing with vendor supplied yocto distro.

In the original "sumo" yocto release that the vendor sent us I could easily change their static flash image to a rootnfs image and tftpboot the kernel, bitstream, and DTB, and use nfs as a root filesystem.  This works great for development and not having to constantly go thru the slow flash update process.

Problem is that their updated release (also sumo) breaks any time I introduce a new kernel fragment like turning on rootnfs.  The resulting image will boot but all attempts to modprobe or insmod any modules result in the error

[    8.237421] xxx_dev: disagrees about version of symbol module_layout

Make a note!

Always double check the name and version of the kernel you are booting against the one you THINK you are loading. This becomes particularly easy to screw up when doing nfs or tftp boots.

Problem was of my own doing:

concatenating a lengthy u-boot string I used ${name} instead of ${hostname} so the wrong kernel was being tftp loaded...and I didn't catch this for a week!

problem solved!