Tiny Core Linux
Off-Topic => Archive / Obsolete => SCM EXtensions => Topic started by: uggla on June 09, 2012, 11:01:25 AM
-
xsane.scm has no wbar icon while xsane.tcz has.
-
There must be typo in the .desktop file or similar, I will look at it tonight.
-
I'm testing the extension and I find two problems:
1- There is an apps/xsane/pkgbase/local/lib/modules/3.0.3-tinycore and not /modules/3.0.21-tinycore
2- I have a multifuncion Samsung scx-4200 with dmesg:
usb 1-1: new high speed USB device number 5 using ehci_hcd
usblp0: USB Bidirectional printer dev 5 if 1 alt 0 proto 2 vid 0x04E8 pid 0x341B
but xsane says "no devices aviable" after scanning for devices.
I know it uses the xerox_mfp driver
there is an /apps/xsane/pkgbase/local/etc/sane.d/xerox_mfp.conf with:
#xerox_mfp.conf
#Xerox Phaser 3200MFP
usb 0x0924 0x3da4
#Dell MFP Laser Printer 1815dn
usb 0x413c 0x5124
#Xerox Phaser 6110MFP
usb 0x0924 0x3d5d
#Samsung CLX-3170fn & CLX-3175FW
usb 0x04e8 0x342a
#Samsung SCX-4200
usb 0x04e8 0x341b
and a /apps/xsane/pkgbase/local/lib/sane/libsane-xerox_mfp.so (so.1 and so.1.0.22)
where is the problem?
Is something that I can do to be the multifuncion be detected as a scanner?
edit:
the result of:
tc@box:/apps/xsane/pkgbase$ sane-find-scanner
# 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.
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
found USB scanner (vendor=0x04e8 [Samsung], product=0x341b [SCX-4200 Series]) at libusb:001:004
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
...
and
tc@box:/apps/xsane/pkgbase$ 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).
edit 2:
perhaps is because I don't have the scanner module in lsmod. How to get it?
-
As of present there is no support for kernel modules in scms, so I will remove the superfluous directory.
I will fix the desktop icon issue also.
As I only have one scanner to test with, and it works, I am not sure what is going on with yours. But I will poke around and see what issues there may be preventing the scanner from being found.
-
I see at least one issue I overlooked, I will aim to fix it today.
-
My report of success was premature, it seems that /usr/local/etc/sane.d files are hardcoded into the binaries. And that those files were mistakenly present in /usr/local when I tested the extension.
No real loss, but I will have to pull it.
-
My report of success was premature, it seems that /usr/local/etc/sane.d files are hardcoded into the binaries. And that those files were mistakenly present in /usr/local when I tested the extension.
I got same conclusion, only way to fix it is clean xsane backend source code. That is unfortunately BAD code, very bad.
Volunteers?
-
Reason for that hardcoding seems to be binary-only drivers. Some manufacturer provides only binary drivers and it IS possible, that driver itself refers bare "/usr" directory -> porting problems for TC cannot be solved.
I try to find out is this the situation, or is there some work-around to solve this problem.
-
You can always create symlinks for such hardcoded binaries.
-
I think a fresh build of sane-backends and xsane would fix the issue and assign the right paths to the sane.d files. I may tackle that when I have some free time.