Samsung Unified Linux driver + CLX-3185 + TC CUPS-strategy

[Juanito]

Anyway, SANE/CUPS extension maintainer should notice these numerous side effects when changing installation point and at least set those file-location vars correctly.

Are some of the cups vars set incorrectly?

Of course, if EVERYONE other distros are using "/usr" installation point, coders may hardcode some of those library directories. That's ALSA problem.

PPI or not, I think there's a certain logic to the base being in /usr and all extensions being in /usr/local

Even if /usr is hardcoded in some cases, it's usually not a big deal to symlink to /usr/local. I saw this once with a lexmark driver for cups - which was only available in a deb - and the error messages made it reasonably easy to make a symlink fix.

[Yleisajattelija]

I'm not sure for CUPS, at least UnifiedLinuxDriver installer uses wrong directory. When correcting those (cp files to correct dir + force static by filetools.lst) CUPS works OK.

My SANE won't work at all at this moment, but I'm not sure, if it is this /usr/local -lib problem or udev.rules related issue. There is another SANE discussion thread (should found by searching with "sane"), where SANE works by dir correction procedure.

[Juanito]

If you got things to work with cups after the UnifiedLinuxDriver installed to /usr by copying files to /usr/local, then you should be able make an extension and be good to go without resorting to filetool.lst and backup/restore.

I'd also guess that your sane woes are more likely due to /usr vs /usr/local than udev...

[Yleisajattelija]

If you got things to work with cups after the UnifiedLinuxDriver installed to /usr by copying files to /usr/local, then you should be able make an extension and be good to go without resorting to filetool.lst and backup/restore.

Yes, that's the goal.

I agree with TC frugal installation PPI-method, no doubt of that.

Gobolinux approach may be theoretically better, but it is impossible recode all unix code written from golden -70:ies. Gobolinux alias/link -system is horrible mess, ever worse than scattered "traditional" linux

It is solid idea to limit "basic TC pack" to minimum and isolate code as much as possible to extensions. Also it looks good trade-off to put border between "/usr" and  "usr/local" directories, that gives maximum compatibility with "industry standard unix" and still makes isolation effective.

[Yleisajattelija]

tc@box:~$ 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 Electronics Co., Ltd.], product=0x343d [CLX-3180 Series]) at libusb:002: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.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

  # You may want to run this program as root to find all devices. Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.

tc@box:~$ 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).
tc@box:~$

[Yleisajattelija]

Contents of file "/usr/local/etc/sane.d/dll.conf" (trying to use that xerox_mfp driver)


# enable the next line if you want to allow access through the network:
net
abaton
agfafocus
apple
avision
artec
artec_eplus48u
as6e
bh
canon
canon630u
canon_dr
#canon_pp
cardscan
coolscan
#coolscan2
coolscan3
#dc25
#dc210
#dc240
dell1600n_net
dmc
epjitsu
#epson
epson2
fujitsu
#gphoto2
genesys
gt68xx
hp
hp3900
hpsj5s
hp3500
hp4200
hp5400
hp5590
hpljm1005
hs2p
ibm
kodak
kvs1025
kvs20xx
leo
lexmark
ma1509
magicolor
matsushita
microtek
microtek2
mustek
#mustek_pp
mustek_usb
mustek_usb2
nec
niash
#p5
pie
pint
pixma
plustek
#plustek_pp
#pnm
qcam
ricoh
rts8891
s9036
sceptre
sharp
sm3600
sm3840
snapscan
sp15c
#st400
#stv680
tamarack
teco1
teco2
teco3
#test
u12
umax
#umax_pp
umax1220u
v4l
xerox_mfp

[Yleisajattelija]

# Edit: this part is added to original xerox_mfp.conf file, CLX-3175 driver should be same than CLX-3185
#Samsung CLX-3185
#usb 0x04e8 0x343d
#end of edit


#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

#Samsung SCX4725-FN
usb 0x04e8 0x341f

#Samsung SCX-4500
usb 0x04e8 0x3426

# Samsung SCX-4500W
usb 0x04e8 0x342b

# Samsung SCX-4824
usb 0x04e8 0x342c

# Samsung SCX-4300
usb 0x04e8 0x342e

# Samsung SCX-4600
usb 0x04e8 0x3433

#Samsung CLX-3185
usb 0x04e8 0x343d

#Xerox WorkCentre 3119 Series
usb 0x0924 0x4265

#Samsung SCX-4623
usb 0x04e8 0x3434

# Samsung SCX-4825FN
usb 0x04e8 0x343c

#Xerox WorkCentre 4118 Series
usb 0x0924 0x420c

#Xerox WorkCentre 3210
usb 0x0924 0x4293

#Xerox WorkCentre 3220
usb 0x0924 0x4294

# Samsung SCX-4500W, network mode
# tcp HOST_ADDR PORT
#     Uncomment and configure:
#tcp scx4500 9400

