UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Visitor a75445
Visitor
310 Views
Registered: ‎10-25-2018

Failed to start Load Kernel Modules in a Yocto Linux Image

Hi everyone,

I created a linux image from yocto, and I am with some issues in the Linux startup. (I can startup, but some kernel modules failed to be loaded)

My sd card has two partitions (boot + root):
The boot partition has: boot.bin, Image, system.dtb e o uEnv.txt (from Xilinx pre-Realeses)
The root partition has: the filesystem (FS) generated in yocto.

In the boot process the linux failed to load some kernel modules. I think the problem is somewhere in my FS, because using the FS of the Xilinx, I had no problems.

Here is part of the boot log.

Welcome to OpenEmbedded nodistro.0!

[    5.109485] systemd[1]: Set hostname to <zcu104-zynqmp>.
[    5.134181] systemd[1]: Initializing machine ID from random generator.
[    5.199572] [drm] Cannot find any crtc or sizes
[    5.364946] systemd[1]: File /lib/systemd/system/systemd-journald.service:36 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgr.
[    5.382019] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[    5.676183] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[    5.691729] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[    5.715820] systemd[1]: Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Audit Socket.
[    5.733216] systemd[1]: Listening on Syslog Socket.
[  OK  ] Listening on Syslog Socket.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Listening on Network Service Netlink Socket.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Socket.
         Mounting Huge Pages File System...
         Mounting Kernel Debug File System...
         Mounting POSIX Message Queue File System...
         Starting Journal Service...
         Starting Remount Root and Kernel File Systems...
[    5.941737] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
         Starting Load Kernel Modules...
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Swap.
         Mounting Temporary Directory (/tmp)...
         Starting udev Coldplug all Devices...
[  OK  ] Started Journal Service.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Started Remount Root and Kernel File Systems.
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[  OK  ] Mounted Temporary Directory (/tmp).
         Mounting Kernel Configuration File System...
         Mounting NFSD configuration filesystem...
         Starting Apply Kernel Variables...
         Starting Rebuild Hardware Database...
         Starting Create System Users...
         Starting Flush Journal to Persistent Storage...
[  OK  ] Mounted Kernel Configuration File System.
[FAILED] Failed to mount NFSD configuration filesystem.
See 'systemctl status proc-fs-nfsd.mount' for details.
[DEPEND] Dependency failed for NFS server and services.
[DEPEND] Dependency failed for NFS Mount Daemon.
[  OK  ] Started Apply Kernel Variables.
[    6.289079] systemd-journald[1701]: Received request to flush runtime journal from PID 1
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Create System Users.
         Starting Create Static Device Nodes in /dev...
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /var/volatile...
[  OK  ] Reached target Containers.
[  OK  ] Mounted /var/volatile.
         Starting Load/Save Random Seed...
[  OK  ] Reached target Local File Systems.
         Starting Rebuild Journal Catalog...
         Starting Rebuild Dynamic Linker Cache...
         Starting Create Volatile Files and Directories...
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Rebuild Journal Catalog.
[  OK  ] Started Create Volatile Files and Directories.
         Starting Network Time Synchronization...
         Starting Update UTMP about System Boot/Shutdown...
         Starting Run pending postinsts...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Rebuild Hardware Database.
         Starting udev Kernel Device Manager...
[  OK  ] Started Run pending postinsts.
[  OK  ] Started udev Kernel Device Manager.
         Starting Network Service...
[  OK  ] Found device /dev/ttyPS0.
[  OK  ] Started Network Service.
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
         Starting Network Name Resolution...
         Starting Load Kernel Modules...
         Starting Run pending postinsts...
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
         Mounting NFSD configuration filesystem...
[FAILED] Failed to mount NFSD configuration filesystem.
See 'systemctl status proc-fs-nfsd.mount' for details.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Host and Network Name Lookups.
[  OK  ] Reached target Network.
[  OK  ] Started Run pending postinsts.
[  OK  ] Started Rebuild Dynamic Linker Cache.
         Starting Update is Completed...
[  OK  ] Started Update is Completed.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on D-Bus System Message Bus Socket.
         Starting sshd.socket.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timers.
[  OK  ] Listening on GPS (Global Positioning System) Daemon Sockets.
[  OK  ] Listening on RPCbind Server Activation Socket.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on sshd.socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting Telephony service...
[  OK  ] Started Serial Getty on ttyS0.
         Starting RPC Bind Service...
[  OK  ] Started Kernel Logging Service.
         Starting Network Time Service (one-shot ntpdate mode)...
         Starting Avahi mDNS/DNS-SD Stack...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Getty on tty1.
[  OK  ] Started System Logging Service.
[  OK  ] Started Xinetd A Powerful Replacement For Inetd.
[  OK  ] Started Serial Getty on ttyPS0.
[  OK  ] Reached target Login Prompts.
         Starting Login Service...
         Starting Save/Restore Sound Card State...
[  OK  ] Started RPC Bind Service.
[  OK  ] Started Network Time Service (one-shot ntpdate mode).
[  OK  ] Started Save/Restore Sound Card State.
[  OK  ] Reached target Sound Card.
         Starting Network Time Service...
