I recently posted my problem regarding getting my multi card reader running again after upgrading from FC4 to FC6. Rather than refer to the old post I have done a lot of research and experimentation and would like to restart discussion afresh.


PROBLEM:
--------
The multicard reader will not declare itself unless I remove the ehci-hcd module with "modprobe -r ehci-hcd" and then unplug the reader from the motherboard USB header socket and back in again.


RESEARCH:
---------
Some points to note:
* My other USB storage devices are working correctly and all connect as SCSI devices such as my Olympus camera and even my GP2X (which is a quirkly little device to connect).
* I have multi-luns enabled.
* I have tried kernels 2.6.19-1.2895.fc6 and 2.6.20 (the latter mentioned improvements in USB in the changelog so it was worth trying)
* It all worked fine in FC4 so the hardware does play nicely.
* As noted above, it works on removal of the echi module and then unplug and plug into the motherboard.

QUESTION:
---------
There is obviously a problem with the initalisation of the device at boot time. Is there something in the scsi command set, /proc or /sys value that will allow a complete "reboot" of the device or re-initialisation as if I had physically unplugged and plugged back in? That way I could at least make a script until the problem improves.

I am not at my desktop this weekend but to unload a device from the scsi chain use the echo command. Check out this link from a quick search on google.
http://tldp.org/HOWTO/archived/SCSI-...g-HOWTO-4.html

Brian

Hi Brian,

Thanks so much this is just the kind of info I am after. I unplugged the device and back in again to get it going and get the required device/interface numbers. I am unsure how to identify the correct parameters.

The document link you mention shows me the required line I need, ie:

echo "scsi add-single-device a b c d" > /proc/scsi/scsi

I tried to first check what the a b c d were by looking doing an: ls /sys/bus/scsi/devices
I get: 1:0:0:0 1:0:0:1 1:0:0:2 1:0:0:3

Then to recreate the problem I inserted the ehci-hcd module and then removed it again which kills the cardreader. Now I try a scsi insert with:

echo "scsi add-single-device 1 0 0 0" > /proc/scsi/scsi

But this gives the line: bash: echo: write error: No such device or address

Ok, so that indicates to me that 1:0:0:0 is not the required IDs for a b c d.

My lsusb -v section for the card reader shows the following:

I am having difficultly identifying from the above what is:

* hostadapter id
* SCSI channel on hostadapter
* ID
* LUN

You get better info issuing the command ' cat /proc/scsi/scsi '

Brian

Ah ok, I'll get the device working and check the contents there this evening.

Ok, excellent, I do have the numbers now...

# cat /proc/scsi/scsi
Attached devices:
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Generic Model: STORAGE DEVICE Rev: 9144
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 01
Vendor: Generic Model: STORAGE DEVICE Rev: 9144
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 02
Vendor: Generic Model: STORAGE DEVICE Rev: 9144
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 03
Vendor: Generic Model: STORAGE DEVICE Rev: 9144
Type: Direct-Access ANSI SCSI revision: 02


So my numbers should be:
1 0 0 0
1 0 0 1
1 0 0 2
1 0 0 3

Hmmm... they're the numbers I came up with before. Maybe I was on the money to start with.
So I enable and disable the ehci-hcd module to kill the cardreader with:

modprobe ehci-hcd
modprobe -r ehci-hcd

Now to try the scsi commands:
echo "scsi add-single-device 1 0 0 0" > /proc/scsi/scsi
echo "scsi add-single-device 1 0 0 1" > /proc/scsi/scsi
echo "scsi add-single-device 1 0 0 2" > /proc/scsi/scsi
echo "scsi add-single-device 1 0 0 3" > /proc/scsi/scsi

And all come back with:
-bash: echo: write error: No such device or address

So it looks like that is where I am stuck.

Check out this script. Run it after you do the disabling/enabling of ehci-hcd. Rescan-Scsi_Bus
http://www.garloff.de/kurt/linux/

Brian

Got the script and ran it. Message back was: No SCSI host adapters found in sysfs

So I'm beginning to think that this is a hardware initialisation thing, not a device wakeup. There is a green led on the reader. The led will only light and the reader come alive under the following two conditions:

1) the ehci-hcd is not present
2) the unit is plugged into the motherboard after linux loads

So I think it has to do with power. Perhaps I need a command that will wake up the actual motherboard usb port or the power supply to the device.

I know of nothing that can do that and it may be possible the motherboard could even do that. Other than that I have one more idea. Go into the bios and see if there is an option like Legacy USB. If so enable it or un enable it and see if that works.

Brian