[sane-devel] I keep receiving mail
Hi, I just checked, brassedoff AT telstra.com is NOT subscribed. However, brassedoff AT bigpond.com IS subscribed. Well, it was, I removed that subscription now. You always must use the same address for unsubscribing as for subscribing. Bye, Henning -Original Message- From: sane-devel-bounces+henning=meier-geinitz...@lists.alioth.debian.org [mailto:sane-devel-bounces+henning=meier-geinitz.de at lists.alioth.debian.org] On Behalf Of elliotj Sent: Freitag, 8. Juni 2007 05:51 To: sane-devel at lists.alioth.debian.org Subject: [sane-devel] I keep receiving mail Hello, Sometime ago I thought I unsubscribed from the sane-devel mailing list. However I still keep getting mail. I tried to unsubscribe again and I received the message below. The message says that I'm not a member of the list but I keep getting mail. Can you please fix this? Regards brassedoff at bigpond.com The results of your email command are provided below. Attached is your original message. - Results: brassedoff at telstra.com is not a member of the sane-devel mailing list - Done. -- 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] SPAM via SANE-Bugs
Hi everybody, Ok, I disabled anonymous posting for now. However, this is not a solution as it prevents the ordinary user from posting bug reports. If I weren't a member of SANE, I wouldn't create an account just for writing a bug report. Please contact the admins at alioth.debian.org for a real solution. SANE is for sure not the only project having this problem. Personally, I got a total of 3 (in words three) spams from the tracking in the last 4 weeks. So there must be some difference? Regards Henning -Original Message- From: sane-devel-bounces+henning=meier-geinitz...@lists.alioth.debian.org [mailto:sane-devel-bounces+henning=meier-geinitz...@lists.alioth.debian.org] On Behalf Of m. allan noah Sent: Donnerstag, 19. April 2007 20:56 To: Mattias Ellert Cc: Gerhard Jaeger; sane-devel@lists.alioth.debian.org Subject: Re: [sane-devel] SPAM via SANE-Bugs On 4/19/07, Mattias Ellert mattias.ell...@tsl.uu.se wrote: 19 apr 2007 kl. 08.39 skrev Gerhard Jaeger: On Mittwoch, 18. April 2007, m. allan noah wrote: then users cannot report bugs without having an alioth account? Hmmm, nope - there should be some kind of guest account or something like use this temporary code to submit a bug report. something that could not easily misused by spam-bots. - Gerhard Any anonymous postings should be stopped ASAP. At the moment I get about 10 spams a day from the SANE bug tracker. Even bugs that have been marked deleted can apparently be used as spam relays. And there seems to be no way to not get mails from bugs you have posted yourself. well, i think we are going to have to get some help here, on of our project admins on alioth will have to change to disallow anonymous posting. henning? allan -- The truth is an offense, but not a sin -- 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] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'saber...@yahoo.com' 2. Manufacturer (e.g. Mustek): 'one touch 9000 usb' 3. Model name (e.g. ScanExpress 1200UB): 'one touch 9000 usb' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x04a7' 6. Product id (e.g. 0x0002): '0x022c' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): '' 9. Data (e.g. sane-find-scanner -v -v): 'This is sane-find-scanner from sane-backends 1.0.18 # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Invalid argument) checking /dev/sg1... failed to open (Invalid argument) checking /dev/sg2... failed to open (Invalid argument) checking /dev/sg3... failed to open (Invalid argument) checking /dev/sg4... failed to open (Invalid argument) checking /dev/sg5... failed to open (Invalid argument) checking /dev/sg6... failed to open (Invalid argument) checking /dev/sg7... failed to open (Invalid argument) checking /dev/sg8... failed to open (Invalid argument) checking /dev/sg9... failed to open (Invalid argument) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Invalid argument) checking /dev/sgc... failed to open (Invalid argument) checking /dev/sgd... failed to open (Invalid argument) checking /dev/sge... failed to open (Invalid argument) checking /dev/sgf... failed to open (Invalid argument) checking /dev/sgg... failed to open (Invalid argument) checking /dev/sgh... failed to open (Invalid argument) checking /dev/sgi... failed to open (Invalid argument) checking /dev/sgj... failed to open (Invalid argument) checking /dev/sgk... failed to open (Invalid argument) checking /dev/sgl... failed to open (Invalid argument) checking /dev/sgm... failed to open (Invalid argument) checking /dev/sgn... failed to open (Invalid argument) checking /dev/sgo... failed to open (Invalid argument) checking /dev/sgp... failed to open (Invalid argument) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument) checking /dev/usbscanner7... failed to open (Invalid argument) checking /dev/usbscanner8... failed to open (Invalid argument) checking /dev/usbscanner9... failed to open (Invalid argument) checking /dev/usbscanner10... failed to open (Invalid argument) checking /dev/usbscanner11...
[sane-devel] Formulardaten
From: cgi-mai...@kundenserver.de To: henn...@meier-geinitz.de Subject: Formulardaten Date: Fri, 02 Feb 2007 03:36:38 +0100 === == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'pma...@verizon.net' 2. Manufacturer (e.g. Mustek): 'microtek' 3. Model name (e.g. ScanExpress 1200UB): 'scanmaker 6000' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): 'microtek lab Inc' 6. Product id (e.g. 0x0002): 'Microtek Scanmaker 6000' 7. Chipset (e.g. lm9831): '???' 8. Comments (e.g. similar to Mustek 1234): 'Using Xandros Desktop Home Edition - Premium Report of unsupported device! No drivers found. Thank you!' 9. Data (e.g. sane-find-scanner -v -v): ''
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'scha...@freenet.de' 2. Manufacturer (e.g. Mustek): 'Microtec' 3. Model name (e.g. ScanExpress 1200UB): 'Scanmaker 3830' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x13D3' 6. Product id (e.g. 0x0002): '0x3206' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): 'scanimage -L device `sm3840:libusb:006:002' is a Microtek ScanMaker 3840 flatbed scanner it works very well.' 9. Data (e.g. sane-find-scanner -v -v): 'device descriptor of 0x13d3/0x3206 at 008:006 bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x13D3 idProduct 0x3206 bcdDevice 0.00 iManufacturer 1 ((null)) iProduct 2 ((null)) iSerialNumber 0 () bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 128 () MaxPower 100 mA interface 0 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass255 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 100 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 1 ms bRefresh 0 bSynchAddress 0 '
[sane-devel] Help needed for unsupported devices list
Hi everybody, I'll be away from home for several months. Therefore I won't be able to access a Unix system nor do any work in CVS. I'll hopefully still have access to email and web, but that's all. Until now, I managed the incoming mails from the form for unsupported scanners: http://www.meier-geinitz.de/tinc?key=rDoQ7lrjformname=adddev I.e. any input given there was sent be email to me. I have now redirected that mails to the sane-devel list. I'll send some examples that I haven't handled until now later. Their subject is Formulardaten (form data). What needs to be done with these reports? 1) Check if the scanner in question is already in our lists (scanner search engine). If yes, check if the report contains any new data (e.g. USB ids, or sane-find-scanner output). If no, ignore report. 2) If the report is about a scanner that is not listed yet, add it to doc/descriptions/unsupported.desc in CVS and add a page in the unsupported directory of the html CVS. This can be done by copying the .template.html to a new name. Add the name to unsupported.desc (see existing files for examples). Commit all files to CVS. The scanner lists should be updated immediately. The search engine is only updated once a day. 3) If the scanner already exists, just add the new data to the exitsing html file in the unsupported directory in html cvs. This takes about 3-10 minutes per Formulardaten mail. About 30% of the reports will be empty or contain crap data. Another 20% will just have the data we already have (I also want to have this scanner supported). I usually don't respond to these reports at all. Maybe one or some people from sane-devel can handle these reports from now on? Ciao, Henning
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'marco1...@tele2.it' 2. Manufacturer (e.g. Mustek): 'hp' 3. Model name (e.g. ScanExpress 1200UB): 'scanjet 3670' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x03f0' 6. Product id (e.g. 0x0002): '0x1405' 7. Chipset (e.g. lm9831): 'GL646_HP' 8. Comments (e.g. similar to Mustek 1234): '' 9. Data (e.g. sane-find-scanner -v -v): ''
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'oav...@bezeqint.net' 2. Manufacturer (e.g. Mustek): 'Lexmark' 3. Model name (e.g. ScanExpress 1200UB): 'X8350' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x043d' 6. Product id (e.g. 0x0002): '0x00b9' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): 'All-in-one printer/scanner. A closed-source binary SDK is available at http://www.lexmark.com/lexmark/sequentialem/home/0,6959,204816596_659668505_0_en,00.html I did not test it with the scanner.' 9. Data (e.g. sane-find-scanner -v -v): '$ sane-find-scanner -v -v device descriptor of 0x043d/0x00b9 at 002:002 bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x043D idProduct 0x00B9 bcdDevice 0.01 iManufacturer 1 ((null)) iProduct 2 ((null)) iSerialNumber 3 ((null)) bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 103 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 6 ((null)) bmAttributes 192 (Self-powered) MaxPower 10 mA interface 0 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass255 bInterfaceSubClass 255 bInterfaceProtocol 255 iInterface 4 ((null)) endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 interface 1 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass7 bInterfaceSubClass 1 bInterfaceProtocol 2 iInterface 5 ((null)) endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 2 (bulk) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x04 (out 0x04) bmAttributes 2 (bulk) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 interface 2 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass8 bInterfaceSubClass 6 bInterfaceProtocol 80 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x85 (in 0x05) bmAttributes 2 (bulk) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x06 (out 0x06) bmAttributes 2 (bulk) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 interface 3 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 3 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass3 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x89 (in 0x09) bmAttributes 3 (interrupt) wMaxPacketSize8 bInterval 16 ms bRefresh 0 bSynchAddress 0 trying to find out which USB chip is used checking for GT-6801 ... this is not a GT-6801 (bDeviceClass = 0) checking for GT-6816 ... this is not a GT-6816 (bcdUSB = 0x200) checking for GT-8911 ... this is not a GT-8911 (check 2, bcdUSB = 0x200) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 0, bInterfaceClass = 255) checking for MA-1015 ... this is not a MA-1015 (bDeviceClass = 0) checking for MA-1509 ... this is not a MA-1509 (bDeviceClass = 0) checking for LM983[1,2,3] ... this is not a LM983x (bcdUSB = 0x200) checking for GL646 ... this is not a GL646 (bDeviceClass = 0, bInterfaceClass = 255) checking for GL646_HP ... this is not a GL646_HP (bDeviceClass = 0, bInterfaceClass = 255) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 0,
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'f...@rens2.com' 2. Manufacturer (e.g. Mustek): 'Lexmark' 3. Model name (e.g. ScanExpress 1200UB): 'X5150' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x043D' 6. Product id (e.g. 0x0002): '0x0065' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): 'Multifunction device. Printing seems to be mostly functional (Not widely tested) by using the Z55 driver from Lexmark.' 9. Data (e.g. sane-find-scanner -v -v): 'This is sane-find-scanner from sane-backends 1.0.18 # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Invalid argument) checking /dev/sg1... failed to open (Invalid argument) checking /dev/sg2... failed to open (Invalid argument) checking /dev/sg3... failed to open (Invalid argument) checking /dev/sg4... failed to open (Invalid argument) checking /dev/sg5... failed to open (Invalid argument) checking /dev/sg6... failed to open (Invalid argument) checking /dev/sg7... failed to open (Invalid argument) checking /dev/sg8... failed to open (Invalid argument) checking /dev/sg9... failed to open (Invalid argument) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Invalid argument) checking /dev/sgc... failed to open (Invalid argument) checking /dev/sgd... failed to open (Invalid argument) checking /dev/sge... failed to open (Invalid argument) checking /dev/sgf... failed to open (Invalid argument) checking /dev/sgg... failed to open (Invalid argument) checking /dev/sgh... failed to open (Invalid argument) checking /dev/sgi... failed to open (Invalid argument) checking /dev/sgj... failed to open (Invalid argument) checking /dev/sgk... failed to open (Invalid argument) checking /dev/sgl... failed to open (Invalid argument) checking /dev/sgm... failed to open (Invalid argument) checking /dev/sgn... failed to open (Invalid argument) checking /dev/sgo... failed to open (Invalid argument) checking /dev/sgp... failed to open (Invalid argument) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument) checking /dev/usbscanner7... failed to open (Invalid argument) checking /dev/usbscanner8... failed to open (Invalid argument) checking /dev/usbscanner9... failed to open (Invalid argument)
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'cslee-s...@cybericom.co.uk' 2. Manufacturer (e.g. Mustek): 'Pacific Image Electronics' 3. Model name (e.g. ScanExpress 1200UB): 'PF3650 Pro3 Film Scanner' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x05e3' 6. Product id (e.g. 0x0002): '0x0143' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): 'Auto Feed film and slide scanner. Switchable USB / Firewire I do not have firewire so can not get details I tried opening it up but it gets too complex and I still need to use this thing. ' 9. Data (e.g. sane-find-scanner -v -v): 'device descriptor of 0x05e3/0x0143 at 003:011 bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 255 bDeviceSubClass 255 bDeviceProtocol 255 bMaxPacketSize0 64 idVendor 0x05E3 idProduct 0x0143 bcdDevice 3.02 iManufacturer 0 () iProduct 0 () iSerialNumber 0 () bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 192 (Self-powered) MaxPower 10 mA interface 0 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass255 bInterfaceSubClass 255 bInterfaceProtocol 255 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 2 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 3 (interrupt) wMaxPacketSize1 bInterval 8 ms bRefresh 0 bSynchAddress 0 '
[sane-devel] SANE2 commitment
Hi, On 2006-12-17 16:43, Gerhard Jaeger wrote: in general I'd say: yes you are right. But on the other hand I don't see any real progress since years regarding SANE2 - so the question is: Stay/stuck on SANE1 w/o any chance to enhance support for recent devices OR start with a standard that has not been finished yet... There is no need to do it only one way. You could write a meta backend (like dll) that connects to a sane2 frontend and translates sane2 api to sane1 and loads sane1 backends. So you'd only update the maintained or new backends to sane2 and let the meta backend do the reast for the old ones. What needs to be done to finish the standard? Is anybody able to point out the open issues? http://www.sane-project.org/sane2/sane2-todo.html And more generally: http://www.sane-project.org/sane2/sane2-todo.html There is already a branch in CVS for SANE2 (see above), it has only the docs, no code yet. Bye, Henning
[sane-devel] SANE2 commitment
Hi, On 2006-12-17 12:49, Gerhard Jaeger wrote: One thing: I'd like to see Hennings opinion here! And we should agree on some version of the SANE2 standard... Unfortunately I'm very busy and can't do any work related to SANE2 in the near future. I'd really appreciate a new effort in this direction. However, please everybody read all the old threads about SANE2. There was already a lot of discussion and the details are NOT easy. So before everybody starts programming, at least the basic ideas of SANE2 should be fixed. Some points like the image formats and the error handling really need to be finally decided. Bye, Henning
[sane-devel] SANE2 commitment
Hi everybody, On 2006-12-15 17:57, Alessandro Zummo wrote: since there seems to be interest in developing sane2, I've decided to start this thread in order to collect the commitment of each developer. [...] Could we please move the SANE2 (and any sane-standard related) topics to the sane-standard mailing list? That's the idea of that list ... SANE2 threads tend to create lot of traffic that is less interesting for users and even some programmers. So lets focus it in sane-standard. sane-standard is moderated to avoid off-topic. Frequent posters will be automatically moderated. Others may take one day time to be approved. More moderators for this and the other SANE mailing lists are wanted. Volunteers please contact me. Bye, Henning
[sane-devel] udev rule for Epson Perfection V10
Hi,
On 2006-11-25 21:15, Martin Kittel wrote:
could you please add the following rule to your udev descriptions in
CVS? I verified it to work with my Epson Perfection V10.
SYSFS{idVendor}==04b8, SYSFS{idProduct}==012d, MODE=664,
GROUP=scanner
Thanks. It's already in our lists in CVS.
Bye,
Henning
[sane-devel] rules.d for Epson Stylus CX6600
Hi,
On 2006-11-01 13:45, Kevet Duncombe wrote:
I just added this entry to my rules.d and am sending it along as the
comment at the top requested.
# Epson Stylus CX6600
SYSFS{idVendor}==04b8, SYSFS{idProduct}==0813, MODE=664,
GROUP=scanner
Thanks. That one is already in our lists.
Bye,
Henning
[sane-devel] Documentation: ColorPage-SF600 is supported
Hi, On 2006-10-02 22:12, Ryan Reading wrote: I e-mailed the maintainer of the backend, but haven't heard anything back, I thought I'd say something here too. Sorry, I must have missed your mail. The ColorPage-SF600 is supported by the gt68xx backend. It's just a repackage of the OpticSlim M12. It uses the same firmware. I was able to get it working simply by adding the PID and VID to the config file, setting the override to the M12, and supply the firmware. Thanks for your report. I'll add the scanner to the source code and gt68xx.conf so manual work shouldn't be necessary in future. How well does it work? Bye, Henning
[sane-devel] Updating lsusb -v, /proc/bus/usb/device, and sane-find-scanner -v -v for Canon CanoScan 4200F (unsupported)
Hi, On 2006-10-03 11:06, Ren? Kjellerup wrote: Regarding the Canon CanoScan 4200F The information on the unsupported page is from a device connected to a usb1.1, I've attached the correct information in 3 plain text files. Ok, I've just updated sane-find-scanner and devices output on our website. Bye, Henning
[sane-devel] unsupported device info correction
Hi, On 2006-09-30 15:29, Serge Major wrote: Device information: Umax AstraSlim 1200 USB scanner. Power supplied from USB bus only. Chips labels on the PCB is: 1. A3966SLB M148313 BPA 2. CSI 24WC16P 0013D (8-pin chip) 3. GRANDTECH GT-6816 F60685.1 0041 (that`s it) Ouput of sane-find-scanner -v -v with root privilegies is: --- device descriptor of 0x080d/0x0110 at 004:002 In addition to the gt68xx backend, you could also try the artec_eplus48u backend. The Umax AstraSlim 1200 SE works with that backend. Edit artec_eplus48u.conf and change this line: usb 0x05d8 0x4011 to usb 0x080d 0x011 Get the firmware file (comes with the windows driver) and adjust the path: option artecFirmwareFile /usr/local/share/sane/artec_eplus48u/1200.usb Bye, Henning
[sane-devel] CanoScan LiDE 70
Hi, On 2006-09-27 22:05, Waitman Gobble wrote: I've purchased a Canon LiDE 70 and would like to use it on my computer. The 70 isn't listed on the sane web site. Could you send us the output of sane-find-scanner -v -v as root when the scanner is plugged in? Is there a way to try to coerce the existing driver, to see if it commands my device properly? My software simply yells at me, telling me my scanner does not exist. It depends on how different the scanner is from currently supported devices. Bye, Henning
[sane-devel] request removal
Hi, On 2006-07-31 05:31, Technomage wrote: seem that I have lost my password info and request removal from the list at this time. See below. On the website mentioned there, you can also request to send the password to you. 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 Bye, Henning
[sane-devel] USB Boeder SmartScan on Debian Sarge
Hi, On 2006-07-30 10:19, Jim McQuillan wrote: It shows pretty clearly that you are missing the ps1fw.usb firmware file. Unfortunately the message is not correct in this case. As there are several scanners with the same USB id for some a special manual override is necessary. This scanner needs the gt680xfw.usb firmware but this can't be detected by the SANE backend automatically. Bye, Henning
[sane-devel] Code freeze for sane-backends 1.0.18
Hi, On 2006-06-26 21:58, Jon Chambers wrote: The dell1600n_net backend is also new for this release. Which is not reflected by any entry in ChangeLog :-) I'll add it to NEWS, but please ad the missing ChangeLog entries. Bye, Henning
[sane-devel] Umax Astra 4500
Hi, On 2006-06-26 21:32, Paul Drynoff wrote: What is the status of Umax Astra 4500 support? unsupported Needs to be added to the genesys backend. For more details, read the mailing list archive of this list on how to add scanners to the genesys backend. Bye, Henning
[sane-devel] Problems with HP Scanjet 4100c USB on FC5
Hi, On 2006-06-26 08:45, Sean Laurent wrote: $ scanimage -L Try to commebt out everything except hp in dll.conf. Run SANE_DEBUG_SANEI_USB=255 SANE_DEBUG_HP=255 scanimage -L and send us the output. Bye, Henning
[sane-devel] Code freeze for sane-backends 1.0.18
Hi everyone, Code freeze for sane-backends 1.0.18 is now active. After code freeze only fixes of grave bugs that render a backend completely unusable or break compilation and documentation updates are accepted. Time table: 2006-07-02 Release There have been quite some changes since the last release. Therefore please test the current version of sane-backends carefully, so all bugs are found until release. Current snapshots are available here: http://www.sane-project.org/snapshots/ I'll attach the current NEWS file. Please check if I missed anything. Bye, Henning -*-Mode: outline-*- New with 1.0.18, released 2006-07-02: * New backends: hp3500 (HP ScanJet 3500 series), pixma (Canon Pixma series), stv680 (Aiptek Pencam and similar). * Updated backends: avision, canon, dll, epson, fujitsu, genesys, gt68xx, microtek2, mustek_pp, niash, plustek, snapscan, sp15c, test, u12, umax1220u. * Scanimage batch mode fixes. * Scanner lists contain USB vendor/product ids and some statistics now. * Udev/hotplug lists are generated autmatically from the .desc files now. * Portability fixes (especially for DragonFlyBSD and HP/UX). * Build system updates. * Updated translations. * Documentation updates. * Bugfixes.
[sane-devel] Couldn't use HP PSC 1210 to scan
Hi, On 2006-06-18 16:58, Franklin wrote: I have a HP PSC 1210. It printed well, and now I wish to use it to scan (on linux). My system is Mandriva 2006, upgrading my sane-backends and saned to 1.0.17, and my libusb to 0.1.12. You'll need the external hpaio backend for this scanner: http://hpinkjet.sourceforge.net/hplip_readme.html Bye, Henning
[sane-devel] [patch] epkowa.desc
Hi, On 2006-06-20 10:29, Olaf Meeuwissen wrote: If some kind SANE developer could commit this, I'd be grateful. Thanks! Both patches are now in CVS. Bye, Henning
[sane-devel] Xerox WorkCentre P16
Hi, On 2006-06-10 16:48, Sangeeta Joneja wrote: I am trying to configure my Xerox WorkCentre P16 on Ubuntu Breezy. I have installed Samsung SCX-4216 driver. The printer works fine but when I am trying to run Scanner thru Samsung configurator the error I get is sane_open - device name SAMSUNG WorkCentre PE16 on USB:0cannot open! That's why this scanner is still listed as unsupported. As the Samsung backends are external (not part of sane-backends) you may have more luck in getting help from Samsung or Xerox directly. Bye, Henning
[sane-devel] Help on SANE.
Hi, On 2006-06-02 11:02, Rupesh Tarpara wrote: I am developing backend for USB hand held scanner, for Fedora Core-5. I have gone through the documentation of SANE standard. I am still not clear about how communication happens between Front-end=backend=Device. Can any one help me with the implementation of backend? The code flow is in chapter 4.4. Looking at existing backend and frontend source code may help to understand what's going on. Asking direct, clear questions may also help to get better answers. Bye, Henning
[sane-devel] Genesys HP ScanJet 2400
Hi, On 2006-06-11 17:40, Nick Booker wrote: I've noticed that there is a section in the HEAD version (1.35) of the file genesys_devices.c in the experimental/genesys tree of CVS mentioning the HP ScanJet 2400c. My questions are: See the archive of this list for a lot of discussion about that scanner. 3) is 2400c just an alias for 2400? Yes. Bye, Henning
[sane-devel] Nikon CoolScan IV and next sane release
Hi, On 2006-05-27 09:19, Giuseppe Sacco wrote: please find the new patch, where I correct one small error and tested it with LS-50. The code you pointed out seems to be a correction of a previous bug, so I think it will not break any working scanner. I just applied your patch to CVS. Test results with LS-50: Blank and white negative film: not working Color negative film: not working Color positive film: working, but I think there is still a problem with autoexposure, since all scanned images are very dark. For now I used status minimal for the LD 50 ED/V ED and untested for Coolscan LS-5000 ED. Bye, Henning
[sane-devel] Feature freeze for sane-backends 1.0.18
Hi everyone, Feature freeze for sane-backends 1.0.18 is now active. This means, that no new backends or new features for existing backends should be committed to CVS anymore. Bug fixes, documentation and translation updates are still ok. Time table: 2006-06-25 Code freeze 2006-07-02 Release After code freeze only fixes of grave bugs that render a backend completely unusable or break compilation and documentation updates are accepted. There have been quite some changes since the last release. Therefore please test the current version of sane-backends carefully, so all bugs are found until release. Current snapshots are available here: http://www.sane-project.org/snapshots/ Developers, please have a look at our growing list of bugs and fix as many bugs as possible: http://alioth.debian.org/tracker/index.php?group_id=30186atid=410366 If the bug report is bogus, please close it with a comment why it's closed. If you need more information from the author, add a comment. If you don't get more info and can't reproduce the bug, close it. Also, you can view only bugs assigned to you to reduce the number of visible bugs. Having a look at bugs assigned to nobody is also worth a try as some bugs affect several backends/maintainers. You can also sort by topic (Summary). Bye, Henning
[sane-devel] Where can I find a port of SANE Backend for Windows?
Hi, On 2006-05-31 13:03, Kerry Menzel wrote: I have a C application that runs on Window and Linux. I would like to use SANE to access a scanner on both windows and Linux so I have a consistent backend. I've been trying to follow links to SANE on windows, but most of the links are broken or they are for the front end. At least in principle, sane-backends can be built on Windows out-of-the-box. See the README.windows that comes with the sane-backends distribution. However I haven't checked if that works for some time. Bye, Henning
saned help? (was Re: [sane-devel] Fujitsu 5120C)
Hi, On 2006-05-31 09:07, m. allan noah wrote: On Tue, 30 May 2006, Jim McQuillan wrote: Ok, I tried using scanimage without saned, and it works ! Now, I need to figure out how to get saned working with this backend. Anyone here can give me any pointers? i wont rule out a bug in the backend, but i dont know enough about saned to even start troubleshooting. what we see is that scanimage via saned is giving random buffer sizes to the calls to sane_read. Thats ok. Any buffer size is acceptable by the SANE standard, even only one byte. You may get a similar error when running scanimage -T. The fujitsu backend seems to assume that the buffer is at least one scan line: bytes -= (bytes % s-params.bytes_per_line); Bye, Henning
[sane-devel] libsane.usermap entry Epson Perfection 1660 Photo
Hi, On 2006-05-25 23:38, Andreas G. Filzer wrote: Please add this to libsane.usermap and have a lot of fun ;-) Thanks. It's already in that file in the development version of SANE. Bye, Henning
[sane-devel] Sane Network with Niash
Hi, On 2006-05-24 00:19, Mike Petersen wrote: I got a problem with sane using it via network. I just got a new scanner an HP scanjet 3400C which works on the machine with the niash backend. I want to use the scanner also over network (the other scanner (parallel) works), but it doesn't work. I got the following info out of the logs : Enabling more debugging may help to locate the problem: On the client: export SANE_DEBUG_NET=255 scanimage ... image.pnm On the server (avoid starting saned from (x)inetd, instead run it manually): export SANE_DEBUG_NIASH=255 saned -d128 Bye, Henning
saned help? (was Re: [sane-devel] Fujitsu 5120C)
Hi, On 2006-06-01 10:46, m. allan noah wrote: saned requests 8188 bytes, backend only returns 7656, cause that is an even number of scanlines. the difference is 532. then saned asks for 528 bytes on the next attempt? why not 532? why not just transmit the 7656? IIRC, saned uses the first 4 bytes in the data stream for the size of the data that is transmitted. Bye, Henning
saned help? (was Re: [sane-devel] Fujitsu 5120C)
Hi, On 2006-06-01 11:14, m. allan noah wrote: IIRC, saned uses the first 4 bytes in the data stream for the size of the data that is transmitted. does that mean that if i actually gave it 8188 bytes, it would drop 4 of them? i need to look at saned more closely... No data is dropped. Just the buffer sizes may vary. I don't remember which buffer size saned uses internally, but if it were e.g. 16kb, it would ask for 16kb - 4 bytes. Bye, Henning
[sane-devel] Another platform for sane
Hi, On 2006-05-22 13:04, Peter Coghlan wrote: A friend gave me his Agfa snapscan 310 SCSI scanner. I connected it up to my old VAX at home which runs VMS (aka OpenVMS) and begun the quest for some software to use it. I came across sane, downloaded version 1.0.17 and gave it a go. I was very impressed by the portability of the code and had very little difficulty getting it to compile under VMS 7.1. Thanks for your report! SANE builds on quite a lot of different platforms so most of the typical portability problems should be fixed meanwhile. I have only tried the snapscan backend so far as I have no other scanners to test with. Hopefully, other (SCSI) backends should be just as easy to get working. I have not looked at frontends other than scanimage. I have also compiled the code on a Dec Alpha machine running VMS with no problems, although I do not have a scanner attached to that machine to test with. I suspect it should also compile ok on Itanium machines running VMS and hope to test this shortly. Even without scanners you can test with the test backend (e.g. scanimage -d test --test or use the test patterns and check if the images look correct). I don't suppose there is much interest in this out there, but I thought I would people know that it can be done, just in case someone somewhere is interested. Please send the patch to the list! Even if we don't include it now, it may be useful for someone. Bye, Henning
[sane-devel] Timetable for the release of sane-backends 1.0.18
Hi, On 2006-05-23 12:07, Wittawat Yamwong wrote: May I commit changes into CVS? There could be a small status update for MP800 and MP830 in the next weeks. My account at alioth.debian.org is wittawat-guest. Go ahead, please! I've just added you to the project. CVS write access can take some hours (cron scripts running...). Updates can be added until feature freeze. After that only bug fixes. Bye, Henning
[sane-devel] Timetable for the release of sane-backends 1.0.18
Hi, On 2006-05-21 21:36, Jon Chambers wrote: On Sun, 21 May 2006, Henning Meier-Geinitz wrote: As already discussed some weeks before, it's time for a new release of sane-backends. [...] - dell1600n_net: Backend code is in CVS, Makefile/configure changes and documentation yet to come. Although I added dell1600n_net.c to CVS I was not planning to commit any changes that would make it part of the official build until these outstanding tasks were done: - Makefile/configure changes (I'm looking at this now) - Support for multipage scans. - Desc file/man page Time is somewhat limited right now so I'm very unlikely to make it before the code freeze but I will try to get at least the desc file in by then. I'd like to get it into the default build for several reasons: - We find out quite quickly if it breaks compilation somewhere - The backend gets much more testing - We don't get questions on how to build it - We don't have to think if it's now an internal or external backend... So if you can't finish the Makefile/configure changes, I'll try to do that before feature freeze. Bye, Henning
[sane-devel] CanoScan LiDE20 finally working
Hi, On 2006-05-23 12:21, Fibonacci Prower wrote: The unstable version is just not working: Believe me, it does. $ scanimage bash: scanimage: command not found This means that you didin't install sane-backends at all or that /usr/local/bin is not in your path. What did you do to install the source code? $ xscanimage xscanimage: error while loading shared libraries: libsane.so.1: cannot open shared object file: No such file or directory sane-backends is not installed. Or this is a version of xscanimage (from the sane-fromtends package) that was linked to sane-backends at a different location. Bye, Henning
[sane-devel] dell1600n_net backend
Hi, On 2006-05-09 22:07, Jon Chambers wrote: Any idea where select.h is on HPUX? (select is a POSIX call so I guess it is somewhere?) I suspect that these issues are likely to be common to most network scanner backends so maybe sanei_tcp.h would be the correct place for this kind of #ifdef? Some Linux manual page says: /* According to POSIX 1003.1-2001 */ #include sys/select.h /* According to earlier standards */ #include sys/time.h #include sys/types.h #include unistd.h saned.c should already have a check for this. Bye, Henning
[sane-devel] CanoScan LiDE20 finally working
Hi, On 2006-05-20 16:50, Fibonacci Prower wrote: Just use sane-backends 1.0.17 to generate the udev rules file. There is no need to run make or make install in this case, just copy the rules file to the appropriate location. Still nothing. I've added my user account to the scanner group, ran the generating script on the hotplug file that came with .16, but still, it only works as root. So you now have a udev rules file? Does it contain the id of your scanner? Have you copied it to the location, where the other rules files are? Have you checked that you use libusb 0.1.12 or newer or use the work-around as mentioned in README.linux on our website? Bye, Henning
[sane-devel] Nikon CoolScan IV and next sane release
Hi, On 2006-05-13 21:01, Giuseppe Sacco wrote: another problem I think I found on this patch is at about line 1525 of the patched file, where it is i = (xfer_len_in 0x3f); while it should be i = (xfer_len_in 0x3f); with a single ampersand. Ok. Could you (or somebody else) post a patch that includes my and your comments? I.e. that can't break support for the other scanners? And that is tested with the LS-50? Thanks, Henning
[sane-devel] Backend driver for Canon CanoScan 4200f
Hi, On 2006-04-20 20:46, Alfred Egger wrote: I also an owner of the 4200f and I searched for information of the Chips inside this scanner a while ago. According to this site the chips are: [...] Maybe someone could integrate this information on the site I noticed above. Thanks! Your info is on our website now. Bye, Henning
[sane-devel] saned pnm-backend - glibc detected *** malloc(): memory corruption (fast):
Hi, On 2006-04-18 14:42, Michael Schwipps wrote: I'm writing a small client application and use saned. The tests of the client use then pnm-backend. There seems to be a bug in this backend. Sorry for the long delay for answering. I just had a quick look at the ocde but I couldn't find any obvious bug, at least not in sane_open. However, the pnm backend is obsolete anyway. Is there any reason not to use e.g. the test backend? If I open the first device pnm:0 it's ok. I can read all options of this device. Then I try to open pnm:1. The reply state is device busy - also ok for me. If I now reread the options of pnm:0 there is a error (see subject line). I can get some options, but always the next get-request after option 2 (filename) fails. Maybe the reason is that option 2 is the only String-option. Could you show us the code (or part of it) you used to cause this error? Bye, Henning
[sane-devel] sanei_tcp
Hi, On 2006-02-27 13:26, Alessandro Zummo wrote: Thanks. I haven't looked at the actual code yet, just some formal things: [..] ok, I will modify the license. please drop me a note when you'll have reviewed the code so I can send the new version just once. Sorry for the long delay. I have no comments on the actual code, but somebody with more betwork knowledge shoulc look at it anyway. What's the status of your AcuLaser CX11NF via network backend? Bye, Henning
[sane-devel] Status of Canon LiDE 40
Hi, Has anybody tested the Canon LiDE 40 with the genesys backend? I guess it works, but it's still listed as untested in our lists. Please tell us if it works (or not). Bye, Henning
[sane-devel] Status of Canon LiDE 40
Hi, On 2006-05-21 19:02, Nikolas Arend wrote: seeing that more and more scanner models of the LiDE series become supported... is there any progress for the LiDE 80? I can't help coding atm, but I could test the backend. The LiDE 80 is still listed as unsupported, but I guess its chipset is such that the genesys backend can support it in principle. The Canon LiDE 35, 40, 50, and 60 are nearly identical so it was easy to support them once the 35 worked. However, the LiDE 80 seems to be a bit different. So as with any other gl646/841 scanner a user has to create log files, understand them and moidfy the genesy backend appropriately. See lots of discussions on sane-devel. As with other scanners, it won't happen automatically, it has to be done by users who own these scanners. If this doesn't happen, this scanner will never be supported. Bye, Henning
[sane-devel] SANE shared library
Hi, On 2006-05-18 23:03, Tamkang wrote: I have a questions: 1. why in /usr/lib/sane has 2 files (ie: libsane-sm3600.so.1 , libsane-sm3600.so.1.0.17) as i know that libsane-sm3600.so.1 is symbolic link to libsane-sm3600.so.1.0.17, This is done automatically by ldconfig. Usuaally there should be at least three files (.so, .so.1, .so.1.0.17). The frontends are linked to libsane.so.1 and this file is a symlink to the latest version of the backend. This way you can update the backends without re-linking the frontends. but why in /usr/local/lib/sane has 4 files (ie: libsane-sm3600.la , libsane-sm3600.so , libsane-sm3600.so.1 , libsane-sm3600.so.1.0.17) ? This is the default. If there are less files like in your first case, your Linux distribution has deleted or just not installed them. The .la file is used by libtool for linking information. IIRC correctly, it's not absolutely necessary with Linux but may be needed for other platforms when linking with libtool. why not only one file libsane-sm3600.so.1.0.17 files to let xsane to link to this driver ? With the next release of sane-backends, you had to build (or at least link) xasne and any other frontend again. 2. because I am still new for linux filesystem hierarchy , so i just want to know that my linux fc5, have installed sane backend from it's fc5 dvd distro, but there is no source code to debug. SANE is provided as GPL (+ SANE exception) software, so you must have the source code (or a way to get it from Fedora). so I downloaded from sane-project website, the source of sane-backend, and then I build and installed in default directory /usr/local/lib/sane, and then the questions is why the source not default to /usr/lib/sane directory? Is there any different between /usr/local/lib/sane and /usr/lib/sane directory ? Software that is not part of the operating system or distribution shouldn't install anything outside of /usr/local/. At least not by default. Bye, Henning
[sane-devel] Status update for pixma backend
Hi, On 2006-05-14 15:18, Wittawat Yamwong wrote: I attached the updated description file for pixma backend. Support for following models was added to the backend: imageCLASS MP730, PIXMA MP750, PIXMA MP760, PIXMA MP780, PIXMA MP830 [...] Ok, let's have a quick look: +++ sane-backends-pixma/backend/pixma.c2006-05-14 00:03:53.0 +0200 ... +#ifdef WITHOUT_SANEI Is this for a standalone mode? I guess that's not needed once the backend goes into SANE CVS? You seem to use fprintf and printf for debugging and information, but I haven't checked if this is called during normal usage. fprintf won't work over the net and printf won't work with programs using stdout for image data (e.g. scanimage). Otherwise it looks fine for me. I haven't looked at the source too much and I couldn't est compilation on anything but Linux/i386. In my opinion it?s ok to put it into CVS. Bye, Henning
[sane-devel] About Backend driver for Canon/HP USB scanner
Hi, On 2006-05-15 10:29, Stephen Liu wrote: I'm considering to purchase either USB CanoScan 4200F (preferrable) or USB HP Scanjet 4370. But they are unsupported on SANE. [url]http://www.sane-project.org/sane-mfgs.html#Z-CANON[/url] [url]http://www.sane-project.org/sane-mfgs.html#Z-HEWLETT-PACKARD[/url] I have been searching The sane-devel Archives [url]http://lists.alioth.debian.org/pipermail/sane-devel/[/url] and could not find available Backend driver for them. Yes. Can any folk on the forum shed me somelight. TIA The lists are correct as far as I know. There is no backend for the Canon 4200F. For the HP 4370, it may be worth trying the external hp3900 backend. However, that scanner is marked as untested so it may or may not work: http://www.sane-project.org/cgi-bin/driver.pl?manu=hewmodel=4370bus=anyv=p= Bye, Henning
[sane-devel] HP ScanJet 5300c only partially detected
Hi, On 2006-05-12 18:46, Damon Butler wrote: If this doesn't happen, try: SANE_DEBUG_DLL=255 scanimage -L and send the output. I set both environment variables, and here's the output I got. [...] [avision] sane_init: Trying to find USB device 3f0 701 ... [avision] sane_init: Trying to find USB device 3f0 701 ... This is the id of the HP 5300c. It doesn't seem to be plugged in. Are you sure that this is your device? The id you gave in your original posting is the one of the HP 3500. That scanner is supported only by the development version of sane-backends. Bye, Henning
[sane-devel] LIDE 60
Hi, On 2006-05-13 17:24, Trent Michael Gamblin wrote: Hi. I have a Canon LiDE 60, and the product ID is 0x221c. Otherwise it's the same as the LiDE 50. You can add it to the list of scanners. Thanks. Thanks. It's already in our lists: http://www.sane-project.org/cgi-bin/driver.pl?manu=canonmodel=%22LiDE+60%22bus=anyv=p= Bye, Henning
[sane-devel] dell1600n_net backend
Hi, On 2006-05-11 21:47, Jon Chambers wrote: On Wed, 10 May 2006, Julien BLACHE wrote: Create an account on http://alioth.debian.org and give us your login name so you can be added to the sane project. My login is phap016-guest. I just added you to the project. It can take some hours until CVS write access works. Bye, Henning
[sane-devel] dell1600n_net backend
Hi, On 2006-05-10 07:44, Julien BLACHE wrote: backend myself as a diff to the most recent major release until it is stable or can it be got into the main repository before that? Henning will correct me if I'm wrong, but the backend can probably go in if it has at least basic support for the scanner and won't cause data loss if something goes wrong. Yes, my rule of thumb is something like if it does something useful, complies with the rules in backend-writing.txt (and the SANE standard), doesn't break compilation and doesn't cause hardware damage it can go in. For more fine-grained control we have the status levels for each scanner. Bye, Henning
[sane-devel] HP scanjet 2300c
Hi, On 2006-05-11 06:58, St?phane VOLTZ wrote: after searching the debug data, I think there is no problem in start position detection (which is correclty reported to be 'top = 65'). In fact it seems that it is the value added to the detected y position is bogus. Currently, we add -2.0 mm which may lead in a negative y movement if the inital y offset is low. I had a similar problem in the gt68xx backend, where in certain situations the scan head bumped at the end of the scan area when a debugging option (scan full area) was set. A check if the start position is = 0 helped to fix this. Bye, Henning
[sane-devel] HP ScanJet 5300c only partially detected
Hi, On 2006-05-11 08:45, Damon Butler wrote: I have a HP ScanJet 5300c (USB connection) hooked up to my Intel MacMini (Mac OS X 10.4.6, fully updated). After installing SANE via the latest darwinports ... ... Try SANE_DEBUG_AVISION=255 scanimage -L (or whatever is needed to set environment variables on MacOS X). You should get debug messages like this: [sanei_debug] Setting debug level of avision to 255. [avision] sane_init:(Version: 1.0 Build: 182) [...] If this doesn't happen, try: SANE_DEBUG_DLL=255 scanimage -L and send the output. If you haven't tried yet, run scanimage as root. Bye, Henning
[sane-devel] Epson Perfection V700 Photo
Hi, On 2006-05-10 10:50, Fredrik Sandstrom wrote: I'm considering buying the scanner of the Subject line, but it seems it's not (yet?) supported by any SANE backend. What's its status, has anyone tried it, and can it be expected to be supported soon? As it's not in our list, nobody has reported anything about it. So we don't know. If it's compatible to some alsready supported scanners, it may be easy to support it. If it's a completely new scanner with a new chip set, this means developing a new backend. This is up to a user of such scanners. Usually, it won't be done by any of the current SANE developers.
[sane-devel] Hotplug and udev files created automatically now, please test!
Hi, On 2006-05-10 18:07, Wittawat Yamwong wrote: The above rules do not work with an older version of libusb (e.g. 0.1.10a shipped with SUSE 10.0). This version looks at /proc/bus/usb first. If the usbfs is mounted, which is normally true, libusb will open a device node in /proc/bus/usb (not in /dev/bus/usb) which is normally not writable by non-root users and is not affected by the above rules. Anyway, I suggest we should stick with the above udev rules. For those who has an older libusb (like me), exporting USB_DEVFS_PATH=/dev/bus/usb as a system wide environment variable could help. I just updated the README.linux file and some other documentation: http://www.sane-project.org/README.linux Bye, Henning
[sane-devel] PLANon DocuPen support
Hi, On 2006-05-08 20:37, Nicola Jelmorini wrote: just a question: in the near future is scheduled to implement SANE support for the PLANon DocuPen (http://www.planon.com/docupen_rc800.php) scanners? As these scanners are not even in our list of unsupported scanners, you are the first one to mention them. Could you send the output of sane-find-scanner -v -v when such a device is plugged into your computer? Without this information, we can't know if they may work with little (or more) cahnges with existing backends. As the device seems to store several images, maybe they behave like normal USB storage devices? In this case you could just plug it into your computer and use it like a USB disk drive or stick. Bye, Henning
[sane-devel] USB speed
Hi, On 2006-05-06 18:50, Pierre Willenbrock wrote: i am trying to make the scanning speed of my scanner depend on the usb speed available. I first attempted to use the detection from the cs3200f backend, but found that it only detects if the device is high speed capable, not if it is currently communicating with high speed. Wouldn't it be better to actually measure speed? E.g. by scanning some data at maximum scanner speed without moving the motor? Obviously this may not be possible with all scanner chipsets. On further investigation i found that there are two ways to determine the used speed on linux: * The first one involves an ioctl, which needs an file descriptor of the device. I cannot see any way to get the fd from libusb. IIRC it is possible but ugly and may break with newer libusb versions. SOmething like declaring an internal libusb structure in your own code and using that to access internal variables. * The second one is looking at /proc/bus/usb/devices, parsing the T-lines. This only needs the device number and the bus number, which can be obtained from libusb. The attached patch adds a function to sanei_usb which adds a function determining the usb speed. Currently, it only reports speeds when using libusb on Linux. I tested this on Linux 2.6.16. Any objections to this approach? I'm not sure if the format libusb device names/numbers are guaranteed to remain unchanged. E.g. it's different for other operating systems. You seem to imply that there will be a solution within libusb? If this is true, I'd prefer to use that one, once it's available. Is the determination of USB speed also needed/useful for other backends? Bye, Henning
[sane-devel] Hotplug and udev files created automatically now, please test!
Hi,
On 2006-05-07 20:39, Peter Christy wrote:
To summarise: I added the following line to my udev.rules (sorry about the
wrod-wrap!)
# permissions for usb scanner
SUBSYSTEM==usb, ACTION==add, ENV{PRODUCT}==4b8/11d/*,
RUN+=/bin/sh -c '/bin/chgrp scanner $env{DEVICE}; /bin/chmod 664
$env{DEVICE}'
Many thanks to all those who have contributed ideas, and particularly to
Wittawat Yamwong for the solution!
Might be an idea to add this fix in the documentation somewhere?
By default, SANE generates a udev rules file like this:
ACTION!=add, GOTO=libsane_rules_end
SUBSYSTEM!=usb_device, GOTO=libsane_rules_end
# Hewlett-Packard ScanJet 4100C
SYSFS{idVendor}==03f0, SYSFS{idProduct}==0101, MODE=660, GROUP=scanner
[...]
LABEL=libsane_rules_end
Does this still work?
Bye,
Henning
[sane-devel] Hotplug and udev files created automatically now, please test!
Hi, On 2006-05-07 21:03, Julien BLACHE wrote: As there are still operating systems that only habe kernel scanner driver support and no libusb port, I think we should keep it. But maybe we should check all documentation to not mention it any longer or clearly mark it as obsolete. Maybe we could disable it or have a build-time option to disable it ? After a quick look at the code, this won't be that easy because it assumes the availability of a way to access device files directly. But you are free to add a lot of #ifdef HAVE_KERNEL_SCANNER_DRIVER :-) Bye, Henning
[sane-devel] Nikon CoolScan IV and next sane release
Hi, On 2006-05-08 08:51, Giuseppe Sacco wrote: It was posted to this list on the 27th october 2005 by Ariel Garcia, here it is. There were some mail with comments on about the C code on that thread. I've just forwarded the patch again to the backend maintainer. Let's try: coolscan2.c: In function 'sane_coolscan2_read': coolscan2.c:1523: error: syntax error before '/' token coolscan2.c:1525: error: 'i' undeclared (first use in this function) [...] Ok, illegal // comments. Fixed. coolscan2.c: In function 'sane_coolscan2_read': coolscan2.c:1524: warning: ISO C90 forbids mixed declarations and code Fixed now. More comments: + sanei_usb_attach_matching_devices (usb 0x04b0 0x4001, cs2_attach); + sanei_usb_attach_matching_devices (usb 0x04b0 0x4002, cs2_attach); Which scanner is id 0x4002? According to our lists, it's the Super Coolscan LS-5000 ED. Does this also work? @@ -2324,14 +2352,14 @@ s-resx_max = 256 * s-recv_buf[20] + s-recv_buf[21]; s-resx_min = 256 * s-recv_buf[22] + s-recv_buf[23]; s-boundaryx = -65536 * (s-recv_buf[36] + 256 * s-recv_buf[37]) + +65536 * (256 * s-recv_buf[36] + s-recv_buf[37]) + 256 * s-recv_buf[38] + s-recv_buf[39]; Well, I don't know nothing abot that backend but wouldn't this break the already existing scanners? s-resy_optical = 256 * s-recv_buf[40] + s-recv_buf[41]; s-resy_max = 256 * s-recv_buf[42] + s-recv_buf[43]; s-resy_min = 256 * s-recv_buf[44] + s-recv_buf[45]; s-boundaryy = -65536 * (s-recv_buf[58] + 256 * s-recv_buf[59]) + +65536 * (256 * s-recv_buf[58] + s-recv_buf[59]) + 256 * s-recv_buf[60] + s-recv_buf[61]; Same here. Just to be sure, use if ((s-type == CS2_TYPE_LS50) || (s-type == CS2_TYPE_LS5000)) here? Bye, Henning
[sane-devel] sane_cancel and sane_read
Hi, On 2006-04-25 15:07, Wittawat Yamwong wrote: Should/must/may a frontend call sane_read after sane_cancel? I think it may but it doesn't need to. I can't find an explicit statement in the standard that it's forbidden to do so. In fact, there is even a status code for sane_read for this case. But it's also not necessary (and not really logical) to call sane_read after sane_cancel(). Case II: The frontend has read a block of image data from a backend and it is writing the data to a file but a IO error occurs. The frontend probably calls sane_cancel. What will/must the frontend do next? Will it call sane_read until an error or EOF occurs? It should do nothing (or call sane_close, sane_exit). This is important to my backend (pixma). It would be much more complex if frontends are not required to call sane_read after sane_cancel because I have to check whether sane_cancel was called synchronously or asynchronously. If it's called synchronously (case II), an outstanding scan operation must be completely canceled before sane_cancel returns. If it's call asynchronously (case I), the request must be postponed by setting a flag for example. The request will be carried out when we return to the reader thread. Why not just kill the reader process in sane_cancel? Do you think the way this is done in the existing backends (e.g. mustek) is wrong? Bye, Henning
[sane-devel] dell1600n_net backend
Hi,
On 2006-04-23 15:16, Jon Chambers wrote:
I have a nominally functional backend for network scanning using a Dell
1600n MFP. The source can be found at
http://www.jon.demon.co.uk/sane-dell1600n_net/dell1600n_net.c
[...]
I am keen to get the source into CVS and also to verify the build on some
other platforms (I suspect that some of the network headers may require
some #ifdef magic).
Ok, let's try (Linux i386):
dell1600n_net.c:78:20: error: tiffio.h: No such file or directory
I guess you must add some magic to not compile the backend if the jpeg
and tiff headers are not present. Or, if this is possible/makes sense,
to #ifdef out that functions calls in your backend.
With libtiff installed, I get these warnings:
dell1600n_net.c: In function 'sane_dell1600n_net_init':
dell1600n_net.c:225: warning: unused parameter 'authorize'
dell1600n_net.c: In function 'sane_dell1600n_net_get_devices':
dell1600n_net.c:263: warning: unused parameter 'local_only'
dell1600n_net.c: In function 'sane_dell1600n_net_get_option_descriptor':
dell1600n_net.c:498: warning: unused parameter 'handle'
dell1600n_net.c: In function 'sane_dell1600n_net_control_option':
dell1600n_net.c:522: warning: unused parameter 'handle'
dell1600n_net.c:522: warning: unused parameter 'info'
dell1600n_net.c: In function 'sane_dell1600n_net_read':
dell1600n_net.c:721: warning: comparison between signed and unsigned
dell1600n_net.c: In function 'sane_dell1600n_net_cancel':
dell1600n_net.c:749: warning: unused parameter 'handle'
dell1600n_net.c: In function 'sane_dell1600n_net_set_io_mode':
dell1600n_net.c:755: warning: unused parameter 'handle'
dell1600n_net.c:755: warning: unused parameter 'non_blocking'
dell1600n_net.c: In function 'sane_dell1600n_net_get_select_fd':
dell1600n_net.c:765: warning: unused parameter 'handle'
dell1600n_net.c:765: warning: unused parameter 'fd'
dell1600n_net.c: In function 'ClearKnownDevices':
dell1600n_net.c:787: warning: cast discards qualifiers from pointer target type
dell1600n_net.c:789: warning: cast discards qualifiers from pointer target type
dell1600n_net.c: In function 'JpegDecompTermSource':
dell1600n_net.c:1869: warning: unused parameter 'cinfo'
Doesn't look critical, but you could use __sane_unused__ to mark
unused parameters explicitely.
Ok, next test on HP-UX risc:
dell1600n_net.c:74:24: sys/select.h: No such file or directory
dell1600n_net.c:77:21: jpeglib.h: No such file or directory
dell1600n_net.c:78:20: tiffio.h: No such file or directory
[more errors deleted]
Before including the code into CVS, please run indent -gnu on it.
SANE_Status sane_get_select_fd (SANE_Handle handle,
SANE_Int * fd)
{
return SANE_STATUS_ACCESS_DENIED;
Why is the access denied? I think the normal answer would be
SANE_STATUS_UNSUPPORTED as you don't implement the function. Same for
set_io_mode.
Bye,
Henning
[sane-devel] Please Help with Epson Stylus CX-5800
Hi, On 2006-05-06 21:25, Craig Setera wrote: I just bought an Epson Stylus CX-5800 All-In-One machine the other day This scanner is not in our lists at all so it's not known, if it is supported at all. Maybe the epkowa backend maintainer knows more about this scanner? Maybe it works with the snapscan backend? Bye, Henning
[sane-devel] xsane 0.991, sane 1.0.17 not working as root.
Hi, On 2006-05-06 20:06, Abhay Kedia wrote: When I run xsane as root, it works without any problems but when running under normal user account, xsane hangs to acquire preview or scan. The user is included in scanner and usb group. Permissions on the relevant file in /proc/bus/usb/ is 0666. If you don't use udev, this should work. If you use udev, the device files are here: /dev/bus/usb/... I have read the document available in following link but it did not help http://www.sane-project.org/README.linux So your distribution sets up the udev rules correctly? E.g. by using the rules file that can be generated in sane-backends/tools/udev/ ? Running scanimage with SANE_DEBUG_SANEI_USB=255 may also help to find the problem. Bye, Henning
[sane-devel] Genius Color Page Vivid 4
Hi, On 2006-05-03 23:44, Andre Carezia wrote: My system is Ubuntu 5.10 and I own a Genius Vivid 4. In order to automatically setup /proc permissions I had to modify the system file Thanks. Our lists in the current development version of SANE already contain this id. Bye, Henning
[sane-devel] Hotplug and udev files created automatically now, please test!
Hi, On 2006-05-04 07:56, Julien BLACHE wrote: Maybe we should pull the plug on the scanner driver support ? As there are still operating systems that only habe kernel scanner driver support and no libusb port, I think we should keep it. But maybe we should check all documentation to not mention it any longer or clearly mark it as obsolete. Bye, Henning
[sane-devel] UMAX 1200S Truncated Image Problem
Hi, On 2006-05-02 21:52, Romash, Cliff wrote: So that the read would ask for less than 32768 (12*2550) and thus complete. Once I do that, all my scans work fine. So my question is why do I need to do this? Is this a bug in the umax backend? Or something else? I don't know the internals of the umax backend in dteail, but maybe it's a problem with the kernel SCSI driver only providing 32k as SCSI buffer? Bye, Henning
[sane-devel] sequence usb commands send, receive
Hi, On 2006-04-29 13:55, gerard klaver wrote: I have a question about usb commands. I have for example the following sequence: send urb 5, send urb 6, send/receive urb7, send/receive urb8, receive urb 5, receive urb6 At this moment i don't know how te handle this. send urb 5, 6 no problem, send/receive urb 7, 8 no problem, but how to handle to receive urb 5 and 6?. As far as I know, at least the stable libusb doesn't provide support for async io. Even if it did, I'm not sure if it would work with Out-of-order URBs. IIRC, this didn't work with SCSI either? Does your USB device really depend on this order? Bye, Henning
[sane-devel] Nikon CoolScan IV and next sane release
Hi, On 2006-04-26 10:45, Giuseppe Sacco wrote: Is there any chance the next sane-backends release will include the patch for supporting CoolScan IV (LS-50 ED)? I haven't seen any response from the backend maintainer (Andras Major) until now. Could you resend the patch to this list, please? This patch was proposed before the current release was prepared and it was never changed/updated. The patch still have some problem, but it works for colour negative film. So there are no compilation/build problems any more? Are the Coolscan IV and LS-50 ED really identical? Our lists say, Coolscan V ED and LS 50 ED are the same, but don't mention Coolscan IV. Bye, Henning
[sane-devel] adding stv680 backend to cvs
Hi, On 2006-04-26 21:44, gerard klaver wrote: I have stil some memory leakage errors (with valgrind xcam -B) when using my stv680 backend. But i think its ready for adding to SANE CVS so it can get a bigger audience and more testers. I don't have such a device but I still had a quick look at the code: - if you use GPLed code from other sources (add_text), I think you can't use the SANE GPL exception for your backend. I get the following compilation warnings: stv680.c: In function 'stv680_init_options': stv680.c:1117: warning: cast discards qualifiers from pointer target type stv680.c: In function 'stv680_fill_image': stv680.c:1136: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'size_t' stv680.c:1144: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'size_t' stv680.c:1162: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'size_t' stv680.c:1162: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'size_t' stv680.c: In function 'stv680_bayer_unshuffle': stv680.c:1295: warning: format '%lx' expects type 'long unsigned int', but argument 6 has type 'unsigned int' stv680.c: In function 'sane_stv680_init': stv680.c:1572: warning: implicit declaration of function 'sanei_config_open' stv680.c:1572: warning: assignment makes pointer from integer without a cast stv680.c:1582: warning: implicit declaration of function 'sanei_config_read' stv680.c: In function 'sane_stv680_read': stv680.c:2077: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'size_t' stv680.c:2077: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'unsigned int' Bye, Henning
[sane-devel] Hotplug and udev files created automatically now, please test!
Hi, On 2006-05-02 14:17, Peter Christy wrote: I've built the latest cvs of sane and installed it, but it seems that it still relies on hotplug to set permissions for USB devices. My system no longer has hotplug (nor does Debian, I believe, and many others are in the process of dropping hotplug and just using udev). sane-backends provides scanner lists and scripts for hotplug, hotplug-ng and udev. They can be found together with some documentation in the tools directory. There were some changes in CVS recently concerning the generation of the scanner lists, so there is the chance that I broke something. But in pronciple, it works. The udev script is also used by the Debian package, in fact it was written by the Debian SANE maintainer :-) In our poackage, the udev (and hotplug ...) scripts are NOT installed automatically. When using udev without hotplug, the actual position of the usb device on the /sys bus seems to be variable. However, it is quite easy to make a symlink (/dev/usbscanner) that will always point to the scanner wherever it is actually mounted. Unfortunately, this symlink - or rather the device it ultimately links to - is under the /sys mount point rather than /proc. /dev/usbscanner (and similar device files like /dev/usb/scanner0) refer to the kernel scanner driver which does not exist on current kernels. Don't used them. SANE uses libusb which uses /proc/bus/usb/... or /dev/bus/usb, whichever is available. For udev, /dev/bus/usb/... is used (see README.linux). I think sane needs to offer an option as to whether it should seek /proc or /dev devices for USB (and possibly others, which I don't have!) SANE doesn't know anything about device files at all. It just asks libusb about the USB devices. Bye, Henning
[sane-devel] HP Scanjet 2400
Hi, On 2006-04-28 18:46, Pusk?s R?bert wrote: I have a HP Scanjet 2400 scanner, and I found out, that it's unsupported by sane. Even in the Genesys backend. Will my scanner be supported, in the near future? This depends on you. The general backend code is there, only the adaption of it to more scanners is missing. For discussion on what needs to be done please search the mailing list archive. So this means if you or another user of this scanner doesn't do this work the scanner will never be supported. This is how SANE (usually) works. Bye, Henning
[sane-devel] xsane errors
Hi, On 2006-04-28 08:31, Gary Montalbine wrote: I get the following errors from xsane: (xsane:5227): Gtk-CRITICAL **: gtk_accel_label_new: assertion `string != NULL' failed [...] You can enable debugging by running xsane like this: XSANE_DEBUG=255 xsane (use a lower debug level to decrease verbosity). Also moving away ~/.sane/xsane may be worth a try. Scanimage -L ~]$ scanimage -L device `epkowa:libusb:005:004' is a Epson Perfection 3490/3590 flatbed scanner device `v4l:/dev/video0' is a Noname Vanilla iTVC15 card virtual device device `snapscan:libusb:005:004' is a EPSON EPSON Scanner1 flatbed scanner Try to comment out the backends you don't use in dll.conf. This may help to find out which backend (if any) is the culprit. Bye, Henning
[sane-devel] pixels_per_line and bytes_per_line
Hi, On 2006-04-25 14:31, Wittawat Yamwong wrote: The SANE Standard Version 1.04 under 4.3.8 states that c = B * n * d/8for d 1 Note that the number of bytes per line can be larger than the minimum value imposed by the right side of this equation. A frontend must be able to properly cope with such padded image formats. The frontend should be able, but in reality it isn't. At least I don't know of any frontend who could do that. You can also test that behaviour with the test backend by setting the option --ppl-loss to a value 0. doesn't need to throw the padding bytes away. But the output image from scanimage is corrupted. It seems to me that the frontend works properly if and only if c = B*n*d/8. What should I do in this case? Fix scanimage and all the other frontends. Or easier, do the removal of the padding in the backend. Bye, Henning
[sane-devel] Preparation for sane-backends release 1.0.18
Hi, On 2006-04-18 18:26, Julien BLACHE wrote: hp_rts88xx Has been running fine in libsane-extras for ages, no problems that I know of. It seems that hp_rts88xx supports the HP3500 scanners, and so does the hp3500 backend. Is it the case ? (the hp3500 scanner is listed in the comments at the top of the hp_rts88xx main source file) The code really seems to be designed also for the HP3500 scanners. However, the web site says, that they don'z work yet. Johannes, can you comment on this topic? We habe now a backend (hp3500) which works with these scanners. Can support in hp_rts88xx be disabled? Also, do you think your backend can go into SANE CVS for the next SANE release? Bye, Henning
SV: [sane-devel] Preparation for sane-backends release 1.0.18
Hi Karl Heinz, As mentioned on sane-devel, the countdown for a new sane-backends release is going to start in some weeks. There are some bug and wishlist reports for the epson backend, some even with patches on the bug tracker. Could you have a look at them? If you have very little time, I could try to make a cumulative patch for the epson backend containig all the patches and send it to you for review. Lis of bugs: https://alioth.debian.org/tracker/index.php?func=detailaid=303342group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=303341group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=303340group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=303321group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=303269group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=302412group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=302146group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=301926group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=301795group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=301581group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=301478group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=300987group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=300977group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=300572group_id=30186atid=410366 https://alioth.debian.org/tracker/index.php?func=detailaid=300179group_id=30186atid=410366 Some of the bugs may be bogus or fixed meanwhile. Bye, Henning On 2006-04-19 14:34, Claus Boje wrote: I intend to start the countdown for the release of sane-backends 1.0.18 in a few weeks. So it's now the right time to include any big changes into sane-backends that are available. Especially big updates of existing backends and new backends should be included in the following weeks. I have not heard anything about my patch for the epson perfection 4990 (se bug 302090). Bye Claus Boje -- 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] Backend driver for Canon CanoScan 4200f
Hi, On 2006-04-19 12:17, David S. Yoder wrote: If not, I'm willing to try (I have sufficient programming experience) but have no experience in developing drivers for Linux, so I will need some guidance in order to comply with the SANE group's guidelines/principles/rules. http://www.sane-project.org/contrib.html Concerning retrieving/storing source from/to CVS, I have no experience, so again there is a need for help. Is there a document providing the necessary steps? http://www.sane-project.org/cvs.html I have a dual boot with Windows 2000 Pro and SuSE 9.3, the scanner is (of course) a CanoScan 4200f. Is there a tool for searching the Archives for info about scanner chips, etc.? The sane-devel mailing list has a search engine. However, ususally I put all information about a scanner on the scanner's web page. But I may have missed something. Bye, Henning
[sane-devel] Preparation for sane-backends release 1.0.18
Hi, On 2006-04-19 11:31, Wittawat Yamwong wrote: The pixma backend in the current version is not ready to be included in sane-backends yet. Many things in the source code needs to be cleaned, e.g. naming convention for global symbols, license, coding style etc. I will look at the code and give you an definitive answer on this weekend. There are still some weeks left so there is no need to make any decision now. I just wanted to give a little warning before actuall making the time table. Also the main criteria for inclusion of a backend are that it does something useful (status minimal is enough), that it doesn't destroy hardware, that it doesn't harm any other backends, that it builds without trouble and that it conforms to the rules in doc/bsackend-writing.txt. A backend does not need to be perfect before it's included :-) Bye, Henning
[sane-devel] Preparation for sane-backends release 1.0.18
Hi, On 2006-04-18 20:21, JKD wrote: hp3900 The fifth release (0.5) of this backend is still in alpha status. It seems to work well with normal/reflective scans in 8 and 16 bit depth and provides colour, gray and lineart modes (gray and lineart emulated in the backend yet) but slide/negative scans don't work properly and sometimes the scanner behaviour forces user to reset device. IMHO the backend is not ready to include in sane-backends. There are still some weeks left for improvement :-) I had a quick look at the package. It compiles fine for me and I couldn't find any fundamental problem when looking at the code. The only thing is: make libcheck says: Libraries exporting 'illegal' symbols: *** backend/.libs/libsane-hp3900.a: D use_gamma_tables Libraries exporting 'non-standard sane_*' symbols: *** backend/.libs/libsane-epson.a: 52d0 T sane_auto_eject Bye, Henning
[sane-devel] Live preview while scanning possible? (lide 60)
Hi, On 2006-04-18 08:51, Yuri Pozzi wrote: is possible to view the image creating while scanning on the lide 60 driver? I've used Vuescan and does it, it would be very useful for my needs. The preview itself is continuously updated (at least with the LiDe 50, which I just tested). As far as i know no SANE frontend does the same when doing a real scan. From the SANE api, this is possible as the scanned data is continuously read by the frontend. So it's just that nobody has implemented that feature yet. Another question, if I do BW scans on sane they don't have much depth instead on Vuescan they have much more greys, is this fixed in the last version of sane? I guess this is about gray mode (not lineart)? With the Lide 50 it looks like this for me (xsane, no gamma/brightness/contrast corrections): http://www.meier-geinitz.de/sane/tmp/gray.png I.e. the darkest four blacks look the same. However, I have no comparison how Windows or Vuescan does this. Bye, Henning
[sane-devel] usb_set_interface and usb_claim_interface
Hi, On 2006-04-17 09:07, Tamkang wrote: Does anyone know why the position of usb_set_interface before usb_claim_interface, get return -1 ? As far as I know there is no libusb function called usb_set_interface. If you refer to usb_set_altinterface, you really must claim the interface before. Using an alternative interface is just a different way of using the same interface so it is blocked by the access. because I am trying to developing driver sm3880 for sane-backend, and I got this I/O Device Error, but I got fixed after, I reverse the usb_claim_interface is on behind, after usb_set_interface function got return 0, any one know why? I highly recommend to use the SANEI wrapper functions in sanei/sanei_usb.c for SANE backends instead of using libusb directly. At least with normal USB devices this makes life a little bit easier for you (and us, because it reduces porting issues). So you write a backend for the Microtek Scanmaker 3880? This scanner is not yet in our list. Could you give more details, e.g. the output of sane-find-scanner -v -v and if the scanner uses the same chipset as the 3800 or some other scanner. Bye, Henning
[sane-devel] Canon LiDE 25 is not working
Hi, On 2006-04-18 08:58, Parag N() wrote: I didn't get you. When i search archive i found that i need to pass --disable-locking to ./configure command which i did. but still scanimage image.pnm shows blackwhite strips in image. Some scanners have a hardware lock mechanism. This switch is usually on the bottom side of the scanner. If it's enabled, the scan head can't move. It's intended for transporting the scanner to avoid destroing the scan head. If this mechanism also exists in your scanner and it's enabled the scan head will not move even if SANE tries to move it. Bye, Henning
[sane-devel] Re: CanoScan LiDE20 jamming with scanimage
Hi, On 2006-04-17 22:37, Fibonacci Prower wrote: Third update: I uninstalled all packages whose name contained the string sane, downloaded the sources from ftp://ftp.sane-project.org/pub/sane/ for both frontends and backends, compiled them, installed them, ran xscanimage... And my scanner still jams. Maybe a problem with the USB part of the kernel used by your distribution? If you have a choice, try a different kernel. Bye, Henning
[sane-devel] Added USB vendor and product ids to all backends, PLEASE CHECK!
Hi everybody, I just committed the last batch of .desc files to CVS. All USB backend .desc files which are included in sane-backends now contain USB vendor and product ids. Some ids are still missing, I'll psot a list later. Backend maintainers: Please check if everything is correct. As I don't know most of the devices, I had to guess the ids from the man pages, config files, web sites and the code itsself. These files were changed today: avision.desc (regenerated with modified version of avision-desc.sh) epson.desc fujitsu.desc hp.desc plustek.desc (also some splitted entries and changed one comment) u12.desc umax.desc Bye, Henning
[sane-devel] Missing USB vendor and product ids, please help!
Hi everybody! I checked our lists and for the following scanners I can't find the correct USB vendor and product ids. If you own such a device or know the ids, please send them to me. Jsut run sane-find-scanner to find out the id. *** Backends included into the sane-backends distribution: epson.desc (Epson DX-3850) fujitsu.desc (Fujitsu fi-4530C) hp5400.desc (Hewlett-Packard ScanJet 5490c) snapscan.desc (AGFA SnapScan e60) umax.desc (UMAX Astra MX3) *** External backends epkowa.desc (EPSON CC-500L) epkowa.desc (EPSON CC-550L) epkowa.desc (EPSON CC-700) epkowa.desc (EPSON F-3200) epkowa.desc (EPSON GT-7400U) epkowa.desc (EPSON GT-8400UF) epkowa.desc (EPSON Stylus CX1500) viceo.desc (IBM IdeaScan 2000 USB) samsung.desc (Samsung SCX-4016) samsung.desc (Samsung SCX-4720F) samsung.desc (Samsung SCX-6220) samsung.desc (Samsung SCX-6320F) samsung.desc (Samsung SF-565P) samsung.desc (Samsung SF-755P) *** Unsupported scanners: unsupported.desc (Avision iVina FB2400) unsupported.desc (C-Channel MyPen Pro) unsupported.desc (C-Channel MoneyPen II) unsupported.desc (Canon IS 12) unsupported.desc (Canon IS 52) unsupported.desc (Epson ) unsupported.desc (Epson ) unsupported.desc (Fujitsu fi-4110EOX2) unsupported.desc (Hewlett-Packard Photosmart 1200 Photo) unsupported.desc (Lexmark X5150) unsupported.desc (Microtek ArtixScan 4000tf) unsupported.desc (Mustek 2400 M) unsupported.desc (Mustek ScanExpress CardSmart) unsupported.desc (Panasonic KV-S2026C) unsupported.desc (Panasonic KV-S2046C) unsupported.desc (Panasonic KV-S2055W) unsupported.desc (Panasonic KV-S3065CW) unsupported.desc (Panasonic KV-S3065CL) unsupported.desc (Panasonic KV-S3085) unsupported.desc (Panasonic KV-S3105C) unsupported.desc (Panasonic KV-S7065C) unsupported.desc (PIE Primefilm 3600PRO) unsupported.desc (Plustek OpticPro A3U) unsupported.desc (Plustek OpticPro S6) unsupported.desc (Plustek OpticPro UA18) unsupported.desc (Plustek OpticPro ST64) unsupported.desc (Plustek OpticPro ST64+) unsupported.desc (Plustek OptiCard 600+) unsupported.desc (Primax Slim-Line 1200) unsupported.desc (Prolink Winscan Pro 2000) unsupported.desc (Quato X-Finity Ultra) unsupported.desc (SmartDisk SmartScan 3600) unsupported.desc (UMAX Astra 4600) unsupported.desc (UMAX Astra 6700) unsupported.desc (UMAX Powerlook 180) unsupported.desc (UMAX Powerlook 1000 USB) unsupported.desc (Visioneer Onetouch 8900) Bye, Henning
[sane-devel] Preparation for sane-backends release 1.0.18
Hi developers! I intend to start the countdown for the release of sane-backends 1.0.18 in a few weeks. So it's now the right time to include any big changes into sane-backends that are available. Especially big updates of existing backends and new backends should be included in the following weeks. What's the status of the following external backends? Can they be included into sane-backends? Keep in mind that this gives you a much bigger audience and many more testers. cs3200f geniusvp2 hp3900 hp_rts88xx pixma stv680 What about the lexmark backend in experimental CVS? Can the code be imported into main CVS to get the Dell a)20 working? Bye, Henning
[sane-devel] Preparation for sane-backends release 1.0.18
Hi again, On 2006-04-18 17:54, Henning Meier-Geinitz wrote: I intend to start the countdown for the release of sane-backends 1.0.18 in a few weeks. So it's now the right time to include any big changes into sane-backends that are available. Especially big updates of existing backends and new backends should be included in the following weeks. One more question is about the status of the java api discussed some time ago on this list. Is it ok to remove the old japi code from sane-backends and add the new code to sane-frontends? Bye, henning
[sane-devel] Hotplug and udev files created automatically now, please test!
Hi everybody, In SANE CVS the creation of the files libsane.usermap, libsane.db and libsane.rules is now done automatically from the backends' description files. libsane.usermap is used by Linux hotplug (tools/hotplug/) libsane.db is used by Linux hotplug-ng (tools/hotplug-ng/) libsane.rules is used by Linux udev (tools/udev) All three files are mainly used to set permissions on the USB device files (e.g. /proc/bus/usb/001/002). The files contain the USb vendor and product ids of all devices supported by SANE (and some more unsupported ones). They are created automatically from the backends' description files using the tool sane-desc. sane-desc is also used to generate our scanner lists on the web site. Therefore, now the lists are in sync and USB ids have to be added only in one place when a new scanner is reported. I can only test hotplug-ng at the moment. This works for me. Please test if hotplug and udev work with the new files. Bye, henning
[sane-devel] Canon CanoScan LiDE 25 ID's
Hi, On 2006-04-05 14:48, Tijmen wrote: The Canon CanoScan LiDE 25's ID's are 04a9:2220 Thanks. The IDs of this scanner are already included in the development version of SANE. Bye, Henning
[sane-devel] FC 5 has problem when detecting sm 3600
Hi, On 2006-04-10 05:15, Tamkang wrote: I have a problem when want to debug the xsane to detect where the sm3600 was ? it appears no device ? first of all the xsane in /usr/bin/xsane it work, then if in /usr/local/bin/xsane, it cannot find out the scanner ? and I have question to ask , because fc5 is have no /etc/hotplug anymore, and is being replace /etc/udev/60-libsane.rules, I already see the sm3600 is already there, is it the xsane will always look the data in 60-libsane.rules to see the device is supported by xsane /sane ? but why in sane-find-scanner it cannot find out the scanner, neither the scanimage -L but the xsane in /usr/bin/xsane it can work normally ? First find out if it really is a permission problem. Run sane-find-scanner and scanimage -L as root. If that works but fails as normal user, it's a permission problem. Then check the way your distribution sets up permissions. sane-backends comes with some files for using with hotplug and udev, but they are not installed automatically. So usually the distribution package authors install these files. Documentation on how this works should come with your distribution. Bye, Henning
[sane-devel] Genius Colorpage Vivid 1200 X
Hi, On 2006-04-12 20:59, Roberson L. Brehm wrote: I have a little problem here, I try run sane in the Genius 1200X and they not find, I have buy this scanner but in the backends they have good status marked $ sane-find-scanner -q found USB scanner (vendor=0x0458, product=0x201d, chip=GT-6816?) at libusb:002:002 The question mark means that you haven't set up permissions correctly. Read README.linux and the documentation that comes with your distribution (e.g. on Debian, /usr/share/doc/libsane/README.Debian.gz). but no work I use Ubuntu Linux the 5.10, can send me a link to I solve this? my gt68xx.conf don't have this genius usb 0x0458 0x201d You need sane-backends 1.0.17 or newer. Bye, Henning
[sane-devel] Device addition to 60-libsane.rules
Hi,
On 2006-04-13 15:32, Eureka Trek wrote:
# Canon Inc.|LiDE 60
SYSFS{idVendor}==04a9, SYSFS{idProduct}==221c, SYMLINK+=scanner-%k
Thanks. The LiDE 60 is already in our lists in the development version
of SANE.
Bye,
Henning
[sane-devel] hp3500 vs. hp_rts88xx
Hi, On 2006-04-14 10:45, Julien BLACHE wrote: The hp3500 backend has been added to the CVS some time ago, supporting HP 3500 series scanners. However, the pre-existing hp_rts88xx backend also claims to support these scanners (and a couple of others, non-3500). It seems that the hp3500 backend has better support for the hardware than hp_rts88xx. Can somebody confirm ? According to the hp_rts8xx web site: HP35x00c scanners (RTS8801 chipset): this is today a development version and doesn't work today. I'm shipping hp_rts88xx as part of libsane-extras in Debian, and obviously I can't have 2 backends supporting the same hardware, so there's a choice to be made :) As the hp3500 backend was written to support the HP 3500 scanners (which is reported to work well) I'd disable the USB ids for those scanners in hp_rts88xx. Bye, Henning
[sane-devel] Backend and stand-alone utility for Canon PIXMA MP150/MP170
Hi, On 2006-04-16 02:17, Wittawat Yamwong wrote: I would like to announce a stand-alone utility and SANE backend for Canon PIXMA MP150/MP170. The software is still in alpha stage and far from complete, because I've no ?programming information about the device at all. Though, it should scan. ;-) The software should work for MP450 and MP500 too. Comments are welcome. Thanks, very nice. I added a pixma.desc file to the SANE CVS so there are links to your backend now: http://www.sane-project.org/lists/sane-backends-external.html#S-PIXMA Feel free to comment on the status levels I used for the scanners. Bye, Henning
