Bug#367190: On Amd64, sane-find-scanner works, scanimage -L does not.

2014-10-26 Thread Jörg Frings-Fürst
Hello,

No answer since 2006.

So I close this bug. 


Thank you for your collaboration in Debian.


CU
Jörg
-- 
pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8  EBCB 422B 44B0 BE58 1B6E
pgp Key: BE581B6E
CAcert Key S/N: 0E:D4:56

Jörg Frings-Fürst
D-54526 Niederkail

Threema-ID: SYR8SJXB

IRC: j_...@freenode.net, j_...@oftc.net

signature.asc
Description: This is a digitally signed message part.


Bug#367190: On Amd64, sane-find-scanner works, scanimage -L does not.

2006-05-15 Thread Julien BLACHE
Peter Chubb [EMAIL PROTECTED] wrote:

Hi,

 FWIW, this looks to be the same (or a similar problem) as
 http://bugzilla.kernel.org/show_bug.cgi?id=5835 

 If I modprobe -r ehci_hcd then  scanimage -L detects the scanner.

Here you go, then... I hope this bug will be fixed one day.

JB.

-- 
 Julien BLACHE [EMAIL PROTECTED]  |  Debian, because code matters more 
 Debian  GNU/Linux Developer|   http://www.debian.org
 Public key available on http://www.jblache.org - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#367190: On Amd64, sane-find-scanner works, scanimage -L does not.

2006-05-14 Thread Peter Chubb
Package: sane
Version: 1.0.14-1
Severity: normal


I'm using an Espon perfection 4990 scanner attached to a USB 2.0 port
The scanner works perfectly when attached to a real x86 box, but does 
not on this box, neither in an ia32 chroot, nor native.
I've tried both epson and epkowa backends.

I'm not sure that the problem may not actually be either in the kernel 
or in libusb.

