hello. wjz304

Thanks for the explanation on why I shouldn't just use vanilla modules instead of compiled ones.

A long time ago, we discussed the conflict between fabio and broadwellnk's ixgbe compiled module, and the method fabio chose at the time was to import a vanilla module instead of a compiled module and replace it with the integrated pack.

Even now the method is confirmed in your apl-modules/official .

I decided to explicitly copy the vanilla module to the path below and use it when bundling the integration pack.

The module of known problem was ixgbe one, but now mlx4 has been confirmed as an additional one.
I didn't have this issue in 7.1, but it is found in 7.2.
https://xpenology.com/forum/topic/62871-tinycore-redpill-loader-tcrp-development-release-09/?do=findComment&comment=444953

So, for users who want to install DSM while using mlx4 nic alone, this vanilla module was included in the integrated pack as a replacement.

https://github.com/PeterSuh-Q3/arpl-modules/tree/main/vanilla/broadwellnk-4.4.302

Have you ever identified a case where vanilla modules need to be replaced and used on other platforms?

Hi @wjz304, i think we have a big issue in redpill-lkm. If we add a lsi sas controller, the drives sometimes disapear or are not able to acces requests. it looks like, it's caused by redpill-lkm. Do you know a solution?