[sane-devel] Acard AEC6712S (atp870u.ko) and HP 6100C C2520A (sg.ko) problems
On Fri, Aug 18, 2006 at 11:54:59AM +0200, abel deuring wrote: If possible, try different cables and another SCSI adapter, or connect another SCSI device to the Acard adapter to get a better idea, where the error might come from. I took the scanner, SCSI-2 cable, and acard SCSI host adapter and plugged them into my roomate's windows computer, installed the appropriate drivers, rebooted a few times, suffered through windows' occult complaints but eventually got the device functioning. Next I tried it on his FC4 system (same hardware, different OS) which, upon loading the appropriate kernel modules segfaulted the kernel and froze the machine. Sometimes I am able to get the kernel modules loaded on my machine before the atp870u driver complains. At this point sane-find-scanner detects the scanner found SCSI processor HP C2520A 3644 at /dev/sg1 but `scanimage -L` does nothing. Perhaps it precipitates an error of some kind because after cancelling the command sane-find-scanner again detects nothing and subsequent driver reloadings print out the same set of SCSI errors. I know at lease someone somewhere has gotten this scanner working before because http://www.sane-project.org/sane-mfgs.html says that support for 'ScanJet 6100C' is 'Complete'. What can I try next? I'm willing to start hacking hardware/drivers if necessary but I have absolutely no idea where to begin, nor even where to ask. Justin
[sane-devel] About HP scanners
Dean Loros autocros...@macdialup.com wrote: Hi, phone calls in return. It seems that HP is getting sensitive in regards to Linux support is willing to talk--The last conversation with a Senior member of tech support ( knowledgeable about Linux Distros) If a SANE developer needs some HP hardware to write a backend, please contact either me or Aur?lien JARNO and we'll forward the request to the right person :) (for the sake of completeness, neither Aur?lien nor I work for HP) JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org GPG KeyID 0xF5D65169
[sane-devel] Canon Lide 50/Plustek
On Friday 18 August 2006 12:40, Simon Troup wrote: Hi my scanner is a Canon Lide 50, I'm on OSX 10.4. Sscanimage is returning this ... device `plustek:libusb:005:003-04a9-220e-ff-00' is a Canon N1240U/LiDE30 USB flatbed scanner ah, interesting ;) didn't know that so far... does it work correctly with the latest CVS version? I've managed to get the scanner to work but it doesn't grab the whole print area, I'm after A4 and it's returning scans that are a little smaller, maybe it's defaulting to letter size or something. How did you grab that - scanimage? The defaults for the backend are far smaller than A4. Just to get me going and pointed in the right area, is there anything that can be done, there was nothing obvious in the config or FAQ, I'm not sure what words I should be searching for or which docs to start on. The devices' maximum scanarea definition could be found in plustek-usbdevs.c - watch out for LiDE30 comments. The default scanarea definition for the backend is located at plustek.h HTH Gerhard
[sane-devel] HP Scanjet 2400 (genesys)
Dear Sir/Madam, I am trying to scan images through the scanner mentioned above. The sane-find-scanner lists my scanner. Also scanimage -L lists the device properly. But when I issue command scanimage image.pnm, I am getting following errors and the hardware makes little motor noise and stops. [genesys] WARNING: Your scanner is not fully supported or at least [genesys] had only limited testing. Please be careful and [genesys] report any failure/success to [genesys] sane-devel@lists.alioth.debian.org. Please provide as many [genesys] details as possible, e.g. the exact name of your [genesys] scanner and what does (not) work. Please let me know how to overcome this problems. It would be a great help. Thanks Regards, Shailesh - How low will we go? Check out Yahoo! Messenger?s low PC-to-Phone call rates. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060819/a8651360/attachment.html From adeur...@gmx.net Sat Aug 19 10:49:38 2006 From: adeur...@gmx.net (abel deuring) Date: Sat Aug 19 10:44:22 2006 Subject: [sane-devel] Acard AEC6712S (atp870u.ko) and HP 6100C C2520A (sg.ko) problems In-Reply-To: 20060819054626.ga10...@jfindlay.us References: 20060818011541.gd11...@jfindlay.us 44e58e73.6060...@gmx.net 20060819054626.ga10...@jfindlay.us Message-ID: 44e6ecc2.6040...@gmx.net Justin, On Fri, Aug 18, 2006 at 11:54:59AM +0200, abel deuring wrote: If possible, try different cables and another SCSI adapter, or connect another SCSI device to the Acard adapter to get a better idea, where the error might come from. I took the scanner, SCSI-2 cable, and acard SCSI host adapter and plugged them into my roomate's windows computer, installed the appropriate drivers, rebooted a few times, suffered through windows' occult complaints but eventually got the device functioning. Next I tried it on his FC4 system (same hardware, different OS) which, upon loading the appropriate kernel modules segfaulted the kernel and froze the machine. Sometimes I am able to get the kernel modules loaded on my machine before the atp870u driver complains. At this point sane-find-scanner detects the scanner found SCSI processor HP C2520A 3644 at /dev/sg1 but `scanimage -L` does nothing. Perhaps it precipitates an error of some kind because after cancelling the command sane-find-scanner again detects nothing and subsequent driver reloadings print out the same set of SCSI errors. I know at lease someone somewhere has gotten this scanner working before because http://www.sane-project.org/sane-mfgs.html says that support for 'ScanJet 6100C' is 'Complete'. What can I try next? I'm willing to start hacking hardware/drivers if necessary but I have absolutely no idea where to begin, nor even where to ask. Sounds like a bug in the lower level part of the SCSI drivers, or like a hardware error. I am not sure what I can honestly recommend. I have never used an Acard SCSI adapter, and don't want to spread FUD, but anyway: Some time ago, other users reported problems with Acard SCSI adapters. The atp870u driver contained at least one strange bug: the data returned for the INQUIRY command was limited to the standard length, while several scanners describe hardware details in an -- absolutely legal -- vendor-specific extension of the inquiry data, thus confusing one or the other Sane backend. I noticed the author of the backend about this bug, never got reply, but somehow and at some time this bug was fixed in the kernel sources. Generally, I have the impression that there are SCSI adapters which are better supported by the Linux kernel, so, before you continue to hunt a bug, it would be worth to try for example an adapter supported for example by the sym53c8xx or the aic7xxx drivers. In my experience, these drivers are very stable, well supported, and you can buy for example a used Adaptec 2940 for a few dollar at Ebay. Abel
[sane-devel] grey 4bit/pixel
Shashi Kumar M.S. wrote: hi, iam searching a scanner that supports at about 300 dpi and 4 bit /pixel grey scanner. i found from the scanner that most of the scanner support 8/16 bit depth in grey mode. is there any way to modify this code to support 4 bit grey scale depth per pixel. well, the source code of scanimage, xsane etc is freely available ;) all suggestions are welcome - look for a (documented) file format that supports 4 bit images (or define your own format ;) - patch scanimage or another frontend so that it can write the scan data in the format you selected. Alternatively, you can convert existing 8 bit images, as produced by a Sane frontend, with a converter program. I am not aware of any 4 bit image formats, but if they exist, you might already find such a converter in the usual Linux distributions. Otherwise, write one. The PPM, PGM, PBM formats (default for scanimage output) are very simple, and it is quite straightforward to read them with C, Python, Perl, Java or whichever other programming language. Abel
[sane-devel] grey 4bit/pixel
On Sat, 19 Aug 2006 14:56:58 +0200, abel deuring adeur...@gmx.net wrote: Shashi Kumar M.S. wrote: hi, iam searching a scanner that supports at about 300 dpi and 4 bit /pixel grey scanner. i found from the scanner that most of the scanner support 8/16 bit depth in grey mode. is there any way to modify this code to support 4 bit grey scale depth per pixel. well, the source code of scanimage, xsane etc is freely available ;) all suggestions are welcome - look for a (documented) file format that supports 4 bit images (or define your own format ;) - patch scanimage or another frontend so that it can write the scan data in the format you selected. Alternatively, you can convert existing 8 bit images, as produced by a Sane frontend, with a converter program. I am not aware of any 4 bit image formats, but if they exist, you might already find such a converter in the usual Linux distributions. Otherwise, write one. The PPM, PGM, PBM formats (default for scanimage output) are very simple, and it is quite straightforward to read them with C, Python, Perl, Java or whichever other programming language. Abel 'XnView' should do the job. Wolfram Heider
[sane-devel] grey 4bit/pixel
On Sat, 19 Aug 2006, abel deuring wrote: Shashi Kumar M.S. wrote: iam searching a scanner that supports at about 300 dpi and 4 bit /pixel grey scanner. i found from the scanner that most of the scanner support 8/16 bit depth in grey mode. is there any way to modify this code to support 4 bit grey scale depth per pixel. Why? What constitutes a good answer might depend on it. - look for a (documented) file format that supports 4 bit images (or define your own format ;) - patch scanimage or another frontend so that it can write the scan data in the format you selected. Alternatively, you can convert existing 8 bit images, as produced by a Sane frontend, with a converter program. I am not aware of any 4 bit image formats, but if they exist, you might already find such a converter in the usual Linux distributions. Otherwise, write one. The PPM, PGM, PBM formats (default for scanimage output) are very simple, and it is None of those formats support 4-bit data. They do support maxlevel=15 data, but the data are represented with 8-bits. PBM (P4) is one bit per pixel. If you want you could stack 4 pbm images. quite straightforward to read them with C, Python, Perl, Java or whichever other programming language. -- Mike henne...@web.cs.ndsu.nodak.edu it stands to reason that they weren't always called the ancients. -- Daniel Jackson
[sane-devel] SANE 2 proposal : sane_get_device_descriptor()
Hello, Using SANE 1, application can retreive informations only about detected devices by sane_get_devices(). That would be nice if SANE allow to retreive such data for any device name. I suggest : * make sane_get_devices() returns a list of device name (e.g. a NULL terminated SANE_String_Const array); * create const SANE_Device_Descriptor* sane_get_device_descriptor(SANE_String_Const name) wich return the device name descriptor. * Drop the name field of SANE_Device_Descriptor. I wish you find this suggestion useful. ?tienne. -- Verso l'Alto !
