Unable to mount sitecom cn300 multi memory card reader.

From: Sander Scheepens (s.scheepens_at_planet.nl)
Date: 09/14/03 

Date: Sun, 14 Sep 2003 20:59:03 +0200

Hello,

The installation of the sitecom cn300 multimemory cardreader. is giving
me some trouble.
I used the Sitecom FAQ . I have the option "Probe all LUNs on each SCSI
device" already sellected.
But in dmesg I can't find this line "scsi0 : SCSI emulation for USB Mass
Storage devices" I also can't find the sd_mod.o module.
The distribution I use is SuSE 8.2 (kernel 2.4.20-4GB). I have a SCSI
CDwriter, wich uses "/dev/sr0".
I have included dmesg, lsusb and cat /proc/bus/usb/devices output.

*_sitecom FAQ:

_* 1. Introduction

This document will cover the installation of the CN-300 Multi Memory
Reader/Writer under Linux. This installation will only work with the
CN-300 revision 3 or 4! To find out which revision you have please check
out the FAQ for the CN-300. Furthermore your system will have to meet
the following demands:

- One free USB port
- Linux kernel 2.4.x or higher
- Linux source must be installed

2. Installation

2.1 Linux kernel configuration

The CN-300 is basically already supported under Linux. The only problem
is that when Linux boots it will see only 1 SCSI disk, while in fact the
CN-300 has 4. To solve this problem we need to configure the Linux
kernel to determine how many drives (Logical Units) each SCSI device has.

Start a console session and type the following (where kernel-version is
found by typing uname ?r).

[linuxprompt]# cd /usr/src/linux-kernel-versie/
[linuxprompt]# make menuconfig

You will now see a menu. This is the Linux kernel configuration menu. In
this menu you will see an item called SCSI support. Upon opening this
item you will see a list in which one thing interests us, namely Probe
all LUNs on each SCSI device. Turn this option on (we advise to not
touch any of the other settings, this can make Linux unstable or not
work at all).
After turning this option on press Esc(ape) twice. You will be asked if
you want to svae the new configuration. Select Yes.

Once back in the console type the following:

[linuxprompt]# make dep modules modules_install bzImage
[linuxprompt]# cp arch/i386/boot/bzImage /boot/kernel.exp

Please note the make command can take a LONG time, depending on the
speed of your computer.

To make Linux start up with the newly compiled kernel we need to edit
the bootloader configuration file. Two popular bootloaders are GRUB and
LILO. Before we move on make sure you know which bootloader you have.

2.2 Configuration GRUB

GRUB uses the file /boot/grub/grub.conf for it?s configuration. Copy the
the lines starting from title and ending with kernel. And then paste
this at the end of the file.
We will then need to edit these pasted lines as follows. Bold print are
the changes.

/boot/grub/grub.conf

title Red Hat Linux (2.4.7-10)
root (hd0,0)
kernel /boot/vmlinuz-2.4.18-3 ro root=/dev/hda3

title LinuxNew
root (hd0,0)
kernel /boot/kernel.exp ro root=/dev/hda3

Now when the computer restart there will be a new item in the bootmenu
named LinuxNew. If this kernel boots up correctly you can select the new
kernel as your default.

2.3 Configuration LILO

LILO uses the /etc/lilo.conf file. It?s basically the same as GRUB, see
the following bold print for the changes.

image=/boot/vmlinuz-2.4.18-3
label=Linux
read-only
root=/dev/hda3

image=/boot/kernel.exp
label=LinuxNew
read-only
root=/dev/hda3

2.4 Making the CN-300 accessible

When Linux has booted up and everything is ok we can check to see if the
CN-300 was detected succesfully. In the systemmessages, using the dmesg
command, we should see something like this:

scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: DMI Model: MultiFlash Rev: 3.00
Type: Direct-Access ANSI SCSI revision: 02
Vendor: DMI Model: MultiFlash Rev: 3.00
Type: Direct-Access ANSI SCSI revision: 02
Vendor: DMI Model: MultiFlash Rev: 3.00
Type: Direct-Access ANSI SCSI revision: 02
Vendor: DMI Model: MultiFlash Rev: 3.00
Type: Direct-Access ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.

Next we need to assign the 4 slots to mountable devices, we do this as
follows:

[linuxprompt]# modprobe sd_mod

Typing dmesg will now show this:

Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi removable disk sdb at scsi0, channel 0, id 0, lun 1
Attached scsi removable disk sdc at scsi0, channel 0, id 0, lun 2
Attached scsi removable disk sdd at scsi0, channel 0, id 0, lun 3
sda : READ CAPACITY failed.
sda : status = 1, message = 00, host
*_
dmesg:_*
095Mb (mask 0xffffffff)
reiserfs: found format "3.6" with standard journal
reiserfs: enabling write barrier flush mode
reiserfs: using ordered data mode
reiserfs: checking transaction log (ide0(3,75)) for (ide0(3,75))
Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Trying to move old root to /initrd ... failed
Unmounting old root
Trying to free ramdisk memory ... okay
Freeing unused kernel memory: 160k freed
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
LVM version 1.0.5+(mp-v6a)(22/07/2002) module loaded
Adding Swap: 136512k swap-space (priority 42)
MSDOS FS: IO charset iso8859-1
MSDOS FS: IO charset iso8859-1
NTFS driver 2.1.1a [Flags: R/O MODULE].
NTFS volume version 3.0.
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (3072 buckets, 24576 max) - 296 bytes per conntrack
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
CSLIP: code copyright 1989 Regents of the University of California
ISDN subsystem Rev: 1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1 loaded
HiSax: Linux Driver for passive ISDN cards
HiSax: Version 3.5 (module)
HiSax: Layer1 Revision 1.1.4.1
HiSax: Layer2 Revision 1.1.4.1
HiSax: TeiMgr Revision 1.1.4.1
HiSax: Layer3 Revision 1.1.4.1
HiSax: LinkLayer Revision 1.1.4.1
HiSax: Approval certification failed because of
HiSax: unauthorized source code changes
HiSax: Total 1 card defined
HiSax: Card 1 Protocol EDSS1 Id=contr0 (0)
HiSax: W6692 driver Rev. 1.1.4.1
PCI: Found IRQ 10 for device 00:10.0
PCI: Sharing IRQ 10 with 00:02.2
Found: Winbond W6692, I/O base: 0xe000, irq: 10
HiSax: W6692 config irq:10 I/O:e000
W6692: Winbond W6692 version (0): W6692 V00
W6692 ISTA=0x0
W6692 IMASK=0xFF
W6692 D_EXIR=0x0
W6692 D_EXIM=0xFF
W6692 D_RSTA=0xA0
Winbond 6692: IRQ 10 count 0
Winbond 6692: IRQ 10 count 4
HiSax: DSS1 Rev. 1.1.4.1
HiSax: 2 channels added
HiSax: MAX_WAITING_CALLS added
HiSax: debugging flags card 1 set to 4
ne2k-pci.c:v1.02 10/19/2000 D. Becker/P. Gortmaker
  http://www.scyld.com/network/ne2k-pci.html
PCI: Found IRQ 11 for device 00:0d.0
eth0: RealTek RTL-8029 found at 0xd400, IRQ 11, 00:40:05:E2:5D:A2.
ippp, open, slot: 0, minor: 0, state: 0000
ippp_ccp: allocated reset data structure c2daa000
raw1394: /dev/raw1394 device initialized
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 19:02:24 Aug 6 2003
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 10 for device 00:02.2
PCI: Sharing IRQ 10 with 00:10.0
usb-uhci.c: USB UHCI at I/O 0xd000, IRQ 10
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
uhci.c: USB Universal Host Controller Interface driver v1.1
hub.c: new USB device 00:02.2-2, assigned address 2
hub.c: USB hub found
hub.c: 4 ports detected
mice: PS/2 mouse device common for all mice
hub.c: new USB device 00:02.2-2.1, assigned address 3
usb.c: USB device 3 (vend/prod 0xc0b/0xa109) is not claimed by any
active driver.
hub.c: new USB device 00:02.2-2.2, assigned address 4
usb.c: USB device 4 (vend/prod 0xc0b/0xa10c) is not claimed by any
active driver.
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
sr0: scsi3-mmc drive: 16x/16x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
Device not ready. Make sure there is a disc in the drive.
Device not ready. Make sure there is a disc in the drive.
Device not ready. Make sure there is a disc in the drive.
PCI: Found IRQ 9 for device 00:0f.0
Device not ready. Make sure there is a disc in the drive.
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
Device not ready. Make sure there is a disc in the drive.
Device not ready. Make sure there is a disc in the drive.
mtrr: 0xd6000000,0x2000000 overlaps existing 0xd6000000,0x800000
Linux video capture interface: v1.00
eth0: no IPv6 routers present
isdn_net: call from 492322181 -> 0 413331915 ignored
isdn_tty: call from 492322181 -> 413331915 ignored
isdn_net: call from 492322181 -> 0 413331915 ignored
isdn_tty: call from 492322181 -> 413331915 ignored
isdn_net: Incoming call without OAD, assuming '0'
isdn_net: call from 0 -> 0 413331915 ignored
isdn_tty: Incoming call without OAD, assuming '0'
isdn_tty: call from 0 -> 413331915 ignored

_*lsusb:*_
Bus 001 Device 003: ID 0c0b:a109 Dura Micro, Inc. (Acomdata) CF/SM
Reader and Writer
Bus 001 Device 004: ID 0c0b:a10c Dura Micro, Inc. (Acomdata) SD/MS
Reader and Writer
_*
cat /proc/bus/usb/devices:*_
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 11/900 us ( 1%), #Int= 1, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 4
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0451 ProdID=2046 Rev= 1.25
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0c0b ProdID=a109 Rev=17.08
S: Manufacturer=ACOMdATA
S: Product=USB CF+SM
S: SerialNumber=340ED8DF0E
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
T: Bus=01 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0c0b ProdID=a10c Rev= 2.00
S: Manufacturer=ACOMdATA
S: Product=USB SD+MS
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms

Relevant Pages

  • Re: linux USB question
    ... The only rules that really matter are these: What a man CAN do, and what a man CAN'T do! ... I know it>>>>> picks up USB and mem sticks. ... >>>>> has been resolved with the new kernel. ... I spent hours of reading trying to get my flash drive working>>>> and then out of frustration I formatted it vfat in linux and it's ...
    (alt.linux)
  • Re: installing embedded os
    ... He is building a custom Linux kernel task scheduler. ... re-inventing the Uheel (USB Wheel). ... Once your are in 32 bit, you can't call 16 bit BIOS functions. ...
    (comp.arch.embedded)
  • Re: cheap printer for linux/lprng
    ... > iii) compatible with linux and easy install ... printer can be refilled through refill kits or the like, ... Not unless you're running a very old kernel. ... Modern kernels include USB ...
    (comp.os.linux.hardware)
  • Re: Wireless mouse - pointer erratic
    ... Check to see which kernel driver is trying to operate your mouse. ... had a different mouse plugged in and it wasn't a USB mouse, ... > installed - it's detected by linux as an HID device. ... > the writing pad it moves - albeit eratticaly, ...
    (comp.os.linux)
  • Re: Minolta dimage a2 on linux
    ... > Has anyone tried to make a usb connection to a dimage a2 on a linux ... Dimage A2 works with his dcraw program (for downloading RAW files ... Kernel versions have 3 numbers. ... It may be that the device's USB IDs aren't in the database of supported ...
    (comp.os.linux.hardware)