IEEE 1394 for Linux / Bugs / #21 nikon coolscan 4000ED does not work

#21 nikon coolscan 4000ED does not work

Status: open-duplicate

Owner: James Goodwin

Labels: sbp2 (22)

Priority: 5

Updated: 2002-03-21

Created: 2001-12-26

Creator: gernot judtmann

Private: No

Hi, I made already several attempts with various
versions of kernel, IEEE1394 subsystem to get the
Nikon Coolscan 4000 ED working under Linux, without
success. this is my current setup:
suse 7.2 with several updates
kernel 2.4.16 (same effect with various previous
versions)
libraw 0.9.0-1

loading the modules seems to work, the device is
recognised (see below),
however, the application vuescan(www.hamrick.com)
does not work with the scanner,
vuescan also exists in a windows version that works
perfectly,
enclosed are the logfiles for both windows and linux,
the first colums is a time stamp in seconds, the
second indicated a time delay

thanks in advance for your support
(this scanner is the only reason I have windows
installed)
gernot judtmann

appenix:

console output when loading modules and rescanning
scsi bus:

bash-2.05# insmod ieee1394
Using
/lib/modules/2.4.16/kernel/drivers/ieee1394/ieee1394.o
bash-2.05# insmod ohci1394
Using
/lib/modules/2.4.16/kernel/drivers/ieee1394/ohci1394.o
bash-2.05# insmod sbp2
Using
/lib/modules/2.4.16/kernel/drivers/ieee1394/sbp2.o
bash-2.05# rescan-scsi-bus.sh
Host adapter 0 (INIA100) found.
Host adapter 1 (sbp2) found.
0 new device(s) found.
0 device(s) removed.
bash-2.05# rescan-scsi-bus.sh
Host adapter 0 (INIA100) found.
Host adapter 1 (sbp2) found.
Scanning for device 1 0 0 0 ...
NEW: Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Nikon Model: LS-4000 ED Rev:
1.04
Type: Scanner ANSI
SCSI revision: 02
1 new device(s) found.
0 device(s) removed.

entries in /var/log/messages:

Dec 26 10:48:44 gernot1 kernel: ohci1394: $Revision:
1.80 $ Ben Collins <bcollins@debian.org>
Dec 26 10:48:44 gernot1 kernel: PCI: Found IRQ 11 for
device 00:0c.0
Dec 26 10:48:44 gernot1 kernel: ohci1394_0: OHCI-1394
1.0 (PCI): IRQ=[11] MMIO=[dc000000-dc001000] Max
Packet=[1024]
Dec 26 10:48:52 gernot1 kernel: ieee1394: sbp2:
Driver forced to serialize I/O (serialize_io = 1)
Dec 26 10:48:52 gernot1 kernel: scsi1 : IEEE-1394
SBP-2 protocol driver
Dec 26 10:48:57 gernot1 kernel: scsi singledevice 0 0
0 0
Dec 26 10:48:57 gernot1 kernel: scsi singledevice 0 0
1 0
Dec 26 10:48:58 gernot1 kernel: scsi singledevice 0 0
2 0
Dec 26 10:48:58 gernot1 kernel: scsi singledevice 0 0
3 0
Dec 26 10:48:59 gernot1 kernel: scsi singledevice 0 0
4 0
Dec 26 10:48:59 gernot1 kernel: scsi singledevice 0 0
5 0
Dec 26 10:49:00 gernot1 kernel: scsi singledevice 0 0
6 0
Dec 26 10:49:00 gernot1 kernel: scsi singledevice 0 0
7 0
Dec 26 10:49:01 gernot1 kernel: scsi singledevice 1 0
0 0
Dec 26 10:49:01 gernot1 kernel: scsi singledevice 1 0
1 0
Dec 26 10:49:01 gernot1 kernel: scsi singledevice 1 0
2 0
Dec 26 10:49:01 gernot1 kernel: scsi singledevice 1 0
3 0
Dec 26 10:49:01 gernot1 kernel: scsi singledevice 1 0
4 0
Dec 26 10:49:01 gernot1 kernel: scsi singledevice 1 0
5 0
Dec 26 10:49:01 gernot1 kernel: scsi singledevice 1 0
6 0
Dec 26 10:49:01 gernot1 kernel: scsi singledevice 1 0
7 0
Dec 26 10:49:07 gernot1 kernel: ieee1394: ConfigROM
quadlet transaction error for node 0:1023
Dec 26 10:49:07 gernot1 last message repeated 2 times
Dec 26 10:49:07 gernot1 kernel: ieee1394: Giving up
on node 0:1023 for ConfigROM probe, too many errors
Dec 26 10:49:10 gernot1 kernel: ieee1394: ConfigROM
quadlet transaction error for node 0:1023
Dec 26 10:49:10 gernot1 kernel: ieee1394: sbp2: Node
0:1023: Max speed [S400] - Max payload [1024]
Dec 26 10:49:10 gernot1 kernel: ieee1394: NodeMgr:
hotplug policy returned -2
Dec 26 10:49:10 gernot1 kernel: ieee1394: Device
added: node 0:1023, GUID 0090b54001ffffff
Dec 26 10:49:35 gernot1 kernel: scsi singledevice 0 0
0 0
Dec 26 10:49:36 gernot1 kernel: scsi singledevice 0 0
1 0
Dec 26 10:49:36 gernot1 kernel: scsi singledevice 0 0
2 0
Dec 26 10:49:37 gernot1 kernel: scsi singledevice 0 0
3 0
Dec 26 10:49:37 gernot1 kernel: scsi singledevice 0 0
4 0
Dec 26 10:49:38 gernot1 kernel: scsi singledevice 0 0
5 0
Dec 26 10:49:38 gernot1 kernel: scsi singledevice 0 0
6 0
Dec 26 10:49:39 gernot1 kernel: scsi singledevice 0 0
7 0
Dec 26 10:49:39 gernot1 kernel: scsi singledevice 1 0
0 0
Dec 26 10:49:39 gernot1 kernel: Vendor: Nikon
Model: LS-4000 ED Rev: 1.04
Dec 26 10:49:39 gernot1 kernel: Type: Scanner
ANSI SCSI revision: 02
Dec 26 10:49:39 gernot1 kernel: scsi singledevice 1 0
1 0
Dec 26 10:49:39 gernot1 kernel: scsi singledevice 1 0
2 0
Dec 26 10:49:40 gernot1 kernel: scsi singledevice 1 0
3 0
Dec 26 10:49:40 gernot1 kernel: scsi singledevice 1 0
4 0
Dec 26 10:49:40 gernot1 kernel: scsi singledevice 1 0
5 0
Dec 26 10:49:40 gernot1 kernel: scsi singledevice 1 0
6 0
Dec 26 10:49:40 gernot1 kernel: scsi singledevice 1 0
7 0

