Re: scsi device files not created when called for

Camaleón wrote: > On Sat, 11 Feb 2012 14:06:40 +0100, Morten Bo Johansen wrote: >> In the latter case, which package should I report against? > I'd say "libsane". I think I'll go for udev. Once the scanner is attached to to a scsi device file, then the appropriate module should be loaded and th

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 de

scsi device files not created when called for

Hi, 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] fi