[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#796250: linux-image-4.0.0-2-amd64: sg module broken?



Control: severity -1 normal
Control: tag -1 moreinfo
Control: tag -1 - upstream patch

On Thu, 2015-08-20 at 14:05 -0500, Richard Jasmin wrote:
> Package: src:linux
> Version: 4.0.8-2
> Severity: grave
> Tags: upstream patch
> Justification: renders package unusable

No, it doesn't.

> when using ImgBurn under wine, the reccommended path is to make sure sg module
> is loaded.
> 
> This works under Fedora(consider it UPSTREAM BLEEDING EDGE debian) but not
> under stretch.I have tried both SPTI and ASPI settings, and neither seem to
> work for ImgBurn to detect my drives under stretch. ASPI mode works just fine
> under Fedora.
> 
> This is neither a program bug in ImgBurn nor a wine deficiency.It is a
> communication problem between userspace application and kernel drivers.The
> issue occurs somewhere between the windows layer and the kernel functions for
> raw device access.The sg module SHOULD provide these needed "generic scsi"
> functions.

Does your user have permission to access the sg devices?

> And for some odd other reason, my kernel version is being kept back even though
> I am not freezing it.I am stuck at 4002, even if newer version is available.

Did you install linux-image-amd64?  That metapackage (or similar for
other kernel flavours) is the way to get upgrades automatically, as the
name of the package containing the kernel changes whenever the module
ABI does.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
                                                            - Robert Coveyou

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: