The never ending hpusbscsi storry

The never ending hpusbscsi storry

[Rene Rebe]

Hi,

Matthias Kindtner wrote:

> scanimage -L
> scanimage: symbol lookup error: /usr/lib/sane/libsane-avision.so.1: undefined 
> symbol: sanei_usb_set_timeout

With the latest backed you need to update include/sane/sanei_usb.h and 
sanei/sanei_usb.c from my SVN repository (will go into SANE CVS in the 
next day).

> device `avision:/dev/sg0' is a Minolta Dimage Scan Dual II film scanner

Don't ever use hpusbscsi. I though I already told all vedors it is that 
broken that they should never ever ship it. It is the first thing that 
will be removed in Linux 2.7.

If it would be me it would be removed from _all kernels right now_ ...

> Mar  4 23:40:51 runningdug scsi: Device offlined - not ready after error 
> recovery: host 1 channel 0 id 0 lun 0
> Mar  4 23:40:51 runningdug scsi1 (0:0): rejecting I/O to offline device
> Mar  4 23:40:51 runningdug scsi1 (0:0): rejecting I/O to offline device
> Mar  4 23:40:51 runningdug scsi1 (0:0): rejecting I/O to offline device
> 
> A simple plug-out plug-in of the usb solve the problem and I can start once
> again

... hpusbscsi as it lifes ...

> I hope there are all messages you need in the mail, otherwise I send it to.
> 
> You have any Idea for me??

find /lib/modules -name hpusbscsi.*o | xargs rm -fv

(or so - assuming no spaces in filenames ...)

and build the backend with the updated sanei_usb* files. Or 
alternatively use a avision backed that is two weeks old (man svn) which 
does not need the updated sanei functionality.

Yours,

-- 
René Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
             http://www.exactcode.de/ | http://www.t2-project.org/
             +49 (0)30  255 897 45

Re: The never ending hpusbscsi storry

[Oliver Neukum]

Am Samstag, 5. März 2005 00:28 schrieb Rene Rebe:
> Don't ever use hpusbscsi. I though I already told all vedors it is that 
> broken that they should never ever ship it. It is the first thing that 
> will be removed in Linux 2.7.
> 
> If it would be me it would be removed from _all kernels right now_ ...

It shall be. A patch to do that is in the queue. The other users have
gone away.

	Regards
		Oliver