[sane-devel] help with Epson 636U debug
Hi all, here's what the response is. setenv SANE_DEBUG_EPSON 255; setenv SANE_DEBUG_SANEI_USB 255; scanimage test.pnm [sanei_debug] Setting debug level of sanei_usb to 255. usb_set_debug: Setting debugging level to 255 (on) usb_os_find_busses: Found 001 usb_os_find_devices: Found USB device at location 0x0f00 usb_os_find_devices: Found 001-05ac-8005-09-00 on 001 at location 0x0f00 usb_os_find_devices: Found USB device at location 0x0f10 usb_os_find_devices: Found 002-04b8-0101-ff-ff on 001 at location 0x0f10 usb_os_open: 04b8:0101 usb_control_msg: 128 6 512 0 0xbfffed48 8 1000 USB error: usb_control_msg(DeviceRequestTO): transaction timed out Unable to get descriptor (-60) usb_os_close: 04b8:0101 usb_os_open: 05ac:8005 usb_os_open(USBDeviceOpenSeize): another process has device opened for exclusive access usb_control_msg: 128 6 512 0 0xbfffed48 8 1000 usb_control_msg: 128 6 512 0 0x301c70 27 1000 usb_os_close: 05ac:8005 [sanei_usb] sanei_usb_init: device 0x05ac/0x8005, interface 0 doesn't look like a scanner (9/9) [sanei_usb] sanei_usb_init: device 0x05ac/0x8005: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x04b8/0x0101 is not configured [sanei_usb] sanei_usb_init: found 0 devices [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0010 [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0030 [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0130 [sanei_debug] Setting debug level of sanei_usb to 255. usb_set_debug: Setting debugging level to 255 (on) [sanei_usb] sanei_usb_init: device 0x05ac/0x8005, interface 0 doesn't look like a scanner (9/9) [sanei_usb] sanei_usb_init: device 0x05ac/0x8005: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x04b8/0x0101 is not configured [sanei_usb] sanei_usb_init: found 0 devices [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0230 [sanei_usb] sanei_usb_open: trying to open device `/dev/usbscanner' [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner' in list [sanei_debug] Setting debug level of sanei_usb to 255. usb_set_debug: Setting debugging level to 255 (on) [sanei_usb] sanei_usb_init: device 0x05ac/0x8005, interface 0 doesn't look like a scanner (9/9) [sanei_usb] sanei_usb_init: device 0x05ac/0x8005: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x04b8/0x0101 is not configured [sanei_usb] sanei_usb_init: found 0 devices [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0001 [sanei_usb] sanei_usb_find_devices: vendor=0x0458, product=0x2004 [sanei_debug] Setting debug level of sanei_usb to 255. usb_set_debug: Setting debugging level to 255 (on) [sanei_usb] sanei_usb_init: device 0x05ac/0x8005, interface 0 doesn't look like a scanner (9/9) [sanei_usb] sanei_usb_init: device 0x05ac/0x8005: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x04b8/0x0101 is not configured [sanei_usb] sanei_usb_init: found 0 devices [sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x1a20 [sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x1a26 [sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x2022 [sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x1a2a [sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x2040 [sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x2060 [sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x207e [sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x20be [sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x20c0 [sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x20b0 [sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x20de [sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x20fc [sanei_usb] sanei_usb_find_devices: vendor=0x04a5, product=0x20fe [sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x0002 [sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x0001 [sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x2061 [sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x2093 [sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x2091 [sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x2095 [sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x2097 [sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x208d [sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x20ff [sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x208f [sanei_usb] sanei_usb_find_devices: vendor=0x06bd, product=0x20fd [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0114 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x011f usb_os_find_busses: Found 001 usb_os_find_devices: Found USB device at location 0x0f00 usb_os_find_devices: Found 001-05ac-8005-09-00 on 001 at location 0x0f00 usb_os_find_devices: Found USB device at location 0x0f10 usb_os_find_devices: Found 002-04b8-0101-ff-ff on 001 at location 0x0f10 [sanei_debug] Setting debug level of
[sane-devel] USB-Scanner Medion 3810 is actually a Medion MD 6190
I'm sorry, by mistake I sent the wrong scanner-name actually it's a Medion MD 6190 Slim 1200 U2 Hi, I'm working with the above mentioned scanner but I can't get it running with SuSE-Linux 9.1. As I could not find support within my distribution I tried to find out which scanner it exactly is with 'sane-find-scanner'. The result was: found USB scanner (vendor=0x0461, product=0x037b) at libusb:001:002 The USB-ID-list on 'www.linux-usb.org/usb.ids' says that it seems to be a Primax sanner but the device number is not mentioned in that section. The command: scanimage -L stated 'No scanners were identified' Does anybody has any solution I could try out? Many thanks for your help -- Georg Halfas georg.hal...@gmx.net
[sane-devel] USB-Scanner Medion 3810 is actually a Medion MD 6190
Hi, regarding the results of our search-engine, which should always be consulted, the scanner is marked as not supported. Sorry, Gerhard On Wednesday 07 July 2004 10:01, Georg Halfas wrote: I'm sorry, by mistake I sent the wrong scanner-name actually it's a Medion MD 6190 Slim 1200 U2 Hi, I'm working with the above mentioned scanner but I can't get it running with SuSE-Linux 9.1. As I could not find support within my distribution I tried to find out which scanner it exactly is with 'sane-find-scanner'. The result was: found USB scanner (vendor=0x0461, product=0x037b) at libusb:001:002 The USB-ID-list on 'www.linux-usb.org/usb.ids' says that it seems to be a Primax sanner but the device number is not mentioned in that section. The command: scanimage -L stated 'No scanners were identified' Does anybody has any solution I could try out? Many thanks for your help
[sane-devel] Epson Perfection 1670 and high resolution
Hi, I have the same problem but already with SANE 1.0.14: gray images obtained from scanner using 1600 dpi (only!) have strange vertical stripes. As for 800 dpi it's ok. That's a different bug then (which I haven't heard of before). It only affects gray images? (i.e. 1600 dpi in color work fine?) There is the same problem not only for gray but for color images also. __ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail
[sane-devel] USB-Scanner Medion 3810 is actually a Medion MD 6190
Am Mi, den 07.07.2004 schrieb Gerhard Jaeger um 10:25: Hi, regarding the results of our search-engine, which should always be consulted, the scanner is marked as not supported. Is there any support in sight. I mean this is a scanner sold by Aldi in Germany at a quite cheap price. So there might be a lot of people having the same problem as I do. Sorry, Gerhard On Wednesday 07 July 2004 10:01, Georg Halfas wrote: I'm sorry, by mistake I sent the wrong scanner-name actually it's a Medion MD 6190 Slim 1200 U2 Hi, I'm working with the above mentioned scanner but I can't get it running with SuSE-Linux 9.1. As I could not find support within my distribution I tried to find out which scanner it exactly is with 'sane-find-scanner'. The result was: found USB scanner (vendor=0x0461, product=0x037b) at libusb:001:002 The USB-ID-list on 'www.linux-usb.org/usb.ids' says that it seems to be a Primax sanner but the device number is not mentioned in that section. The command: scanimage -L stated 'No scanners were identified' Does anybody has any solution I could try out? Many thanks for your help
[sane-devel] discussion: Future of SANE-project
these all sound like good ideas, (other than your points about free vs proprietary software, which i strongly dislike) and it is certainly worth explaining the value of sane to any vendor who will listen. however, your point seems revolve around wanting to supplant twain by building an evangalist organization, and wanting the sane developers to spend time to do it. In case you had not noticed, we often ARE hobbyists. like any other open-source project, if you want something, you should be prepared to do it yourself. 'show me the code' by picking a vendor, figuring out if the backend maintainer has any good contacts, and start talking to the company yourself. allan On Wed, 7 Jul 2004, David N. Paules wrote: Perhaps I misunderstood SANE's goals. From what I've seen, the backends do not dictate what the front-ends look like, only their capability. I don't understand why the bluster about multiple front-ends and more control over the gui. I was under the impression that one sane backend for a device will support multiple applications (front-ends) such as image capture, OCR, digital camera photo image acquisition, video acquisition from a digital camcorder, etc. Besides, the SANE project is open for review/suggestions for enhancement, so why not get some feedback from scanner makers on what makes SANE a non-option for the future? What 'minimum requirements' are missing from the current architecture? I can see your point about GPL'd backends. I agree it is easier to debug and extend them. But here's my point: Do you want to be the one always repairing and fixing scanners to work with SANE? Or do you want all the manufacturers to feel responsible for ensuring SANE compliance? If SANE is architected intelligently (i.e., backwards compliance with older backends), open source backends may not be necessary. The manufacturers will currently see the SANE org as a free resource for reaching other markets they didn't officially target (i.e. the *nix markets). There is no urgency or requirement for them to support SANE just because the project is open source. In fact, that is the number one reason they will NOT be concerned. 'Those hackers at SANE-project.org will make my device compliant with their software. And I don't have to pay for it.' But, if the ultimate goal of SANE is to supplant TWAIN as the standard for accessing image devices, shouldn't more effort be put on making SANE the future standard. This route will cause scanner makers and their support network to conciously choose to either support or not support the new standard. The SANE project's developers should then concentrate on enhancing the architecture, ensure backwards compatibility, create and market compliance badges, create plugins for Adobe products (like existing TWAIN plugins), etc. and not write new backend modules for each new device that comes on the market. Perhaps working examples demonstrating how scanner makers can leverage their investment in TWAIN support while migrating to SANE might be useful for getting scanner makers to take notice of SANE. If an upgrade path was readily shown, techno-geeks at the manufacturer might prefer and sell the SANE idea to managers within the company. Formal propoganda of industry heavyweight support (a consortium of scanner makers and front-end application development houses) on the web-site might make other makers feel the need to join in. Without this kind of direction, I simply see SANE as being a hobbyist-level effort which is why I questioned the future of it. Thanks for listening and answering my questions. Dave Paules Quantum Leap Innovations m. allan noah wrote: it is important to remember that the developers of sane are volunteers just like you. most of us got involved because we had a lame scanner too. we probably dont have time for such evangelism. But if someone was offering sure, sure. i got no problem with someone acting as a liason to hardware vendors. i do this myself with fujitsu. that said, even if someone had the time to run around and convince vendors of the merits of sane, there would be at least two recurring sentiments: 1. sane spec is not complete, cause it does not support various LEDs,buttons or sensors that the manufacturers believe add so much value (and brand distinction) to their products. Proposals to include this have been discussed, possibly input from a manufacture would help. sure, and none of us ever had the time to actually formallize the proposal, let alone get input from manuf. 2. they are going to want more control over the gui so they can do things like show pictures and diagrams of the scanner, which means they are going to write their own front-end half the time. Or repackage existing - under GPL - is this a problem. a
[sane-devel] (no subject)
Hello Cosmin, in June I wrote this message, since this time I was not hearing anything from you. Do you had seen my message? I´m very interested in working together, please seen me a short notice. Many thanks Ronald Hello Cosmin, It's the complete driver. Anything needed to acces the scanner is there. That´s good, that will make it not so difficult. So normally, we will find all parts what we will need in the sources. Do you got also some documentation from Mustek? Yes, I need help, somebody to talk to. I thought I can do it all alone, but I can't. I would really like you ground. What do you think? Yes, I will need all informations. Then we will talk about the same things. Do you think it will be possible to get the same as you have? Can you ask them? Normally I have some time in the evening for programming, not much, because Iôm alone with my 4 year old kid. Send him all the best from me :) Many thanks. Do you have a step list for what has to be done, to get this into sane working? But I think first of all, we must get the check-usb-chip program working correctly for the scanner. Ronald -- Ronald Humphries ro...@gmx.de
[sane-devel] discussion: Future of SANE-project
m. allan noah wrote: do it. In case you had not noticed, we often ARE hobbyists. like any other open-source project, if you want something, you should be prepared to do it yourself. 'show me the code' by picking a vendor, figuring out if the backend maintainer has any good contacts, and start talking to the company yourself. I agree. But, if more people who know about the efforts they can point others in the right direction if they want to evangalize. True, many may want to have others do the work, but usually several people putting in a little time can do more than one putting in a lot of time.
[sane-devel] please help w/Epson 636U and Panther
I'm about to receive a Perfection 636S, which uses the same command set as the 636U. This means that I can (for the first time) actually debug this problem myself. I can assure you that this problem will be fixed in a few weeks. Karl Heinz On Jul 4, 2004, at 4:03 PM, Julien BLACHE wrote: Henning Meier-Geinitz henn...@meier-geinitz.de wrote: Hi, Anyway, make sure that a line containing only usb is in epson.conf. If that's the case, show us the complete log. To make the log shorter, you can disable everything but epson in dll.conf. Support for the Perfection 636U seems to be kind of broken lately, see http://bugs.debian.org/248885, reported 52 days ago (with full debug log from the epson backend). JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org GPG KeyID 0xF5D65169 -- 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
