[sane-devel] devfs and scanner detection

[Mr E_T]

When devfs is used and modules are autoloaded the device is not listed under
/dev/usb

It is not listed until the module is loaded.

The module is loaded when a program attempts to open say /dev/usb/scanner0

BUT sane only opens the device IF it exists in a directory listing.

In this case the device wont exist because the kernel does not know that an
application is looking for it.

Currently I have had to modprobe the scanner module b4 I run a sane aware
program.

The problem as I said is that the usb module does a directory listing b4 opening
the device file Whereas it should just try opening it.

This should cause the kernel to attempt to create the device if it does not
exist.

Thanx

-- 
regs MR E_T
___
\  \
  \   OOHH I hate TYPOS  \
\  \
  ~~~

[sane-devel] devfs and scanner detection

[Henning Meier-Geinitz]

Hi,

On Sun, Aug 17, 2003 at 10:37:51PM +0800, Mr E_T wrote:
> The problem as I said is that the usb module does a directory listing b4 
> opening
> the device file Whereas it should just try opening it.

It shouldn't. If the device file is not there, SANE thinks there is no
device. SANE can't open all possible device files because the kernel
takes too long. We did this in earlier versions but wainting more than
30 seconds for a "scanimage -L" when devfs is used is just not
acceptable.

Shouldn't hotplug care for autoloading the scanner module when the
scanner is plugged in? If that doesn't work for some reason, you could
also add a link /dev/usb/scanner --> /dev/usb/scanner0.

> This should cause the kernel to attempt to create the device if it does not
> exist.

The only way to find out quickly if a device (possibly) exists with
devfs is to look if the device file is there.

Bye,
  Henning

[sane-devel] OS X Firewire support

[Karl Heinz Kremer]

This really is cool stuff... It works even with "real" IEEE1394 EPSON  
scanners - that
is if you have the current CVS version of the backend. I tried it with  
an EPSON  GT-3
scanner connected via IEEE-1394. The scanner gets correctly reported by
scanimage -L, and I did a number of successful scans.

Great job,

Karl Heinz


On Sunday, August 17, 2003, at 08:47 AM, Guy Brooker wrote:

