Re: scsi device files not created when called for
On Sat, 11 Feb 2012 14:06:40 +0100, Morten Bo Johansen wrote:
> My scanner suddenly stopped working. It is connected through firewire
> and when I turn it on, the firewire devices are created:
> My Epson scanner is thus recognized. However, the scanner is also being
> attached to a scsi device, but the scsi device files are not being
> created automatically under /dev/ which means that xsane will not see
> it. When I ran:
> ~/ % sudo modprobe sg
> manually, the scsi device files are created as /dev/sg0 etc. and my
> scanner now works again with xsane.
> I could load the "sg" module from /etc/modules, but I do not think it
> should be necessary.
> I wonder if there is something wrong with my setup, since I need to
> manually load the scsi generic driver, or if this is a bug that I should
As it was not necessary to manually load the generic scsi before, it
shouldn't be needed now so could be an error, maybe an "udev" rule wrong
or missing :-?
> In the latter case, which package should I report against?
I'd say "libsane".
> Some info:
> ~/ % uname -a
> Linux gatsby 3.2.0-1-686-pae #1 SMP Sun Feb 5 23:52:49 UTC 2012 i686
> package "udev" is version 175-3
You're on sid, right?