[sane-devel] Driverless IPP Scanning with SANE
Hi, the Printing Working Group (http://www.pwg.org/) has developed several standards for printers and multi-function devices (print, scan, copy, fax) to allow its use without hardware-model-specific software or data (aka driver). There are already all standards needed for driverless printing and they are actually implemented in printers on the market. The PWG's own driverless printing standard is IPP Everywhere, but AirPrint, Wi-Fi Direct, and Mopria us also a lot of the PWG's standards. All of these standards use the PWG's Internet Printing Protocol (IPP) and DNS-SD but different standardized formats for the print jobs. Wi-Fi Direct adds a printer-internal Wi-Fi server for wireless printing without Wi-Fi router. Via IPP-over-USB also devices connected to USB are supported (Linux support via ippusbxd, https://github.com/OpenPrinting/ippusbxd). These driverless printing standards are fully supported in Linux, from Ubuntu 17.10 on and continuously improved. The PWG has recently also developed an IPP scanning standard, which provides a standard protocol for communicating with scanners in IPP multi-function devices (via network or IPP-over-USB): http://ftp.pwg.org/pub/pwg/candidates/cs-ippscan10-20140918-5100.17.pdf The best way to access this class of scanners from Linux would be to create a SANE backend for IPP Scan. Therefore I have opened a project for the Google Summer of Code 2018: https://wiki.linuxfoundation.org/gsoc/google-summer-code-2018-openprinting-projects#sane-module-for-ipp-driverless-scanning -- SANE module for IPP driverless scanning --- Version 2.0 and newer of the Internet Printing Protocol (IPP) support polling the full set of capabilities of a printer and if the printer supports a known Page Description Language (PDL), like PWG Raster, Apple Raster, PCLm, or PDF, it is possible to print without printer-model-specific software (driver) or data (PPD file), so-called “driverless” printing. This concept was introduced for printing from smartphones and IoT devices which do not hold a large collection of printer drivers. Driverless printing is already fully supported under Linux. Standards following this scheme are IPP Everwhere, Apple AirPrint, Mopria, and Wi-Fi Direct Print. As there are many multi-function devices (printer/scanner/copier all-in-one) which use the IPP, the Printing Working Group (PWG) has also worked out a standard for IPP-based scanning, “driverless” scanning, to also allow scanning from a wide range of client devices, independent of which operating systems they are running. Conventional scanners are supported under Linux via the SANE (Scanner Access Now Easy) system and require drivers specific to the different scanner models. Most of them are written based on reverse-engineering due to lack of support by the scanner manufacturers. To get driverless scanning working with the software the users are used to the best solution is to write a SANE module for driverless IPP scanning. This module will then automatically support all IPP scanners, thousands of scanners where many of them do not yet exist. The student's task is to write this SANE module for IPP driverless scanning and so make Linux ready for the future of driverless devices. Mentors: Till Kamppeter, Project Leader OpenPrinting (till at linux dot com), SANE upstream developers TBD Desired knowledge: C programming, DNS-SD, IPP Code license: GPL 2+ -- I want to ask whether someone of you would (together with me) mentor a student to do this project. The SANE project does not need to be mentoring organization at the GSoC for that. Mentoring organization will be the Linux Foundation. Thank you very much in advance Till -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Which HP-AIO Devices are supported by SANE
rohit bal wrote: I want to make a custom Scan application supporting HP-AIO devices. Can anyone give me the list of All HP-AIO devices supported by SANE. HP's multi-function devices are not supported by the core package of SANE. They use the add-on SANE driver of HPLIP from http://hplipopensource.com/ Here you find a list of all supported devices. The driver is fully open-source for 98 % of the devices (there are a few which need a proprietary plug-in). So for nearly all of the devices you can take the code for your application. Till
[sane-devel] Which HP-AIO Devices are supported by SANE
There is one SANE backend named hpaio for all multi-function devices from HP. It gets installed into the same directory where all the other backends are. The backend is part of HPLIP, so you need to have HPLIP installed to get this backend onto your system. Till rohit bal wrote: Thanks for the info. Which sane Backend supports 7650,5590 device. Please let me know the path of the sane backend. Thanks Rohi Date: Wed, 4 Feb 2009 10:50:49 +0100 From: till.kamppeter at gmail.com To: rohitsharma36 at hotmail.com CC: sane-devel at lists.alioth.debian.org Subject: Re: [sane-devel] Which HP-AIO Devices are supported by SANE rohit bal wrote: I want to make a custom Scan application supporting HP-AIO devices. Can anyone give me the list of All HP-AIO devices supported by SANE. HP's multi-function devices are not supported by the core package of SANE. They use the add-on SANE driver of HPLIP from http://hplipopensource.com/ Here you find a list of all supported devices. The driver is fully open-source for 98 % of the devices (there are a few which need a proprietary plug-in). So for nearly all of the devices you can take the code for your application. Till Discover your phone style WIN a Windows Mobile phone. Your style! Try it now! http://www.whatsmyphonestyle.com Discover your phone style WIN a Windows Mobile phone. Your style! Try it now! http://www.whatsmyphonestyle.com
[sane-devel] HP officejet: access scanner over the network
To be able to access your scanner without supplying the scanner URI (hpaio:/...) and so also to be able to access it with saned and xsane, you need to set up a CUPS queue for the printing part of your device (with CUPS URI hp:/net/Officejet_J6400_series?ip=192.168.2.103). Then you can do the scanimage command without the -d option: scanimage -x 215.9 -y 297 -pv --mode gray $FILE and use also any other frontend without specifying your scanner. And if you run saned, it will share your scanner then. Till Wouter van Marle wrote: Has anyone an idea on this issue? On Tue, 2008-12-30 at 10:17 -0600, gobo wrote: you need to have hplip installed. with hplip you can then use hpaio to access the scanner across the network. for example: scanimage -x 215.9 -y 297 -d hpaio:/net/Officejet_J6400_series?ip=192.168.2.103 -pv --mode gray $FILE OK that part works after substituting my scanner name and ip of course. So the scanner can be addressed, and is scanning properly. But this is not the way I like to do my scanning of course, it's nice for testing and all. How can I integrate this into a saned server or whatever, so I can use xsane or another sane compliant software in the network to access this scanner? Previously the HP was connected to the server over USB, and the rest of the workstations could very easily access the scanner through the saned interfaces. The workstations are on Mandriva Linux by the way, and could easily add this scanner through the control panel. Just give the ip of the server, and the scanner was detected automatically. Wouter. On Tue, Dec 30, 2008 at 7:45 AM, Wouter van Marle wouter at squirrel-systems.com wrote: Hi all, I am the happy owner of an HP Officejet Pro L7560 (an all-in-one device). Until recently I had this connected to my server through USB, and printing and scanning all worked fine. Of course using sane on the server to access the scanner from the workstations. Now I have a new office, all is rearranged, and the Officejet is connected directly to the network. It gets it's IP from the server by DHCP, which I configured to be fixed, so far so good. Printing (though Cups) works like a charm after some googling to get the correct way to address the printer, but now scanning! How can I do this? A couple of hours searching Google didn't give me a single clue... the scanner is not found automatically by Sane, and no idea on how to address it. I'm looking for one of two solutions: 1) server is talking to the scanner one way or another, and then shares the scanner with the workstations through the existing Sane interface. 2) the workstations (three only, it's a small network) talk to the scanner directly (they are all on the same 192.168.2.0/24 subnet) (if easy/automatically to configure on the workstations). Wouter. -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org
[sane-devel] HP officejet: access scanner over the network
Try running scanimage -L as root. If it finds the scanner, there is a permission problem. Till Wouter van Marle wrote: Dear Till, Thank you for your answer. Unfortunately it doesn't work like that for me. I have installed the printer in CUPS, the uri is hp:/net/Officejet_Pro_L7500?ip=192.168.2.9 Printing works, so the above setting/uri is for sure correct. However scanimage -L doesn't list any scanners. Wouter. On Wed, 2009-01-07 at 09:46 +0100, Till Kamppeter wrote: To be able to access your scanner without supplying the scanner URI (hpaio:/...) and so also to be able to access it with saned and xsane, you need to set up a CUPS queue for the printing part of your device (with CUPS URI hp:/net/Officejet_J6400_series?ip=192.168.2.103). Then you can do the scanimage command without the -d option: scanimage -x 215.9 -y 297 -pv --mode gray $FILE and use also any other frontend without specifying your scanner. And if you run saned, it will share your scanner then. Till Wouter van Marle wrote: Has anyone an idea on this issue? On Tue, 2008-12-30 at 10:17 -0600, gobo wrote: you need to have hplip installed. with hplip you can then use hpaio to access the scanner across the network. for example: scanimage -x 215.9 -y 297 -d hpaio:/net/Officejet_J6400_series?ip=192.168.2.103 -pv --mode gray $FILE OK that part works after substituting my scanner name and ip of course. So the scanner can be addressed, and is scanning properly. But this is not the way I like to do my scanning of course, it's nice for testing and all. How can I integrate this into a saned server or whatever, so I can use xsane or another sane compliant software in the network to access this scanner? Previously the HP was connected to the server over USB, and the rest of the workstations could very easily access the scanner through the saned interfaces. The workstations are on Mandriva Linux by the way, and could easily add this scanner through the control panel. Just give the ip of the server, and the scanner was detected automatically. Wouter. On Tue, Dec 30, 2008 at 7:45 AM, Wouter van Marle wouter at squirrel-systems.com wrote: Hi all, I am the happy owner of an HP Officejet Pro L7560 (an all-in-one device). Until recently I had this connected to my server through USB, and printing and scanning all worked fine. Of course using sane on the server to access the scanner from the workstations. Now I have a new office, all is rearranged, and the Officejet is connected directly to the network. It gets it's IP from the server by DHCP, which I configured to be fixed, so far so good. Printing (though Cups) works like a charm after some googling to get the correct way to address the printer, but now scanning! How can I do this? A couple of hours searching Google didn't give me a single clue... the scanner is not found automatically by Sane, and no idea on how to address it. I'm looking for one of two solutions: 1) server is talking to the scanner one way or another, and then shares the scanner with the workstations through the existing Sane interface. 2) the workstations (three only, it's a small network) talk to the scanner directly (they are all on the same 192.168.2.0/24 subnet) (if easy/automatically to configure on the workstations). Wouter. -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org
[sane-devel] [lsb-discuss] Scanning interfaces and LSB 4.0
Theodore Ts'o wrote: The simple solution would be add the necessary Scanner interfaces to the LSB. Unfortunately, we have many other high priority items on our work queue, and the SANE interfaces need to be documented before they could be added to the LSB. This means we need volunteers to do the following: 1) Determine the set of SANE interfaces that needs to be added to the LSB. Here we would need the complete set of interfaces for a scanner driver/backend. Anyone from the SANE developers could tell what exactly is needed? 2) Find out what documentation, if any exists for those interfaces. Ducumentation of the API is here: http://www.sane-project.org/html/doc009.html 3) Write any missing interfaces. You mean documentation/tests. If we can't get someone to do this, there are other alternatives, such as issuing waivers to printer driver packages. And maybe if the SANE interfaces are in a file with a specific name, and/or there is an easy way to recognize a package as being a printer driver, we can teach the LSB AtK to automatically give the scanner module a pass. Till, is that a fair summary of the situation? And do we have anyone with some free time to work on it? Unfortuntaly most of the usual suspects are busy with other high priority LSB 4.0 projects Yes, this is OK. As a last mean we issue waivers, but the best solution would be having SANE in the LSB. I appreciate very much if SANE developers could help here. Till
[sane-devel] SANE in LSB 4.0
Hi, we plan to include the SANE API into LSB 4.0, to make it easier for hardware vendors to write scanner drivers and make them available as distribution-independent packages or in case of multi-function devices to make distribution-independent driver packages for both printer and scanner part. See https://www.linuxfoundation.org/en/ProjectPlan40#LSB-Printing_Module https://www.linuxfoundation.org/en/SANE40 The standardization will be based on the SANE1 API, as SANE2 is not started yet and even if it would have been defined it would take some years to have it in all enterprise distributions (mainly SLES and RHEL, on which the LSB is based). So even with SANE2 in the plans it would be a great step forward tohave SANE1 in the LSB. I want to ask you as upstream developers of SANE whether you could help us on integrating SANE in the LSB by contributing work on the documentation and testing framework. We would appreciate if you could help us. Till
[sane-devel] SANE 1.1.0 Release discussion
This is a much better solution than coming with a completely new SANE2 API. At the Linux Foundation Summit in April we have decided on taking the SANE1 API into LSB 4.0, so that scanner manufacturers can make distribution-independent LSB-based scanner driver packages. Standardizing on the driver structure, like option names and groups, debug modes, ... is also a great improvement step without need of API changes. Please post specs soon, so that I can add them to the driver design guidelines https://www.linux-foundation.org/en/OpenPrinting/WritingAndPackagingPrinterDrivers (perhaps the Wiki page needs to be renamed sooner or later, as with the LSB DDK I am also addressing scanner drivers). Also the planned release schedule is great, as this way SANE 1.1.0 will make it into the fall editions of the major Linux distributions (Ubuntu Intrepid, Fedora 10, ...). Till m. allan noah wrote: Lets talk about SANE 1.1.0 release, both timetables and deliverables. I have tried to pick some things from recent discussions, and build on the momentum provided by stef and julien. It is not my intention to hijack this process, but I have some spare cycles coming up, and we are all tired of talking :) I have five general points for 1.1.x: - no changes to function calls - no changes to structures - 1.0 backends forward compatible with 1.1 - improve backend consistency - support more advanced scanners Based on those ideas, I propose: 1. Consistent, translatable option groups (please add/change to this list): 'Standard' = source, mode, resolution 'Geometry' = x/y and paper size params 'Enhancement' = bright/gamma/contrast/thresh, rif, sharpen, halftone settings, etc 'Advanced' = compression, calibration, double/manual feed controls, backlights, tests, dropout, etc 'Sensors/Buttons' = an option for every hardware button or sensor others? 2. Consistent well known-options, button handling and papersize come to mind. others? 3. Two new return codes: SANE_STATUS_HW_LOCK to tell the frontend that the scanner has a hardware lock installed, and SANE_STATUS_WARMING_UP for lamp. 4. More SANE_FRAME types, jpeg, fax, IR, text, xml. 5. Add SANE_TYPE_HW_BUTTON for scanners' buttons. The constraint field would allow to distinguish between push buttons (0 or 1 )and 'wheel buttons' (0 to N). 6. Common debugging bitmask: 1 major errors 2 minor errors 4 function start/stop msgs 8 function detail msg 16 SANE_OPTION processing msgs 32 calibration msgs 64 outgoing command dump 128 incoming data dump help me fix that... 6. Add common configuration reading function in sanei_* so that new or maintained backends can benefit from it. Wholesale config file restructuring? Other things from stef's list have been left out because the dont meet my 5 points, anyone else have some more? My plan is to work on this over the next two months, and aim for a feature freeze around July 4th, with release close to July 30th, though we could certainly accelerate that with some help. Comments welcome. allan
[sane-devel] SANE2, what do we want ?
Note also one thing about the SANE2 discussion: Currently I am working on getting SANE1 into the LSB (I posted already about this some months ago and no one answered). This will help us that it is much easier for scanner manufacturers to ship drivers with their scanners. They can simply build them with the LSB DDK and then they will work on all (LSB-compliant) distros. Till stef wrote: Le Friday 28 March 2008 22:05:24 Julien BLACHE, vous avez ?crit : stef stef.dev at free.fr wrote: Hi, I'm rather inclined to the 3 goal, since I feel there are quite a few things to do to improve SANE. Having a new standard doesn't mean SANE 1 stops to exist. Both can coexist. Do you really think there is the needed manpower to co-maintain 2 versions of SANE? JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169 Hello, indeed we are only a few people. But things can be done so that it isn't hard to achieve. However, does it mean you are akin to keep things as they are ? which is -of course- perfectly fine. Regards, Stef
[sane-devel] IP address location
You need to change the IP in the configuration of your CUPS print queue, HPLIP gets this info from there also for the non-printing functions. Till Jim wrote: I had to change IP address in router. Now, sane cannot find printer/scanner/fax (HP 7410). Have looked for 4 hours for location(s) to change IP address in Sane. The 7410 prints OK, but Xsane can't find printer. Investigation reveals it still has old IP address. Where can I go to change it to new IP address? Thanks, Jim
[sane-devel] LSB DDK: Support for scanner drivers/SANE into LSB 3.2?
Ren? Rebe wrote: On Friday 22 June 2007 13:30:13 Till Kamppeter wrote: Ren? Rebe wrote: Hase the SANE2 development actually started? What are the limitations of Don't think so. [...] I think SANE 1 is pretty fine and in too wide use to abondone. Features of new scanners, such as JPEG and infrared frames can easily be added without breaking anything, just new types. I think most SANE 2 jadda jadda is driven by some let's rewrite everything so that it looks prettier without thinking about the aspects like: - enforcing all application support to be rewritten - probably loosing a lot of old driver noone will port to SANE 2 and probably: - not enough volunteers to rewrite everything from scratch which is possibly why no SANE 2 code despite a lot of SPEC talking has seen the wild, yet. [...] As a company having Open Source scanning solutions in production, and helping other companies to do so I appreciate this efford and would help - however I can only do so if SANE 2 development does not throw all away that we built up the last 10 years. I think under these circumstances it is the best to simply go ahead and do everything to get the current SANE into the LSB. The time is much better invested for getting SANE into the LSB than for writing a new SANE. Current SANE in LSB will make many manufacturers start supporting Linux immediately. SANE2 will make a big confusion and repel the manufacturers. So I recommend for the best for Linux on the desktop and for the SANE project is to concentrate on getting SANE into the LSB now. Yes, this is my talking for a long time. Unfortunatly some SANE developers lobby for the SANE2 from scratch. I take a look into what is necessary to get SANE into the LSB over the weekend. Thank you for bringing this to our attention. Yours, Any progress on preparing SANE for getting it into the LSB? Till
[sane-devel] LSB DDK: Support for scanner drivers/SANE into LSB 3.2?
Any news on SANE and LSB? Till Till Kamppeter wrote: Till Kamppeter wrote: Does the lsb project expect some testing code to be written? What tests would be needed, or expected, if any? What we need is two interfaces of SANE, once the frontend/library interface, so that one can have scanning functionality in LSB-packaged applications, and second, the library/backend interface to allow distribution-independent LSB-based scanner driver packages. Am I right that these two interfaces are the same and that what I call library, being the file /usr/lib/libsane.so.1 is a copy (why not a symlink?) of the dll backend (/usr/lib/sane/libsane-dll.so.1)? Then we would have only one interface to test, but we need to test both sides of it. We need to test whether a library with that interfaces is there for being linked by (LSB-built) frontends and we need to test whether there is a dll backend with the appropriate backend interface which will find an added (LSB-built) driver. Till
[sane-devel] LSB DDK: Support for scanner drivers/SANE into LSB 3.2?
Gerald Murray wrote: Ren? Rebe wrote: I take a look into what is necessary to get SANE into the LSB over the weekend. Did you already find out something? Hi Till, I took a quick look. It looks like the lsb project wants headers --stripped of all comments and programmer remarks; the library would be empty functions, as 'basic' as possible. Possibly headers: sane.h, saneopts.h would be enough, as lsb tools would only test for the presence of sane, so none of the libraries in /usr/lib/sane/* would be tested? /usr/lib/libsane.so would be the basic library. Does the lsb project expect some testing code to be written? What tests would be needed, or expected, if any? What we need is two interfaces of SANE, once the frontend/library interface, so that one can have scanning functionality in LSB-packaged applications, and second, the library/backend interface to allow distribution-independent LSB-based scanner driver packages. The LSB expects also testing code. Usually a program which exercises all the interfaces which are selected as requirement for the LSB (ideally, one should require all interfaces of the library). A test program could look like this: http://svn.easysw.com/public/cups/trunk/cups/testcups.c This is for CUPS but one could do a similar thing for SANE. The test program should not depend on a particular scanner model. One could auto-detect a scanner and if none is there use the test backend. The individual drivers in /usr/lib/sane/ do not need to be tested. Important are only the interfaces for new drivers and for applications with scanning functionality. Till
[sane-devel] LSB DDK: Support for scanner drivers/SANE into LSB 3.2?
Till Kamppeter wrote: Does the lsb project expect some testing code to be written? What tests would be needed, or expected, if any? What we need is two interfaces of SANE, once the frontend/library interface, so that one can have scanning functionality in LSB-packaged applications, and second, the library/backend interface to allow distribution-independent LSB-based scanner driver packages. Am I right that these two interfaces are the same and that what I call library, being the file /usr/lib/libsane.so.1 is a copy (why not a symlink?) of the dll backend (/usr/lib/sane/libsane-dll.so.1)? Then we would have only one interface to test, but we need to test both sides of it. We need to test whether a library with that interfaces is there for being linked by (LSB-built) frontends and we need to test whether there is a dll backend with the appropriate backend interface which will find an added (LSB-built) driver. Till
[sane-devel] LSB DDK: Support for scanner drivers/SANE into LSB 3.2?
Ren? Rebe wrote: I take a look into what is necessary to get SANE into the LSB over the weekend. Did you already find out something? Till
[sane-devel] LSB DDK: Support for scanner drivers/SANE into LSB 3.2?
Hi, one important point which prevented from packaging HP's HPLIP was that it contains a SANE driver for the scanners in HP's multi-function devices and SANE is neither in the LSB nor in the LSB DDK. Also other printer manufacturers, like Epson or Brother could run into this problem. I succeeded now to build SANE (sane-backends) with dynamically linked drivers in the LSB 3.1 Build Environment chroot. This SANE version does not work with parallel port scanners (some standard hardware IO functions needed by libieee1284 not in LSB) and it is not able to ask the user for a password (getpass() not in the LSB), but it provides the full SANE API for building scanner drivers. To test whether scanner drivers built with this SANE version will work in real distros I have simply replaced some drivers of my normal system (Ubuntu Gutsy) by drivers from my LSB SANE package and they work also under Gutsy's SANE. Note also that Gutsy comes with SANE 1.0.18 and my package is a subversion snapshot of SANE near 1.0.19. So everything seems SANE now to make distribution-independent packages of scanner drivers. And this will not only help for being able to include the scanner drivers for multi-function devices in the distribution-independent printer driver packages, it will also allow the creation of distribution-independent driver packages for stand-alone scanners and so we expand the LSB DDK also to scanners. Therefore I suggest also to take SANE into the LSB 3.2. SANE comes with every distro, and its ABI (including the dynamic linking of the drivers) is really stable (SANE 1.0.x series). Manufacturers like for example Brother (I am not sure, perhaps Samsung too) provide binary-only SANE drivers which easily plug into all current distros. SANE in the LSB would also allow LSB applications to have access to scanners. Apps like OpenOffice.org could be LSB-packaged with full functionality then. SANE developers, WDYT about SANE getting into the LSB? Are you willing to provide API documentation and testing procedures? Till
[sane-devel] [lsb-discuss] LSB DDK: Support for scanner drivers/SANE into LSB3.2?
Wichmann, Mats D wrote: Just comments on this piece, not on the bigger question of whether SANE support should be added to LSB and when (when mostly depends on who has time to do the work). I have already asked on the SANE mailing list whether the SANE developers would provide documentation and testing scripts, but did not get an answer yet. Hardware specifics were always considered outside the scope of LSB as it was purely focused on defining a target for user-level applications. With the new focus on hardware in the form of printers and perhaps now scanners we may need to think a bit about that. The LSB DDK is generally intended to allow hardware manufacturers to supply drivers in a distribution-independent way and so to make it easier for them to support Linux. It covers only user-space drivers, not kernel modules. Having the printing and scanning infrastructure in the LSB is also important for user-level applications, as they can have printing and scanning functionality then (most common user applications have printing functionality, and many also scanner access, like OpenOffice.org or the GIMP). getpass has been explained as one of those don't use this interfaces as the password is stored in clear text in the process's address space. The glibc documentation contains one alternative implementation. It should be possible to have password prompting without using getpass specifically. So we should file bugs against CUPS and SANE that they use this unsecure function and should replace it? Till
[sane-devel] LSB DDK: Support for scanner drivers/SANE into LSB 3.2?
Ren? Rebe wrote: SANE developers, WDYT about SANE getting into the LSB? Are you willing to provide API documentation and testing procedures? Some of us (read including me) are interested in this standardization efford, while others plan to reinvent the SANE wheel with a 100% incompatible SANE2 for about 5 years or so, now. Hase the SANE2 development actually started? What are the limitations of the current SANE framework? Is there no possibility to overcome them without creating completely new driver and application APIs/ABIs? Having the SANE API in the LSB is certainly a big step forward in future end-user experience with Desktop Linux, it certainly also makes it harder to rectify an incomtiable rewrite of SANE just for the sake of it. I would appreciate the cooperation from the SANE developers to get SANE into LSB 3.2, as only adding this adds the same possibilities for scanners which we have now with the LSB DDK for printers. See http://www.openprinting.org/ http://www.linux-foundation.org/en/OpenPrinting/WritingAndPackagingPrinterDrivers http://www.linux-foundation.org/en/OpenPrinting/LFSummitMountainView2007 http://www.linux-foundation.org/images/e/e4/Distro-Independent-Packages.pdf Till
[sane-devel] LSB DDK: Support for scanner drivers/SANE into LSB 3.2?
Ren? Rebe wrote: Hase the SANE2 development actually started? What are the limitations of Don't think so. [...] I think SANE 1 is pretty fine and in too wide use to abondone. Features of new scanners, such as JPEG and infrared frames can easily be added without breaking anything, just new types. I think most SANE 2 jadda jadda is driven by some let's rewrite everything so that it looks prettier without thinking about the aspects like: - enforcing all application support to be rewritten - probably loosing a lot of old driver noone will port to SANE 2 and probably: - not enough volunteers to rewrite everything from scratch which is possibly why no SANE 2 code despite a lot of SPEC talking has seen the wild, yet. [...] As a company having Open Source scanning solutions in production, and helping other companies to do so I appreciate this efford and would help - however I can only do so if SANE 2 development does not throw all away that we built up the last 10 years. I think under these circumstances it is the best to simply go ahead and do everything to get the current SANE into the LSB. The time is much better invested for getting SANE into the LSB than for writing a new SANE. Current SANE in LSB will make many manufacturers start supporting Linux immediately. SANE2 will make a big confusion and repel the manufacturers. So I recommend for the best for Linux on the desktop and for the SANE project is to concentrate on getting SANE into the LSB now. Till
[sane-devel] LSB DDK: Support for scanner drivers/SANE into LSB 3.2?
Ren? Rebe wrote: Yes, this is my talking for a long time. Unfortunatly some SANE developers lobby for the SANE2 from scratch. I take a look into what is necessary to get SANE into the LSB over the weekend. To see what is required visit the LSB developer network (the parts for application developers): http://www.linux-foundation.org/en/Developers The LSB package of sane-backends which I have built already is here: http://www.linux-foundation.org/~till/tmp/sane-lsb/ Thank you very much in advance for your cooperation. Till
[sane-devel] Epson 4490 in Debian
Julien BLACHE wrote: If something like that would materialise, I suggest we also drag in the CUPS and ghostscript packagers to get the EPSON AVASYS printer drivers on the right track as well. # Johannes Meixner has already contacted us, Till Kamppeter just did. That'd be nice indeed. I don't know if the printer drivers are packaged in Debian, but they certainly could be once they'll be free :) The free printer drivers from Epson Avasys are packaged in Debian, as they are built into ESP GhostScript (gs-esp). Till
[sane-devel] HP PSC 1410 and 1510
The 1410 and 1510 are both completely supported. See http://hplip.sf.net/ You can buy them both. The 1510 I have tested by myself on Mandriva 2006. It works perfectly. I got it for testing from HP. Till Michael Hennebry wrote: I'm thinking of getting an HP PSC 1410 or 1510 all-in-one. First I would like to know whether I can make it go. I've read that 1410 works with CUPS and with sane, but haven't found mention of either the 1410 or the 1510 on sane's website. What do I need to find out to know whether the 1410 or 1510 will work with sane?
[sane-devel] Scanner (USB) not found after kernel upgrade
Johannes Meixner wrote: Hello, On Feb 7 21:32 Till Kamppeter wrote (shortened): The usblp module can be replaced by a libusb-based CUPS backend. Download http://www.linuxprinting.org/till/tmp/usb-libusb.c ... The libusb-based CUPS backend is written by Couriousous, a Mandriva contributor, thanks to him for this work. I CC him, so that he can perhaps help on this issue. I do not understand how the original code should work (at least not for CUPS 1.1.x) because there is no main function. Doesn't each CUPS backend run as stand-alone program? Sorry, forgot to give the correct instructions. Here are the instructions which Couriousous has given: I've written a cups libusb backend. It is source-compatible with usb-unix.c. To use it, edit usb.c and change the usb-unix.c include by usb-libusb.c. Then compile with -lusb ( by setting LDFLAGS ). It's based on usb-unix.c, highly inspired of usblp kernel module and sane. Another problem is the memory card reader in the Epson photo printers and MF devices, AFAIK there is no libusb-based driver for USB mass storage devices, and no solution to provide mountable file systems completely in user space. Yes. For me it hangs up during list_devices() with endless - INFO: USB printer is busy; will retry in 5 seconds... - messages and dmesg reports usbfs: interface 2 claimed by usb-storage while ... sets config I don't know if it is possible with libusb but it should give up after a short time instead of endless probing (perhaps one can replace the unlimited while loops with limited for loops). After rmmod usb-storage it detects my EPSON Stylus Photo RX420 correctly. The conflict with usb-storage is because the RX420 has also a cardreader unit included. And on which level this has to be fixed? Here only CUPS and the kernel are involved. But here there is still a bug, printer/card reader combos from Epson worked for a long time, until the most recent kernel changes were done. Till
[sane-devel] 2 new paperweights: HP ScanJet 3800 and 4890
Henning Meier-Geinitz wrote: Hi, On Tue, Nov 15, 2005 at 02:41:30AM +0100, Till Kamppeter wrote: On the SANE has found a GL841 chipset and so I tried to run it with the genesys backend. I added usb 0x03f0 0x1b05 to genesys.con and ran SANE_DEBUG_GENESYS=255 scanimage -L but also without success. I think the code must be also changed (genesys_devices.c, at the end of that file). If this is possible, it would be great. Patches welcome. Thanks! I added the 4890 to our lists. It has the same ids as the 4850 (which is also not supported). Does not look so nice, then 4890 and 4850 seem to be the same hardware and when they did not succeed with the 4850 ... Works for me (tm). I also got some reports from other users through this interface recently. Maybe it was just too much data? Should be checked, there should be nothing preventing people from supplying as much info as possible, many people would give up instead of putting the info onto their own web space and then posting on the list. Till
[sane-devel] Reporting an unlisted/unsupported printer
gerard klaver wrote: On Thu, 2005-10-20 at 11:11 -0400, lhs wrote: Make HP Model PSC 1610 All-in-One, PSC 1600 series Bus USB V ID 03f0 P ID 4811 Chip? lines deleted Did you check the hpiao (externel backend) http://hpinkjet.sourceforge.net/hplip_readme.html#Device The PSC 1600 is reported to be supported, so the 1610 maybe also or in a next release. This model works with HPLIP. I have it here and scanning works without problems. Till
[sane-devel] HP Offijet 5110
sane-find-scanner shows only scanners which are accessed the standard way on USB or SCSI. The HP multi-function devices have a special access method. There are low-level driver daemons (HPLIP: hpiod and hpssd; HPOJ: ptal-mlcd) which talk to the scanner via the usblp kernel module (the one for USB printers). The hpaio and hpoj backends talk to the appropriate low-level driver daemon. scanimage -L should show your scanner. Till Guido Milanese wrote: I recently bought a HP officejet 5110: it works very well as USB printer, but I do not know how to configure it as scanner. I posted a message in another list (linuxprinting.hp) but I thinks it was not the best place, so I'm repeating the question here. Typing sane-find-scanner from shell or using GUI provided by my Linux distribution (Mandriva LE 2005: kernel 2-6-11) does not change the final result: the scanner is not seen by the OS. The answer of sane-find-scanner is: # No SCSI scanners found.[etc] # No USB scanners found. [etc] scanimage -L outputs: No scanners were identified. etc. The driver used by CUPS is hplip. There is also hpoj, that I understand that must be used for scanning. I the list below correct? /usr/lib/sane/libsane-hpoj.so /usr/lib/sane/libsane-hpoj.so.1 /usr/lib/sane/libsane-hpoj.so.1.0 /usr/lib/libhpojip.so.0 /usr/lib/libhpojip.so.0.1 /usr/lib/libsane-hpoj.so /usr/lib/libsane-hpoj.so.1 /usr/lib/libsane-hpoj.so.1.0 I also found, googling for a while, that there must be libusb: in my system I found: /usr/bin/libusb-config /usr/lib/libusb.la /usr/lib/libusb.so /lib/libusb-0.1.so.4 /lib/libusb-0.1.so.4.4.0 /lib/libusb.la I thank your for any help. What I would like to find is a good tutorial or a howto. thanks!
[sane-devel] genesys backend
Jens Luedicke wrote: On 9/23/05, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote: Hi I spent some time on fixing the last few bugs in the gl841 part known to me and preparing the backend for the final inclusion of gl841 support needed for my scanner. nice work :) random question: how can I use xsane without running it as root? xsane doesn't find the scanner if I run it as a user. Try this: http://www.linuxprinting.org/download/digitalimage/Scanning-as-Normal-User-on-Wierd-Scanner-Mini-HOWTO.txt Till
[sane-devel] Epson CX3200's scanner isn't detected with recent
Couriousous, here is again a case for your libusb-based CUPS backend. LukenShiro, can you rebuild your CUPS usb backend with the following: http://www.linuxprinting.org/till/tmp/usb-libusb.c Couriousous' installation instructions: - I've written a cups libusb backend. It is source-compatible with usb-unix.c. To use it, edit usb.c and change the usb-unix.c include by usb-libusb.c. Then compile with -lusb ( by setting LDFLAGS ). It's based on usb-unix.c, highly inspired of usblp kernel module and sane. It works here, but I've not tested it under all possible condition and failures, so it contain bugs. - Then unload the usblp kernel module, restart CUPS and you should be able to print and to scan. Till LukenShiro wrote: sane-backends' versions Reply-To: I'm using an Epson CX-3200 all-in-one/MFP (usb printer+scanner+photocopier), when usblp kernel module is loaded the scanner part is not detected (not even by root, but anyway it isn't a matter of permissions) by xsane and scanimage, and obviously it doesn't work. I tried sane-backends-1.0.16 and sane today snapshot (September 22nd), libusb-0.1.8 and 0.1.10a, with Gentoo and Slackware, both with kernel 2.6.13 (vanilla). epson is uncommented in dll.conf and right device id has been written in epson.conf. sane-find-scanner gives me this message: [..] found USB scanner (vendor=0x04b8 [EPSON], product=0x0802 [USB MFP]) at libusb:001:010 [??] scanimage -L : No scanners were identified.[..] lsusb : [..] Bus 001 Device 010: ID 04b8:0802 Seiko Epson Corp. Stylus CX3200 [..] xsane gives me about this message (it's in Italian language): No available device. in /var/log/messages and /var/log/syslog I've such messages: Sep 22 23:00:17 usb 1-1: usbfs: interface 1 claimed by usblp while 'scanimage' sets config #1 ep 22 23:19:09 usb 1-1: usbfs: interface 1 claimed by usblp while 'xsane' sets config #1 Sep 22 23:26:13 usb 1-1: usbfs: interface 1 claimed by usblp while 'scanimage' sets config #1 SANE_EPSON_DEBUG=255 scanimage : [sanei_debug] Setting debug level of epson to 255. [epson] sane_init: sane-backends 1.0.16-cvs [epson] sane_init, # epson.conf [epson] sane_init, # [epson] sane_init, # here are some examples for how to configure the EPSON backend [epson] sane_init, # [epson] sane_init, # SCSI scanner: [epson] sane_init, #scsi EPSON [epson] sane_init, # for the GT-6500, comment out the previous line and uncomment the following line: [epson] sane_init, #scsi [epson] sane_init, # [epson] sane_init, # Parallel port scanner: [epson] sane_init, #pio 0x278 [epson] sane_init, #pio 0x378 [epson] sane_init, #pio 0x3BC [epson] sane_init, # [epson] sane_init, # USB scanner: [epson] sane_init, # There are two different methods of configuring a USB scanner: libusb and the kernel module [epson] sane_init, # For any system with libusb support (which is pretty much any recent Linux distribution) the [epson] sane_init, # following line is sufficient. This however assumes that the connected scanner (or to be more [epson] sane_init, # accurate, it's device ID) is known to the backend. [epson] sane_init, #usb [epson] sane_init, # For libusb support for unknown scanners use the following command [epson] sane_init, # usb product ID device ID [epson] sane_init, # e.g.: [epson] sane_init, # usb 0x4b8 0x110 [epson] sane_init, # And for the scanner module, use the following configuration: [epson] sane_init, #usb /dev/usbscanner0 [epson] sane_init, #usb /dev/usb/scanner0 [epson] sane_init, usb 0x4b8 0x802 [epson] attach_one_usb(libusb:001:010) [epson] SANE Epson Backend v0.2.45 - 2000-01-09 [epson] attach(libusb:001:010, 3) [epson] attach: opening libusb:001:010 [epson] sane_get_devices() scanimage: no SANE devices found If I remove usblp module (with rmmod), the scanner got recognized and working, but it is only a workaround: scanimage -L : device `epson:libusb:001:010' is a Epson CC-570L flatbed scanner and xsane starts smoothly I suppose there is a problem with printer part that monopolizes all. BTW I've found a SUSE user's post on http://forums.suselinuxsupport.de/index.php?s=ea9dc99f955913e529b5 d2c7e1eb61a8showtopic=19054pid=109816st=0#entry109816 (one URL), regarding a similar problem with another MFP. He says: Seems that usb_set_configuration in sanei_usb.c was causing the failure since usblp had already set it. Commenting out the function and recompiling SANE allowed the interface to be claimed without problem. Xsane and Kooka are now happy. Thank you.
[sane-devel] geniusvp2 backend and SANE 1.0.16
Oi, I am packaging SANE 1.0.16 for Mandriva Linux currently. Unfortunately, I did not get the patch for the geniusvp2 backend applied: --- [...] Patch #19 (sane-backends-1.0.15-geniusvp2-0.2.1.patch.bz2): + /usr/bin/bzip2 -d + patch -p1 -s 1 out of 3 hunks FAILED -- saving rejects to file backend/Makefile.in.rej 18 out of 130 hunks FAILED -- saving rejects to file configure.rej ^^ The next patch would create the file doc/descriptions-external/geniusvp2.desc, which already exists! Assume -R? [n] n Apply anyway? [n] n 1 out of 1 hunk ignored -- saving rejects to file doc/descriptions-external/geniusvp2.desc.rej 1 out of 2 hunks FAILED -- saving rejects to file doc/sane.man.rej error: Bad exit status from /home/tkamppeter/tmp/rpm-tmp.96221 (%prep) --- Can you update your patch? Or better, can you make a distribution without patch, having the additional files as usual files and a script placing the files in the source tree and adding necessary stuff into the configure.in/.ac file and the Makefile.in and then run autoconf/automake. In patches you should also never generate patches on machine-generated files (like configure) but only on human-entered files (like configure.in/.ac), so that the patch gets small and simple. Otherwise there is no chance to manually adapt the patch to a new version of SANE. The best is to avoid patches as a source tarball. It is a maintenance nightmare. I have temporarily deactivated the geniusvp2 backend in the Mandriva SANE RPM now. I will put it back in as soon as an update is available. Thanks in advance for your help. Till
[sane-devel] Epson Perfection 1260 Photo does not work with SANE 1.0.16
Oi, after upgrading to SANE 1.0.16 the Epson Perfection 1260 Photo is not recognized by the plustek backend any more. See http://www.linuxprinting.org/till/tmp/sane-1.0.16-epson-1260-debug-20050813.txt This is the output of SANE_DEBUG_PLUSTEK=255 scanimage -L lsusb -vvv sane-find-scanner Till
[sane-devel] Olivetti Job_Jet M400 sane support
Oi, Christian, I am forwarding this to the HPLIP developer team at HP. Dave, Shiyun, would it be possible to let HPLIP also support the OEM/rebadged devices like the Olivetti job_jet series? AFAIR it supports also Apollo and this Sony MF device. I will forward you the rest of the thread in a separate e-mail. Till Christian Gruber wrote: Hi! is there a way of adding support for the jobjet m400 all-in-one device from olivetti? It?s an oem from the hp officejet 6110. the only differnce is the usb vendor- and model-id. lG Christian -- Christian Gruber c...@chilia.com (gpg-ID: 1019E9AD) www.mindestens.net/contacts/cg.html Phone: +43/(0)676 507 507 5 Fax: +43/(0)820 55585 3002
[sane-devel] Epson Perfection 1260 Photo does not work with SANE 1.0.16
Henning Meier-Geinitz wrote: Hi, On Sat, Aug 13, 2005 at 09:14:13PM +0200, Till Kamppeter wrote: Oi, after upgrading to SANE 1.0.16 the Epson Perfection 1260 Photo is not recognized by the plustek backend any more. See The important part is: [plustek] sanei_access_lock failed: 11 Maybe you don't have the necessary permissions for the lock? You can also disable locking during the configure run. export SANE_DEBUG_SANEI_ACCESS=255 should show some more details. Search this list for more details. Bye, Henning Thank you very much. I got it working now. What was missing was the directory for the lock files. After doing mkdir -p /var/lib/lock/sane/ the scanner is found. So the bug is that make install does not create this directory. Till
[sane-devel] Kyocera FS-1118 MFP
David, Markus, any chance here? Till Rainer Bendig aka Ny wrote: Hi, does anyone know if the scanner of the multi-function-printer Kyocera FS-1118 MFP works with sane? Kyocera said nothing in replies to my mails :-( Greetings, Rainer
[sane-devel] IScan 1.14.0 startup delay, not working Perf 2450, not compiling on Mandriva LE2005/gcc 3.4.3
libusb: 0.1.8 kernel: 2.6.11 I am trying to get an Epson Perfection 2450 and 4180 to work on the distro mentioned in the subject. At first I tried /home/test/iscan-1.14.0-3.i386.rpm, but iscan had a long delay to start up with both with the Perfection 4180 and 2450 Photo. The 4180 actually worked, once the iscan window was open. Also multiple page scanning with the pages initiated by the scanner's button works. The 2450 did not work. Here the debug output for the 2450 Photo (in epkowa.conf only usb line is active, in dll.conf epson, plustek, and snapscan are commented out): - [test@majax ~]$ SANE_DEBUG_EPKOWA=255 iscan [sanei_debug] Setting debug level of epkowa to 255. [epkowa] sane_init: iscan 1.14.0 [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.14.0 - 2005-02-18 [epkowa] attach(, 3) [epkowa] attach: opening [epkowa] attach_one_usb(libusb:001:086) [epkowa] SANE EPKOWA Backend 1.14.0 - 2005-02-18 [epkowa] attach(libusb:001:086, 3) [epkowa] attach: opening libusb:001:086 [epkowa] Found valid EPSON scanner: 0x4b8/0x112 (vendorID/productID) [epkowa] send buf, size = 2 [epkowa] buf[0] 1b . [epkowa] buf[1] 40 @ [epkowa] receive buf, expected = 1, got = 0 [epkowa] get_identity_information() [epkowa] send buf, size = 2 [epkowa] buf[0] 1b . [epkowa] buf[1] 49 I [epkowa] receive buf, expected = 4, got = 4 [epkowa] buf[0] 02 . [epkowa] buf[1] 12 . [epkowa] buf[2] 6a j [epkowa] buf[3] 00 . [epkowa] code 02 [epkowa] status 12 [epkowa] count 106 [epkowa] receive buf, expected = 106, got = 106 [epkowa] buf[0] 42 B [epkowa] buf[1] 38 8 [epkowa] buf[2] 52 R [epkowa] buf[3] 32 2 [epkowa] buf[4] 00 . [epkowa] buf[5] 52 R [epkowa] buf[6] 3c [epkowa] buf[7] 00 . [epkowa] buf[8] 52 R [epkowa] buf[9] 48 H [epkowa] buf[10] 00 . [epkowa] buf[11] 52 R [epkowa] buf[12] 4b K [epkowa] buf[13] 00 . [epkowa] buf[14] 52 R [epkowa] buf[15] 50 P [epkowa] buf[16] 00 . [epkowa] buf[17] 52 R [epkowa] buf[18] 5a Z [epkowa] buf[19] 00 . [epkowa] buf[20] 52 R [epkowa] buf[21] 64 d [epkowa] buf[22] 00 . [epkowa] buf[23] 52 R [epkowa] buf[24] 78 x [epkowa] buf[25] 00 . [epkowa] buf[26] 52 R [epkowa] buf[27] 85 . [epkowa] buf[28] 00 . [epkowa] buf[29] 52 R [epkowa] buf[30] 90 . [epkowa] buf[31] 00 . [epkowa] buf[32] 52 R [epkowa] buf[33] 96 . [epkowa] buf[34] 00 . [epkowa] buf[35] 52 R [epkowa] buf[36] a0 . [epkowa] buf[37] 00 . [epkowa] buf[38] 52 R [epkowa] buf[39] af . [epkowa] buf[40] 00 . [epkowa] buf[41] 52 R [epkowa] buf[42] b4 . [epkowa] buf[43] 00 . [epkowa] buf[44] 52 R [epkowa] buf[45] c8 . [epkowa] buf[46] 00 . [epkowa] buf[47] 52 R [epkowa] buf[48] d8 . [epkowa] buf[49] 00 . [epkowa] buf[50] 52 R [epkowa] buf[51] f0 . [epkowa] buf[52] 00 . [epkowa] buf[53] 52 R [epkowa] buf[54] 0a . [epkowa] buf[55] 01 . [epkowa] buf[56] 52 R [epkowa] buf[57] 2c , [epkowa] buf[58] 01 . [epkowa] buf[59] 52 R [epkowa] buf[60] 40 @ [epkowa] buf[61] 01 . [epkowa] buf[62] 52 R [epkowa] buf[63] 5e ^ [epkowa] buf[64] 01 . [epkowa] buf[65] 52 R [epkowa] buf[66] 68 h [epkowa] buf[67] 01 . [epkowa] buf[68] 52 R [epkowa] buf[69] 90 . [epkowa] buf[70] 01 . [epkowa] buf[71] 52 R [epkowa] buf[72] e0 . [epkowa] buf[73] 01 . [epkowa] buf[74] 52 R [epkowa] buf[75] 58 X [epkowa] buf[76] 02 .
[sane-devel] Epson 2480 Transparency-Adapter?
Jaroslaw Gorny wrote: Hmmm. Bad luck. My parents got 2580. I'm going to 'borrow' it. Is there any chance to enable this motor? Or at least some tips where to start??? If it is possible to have it working but nobody is interested, maybe I could try To be true I'm interested _only_ in scanning transparent materials, so this function is _very_ important for me... To get your 2580 at least to work as a normal flatbed scanner for non-transparent documents and photos, simply unplug the cable of the lid. The lower part of your scanner is identical to the 2480. And with the lid not being plugged it works. Till
Please remove hpusbscsi Was: [sane-devel] HP 7450C, hpusbscsi, permissions in Fedora Core 3
I have reported this to our Mandrakesoft kernel guys, so next Mandrakelinux version (10.2) should not have this problem any more. http://qa.mandrakesoft.com/show_bug.cgi?id=12891 For now, simply remove or rename the module on your system. Till Rene Rebe wrote: Hi, we should remove hpusbscsi from the Kernel. It is long obsolete and very unstable. I can send a patch for 2.4 and 2.6 (if needed) ;-) George Garvey wrote: On Sat, Jan 01, 2005 at 10:11:30PM -0800, Thomas Frayne wrote: ... As far as I know, Rene has made it pretty clear he doesn't want to use hpusbscsi with the avision driver. He prefers libusb. Yes. Hpusbscsi has many drawbacks. The major ones are: - does not work with new scanners (that are designed for USB 2.0) - it is highly instable (e.g. during an i/o error it locks up quite easily and leaves the (usb sub-)system in a state that needs a reboot ... The later problem made me add the user-space i/o code to the SANE/Avision backend, because I had to reboot my system every 5 minutes during development ... Yours,
[sane-devel] Epson 2480 Transparency-Adapter?
I have also reported about this scanner in a longer thread earlier on this list and found out that it works. What does not work is the motorized transparency unit of the 2580. Till Jaroslaw Gorny wrote: On Tue, 04 Jan 2005 20:42:29 +0100 Julien BLACHE j...@jblache.org wrote: Reinald Kirchner reinald.kirch...@qbcl.de wrote: is there any chance, to get the transparency-adaptor of the mentioned scanner working? Would it be of any help to post debug-output to the list? It works out of the box, AFAIK. Hmmm. so why it is still on 'unsupported' list?? http://www.sane-project.org/unsupported/epson-perfection-2480-photo.html Yours,
[sane-devel] Device IDs for Epson MF devices
Oi, here are some device IDs, both are MF devices which work with the epson backend: epson cx 6400: 0x04b8 0x0805 epson cx 3650: 0x04b8 0x080e Till
[sane-devel] USB Epson Perfection 1250: sane_start: Device busy
Julien BLACHE wrote: Tim Waugh twa...@redhat.com wrote: Well this still seems to be affecting 1.0.15 even with the epson backend change. Commenting out the epson line in dll.conf makes things work; they don't work if the line is uncommented. Can you give us the USB IDs of your scanner ? JB. Here are the USB IDs of the Perfection 1260: -- [root@majax dbus]# lsusb Bus 001 Device 039: ID 04b8:011d Seiko Epson Corp. Perfection 1260 Photo ... -- This model is also driven by the plustek driver and should not appear in the epson driver, like the 1250. I have checked now, with our Cooker package of SANE 1.0.15 the Perfection 1260 works without problems. No patches applied to epson and both epson and plustek are active in dll.conf. I do not have a 1250 for testing. Till
[sane-devel] USB Epson Perfection 1250: sane_start: Device busy
During some period of time around SANE 1.0.14 the Epson Perfection 1250 and 1260 where accidentally entered as supported models in the epson backend, so the epson backend was hanging on them and so the plustek backend, which really supports them, could not access them any more. So the quick solution is commenting out epson in the /etc/sane.d/dll.conf, the correct solution is removing the appropriate entries in the source code of the epson backend. Till Tim Waugh wrote: I've had a report that with sane-backends 1.0.14 and 1.0.15, SANE applications are giving this error when trying to scan with a USB Epson Perfection 1250: sane_start: Device busy Logs with SANEI_DEBUG_ variables set can be found here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140248 It isn't a permissions problem: the /proc/bus/usb node is opened without problem. This part of the debug output might be relevant: [sanei_usb] sanei_usb_get_vendor_product: device 0: vendorID: 0x04b8, productID: 0x010f [sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes [sanei_usb] : 1B 40 .@.. [sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes [sanei_usb] sanei_usb_read_bulk: trying to read 1 bytes USB error: error reading from bulk endpoint 0x82: Connection timed out [sanei_usb] sanei_usb_read_bulk: read failed: Connection timed out [sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes [sanei_usb] : 1B 49 .I.. [sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes [sanei_usb] sanei_usb_read_bulk: trying to read 4 bytes USB error: error reading from bulk endpoint 0x82: Connection timed out [sanei_usb] sanei_usb_read_bulk: read failed: Connection timed out Any ideas? Tim. */
[sane-devel] I have the Epson Perfection 2480 and 2580 for testing
Oliver Schwartz wrote: On Wednesday 20 October 2004 02.00, Till Kamppeter wrote: Oliver Schwartz wrote: The delays are annoying, but it seems that all delays are requested by the scanner. You can try to reduce the number of retries for the test_unit_ready in snapscan-scsi.c, line 1008 and see if that works any better. Would this really help? The scanners are USB scanners and not SCSI scanners. Yes - some of routines in snapscan-scsi.c are used for usb as well. /Oliver I tried reducing the retries now, but nothing changed. -- [root@majax s]# xsane [4] 28629 [root@majax s]# [snapscan] Scanner warming up - waiting 4 seconds. [snapscan] Scanner warming up - waiting 33 seconds. [snapscan] Scanner warming up - waiting 30 seconds. [4]+ Donexsane [root@majax s]# -- Till
[sane-devel] I have the Epson Perfection 2480 and 2580 for testing
Oliver Schwartz wrote: Hi, Why does the frontend want to set the gray gamma table to (nil)? [snapscan] sane_snapscan_control_option (0x823a6b0, 24, 1, (nil), 0xbfffdffc) Maybe I don't understand something here but that looks strange. This seems to cause the crash (which is not that surprising). For some reason the frontend passes an invalid pointer. I have tried now with xscanimage and have interesting results: The 2480 and 2580 consist of a lower part with the glass and scanning head and a lid with the transparency unit. The lower parts of both are absolutely identical, including the USB vendor/product IDs. The difference between the 2480 and 2580 is made up by the lids. The lid of the 2480 has a simple light which is turned on in transparency mode. You insert the film or slides in a special frame and put this on the glass, so film or slide are placed under the light and parallel to the scanner's borders. The 2580 has an automatic film feeder. You remove the white background from the inner side of the lid, close the lid and open a little door on the upper side of the lid. There you insert a piece of 35-mm film and the scanner pulls it in automatically. For slides there is a frame for the scanner glass again, but a different one. In principle the scanners work with SANE and the snapscan driver, but there are some problems: - You need the scanner's firmware, as for all scanners used with the snapscan driver. - There are long delays between starting the scanner software and the GUI opening or the scan beginning. Messages like [snapscan] Scanner warming up - waiting 33 seconds appear on the console from where the scanning frontend was started. - The biggest problem is that the USB device address (like libusb:001:015) changes when the firmware is uploaded, it seems that after the upload the scanner is disconnected and then reconnected and so it gets a new ID. This means that the very first start of a frontend (after connecting/turning on the scanner) lets the GUI open, but trying to preview of to scan gives Invalid argument. Comparing the output of lsusb reveals that the USB device address changed at the moment where the firmware upload finished. On subsequent runs of scanning frontends the firmware is not uploaded again and so the address does not change. So one can scan when one closes the frontend and opens it again. Perhaps one should do modifications on the snapscan backend to take the reconnection/address change into account. - The lid of the 2580 is not compatible with SANE. If the lid is in use with any of the two lower parts (2480 and 2580) the preview does not work. The head moves shortly and the preview is a stripy dirty white. Normal scanning does work at least in flatbed mode. Switching to the transparency unit makes the frontend freezing. Both lower parts work without problems when the lid of the 2480 or no lid at all is connected. With the lid of the 2480 one can switch to the transparency unit and scan transparent documets correctly. Without lid the button for the transparency unit simply does not appear. Till Can you try another frontend (e.g. xscanimage)? It may also help to delete any xsane preferences (stored in ~/.sane/xsane IIRC). /Oliver
[sane-devel] I have the Epson Perfection 2480 and 2580 for testing
Oliver Schwartz wrote: Hi, http://www.linuxprinting.org/till/tmp/eps2480debug.log http://www.linuxprinting.org/till/tmp/eps2580debug.log [snapscan] sense_handler: Hardware error. (0x00, 0x04) according to my docs this means scan module locked. You probably didn't remove the transportation lock. For Benq scanners it's a small switch on the bottom side of the scanner. /Oliver Thanks, on the 2480 this was really the case. On the 2580 it was already open. Now I have tried to scan with the 2480 and I was even successful sometimes. When it worked the problem was that there were long delays until the scan to start (command line) or the GUI to appear (xsane). There were console messages like --- [snapscan] Scanner warming up - waiting 9 seconds. [snapscan] Scanner warming up - waiting 33 seconds. [snapscan] Scanner warming up - waiting 9 seconds. [snapscan] Scanner warming up - waiting 33 seconds. --- --- scanimage --test --- worked with the long delays before actual scanning as described above. --- SANE_DEBUG_SNAPSCAN=255 scanimage 1.pnm 2 eps2480_2debug.log --- produced a correct output. 1.pnm was a scan of the full scanning area. Again the long delays. --- SANE_DEBUG_SNAPSCAN=255 xsane eps2480_3debug.log 21 --- Successful run of xsane. Nothing than one pre-scan of the full scanning area was done. In another run of xsane the GUI opened but pre-scanning did not work, real scanning worked then and pre-scanning only bafter the first real scan. On all later attempts I got a segmentation fault when the GUI started to open. The command line was the following: --- SANE_DEBUG_SNAPSCAN=255 xsane eps2480_4debug.log 21 --- Here are the URLs of the debug log files: http://www.linuxprinting.org/till/tmp/eps2480_2debug.log http://www.linuxprinting.org/till/tmp/eps2480_3debug.log http://www.linuxprinting.org/till/tmp/eps2480_4debug.log Till
[sane-devel] I have the Epson Perfection 2480 and 2580 for testing
Till Kamppeter wrote: --- SANE_DEBUG_SNAPSCAN=255 xsane eps2480_3debug.log 21 --- Successful run of xsane. Nothing than one pre-scan of the full scanning area was done. In another run of xsane the GUI opened but pre-scanning did not work, real scanning worked then and pre-scanning only bafter the first real scan. When the pre-scan failed, it said Invalid argument. Till
[sane-devel] I have the Epson Perfection 2480 and 2580 for testing
Oliver Schwartz wrote: It seems the 2580 behaves somewhat different, although it uses the same USB ID. Up to now I have no idea what's going wrong. The log you sent for the 2580 indicates an error in snapscani_usb_open() which is only a small wrapper for sanei_usb_open(). Can you provide logs with SANE_DEBUG_SANEI_USB=255 as well? Here we go: http://www.linuxprinting.org/till/tmp/eps2580debug2.log Coomand line was: SANE_DEBUG_SANEI_USB=255 SANE_DEBUG_SNAPSCAN=255 scanimage 1.pnm 2 eps2580debug2.log 1.pnm had 0 bytes after running this command. Till Now I have tried to scan with the 2480 and I was even successful sometimes. When it worked the problem was that there were long delays until the scan to start (command line) or the GUI to appear (xsane). The delays are annoying, but it seems that all delays are requested by the scanner. You can try to reduce the number of retries for the test_unit_ready in snapscan-scsi.c, line 1008 and see if that works any better. On all later attempts I got a segmentation fault when the GUI started to open. The command line was the following: There's nothing obvious in the log. Can you run xsane in gdb and create a stacktrace (command bt IIRC) after the crash? /Oliver
[sane-devel] I have the Epson Perfection 2480 and 2580 for testing
Oliver Schwartz wrote: The delays are annoying, but it seems that all delays are requested by the scanner. You can try to reduce the number of retries for the test_unit_ready in snapscan-scsi.c, line 1008 and see if that works any better. Would this really help? The scanners are USB scanners and not SCSI scanners. Till
[sane-devel] I have the Epson Perfection 2480 and 2580 for testing
Oliver Schwartz wrote: On all later attempts I got a segmentation fault when the GUI started to open. The command line was the following: There's nothing obvious in the log. Can you run xsane in gdb and create a stacktrace (command bt IIRC) after the crash? /Oliver Here is a stacktrace of a failed scanimage --test: -- [root@majax s]# gdb -c core.21805 /usr/bin/scanimage GNU gdb 6.0-2mdk (Mandrake Linux) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i586-mandrake-linux-gnu...Using host libthread_db library /lib/tls/libthread_db.so.1. Core was generated by `scanimage --test'. Program terminated with signal 11, Segmentation fault. warning: current_sos: Can't read pathname for load map: Input/output error Reading symbols from /usr/lib/libsane.so.1...done. Loaded symbols for /usr/lib/libsane.so.1 Reading symbols from /usr/lib/libusb-0.1.so.4...done. Loaded symbols for /usr/lib/libusb-0.1.so.4 Reading symbols from /lib/libnsl.so.1... Reading symbols from /usr/lib/debug//lib/libnsl-2.3.3.so.debug...done. done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /usr/lib/libjpeg.so.62...done. Loaded symbols for /usr/lib/libjpeg.so.62 Reading symbols from /usr/lib/libieee1284.so.3...done. Loaded symbols for /usr/lib/libieee1284.so.3 Reading symbols from /usr/lib/libgphoto2.so.2...done. Loaded symbols for /usr/lib/libgphoto2.so.2 Reading symbols from /usr/lib/libgphoto2_port.so.0...done. Loaded symbols for /usr/lib/libgphoto2_port.so.0 Reading symbols from /lib/libdl.so.2... Reading symbols from /usr/lib/debug//lib/libdl-2.3.3.so.debug...done. done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /usr/lib/libexif.so.9...done. Loaded symbols for /usr/lib/libexif.so.9 Reading symbols from /lib/tls/libm.so.6... Reading symbols from /usr/lib/debug//lib/tls/libm-2.3.3.so.debug...done. ---Type return to continue, or q return to quit--- done. Loaded symbols for /lib/tls/libm.so.6 Reading symbols from /lib/tls/libc.so.6... Reading symbols from /usr/lib/debug//lib/tls/libc-2.3.3.so.debug...done. done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/lib/sane/libsane-hpaio.so.1...done. Loaded symbols for /usr/lib/sane/libsane-hpaio.so.1 Reading symbols from /usr/lib/libhpip.so.0...done. Loaded symbols for /usr/lib/libhpip.so.0 Reading symbols from /lib/libnss_files.so.2... Reading symbols from /usr/lib/debug//lib/libnss_files-2.3.3.so.debug...done. done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /usr/lib/sane/libsane-hpoj.so.1...done. Loaded symbols for /usr/lib/sane/libsane-hpoj.so.1 Reading symbols from /usr/lib/libptal.so.0...done. Loaded symbols for /usr/lib/libptal.so.0 Reading symbols from /usr/lib/libhpojip.so.0...done. Loaded symbols for /usr/lib/libhpojip.so.0 Reading symbols from /usr/lib/libsnmp.so.5...done. Loaded symbols for /usr/lib/libsnmp.so.5 Reading symbols from /usr/lib/libcrypto.so.0.9.7...done. Loaded symbols for /usr/lib/libcrypto.so.0.9.7 Reading symbols from /usr/lib/sane/libsane-v4l.so.1...done. Loaded symbols for /usr/lib/sane/libsane-v4l.so.1 Reading symbols from /usr/lib/sane/libsane-umax1220u.so.1...done. Loaded symbols for /usr/lib/sane/libsane-umax1220u.so.1 Reading symbols from /usr/lib/sane/libsane-umax.so.1...done. Loaded symbols for /usr/lib/sane/libsane-umax.so.1 Reading symbols from /usr/lib/sane/libsane-u12.so.1...done. Loaded symbols for /usr/lib/sane/libsane-u12.so.1 Reading symbols from /usr/lib/sane/libsane-teco3.so.1...done. Loaded symbols for /usr/lib/sane/libsane-teco3.so.1 Reading symbols from /usr/lib/sane/libsane-teco2.so.1...done. Loaded symbols for /usr/lib/sane/libsane-teco2.so.1 Reading symbols from /usr/lib/sane/libsane-teco1.so.1...done. Loaded symbols for /usr/lib/sane/libsane-teco1.so.1 Reading symbols from /usr/lib/sane/libsane-tamarack.so.1...done. Loaded symbols for /usr/lib/sane/libsane-tamarack.so.1 Reading symbols from /usr/lib/sane/libsane-sp15c.so.1...done. Loaded symbols for /usr/lib/sane/libsane-sp15c.so.1 ---Type return to continue, or q return to quit--- Reading symbols from /usr/lib/sane/libsane-snapscan.so.1...done. Loaded symbols for /usr/lib/sane/libsane-snapscan.so.1 Reading symbols from /usr/lib/sane/libsane-sm3600.so.1...done. Loaded symbols for /usr/lib/sane/libsane-sm3600.so.1 Reading symbols from /usr/lib/sane/libsane-sharp.so.1...done. Loaded symbols for /usr/lib/sane/libsane-sharp.so.1 Reading symbols from /usr/lib/sane/libsane-sceptre.so.1...done. Loaded symbols for /usr/lib/sane/libsane-sceptre.so.1 Reading symbols from
[sane-devel] I have the Epson Perfection 2480 and 2580 for testing
Oliver Schwartz wrote: Hi, Thanks, on the 2480 this was really the case. On the 2580 it was already open. It seems the 2580 behaves somewhat different, although it uses the same USB ID. Up to now I have no idea what's going wrong. The log you sent for the 2580 indicates an error in snapscani_usb_open() which is only a small wrapper for sanei_usb_open(). Can you provide logs with SANE_DEBUG_SANEI_USB=255 as well? Now I have tried to scan with the 2480 and I was even successful sometimes. When it worked the problem was that there were long delays until the scan to start (command line) or the GUI to appear (xsane). The delays are annoying, but it seems that all delays are requested by the scanner. You can try to reduce the number of retries for the test_unit_ready in snapscan-scsi.c, line 1008 and see if that works any better. On all later attempts I got a segmentation fault when the GUI started to open. The command line was the following: There's nothing obvious in the log. Can you run xsane in gdb and create a stacktrace (command bt IIRC) after the crash? /Oliver Here a backtrace fron xsane with the 2480: - [root@majax s]# gdb -c ~/core.10148 /usr/bin/xsane GNU gdb 6.0-2mdk (Mandrake Linux) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i586-mandrake-linux-gnu... (no debugging symbols found)...Using host libthread_db library /lib/tls/libthread_db.so.1. Core was generated by `xsane'. Program terminated with signal 11, Segmentation fault. warning: current_sos: Can't read pathname for load map: Input/output error Reading symbols from /usr/lib/libsane.so.1...done. Loaded symbols for /usr/lib/libsane.so.1 Reading symbols from /usr/lib/libusb-0.1.so.4...done. Loaded symbols for /usr/lib/libusb-0.1.so.4 Reading symbols from /lib/libnsl.so.1... Reading symbols from /usr/lib/debug//lib/libnsl-2.3.3.so.debug...done. done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/tls/libm.so.6... Reading symbols from /usr/lib/debug//lib/tls/libm-2.3.3.so.debug...done. done. Loaded symbols for /lib/tls/libm.so.6 Reading symbols from /usr/lib/libjpeg.so.62...done. Loaded symbols for /usr/lib/libjpeg.so.62 Reading symbols from /usr/lib/libieee1284.so.3...done. Loaded symbols for /usr/lib/libieee1284.so.3 Reading symbols from /usr/lib/libgphoto2.so.2...done. Loaded symbols for /usr/lib/libgphoto2.so.2 Reading symbols from /lib/libdl.so.2... Reading symbols from /usr/lib/debug//lib/libdl-2.3.3.so.debug...done. done. Loaded symbols for /lib/libdl.so.2 ---Type return to continue, or q return to quit--- Reading symbols from /usr/lib/libgtk-x11-2.0.so.0...done. Loaded symbols for /usr/lib/libgtk-x11-2.0.so.0 Reading symbols from /usr/lib/libgdk-x11-2.0.so.0...done. Loaded symbols for /usr/lib/libgdk-x11-2.0.so.0 Reading symbols from /usr/lib/libatk-1.0.so.0...done. Loaded symbols for /usr/lib/libatk-1.0.so.0 Reading symbols from /usr/lib/libgdk_pixbuf-2.0.so.0...done. Loaded symbols for /usr/lib/libgdk_pixbuf-2.0.so.0 Reading symbols from /usr/lib/libpangoxft-1.0.so.0...done. Loaded symbols for /usr/lib/libpangoxft-1.0.so.0 Reading symbols from /usr/lib/libpangox-1.0.so.0...done. Loaded symbols for /usr/lib/libpangox-1.0.so.0 Reading symbols from /usr/lib/libpango-1.0.so.0...done. Loaded symbols for /usr/lib/libpango-1.0.so.0 Reading symbols from /usr/lib/libgobject-2.0.so.0...done. Loaded symbols for /usr/lib/libgobject-2.0.so.0 Reading symbols from /usr/lib/libgmodule-2.0.so.0...done. Loaded symbols for /usr/lib/libgmodule-2.0.so.0 Reading symbols from /usr/lib/libglib-2.0.so.0...done. Loaded symbols for /usr/lib/libglib-2.0.so.0 Reading symbols from /usr/lib/libpng.so.3...done. Loaded symbols for /usr/lib/libpng.so.3 Reading symbols from /usr/lib/libtiff.so.3...done. Loaded symbols for /usr/lib/libtiff.so.3 Reading symbols from /lib/libz.so.1...done. Loaded symbols for /lib/libz.so.1 Reading symbols from /lib/tls/libc.so.6... Reading symbols from /usr/lib/debug//lib/tls/libc-2.3.3.so.debug...done. done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/lib/libgphoto2_port.so.0...done. Loaded symbols for /usr/lib/libgphoto2_port.so.0 Reading symbols from /usr/lib/libexif.so.9...done. Loaded symbols for /usr/lib/libexif.so.9 Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Loaded symbols for /usr/X11R6/lib/libX11.so.6 Reading symbols from /usr/X11R6/lib/libXrandr.so.2...done. Loaded symbols for /usr/X11R6/lib/libXrandr.so.2 Reading symbols from /usr/X11R6/lib/libXi.so.6...done. Loaded symbols for
[sane-devel] I have the Epson Perfection 2480 and 2580 for testing
Impossible, I have installed SANE always by RPM, for a new version I have rebuilt the RPM on the compiling machine and then updated the RPM on my testing machine. Till Oliver Schwartz wrote: Hi, the backtraces are quite obscure. Is there any chance that you have two versions of SANE installed on your system (e.g. one in /usr/lib/sane, another one in /usr/local/lib/sane)? /Oliver
[sane-devel] I have the Epson Perfection 2480 and 2580 for testing
Thank you for the links. The Windows driver packages and so the firmware files are absolutely the same for both the 2480 and the 2580 scanners. Unfortunately, both scanners do not work. I have specified the firmware file in /etc/sane.d/snapscan.conf and scanimage -L confirms that snapscan is the driver in use for both models. I am using sane-backends 1.15-pre1. To get a debug log I executed SANE_DEBUG_SNAPSCAN=255 scanimage 1.pnm 2 eps2580debug.log The log files are http://www.linuxprinting.org/till/tmp/eps2480debug.log http://www.linuxprinting.org/till/tmp/eps2580debug.log Till Karl Heinz Kremer wrote: You can download them from EPSON's web site: http://www.epson.com/cgi-bin/Store/support/supDetail.jsp? BV_UseBVCookie=yesoid=41623infoType=Overview http://www.epson.com/cgi-bin/Store/support/supDetail.jsp? BV_UseBVCookie=yesoid=41624infoType=Overview On Oct 18, 2004, at 2:29 PM, Till Kamppeter wrote: Oi, I got the above-mentioned scanners for some days for testing. Unfortunately without the Windows CDs. Can someone send me the firmware files for them (*.bin) files? The firmware file in Epson's IScan package seems not to work, too old or so. XSane segfaults with it. Thanks. Till -- 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] I have the Epson Perfection 2480 and 2580 for testing
Oi, I got the above-mentioned scanners for some days for testing. Unfortunately without the Windows CDs. Can someone send me the firmware files for them (*.bin) files? The firmware file in Epson's IScan package seems not to work, too old or so. XSane segfaults with it. Thanks. Till
[sane-devel] Problem with epson backend and Epson Perfection 1260 Photo
This is a multi-part message in MIME format. --000108000907070407090503 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Thank you very much, and sorry for the duplicate report. I have fixed the problem now by applying the attached patch to sane-backends 1.0.14. The patch is derived from the CVS (via the cvsweb interface). I have uploaded the fixed sane-backends package as 1.0.14-3mdk to the Mandrakelinux Cooker now. Till gerard klaver wrote: See bugreport 300751 about epson 1250/1260 (plustek) problems with the epson backend. CVS update should do the trick. --000108000907070407090503 Content-Type: text/x-patch; name=sane-backends-1.0.14-epson-backend-no1250-1260.patch Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename=sane-backends-1.0.14-epson-backend-no1250-1260.patch === RCS file: /var/lib/gforge/chroot/cvsroot/sane/sane-backends/backend/epson_usb.c,v retrieving revision 1.9 retrieving revision 1.11 diff -u -r1.9 -r1.11 --- sane-backends/backend/epson_usb.c 2004/04/11 17:16:56 1.9 +++ sane-backends/backend/epson_usb.c 2004/06/13 12:41:00 1.11 @@ -14,19 +14,17 @@ 0x10a, /* GT-8700 / Perfection 1640 */ 0x107, /* ES-2000 / Expression 1600 */ 0x10e, /* ES-2200 / Expression 1680 */ - 0x10f, /* GT-7200 / Perfection 1250 */ 0x110, /* GT-8200 / Perfection 1650 */ 0x112, /* GT-9700 / Perfection 2450 */ 0x116, /* GT-9400 / Perfection 3170 */ 0x11b, /* GT-9300 / Perfection 2400 */ 0x11c, /* GT-9800 / Perfection 3200 */ - 0x11d, /* GT-7300 / Perfection 1260 */ 0x11e, /* GT-8300 / Perfection 1660 */ 0x126, /* ES-7000 / GT-15000 */ 0x128, /* GT-X700 / Perfection 4870 */ 0x801, /* CC-600 / CX-5[1234]00 */ 0x802, /* CC-570 / CX-3[12]00 */ - 0x806, /* PM-A850 */ + 0x806, /* PM-A850 / RX600 */ 0x807, /* RX-500 */ 0x808, /* CX-5400 */ 0/* last entry - this is used for devices that are specified --000108000907070407090503--
[sane-devel] Re: ISCAN 1.10.0 and Mandrakelinux Cooker
Olaf Meeuwissen wrote: You are aware of the ABI changes between gcc 3.3 and 3.4, right? These may lead to trouble using the Perfection 1250/1260 and Perfection 3170 and when linking with libesmod.so. Is it possible to complie iscan and/or the epkowa backend without the non-free libraries (then without support for the Perfection 1250/1260 and 3170)? Once one could compile with gcc 3.4.1 then and second, one could include it in Mandrakelinux, as then one would have totally free software (i would appreciate then if you put out two separate source tarballs, one with free stuff and one with the non-free add-on stuff). Thanks for the patch, expect to see it in an upcoming release (no promises as to what version). I'm still with gcc 3.3. Mandrakelinux 10.1 will come with gcc 3.4.1, so the whole distro will be built with this compiler. As for required development packages, it would be nice if distributors agreed on using the same name ;-) As SANE is version 1.0.14 I have also edited the line V_REV=12 to be V_REV=14 Hmm, it doesn't matter much I guess, but the bits and pieces from sane-backends used by iscan are only at 1.0.12. Personally, I prefer to keep V_REV=12 for that reason. Why are there parts of SANE in iscan/epkowa? It should use thes installed SANE for best compatibility. Does the installation of iscan/epkowa overwrite SANE files and so downdates them from 1.0.14 to 1.0.12? Can this be avoided? Can I perhaps simply manually install the epkowa backend and perhaps the iscan GUI and nothing else of iscan/epkowa? Then I have compiled and installed the package. Unfortunately, ISCAN did not work correctly: 1. scanimage -L shows the Epson Perfection Photo 2450 as working with the epson driver (which is the ISCAN version now). Please don't use the epson backend from iscan. It is outdated (see above). It is unfortunate that the backend/Makefile.in still installs it (as well as libsane!). Note that our rpm.spec only puts the epkowa backend in the rpm. # I've been working on a rewrite of the build infra-structure in my own # time and submitted a patch to pipsnews, but it is low on the priority # list :-( I didn´t know, thought it was somehow hacked by you (better color calibration or so). It was installed by make install. So one should consider it as a bug that make builds it and make install installs it. One can scan with XSane, but only in the usual flatbed mode. When trying to use the TPU, already switching to the TPU freezes XSane for a minute or so. When trying to scan (Preview), XSane freezes for some minutes and then there is an error message, telling that there is a communication problem with the scanner andthe console from which I started XSane appear the messages Could this somehow be related to the USB timeouts reported in http://alioth.debian.org/tracker/index.php?func=detailaid=300830group_id=30186atid=410366 and the thread mentioned? Probably you have seen my other tread on the SANE list today, of the epson backend hanging on the Perfection 1260. It was a bug in the epson backend of SANE 1.0.14 which is fixed on SANE CVS and I have fixed it on the Cooker of Mandrakelinux now. Perhaps there are relations to this. Now I have applied the fix and iscan/epkowa is not installed and the 1260 works with plustek and the 2450 with epson, both installed on the same machine with a fresh Cooker (kernel 2.6.8 final, perhaps this helped, too). [epson] You may have to power on your TPU [epson] Also you may have to restart the Sane frontend. The TPU light does not turn on. When switching back to flatbed mode all works normally again. 2. If the Epson Perfection 1260 Photo is turned on, the epson backend (both the original SANE one and the ISCAN one) hangs for several minutes and then even the also connected Perfection 2450 is not detected. The ISCAN epson backend produces the message The Perfection 1260 is *not* supported by the epson backend. It is only supported by the epkowa and plustek backends. Ditto for the 1250. This was caused by a bug in the epson backend in 1.0.14. See my other thread of today on the SANE list. It is fixed now for the original SANE epson backend in the Mandrakelinux package of SANE and in the SANE CVS. [epson] ident failed on the console where scanimage -L was called. 3. The epkowa backend does not recognize the Epson Perfection 1260 Photo. The scanner is OK, as it works without problems with the plustek backend. Commenting out the plustek backend in dll.conf does also not help for epkowa recognizing the scanner. Configuration: only usb in the epkowa.conf file. Do you have a log of
[sane-devel] LaserJet 3380
Henning Meier-Geinitz wrote: Hi, On Thu, Jun 17, 2004 at 03:56:04PM +0200, Peter Jamriško wrote: I have a problem with HP LaserJet 3380 printer. Hpoj recognized it successfully (as hp_LaserJet_3380), but sane-find-scaner didn't find it at all. Can someone help me with this? Which kind of device is it (USB)? Please show us the output from sane-find-scanner -v -v If the device is detected by the hpoj backend, there is no need for sane-find-scanner. Bye, Henning The LaserJet 3380 is for sure an HPOJ device and so SANE shows it only with scanimage -L, and that only after you have done ptal-init setup and started HPOJ. Till
[sane-devel] hp officejet support
HPOJ is not given up. There will be done bigger changes on its architecture to support more functionality than currently. Therefore there is a longer time without releases. HPIJS is only a filter to convert PostScript (with the help of GhostScript) to PCL or LIDIL. It has nothing to do with bringing the machine into USB packet mode, telling that the following data is a print job, and so on. You probably mis-interpreted the last announcements by HP. They told that David Paschal is not working on the HPOJ development any more and therefore the HPIJS team has overtaken resonsability on the HPOJ project. This does not mean that HPIJS should overtake any functionality of HPOJ or that HPOJ's tasks should go under the responsability of SANE. HPIJS will stay a print filter and HPOJ will stay responsable for the scanning and memory card reading part of HP's MF devices. Till Fetka Mario wrote: how about bringing back the officejet support to the hp backend now that printing on OJ is managed by th hpijs driver there is no need for an extra package for scanning (hpoj not maintained since 0.91) only a suggestion wfg Mario
[sane-devel] Scans of Umax Astraslim completely black
I got the following bug report on Mandrakesoft's bug tracking system http://qa.mandrakesoft.com/show_bug.cgi?id=9128 Mandrakelinux 10.0 uses SANE 1.0.13. Is this problem already known? Till
[sane-devel] Nikon LS-1000 does not work correctly
See http://qa.mandrakesoft.com/show_bug.cgi?id=7775 Till
[sane-devel] Re: How to link the Scan Button of CX3100 to a linux application?
I recommend that you post this on the SANE mailing list (http://www.sane-project.org/), as this is a scanning problem. I am CCing this posting to there. AFAIK noone has written a driver for scanner buttons yet (also not for other scanner models). The scanner probably sends a certain signal through the USB which is caught by a background process under Windows. This process then starts a program to do the scan. The best way to write a similar program under Linux is to use a USB sniffer to analyze how the signal looks like and then write a daemon which listens for such signals. Till Alton Hernandez wrote: Hi, Can anyone tell me how I can link the Scan Button of CX3100 to a Linux application? I believe in the Windows environment, you can just press this button and the printer will scan the document and send it to your application of choice. But in Linux, this button seems to be useless because it does not do anything.
[sane-devel] Sane only available to Super User - Canon FP330P
Matthew Duggan wrote: On Mon, Dec 15, 2003 at 07:22:37PM +1300, Kim L. Mantle wrote: Matthew Many thanks for your advice. I have taken heed of your advice and completed those changes to the canon_pp.conf file and all works sweetly. Tell me though Matthew - is option 2 an option, as such, or can the changes be made in conjunction with Till's suggestion plus your amendment (option 1)? Kind regards Kimbo Hi, Sorry, I should have explained more clearly. Setting up your user to have access to the parport will allow you to access the backend directly without the need for running saned. The changes can be made independently so you can do both if you want. I'd recommend trying both methods, because depending on your hardware setup, xsane through saned may be faster than running xsane directly. Why is X-Sane through saned faster than direct scanner access with X-Sane? Should I modify scannerdrake (scanner setup tool of Mandrake Linux) so that all scanners get configured via saned? Till
[sane-devel] HP ScanJet 4200 backend (hp4200) and SANE 1.0.13
The bug of no HP-4200 scanners being recognized is fixed now. I have tested it on my test box with an Epson Perfection 2450 and an HP PSC 950. I have uploaded a fresh version of sane-backends with this patch to Mandrake's Cooker now. Thanks for the new patch. Till adria...@users.sourceforge.net wrote: Hi, I have tested latest patch and solving the bug that make the hp4200 backed to detect the scanner if any usb scanner was plugged in even if it was not a hp4200. Maybe that one is not really solved but I need somebody's help (Till?) to try out a patched SANE and to tell me if the problem is now solved (if not, a debug trace will be welcomed; I don't own any other usb scanner to test). BTW, can anybody or has anybody tested the backend? You can download it before public release from (this is the latest and updated patch): http://hp4200-backend.sourceforge.net/sane-backends-1.0.13-hp4200-0.4.patch.gz Thanks in advance, Adrian
[sane-devel] [Fwd: Re: [lp.epson] Epson CX5400]
This is a multi-part message in MIME format. --050805020801060101080009 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Here is a user confirmation that the Epson Stylus CX5400 (MF device) scans with the epson backend. Till --050805020801060101080009 Content-Type: message/rfc822; name=Re: [lp.epson] Epson CX5400 Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename=Re: [lp.epson] Epson CX5400 Path: news.linuxprinting.org!not-for-mail From: s...@altered.com (Dimitris) Newsgroups: linuxprinting.epson.general Subject: Re: [lp.epson] Epson CX5400 Date: Mon, 15 Dec 2003 17:09:02 + (UTC) Organization: http://www.linuxprinting.org/ Message-ID: brkpre$bic$1...@poblano.linuxprinting.org References: bqoa9b$khe$1...@poblano.linuxprinting.org NNTP-Posting-Host: poblano.linuxprinting.org X-Trace: poblano.linuxprinting.org 1071508142 11852 127.0.0.1 (15 Dec 2003 17:09:02 GMT) X-Complaints-To: use...@linuxprinting.org NNTP-Posting-Date: Mon, 15 Dec 2003 17:09:02 + (UTC) User-Agent: WebNews/LinuxPrinting.org $Revision: 1.5 $. Xref: news.linuxprinting.org linuxprinting.epson.general:3304 In article bqoa9b$khe$1...@poblano.linuxprinting.org, fred_sand...@hotmail.com (Fred Sanders) writes: I have the Epson Stylus CX5400 working for both printing and scanning. I'm running Fedora Core 1 (2.4.22-1.2129.nptl kernel). I had to add the following entry in my /etc/sane.d/epson.conf file: usb 0x4b8 0x808 Xsane now works for scanning after that fix. I can confirm that this works. My 5400 scans fine once i added the following line in /etc/sane.d/epson.conf usb 0x4b8 0x808 then run: modprobe scanner vendor=0x4b8 product=0x808 that did the trick. i can use xsane, or gimp to scan without any problems. its quite fast too! --050805020801060101080009--
[sane-devel] Sane only available to Super User - Canon FP330P
Proceed as shown on http://www.linuxprinting.org/download/digitalimage/Scanning-as-Normal-User-on-Wierd-Scanner-Mini-HOWTO.txt and your scanner should also work for normal users. Till Kim L. Mantle wrote: I have MandrakeLinux 9.2. For the past month or so I have had great difficulty trying to find out why Xsane would only recognise 'Super User' and not 'Normal User'. I have made sure on each occasion I have re-installed 9.2 that there is only one installation of Sane. I have then installed/upgraded (Sane Backends 1.0.12-5mdk) - also used the version on the Distro's CDs - and then Xsane and also tried it the other way around. But each time I get the message 'No Device found' when using 'Normal User' - yet when I use 'Super User' - bang... in comes Xsane and I am also then able to use Gimp. Via the Konsole I am only able to get any sense out of the scanner by using the commands scanimage -L or -T and xsane by using 'Super User'. When I try to get the same answers with 'Normal User' - I am told that there is no device. All I am wanting to achieve for the installation via DrakeScanner to load in what I require and then for me to use the scanner. When I use 'Super User' Xsane keeps telling me not to use 'Super User' as it is dangerous. Has anyone any solution - I know this same situation exists with other users as the author of Xsane has gone to some lengths to explain things with is various readme files. There has to be a solution surely .. Is it that Sane loads wrong file permissions? Please help me out of this hole I seem to have gotten into. Thanks Kimbo
[sane-devel] HP ScanJet 4200 backend (hp4200) and SANE 1.0.13
Oi, I am packaging SANE 1.0.13 for Mandrake Linux. I want to include the hp4200 backend. For that I have updated the patch from SourceForge (http://sourceforge.net/projects/hp4200-backend) to work with SANE 1.0.13. The updated patch you can find at http://www.linuxprinting.org/till/tmp/sane-backends-1.0.13-hp4200-0.4.patch.bz2 Unfortunately, SANE does not compile any more after applying this patch. I get the following error message: - i586-mandrake-linux-gnu-gcc -c -O2 -fomit-frame-pointer -pipe -march=i586 -mcpu=pentiumpro -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/share -DV_MAJOR=1 -DV_MINOR=0 -I/usr/include/gphoto2 -I/usr/include -DBACKEND_NAME=hp4200 -DLIBDIR=/usr/lib/sane hp4200.c -fPIC -DPIC -o .libs/hp4200.o In file included from hp4200.c:117: ../include/sane/sanei_backend.h:155: error: conflicting types for `Option_Value' hp4200.h:53: error: previous declaration of `Option_Value' hp4200.c: In function `sane_hp4200_init': hp4200.c:2476: warning: unused parameter `authorize' hp4200.c: In function `sane_hp4200_set_io_mode': hp4200.c:3036: warning: unused parameter `h' hp4200.c: In function `sane_hp4200_get_select_fd': hp4200.c:3046: warning: unused parameter `h' hp4200.c:3046: warning: unused parameter `fd' hp4200.c: At top level: hp4200.c:496: warning: `dump_register_cache' defined but not used hp4200.c:652: warning: `compute_datalink_bandwidth' defined but not used make[1]: *** [hp4200.lo] Error 1 make[1]: Leaving directory `/home/tkamppeter/rpm/BUILD/sane-backends-1.0.13/backend' make: *** [all-recursive] Error 1 - Has someone an idea how to fix this? Otherwise support for the HP ScanJet 4200 will get lost in SANE 1.0.13 and also in the next Mandrake release. If there is no solution, I suggest to list the HP ScanJet 4200 in the scanner database as Unsupported again, as it does not work with the current version of SANE. Till
[sane-devel] HP ScanJet 4200 backend (hp4200) and SANE 1.0.13
Thanks for the patch, but it seems to need more adaptation: --- i586-mandrake-linux-gnu-gcc -o gamma4scanimage gamma4scanimage.o -L/usr/lib -lm i586-mandrake-linux-gnu-gcc -c -O2 -fomit-frame-pointer -pipe -march=i586 -mcpu=pentiumpro -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/share -DV_MAJOR=1 -DV_MINOR=0 -I/usr/include/gphoto2 -I/usr/include hp4200offd.c i586-mandrake-linux-gnu-gcc -o hp4200offd hp4200offd.o ../backend/.libs/lm9830.o -L/usr/lib ../sanei/libsanei.a ../sanei/libsanei.a(sanei_usb.o)(.text+0x561): In function `sanei_usb_init': : undefined reference to `usb_init' ../sanei/libsanei.a(sanei_usb.o)(.text+0x573): In function `sanei_usb_init': : undefined reference to `usb_get_busses' ../sanei/libsanei.a(sanei_usb.o)(.text+0x580): In function `sanei_usb_init': : undefined reference to `usb_get_busses' ../sanei/libsanei.a(sanei_usb.o)(.text+0x8a2): In function `sanei_usb_init': : undefined reference to `usb_set_debug' ../sanei/libsanei.a(sanei_usb.o)(.text+0x8ac): In function `sanei_usb_init': : undefined reference to `usb_find_busses' ../sanei/libsanei.a(sanei_usb.o)(.text+0x8b1): In function `sanei_usb_init': : undefined reference to `usb_find_devices' ../sanei/libsanei.a(sanei_usb.o)(.text+0xaa9): In function `sanei_usb_get_vendor_product': : undefined reference to `usb_device' ../sanei/libsanei.a(sanei_usb.o)(.text+0xabf): In function `sanei_usb_get_vendor_product': : undefined reference to `usb_device' ../sanei/libsanei.a(sanei_usb.o)(.text+0xe80): In function `sanei_usb_open': : undefined reference to `usb_open' ../sanei/libsanei.a(sanei_usb.o)(.text+0xe93): In function `sanei_usb_open': : undefined reference to `usb_device' ../sanei/libsanei.a(sanei_usb.o)(.text+0xec9): In function `sanei_usb_open': : undefined reference to `usb_set_configuration' ../sanei/libsanei.a(sanei_usb.o)(.text+0xee6): In function `sanei_usb_open': : undefined reference to `usb_claim_interface' ../sanei/libsanei.a(sanei_usb.o)(.text+0x11b5): In function `sanei_usb_open': : undefined reference to `usb_strerror' ../sanei/libsanei.a(sanei_usb.o)(.text+0x11fc): In function `sanei_usb_open': : undefined reference to `usb_close' ../sanei/libsanei.a(sanei_usb.o)(.text+0x1387): In function `sanei_usb_close': : undefined reference to `usb_release_interface' ../sanei/libsanei.a(sanei_usb.o)(.text+0x1392): In function `sanei_usb_close': : undefined reference to `usb_close' ../sanei/libsanei.a(sanei_usb.o)(.text+0x143d): In function `sanei_usb_read_bulk': : undefined reference to `usb_bulk_read' ../sanei/libsanei.a(sanei_usb.o)(.text+0x159e): In function `sanei_usb_read_bulk': : undefined reference to `usb_clear_halt' ../sanei/libsanei.a(sanei_usb.o)(.text+0x164d): In function `sanei_usb_write_bulk': : undefined reference to `usb_bulk_write' ../sanei/libsanei.a(sanei_usb.o)(.text+0x1777): In function `sanei_usb_write_bulk': : undefined reference to `usb_clear_halt' ../sanei/libsanei.a(sanei_usb.o)(.text+0x1907): In function `sanei_usb_control_msg': : undefined reference to `usb_control_msg' ../sanei/libsanei.a(sanei_usb.o)(.text+0x1910): In function `sanei_usb_control_msg': : undefined reference to `usb_strerror' ../sanei/libsanei.a(sanei_usb.o)(.text+0x1a2e): In function `sanei_usb_read_int': : undefined reference to `usb_bulk_read' ../sanei/libsanei.a(sanei_usb.o)(.text+0x1b74): In function `sanei_usb_read_int': : undefined reference to `usb_clear_halt' collect2: ld returned 1 exit status make[1]: *** [hp4200offd] Error 1 make[1]: Leaving directory `/home/tkamppeter/rpm/BUILD/sane-backends-1.0.13/tools' make: *** [all-recursive] Error 1 --- Till Adrian Perez Jorge wrote: Hi all, After reading this I have also updated the patch for SANE 1.0.13 but until Saturday at the afternoon I can not test it. Can anybody here that owns an hp4200c scanner and is capable of patching and compiling SANE 1.0.13 test this stuff before Saturday? You can download the patch at http://hp4200-backend.sourceforge.net/sane-backends-1.0.13-hp4200-0.4.patch.gz I would love to see the backend integrated into the official SANE distribution to avoid continuous patches after every new SANE relase (SANE releases are much faster than me :P) More support will come after using the scanner again, sorry. Till: thanks for your effort! Till Kamppeter wrote: Oi, I am packaging SANE 1.0.13 for Mandrake Linux. I want to include the hp4200 backend. For that I have updated the patch from SourceForge (http://sourceforge.net/projects/hp4200-backend) to work with SANE 1.0.13. The updated patch you can find at http://www.linuxprinting.org/till/tmp/sane-backends-1.0.13-hp4200-0.4.patch.bz2 Unfortunately, SANE does not compile any more after
[sane-devel] HP ScanJet 4200 backend (hp4200) and SANE 1.0.13
Julien BLACHE wrote: Till Kamppeter till.kamppe...@gmx.net wrote: Thanks for the patch, but it seems to need more adaptation: --- i586-mandrake-linux-gnu-gcc -o gamma4scanimage gamma4scanimage.o -L/usr/lib -lm i586-mandrake-linux-gnu-gcc -c -O2 -fomit-frame-pointer -pipe -march=i586 -mcpu=pentiumpro -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/share -DV_MAJOR=1 -DV_MINOR=0 -I/usr/include/gphoto2 -I/usr/include hp4200offd.c i586-mandrake-linux-gnu-gcc -o hp4200offd hp4200offd.o ../backend/.libs/lm9830.o -L/usr/lib ../sanei/libsanei.a ../sanei/libsanei.a(sanei_usb.o)(.text+0x561): In function `sanei_usb_init': : undefined reference to `usb_init' It needs libusb. Thanks, but I have libusb and the appropriate -devel package installed and the other backends get correctly compiled with libusb. A complete log of my attemt to build an RPM of SANE 1.0.13 (contains the screen output of ./configure and make) you can find on http://www.linuxprinting.org/till/tmp/sane-1.0.13-hp4200-compile.log Till
[sane-devel] HP ScanJet 4200 backend (hp4200) and SANE 1.0.13
Thank you very much. The SANE RPM compiled now, with libusb. So Mandrake 10.0 will have the hp4200 backend and it will get tested as part of the Cooker (development version, approaching the 10.0 release). I by myself cannot test as I don´t have an HP ScanJet 4200. Till Adrian Perez Jorge wrote: Hey! Wait a bit! ;) I did not tested the compilation with libusb support, sorry. I have now tested both: compiling sane with libusb support and without it and you can now download again the corrected patch at the same location: http://hp4200-backend.sourceforge.net/sane-backends-1.0.13-hp4200-0.4.patch.gz Excuse me for the inconveniences. Cheers, Adrian. Till Kamppeter wrote: Julien BLACHE wrote: Till Kamppeter till.kamppe...@gmx.net wrote: Thanks for the patch, but it seems to need more adaptation: --- i586-mandrake-linux-gnu-gcc -o gamma4scanimage gamma4scanimage.o -L/usr/lib -lm i586-mandrake-linux-gnu-gcc -c -O2 -fomit-frame-pointer -pipe -march=i586 -mcpu=pentiumpro -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/share -DV_MAJOR=1 -DV_MINOR=0 -I/usr/include/gphoto2 -I/usr/include hp4200offd.c i586-mandrake-linux-gnu-gcc -o hp4200offd hp4200offd.o ../backend/.libs/lm9830.o -L/usr/lib ../sanei/libsanei.a ../sanei/libsanei.a(sanei_usb.o)(.text+0x561): In function `sanei_usb_init': : undefined reference to `usb_init' It needs libusb. Thanks, but I have libusb and the appropriate -devel package installed and the other backends get correctly compiled with libusb. A complete log of my attemt to build an RPM of SANE 1.0.13 (contains the screen output of ./configure and make) you can find on http://www.linuxprinting.org/till/tmp/sane-1.0.13-hp4200-compile.log Till
[sane-devel] Epson gt-8000 transparency experiment
Bart Buitinga wrote: I think I'll just keep the GT-8000 for the countless things it's good at, and look for a more primitive one for this project. Thank you all for your attention and good luck with your project, Try to get a (used) Epson Perfection 2450 Photo. It has a fixed TPU light in its lid and one can easily remove the lid but keep the TPU light plugged in. So if you have the lid at the side of the scanner with the light side on the table you can scan available light, for example from the photo magnifier. So you do not need to open the scanner or to short-circuit any contacts. Put a screen on the top of the scanner glass (A4-sized plastic sheet or glass diffusing screen) and it should work. Till
[sane-devel] Epson Stylus CX-6400
You can remove the untested marks from the CX-3200 and CX-5200, as I had tested these models with the epson backend already several months ago and they both work. Till Henning Meier-Geinitz wrote: Hi, On Wed, Nov 26, 2003 at 12:03:01PM -0500, Bernie Gardner wrote: Thanks for the reply. I submitted a report to the unsuppo... form. I'll keep playing with as I have time and report an... I've added this scanner to our lists: http://www.sane-project.org/lists/sane-mfgs-cvs.html#EPSON Bye, Henning
[sane-devel] Re: [lp.epson] Epson CX5400
Sorry, as usual, I have used the wrong address. The right address for the SANE mailing list is sane-devel@lists.alioth.debian.org Till Till Kamppeter wrote: Laurent Saint-Michel wrote: The printer is working fine here. I didn't succeed yet for the scan. Can you try at first the epson backend of SANE and if this does not work the plustek backend? Please post your results here and also on the SANE developer's mailing list of http://www.sane-project.org/. Till
[sane-devel] WebCams and SANE
José Alberto Nuñez Aranguren wrote: Hi, I'm looking for a web cam that works with SANE lib. Does it exist? All webcams which are working via video4linux work also with the v4l backend of SANE. Till
[sane-devel] Epson Stylus CX-6400/CX-8400 (was: Please add the following printer ID's)
Does someone know about the scanners of these devices? Do they simply work with the epson backend of SANE as the older CX-... models? Unfortunately, they are not listed on the SANE project site yet. Till Robert Krawitz wrote: Epson Stylus CX-8400 Epson Stylus CX-6400 These are all-in-one devices that I presume (and will update the Gimp-Print databases in 4.2 and 4.3) correspond to the C84 and C64 respectively.
[sane-devel] New bug introduced for Canon LiDE 30
Thanks for the patch. Gerhard, what do you recommand to fix SANE 1.0.12 in Mandrake 9.2 so that the Canon LiDE scanners work? This patch or one of your tarballs as http://www.gjaeger.de/scanner/test/plustek-0.46-TEST1.tar.gz Or can you give me a patch for 1.0.12 which contains all the latest fixes? Till Monty wrote: On Thu, Sep 11, 2003 at 01:08:37PM +0200, Till Kamppeter wrote: Monty wrote: LiDE20 and liDE30 never worked well; the autocal code was broken. I know, I have them. I spent several days debugging the plustek backend for exactly these scanners last month; see CVS (gerhard integrated my patches I believe), or contact me for a Canoscan LiDE patch against vanilla 1.0.12. Can you send me the patch? Gerhard has, I believe, integrated it into his latest Plustek backend download. He may have added additional improvements since I made the patch; you should probably ask him... specifically, I only enabled the patch for CanoScan LiDE (as that's all I had to test) but it likely fixes autocal for a wider array of scanners if you turn it on in the conf file. Gerhard may have correctly identified a larger default set. Regardless, the patch as I originally constructed it is attached. It applies to vanilla 1.0.12. The patch has nothing whatsoever to do with USB communication issues; like I said, I use 1.0.12 happily with USB, but I need a hub to make most USB devices work properly with my box and Linux. It's not specific to SANE; most of my USB devices when not on the hub will work perfectly one week, not at all the next... Monty diff -ruNw sane-backends-1.0.12/backend/canoscan-calibrate.c sane-backends-1.0.12-canoscan/backend/canoscan-calibrate.c --- sane-backends-1.0.12/backend/canoscan-calibrate.c 1969-12-31 19:00:00.0 -0500 +++ sane-backends-1.0.12-canoscan/backend/canoscan-calibrate.c 2003-08-15 01:54:37.0 -0400 @@ -0,0 +1,982 @@ +/*. + * Project : SANE library for Plustek flatbed scanners; canoscan calibration + *. + */ + +/** @file canoscan-calibrate.c + * @brief Calibration routines. + * + * Based on sources acquired from Plustek Inc. and Gerhard Jaeger + * gerh...@gjaeger.de + * + * Current rehash by Monty mo...@xiph.org + * + * The basic premise: The stock Plustek-usbshading.c in the plustek + * driver is effectively nonfunctional for Canon CanoScan scanners. + * These scanners rely heavily on all calibration steps, especially + * fine white, to produce acceptible scan results. However, to make + * autocalibration work and make it work well involves some + * substantial mucking aobut in code that supports thirty other + * scanners with widely varying characteristics... none of which I own + * or can test. + * + * Therefore, I'm splitting out a few calibration functions I need + * to modify for the CanoScan which allows me to simplify things + * greatly for the CanoScan without worrying about breaking other + * scanners, as well as reuse the vast majority of the Plustek + * driver infrastructure without forking. + * + * History: + * - 0.45m - birth of the file; tested extensively with the LiDE 20 + * + * This file is part of the SANE package. + * + * This program is free software; you can redistribute it and/or + * modify it under the terms of the GNU General Public License as + * published by the Free Software Foundation; either version 2 of the + * License, or (at your option) any later version. + * + * This program is distributed in the hope that it will be useful, but + * WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not, write to the Free Software + * Foundation, Inc., 59 Temple Place - Suite 330, Boston, + * MA 02111-1307, USA. + * + * As a special exception, the authors of SANE give permission for + * additional uses of the libraries contained in this release of SANE. + * + * The exception is that, if you link a SANE library with other files + * to produce an executable, this does not by itself cause the + * resulting executable to be covered by the GNU General Public + * License. Your use of that executable is in no way restricted on + * account of linking the SANE library code into it. + * + * This exception does not, however, invalidate any other reasons why + * the executable file might be covered by the GNU General Public + * License. + * + * If you submit changes to SANE to the maintainers to be included in + * a subsequent release, you agree by submitting the changes
[sane-devel] hp4200 backend detects non-HP scanners as HP ScanJet 4200
Henning Meier-Geinitz wrote: Hi, On Sun, Aug 31, 2003 at 02:04:38PM +0200, Till Kamppeter wrote: Now, within the two days which me original posting needed to arrive on the SANE list, there is more information. See http://qa.mandrakesoft.com/show_bug.cgi?id=4987 Especially also a user with a Mustek ScanExpress 1200 (gt68xx driver) observed this problem. It seems that the hp4200 backend recognizes every scanner on USB as an HP ScanJet 4200. There is a macro NO_AUTODETECT that's used in that code. Maybe it's defined? So NO_AUTODETECT means Do not identify, consider everything on the USB as an HP ScanJet 4200? I have checked, nowhere NO_AUTODETECT is defined and looking onto the compiler output NO_AUTODETECT is not set. Till
[sane-devel] hp4200 backend detects non-HP scanners as HP ScanJet 4200
Now, within the two days which me original posting needed to arrive on the SANE list, there is more information. See http://qa.mandrakesoft.com/show_bug.cgi?id=4987 Especially also a user with a Mustek ScanExpress 1200 (gt68xx driver) observed this problem. It seems that the hp4200 backend recognizes every scanner on USB as an HP ScanJet 4200. Till Till Kamppeter wrote: This is a bug reported by someone with an Epson Perfection 1650 who tested the release candidate 1 of the new Mandrake 9.2: https://qa.mandrakesoft.com/show_bug.cgi?id=4987 For Mandrake 9.2 I have packaged SANE 1.0.12 with hp4200 version 0.4. I can also reproduce the bug with my Epson Perfection 1260 Photo and the same software versions. I have a system with an HP PSC 950 and an Epson Perfection 1260 Photo and I get the following: --- [root@majax g]# sane-find-scanner | grep -v \# found USB scanner (vendor=0x04b8, product=0x011d) at /dev/usb/scanner0 found USB scanner (vendor=0x04b8 [EPSON], product=0x011d [EPSON Scanner]) at libusb:001:115 [root@majax g]# scanimage -L device `hpoj:mlc:usb:PSC_900_Series' is a Hewlett-Packard PSC 900 Series multi-function peripheral device `plustek:/dev/usb/scanner0' is a Epson Perfection 1260/Photo USB flatbed scanner device `hp4200:/dev/usb/scanner0' is a Hewlett-Packard HP-4200 flatbed scanner [root@majax g]# --- and /proc/bus/usb/devices has the following entries --- T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 22/900 us ( 2%), #Int= 2, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=1000 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 7 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0451 ProdID=2077 Rev= 1.00 S: Product=General Purpose USB Hub C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms T: Bus=01 Lev=02 Prnt=02 Port=04 Cnt=01 Dev#=115 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=ff MxPS= 8 #Cfgs= 1 P: Vendor=04b8 ProdID=011d Rev= 1.00 S: Manufacturer=EPSON S: Product=EPSON Scanner C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=usbscanner E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=16ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms T: Bus=01 Lev=02 Prnt=02 Port=05 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=1e11 Rev= 1.00 S: Manufacturer=Hewlett-Packard S: Product=PSC 950xi S: SerialNumber=MY21AC21J6WP C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA I: If#= 0 Alt= 0 #EPs= 3 Cls=07(print) Sub=01 Prot=03 Driver=usblp E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I: If#= 0 Alt= 1 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 0 Alt= 2 #EPs= 1 Cls=07(print) Sub=01 Prot=01 Driver=usblp E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms --- So my Epson Perfection 1260 Photo is detected both as Epson and as HP (/dev/usb/scanner0). If I unload the scanner.o kernel module with rmmod scanner.o my scanners are correctly detected (The HP 4200 disappears, the other two stay). So the problem only happens with access to the scanners via the kernel module but not with user-mode USB access via libusb. This seems for me to be a bug in the hp4200 backend that it recognizes also scanners which use other drivers (and will not necessarily work with hp4200). Or is it safe to not use scanner.o any more at all, for example shipping Mandrake Linux with a kernel without this module or at least adding a line to /etc/modules.conf to suppress automatic loading of the module? Are there really scanners/backends which need scanner.o? What is the advantage of scanner.o vs. libusb? Till ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] hp4200 backend detects non-HP scanners as HP ScanJet 4200
This is a bug reported by someone with an Epson Perfection 1650 who tested the release candidate 1 of the new Mandrake 9.2: https://qa.mandrakesoft.com/show_bug.cgi?id=4987 For Mandrake 9.2 I have packaged SANE 1.0.12 with hp4200 version 0.4. I can also reproduce the bug with my Epson Perfection 1260 Photo and the same software versions. I have a system with an HP PSC 950 and an Epson Perfection 1260 Photo and I get the following: --- [root@majax g]# sane-find-scanner | grep -v \# found USB scanner (vendor=0x04b8, product=0x011d) at /dev/usb/scanner0 found USB scanner (vendor=0x04b8 [EPSON], product=0x011d [EPSON Scanner]) at libusb:001:115 [root@majax g]# scanimage -L device `hpoj:mlc:usb:PSC_900_Series' is a Hewlett-Packard PSC 900 Series multi-function peripheral device `plustek:/dev/usb/scanner0' is a Epson Perfection 1260/Photo USB flatbed scanner device `hp4200:/dev/usb/scanner0' is a Hewlett-Packard HP-4200 flatbed scanner [root@majax g]# --- and /proc/bus/usb/devices has the following entries --- T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 22/900 us ( 2%), #Int= 2, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=1000 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 7 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0451 ProdID=2077 Rev= 1.00 S: Product=General Purpose USB Hub C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms T: Bus=01 Lev=02 Prnt=02 Port=04 Cnt=01 Dev#=115 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=ff MxPS= 8 #Cfgs= 1 P: Vendor=04b8 ProdID=011d Rev= 1.00 S: Manufacturer=EPSON S: Product=EPSON Scanner C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=usbscanner E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=16ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms T: Bus=01 Lev=02 Prnt=02 Port=05 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=1e11 Rev= 1.00 S: Manufacturer=Hewlett-Packard S: Product=PSC 950xi S: SerialNumber=MY21AC21J6WP C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA I: If#= 0 Alt= 0 #EPs= 3 Cls=07(print) Sub=01 Prot=03 Driver=usblp E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I: If#= 0 Alt= 1 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 0 Alt= 2 #EPs= 1 Cls=07(print) Sub=01 Prot=01 Driver=usblp E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms --- So my Epson Perfection 1260 Photo is detected both as Epson and as HP (/dev/usb/scanner0). If I unload the scanner.o kernel module with rmmod scanner.o my scanners are correctly detected (The HP 4200 disappears, the other two stay). So the problem only happens with access to the scanners via the kernel module but not with user-mode USB access via libusb. This seems for me to be a bug in the hp4200 backend that it recognizes also scanners which use other drivers (and will not necessarily work with hp4200). Or is it safe to not use scanner.o any more at all, for example shipping Mandrake Linux with a kernel without this module or at least adding a line to /etc/modules.conf to suppress automatic loading of the module? Are there really scanners/backends which need scanner.o? What is the advantage of scanner.o vs. libusb? Till
[sane-devel] Translation status
Yann E. MORIN wrote:
Good {evening,morning,afternoon} all!
(Sorry Henning for the private mail... Still not used to the reply policy!
;-/)
Once upon a time (on Friday 22 August 2003 20:05), Henning Meier-Geinitz
wrote :
fr Translated : 579 (92.3%)
Here I am again, with an updated .fr.po translation :
Translated : 619 (98.7%)
of which :0 fuzzy ( 0.0%)
Not translated :8 ( 1.3%)
Total : 627
French-aware readers, would some one comment on those translations (not yet
included in the above result), before I submit the file :
Bayer Dither {16,64} - Bayer entrelaçé {16,64}
Dithemap {1,2} - Table d'entrelçage {1,2}
To me, dithering is the same for color-space as halftone is for BW-space.
Am I right? And does that make sense to translate 'dither' (and dithering,
...) as 'entrelaçé'?
Salut,
I am not perfect in french, but 'entrelaçé' is interlaced for me, in
printing also weaving. This means that on one sweep of the print head
not all pixels of the covered area are printed, the next sweep goes over
this area (or a part of it again) to print pixels which were left out
the first time. This is done to get a resolution higher than the
distance between the nozzles, or to make the paper less wet on high ink
densities, or also to reduce stripes of the print head sweeps.
Dithering is something completely different, which is also done by laser
printers. One does dithering to raise the colour depth on the cost of
resolution. A laser has only one bit of native colour depth, inkjets 1
or 2 bits (always per ink/toner colour, usually CMYK or CMYmyK). As
photos have 8 bits of colour depth per colour component of RGB but often
a lower resolution than the printer, one takes a matrix of printer
pixels, for example 4x4, and makes up one photo pixel of them. By
combining different dot patterns in such a matrix the avarage colour
impression of the matrix can have many more different color tones then a
printer pixel.
Unfortunately, I do not know the french word for dithering. Perhaps you
should have a look at the translations of the GIMP-Print package
(http://gimp-print.sf.net/).
Till
[sane-devel] HP PSC 1210
Julien BLACHE wrote: Sebastian 'Frank©' Wieseler franks.h...@arcor.de 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] Help scanner
Your scanner needs its firmware to be loaded before you can scan. If you had a Windows session before your Linux session this had be done already, but if you start with Linux, Linux must do it. See the comments in the file /etc/sane.d/snapscan.conf or enter the command man sane-snapscan for more information. Till palimsesto wrote: Hello! I have problem with my scanner and I hope someone could help me. I installed Mandrake 9.1 and detected all the hardward I have, but when I want work with the scanner it's impossible for me. I get the follow message : snapscan/dev/usb/scanner0...invalid argument. I got this message from Sane and from Gimp to. If I start my computer from win all run perfectly and after I works with Linux any problem, but if I start my computer from Linux I get the message I wrote when I call my scanner or Sane. Don't like this kind of dependence of win, but I don't found any way to solve this. I have read de page of Sane and follow all the steps there I found but my scanner doesn't work. I try with : sane-find-scanner and found perfectly my USB scanner and also with the scanimage -L command and again detected the scanner but still does'nt work. And I hope isn't complicated but I'm working with Linux fifteen days about and enjoy it but this problem Bye! Juan Carlos ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Epson CX5200 not detected with sane-find-scanner
Jeff Courtade wrote: When running this with the official distribution there was no additional output from scanimage -L with export SANE_DEBUG_EPSON=255 set. I installed the available dev snapshot just now. After setting up /etc/sane.d/epson.conf usb /dev/usb/scanner0 now when I set the debug level I get additional output and it detects my scanner This is the output from that Should it be detected as an unknown model? This is absolutely correct, I got this model from Epson for some weeks for testing here to MandrakeSoft and I got it also detected as an unknown model and it scanned perfectly. Also the test page generator under the scanner worked perfectly. Till
[sane-devel] Third revision of Scanner HOWTO available
Major A wrote:
chapter 5.:
saned section: there's no mention at all of the changes required to
net.conf. Also, what's the warning all about? I'd say it's advisable
to run saned as a dedicated user (I usually call it saned), but it's
not a group. Also, once saned is set up properly, _everyone_ has
access to the scanner without requiring root privileges, as long as
their computer is listed in saned.conf.
I didn´t look into the document, but it should be mentioned that with
saned and the net backend acting on one and the same machine as both
client and server parallel scanners which are normally only accessible
by root (e. g. Canon) can be accessed by normal users. Here a Mini-HOWTO:
The problem is that the SANE driver for your scanner accesses the
parallel port directly, without use of the kernel. Such way of device
access is only possible for root. Due to the kernel not being used there
is no special file in /dev or /proc which represents the scanner and
whose permissions can be opened for normal users.
Scanning-as-Normal-User-on-Wierd-Scanner-Mini-HOWTO
---
Original version I presented on MandrakeClub:
http://www.mandrakeclub.com/modules.php?op=modloadname=Splatt_Forumfile=viewtopictopic=5895forum=13
This version can also be used with non-Mandrake distros.
1. Make sure that saned is installed as in some distros it can be in an
extra package (for example in Mandrake, type urpmi saned as root or
use rpmdrake there).
2. Get root and stay root for the next steps. Create or edit
/etc/xinetd.d/saned (we assume xinetd is used as in most modern distros):
# default: off
# description: The sane server accepts requests \
# for network access to a local scanner via the \
# network.
service sane
{
disable = no
port= 6566
socket_type = stream
wait= no
groups = yes
user= root
group = root
server = /usr/sbin/saned
}
It can be already provided by your distro, but probably with
user = saned
group = saned
Make sure that you have
user = root
group = root
Add the line
sane 6566/tcp # SANE Control Port
to /etc/services if your distro didn´t put it there already.
3. Restart xinetd with
service xinetd restart
4. Add a line only containing localhost in both /etc/sane.d/saned.conf
and /etc/sane.d/net.conf. Make sure that in /etc/sane.d/dll.conf is a
line containing only net and a line containing only the name of the
driver for your scanner, both without comment sign (#) in the
beginning. Make also sure that the configuration file for your scanner
driver /etc/sane.d/your scanner´s driver.conf is correctly set up (see
man sane-your scanner´s driver).
Mandrake Linux users can also proceed as follows:
Start Scannerdrake
scannerdrake
and click on Scanner sharing. Mark The scanners on this machine are
available to other computers and Use scanners on remote computers.
Click on Scanner sharing to hosts and in the next window on Add
host. Then choose Name/IP address of host: and type localhost in
the input line. Click OK and Done. Now click Use scanners on hosts:
... and in the dialog appearing Add host. In the next window choose
This machine and click OK. Click Done to get back into the
Scanner sharing and OK to get back into the main window of
Scannerdrake. Now you can close Scannerdrake.
5. Run X-Sane (or your preferred frontend) as normal user and you should
be able to scan. Please report here whether it really works.
6. You can still share your scanner on a network, simply add the
addresses of the clients to your /etc/sane.d/saned.conf file.
How does this work?
We use the network scanning facility of SANE, but our network consists
of only one machine, the machine where your parallel scanner is
connected to. You do not need a network card for it. Linux has a virtual
network consisting of only the local machine which is used when your
machine is called with the name localhost or the IP address 127.0.0.1.
So the server and the client are on the same machine. The server is the
saned which you have installed in step (1). It calls the scanner
driver and communicates with the scanner. To make this possible you let
it run with root privileges. This you have configured in step (2) and
(3). In step (4) you have told that the local machine and no other
machine can access to your scanner (/etc/sane.d/saned.conf or
scannerdrake's Scanner sharing to hosts: button) and that locally
started scanning software should search for scanner servers on the local
machine (/etc/sane.d/net.conf or scannerdrake's Use the scanners on
hosts: button). The client is the X-Sane running as a normal user,
started in step (5). It searches for local scanners where a normal user
has access to and for remote scanners. In your case it searches only on
the local machine and finds the saned providing your
[sane-devel] xsane cutting off part of scan
You should also post on the HPOJ mailing list (see http://hpoj.sf.net/) so that the developers of HPOJ, the actual driver for this device, see your report. Till Scott Savarese wrote: I have an HP PSC 2210 printer working with xsane. I have it scanning, but I am having a problem scanning full size papers. If a page is 8.5x11 inches, it only scans the left 8 inches cutting off the right .5 inches. Is there a way to fix this? Let me know what information you need to help. I can send my xsanerc and the printer config file if you'd like.
[sane-devel] PATCH: XSane hardcodes Netscape as browser
Oliver Rauch wrote: Hello Tim. My name is Till. You can enter a html viewer in xsane-preferences-setup-display. There is no need to patch xsane. Thank you for the info. A suggestion: One could add a checkbox automatic and when it is checked, the BROWSER variable is used and if the BROWSER variable is not set, the most common browsers are tried (netscape, mozilla, konqueror, galeon, opera). Till Oliver On Thursday 03 July 2003 19:06, Till Kamppeter wrote: Oi, for displaying HTML help pages XSane calls always the web browser Netscape and does not try another browser if Netscape is not installed. As newer distros do not ship Netscape any more (or they ship it only in boxed editions) it is often not possible to call the help pages out of XSane. Daouda Lo from MandrakeSoft (daouda at mandrakesoft dot com) has made a patch (for XSane 0.91) to use the BROWSER environment variable which we use in Mandrake Linux from now on as long as the problem is not solved upstream. I have made the patch available here http://www.linuxprinting.org/till/tmp/xsane-0.91-browser.patch.bz2 Oliver, can you apply it to XSane, so that the browser problem will be solved in 0.92? Thanks in advance. Till ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Second draft of Scanner HOWTO for TLDP
Howard Shane wrote: I've visited the libusb site, and the only documentation available seems to be for developers. If someone can point me to more user-oriented information I'll be happy to include it. I assume it's out of the beta phase? Are there distribution manufacturers including it in their stable branches of binaries? Mandrake contains libusb since 9.0 or so. SANE and libgphoto2 of Mandrake Linux 9.1 are compiled with libusb support. To use libusb with binary packages, the libusb* package has to be installed with urpmi libusb For compiling programs using libusb you need also the libusb*-devel package which can be installed with urpmi libusb-devel I don´t have info about other distros (I work as developer at MandrakeSoft), but if Debian ships libusb my guess is that one installs it with apt-get install libusb apt-get install libusb-dev I hope this helps. Till
[sane-devel] Exif informations
Is the device which you are using really a scanner?
If it is a locally (USB, SCSI, parallel, ISA or PCI card) scanner and
the Windows driver gives you the possibility to save the scanned image
as a JPEG with EXIF info, the EXIF info is most probably generated by
the Windows driver, as local scanners usually send raw image data over
the wire. In this case it would be an idea of enhancement for SANE or
its frontends to save info about the image and or applied correction
operations in an EXIF header when saving the image as JPEG.
If it is a network-connected high-end multi-function device (usually
based on an office copy machine) which allows the user to download scans
as JPEG files via a web interface, FTP, or e-mail you can apply
libexif-based tools on the JPEG files as soon as they are onm your hard
disk, see below about these tools.
If your device is a digital camera (or the small HP PhotoSmart scanner
which scans onto a photo memory card) the camera´s firmware stores the
camera settings in an EXIF haeder when you let the camera save the photo
as JPEG on the memory card. Use gtkam (gphoto2 frontend with remote
control feature, http://www.gphoto.org/) or the buttons of the camera to
take the photos, then they get saved on the card. If there is a driver
for SANE to take or download photos (does this exist?) it is possible
that you get the image as raw data, without EXIF header (as from a local
scanner). Download the photos via USB mass storage or gphoto2. Then use
libexif-base tools for reading and editing the EXIF headers.
libexif and the exif (command line) and gexif (graphical) frontends
you can find in many distros or on
http://sourceforge.net/projects/libexif. In addition, gtkam, gphoto2,
flphoto (http://www.easysw.com/~mike/flphoto/), and several web album
systems support EXIF (when compiled with libexif).
Till
Georges Roux wrote:
Yes like this:
EXIF tags in 'IMG002.jpg' ('Intel' byte order):
+--
Tag
|Value
+--
Manufacturer
|Nikon
x-Resolution
|2900/1
y-Resolution
|2900/1
Resolution Unit
|Inch
Date and Time |2003.05.17
22.38.02
YCbCr Positioning
|centered
Exif Version|Exif Version
2.1
ComponentsConfigurat|Y Cb Cr
-
Maker Note |32 bytes unknown
data
FlashPixVersion |FlashPix Version
1.0
Color Space
|sRGB
PixelXDimension
|3979
PixelYDimension
|2674
+--
to have some informations about parameters, date...
Georges
Henning Meier-Geinitz wrote:
Hi,
On Sat, May 17, 2003 at 05:44:25PM +0200, Georges Roux wrote:
Is it possible to have Exif, supported in a next release?
Can you give some more details? Do you want the frontends to output
the images as exif? For XSane?
[sane-devel] net/saned problems with EPSON backend
Henning Meier-Geinitz wrote: Hi, On Wed, May 14, 2003 at 07:27:55AM -0400, k...@khk.net wrote: Yes, I've received one report about this. I don't remember which scanner was involved, but the symptoms were similar. I guess it's time to learn more about the net backend... Any news about this? Can anyone reproduce the problems with other backends? Tomorrow is code freeze and if there is a wide-spread bug I'd like to fix it. On the other hand there haven't been changes to saned that may have changed such behaviour during the last few releases. So if there is a bug I guess has been sitting there for quite a long time. I have seen this problem (Invalid argument when switching options with XSane on client box), too, but only with XSane. when I use QuiteInSane, all works perfectly. Till
[sane-devel] Re: ppscsi for kernel 2.4
Tim Waugh wrote: I'm afraid I no longer maintain the ppSCSI patch due to lack of time. Will someone else at Red Hat do it or will the patch be removed from the Red Hat kernels? Anyone on the list who wants to overtake the maintainership of this patch so that parallel scanners stay supported under Linux? Tim, can you make a tarball of the web site and the downloadable stuff before you shut down the site, so that it can be moved to a new place? Thank you. Till
[sane-devel] Re: ppscsi for kernel 2.4
Bruno Barberi Gnecco wrote: I read your posts at the sane mailing list. Have you managed to find ppscsi for kernel 2.4? Thanks a lot, Oi, We ship our 2.4.21presomething kernel in Mandrake 9.1 with the ppscsi module. The patch is most probably derived from this patch for kernel 2.5.x: ftp://people.redhat.com/twaugh/patches/linux25 Get the patch which we use from http://www.linuxprinting.org/till/tmp/ppscsi_support_2.4.21.patch it is nearly the same as the original patch from the FTP site mentioned above or from http://www.linuxprinting.org/till/tmp/ppscsi_support_2.5.x.patch Tim, can you perhaps put the patch for kernel 2.4.21 onto your FTP site? Thank you. Bruno, por favor experimente este patch (please test). Please tell also with which kernel version you test. Till
[sane-devel] Re: Scanner 5370Cse
Arnaud de Lorbeau wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 06 March 2003 12:50 pm, you wrote: Arnaud can you post your /etc/sane.d/dll.conf, /etc/sane.d/avision.conf files, only to be sure that there all is correct? Here are the files, Till. - -- Arnaud de Lorbeau - 1024D/BE708FE3 Mandrakesoft S.A. - 43, rue d'Aboukir, 75002 Paris - FRANCE +33 (0) 1 40 41 00 41 - http://www.mandrakelinux.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+Z57JAq8L8r5wj+MRAmdMAJ9McEw2+1/tLrNdVGjd3pUplLvrEQCeMZGW bvmBiC3pi9mDzedN7eHG3Dw= =jUVR -END PGP SIGNATURE- #option disable-gamma-table #option disable-calibration #option old-calibration #option one-calib-only #option force-a4 #option disable-c5-guard scsi AVISION scsi FCPA scsi MINOLTA scsi MITSBISH MCA-S600C scsi MITSBISH MCA-SS600 scsi HP scsi hp /dev/scanner /dev/sg1 # enable the next line if you want to allow access through the network: net abaton agfafocus apple avision artec artec_eplus48u as6e bh canon canon630u #canon_pp coolscan coolscan2 #dc25 #dc210 #dc240 dmc epson fujitsu gt68xx hp hp4200 hpsj5s leo matsushita microtek microtek2 mustek #mustek_pp mustek_usb nec pie pint plustek #pnm qcam ricoh s9036 sceptre sharp sm3600 snapscan sp15c #st400 tamarack teco1 teco2 teco3 #test umax #umax_pp umax1220u v4l viceo # # The following backends are not included in the sane-backends distribution # If you want to use them, download them from their webpages and read their # documentation # # HP OfficeJet backend homepage: http://hpoj.sf.net/ # Uncomment the following line if hpoj is installed: #hpoj niash
[sane-devel] Support for Alcatel Speed Touch ADSL internet scanner?
Oi, I have run sane-find-scanner on a machine with the Alcatel Speed Touch USB ADSL Modem connected: [root@majax root]# sane-find-scanner -q found USB scanner (vendor=0x04b8, product=0x0112) at /dev/usb/scanner0 found USB scanner (vendor=0x04b8, product=0x011d) at /dev/usb/scanner1 found USB scanner (vendor=0x04b8, product=0x0801) at /dev/usb/scanner2 found USB scanner (vendor=0x04b8 [EPSON], product=0x0112 [EPSON Scanner]) at libusb:001:004 found USB scanner (vendor=0x04b8 [EPSON], product=0x011d [EPSON Scanner]) at libusb:001:010 found USB scanner (vendor=0x04b8 [EPSON], product=0x0801 [USB MFP]) at libusb:001:012 found USB scanner (vendor=0x06b9 [ALCATEL], product=0x4061 [Speed Touch USB ]) at libusb:001:013 [root@majax root]# Not only the three connected scanners are listed, but also the Alcatel modem. I didn't know that this device is an internet scanner. In Mandrake Linux this causes the problem that Harddrake lists this device in the scanner sub-directory and users get confused. Perhaps there is a bug in sane-find-scanner which makes the modem recognized as a scanner. Here is the part which this device produces in /proc/bus/usb/devices; -- T: Bus=01 Lev=02 Prnt=02 Port=06 Cnt=06 Dev#= 13 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=06b9 ProdID=4061 Rev= 0.00 S: Manufacturer=ALCATEL S: Product=Speed Touch USB S: SerialNumber=0090D043AD74 C:* #Ifs= 3 Cfg#= 1 Atr=80 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=50ms I: If#= 1 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) I: If#= 1 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=06(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=07(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=87(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 1 Alt= 2 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=06(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms E: Ad=07(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms E: Ad=87(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 1 Alt= 3 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=06(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms E: Ad=07(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms E: Ad=87(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=05(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms E: Ad=85(I) Atr=02(Bulk) MxPS= 8 Ivl=0ms -- lsusb -vvv gives this: -- Bus 001 Device 013: ID 06b9:4061 Alcatel Telecom Speed Touch ISDN Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x06b9 Alcatel Telecom idProduct 0x4061 Speed Touch ISDN bcdDevice0.00 iManufacturer 1 ALCATEL iProduct2 Speed Touch USB iSerial 3 0090D043AD74 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 147 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type none wMaxPacketSize 16 bInterval 50 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 1 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5
[sane-devel] Brother MFC 6800
Fernando Trias wrote: Folks, I've got a Brother MFC 6800 multi-function printer/scanner/fax and plan to do some work on the scanning backend of sane. I already got information from Dmitri Katchalov, who has done a lot of work to decipher the proprietary protocol. I have one question (so far): The USB device provides three interfaces. The first one is the printer and the second one is the scanner. However, I'm having problems with sane even looking at the device. Perhaps I'm misreading the code, but it seems that there are a few problems for this device. First, in sanei_usb_init(), the part that enumerates USB devices with libusb only looks at the first interface, which in the case of this device is the printer (class 7, USB_CLASS_PRINTER), whereas the scanner is on interface 2 and is class 0xff (USB_CLASS_VENDOR_SPECIFIC). Perhaps sane could enumerate the interfaces and test each one? Second, kernel_get_vendor_product() is unable to get the Vendor and Product ids. The calls to ioctl() all fail. So even if I create a link in /dev/usb/scanner (or whatever), I can't get it identified. Any ideas? Try kernel 2.4.21, on the new Epson MF devices (Stylus CX3200/CX5200) there was also the problem that oinly the first device was recognized. This is solved in kernel 2.4.21. See also http://www.linuxprinting.org/show_printer.cgi?recnum=Epson-Stylus_CX3200 http://www.linuxprinting.org/show_printer.cgi?recnum=Epson-Stylus_CX5200 Another question: is there any consumer-oriented multi-function printer/scanner/fax that is supported by sane? All current HPs (PSC, OfficeJet, LaserJet) and Epson (Stylus CX3200/CX5200) are supported in terms of printing, scanning, and photo card access. PC-assisted fax is not supported yet, but it is worked on it. See http://www.linuxprinting.org/printer_list.cgi?make=Epson http://www.linuxprinting.org/printer_list.cgi?make=HP http://hpoj.sf.net/ http://www.linuxprinting.org/show_printer.cgi?recnum=Epson-Stylus_CX3200 http://www.linuxprinting.org/show_printer.cgi?recnum=Epson-Stylus_CX5200 Till
[sane-devel] Fujitsu USB scanner support working!
Can you post a patch which fixes both the fujitsu and the epson backend? Till Ron Cemer wrote: It's definitely a bug. And you're right, it's still not working in the epson module, even when you change the sscanf from %d to %i, so there's probably another bug somewhere. However, when I copied the same code into fujitsu.c, changed the sscanf from %d to %i, and on success (sscanf returns 2) I call sanei_usb_attach_matching_devices(...) [instead of sanei_config_attach_matching_devices], I can now configure my fujitsu scanner using usb 0x04c5 0x1042, and scanimage recognizes the scanner and I am able to scan just fine. My guess is that either sanei_config_attach_matching_devices has a bug, or possibly more likely, it's more appropriate to call sanei_usb_attach_matching_devices, since we know for sure that we're trying to attach a USB device. Till Kamppeter wrote: Henning Meier-Geinitz wrote: I think it's ok. The epson backend checks for usb vendor product and calls sanei_usb_attach_matching_devices if it find such a line. Otherwise it checks for usb and calls attach for the device name. If it's not usb, it calls sanei_config_attach_matching_devices(line, attach_one); Are you sure that the epson backend understands something other than fixed devices? I have tried usb 0x04b8 0x0112 for my Epson Perfection 2450 and the epson backend did not find it. The only way to get this scanner working is to use a fixed address as usb /dev/usb/scanner1 Till ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Fujitsu USB scanner support working!
Thank you for the patch. The epson backend works correctly now. I have
included the patch in the SANE package for Mandrake 9.1.
Till
Ron Cemer wrote:
Sure. Here is the Epson patch. It makes epson.conf work properly with
lines formatted like usb 0x04b8 0x011e (where 0x04b8 is the vendor and
0x011e is the product).
Henning, can you put this into the latest version?
The fujitsu patches are huge, since they also add USB support, and
support for the fi-4220C scanner. I've posted them before, and they are
in the process of being reviewed.
Thanks!
Ron
Till Kamppeter wrote:
Can you post a patch which fixes both the fujitsu and the epson
backend?
Till
--- backend/epson.c.orig 2002-12-31 13:20:33.0 -0800
+++ backend/epson.c 2003-02-15 10:22:52.0 -0800
@@ -1709,16 +1709,6 @@
*/
/*
- * if the config file contains a line usb /dev/usbscanner, then
handle
- * this here and use the USB device from now on.
- */
- if (s-hw-connection == SANE_EPSON_USB)
- {
- /* we have a match for the USB string and adjust the device
name */
- sanei_usb_init();
- }
-
- /*
* if interface is SCSI do an inquiry.
*/
@@ -2215,6 +2205,8 @@
if( version_code != NULL)
*version_code = SANE_VERSION_CODE (V_MAJOR, V_MINOR,
SANE_EPSON_BUILD);
+ sanei_usb_init();
+
/* default to /dev/scanner instead of insisting on config file */
if( (fp = sanei_config_open (EPSON_CONFIG_FILE)))
{
@@ -2231,7 +2223,7 @@
if( !len)
continue; /* ignore empty
lines */
- if (sscanf(line, usb %d %d, vendor, product) == 2)
+ if (sscanf(line, usb %i %i, vendor, product) == 2)
{
sanei_usb_attach_matching_devices(line,
attach_one_usb);
}
[sane-devel] Fujitsu USB scanner support working!
Henning Meier-Geinitz wrote: I think it's ok. The epson backend checks for usb vendor product and calls sanei_usb_attach_matching_devices if it find such a line. Otherwise it checks for usb and calls attach for the device name. If it's not usb, it calls sanei_config_attach_matching_devices(line, attach_one); Are you sure that the epson backend understands something other than fixed devices? I have tried usb 0x04b8 0x0112 for my Epson Perfection 2450 and the epson backend did not find it. The only way to get this scanner working is to use a fixed address as usb /dev/usb/scanner1 Till
[sane-devel] Fujitsu USB scanner support working!
Yes, simply usb works. Can you mention this in the man page and in the comments of the config file? They seem to be untouched since the time before this new feature was introduced. Thank you. Till Karl Heinz Kremer wrote: There is a bug in the backend. YOu have to use decimal value instead of hex values. But for all known scanners (and the 2450 is known in the latest version of the backend) you don't have to specify the vendor / product ID. You can just put a line usb into the config file, and the backend will use libusb to search for all known devices. Karl Heinz Till Kamppeter said: Henning Meier-Geinitz wrote: I think it's ok. The epson backend checks for usb vendor product and calls sanei_usb_attach_matching_devices if it find such a line. Otherwise it checks for usb and calls attach for the device name. If it's not usb, it calls sanei_config_attach_matching_devices(line, attach_one); Are you sure that the epson backend understands something other than fixed devices? I have tried usb 0x04b8 0x0112 for my Epson Perfection 2450 and the epson backend did not find it. The only way to get this scanner working is to use a fixed address as usb /dev/usb/scanner1 Till ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] HP Scanjet 5300c
Is the current code already in SANE 1.0.10 or do I need to update so that we can support the HP Scanjet 5300c with our next Mandrake release? Till Rene Rebe wrote: Hi. The hp5300 should work for a year now ... Could you: a) make sure you have the last SANE/Avision release (for URL see below) b) update to kernel 2.4.20 ? The avision.conf should be plain vanilla - untouched. All enable* or disable* options should NOT be present, or commented out. THEY ARE FOR DEBUG PURPOSES ONLY! The web locations: - SANE/Avision homepage: http://drocklinux.dyndns.org/rene/avision/ - Sourcecode: http://www.rocklinux.org/people/rene/sane/src/ - Patches: http://www.rocklinux.org/people/rene/sane/patches/ - Incremental patches: http://www.rocklinux.org/people/rene/sane/patches/incremental/ - Precompiled binary: http://www.rocklinux.org/people/rene/sane/patches/bin - Possible mirror sites: http://www.rocklinux.de/people/rene/sane/ http://www2.rocklinux.org/people/rene/sane/ On: Tue, 4 Feb 2003 07:08:35 -0500, Adam Ritchie a...@lni.net wrote: Hi all, has anyone got the hp 5300c to work with sane 1.0.9 or 1.0.10? I just recently downloaded, compiled and installed 1.0.10 without any problems. When I try to scan something, it gets about 11 or 12% through the scan and then the scan hangs and about 1 minute later - linux crashes. I am running MDK 8.1, kde 3.0.3, kernel 2.4.18. I am just curious as to what the avision.conf should look like. Scanimage -L finds the scanner no problem at /dev/sg0. Do I need to leave the buffer size at the default of 128k or should that be changed? Oh, by the way the scanner's rev. is 6.0 if that makes any difference or not. I've also so tried some of the suggestions from the man pages but they didn't make any difference. Regards, Adam Ritchie - René -- René Rebe - Europe/Germany/Berlin e-mail: rene.r...@gmx.net, r...@rocklinux.org web: www.rocklinux.org, drocklinux.dyndns.org/rene/ Anyone sending unwanted advertising e-mail to this address will be charged $25 for network traffic and computing time. By extracting my address from this message or its header, you agree to these terms. ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Artec Viewstation AT3 SCSI scanner
Once, do not use printerdrake, as there is a problem with it with some scanners. Proceed as shown on http://www.mandrakeclub.com/modules.php?op=modloadname=Splatt_Forumfile=viewtopictopic=3641forum=13 to update SANE to 1.0.9 (if needed) and to manually set up the scanner. Till Anders Drejer wrote: I am trying to make my Artec Viewstation AT3 scanner work on my Linux Mandrake 9.0. When I try to configure it with ScanDrake it find the scanner, but no driver (but there should be one according to the manual). sane-fins-scanner also finds the scanner (sane-find-scanner: found SCSI scanner ULTIMA AT3 1.60 at device /dev/sg1). Do I have to make some manual configurations or should ScanDrake do the work?
[sane-devel] Epson Perfection 1260 Photo (plustek): TPA/saned problem
Oi, I have freshly compiled and installed SANE 1.0.10 final. I have also rebuilt XSane 0.90 against the current SANE. The scanner I used for the test id the Epson Perfection 1260 Photo with the TPA connected. The config files /etc/sane.d/dll.conf and /etc/sane.d/plustek.conf are the ones as they come with the package. /etc/sane.d/net.conf contains only localhost and /etc/sane.d/saned.conf contains only +. I have started xsane and in the menu I have chosen net:localhost:plustek:libusb:001:007 as the scanner I want to use. When I switch to the desired TPA mode (Normal, Transparency, Negative) there is no problem, but when I have scanned a preview in the Normal mode and then switch the TPA mode I get a little window with the message and the TPA mode is not changed: Failed to set value of option source: Invalid argument I have set SANE_DEBUG_PLUSTEK=255 as I have done this (one preview in normal mode, switch to Transparency, exit) to get this error log: http://www.linuxprinting.org/till/tmp/sane-plustek-debug-20030201-1.txt Doing the same with xscanimage of sane-frontends 1.0.10 there is no problem. I can switch to the TPA and scan with it. It does not matter whether I am root or a normal user, so no permission problem. The behaviour is exactly the same (TPA switching does not work after a scan in S-SANE, but works in xscanimage) when I run a really remote client (server is SANE 1.0.10, client is SANE 1.0.9, both run X-SANE 0.90). There is also no problem when I use the direct, local address of the scanner (plustek:libusb:001:007). Till
[sane-devel] Hewllet Packard 4300c Scanner
You don't need to remove anything as I have already included the NIASH support into the Mandrake packages of SANE beginning from version 1.0.9. DO NOT run scannerdrake. Add a line containing only niash to your /etc/sanbe.d/dll.conf and you are ready to scan. Simply start the scanning program of your choice. Happy scanning. Till Yago wrote: But if I want to remove my SANE packet (is the sane-backends-1.0.9-3.1mdk and sane-frontends-1.0.9-1.1mdk) I need to remove also this software: libsane1-1.0.9-3.1mdk libsane-devel-1.0.9-3.1mdk xsane-0.90-1.1mdk xsane-gimp-0.90-1.1mdk And the dependencies that suppose remove also: kdegraphics-3.0.3-11mdk kdegraphics-devel-3.0.3-11mdk kdevelop-2.1.3-6mdk koffice-1.2-3mdk koffice-devel-1.2-3mdk koffice-i18n-es-1.2-1mdk So I don't know if after to delete all this software I will to use KDE, Koffice and some any other aplications with liasions with that ones. I have a Mandrake 9.0 distro with 2.4.19 Kernel version with the USB module charged at init (UHCI) and the sane-find-scanner returns that: # No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter. found USB scanner (vendor=0x03f0, product=0x0305) at /dev/usb/scanner0 found USB scanner (vendor=0x03f0, product=0x0305) at /dev/usbscanner found USB scanner (vendor=0x03f0, product=0x0305) at /dev/usbscanner0 found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x0305 [Hewlett-Packard ScanJet 4300C]) at libusb:001:002 # A USB device was detected. This program can't be sure if it's really # a scanner. If it is your scanner, it may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Scanners connected to the parallel port or other proprietary ports can't be # detected by this program. I need help and I am new in all that Linux scanner stories . Thanks to all.
[sane-devel] HP 2200 C and sane1.0.10-pre2
Are these fixes in SANE 1.0.10 or have I to update the plustek backend from your site (I make RPMs for SANE 1.0.10 for Mandrake currently). Please answer to the list and in addition to me (to overcome the delay on the list). Till Jaeger, Gerhard wrote: Crazy world!?! I checked pre3 with my HP2200C and found two major bugs in the Plustek backend, that causes too dark pictures on the HP... Fixed them and everything is fine now...
[sane-devel] Canon Lide30: success!
Gerhard Jaeger wrote: some historical stuff ;-) I started the Plustek backend two years ago after receiving a parallelport scanner (OpticPro 9636T). As SANE is rather plattform independent, I only checked in the backend ocde , and not the kernel-mode driver ( as this one is only for various Linux Kernels available) ... This kernel-mode driver, available at my pages on the web, is named pt_drv (PlusTek_DRiVer) and during its' installation it creates the /dev/pt_drv entry... I don't find on your page (http://www.gjaeger.de/scanner/plustek.html). Can you give me an exact URL? Or if you have taken it from your site what alternative to use or where to get it? mknod is used to create device nodes!!! I know what mknod is, I wanted to know with which parameters I have to run mknod to create the device, but when I get the package, I can see it there. Thank you. Till
