From: Azog <slashmail@arnor.net>
To: gene.heskett@verizon.net
Cc: Steve Kieu <haiquy@yahoo.com>, kernel <linux-kernel@vger.kernel.org>
Subject: Re: Need help about scanner (2.6.2-mm1)
Date: Mon, 09 Feb 2004 12:59:21 -0800 [thread overview]
Message-ID: <1076360361.6331.45.camel@moria.arnor.net> (raw)
In-Reply-To: <200402062307.37040.gene.heskett@verizon.net>
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.
Also, now that usb-scanner.ko is gone, a paragraph of help in the
http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt
file would be a great thing as well.
On Fri, 2004-02-06 at 20:07, Gene Heskett wrote:
> On Friday 06 February 2004 20:58, Steve Kieu wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >
> >Hi,
> >
> >Your help saved me lot of headache :-)
>
> Thanks for the flowers.
>
> > --- Gene Heskett <gene.heskett@verizon.net> wrote: >
> >On Friday 06 February 2004 18:57, Steve Kieu
> >
> >wrote:
> >> >-----BEGIN PGP SIGNED MESSAGE-----
> >>
> >> Take any device paths out of
> >> the /usr/local/etc/saned/nameofyourscanner.dll
> >
> >just .conf ; not dll :-)
>
> Can I plead alzheimers or something? Working with ancient grey matter
> here. Its working on the 70th trip around our star. :-)
>
> >> leaving only a single [usb] as a specifier unless
> >
> >Yes it saved me. It work now. Why no other sane
> >documentation said like yours? I think people at sane
> >project should take your point to add to their
> >documentation.
>
> I don't ATM recall exactly where I first heard or read about this.
>
> Maybe in the libusb docs? No, not a thing, even clear back up to the
> root dir of the libusb archive. Maybe I got it from the sane list?
>
> In any event, thats too damned hard to find and if the libusb author
> is copying the mail here, that little detail really should be added
> to the README and/or INSTALL.libusb raw text files, or to a FAQ on
> the libusb website, the quicker of the two alternatives if this
> version of the library is stable (and it seems so to me).
>
> The authors doc/html files are quite complete, I just read them all,
> but they attack *only* the api the programmer would use, and the
> actual non-programming user who just wants to use his scanner with
> this new-fangled system gets hung out to dry. This question gets
> asked, and answered the same way, many times on the sane list too.
>
> It may have been added to the sane-backend docs in a recent version,
> I'm at least one version out of date here, not being inclined to "fix
> something thats not broken" at my home site. :-)
>
> [...]
next prev parent reply other threads:[~2004-02-09 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2004-03-18 1:00 Sid Boyce
-- 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=1076360361.6331.45.camel@moria.arnor.net \
--to=slashmail@arnor.net \
--cc=gene.heskett@verizon.net \
--cc=haiquy@yahoo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox