You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
./compile.sh kernel BOARD=helios64 BRANCH=edge RELEASE=bookworm BUILD_KSRC=no
(...)
[馃惓|馃尡] Starting main configuration
[馃惓|馃尡] Using REVISION from [ main VERSION file: '24.5.0-trunk' ]
modprobe: FATAL: Module ext4 not found in directory /lib/modules/6.7.12-amd64
[馃惓|馃挜] error! [ Filesystem type unsupported by build host: ext4 ]
[馃惓|馃挜] Exiting with error 43 [ at /armbian/lib/functions/logging/traps.sh:1
exit_with_error() --> lib/functions/logging/traps.sh:1
check_filesystem_compatibility_on_host() --> lib/functions/configuration/main-config.sh:535
do_main_configuration() --> lib/functions/configuration/main-config.sh:143
do_with_logging() --> lib/functions/logging/section-logging.sh:81
do_with_conditional_logging() --> lib/functions/logging/section-logging.sh:111
prep_conf_main_minimal_ni() --> lib/functions/main/config-prepare.sh:72
artifact_kernel_cli_adapter_config_prep() --> lib/functions/artifacts/artifact-kernel.sh:265
artifact_cli_adapter_config_prep() --> lib/functions/artifacts/artifacts-obtain.sh:34
cli_artifact_run() --> lib/functions/cli/cli-artifact.sh:36
armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136
cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176
main() --> compile.sh:50
]
There might be no clean fix without requiring root access, but output an error message that state that ext4 loaded is required might be enough.
How to reproduce?
I did not test it but I supposed it is enough to run the build in a VM with a Linux system that has no ext4 filesystem loaded.
On such a system (mine is a bare install with only btrfs filesystems) where ext4 is not laded running: ./compile.sh kernel BOARD=helios64 BRANCH=edge RELEASE=bookworm BUILD_KSRC=no
Branch
main (main development branch)
On which host OS are you running the build script and observing this problem?
ext4 module is available on the build host despite the error telling otherwise, and running sudo modprobe ext4 o the build host is a working workaround.
ls /lib/modules/6.7.12-amd64/kernel/fs//ext4
ext4.ko.xz
What happened?
There might be no clean fix without requiring root access, but output an error message that state that ext4 loaded is required might be enough.
How to reproduce?
I did not test it but I supposed it is enough to run the build in a VM with a Linux system that has no ext4 filesystem loaded.
On such a system (mine is a bare install with only btrfs filesystems) where ext4 is not laded running:
./compile.sh kernel BOARD=helios64 BRANCH=edge RELEASE=bookworm BUILD_KSRC=no
Branch
main (main development branch)
On which host OS are you running the build script and observing this problem?
Debian 13 Trixie
Are you building on Windows WSL2?
Relevant log URL
https://paste.armbian.com/ihebugunif
Code of Conduct
The text was updated successfully, but these errors were encountered: