All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Need help about scanner (2.6.2-mm1)
Date: Thu, 18 Mar 2004 01:00:40 +0000	[thread overview]
Message-ID: <4058F4B8.5050304@blueyonder.co.uk> (raw)

Azog wrote:
 > Thank you so much for the tip! This seems to have solved my problem
 > too.

 > I changed my epson.conf file to just say
 > "usb"
 > instead of
 > "usb /dev/usb/scanner0"

 > and now, finally, it works. I do hope the SANE documentation writers
 > get around to adding that little tidbit of info SOMEWHERE, I was
 > tearing my hair out and rebooting back to 2.4 to use my scanner.

I tried that in 2.6.5-rc1-mm1, restarted sane, but it still fails. 
scanimage -L does not find the scanner, sane-find-scanner finds it, but 
says I have scsi modules loaded, even though I've rmmod them. I'm using 
a recent CVS libusb and sane.
I found an article on linuxtoday.com that pointed me to vuescan where I 
downloaded their initial linux release and the scanner (Epson USB 610) 
works fine using it. It uses the libusb-0.1.so.4.4.1 I have installed, 
so that points back to a problem with sane which I have added to their 
bug list.
Regards
Sid.

-- 
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.


             reply	other threads:[~2004-03-18  1:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18  1:00 Sid Boyce [this message]
     [not found] <200402061948.37410.gene.heskett@verizon.net>
2004-02-07  1:58 ` Need help about scanner (2.6.2-mm1) Steve Kieu
2004-02-07  4:07   ` Gene Heskett
2004-02-09 20:59     ` Azog
  -- strict thread matches above, loose matches on Subject: below --
2004-02-06 23:57 Steve Kieu
2004-02-07  0:00 ` Randy.Dunlap
2004-02-07  0:14 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4058F4B8.5050304@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.