On Sun, 30 Jul 2006 22:51:28 +1200 Nick Rout <[EMAIL PROTECTED]> wrote:
> On Sun, 30 Jul 2006 15:40:15 +1200 > Andrew Packer <[EMAIL PROTECTED]> wrote: > > > Since I've upgraded from Ubuntu Breezy (5.10) to Dapper (6.06), I can't > > get my Epson Perfection 2450 Photo scanner to work in Linux. > > > > In Breezy, xsane would work provided I ran it twice (i.e. open - close - > > open again). On the initial run, xsane would find the scanner > > immediately, but it wouldn't operate it. On the second run, xsane would > > take many seconds to find the scanner, but would then operate it > > normally. > > > > Now in Dapper, xsane takes many seconds to find the scanner and still > > won't operate it; trying to scan yields, after some more utter > > inactivity, "Failed to start scanner: Error during device I/O". Closing > > and rerunning xsane produces an identical result. So does running it as > > root via sudo. > > > > xscanimage (which also used to work in Breezy, the rare time I'd try it > > out) fails similarly with the same message. > > > > I've downloaded and installed the Epson-Kowa (Avasys) program iscan. It > > fails with the message "Could not send command to scanner. Check the > > scanner's status." That's both as a normal user and as root. > > > > lsusb yields > > Bus 004 Device 003: ID 04b8:0112 Seiko Epson Corp. Perfection 2450 > > > > scanimage -L yields > > device `epson:libusb:004:003' is a Epson GT-9700 flatbed scanner > > > > sane-find-scanner yields > > found USB scanner (vendor=0x04b8 [EPSON], product=0x0112 [EPSON > > Scanner]) at libusb:004:003 > > > > I've tried commenting out the "scsi Epson" line in > > the /etc/sane.d/epson.conf file, but that makes no difference. > > Likewise, no difference when I add the manufacturer and product no. in > > the line which otherwise reads simply "usb". iscan uses the alternative > > config file /etc/sane.d/epkowa.conf, and I've done the same to that > > file, to no avail. > > > > I've tried kooka but it doesn't even throw up any warning windows - just > > doesn't activate the scanner. > > > > I've tried the scanner on my wife's AMD-64 (also running Dapper), and > > xsane behaves identically (to my knowledge she hasn't got any other > > scanning software). > > > > The scanner does work on my machine in WinXP, although it does crash > > every few pages and has to be powered off and on again to reset. (It's > > shown that misbehaviour for years.) > > > > Google is NOT being my friend for this issue. > > > > Any ideas? > > All of those scanning options except iscan use sane as the base. I would be > using the sane command line tools and looking for errors in their output and > in the system logs. > > scanimage -L > > and > > sane-find-scanner > > come to mind. > apt-get install sane-utils to get those command line tools.
