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

scsi device files not created when called for


My scanner suddenly stopped working. It is connected through firewire and
when I turn it on, the firewire devices are created:

   ~/ % dmesg | tail -6
   [ 8377.031246] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
   [ 8377.529022] scsi7 : SBP-2 IEEE-1394
   [ 8377.529102] firewire_sbp2: fw1.0: 127s mgt_ORB_timeout limited to 40s
   [ 8377.529108] firewire_core: created device fw1: GUID 00004800004ee815, S400
   [ 8377.728590] firewire_sbp2: fw1.0: logged in to LUN 0000 (0 retries)
   [ 8377.729957] scsi 7:0:0:0: Processor         EPSON    GT-X900          1.06 PQ: 0 ANSI: 4

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
report? In the latter case, which package should I report against?

Some info:

   ~/ % uname -a        
   Linux gatsby 3.2.0-1-686-pae #1 SMP Sun Feb 5 23:52:49 UTC 2012 i686 GNU/Linux

   package "udev" is version 175-3



Reply to: