基于Yocto构建Xilinx PCIe驱动后直接拷贝.ko文件加载遇问题求助

Got it, let's walk through the common issues when manually copying a Yocto-built kernel module to your target device, and how to fix them—since you skipped Yocto's standard module packaging workflow, there are a few critical pieces you're missing:

1. Kernel Version/Configuration Mismatch #

Kernel modules are tightly tied to the exact kernel they're compiled against. Even minor differences (like a patch level or enabled config flag) will cause loading to fail.

• On your target device, run uname -r to get the running kernel version.
• On your build host, check the module's compiled kernel info with:

  modinfo xpcie.ko | grep vermagic
  

• The vermagic string from both commands must match exactly. If they don't, you need to recompile the module against the exact kernel source/config used for your target image.

2. Missing Module Dependencies #

Your PCIe module might rely on other kernel modules that aren't loaded yet.

• Try loading the module manually with insmod /lib/modules/xpcie.ko—this will give you a clear error if there's a missing dependency (e.g., Unknown symbol in module).
• Resolve dependencies by loading the required modules first, or use modprobe xpcie once you've fixed the module index (see next step).

3. Stale Module Index Files #

Yocto automatically generates module index files (modules.dep, modules.symbols, etc.) in /lib/modules/<kernel-version>/ when packaging modules. Copying the .ko file manually doesn't update these.

• On your target device, navigate to the kernel version directory (replace <kernel-version> with the output from uname -r):

  cd /lib/modules/<kernel-version>/
  

• Run depmod -a to regenerate the index files. This lets modprobe locate and load your module correctly.

4. Permissions or SELinux Issues #

• Check the permissions of your module file:

  ls -l /lib/modules/xpcie.ko
  

  It should have read permissions for all users (e.g., -rw-r--r--). Fix permissions with chmod 644 /lib/modules/xpcie.ko if needed.
• If your target has SELinux enabled, it might block the module. Test temporarily by running setenforce 0, then try loading the module. If it works, restore the SELinux context with:

  restorecon -v /lib/modules/xpcie.ko
  

5. Recommended: Switch to Yocto's Standard Module Packaging #

Since you're already using Yocto to build the module, it's far more reliable to let Yocto handle packaging and installation:

• Update your met recipe to include the module: Add KERNEL_MODULES += "xpcie" and optionally KERNEL_MODULE_AUTOLOAD += "xpcie" to auto-load the module on boot.
• Rebuild the recipe with bitbake met—this generates a package (RPM/DEB) that includes the module and handles all index files, dependencies, and version matching.
• Copy the generated package from your build directory (usually under tmp/deploy/rpm/ or tmp/deploy/deb/) to the target, then install it with rpm -i <package-name>.rpm or dpkg -i <package-name>.deb.

内容的提问来源于stack exchange，提问作者Newbie_SW