[sane-devel] Linoscan 1200 on Linux
Hello all! I'd like some advice on whether this scanner is usable under Linux. My sister brought the Heidelberg AG Linoscan 1200 back when her work chucked it out, and I thought I'd try and get it running under Linux (Ubuntu 7.10). It connects via USB, and lsusb gives: Bus 001 Device 002: ID 0a18:1030 Heidelberger Druckmaschinen AG However, xsane claims there are no devices available, and Google search hasn't turned up any evidence it works with sane. The only relevant links I can find are http://lists.alioth.debian.org/pipermail/sane-devel/2007-May/019180.html, where a user offered the scanner on this list for testing, and www.silverfast.com/forum/possible-mac-os-x-solution-for-linotype-scanners-t1265.html, where someone explains that the "LinoScan 1200 is a special problem under OS-X which is related to the USB communication chip". Don't know if that's relevant here or not. Can the Linoscan 1200 be used, or should I be looking for an alternative? I've exhausted my few hardware-investigating abilities, but would be happy to try suggestions. Thank you in advance, Ben
[sane-devel] saned: Permission problem on Fedora 8, Deskjet_F300_series all-in-one
On 1/2/08, Nick Urbanik wrote: > Dear Folks, > > I am having problems setting up saned on Fedora 8: > $ grep sane /var/log/rpmpkgs > libsane-hpaio-2.7.7-6.fc8.i386.rpm > sane-backends-1.0.18-17.fc8.i386.rpm > sane-backends-devel-1.0.18-17.fc8.i386.rpm > sane-backends-libs-1.0.18-17.fc8.i386.rpm > sane-frontends-1.0.14-3.fc7.i386.rpm > xsane-0.994-4.fc8.i386.rpm > xsane-gimp-0.994-4.fc8.i386.rpm > > I've created user and group saned. > $ grep saned /etc/passwd > saned:x:1020:1021:User to run saned scanner daemon only:/:/sbin/nologin > > When I do: > $ sudo -u saned sane-find-scanner |grep ^found > found USB scanner (vendor=0x03f0, product=0x5511) at libusb:003:004 > However, as myself, we also get the model information: > $ sane-find-scanner |grep ^found > found USB scanner (vendor=0x03f0 [HP], product=0x5511 [Deskjet F300 series]) > at > +libusb:003:004 > $ scanimage -L > device `hpaio:/usb/Deskjet_F300_series?serial=CN72FGM1CB04KH' is a > Hewlett-Packard Deskjet_F300_series all-in-one > And as the saned user, we get no biscuit: > $ sudo -u saned scanimage -L > > No scanners were identified. > > Here are the permissions: > $ ls -l /proc/bus/usb/003/004 > -rw-r--r-- 1 root root 147 2008-01-03 06:21 /proc/bus/usb/003/004 > $ cat /selinux/enforce 0 > > local scanning works fine for me. local scanning works fine as what user? the perms on that node dont allow anyone other than root to write to the device... allan -- "The truth is an offense, but not a sin"
[sane-devel] sp15c vs. avision backends
On 1/10/08, jazz_johnson at verizon.net wrote: > I decided to do some testing on the avision backend with the Fujitsu SP15C. > > The first major difference I've noticed, is that the avision backend > monopolizes the scanner so that only one program can use the scanner while > that program is running, i.e. the first user who runs xsane will see the > avision/sp15c backends listed, but after they select avision, if another user > then runs xsane, that user won't see that scanner (neither the avision nor > the sp15c backends will be listed). > > By contrast, one can run multiple xsane sessions with the sp15c backend. A > user can even run xsane on one desktop and also execute batch scanning from a > shell on another, which is very convenient. Imagine you have a pile of > documents, most of which can be scanned from a batch shell script without > user intervention, but interspersed throughout that pile are a handful of > pages which require manual adjustments to gamma/brightness/contrast/color. > It's convenient to keep xsane open on a desktop for interactively scanning > these few documents, but to do the bulk of the scanning from a > non-interactive shell script. And if other users also need to occasionally > scan something to email or to fax, they can do so from their own xsane > sessions without interrupting each other. > but only if they coordinate who's documents are on the scanner at that moment. some backends now implement a locking feature to prevent exactly this kind of access. it is made possible by the fact that sp15c.c closes the file handle at the end of attach, and does not re-open it til sane_start. this comment precedes the call to close: /* Why? */. Concurrent access is why, i suppose :) With backends that know how to read scanner sensors and buttons, this means a lot of opening and closing... allan -- "The truth is an offense, but not a sin"
[sane-devel] Artec E+pro almost working
if you can put a small pnm up on the web somewhere demonstrating the problem you might get more help, but it sounds like a calibration issue, which can be fairly specific to the chip involved, and without docs can be difficult to get right. allan On 1/9/08, Philip Aston wrote: > Listed as minimal support. > With the artec firmware 1200.usb installed, this scanner works with 2 > bugs: > 1 crashes @ 1200dpi, ok other resolutions- > 2 probably more important, there are slight discolorations, the colour > is reproduced but slightly darker, running vertically every 5mm, giving > an impression of vertical lines. This is OK for text but not for photos. > I am a new-ish Linux user & would like to work on this although have no > knowledge as yet... would anyone be able to suggest something/ offer > assistance? I note that a previous user had the same problem with this > scanner so I assume the fault is not with my computer or scanner.-Phil > > > -- > 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 > -- "The truth is an offense, but not a sin"
[sane-devel] Printer Canon MP 140 not acknowledged by Xsane
if you put these usb ids into our search engine at: http://www.sane-project.org/cgi-bin/driver.pl you will see that canon has recently released a closed-source driver for this scanner, but it is untested. If you would rather an open-source driver, you might have to 'scratch your own itch' by writing some code yourself, or finding a programmer willing to do it. allan On 1/10/08, arnaudhmail-mailbox at yahoo.fr wrote: > Good morning, > > After several researches on Internet, I discovered that the printer Canon > MP 140 is not acknowledged by Xsane. It is not useful under Linux. Can you > make sure that it is useful by the software of numeration Xsane and Kooka in > future? > > > Thank you. > > For your information: usb ID: 04a9:172b Canon, Inc > > > > > > Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! > Mail > > > -- > 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 > -- "The truth is an offense, but not a sin"
[sane-devel] Linoscan 1200 on Linux
easiest thing to do is to open the scanner and get logos and numbers off the larger chips. second easiest is to take a trace under windows using benoit's usbsnoop, put it on the web, and post a link on this list. if you are lucky, someone here might recognize the protocol. allan On 1/10/08, Ben F-W wrote: > Hello all! I'd like some advice on whether this scanner is usable under > Linux. > > My sister brought the Heidelberg AG Linoscan 1200 back when her work > chucked it out, and I thought I'd try and get it running under Linux > (Ubuntu 7.10). It connects via USB, and lsusb gives: > Bus 001 Device 002: ID 0a18:1030 Heidelberger Druckmaschinen AG > > However, xsane claims there are no devices available, and Google search > hasn't turned up any evidence it works with sane. The only relevant > links I can find are > http://lists.alioth.debian.org/pipermail/sane-devel/2007-May/019180.html, > where a user offered the scanner on this list for testing, and > www.silverfast.com/forum/possible-mac-os-x-solution-for-linotype-scanners-t1265.html, > > where someone explains that the "LinoScan 1200 is a special problem > under OS-X which is related to the USB communication chip". Don't know > if that's relevant here or not. > > Can the Linoscan 1200 be used, or should I be looking for an > alternative? I've exhausted my few hardware-investigating abilities, but > would be happy to try suggestions. > > Thank you in advance, > > Ben > > -- > 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 > -- "The truth is an offense, but not a sin"
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'slashbeast at jid.pl' 2. Manufacturer (e.g. "Mustek"): 'HP' 3. Model name (e.g. ScanExpress 1200UB): 'G4010' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x03f0' 6. Product id (e.g. 0x0002): '0x4505' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): '> if you own an unsupported scanner, please send as much information as possible. Roger. i send lsusb -vv and sane-find-scanner -v -v on my Current testing (~amd64) Gentoo.' 9. Data (e.g. sane-find-scanner -v -v): 'jinchuuriki slashbeast # lsusb -vv Bus 002 Device 006: ID 03f0:4505 Hewlett-Packard Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize064 idVendor 0x03f0 Hewlett-Packard idProduct 0x4505 bcdDevice5.00 iManufacturer 1 Hewlett-Packard iProduct3 HP Scanjet G4000 Photo series iSerial12 CN6CQA660004 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 10mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 8 jinchuuriki slashbeast # 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) checki
[sane-devel] sp15c vs. avision backends
I decided to do some testing on the avision backend with the Fujitsu SP15C. The first major difference I've noticed, is that the avision backend monopolizes the scanner so that only one program can use the scanner while that program is running, i.e. the first user who runs xsane will see the avision/sp15c backends listed, but after they select avision, if another user then runs xsane, that user won't see that scanner (neither the avision nor the sp15c backends will be listed). By contrast, one can run multiple xsane sessions with the sp15c backend. A user can even run xsane on one desktop and also execute batch scanning from a shell on another, which is very convenient. Imagine you have a pile of documents, most of which can be scanned from a batch shell script without user intervention, but interspersed throughout that pile are a handful of pages which require manual adjustments to gamma/brightness/contrast/color. It's convenient to keep xsane open on a desktop for interactively scanning these few documents, but to do the bulk of the scanning from a non-interactive shell script. And if other users also need to occasionally scan something to email or to fax, they can do so from their own xsane sessions without interrupting each other. --- Jeremy