Dec 26 11:15:40 gernot1 kernel: scsi : aborting
command due to timeout : pid 97, scsi1, channel 0, id
0, lun 0 Read Capacity 01 00 00 00 03 00 00 3a 80
Dec 26 11:15:40 gernot1 kernel: ieee1394: sbp2:
aborting sbp2 command

Discussion

gernot judtmann - 2001-12-26

vuescan logfiles (linux and windows)

vuescanlogs.tar.gz

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ben Collins - 2002-03-21

labels: --> sbp2

assigned_to: nobody --> jamesg

status: open --> open-duplicate
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ben Collins - 2002-03-21

Logged In: YES
user_id=196071

I've not used any scanners with sbp2. James will have to
comment on this one.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

James Goodwin - 2002-04-22

Logged In: YES
user_id=55674

Sorry, just catching up on support... =(

I've worked with others to get Epson scanners working with
the sbp2 driver, so I suspect we can get this one going.
Any new status on this? I can see from the trace that the
scsi inquiry command was ok, but that a read capacity
failed on the device.

A couple things
- Please update to the latest ieee1394 source here, and
see if the behavior is the same.
- Uncomment the "#define CONFIG_IEEE1394_SBP2_DEBUG 2"
near the top of sbp2.c, and send a debug trace.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nobody/Anonymous - 2002-04-22

Logged In: NO

hi,
I will not have time to make the proposed checks before the
coming weekend
gernot

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

gernot judtmann - 2002-05-09

log

sbp2log.txt.gz

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

gernot judtmann - 2002-05-09

Logged In: YES
user_id=270580

Hi, I finally manged to made the proposed tests (sorry
for the delay):
I loaded the newest version, enabled the logging,
compiled, installed and loaded the modules.
The version behaves better, the scanner is detected by
vuescan, but I cannot scan, when I activate a preview or a
scan nothing happens, also no error message appears. I
enclose the logfile. Please let me know, if I can make
additional checks.
best regards and thank you for the support
gernot

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

nikon coolscan 4000ED does not work

Group

Searches

Help

#21 nikon coolscan 4000ED does not work

Discussion