[Yleisajattelija]

Installed sane packages:

xsane.tcz
sane-backends.tcz
sane-backends-dev.tcz
Edit: libusb.tcz

Missing something?

[Juanito]

$ sane-find-scanner
found USB scanner (vendor=0x04e8 [Samsung Electronics Co., Ltd.], product=0x343d [CLX-3180 Series]) at libusb:002:004

This might be helpful: http://ubuntuforums.org/showthread.php?t=341621&page=83

$ scanimage -L

No scanners were identified.

Hmm - I get:

Code: [Select]

$ scanimage -L
device `hpaio:/usb/OfficeJet_G85?serial=SGG13E0C49VL' is a Hewlett-Packard OfficeJet_G85 all-in-one

Contents of file "/usr/local/etc/sane.d/dll.conf" (trying to use that xerox_mfp driver)

# enable the next line if you want to allow access through the network:
net
abaton
agfafocus
...
xerox_mfp

It might be better to comment out or delete everything except "xerox_mfp", all I have is:

Code: [Select]

$ cat /usr/local/etc/sane.d/dll.conf
hpaio
net


# Edit: this part is added to original xerox_mfp.conf file, CLX-3175 driver should be same than CLX-3185
#Samsung CLX-3185
#usb 0x04e8 0x343d
#end of edit

Shouldn't it look like this (i.e. delete the "#" before "usb")

Code: [Select]

# Edit: this part is added to original xerox_mfp.conf file, CLX-3175 driver should be same than CLX-3185
#Samsung CLX-3185
usb 0x04e8 0x343d
#end of edit

[Yleisajattelija]

I added first that added text on "xerox_mfp.conf file for comment, active text without "#" is later on file.

I have read those SamsungUnifiedLinux ubuntu discussion threads, but remember, debian use "/usr" installation point.

xerox_mfp is part of standard sane package, should work "out of the box".

I don't know, how to find out if sane-backend finds and reads that xerox_mfp.conf file at all. That would be logical consequence for "/usr/local" installation point.

[Yleisajattelija]

SamsungUnifiedLinuxDriver installer adds twos files at "etc/udev/rules.d/" directory

a) 98_smfpautoconf_samsung.rules

# This file is a part of Unified Linux Driver
# Rules to allow low level USB device access for smfpautoconf

SUBSYSTEM!="usb_device", GOTO="label_end"
ACTION!="add", GOTO="label_end"

ATTRS{idVendor}=="0419", MODE="0666"
ATTRS{idVendor}=="04e8", MODE="0666"
ATTRS{idVendor}=="0924", MODE="0666"
ATTRS{idVendor}=="413c", MODE="0666"

LABEL="label_end"

b)  99_smfpautoconf_samsung.rules

# This file is a part of Unified Linux Driver
# Rules to allow low level USB device access for smfpautoconf

SUBSYSTEM!="usb", GOTO="label_end"
ACTION!="add", GOTO="label_end"

ATTRS{idVendor}=="0419", MODE="0666"
ATTRS{idVendor}=="04e8", MODE="0666"
ATTRS{idVendor}=="0924", MODE="0666"
ATTRS{idVendor}=="413c", MODE="0666"

LABEL="label_end"


I don't know if these are needed without network scanner SANE-server "saned".

Thas miserable SANE-documentation says, that SANE-default directories may be changed by settin variables, but these variables should export at compile time.

[Juanito]

I have read those SamsungUnifiedLinux ubuntu discussion threads, but remember, debian use "/usr" installation point.

OK, but on my machine sane is reading files from /usr/local/etc/sane.d - note also, by default, tinycore will load libs from both /usr/lib and /usr/local/lib

I don't know, how to find out if sane-backend finds and reads that xerox_mfp.conf file at all. That would be logical consequence for "/usr/local" installation point.

To double-check you can make a symlink from /etc/sane.d -> /usr/local/etc/sane.d, but I don't think that is the issue..

Edit: you could also double-check:

Code: [Select]

$ ldd /usr/local/lib/sane/libsane-xerox_mfp.so.. to be sure you're not missing anything

[Juanito]

SamsungUnifiedLinuxDriver installer adds twos files at "etc/udev/rules.d/" directory

If these two files are in place you can do the following:

Code: [Select]

$ sudo udevadm trigger
$ sudo udevadm monitor..and then plug your scanner in to see what you get

[Yleisajattelija]

I think easiest way is to recompile SANE source.

To do that, I need to know "tc specalities", this /usr/local installation point and others.

There is some discussion for udev.rules (defaults should be OK), anything else need to be known?

[Juanito]

See http://distro.ibiblio.org/tinycorelinux/3.x/tcz/src/sane-backends/sane-backends.tcbuild

You can also get the standard tc cflags/cxxflags from the extension making section of the wiki