> On 12/8/03 5:06 pm, "Martijn van Oosterhout"  wrote:
>
>> On Tue, Aug 12, 2003 at 03:46:45PM +0200, Guy Brooker wrote:
>>>
>>> Hi,
>>>
>>> I've almost completed testing of a patch to sane_scsi.c which  
>>> supports the
>>> IOKit SCSI Architecture Model API.
>>
>> Very cool stuff!
>>
>>
>> 1. Use diff to work out the differences between the base version and  
>> your
>> changes
>> 2. Or just post the code and how to make it work.
>>
>
> OK, a zip archive for the patch to 1.0.12 is available at
>
> http://homepage.mac.com/guy_brooker/.cv/guy_brooker/Public/Sane/sane- 
> backend
> s-1.0.12-osx.zip-link.zip
>
> It only modifies one file, sane-backends-1.0.12/sanei/sanei_scsi.c
>
> It still supports the previous implementation which uses the  
> deprecated SCSI
> Family IOKit API, so all being well it should not break anything that  
> has
> previously worked.
>
> I have added some #ifdefs which may allow it to be compiled when  
> either the
> old or new i/f are not available, but this has not been tested. To use  
> just
> the old API, compile with OSX_ONLY_10_1_API defined, and to use just  
> the new
> API, compile with OSX_ONLY_10_2_API defined. By default neither are  
> defined,
> and both APIs are used.
>
> The modifications should allow Firewire scanners, and SCSI scanners  
> plugged
> into a firewire-SCSI bridge (such as Orange Micro's) to work with sane  
> under
> Jaguar and future OS's.
>
> I have only been able to test it with my EPSON GT-7000 on my iMac.  
> Please
> could other interested parties give it a go and let me know if you  
> have any
> success ?
>
> scanimage -L works fine :
>
> % scanimage -L device
> `epson:iokitscsi@<0450201222af34a59175>' is a Epson GT-7000 flatbed
> scanner
>
> As does xsane (which I installed using fink)
>
> The only problem I have is that both these tools need dll.conf and
> epson.conf in the current working directory, they don't find the  
> version in
> the standard location for some reason. I'll look into that later, but I
> don't think it has anything to do with my changes.
>
> As you can see from above, the device name is made up, and I use the  
> text
> 'iokitscsi@<' followed by the SCSIUserClient GUID from the IO  
> Registry. That
> is the unique ID for the client, and allows me to refind the device  
> very
> quickly. The only problem is that the number will change after reboot,  
> or if
> the device is unplugged, and replugged into the firewire port.
>
> sane-find-scanner does not work, as it hard codes device names for each
> platform. Just use scanimage -L
>
> I am now thinking about implementing a TWAIN Data Source, but it seems  
> a
> huge job The windows ones don't seem to be much of a starting  
> point, but
> Apple provides some basic sample code that might get me started. If  
> anyone
> else has started on that, could you drop me a line ?
>
> Cheers,
> Guy
>
> ___
> Sane-devel mailing list
> sane-de...@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel

[sane-devel] HP PSC 1210

[Till Kamppeter]

Julien BLACHE wrote:
> Sebastian 'Frank©' Wieseler  wrote:
> 
> 
>>- OS: Debian GNU/Linux [Woody 3.0r1]
>>- SANE: sane_1.0.11-2_i386.deb
>>- libUSB: libusb-0.1-4_0.1.7-2_i386.deb
>>- Kernel: 2.4.20
>>- HPOJ >0.9
>>- hp-backend: 1.01
>>
>>*So* now my configs file looks like:
>># cat nano /usr/local/etc/sane.d/hp.conf

You scanner does not use the "hp" backend. So every change in 
/usr/local/etc/sane.d/hp.conf (or /etc/sane.d/hp.conf) has no influence. 
Your device uses the "hpoj" backend provided by the HPOJ package. So 
take care that /usr/local/etc/sane.d/dll.conf (or /etc/sane.d/dll.conf) 
has a line only containing "hpoj" without "#" in the beginning.

Take also care that you have the current CVS snapshot of HPOJ as the 
released HPOJ 0.9 still does not support your device correctly. The CVS 
version of HPOJ must be built with libusb. That means you have to 
install either libusb from source or you have to install the 
libusb-devel (or libusb-dev) package of your distro. See

http://hpoj.sourceforge.net/todo.shtml

section "Known bugs in 0.90, fixed or documented as appropriate and 
checked into CVS", first paragraph.

Note that when you use HPOJ that you have also to direct the printing to 
HPOJ. See the documentation of HPOJ.

Till

[sane-devel] HP PSC 1210

[Peter Kirchgessner]

Hello Sebastien,

the scanner is only supported by the CVS-version of hpoj-backend, which 
you already have downloaded. It is not supported by the hp-backend. So 
the entries in hp.conf are not necessary. You should call scanimage with 
something like

scanimage -d hpoj:mlc:usb:PSC:1200

I am not quite sure if this is correct, but this is what the 
documentation says that comes with the hpoj-backend. See subdirectory 
doc of the source code for more details.

Sincerely

Peter

Sebastian 'Frank©' Wieseler schrieb:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> 
> Hallo list,
> I have a big problem with my new device hp psc 1210 - this is a
> 3-in-1-device (printer, scanner and can make copies ;))
> 
> My problem is the scanner - printer works fine.
> I've read the manual and see that I must use HPOJ (in the CVS version).
> I have done so, but it doesn't work.
> 
> I don't know what to do now, please help me.
> My configuration:
> 
> - OS: Debian GNU/Linux [Woody 3.0r1]
> - SANE: sane_1.0.11-2_i386.deb
> - libUSB: libusb-0.1-4_0.1.7-2_i386.deb
> - Kernel: 2.4.20
> - HPOJ >0.9
> - hp-backend: 1.01
> 
> *So* now my configs file looks like:
> # cat nano /usr/local/etc/sane.d/hp.conf
> usb HP
> option dumb-read
> /dev/usb/scanner
> option connect-device
> /dev/usbscanner
> option connect-device
> 
> # cat /usr/local/etc/sane.d/dll.conf
> hp
> hpoj
> ...
> 
> # sane-find-scanner
> found USB scanner (UNKNOWN vendor and product) at device dev/usb/scanner
> found USB scanner (UNKNOWN vendor and product) at device /dev/usbscanner
> found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x2f11 [psc
> 1200 series]) at libusb:001:002
> 
> # scanimage -d hp:/dev/usbscanner
> scanimage: open of device hp:/dev/usbscanner failed: Error during device 
> I/O
> 
> So what should I do? Any idea?
> 
> Greetings
> Sebastian Wieseler
> 
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.2 (GNU/Linux)
> 
> iD8DBQE/P1s+4z2wBHhPV9sRArJmAJoDTB3jk0CASt9Op6mjOlGvP8c4FACeJfnM
> T2Qn1Xc/JKTUPM/QM9NcSjY=
> =iCqZ
> -END PGP SIGNATURE-
> 
> 
> 
> 
> ___
> Sane-devel mailing list
> sane-de...@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel
> 


-- 
Peter Kirchgessner
http://www.kirchgessner.net
mailto:pe...@kirchgessner.net

[sane-devel] Help scanner (II)

[Juan Carlos]

Hello!
I try typing "man sane-snapscan" and I haven't this file. I read, as 
well the file snapscan.conf several times but I don't found the place ot 
the firmware file.
I try to write -as root- in that file but duplicate de file with and 
ASCII code at the end of one file (Alt-126 in Win but a mystery in Linux 
for me).
I try, again, with all the commands I said you but no sense the usb 
scanner is detectec but not work
Please tell me one more time you answer more easily for a newest linux 
user, with the place of the files to write if it's possibleThanks a 
lot.
I hope I don't need to be an experte to run linux normally.I hope 
your answer too.

Bye,
Juan Carlos

[sane-devel] HP PSC 1210

[Julien BLACHE]

Sebastian 'Frank©' Wieseler  wrote:

> - OS: Debian GNU/Linux [Woody 3.0r1]
> - SANE: sane_1.0.11-2_i386.deb
> - libUSB: libusb-0.1-4_0.1.7-2_i386.deb
> - Kernel: 2.4.20
> - HPOJ >0.9
> - hp-backend: 1.01
>
> *So* now my configs file looks like:
> # cat nano /usr/local/etc/sane.d/hp.conf

[...]

Have you installed the libsane package, or did you build sane-backends
by hand ?

If you installed the package, the configuration files are located
under /etc/sane.d/...

JB.

-- 
Julien BLACHE    
 

[sane-devel] HP PSC 1210

[Sebastian 'Frank©' Wieseler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hallo list,
I have a big problem with my new device hp psc 1210 - this is a
3-in-1-device (printer, scanner and can make copies ;))

My problem is the scanner - printer works fine.
I've read the manual and see that I must use HPOJ (in the CVS version).
I have done so, but it doesn't work.

I don't know what to do now, please help me.
My configuration:

- OS: Debian GNU/Linux [Woody 3.0r1]
- SANE: sane_1.0.11-2_i386.deb
- libUSB: libusb-0.1-4_0.1.7-2_i386.deb
- Kernel: 2.4.20
- HPOJ >0.9
- hp-backend: 1.01

*So* now my configs file looks like:
# cat nano /usr/local/etc/sane.d/hp.conf
usb HP
option dumb-read
/dev/usb/scanner
 option connect-device
/dev/usbscanner
 option connect-device

# cat /usr/local/etc/sane.d/dll.conf
hp
hpoj
...

# sane-find-scanner
found USB scanner (UNKNOWN vendor and product) at device dev/usb/scanner
found USB scanner (UNKNOWN vendor and product) at device /dev/usbscanner
found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x2f11 [psc
1200 series]) at libusb:001:002

# scanimage -d hp:/dev/usbscanner
scanimage: open of device hp:/dev/usbscanner failed: Error during device I/O

So what should I do? Any idea?

Greetings
Sebastian Wieseler


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/P1s+4z2wBHhPV9sRArJmAJoDTB3jk0CASt9Op6mjOlGvP8c4FACeJfnM
T2Qn1Xc/JKTUPM/QM9NcSjY=
=iCqZ
-END PGP SIGNATURE-

[sane-devel] OS X Firewire support

[Guy Brooker]

On 12/8/03 5:06 pm, "Martijn van Oosterhout"  wrote:

> On Tue, Aug 12, 2003 at 03:46:45PM +0200, Guy Brooker wrote:
>> 
>> Hi,
>> 
>> I've almost completed testing of a patch to sane_scsi.c which supports the
>> IOKit SCSI Architecture Model API.
> 
> Very cool stuff!
> 
> 
> 1. Use diff to work out the differences between the base version and your
> changes
> 2. Or just post the code and how to make it work.
> 

OK, a zip archive for the patch to 1.0.12 is available at

http://homepage.mac.com/guy_brooker/.cv/guy_brooker/Public/Sane/sane-backend
s-1.0.12-osx.zip-link.zip

It only modifies one file, sane-backends-1.0.12/sanei/sanei_scsi.c

It still supports the previous implementation which uses the deprecated SCSI
Family IOKit API, so all being well it should not break anything that has
previously worked.

I have added some #ifdefs which may allow it to be compiled when either the
old or new i/f are not available, but this has not been tested. To use just
the old API, compile with OSX_ONLY_10_1_API defined, and to use just the new
API, compile with OSX_ONLY_10_2_API defined. By default neither are defined,
and both APIs are used.

The modifications should allow Firewire scanners, and SCSI scanners plugged
into a firewire-SCSI bridge (such as Orange Micro's) to work with sane under
Jaguar and future OS's.

I have only been able to test it with my EPSON GT-7000 on my iMac. Please
could other interested parties give it a go and let me know if you have any
success ?

scanimage -L works fine :

% scanimage -L device
`epson:iokitscsi@<0450201222af34a59175>' is a Epson GT-7000 flatbed
scanner

As does xsane (which I installed using fink)

The only problem I have is that both these tools need dll.conf and
epson.conf in the current working directory, they don't find the version in
the standard location for some reason. I'll look into that later, but I
don't think it has anything to do with my changes.

As you can see from above, the device name is made up, and I use the text
'iokitscsi@<' followed by the SCSIUserClient GUID from the IO Registry. That
is the unique ID for the client, and allows me to refind the device very
quickly. The only problem is that the number will change after reboot, or if
the device is unplugged, and replugged into the firewire port.

sane-find-scanner does not work, as it hard codes device names for each
platform. Just use scanimage -L

I am now thinking about implementing a TWAIN Data Source, but it seems a
huge job The windows ones don't seem to be much of a starting point, but
Apple provides some basic sample code that might get me started. If anyone
else has started on that, could you drop me a line ?

Cheers,
Guy

[sane-devel] Umax P2000

[Frederick Noronha (FN)]

Still can't get my Astra Umax P2000 working. It just says no scanner 
device found. Tried multiple OSs (Woody-Debian, Elx, Knoppix, Mandrake) 
and at least three computers. Any help would be much appreciated. FN
-- 
-
Frederick Noronha (FN)| http://www.fredericknoronha.net
Freelance Journalist  | http://www.bytesforall.org
http://goalinks.pitas.com | http://joingoanet.shorturl.com
http://linuxinindia.pitas.com | http://www.livejournal.com/users/goalinks
-
T: 0091.832.2409490 or 2409783 M: 0 9822 122436
-

[sane-devel] Umax P2000

[stef]

On Sun, Aug 17, 2003 at 01:04:06PM +0530, Frederick Noronha (FN) wrote:
> Still can't get my Astra Umax P2000 working. It just says no scanner 
> device found. Tried multiple OSs (Woody-Debian, Elx, Knoppix, Mandrake) 
> and at least three computers. Any help would be much appreciated. FN
> -- 
> -
> Frederick Noronha (FN)| http://www.fredericknoronha.net
> Freelance Journalist  | http://www.bytesforall.org
> http://goalinks.pitas.com | http://joingoanet.shorturl.com
> http://linuxinindia.pitas.com | http://www.livejournal.com/users/goalinks
> -
> T: 0091.832.2409490 or 2409783 M: 0 9822 122436
> -
> ___
> Sane-devel mailing list
> sane-de...@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel

Hello,

we need more informations in order to help you. As a start, you can send
the output of 'scanimage -L', after setting on traces (in a command shell):

export SANE_DEBUG_UMAX_PP=255
scanimage -L

Also, you might find usefull tips at http://umax1220p.sourceforge.net .

Regards,
Stef