[sane-devel] "perfection" 2480

2006-04-07 Thread fredthetree
[daniel@daniel ~]$ uname -a
FreeBSD daniel.higham.ca 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Thu Feb
9 08:42:05 AST 2006 r...@daniel.higham.ca:/usr/obj/usr/src/sys/MACHINE
i386

[daniel@daniel ~]$ scanimage --version
scanimage (sane-backends) 1.0.17; backend version 1.0.17

[daniel@daniel ~]$ export SANE_DEBUG_SNAPSCAN=255
[daniel@daniel ~]$ sudo scanimage -T
[snapscan] snapscani_usb_open(libusb:/dev/usb0:/dev/ugen0)
[snapscan] add_usb_device: Checking if 0x04b8 is a supported USB vendor ID
[snapscan] snapscani_check_device()
[snapscan] mini_inquiry
[snapscan] snapscan_cmd
[snapscan] snapscani_usb_cmd(0,0xbfbfe0a0,6,0xbfbfe070,0xbfbfe06c (36))
[snapscan] atomic_usb_cmd(0,0xbfbfe0a0,6,0xbfbfe070,0xbfbfe06c (36))
[snapscan] usb_cmd(0,0xbfbfe0a0,6,0xbfbfe070,0xbfbfe06c (36))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing:  0x12 0x00 0x00 0x00 0x24 0x00
[snapscan] Written 6 bytes
[snapscan] usb_read: reading:  0xf9 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] Read 8 bytes
[snapscan] usb_read: reading:  0x06 0x00 0x02 0x02 0x49 0x00 0x00 0x00 0x45
0x50 ...
[snapscan] Read 36 bytes
[snapscan] usb_read: reading:  0xfb 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] Read 8 bytes
[snapscan] snapscani_check_device: Is vendor "EPSON" model "EPSON Scanner" a
supported scanner?
[snapscan] snapscani_get_model_id(EPSON Scanner, 0, 2)
[snapscan] snapscani_get_model_id: looking up scanner for ID 0x04b8,0x0121.
[snapscan] snapscani_get_model_id: scanner identified
[snapscan] snapscani_check_device: Autodetected driver: Perfection 2480
[snapscan] snapscani_usb_close(0)
[snapscan] 1st read 3 write 1
[snapscan] snapscani_usb_cmd(0,0xbfbfe0e0,6,0x0,0x0 (0))
[snapscan] atomic_usb_cmd(0,0xbfbfe0e0,6,0x0,0x0 (0))
[snapscan] usb_cmd(0,0xbfbfe0e0,6,0x0,0x0 (0))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing:  0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] Written 6 bytes
[snapscan] usb_read: reading:  0xfb 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] Read 8 bytes
[snapscan] 2nd read 4 write 2
[snapscan] snapscani_init_device_structure()
[snapscan] sane_snapscan_get_devices (0xbfbfe6b8, 0)
[snapscan] sane_snapscan_open (libusb:/dev/usb0:/dev/ugen0, 0xbfbfe6b4)
[snapscan] find_device
[snapscan] sane_snapscan_open: Allocating 129024 bytes as scanner buffer.
[snapscan] sane_snapscan_open: allocated scanner structure at 0x8064000
[snapscan] open_scanner
[snapscan] snapscani_usb_open(libusb:/dev/usb0:/dev/ugen0)
[snapscan] sane_snapscan_open: waiting for scanner to warm up.
[snapscan] wait_scanner_ready
[snapscan] test_unit_ready
[snapscan] snapscan_cmd
[snapscan] snapscani_usb_cmd(0,0xbfbfe490,6,0x0,0x0 (0))
[snapscan] atomic_usb_cmd(0,0xbfbfe490,6,0x0,0x0 (0))
[snapscan] usb_cmd(0,0xbfbfe490,6,0x0,0x0 (0))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing:  0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] Written 6 bytes
[snapscan] usb_read: reading:  0xfb 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] Read 8 bytes
[snapscan] sane_snapscan_open: performing scanner self test.
[snapscan] send_diagnostic
[snapscan] snapscan_cmd
[snapscan] snapscani_usb_cmd(0,0xbfbfe650,6,0x0,0x0 (0))
[snapscan] atomic_usb_cmd(0,0xbfbfe650,6,0x0,0x0 (0))
[snapscan] usb_cmd(0,0xbfbfe650,6,0x0,0x0 (0))
[snapscan] sane_snapscan_open: self test passed.
[snapscan] inquiry
[snapscan] snapscan_cmd
[snapscan] snapscani_usb_cmd(0,0x8064030,6,0x808c000,0x8064140 (139))
[snapscan] atomic_usb_cmd(0,0x8064030,6,0x808c000,0x8064140 (139))
[snapscan] usb_cmd(0,0x8064030,6,0x808c000,0x8064140 (139))
[snapscan] usb_cmd: cmdlen=6, datalen=0
[snapscan] usb_write: writing:  0x12 0x00 0x00 0x00 0x8b 0x00
[snapscan] Written 6 bytes
[snapscan] usb_read: reading:  0xf9 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[snapscan] Read 8 bytes
[snapscan] usb_read Only 0 bytes read
[snapscan] usb_read: reading:  0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x00 ...
[snapscan] Read 0 bytes
[snapscan] inquiry: snapscan_cmd command failed: Error during device I/O
[snapscan] sane_snapscan_open: error in inquiry command: Error during device
I/O
scanimage: open of device snapscan:libusb:/dev/usb0:/dev/ugen0 failed: Error
during device I/O
[snapscan] sane_snapscan_exit


