I finally solved my issue too...
Looks like something was changed in the systemd boot sequence. The fstab tried mounting /dev/lsirad and verifying the file-system before the driver was installed. As when I exclude the mount from fstab, reboot and mount it manually, everything works fine. A trap is when you manually force the boot via rescue console after the FW Error occurred, the driver seems non working.
Changing the fstab entry to not verify the file-system at boot seems to make it work. Further testing still required.
Looks like something was changed in the systemd boot sequence. The fstab tried mounting /dev/lsirad and verifying the file-system before the driver was installed. As when I exclude the mount from fstab, reboot and mount it manually, everything works fine. A trap is when you manually force the boot via rescue console after the FW Error occurred, the driver seems non working.
Changing the fstab entry to not verify the file-system at boot seems to make it work. Further testing still required.
Statistics: Posted by Astralix — 2024-10-05 08:27