[  OK  ] Started NFS status monitor for NFSv2/3 locking..
[  OK  ] Started Login Service.
[  OK  ] Started Network Time Service.
[  OK  ] Started Telephony service.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Reached target Multi-User System.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.

OpenEmbedded nodistro.0 zcu104-zynqmp ttyPS0

Does someone have any idea how can I resolve this?

 

Best regards

0 Kudos
9 Replies
Voyager
Voyager
226 Views
Registered: ‎09-14-2016

Re: Failed to start Load Kernel Modules in a Yocto Linux Image

Hi @a75445,

 

Please provide 

See 'systemctl status systemd-modules-load.service' for details.

Cheers,

Trigger 

0 Kudos
Visitor a75445
Visitor
224 Views
Registered: ‎10-25-2018

Re: Failed to start Load Kernel Modules in a Yocto Linux Image

Hi @trigger ,

Thanks for the reply.

root@zcu104-zynqmp:~# systemctl status systemd-modules-load.service
��● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2020-01-25 04:48:55 UTC; 20s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 3020 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 3020 (code=exited, status=1/FAILURE)

Jan 25 04:48:55 zcu104-zynqmp systemd[1]: Starting Load Kernel Modules...
Jan 25 04:48:55 zcu104-zynqmp systemd-modules-load[3020]: Failed to find module 'fuse'
Jan 25 04:48:55 zcu104-zynqmp systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Jan 25 04:48:55 zcu104-zynqmp systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Jan 25 04:48:55 zcu104-zynqmp systemd[1]: Failed to start Load Kernel Modules.
root@zcu104-zynqmp:~# 

Cheers

0 Kudos
Voyager
Voyager
210 Views
Registered: ‎09-14-2016

Re: Failed to start Load Kernel Modules in a Yocto Linux Image

Hi @a75445 


Failed to find module 'fuse'

 

As you are working with Yocto : http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-kernel/fuse/fuse_2.7.2.bb?h=laverne

 

IMAGE_INSTALL += " fuse " 

 

inside recipe image or conf/local.conf

 

Cheers,

Trigger

0 Kudos
Visitor a75445
Visitor
195 Views
Registered: ‎10-25-2018

Re: Failed to start Load Kernel Modules in a Yocto Linux Image

Hi @trigger,

Thanks one more time for the reply,

I am not using the yocto from its git repository, I am using the oe-gnss-sdr-manifest, which uses fuse_2.9.8.

I wasn't able to find the fuse folder in the recipes-kernel, however, I found it in meta-oe/meta-filesystems/recipes-support.

I will try your suggestion.

If that resolves my problem I will mark your reply as solution.

Cheers

0 Kudos
Visitor a75445
Visitor
104 Views
Registered: ‎10-25-2018

Re: Failed to start Load Kernel Modules in a Yocto Linux Image

Hi @trigger,

I have tried what you suggested and didn't resolve my problem.

First I used IMAGE_INSTALL += " fuse " and my Linux stops booting (kernel panic)

After that occurred I checked the yocto documentation and it says the following:

  • Using IMAGE_INSTALL with the += operator from the /conf/local.conf file or from within an image recipe is not recommended as it can cause ordering issues.
  • When you use this variable, it is best to use it as follows:
    • IMAGE_INSTALL_append = " package-name"

So I tried IMAGE_INSTALL_append = " fuse" and I got the same problem.

Failed to find module 'fuse'

 Any more suggestions?

Cheers.

0 Kudos
Voyager
Voyager
62 Views
Registered: ‎09-14-2016

Re: Failed to start Load Kernel Modules in a Yocto Linux Image

Hi @a75445 

 

Could you provide us error log ?

 

Cheers,

Trigger

0 Kudos
Voyager
Voyager
61 Views
Registered: ‎09-14-2016

Re: Failed to start Load Kernel Modules in a Yocto Linux Image

Maybe enable CONFIG_FUSE_FS in kernel configuration
0 Kudos
Visitor a75445
Visitor
44 Views
Registered: ‎10-25-2018

Re: Failed to start Load Kernel Modules in a Yocto Linux Image

Hi @trigger ,

The log file is the same as my first post.

I can be wrong, but I think that the kernel is not the problem, because I am using the kernel provided by Xilinx Linux releases.

What I have, to be more clear, is:

  • A boot partition with: BOOT.BIN + uEnv.txt, Image and zynqmp-zcu104-revC.dtb [All from 2019.2-zcu104-release]
  • A root partition with: the filesystem generated by yocto.

I think the problem is in the filesystem because when I use the filesystem from 2019.2-zcu104-release all goes right and when I use my filesystem the problems that I aforementioned happen.

Cheers and thank you for the replay

0 Kudos
Voyager
Voyager
20 Views
Registered: ‎09-14-2016

Re: Failed to start Load Kernel Modules in a Yocto Linux Image

@a75445 

 

I don't have any idea :S

You can maybe take a look inside your rootfs and double check that driver is correctly deploy ? And try to built-in inside the kernel itself.

 

Cheer,

Trigger

0 Kudos