any ideas?
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060407/52ec9e88/attachment.html
From fredthet...@gmail.com  Sat Apr  8 03:36:47 2006
From: fredthet...@gmail.com (fredthetree)
Date: Sat Apr  8 03:37:05 2006
Subject: [sane-devel] Re: "perfection" 2480
In-Reply-To: 
References: 
Message-ID: 

in the past, the scanning head would do a little movement when the system is
booted, but... now the light on the front turns white and nothing happens =/

On 4/7/06, fredthetree  wrote:
>
> [daniel@daniel ~]$ uname -a
> FreeBSD daniel.higham.ca 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Thu
> Feb  9 08:42:05 AST 2006 
> r...@daniel.

[sane-devel] Re: fujitsu fi-4120c2 problems

2006-04-07 Thread m. allan noah
On Fri, 7 Apr 2006, Charles Duffy wrote:

> You might consider trying the latest drivers by m. allen noah. See 
> http://www2.pfeiffer.edu/~anoah/fujitsu/
>

i had hoped to have another release of that code last weekend, but a dead 
motherboard got in the way. perhaps next week.

colors may be reversed, and many features are disabled, but the up3 
version should at least let you make some scans until then.

allan

-- 
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera


[sane-devel] Hardware producers

2006-04-07 Thread Steve Nordquist
>> After looking at many of the producer's websites
>> and digging for answers, there seems to be a lack of
>> knowledge or interest in doing so. Maybe commercial
>> reasons are the base for that, I don't know. My
>> question is: is there a forum or a group of people
>> that tries to motivate these producers for including
>> all things needed to run the equipment?

Yeah, the IPC, engineering (ACM, IEEE, often enough the APS) and design (ID?) 
community.
The people boxing things and packing them into container ships FOB Finland are 
usually acting as Q/C conscious droids from a spec list negotiated a couple of 
times, 7 months out; they need somehow to get the signal propogated from the 
engineers through 8 months of live marketing-person hype.  That's a bit long 
for a consistent and constant message; but who's going to punch up the 
Workmanship (while keeping it fungible) in month 5 and 7?  Better make it 
easier for the various executives to do that.

Argh.  A rift in The Channel.  The Grand Line must be near, maties.

Secondly, I guess the business school and administrative (e.g. sysadmin, BOFH, 
Board) people who need to know that the neat tech docs aren't going to cause 
brand dilution or cooption because of excess internal strategic info inside; 
that is, once your product is snap-together (apart) except for 2 screws, which 
happens when the first unit made that way sells through, you need to write off 
secrecy and special regard (e.g. liability discussion) about the types, 
positions and designers of the connectors, and yet not include the address of 
some plastic case designer who doesn't want visits about the actual Channel 
Brand or its products.  So oddly enough we have a need to create a toy, 
skeleton specs model at the time of delivery (or dock inspection)



[sane-devel] OpticPro ST24 at cvs-04-01-2001

2006-04-07 Thread tymoteusz drozd
Hi all 
i have done small test of ganesys backend (cvs-01042006) with Plustek OpticPro 
St24.I whose very happy when my scanner start scaning (after uncommenting 
proper line in genesys.conf).but afther while i discovered that some things 
are not right.
in 150dpi mode (grayscale) everything is perfect :). after change to 
color
i recive bad synchronization between red green and blue. also i'v seen 
black ?!? im not sure is this right. i know about rgb colors but i dont know 
about rgb & black .reasumming - color palette is wrong(im almost sure that is 
becuse black apears as another base kolor).
in 300dpi mode i have nottice problem with scanning speed which is two 
times 
to fast
 and thats result in leaving physical area of scan(possible damange  of 
scanner).(fix is possible by correct scanning speed. for example normal speed 
is in 150dpi right now.halfspeed should be in 300dpi.in 600 dpi speed should 
be 4 times smaller then in 150dpi. and 1200dpi gets 8 times smaller speed).i 
also think that synchronization  of  colors is bad by wrong speed of 
scanning.
Scanning in higher resolution is not possible due to leaving of 
physical 
scanning area.
I hope that those information can be useful.
if somebody has more succes with this scanner pleas let me know.

