[sane-devel] HP 5300/6300 Transparency support
I've done some searching but can't seem to find an answer. Is the transparency adaptor for the HP 5300/6300/7400 scanner series supported by the sane drivers? I need a transparency scanner that can scan medium format negatives at the least. If the transparency adaptor is not supported, is anyone working on it, and what could I do to help? I haven't bought one of these yet, but if there is work ongoing I will, and would even contribute one to someone working on it. Thanks, Brian
[sane-devel] offtopic 35-mm scanner question
Miguel Bazdresch wrote: On 10/20/05, Alan Corey alanco...@yahoo.com wrote: I'd have to pretty much agree with breacher even though I'm not familiar with the Epson Perfection 2400 and I'm a newbie with SANE. I've got one flatbed scanner with a transparency adapter built in, and it makes me wonder why they bothered except as a marketing tactic. It's about useless. I have an Epson 2480 and I'm quite satisfied with it. I haven't used it for negatives, only slides; for many purposes the results are quite good. Some random thoughts: * Sane support is very good, but native support (in windows) is still better. In particular: The windows driver detects and crops the slide area; under sane, you have to manually crop the slide mount. The windows driver supports 16 bit per channel, and this really makes a difference for high-quality scans. * Having said that, working in xsane is infinitely more comfortable than the obnoxious Epson software under windows. * Flatbed scanning is slow. Not just the scan itself, but the process of placing the slides, cleaning the scan surface, opening and closing the lid it quickly adds up. If the archive is very large, the time savings of a batch scanner could be worth the extra money. * For a large archive, I'd even look into spending the money in having somebody else do the scanning, a large photo shop or somebody else who can do a high-quality job. In short, for web posting and small prints I find the 2480+sane to be an exceptionally good combination for the money. I'd like to comment on this also, as I am currently working on making the Canon CanoScan 8400F, work as a negative scanner in Linux. The thing with scanning in negatives is this, first due to the small size of negatives, in order to print of a decent picture requires considerable magnification. This is a lesser problem with medium format negatives. Negatives generally have a dpi resolution of around 3-5000. Hence you'll want nothing less than a 3200x3200 dpi capable scanner for decent output if you plan on printing anything over 4x6. Secondly, it will take you a very long time to scan in a collection with even a dedicated film scanner. Scans at high resolution are huge (100MB+) and slow. The best solution is to take your negatives to a professional and have them scanned and put on CD. It's much faster and possibly more cost effective. Thirdly, most of the windows software with the better quality film scanning scanners has lots of enhancement capabilities built in, that clean up negatives as they are scanned in. While this can be done in Linux after scanning, it is not trivial. So even if you get a professional quality scanner that works in Linux, the quality of the raw scans will likely be less than an equivalent in Windows. If I haven't yet deterred your interest, your best bet is to go with an Epson. Expect to pay around $200 - $400 for one that will be satisfactory for film scanning. There are a number of reviews on the Internet by photographers. Try googling for them. BTW, the CanoScan 8400F and 9950F can both create near original quality scans, unfortunately, neither works in Linux yet, and Canon is not Linux friendly. The Epson 4870 and 4990 are also very excellent. $0.02, Brian JD
[sane-devel] genesys backend
Pierre Willenbrock wrote: Brian J Densmore schrieb: Pierre Willenbrock wrote: I did a major restructuring on the gl841 part. You may want to take a look at that. Are you referring to the patch you created? I've already applied that. Essentially to add support for a gl841/gl842 based scanner you need to find out the motor acceleration curve and type(half-step, quarter step capable), ccd settings and analog frontend settings. Well as for the motor acceleration, I'm not sure I need to do anything there except use the code that the Medion 6228 uses. At least for resolution up to 2400 xdpi. I'm currently building a Windows machine with USB support so I can do some USB sniffing. I am still trying to get the datasheet for the GL843, I am hopeful of getting that from a tech at genesys soon. I'm sure the registers are different from the 842. Also the 8400 is eighth step capable. All of these can be obtained from an usb sniffer log, captured while the windows driver calibrates the scanner. I can help analyzing a sniffusb log. You will find the ccd settings struct to be missing the gl841 ccd clock settings. My scanner didn't need them, so i didn't add them. Just add more fields there, as needed. Transparent adapter support is completely missing. Any ideas on where I could steal some code from to try to make work. I've seen the registers in the 842 specs that need to be populated. If you'd like I could work on adding that to the existing scanners. Not sure if any of them are capable. We will need to add support for horizontal resolutions which do not directly map to one of the gl841 settings(600, 1200, 2400dpi). Using these settings the chip decides which memory layout to use, and how to treat the dpiset setting. Technically, in 2400dpi mode you can equip the scanner with a 43690 pixel ccd with arbitrary resolution, in 1200dpi mode half of that. I noticed you were using a 'non-supported' resolution on the LiDE. Why not not just use the resolutions that the GL84x are designed for? There is also the possibility of using the deletion type bit in the AVEENB register (bit 6 of reg 3)? That is the one you were talking about right? The 842 chip should have 1200,600,400,300,200,150,120,80 for a 1200 xdpi scanner, by setting registers 44 and 45 (0x2C, 0x2D) and clearing the AVEENB bit. I don't know what the bit settings are for those resolutions though. They aren't defined in the spec, that I can see. Thanks, Brian JD
[sane-devel] Genesys - CanoScan 8400F
My investigation of the CanoScan 8400F has so far found the following. -- chips : Scanner chip = GL843[1] I'm trying to get the datasheet on this. It's not downloadable yet that I can see. I'll use the 842 datasheet for now. I suspect the main differences between the 842 and 843 are increased memory support and increased resolution support. The 8400F supports 3200x6400 scanning and any transparency up to 6x22cm. Samsung K4S6411632H-UC75, 64Mb, 4Mb x 16 x 4 banks SDRAM = 8MB. [2] Wolfson WM8199CDS image digitizer [3] Allegro A3967SLB microstepping motor driver [4] Allegro L6219DS Dual full-bridge PWM motor driver. [5] A few other chips I didn't identify. -- cat /proc/bus/usb/devices : ... T: Bus=01 Lev=01 Prnt=01 Port=05 Cnt=01 Dev#= 29 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=04a9 ProdID=221e Rev= 4.00 S: Manufacturer=Canon S: Product=CanoScan C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 10mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=16ms sane-find-scanner output: ... device descriptor of 0x04a9/0x221e at 001:029 (Canon CanoScan) bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 255 bDeviceSubClass 255 bDeviceProtocol 255 bMaxPacketSize0 64 idVendor 0x04A9 idProduct 0x221E bcdDevice 4.00 iManufacturer 1 (Canon) iProduct 2 (CanoScan) 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 trying to find out which USB chip is used ... checking for GL646 ... this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL646_HP ... this is not a GL646_HP (bcdUSB = 0x200) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL841 ... This USB chip looks like a GL841 found USB scanner (vendor=0x04a9 [Canon], product=0x221e [CanoScan], chip=GL841) at libusb:001:029 ... -- ref: [1]http://www.genesyslogic.com/econtents/product02.asp?SN=48minicidx=3lastcidx=18 [2]http://www.samsung.com/Products/Semiconductor/DRAM/SDRAM/SDRAMcomponent/64Mbit/K4S641632H/K4S641632H.htm [3]http://www.wolfsonmicro.com/products/digital_imaging/WM8199/ [4]http://www.allegromicro.com/sf/3967/ [5]http://www.allegromicro.com/sf/6219/ I have datasheets for all but the GL843, or you can download them at the references listed above. -- Also, I'm asking for help. I'm doing something wrong, I'm sure. I can't seem to download the experimental code via cvs. I've followed the instruction on the alioth CVS page, but I get : Fatal error, aborting. anoncvs_sane: no such system user I have worked around this, but it's only a work-around. I'd like to know what I'm doing wrong. Sorry about the length. Thanks, Brian JD
[sane-devel] Genesys - CanoScan 8400F
My investigation of the CanoScan 8400F has so far found the following. -- chips : Scanner chip = GL843[1] I'm trying to get the datasheet on this. It's not downloadable yet that I can see. I'll use the 842 datasheet for now. I suspect the main differences between the 842 and 843 are increased memory support and increased resolution support. The 8400F supports 3200x6400 scanning and any transparency up to 6x22cm. Samsung K4S6411632H-UC75, 64Mb, 4Mb x 16 x 4 banks SDRAM = 8MB. [2] Wolfson WM8199CDS image digitizer [3] Allegro A3967SLB microstepping motor driver [4] Allegro L6219DS Dual full-bridge PWM motor driver. [5] A few other chips I didn't identify. -- cat /proc/bus/usb/devices : ... T: Bus=01 Lev=01 Prnt=01 Port=05 Cnt=01 Dev#= 29 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=04a9 ProdID=221e Rev= 4.00 S: Manufacturer=Canon S: Product=CanoScan C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 10mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=16ms sane-find-scanner output: ... device descriptor of 0x04a9/0x221e at 001:029 (Canon CanoScan) bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 255 bDeviceSubClass 255 bDeviceProtocol 255 bMaxPacketSize0 64 idVendor 0x04A9 idProduct 0x221E bcdDevice 4.00 iManufacturer 1 (Canon) iProduct 2 (CanoScan) 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 trying to find out which USB chip is used ... checking for GL646 ... this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL646_HP ... this is not a GL646_HP (bcdUSB = 0x200) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL841 ... This USB chip looks like a GL841 found USB scanner (vendor=0x04a9 [Canon], product=0x221e [CanoScan], chip=GL841) at libusb:001:029 ... -- ref: [1]http://www.genesyslogic.com/econtents/product02.asp?SN=48minicidx=3lastcidx=18 [2]http://www.samsung.com/Products/Semiconductor/DRAM/SDRAM/SDRAMcomponent/64Mbit/K4S641632H/K4S641632H.htm [3]http://www.wolfsonmicro.com/products/digital_imaging/WM8199/ [4]http://www.allegromicro.com/sf/3967/ [5]http://www.allegromicro.com/sf/6219/ I have datasheets for all but the GL843, or you can download them at the references listed above. -- Also, I'm asking for help. I'm doing something wrong, I'm sure. I can't seem to download the experimental code via cvs. I've followed the instruction on the alioth CVS page, but I get : Fatal error, aborting. anoncvs_sane: no such system user I have worked around this, but it's only a work-around. I'd like to know what I'm doing wrong. Sorry about the length. Thanks, Brian JD
[sane-devel] Genesys - CanoScan 8400F (pt2)
My investigation of the CanoScan 8400F has so far found the following. cat /proc/bus/usb/devices : ... T: Bus=01 Lev=01 Prnt=01 Port=05 Cnt=01 Dev#= 29 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=04a9 ProdID=221e Rev= 4.00 S: Manufacturer=Canon S: Product=CanoScan C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 10mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=16ms sane-find-scanner output: ... device descriptor of 0x04a9/0x221e at 001:029 (Canon CanoScan) bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 255 bDeviceSubClass 255 bDeviceProtocol 255 bMaxPacketSize0 64 idVendor 0x04A9 idProduct 0x221E bcdDevice 4.00 iManufacturer 1 (Canon) iProduct 2 (CanoScan) 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 trying to find out which USB chip is used ... checking for GL646 ... this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL646_HP ... this is not a GL646_HP (bcdUSB = 0x200) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL841 ... This USB chip looks like a GL841 found USB scanner (vendor=0x04a9 [Canon], product=0x221e [CanoScan], chip=GL841) at libusb:001:029 ... Brian JD
[sane-devel] Genesys - CanoScan 8400F (pt3)
My investigation of the CanoScan 8400F has so far found the following. -- ref: [1]http://www.genesyslogic.com/econtents/product02.asp?SN=48minicidx=3lastcidx=18 [2]http://www.samsung.com/Products/Semiconductor/DRAM/SDRAM/SDRAMcomponent/64Mbit/K4S641632H/K4S641632H.htm [3]http://www.wolfsonmicro.com/products/digital_imaging/WM8199/ [4]http://www.allegromicro.com/sf/3967/ [5]http://www.allegromicro.com/sf/6219/ I have datasheets for all but the GL843, or you can download them at the references listed above. -- Also, I'm asking for help. I'm doing something wrong, I'm sure. I can't seem to download the experimental code via cvs. I've followed the instruction on the alioth CVS page, but I get : Fatal error, aborting. anoncvs_sane: no such system user I have worked around this, but it's only a work-around. I'd like to know what I'm doing wrong. Sorry about the length. Thanks, Brian JD
[sane-devel] TWAIN 2.0 targetting Linux
Johannes Meixner wrote: Hello, On Oct 12 11:12 Ren? Rebe wrote (shortened): Maybe it's time someone works on making TWAIN applications for Linux? Why? SANE is the OSS cross platform API for Unix, Unix-a-like or even OS/2. Of course, but... Thanks all for educating me on the benefits of SANE over TWAIN. Actually, I'm just testing my ability to post here. My last five posts have not posted. Brian JD
[sane-devel] genesys backend
Pierre Willenbrock wrote: Pierre Willenbrock schrieb: The attached patch primarily adds yet another shading calibration method, using the black and white strips at the top of the scanning area. It also adds support for led exposure calibration needed for cis scanners and instant power saving features. I just checked that one in into experimental cvs. Full support for Canon LiDE 35/40/50 will follow shortly. Regards, Pierre Do you have any code that I could look at and use to add support for the 8400F and 9950F? Thanks, Brian JD
[sane-devel] Genesys - CanoScan 8400F
Brian J Densmore wrote: My investigation of the CanoScan 8400F has so far found the following. -- chips : ... Allegro A3967SLB microstepping motor driver. Allegro L6219DS Dual full-bridge PWM motor driver. My research on this chip tells me this is identical in function and logic to the 2916. Only the pinout is different. Sorry about the duplicate posts. Also on the CanoScan 9950F the product id for it is 0x2219. The CanoScan 9950F chip does not appear to be detected as a GL841 chip, it may be a GL846 and have a new register layout. Alternatively, upgrading the genesys driver might help. The scan was run on sane version 1.0.15. see output below (thanks to breacher): device descriptor of 0x04a9/0x2219 at 002:002 (Canon Scanner) bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 255 bDeviceSubClass 255 bDeviceProtocol 255 bMaxPacketSize0 64 idVendor 0x04A9 idProduct 0x2219 bcdDevice 3.01 iManufacturer 1 (Canon) iProduct 2 (Scanner) 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) 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 endpoint 2 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 3 (interrupt) wMaxPacketSize1 bInterval 8 ms bRefresh 0 bSynchAddress 0 trying to find out which USB chip is used checking for GT-6801 ... this is not a GT-6801 (bcdUSB = 0x200) ... checking for GL646 ... this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL646_HP ... this is not a GL646_HP (bcdUSB = 0x200) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL841 ... this is not a GL841 (reg 0x38 != 0x15) checking for ICM532B ... this is not a ICM532B (check 2, bcdUSB = 0x200) Couldn't determine the type of the USB chip found USB scanner (vendor=0x04a9 [Canon], product=0x2219 [Scanner]) at libusb:002:002 regards, brian jd
[sane-devel] Genesys driver chipsets
Is there a list of the different chips used by the various devices for the genesys driver? I've been searching the archives and unsupported pages to find them. I figure any chips that are identical between the different devices could be used rather than create duplicate entries. For example, I have added the CanoScan 8400F to the MOTOR_5345 motor, since it is the same chip. This might not be a correct choice as the 8400F has two motor controllers. I suppose I'll need to do some usb snooping to be sure. Brian JD
[sane-devel] help offer to support Canon 9950F
Breacher wrote: Hi, I subscribed to this list on Henning Meier-Geinitz' suggestion. I am the owner of a Canon CanoScan 9950F scanner, which i would like very much to be usable exclusively with (X)sane. It's an awesome scanner, 4800 dpi on hardware alone, with racks to scan an entire photo film, or 16 slides at once, ... For the genesys backend to support it without a developer to own such a device, i am willing to test stuff that a developer writes blindly and report how it works out. I'm ready to make online sessions with the developer with a ssh account on my Debian box. I will say on IRC what happens with the scanner as the developer tests it. So please, who is working on the genesys backend at the moment contact me to further this project. I believe supporting big scanners would bring even more credibility to Sane. Thanks Breacher I also am interested in getting these features working for the genesys backend. I have a Canon CanoScan 8400F, the little sibling to the 9950F. I am willing to test and develop. In fact I am beginning to work on modifying the existing genesys driver to support this scanner anyway. Thanks, Brian JD
[sane-devel] TWAIN 2.0 targetting Linux
Julien BLACHE wrote: St?phane VOLTZ stef...@modulonet.fr wrote: I believe this is a great thing. Some time in the future, people will be able to bought scanner with the software to have it run immediatly under linux. It is what most people (including me) want. A good point for the so-called 'linux desktop'. And you're completely WRONG. What drivers are you going to get with your scanner for Linux ? Binary-only i386 crappy proprietary drivers written in C++ ? 1. this won't help non-i386 users 2. there are no TWAIN applications for Linux (yet) 3. C++ means the drivers *WILL* be broken at some point by an ABI change (because, yes, that's going to happen AGAIN). 4. as the drivers will basically go unmaintained after a year, and the source won't be released anyway, you'll be stuck with an unusable scanner. Looks like an improvement to me, indeed. Did you read the code Mustek sent to Henning ? No ? You should. That's what you'll get with your scanner. I tend to agree with the previous poster, this will be a good thing. Not all proprietary drivers are crappy. Secondly, it's a step in the right direction. Expanded support for Linux isn't a bad thing. The drivers are, as you have noted, likely to be tied to a particular kernel/lib version of Linux. The drivers are also likely to be written specifically to a limited number of distros. While this is not likely to be helpful to many, it may be a starting point from which FOSS TWAIN applications can be written. As far as point 4 goes, there is nothing preventing anyone from having an alternate boot image for the older supported Linux version. At least then you'd be able to reboot to do your scanning. Were Canon to make a proprietary Linux driver for my 8400F (be still my heart), I'd download it in a flash. I welcome the day I can, buy a scanner and plug it in and have it work. I don't care if it is proprietary. As long as it works and doesn't trash my system. Maybe it's time someone works on making TWAIN applications for Linux? Me I'm too busy trying to modify the gl841 driver to support a CanoScan 8400F at max resolution with the transparency options, since no one seems to be working on it and the current developers haven't responded to my queries. Just so I can scan in some 70 year old medium format negatives.
[sane-devel] plustek_pp not working properly for 12000P
Henning Meier-Geinitz wrote: Hi, On Tue, Sep 13, 2005 at 03:39:20PM -0500, Brian J Densmore wrote: I am running a debian system with a manually compiled/installed 2.6.13 kernel. I've built the plustek pp kernel module and use that. Scanimage can't find the scanner, unless it is specified on a -d option, or via an environment default scanner setting. Is plustek_pp listed in dll.conf (and not commented out)? Yes, the dll.conf is set up correctly, but plustek_pp.conf wasn't. Everything is working fine now. Thanks, I checked those config files a dozen times and missed my mistake every time. Brian
[sane-devel] plustek_pp not working properly for 12000P
I am running a debian system with a manually compiled/installed 2.6.13 kernel. I've built the plustek pp kernel module and use that. Scanimage can't find the scanner, unless it is specified on a -d option, or via an environment default scanner setting. Scanning in only works in lineart or dithered modes. The gray and color modes produce only solid black output. Perhaps this is not the right forum for this, but this scanner worked in Mandrake, and obviously still works based on the dithered images. output of my /proc fs : brian:~$ cat /proc/pt_drv/device0/info Model : 12000P/96000P Portaddress : 0x378 Portmode: EPP (fast I/O, autodetect) Buttons : 0 Warmuptime : 0s Lamp timeout: 0s mov-switch : 0 I/O-delay : 0 CCD-Type: SONY Type TPA : no brian:~$ cat /proc/pt_drv/info Plustek Flatbed Scanner Driver version 0.43-7 Devices : 1 IOCTL-Version: 0x0104 Output of scanimage with a default device: brian:~$ export SANE_DEFAULT_DEVICE=plustek_pp:/dev/pt_drv0 brian:~$ scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). default device is `plustek_pp:/dev/pt_drv0' -- Output of scanimage with debugging turned on: root:/home/brian# scanimage [sanei_debug] Setting debug level of plustek_pp to 256. [plustek_pp] PlustekPP backend V0.43-7, part of sane-backends 1.0.16 [plustek_pp] # Plustek-PP SANE Backend configuration file [plustek_pp] # For use with Plustek parallel-port scanners [plustek_pp] # [plustek_pp] [plustek_pp] # [plustek_pp] # user either [direct] or [kernel] to access the scanner [plustek_pp] # when using [kernel], device specifies the device-node, which is created [plustek_pp] # by the kernel-module loader (applies only to Linux) [plustek_pp] # when using [direct], device is used to set the parallel-port base address [plustek_pp] # or a device-name suitable for libieee1284, i.e. parport0 [plustek_pp] # [plustek_pp] [direct] [plustek_pp] device 0x378 [plustek_pp] Decoding device name 0x378 [plustek_pp] [plustek_pp] # [plustek_pp] # leave the default values as specified in /etc/modules.conf [plustek_pp] # [plustek_pp] option warmup-1 [plustek_pp] Decoding option warmup [plustek_pp] option lOffOnEnd -1 [plustek_pp] Decoding option lOffOnEnd [plustek_pp] option lampOff -1 [plustek_pp] Decoding option lampOff [plustek_pp] [plustek_pp] # model override switch, mostly for cosmetic changes, if the autodetection [plustek_pp] # does not work or could not work correctly [plustek_pp] #option mov 7 [plustek_pp] [plustek_pp] # [plustek_pp] # example for accessing the scanner via libieee1284 [plustek_pp] # [plustek_pp] [direct] [plustek_pp] attach (0x378, 0xbfffc8c8, (nil)) [plustek_pp] Device configuration: [plustek_pp] device name : 0x378 [plustek_pp] direct I/O: yes [plustek_pp] warmup: -1s [plustek_pp] lampOff : -1 [plustek_pp] lampOffOnEnd : yes [plustek_pp] model override: 0 [plustek_pp] - [plustek_pp] drvopen() [plustek_pp] open: PtDrvInit failed: 4 [plustek_pp] open failed: -1 [plustek_pp] device 0x378 [plustek_pp] Decoding device name 0x378 [plustek_pp] #device parport0 [plustek_pp] [plustek_pp] # [plustek_pp] # example for accessing the scanner via the kernel module [plustek_pp] # [plustek_pp] #[kernel] [plustek_pp] device /dev/pt_drv0 [plustek_pp] Decoding device name /dev/pt_drv0 [plustek_pp] # [plustek_pp] #option warmup-1 [plustek_pp] #option lOffOnEnd -1 [plustek_pp] #option lampOff -1 [plustek_pp] attach (/dev/pt_drv0, 0xbfffc8c8, (nil)) [plustek_pp] Device configuration: [plustek_pp] device name : /dev/pt_drv0 [plustek_pp] direct I/O: yes [plustek_pp] warmup: -1s [plustek_pp] lampOff : -1 [plustek_pp] lampOffOnEnd : yes [plustek_pp] model override: 0 [plustek_pp] - [plustek_pp] drvopen() [plustek_pp] open: PtDrvInit failed: 4 [plustek_pp] open failed: -1 [plustek_pp] sane_open - /dev/pt_drv0 [plustek_pp] attach (/dev/pt_drv0, 0xbfffd8fc, 0xbfffe948) [plustek_pp] Device configuration: [plustek_pp] device name : [plustek_pp] direct I/O: no [plustek_pp] warmup: 0s [plustek_pp] lampOff : 0 [plustek_pp] lampOffOnEnd : no [plustek_pp] model override: 0 [plustek_pp] - [plustek_pp] drvopen() [plustek_pp] Scanner information: [plustek_pp] Vendor : Plustek [plustek_pp] Model : 12000P/96000P [plustek_pp] Asic : 0x10 [plustek_pp] Flags : 0x0200 [plustek_pp] drvclose() [plustek_pp] attach: model = 12000P/96000P [plustek_pp] Presetting Gamma tables (len=256) [plustek_pp] -- [plustek_pp] sane_start [plustek_pp] drvopen() [plustek_pp] scanmode = 3 [plustek_pp] bright 0 contrast
[sane-devel] genesys and gl841
First posting warning. I am a newbie to device drivers. I am interested in assisting in the development of a functioning driver for gl841 chipsets. I have a Canon 8400F and want to use it in Linux for scanning 35mm and medium format negatives at full 3200 resolution. Is there anyway I can help? I've scanned the archives and it looks as though the scanner is definitely not usable in Linux at present. Brian JD
