[sane-devel] Re: strange problems LIDE30
Hi, On Wed, Oct 06, 2004 at 05:07:46PM -0400, Brian K. White wrote: The manufacturer says that it does 1200x2400 optically, but xsane only offers a listbox that says a single value from 0 to 2400, no XXXxYYY choices, so I picked 2400 just to go for a worst case scenario but I have no idea what it's actually going to do. A lie, only actualy produce 1200x1200? a distorted image? silently double every pixel in one direction? silently double every pixel in both directions? or maybe the scanner will do the doubling in one direction in firmware and present sane with 2400x2400 data? As it doesn't make sense to crete distorted images SANE backends usually either duplicate pixels or interpolate them. I've seen several Windows drivers that interpolate even if it's not necessary: E.g. harware resolution 100 and 200 dpi, driver uses 100 dpi when asked for 200. Also some scanners are advertized to make 600x1200 dpi but can't do (and don't do) 1200 dpi even vertically. It looks like nobody ever checked what the Windows driver really scans. I don't know what's the case with the LiDEs, however. It's only at about 10 or 15% progress after 20 minutes so I'll send another post when it's done, or when it crashes. At least with the scanners supported by the gt68xx backend, a low scan width is important for higher speed at high resolutions. As you usually use high resolutions for smaller sections of photos or slides that's not that unreasonable. This box has a gig of ram so hopefully it's enough for this worst-case scenario if sane doesn't open a file and work with smaller chunks in ram. This is a dual 1gig p3 too. That might be relevant by making it more likely that there is always a cpu available to service the usb interrups? Or rather, that the one cpu that seems to be the only one that even sees interrupts, is more likely to be able to keep up. One of the problems is that libusb doesn't allow async i/o. So you can't send some buffers to be filled and wait for their completion. Bye, Henning
[sane-devel] No device available
jurek Ela Tryjarscy wrote: Hi , In my box I have Redhat 9. I must connect via SCSI Interface Umax Mirage II scanner. SCSI adapter is Acard AEC-6712TU. Linux System logs contain: Oct 4 19:19:05 localhost kernel:ACARD AEC-671X PCI Ultra/W SCSI-3 Host Adapter: 0IO:1000, IRQ:11. Oct 4 19:19:05 localhost kernel: ID: 7 Host Adapter Oct 4 19:19:05 localhost kernel: scsi0 : ACARD AEC-6710/6712/67160 PCI Ultra/W/LVD SCSI-3 Adapter Driver V2.6+ac I have never used the atp870u driver, but I assume that this driver should print some message about the devices it detected on the bus as other drivers do. In other words: for some reason it could not find the scanner. My qustion is: How to install correctly the scanner and the scsi adapter - I must make any mistake. I do: modprobe sg modprobe atp870u [root@localhost scsi]# lsmod Module Size Used byNot tainted atp870u23856 0 (unused) sg 36524 0 (unused) scsi_mod 107160 2 [atp870u sg] ide-cd 35676 0 (autoclean) cdrom 33728 0 (autoclean) [ide-cd] parport_pc 19076 1 (autoclean) lp 8996 0 (autoclean) parport37056 1 (autoclean) [parport_pc lp] autofs 13268 0 (autoclean) (unused) 8139too18120 1 mii 3976 0 [8139too] keybdev 2976 0 (unused) mousedev5492 1 hid22148 0 (unused) input 5888 0 [keybdev mousedev hid] usb-uhci 26348 0 (unused) usbcore78816 1 [hid usb-uhci] ext3 70784 2 jbd51892 2 [ext3] [root@localhost root]# ls /proc/scsi atp870u scsi [root@localhost scsi]# more scsi Attached devices: none here you should get 3 lines describing the scanner. I think it should be also sg directory in /proc/scsi yes -- but I don't know, if the SG driver creates this directory, if it does not see any devices. [root@localhost root]# sane-find-scanner # No SCSI scanners found. If you expected something different, make sure that that's because sane-find-scanner simply reads /proc/scsi/scsi, and this file is empty. # you have loaded a SCSI driver for your SCSI adapter. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try modprobe sg. Can anyone help me ? I don't have a really good hint. The core problem is that the atp870u driver does not find the scanner, hence any attempt to access it will fail. Unfortunately the kernel sources don't seem to contain useful documentation e.g. about module parameters. A very simple attempt could be to issue the command echo scsi add-single-device 0 0 6 0 /proc/scsi/scsi If the atp870u driver performs a bus reset and does not wait long enough for SCSI devices to finish their reset procedure, it will not find the scanner, when it scans the bus for devices after the reset. Abel
[sane-devel] is coolscan2 maintained?
I am trying to get in touch with the coolscan2 backend author but I got no replies neither to private emails, neither in this list. I even checked that his last commit is dated january 2003, so I am wondering if he is still working at this project. Sorry for not replying, I've had a busy time at work. I'm maintaining coolscan2, but I need help with a few things. Here's the list of the most important tasks still to be done: - get LS50 and LS5000 to work, maybe LS9000 too. - fix frame offset on LS4000 (should be easy, I just haven't had the time yet). - add multiscan for those models that support it. - fix positioning with LS8000. I tried to get the first point done a few times, but it has proved a bit difficult with no direct access to a scanner. If anyone could work out what needs to be done, I'd be happy to incorporate it into the code. Same goes for all other tasks. Since I have an LS4000, I'll probably do points 2 and 3 myself. With respect to all points above except multiscanning, there is no more information that I can find in the Nikon specs that could help. These things have to be solved via reverse engineering (looking at logs). Please do NOT contact me privately. If you have a question, please post it on the list, I subscribe to it, and even if I don't reply, someone else might help you. Andras
[sane-devel] Re: strange problems LIDE30
Hi, let's try and shed some light on the plustek-backend and the LiDE30 scanner: - The scanner is a USB1.1 device, as the used chipset, a LM9833 is only capable to do USB1.1. - The LM9833 is able to scan @ 8bit per color-channel or @ 16bit where did you get the full-color from? You either scan with the color option, then it's 8bit per channel or you scan with the color 42/48 option, then it's 16bit. - The LiDE30 is able to scan @1200dpi in X direction, because it's the native resolution of the sensor, and the motor is able to do 2400dpi steps. Therefore X direction information is doubled. - The backend does some calibration @ the start of each scan, this might take a while. This time has also been increased from 1.0.13 up to 1.0.14 This is necessary to avoid stripes. To reduce the time, it's now possible to let the backend save the information of the coarse calibration (option cacheCalData in the config file, or --calibration-cache=yes for scanimage). This is working for the latest CVs snapshots. Please note, all backend before 1.0.14 are not recommendend for use with the LiDE devices, as the calibration does not work correctly! Also using kernel 2.6.x (x 8) might cause problems with the USB. Also note, that full-size scanning using the 2400dpi might not work. At least I've never tested, because I've not that much memory in my boxes. 2400dpi also create that much data, that a USB1.1 device really needs some time to send the data to the box. Here the bandwidth is the limiting factor. We might can tweak the motor settings for the 2400dpi to avoid backtracking. Before continuing, I suggest to use the latest CVS snapshots, a kernel 2.6.7 and the latests libusb. The next step will be to check if you really need to do scans @2400dpi, at least full-size ones. Ciao, Gerhard
[sane-devel] scanner hp5400
Selon Henning Meier-Geinitz henn...@meier-geinitz.de: Hi, On Sat, Oct 02, 2004 at 04:25:14PM +0200, Fran=E7ois Patte wrote: I am unable to have the scanner hp5400c working under linux. Here the result of: [...] [hp5400] vendor/product 0x03F0-0x1005 opened [hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D 1200 [hp5400] Read: reqtype =3D 0xC0, req =3D 0x04, value =3D C500 [hp5400] Command 12 verified [hp5400] Sorry, unknown scanner version. Attempted match on : [hp5400] * 'SilitekIBlizd C3 ScannerV0.84' [hp5400] * 'SilitekIBlizd C3 ScannerV0.86' [hp5400] * 'SilitekIBlizd C3 ScannerV0.87' [hp5400] Version is '' What can I do else? Rebuild sane-backends like this: CFLAGS=3D-DNO_STRING_VERSION_MATCH ./configure make make install That's untested but I think it disables the version test. This has solved the problem: scanner is now working. Please include this change in the next version of sane-backends. I hope t= hat linux distributors will make the change too: it is not so easy to compile= only one package when several packages depend on it and that all where install= ed by the way of rpm Thank you. -- Fran=E7ois Patte Ecole fran=E7aise d'Extr=EAme-Orient - Pune - Inde Universit=E9 Ren=E9 Descartes - Paris 5 UFR de math=E9matiques et informatique http://www.math-info.univ-paris5.fr/~patte
[sane-devel] scanner hp5400
Hi, On Thu, Oct 07, 2004 at 01:11:42PM +0200, François Patte wrote: This has solved the problem: scanner is now working. Please include this change in the next version of sane-backends. I hope that linux distributors will make the change too: it is not so easy to compile only one package when several packages depend on it and that all where installed by the way of rpm The version check has already been disabled in CVS so the change will be in sane-backends 1.0.14. Bye, Henning
[sane-devel] scanner hp5400
Hi, On Thu, Oct 07, 2004 at 01:33:36PM +0200, Henning Meier-Geinitz wrote: The version check has already been disabled in CVS so the change will be in sane-backends 1.0.14. 1.0.15 obviously. Bye, Henning
[sane-devel] is coolscan2 maintained?
Il gio, 2004-10-07 alle 00:41, Major A ha scritto: [...] I tried to get the first point done a few times, but it has proved a bit difficult with no direct access to a scanner. If anyone could work out what needs to be done, I'd be happy to incorporate it into the code. Same goes for all other tasks. Since I have an LS4000, I'll probably do points 2 and 3 myself. I may give you ssh access to a linux machine connected to an LS-50. I may do it only for one week, just send me an ssh public key, a disk quota requirement, a username, a start date and specify if you need a color slide or a color/bW film loaded. If I might help in any other way, just tell me. Bye, Giuseppe
[sane-devel] Re: strange problems LIDE30
Gerhard Jaeger wrote: Hi, let's try and shed some light on the plustek-backend and the LiDE30 scanner: - The scanner is a USB1.1 device, as the used chipset, a LM9833 is only capable to do USB1.1. - The LM9833 is able to scan @ 8bit per color-channel or @ 16bit where did you get the full-color from? You either scan with the color option, then it's 8bit per channel or you scan with the color 42/48 option, then it's 16bit. - The LiDE30 is able to scan @1200dpi in X direction, because it's the native resolution of the sensor, and the motor is able to do 2400dpi steps. Therefore X direction information is doubled. - The backend does some calibration @ the start of each scan, this might take a while. This time has also been increased from 1.0.13 up to 1.0.14 This is necessary to avoid stripes. To reduce the time, it's now possible to let the backend save the information of the coarse calibration (option cacheCalData in the config file, or --calibration-cache=yes for scanimage). This is working for the latest CVs snapshots. Please note, all backend before 1.0.14 are not recommendend for use with the LiDE devices, as the calibration does not work correctly! Also using kernel 2.6.x (x 8) might cause problems with the USB. Also note, that full-size scanning using the 2400dpi might not work. At least I've never tested, because I've not that much memory in my boxes. 2400dpi also create that much data, that a USB1.1 device really needs some time to send the data to the box. Here the bandwidth is the limiting factor. We might can tweak the motor settings for the 2400dpi to avoid backtracking. Before continuing, I suggest to use the latest CVS snapshots, a kernel 2.6.7 and the latests libusb. The next step will be to check if you really need to do scans @2400dpi, at least full-size ones. Ciao, Gerhard Very informative Thanks much No, I at least have no real use for scanning full sheets in color at 2400dpi. I only did it for the purpose of testing the system, it's the worst case combination of all offered options. I never had a problem with normal jobs. I've done a few partial pages at 600dpi color, many full pages at 100-600 gray bw Never had a problem. Even though I'm just under your recommendation on several fronts. These are all what's currently available from suse pre-built and Yast-installable: bwlin1:~ # uname -a Linux bwlin1 2.6.5-7.108-smp #1 SMP Wed Aug 25 13:34:40 UTC 2004 i686 i686 i386 GNU/Linux bwlin1:~ # scanimage --version scanimage (sane-backends) 1.0.13; backend version 1.0.13 bwlin1:~ # ls /usr/lib/*usb* /usr/lib/libusb-0.1.so.4 /usr/lib/libusb.a /usr/lib/libusb.so /usr/lib/libusb-0.1.so.4.4.0 /usr/lib/libusb.la bwlin1:~ # Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/ +[+++[-]-]+..+.+++.-.[+---]++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
[sane-devel] Compiling problems
Hello everyone. Here's my problem. When I try to compile the latest sane backends with t= he Genesys files, it returns an error about not being able to find genesy= s.o in the lib folder. Now I read the README file, but it still won't = compile properly. Does anyone have a suggestion? Thank you, -- Jason A. ICQ# 148434286 --=20 ___ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm
[sane-devel] No device available
Are you sure that the SCSI ID of the scanner is different from any other ID on the bus? Is the bus properly terminated? Is the SCSI cable of permissible length? If the SCSI controller cannot initialize its bus, it might declare itself as offline at boot time. Regards, Ulrich Deiters
[sane-devel] USB scanners DO work on Solaris 10 x86
Hi, On Thu, Oct 07, 2004 at 08:26:50PM +0200, Tomasz Orli?ski wrote: I would like to inform you, that I have compiled SANE on Sun Solaris 10 x86 with built-in USB scanner support. Very nice. I'd like to place your mail in README.solaris in SANE CVS so it can be easily find. What's your opinion on this? I guess you used sane-backends 1.0.14? I'll update our supported platforms list accordingly. Thanks for your report. It looks like a real adventure to use Solaris/x86 :-) Bye, Henning -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] scanning via network
--nextPart1547262.qRYlrS05dl Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I can scan from my server, where the scanner is connected, but i can't scan= =20 from my network-pc. The only change on the system is a backend-update on th= e=20 server by using the last sorces of karsten festag. It seems to be an error in the updatet files, I've just reinstalled the las= t=20 version before, and suddenly there is no error ... Thanks Am Donnerstag, 7. Oktober 2004 19:59 schrieb Henning Meier-Geinitz: Hi, On Thu, Oct 07, 2004 at 07:46:20PM +0200, Christoph Knauer wrote: But now there is a network-problem since I'm using this new backend-package: I can't scan on my network anymore. To compile only the microtek2-code was changed, all other stuff was used before, too. If that's true, it's not a network problem. When I've a look into my xinetd.log, there are these entries: 04/10/5@17:49:02: START: sane from=3D192.168.10.1 04/10/5@23:39:51: EXIT: sane status=3D0 duration=3D21049(sec) --^ before using the new microtek2 04/10/6@10:15:59: START: sane from=3D192.168.10.1 04/10/6@10:15:59: EXIT: sane status=3D127 duration=3D0(sec) --^ after using the new microtek2 I've looked for all my conf-files, and they seems to be unchanged. Any Ideas? First describe what you do and what your problem actually is. Is the network scanner not detected or doesn't it scan? Log messages from saned? Bye, Henning =2D-=20 GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261 =2D alles rund um 11 Internet (ISDN, DSL, und vieles mehr) unter http://www.profiseller.de/shop/christoph-knauer --nextPart1547262.qRYlrS05dl Content-Type: application/pgp-signature -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBBZZmHgy/nEXRCgmERAnPhAJ0V4GrMKFR1RyakkTHtWzIBme+2rgCeJt5n jTzEb4W4mIU3kaX8tBIjheo= =i8Sr -END PGP SIGNATURE- --nextPart1547262.qRYlrS05dl--
[sane-devel] scanning via network
Hi, On Thu, Oct 07, 2004 at 09:31:15PM +0200, Christoph Knauer wrote: I can scan from my server, where the scanner is connected, but i can't scan from my network-pc. The only change on the system is a backend-update on the server by using the last sorces of karsten festag. It seems to be an error in the updatet files, I've just reinstalled the last version before, and suddenly there is no error ... Ok. So I'll ask again: First describe what you do and what your problem actually is. Is the network scanner not detected or doesn't it scan? If it doesn't scan, which error message do you get and when? Bye, Henning
