[sane-devel] Epson CX5500 without the non-free libs.
On Wednesday 20 August 2008 23:08, m. allan noah wrote: 2008/8/19 Vital Mission Software guru at vitalmis.com: I have posted my problem to the AVASYS message board. In the meantime, is there any alternative way of getting this scanner to work. Perhaps hire someone to reverse engineer this scanner, I could do the reverse engineering myself, I was looking for something I could do a little more quickly. or (faster and less expensive) buy a different one. Already have another one, a Canon LiDE 80. But that's not supported either and it's been on the unsupported list since 2007-01-28. Are then any supported scanners that are currently available? It doesn't look like it. However, LiDE 80 looks like it may be easier to get going than the CX5500, so if someone could point me to the appropriate documentation I could perhaps bring it into the supported list. Keith Harwood. -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080821/83e8dec2/attachment.pgp
[sane-devel] SANE does not recognize my Epson CX-3900 anymore
Hi friends
I've just reinstalled my system and can't make work SANE again with my Epson
CX-3900
My scanner is 100% supported and was running on Slackware 12 (now 12.1), all
installation procedure for MY scanner was stored in a text file so I don't
forget it (have reinstalled it several times before)...
First installed backend (x.19), then frontends (x.14?) and finally xsane 0.995,
it is installed as usual at /usr/local, the configuration I use always is this:
/usr/local/etc/sane.d/epson.conf:
# SCSI scanner:
# *** all scsi was commented ***
#
# USB scanner:
# There are two different methods of configuring a USB scanner: libusb and the
kernel module
# For any system with libusb support (which is pretty much any recent Linux
distribution) the
# following line is sufficient. This however assumes that the connected scanner
(or to be more
# accurate, it's device ID) is known to the backend.
usb
# For libusb support for unknown scanners use the following command
# usb product ID device ID
#found USB scanner (vendor=0x04b8 [EPSON], product=0x082f [USB MFP]) at
libusb:002:002
usb 0x04b8 0x082f
/etc/udev/rules.d/45-libsane.rules:
# Epson CX3900
SYSFS{idVendor}==04b8, SYSFS{idProduct}==082f, MODE=664, GROUP=scanner
and everything used to work, but this time does not... the only change on the
system was that I used Slackware 12.0 and now 12.1, kernel configuration is the
same...
I read an article on internet that somebody had troubles when 'usblp' module
was loaded (it loads on my system when the scanner is plugged)... tried again
unloading the module before running xsane but still no scanning device is
detected...
The scanner is working on windows, so it is not the problem... I think it may
be some library incompatibility but 't can't find nothing yet...
Any suggestion?
Thanks!
_
Connect to the next generation of MSN Messenger?
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-ussource=wlmailtagline
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080821/11eb2712/attachment.htm
[sane-devel] SANE does not recognize my Epson CX-3900 anymore
Kanito 73 kanito73 at hotmail.com writes:
Hi friends
I've just reinstalled my system and can't make work SANE again with
my Epson CX-3900
My scanner is 100% supported and was running on Slackware 12 (now
12.1), all installation procedure for MY scanner was stored in a
text file so I don't forget it (have reinstalled it several times
before)...
Disclaimer: not familiar with Slackware.
First installed backend (x.19), then frontends (x.14?) and finally
xsane 0.995, it is installed as usual at /usr/local, the
configuration I use always is this:
All of the above lives in /usr/local? Any SANE bits living somewhere
else on your system, like say in /usr/lib/sane/ or /etc/sane.d/?
/usr/local/etc/sane.d/epson.conf:
# SCSI scanner:
# *** all scsi was commented ***
#
# USB scanner:
# There are two different methods of configuring a USB scanner: libusb and
the kernel module
# For any system with libusb support (which is pretty much any recent Linux
distribution) the
# following line is sufficient. This however assumes that the connected
scanner (or to be more
# accurate, it's device ID) is known to the backend.
usb
# For libusb support for unknown scanners use the following command
# usb product ID device ID
#found USB scanner (vendor=0x04b8 [EPSON], product=0x082f [USB MFP]) at
libusb:002:002
usb 0x04b8 0x082f
^
Is this in your epson.conf? It should not be necessary.
/etc/udev/rules.d/45-libsane.rules:
# Epson CX3900
SYSFS{idVendor}==04b8, SYSFS{idProduct}==082f, MODE=664, GROUP=scanner
Does the scanner group exist on your system? Are you a member of that
group? If not, that might be the problem.
and everything used to work, but this time does not... the only
change on the system was that I used Slackware 12.0 and now 12.1,
kernel configuration is the same...
I read an article on internet that somebody had troubles when
'usblp' module was loaded (it loads on my system when the scanner is
plugged)... tried again unloading the module before running xsane
but still no scanning device is detected...
The usblp module is known to cause problems with some of the Epson MFP
devices but AFAIK not with any of the all-in-ones like your CX3900.
The scanner is working on windows, so it is not the problem... I
think it may be some library incompatibility but 't can't find
nothing yet...
Any suggestion?
Does your /etc/ld.so.conf include some reference to a lib/sane
directory? It shouldn't. Remove and run `ldconfig` to fix.
Otherwise, some debugging info might help.
Hope that helps,
--
Olaf Meeuwissen FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962 sign up at http://member.fsf.org/
[sane-devel] LiDE 90
Hello, Thank you for answer Pierre. Some questions again ! Hi Guillaume, Guillaume Gastebois schrieb: Hello, I'm back with my LiDE 90 ! I see in my windows logs the following sequence for gpios (reg 0x6C) : 02 12 0e 1a 0a 0e/3e (3e for half ccd log) (seems to be scanning moment) 0e 0a 0e/3e (3e for half ccd log) 02 Did you see some GPIO sequences necessary like with your lide 35 scanner ? With tests I identifies GPIO11 as home switch (with 1 scanner doesn't see home position any more) and GPIO14 as half CCD. But it doesn't seems to be so simple. Why windows driver plays with home switch ? The home switch is of the photoelectric variety most of the time, so switching it off saves a few milli Amperes. OK I can let GPIO11 to 0 (not interested to save few mA for the moment !!!) Why did I have half image with GPIO13/14 to 0 ? That question cannot be answered without knowledge of the actual electrical connections. I'd just accept the fact that GPIO13/14 needs to be switched together. In one 1200dpi log, I get the value 0x22 for reg 0x6C. (but I'm not sure of this log). Subsidiary question : where in the code to play to modify default 0x6C register value before calibration, before scanning and after scanning ? So you think that I just have to find the good value and let it from begining to the end the same ? Why windows driver plays with reg 0x6C ? The genesys_gl841-part unifies the setup for calibration scans and regular scans. The mid level functions get a set of parameters describing what, where and how to scan, and setup everything for that. Those functions are: gl841_init_motor_regs_off, gl841_init_motor_regs, gl841_init_motor_regs_scan for the motor control part, gl841_init_optical_regs_off, gl841_init_optical_regs_scan for the optical control part. gl841_init_scan_regs and gl841_feed pose as frontends for these functions. Before scanning, each of the mid level functions sets the bits that control parts of the scanner relating to the given function. For example, gl841_init_optical_regs_scan sets the bits needed for half-ccd mode, while gl841_init_motor_regs_scan will be responsible to setup a given motor power mode. OK It answers my question about changing 0x6C value ? If you really need to do things differently for calibration and regular scanning(which i doubt), you need to look at gl841_init_regs_for_coarse_calibration, gl841_init_regs_for_shading, gl841_init_regs_for_scan, gl841_offset_calibration, gl841_coarse_gain_calibration, gl841_led_calibration. IIRC the init_regs functions are called before the actual action is done, and the resulting register set is directly written to the scanner. The actual calibration happens in the other functions, using or not using the previously setup registers. All of these call gl841_init_scan_regs and gl841_feed to get their work done, but the register set can be modified after that call. The initial bit-fiddling (if needed) happens in gl841_init_registers, starting off from the values stored in genesys_devices.c: static Genesys_Gpo Gpo[]. Regards Guillaume Regards, Pierre Regards Guillaume
[sane-devel] SANE 1.0.19 does not find CX3900, 1.0.18 works but...
Hi again
I reinstalled many times backend 1.0.19, frontend 1.0.14 and xsane 0.995 but
was unable to make it work with my Epson CX3900... Just to try removed latest
version and installed the previous backend 1.0.18 and xsane 0.994 and now it
recognizes the scanner and works fine, but now I have another problem, can't
scan as normal user since the device is not found, as root it works...
I spent all day reading documentation, faqs, troubleshootings, forums, etc. and
am almost sure the installation and setup is correct...
/etc/udev/rules.d/45-libsane.rules
# Epson DX 4000
SYSFS{idVendor}==04b8, SYSFS{idProduct}==082f, MODE=664, GROUP=scanner
/usr/local/etc/sane.d/epson.conf
---
# epson.conf
#
# here are some examples for how to configure the EPSON backend
#
# SCSI scanner:
scsi EPSON
# for the GT-6500:
scsi EPSON SC
#
# Parallel port scanner:
#pio 0x278
#pio 0x378
#pio 0x3BC
#
# USB scanner:
# There are two different methods of configuring a USB scanner: libusb and the
kernel module
# For any system with libusb support (which is pretty much any recent Linux
distribution) the
# following line is sufficient. This however assumes that the connected scanner
(or to be more
# accurate, it's device ID) is known to the backend.
usb
# For libusb support for unknown scanners use the following command
# usb
# e.g.:
# usb 0x4b8 0x110
# And for the scanner module, use the following configuration:
#usb /dev/usbscanner0
#usb /dev/usb/scanner0
usb 0x04b8 0x082f
/etc/group
-
...
scanner:x:93:install,testuser
...
// install is not a system related user, just created it to test the programs,
testuser too
Well, as I said the problem is that can't use the scanner as normal user, the
rule entry in the udev configuration seems not to work, when the scanner is
plugged the created device at /proc/bus/usb (generally 001:002 or 002:002) has
root as owner and root as group too with permission rw-r--r--!!! If I
change the permission by hand to rw-rw-rw makes no difference scanner is still
not found, then if I try to make 'chown root.scanner' so it appears like this:
rw-rw-rw- root scanner 002
but normal user is unable to use xsane, 'scanimage -L' works only as root and
can't do nothing, udev entry does not work, setting permissions and group by
hand does not work, anything allows normal users to access scanner...
Please help me don't know what else to do!!! :(
_
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+worldmkt=en-USform=QBRE
[sane-devel] Canon MF4140
Jean-Nicolas,
There seems to be a lot of confusion.
Daniel seems to also have the same unit but must be having separate
problems from me. He is NOT answering for me.
Let me repeat my situation.
I am running on Mac 10.5. I have used both Mattias Ellert's pre-built
binaries for mac, as well as building the sane package myself.
This is from sane-find-scanner.
found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x26a3
[MF4100]) at libusb:003:004-04a9-26a3-00-00
And scanimage -L reports
device `pixma:04A926A3_SDF7Z0155773B' is a CANON Canon imageCLASS
MF4150 multi-function peripheral
When I attempt to execute scanimage -T, it tries to read the first
scanline and freezes.
Now udev is definitely NOT running on my machine. the GREP output is
misleading, because it shows my GREP process looking for the term
udev. If I export the output of ps -A to a file, udev does not exist.
But as I said, there IS a /usr/local/etc/udev/rules.d/libsane.rules
that exists and it has the proper listing for the 4150. I had to
manually move the .rules file as it was created in my build but didn't
transfer to /usr/local/etc/udev/rules.d/ that did already exist.
So my question is, When/how does udev get created? Should it be
created by the build? Might I have used the wrong parameters in the
configure command?
I used ./configure --prefix=/usr/local --sysconfdir=/usr/local/etc
Does this make things clearer?
bob
On Aug 21, 2008, at 1:42 AM, Jean-Nicolas Gautier wrote:
Hello,
I don't understand, do you have line called udevd when you type ps -
A in a concole?
What is your distribution (ubuntu, suse,mandriva, ...)?
Personally (a slackware distribution) I have a file called rc.udev
in folder /etc/rc.d ; this file must be executable in order to start
udev at boot.
Do you have this file somewhere in /etc/* ? You can check if the
file is executable by doing ls -l /path/to/your/file . It must give
something like :
-rwxr-xr-x 1 root root 3920 2008-05-07 14:50 /etc/rc.d/rc.udev*
Bob Dronski a ?crit :
First of all, thanks to the both of you for replying. I really
want to keep this unit, and I was worried when I heard nothing for
a few days.
Well, I did find a copy of libsane.rules in my build and it DID
have the listing Daniel mentioned. I manually moved the file into
the empty udev folder. But udev doesn't seem to be running
12947 ttys0010:00.00 grep udev
Where would I find it? Did I have to do something special in the
build?
Thanks,
bob
On Aug 20, 2008, at 9:56 AM, Jean-Nicolas Gautier wrote:
You must verify that udev is running, do ps -A | grep udev in a
console. It must give something like : 1049 ? 00:00:00 udevd
Then you can verify that the user who try to use the scanner
belong to
the scanner group. Do grep scanner /etc/* in a console, it
must give
something like : /etc/group:scanner::93:root,users
Daniel Stender a ?crit :
Canon MF4140 (Laserprinter/Scanner/Fax)
found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x26a3
[MF4100]) at libusb:002:002 but scanimage -L fails
Found on the net: http://ubuntuforums.org/showthread.php?t=878966
- by adding SYSFS{idVendor}==04a9, SYSFS{idProduct}==26a3,
MODE=0664, GROUP=scanner to libsane.rules the thing should
run: device `pixma:04A926A3_SDF680281822B' is a CANON Canon
imageCLASS MF4150 multi-function peripheral
but it doesn't (backends 1.0.19). Any ideas (hacks, workarounds,
modifying pixma backend?)
Greetings, Daniel Stender
--
Jean-Nicolas Gautier
28, rue Pelletier
1030 Schaerbeek
T?l.: 02/ 742 09 92
GSM : 0494/ 84 14 59
Please, consider your environmental responsibility before
printing this email.
--
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
--
Jean-Nicolas Gautier
28, rue Pelletier
1030 Schaerbeek
T?l.: 02/ 742 09 92
GSM : 0494/ 84 14 59
Please, consider your environmental responsibility before printing
this email.
[sane-devel] Canon MF4140
On Thu, Aug 21, 2008 at 10:41 AM, Bob Dronski dronski at gmail.com wrote: Jean-Nicolas, There seems to be a lot of confusion. Daniel seems to also have the same unit but must be having separate problems from me. He is NOT answering for me. Let me repeat my situation. I am running on Mac 10.5. I have used both Mattias Ellert's pre-built binaries for mac, as well as building the sane package myself. This is from sane-find-scanner. found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x26a3 [MF4100]) at libusb:003:004-04a9-26a3-00-00 And scanimage -L reports device `pixma:04A926A3_SDF7Z0155773B' is a CANON Canon imageCLASS MF4150 multi-function peripheral When I attempt to execute scanimage -T, it tries to read the first scanline and freezes. Now udev is definitely NOT running on my machine. the GREP output is misleading, because it shows my GREP process looking for the term udev. If I export the output of ps -A to a file, udev does not exist. But as I said, there IS a /usr/local/etc/udev/rules.d/libsane.rules that exists and it has the proper listing for the 4150. I had to manually move the .rules file as it was created in my build but didn't transfer to /usr/local/etc/udev/rules.d/ that did already exist. So my question is, When/how does udev get created? Should it be created by the build? Might I have used the wrong parameters in the configure command? I used ./configure --prefix=/usr/local --sysconfdir=/usr/local/etc udev is a linux-only device manager thing. it is only used by sane to set permissions on devices so that non-root users can scan. therefore, all users that have difficulty scanning should try as root user first. if root cannot scan, permissions (and hence, udev) are likely NOT the problem. i see no evidence that this backend supports this scanner, other than similarity of name to other, supported models. It might require only a minor tweak to a config file, or it might take a completely new backend, depending on how similar it is to existing models. allan -- The truth is an offense, but not a sin
[sane-devel] Canon MF4140
Allan, Thanks for clearing up the udev confusion. I guess that's why I had a problem finding info on it. I do understand that my model may not be supported. But according to the pixma help page --- The following models may use the same Pixma protocol as those listed above, but have not yet been reported to work (or not). They are declared in the backend so that they get recognized and activated. Feedback in the Sane-dev mailing list welcome. PIXMA MP740 ImageCLASS MF3110, MF3240, MF4150 ImageCLASS MF5630, MF5650, MF5730, MF5750, MF5770, MF8170c -- So I was attempting to follow the recommendations. Hopefully Nicolas might be able to tell me if it's worth pursuing upon his return. I have until next Thursday to return the unit. bob On Aug 21, 2008, at 9:51 AM, m. allan noah wrote: On Thu, Aug 21, 2008 at 10:41 AM, Bob Dronski dronski at gmail.com wrote: Jean-Nicolas, There seems to be a lot of confusion. Daniel seems to also have the same unit but must be having separate problems from me. He is NOT answering for me. Let me repeat my situation. I am running on Mac 10.5. I have used both Mattias Ellert's pre- built binaries for mac, as well as building the sane package myself. This is from sane-find-scanner. found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x26a3 [MF4100]) at libusb:003:004-04a9-26a3-00-00 And scanimage -L reports device `pixma:04A926A3_SDF7Z0155773B' is a CANON Canon imageCLASS MF4150 multi-function peripheral When I attempt to execute scanimage -T, it tries to read the first scanline and freezes. Now udev is definitely NOT running on my machine. the GREP output is misleading, because it shows my GREP process looking for the term udev. If I export the output of ps -A to a file, udev does not exist. But as I said, there IS a /usr/local/etc/udev/rules.d/libsane.rules that exists and it has the proper listing for the 4150. I had to manually move the .rules file as it was created in my build but didn't transfer to /usr/local/etc/udev/rules.d/ that did already exist. So my question is, When/how does udev get created? Should it be created by the build? Might I have used the wrong parameters in the configure command? I used ./configure --prefix=/usr/local --sysconfdir=/usr/local/etc udev is a linux-only device manager thing. it is only used by sane to set permissions on devices so that non-root users can scan. therefore, all users that have difficulty scanning should try as root user first. if root cannot scan, permissions (and hence, udev) are likely NOT the problem. i see no evidence that this backend supports this scanner, other than similarity of name to other, supported models. It might require only a minor tweak to a config file, or it might take a completely new backend, depending on how similar it is to existing models. allan -- The truth is an offense, but not a sin
[sane-devel] Neatreceipts Scanner
Hi All, I have FreeBSD 7.0 on a T42. I have installed : sane-backends-1.0.19_1 API for access to scanners, digitals camera, frame grabbers xsane-0.995_2 Gtk-based X11 frontend for SANE (Scanner Access Now Easy) I copied cism216 to /usr/local/share/sane/gt68xx/. I plugged in the scanner and still get the ugen0. I did a chmod 666 on /dev/ugen0 and it still can't recognize it as user. if I do xsane as su it will come up and recognize the device. Now when I try to scan the device it will come up as Failed to start scanner: Device busy. Here are the results of a SANE run: Gargoyle# sane-find-scanner -q found USB scanner (vendor=0x07b3, product=0x0412 [600dpi USB Scanner], chip=GT-6816) at libusb:/dev/usb1:/dev/ugen0 Gargoyle# scanimage -L device `gt68xx:libusb:/dev/usb1:/dev/ugen0' is a Plustek OpticSlim M12 flatbed scanner Sincerely, Brendhan
[sane-devel] Neatreceipts Scanner
On Thu, 2008-08-21 at 16:06 -0400, Understudy wrote: Hi All, I have FreeBSD 7.0 on a T42. I have installed : sane-backends-1.0.19_1 API for access to scanners, digitals camera, frame grabbers xsane-0.995_2 Gtk-based X11 frontend for SANE (Scanner Access Now Easy) I copied cism216 to /usr/local/share/sane/gt68xx/. I plugged in the scanner and still get the ugen0. I did a chmod 666 on /dev/ugen0 and it still can't recognize it as user. if I do xsane as su it will come up and recognize the device. Now when I try to scan the device it will come up as Failed to start scanner: Device busy. Here are the results of a SANE run: Gargoyle# sane-find-scanner -q found USB scanner (vendor=0x07b3, product=0x0412 [600dpi USB Scanner], chip=GT-6816) at libusb:/dev/usb1:/dev/ugen0 Gargoyle# scanimage -L device `gt68xx:libusb:/dev/usb1:/dev/ugen0' is a Plustek OpticSlim M12 flatbed scanner Sincerely, Brendhan Did you read the Readme file for BSD?, something IIRC with permissions also for group scanner? -- m.vr.gr. Gerard Klaver
[sane-devel] Canon MF4140
Hi Bob, I sent you a private email regarding this but apparently you didn't get it. I wrote the Imageclass section and Allan is correct. Your all-in-one shares the same Windows front-end stuff from Canon as mine. But beyond that, I have no idea whether the base USB communications protocol is the same or not. What's really needed are USB snoop logs, preferably from a Windows scan. Can you run Parallels or Bootcamp into Win2k or higher? -Dennis
[sane-devel] niash : HP 3300C flatbed not detecting physical scan area height
Hi all: I am using FreeBSD 6.3-RC2, with a custom kernel without uscanner support (otherwise niash won't work, as it needs libusb). I am using the following, built from ports: libusb-0.1.12_2 sane-backends-1.0.19_1 The scanner is perfectly detected and scanimage -L and scanimage -T work just fine. I tried a preview with xsane and scans too. However, when selecting an area for scanning it started making loud noises ?clack-clack?. Needless to say, I turned it off inmediatly, and apparently the scanner is not damaged. However this is very bad news for what used to be a fully supported device. This scanner worked perfectly in GNU/Linux, using: libusb-0.1.12 sane-backends-1.0.18 I'd say that it got broken from 1.0.18 to 1.0.19, but I'm not sure abut risking the scanner using the previous version in FreeBSD until it is clear why it is behaving this way. Greetings from Europe.