$ lsusb
Bus 001 Device 014: ID 0924:fff2 Xerox 
Bus 001 Device 001: ID :  
Bus 002 Device 042: ID 04b8:012a Seiko Epson Corp. 
Bus 002 Device 001: ID :  
$ SANE_DEBUG_EPKOWA=255 scanimage -L
[sanei_debug] Setting debug level of epkowa to 255.
[epkowa] sane_init: sane-backends 1.0.17
[epkowa] sane_init, # epkowa.conf -- sample configuration for the EPKOWA SANE 
backend
[epkowa] sane_init, # Copyright (C) 2004  Olaf Meeuwissen
[epkowa] sane_init, #
[epkowa] sane_init, # See sane-epkowa(5), sane-scsi(5) and sane-usb(5) for 
details.
[epkowa] sane_init, 
[epkowa] sane_init, # SCSI scanners can be configured simply by listing the 
path to the
[epkowa] sane_init, # device.  For example, if your system claims to have a 
/dev/scanner
[epkowa] sane_init, # SCSI device, all you have to do is uncomment the 
following line:
[epkowa] sane_init, #
[epkowa] sane_init, #/dev/scanner
[epkowa] sane_init, #
[epkowa] sane_init, # In the interest of maintainability, most installations 
would have
[epkowa] sane_init, # /dev/scanner sym-linked to the real SCSI scanner device 
node.
[epkowa] sane_init, #
[epkowa] sane_init, # An alternative way that works for many operating systems 
and is a
[epkowa] sane_init, # little bit more generic, is to have the backend probe 
for your SCSI
[epkowa] sane_init, # scanner with the following configuration command:
[epkowa] sane_init, #
[epkowa] sane_init, scsi EPSON
[epkowa] sane_init, 
[epkowa] sane_init, # On systems with libusb, the following line is sufficient 
to get the
[epkowa] sane_init, # backend to recognise your USB scanners.  It presumes, 
however, that
[epkowa] sane_init, # the scanner---more precisely, it's USB product ID---is 
known to the
[epkowa] sane_init, # backend.
[epkowa] sane_init, # For all USB scanners that are officially supported by 
this backend,
[epkowa] sane_init, # this presumption is true.  A list of such scanners can 
be found in
[epkowa] sane_init, # sane-epkowa(5).
[epkowa] sane_init, #
[epkowa] sane_init, usb
[epkowa] attach_one_usb()
[epkowa] SANE EPKOWA Backend 1.16.0-3 - 2005-06-29
[epkowa] attach(, 3)
[epkowa] attach: opening 
[epkowa] attach_one_usb(libusb:002:042)
[epkowa] SANE EPKOWA Backend 1.16.0-3 - 2005-06-29
[epkowa] attach(libusb:002:042, 3)
[epkowa] attach: opening libusb:002:042
[epkowa] Found valid EPSON scanner: 0x4b8/0x12a (vendorID/productID)
[epkowa] reset()
[epkowa] send buf, size = 2
[epkowa] buf[0] 1b .
[epkowa] buf[1] 40 @
[epkowa] receive buf, expected = 1, got = 1
[epkowa] buf[0] 06 .
[epkowa] get_identity_information()
[epkowa] send buf, size = 2
[epkowa] buf[0] 1b .
[epkowa] buf[1] 49 I
[epkowa] receive buf, expected = 4, got = 0
[epkowa] ident failed
[epkowa] close_scanner(fd = 0)
[epkowa] sane_init, 
[epkowa] sane_init, # For any USB scanner not known to the backend (yet), you 
may, at your
[epkowa] sane_init, # own peril(!!), force the backend to recognise and use it 
via libusb.
[epkowa] sane_init, # You can do so by the following configuration command:
[epkowa] sane_init, #
[epkowa] sane_init, #   usb USB vendor ID USB product ID
[epkowa] sane_init, #
[epkowa] sane_init, # SEIKO EPSON's USB vendor ID is '0x04b8' (without 
quotes).  In order
[epkowa] sane_init, # to find the USB product ID, use lsusb(1) or, on Linux 
systems, peek
[epkowa] sane_init, # at the information in /proc/bus/usb/devices.
[epkowa] sane_init, # A sample configuration for the Perfection 1650 
(GT-8200), which has
[epkowa] sane_init, # a product ID of 0x0110, would look as follows:
[epkowa] sane_init, #
[epkowa] sane_init, #usb 0x04b8 0x012a
[epkowa] sane_init, 
[epkowa] sane_init, usb 0x04b8 0x012a
[epkowa] attach_one_usb(libusb:002:042)
[epkowa] SANE EPKOWA Backend 1.16.0-3 - 2005-06-29
[epkowa] attach(libusb:002:042, 3)
[epkowa] attach: opening libusb:002:042
[epkowa] Found valid EPSON scanner: 0x4b8/0x12a (vendorID/productID)
[epkowa] reset()
[epkowa] send buf, size = 2
[epkowa] buf[0] 1b .
[epkowa] buf[1] 40 @
[epkowa] receive buf, expected = 1, got = 1
[epkowa] buf[0] 06 .
[epkowa] get_identity_information()
[epkowa] send buf, size = 2
[epkowa] buf[0] 1b .
[epkowa] buf[1] 49 I
[epkowa] receive buf, expected = 4, got = 0
[epkowa] ident failed
[epkowa] close_scanner(fd = 0)
[epkowa] sane_init, 
[epkowa] sane_init, # When not accessing your USB scanner via libusb, you may 
need to use
[epkowa] sane_init, # one of the configuration commands below or commands that 
are almost
[epkowa] sane_init, # the same.  These commands typically access the scanner 
via a kernel
[epkowa] sane_init, # scanner module.
[epkowa] sane_init, #
[epkowa] sane_init, #usb 

Bug#367190: On Amd64, sane-find-scanner works, scanimage -L does not.

2006-05-14 Thread Julien BLACHE
reopen 367190
reassign 367190 libsane
thanks

Peter Chubb [EMAIL PROTECTED] wrote:

 Julien epkowa needs proprietary, binary only modules to work with
 Julien your scanner, and they are only available for i386.

 But the same thing happens with the epson backend.

Hmm, I don't see the 4990 listed as supported, even in the CVS. Though
if it works on i386 there's no reason it wouldn't work on amd64 too.

I'll have a look at the build logs, just in case.

Do you have the same kernel version running on both machines ? Can you
try to boot a i386 kernel (live cd ?) on the amd64 and try to scan ?

Thanks,

JB.

-- 
 Julien BLACHE [EMAIL PROTECTED]  |  Debian, because code matters more 
 Debian  GNU/Linux Developer|   http://www.debian.org
 Public key available on http://www.jblache.org - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]