On 25/06/14 17:00, Michael Biebl wrote:
Ben, Russel: I'm about to make the upload with the change Martin
mentioned, but it would be great if you can confirm that using
SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST!="[module/sg]",
RUN+="/sbin/modprobe -b sg"
actually works for you as well.
Am 25.06.2014 10:20, schrieb Martin Pitt:
> E. g. in wheezy the rule looked like
>
> SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST!="[module/sg]",
> RUN+="/sbin/modprobe -b sg"
>
> So the main change was that we now use the kmod builtin instead of
> calling modprobe. The latter is much
On Wed, 25 Jun 2014 09:02:59 Michael Biebl wrote:
> Russel, can you confirm that that reverting the "kmod load sg" patch
> also fixes your problem?
It seems to. Booted once since applying it and it worked.
--
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.c
Hello all,
Michael Biebl [2014-06-25 9:01 +0200]:
> This was one of the patches you merged over from Ubuntu and it seems
> that loading the sg module does break luks+crypt.
>
> Do you remember why that patch was needed in the first place?
No, it didn't come from Ubuntu, but this has been a Debi
Some updates after more debugging.
The original rule was
SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST!="[module/sg]", \
RUN+="/sbin/modprobe -b sg"
and was added to fix [1].
Apparently this didn't cause any issues so far.
This was then modified to
5 matches
Mail list logo
