I already addressed the following issue in the https://forum.odroid.com/viewtopic.php?f=99&p=378029 and the Armbian forum. A kind user pointed out that this could be a OMV6 bug, so I'm trying to seek help here also.
-------
I already posted the question in the Odroid forum. I decided to post it here too since it may be more inherent to the Armbian OS.
I used both Armbian_23.02.3_Odroidxu4_bullseye_current_5.4.239.img from the odroidxu4 archive and Armbian-unofficial_23.11.0-trunk_Odroidxu4_bullseye_current_6.1.63 generated from the Armbian build script. (Base CLI Image).
After flashing the former image and then installing OMV6, this is the output that OMV6 gives me when installing the openmediavault-wireguard plugin:
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed: linux-image-6.1.0-0.deb11.13-rt-armmp linux-image-rt-armmp wireguard wireguard-tools
Suggested packages: linux-doc-6.1 debian-kernel-handbook openresolv | resolvconf
Recommended packages: firmware-linux-free apparmor
The following NEW packages will be installed: linux-image-6.1.0-0.deb11.13-rt-armmp linux-image-rt-armmp openmediavault-wireguard wireguard wireguard-tools
0 upgraded, 5 newly installed, 0 to remove and 8 not upgraded.
(Reading database ... 45551 files and directories currently installed.)
Preparing to unpack .../linux-image-6.1.0-0.deb11.13-rt-armmp_6.1.55-1~bpo11+1_armhf.deb ...
Unpacking linux-image-6.1.0-0.deb11.13-rt-armmp (6.1.55-1~bpo11+1) ...
Selecting previously unselected package linux-image-rt-armmp.
Preparing to unpack .../linux-image-rt-armmp_6.1.55-1~bpo11+1_armhf.deb ...
Unpacking linux-image-rt-armmp (6.1.55-1~bpo11+1) ...
Selecting previously unselected package wireguard-tools.
Preparing to unpack .../wireguard-tools_1.0.20210223-1_armhf.deb ...
Unpacking wireguard-tools (1.0.20210223-1) ...
Selecting previously unselected package wireguard.
Preparing to unpack .../wireguard_1.0.20210223-1_all.deb ...
Unpacking wireguard (1.0.20210223-1) ...
Selecting previously unselected package openmediavault-wireguard.
Preparing to unpack .../openmediavault-wireguard_6.3.7_all.deb ...
Unpacking openmediavault-wireguard (6.3.7) ...
Setting up linux-image-6.1.0-0.deb11.13-rt-armmp (6.1.55-1~bpo11+1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.4.239-odroidxu4
I: /initrd.img.old is now a symlink to boot/initrd.img-5.4.239-odroidxu4
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-0.deb11.13-rt-armmp
I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-0.deb11.13-rt-armmp
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-0.deb11.13-rt-armmp:.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-0.deb11.13-rt-armmp
update-initramfs: Converting to u-boot format
Setting up wireguard-tools (1.0.20210223-1) ...
wg-quick.target is a disabled or a static unit, not starting it.
Setting up linux-image-rt-armmp (6.1.55-1~bpo11+1) ...
Setting up wireguard (1.0.20210223-1) ...
Setting up openmediavault-wireguard (6.3.7) ...
Updating configuration database ...
net.ipv4.ip_forward = 1
modprobe: FATAL: Module wireguard not found in directory /lib/modules/5.4.239-odroidxu4
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for openmediavault (6.9.8-1) ...
Updating workbench configuration files ...
Restarting engine daemon ...
END OF LINE
Alles anzeigen
Then, after rebooting, here is the output of minicom:
Spoiler
U-Boot 2017.05-armbian (Apr 04 2023 - 04:20:05 +0000) for ODROID-XU4
CPU: Exynos5422 @ 800 MHz
Model: Odroid XU4 based on EXYNOS5422
Board: Odroid XU4 based on EXYNOS5422
Type: unknown
DRAM: 2 GiB
MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
MMC Device 0 ( SD ): 59.5 GiB
Card did not respond to voltage select!
mmc_init: -95, time 12
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: No ethernet found.
Press quickly 'Enter' twice to stop autoboot: 0 ** File not found /boot.ini **
## Executing script at 43e00000
Wrong image format for "source" command
13433 bytes read in 40 ms (327.1 KiB/s)
## Executing script at 43e00000
** File not found /boot/armbianEnv.txt **
** Unrecognized filesystem type **
** File not found armbianEnv.txt **
7386616 bytes read in 594 ms (11.9 MiB/s)
35334161 bytes read in 2680 ms (12.6 MiB/s)
0 bytes read in 34 ms (0 Bytes/s)
Found mainline kernel configuration
87881 bytes read in 90 ms (953.1 KiB/s)
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
Kernel image @ 0x40008000 [ 0x000000 - 0x70b5f8 ]
## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 35334097 Bytes = 33.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
** File not found /boot.scr **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
mmc_init: -110, time 100
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
starting USB...
USB0: USB EHCI 1.00
USB1: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB2: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... XHCI timeout on event type 33... cannot recover.
BUG: failure at drivers/usb/host/xhci-ring.c:467/xhci_wait_for_event()!
BUG!
resetting ...
U-Boot 2017.05-armbian (Apr 04 2023 - 04:20:05 +0000) for ODROID-XU4
CPU: Exynos5422 @ 800 MHz
Model: Odroid XU4 based on EXYNOS5422
Board: Odroid XU4 based on EXYNOS5422
Type: unknown
DRAM: 2 GiB
MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
MMC Device 0 ( SD ): 59.5 GiB
Card did not respond to voltage select!
mmc_init: -95, time 11
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: No ethernet found.
Press quickly 'Enter' twice to stop autoboot: 0 ** File not found /boot.ini **
## Executing script at 43e00000
Wrong image format for "source" command
13433 bytes read in 41 ms (319.3 KiB/s)
## Executing script at 43e00000
** File not found /boot/armbianEnv.txt **
** Unrecognized filesystem type **
** File not found armbianEnv.txt **
7386616 bytes read in 599 ms (11.8 MiB/s)
35334161 bytes read in 2699 ms (12.5 MiB/s)
0 bytes read in 34 ms (0 Bytes/s)
Found mainline kernel configuration
87881 bytes read in 90 ms (953.1 KiB/s)
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
Kernel image @ 0x40008000 [ 0x000000 - 0x70b5f8 ]
## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 35334097 Bytes = 33.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
** File not found /boot.scr **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
mmc_init: -110, time 101
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
starting USB...
USB0: USB EHCI 1.00
USB1: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB2: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... Device NOT ready Request Sense returned 04 44 81
2 USB Device(s) found
scanning bus 2 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 1 Ethernet Device(s) found
USB device 0: Device 0: not available
Waiting for Ethernet connection... done.
BOOTP broadcast 1
Alles anzeigen
And the ODROID doesn't go further. It stays stuck at "BOOTP broadcast 1".
What could be the issue?
Thanks in advance for your help.