------- Comment From <email address hidden> 2016-07-21 12:08 EDT-------
@adconrad,
> There were huge updates to the scsi_dh_alua driver in the 4.4.0-30 kernel.
> I can't see the LTC bug you referenced, so I can't tell if said updates
> address your issue, but I was hopeful. :P
Ok, I see. I'll ask if that helps w/ the other bug.
Nevertheless, having modprobe.blacklist working by default on the installer would be interesting.
I passed around a sed line to use modprobe -b on hw-detect, a simple workaround, but that definitely isn't convenient (neither for preseed). And since I don't know much of modprobe and its usage on the installer, I decided to reach out for you guys first.
Now that is seems to be clear, can get hw-detect be updated to use modprobe -b ?
------- Comment From <email address hidden> 2016-07-21 12:08 EDT-------
@adconrad,
> There were huge updates to the scsi_dh_alua driver in the 4.4.0-30 kernel.
> I can't see the LTC bug you referenced, so I can't tell if said updates
> address your issue, but I was hopeful. :P
Ok, I see. I'll ask if that helps w/ the other bug.
Nevertheless, having modprobe.blacklist working by default on the installer would be interesting.
I passed around a sed line to use modprobe -b on hw-detect, a simple workaround, but that definitely isn't convenient (neither for preseed). And since I don't know much of modprobe and its usage on the installer, I decided to reach out for you guys first.
Now that is seems to be clear, can get hw-detect be updated to use modprobe -b ?
Thanks!