ps.sorry for errors in text.english isnt my strong side :)

regards


BliZZi


[sane-devel] Re: fujitsu fi-4120c2 problems

2006-04-07 Thread Charles Duffy
You might consider trying the latest drivers by m. allen noah. See 
http://www2.pfeiffer.edu/~anoah/fujitsu/



[sane-devel] Canoscan Lide 60 with Ubuntu Dapper

2006-04-07 Thread Bertock
Hi everybody!
I'm an Ubuntu user and I have installed Dapper Drake that includes also 
the last back-ends SANE (1.0.17) that are necessary to use my scanner (a 
Canoscan Lide 60).
I have only a little problem: I can only use it as root!

Here I post the configuration files that I think are useful ( = my 
user name):

*/etc/sane.d/genesys.conf*:
# genesys.conf: Configuration file for Genesys Logic GL646 and GL841 
based scanners

#
# scanners that are not yet supported
# uncomment them only for developpment purpose
#

# UMAX Astra 4500 and Avision iVina 1600
#usb 0x0638 0x0a10

# Hewlett Packard ScanJet 2400c
#usb 0x03f0 0x0a01

# Hewlett Packard ScanJet 3670c
#usb 0x03f0 0x1405

# Plustek OpticPro ST24
#usb 0x07b3 0x0601


#
# supported scanners
#

# Medion MD5345/MD6228/MD6471
usb 0x0461 0x0377

# Hewlett Packard ScanJet 2300c
usb 0x03f0 0x0901

# Canon LiDE 35/40/50
usb 0x04a9 0x2213

# Canon LiDE 60
usb 0x04a9 0x221c


*/etc/udev/rules.d/45-libsane.rules*:
# This file is part of the SANE distribution
#
# udev rules file for supported scanners
#
#
# For now, only USB scanners are listed/supported by this set of rules;
# feel free to add support for other busses.
#
# To add an USB scanner, add a rule to the list below between the 
SUBSYSTEM...
# and LABEL... lines.
#
# To run a script when your scanner is plugged in, add RUN="/path/to/script"
# to the appropriate rule.
#

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

# Hewlett-Packard|ScanJet 4100C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0101", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|PhotoSmart S20
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0102", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 4200C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0105", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 6200C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0201", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 3300C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0205", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 4300C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0305", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 5200C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0401", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 3400C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0405", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 2100C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0505", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 6300C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0601", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 2200C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0605", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 5300C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0701", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 4400C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0705", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 7400C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0801", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 4470c
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0805", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 2300C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0901", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 2400c
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="0a01", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 5400C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="1005", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 5470C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="1105", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 5550C
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="1205", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|Scanjet 4570c
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="1305", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|PSC 750
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="1411", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 3570c
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="2005", MODE="664", 
GROUP="scanner"
# Hewlett-Packard|ScanJet 3500c
SYSFS{idVendor}=="03f0", SYSFS{idProduct}=="2205", MODE="664", 
GROUP="scanner"
# Mustek Systems Inc.|BearPaw 1200
SYSFS{idVendor}=="0400", SYSFS{idProduct}=="1000", MODE="664", 
GROUP="scanner"
# Mustek Systems Inc.|BearPaw 2400
SYSFS{idVendor}=="0400", SYSFS{idProduct}=="1001", MODE="664", 
GROUP="scanner"
# Lexmark|X70/X73
SYSFS{idVendor}=="043d", SYSFS{idProduct}=="002d", MODE="664", 
GROUP="scanner"
# Lexmark|X83
SYSFS{idVendor}=="043d", SYSFS{idProduct}=="003d", MODE="664", 
GROUP="scanner"
# Lexmark|X1185
SYSFS{idVendor}=="043d", SYSFS{idProduct}=="007c", MODE="664", 
GROUP="scanner"
# Genius|ColorPage-Vivid Pro Scanner
SYSFS{idVendor}=="0458", SYSFS{idProduct}=="2001", MODE="664", 
GROUP="scanner"
# Genius|ColorPage HR6 V2
SYSFS{idVendor}=="0458", SYSFS{idProduct}=="2007", MODE="664", 
GROUP="scanner"
# Genius|ColorPage HR6 V2
SYSFS{idVendor}=="0458", SYSFS{idProduct}=="2008", MODE="664", 
GROUP="scanner"
# G