On Thursday 15 January 2004 02:58am, Richard Charlewood wrote:
> Hi Bill,
>
> Thanks again for the reply and all this help you are giving me! I really
> do appreciate it!

No problem. I'm happy to help if I can. But I hope others are reading this 
thread too, because I'm not intimately familiar with the SCSI subsystem, 
which seems to be generating the errors you're seeing. (Wise of you to put 
this thread back on-list.)

> About the memory stick - I also wondered about the formatting so I took
> the stick into a local computer shop where they put it in a card reader
> and copied all the contents onto a CD for me.  I then formatted it
> using the camera and tried again. It didn't work without pictures and it
> didn't work with a few test photos either. :(  So I'm left thinking its a
> Linux issue.

OK, I agree. Sorry about the "false start", but I think it was worthwhile to 
rule out that issue (formatting) right from the start.

> Scratching around on Google I cam across mention of multi-card readers (6
> in 1 things) where the person had to recompile the kernel with
> CONFIG_SCSI_MULTI_LUN=y - do you know if you had that set in your kernel?

No, I do not (and never have on that machine). Currently, per '/usr/src/
linux/.config':

   # CONFIG_SCSI_MULTI_LUN is not set

In fact, I knew without even checking because I did a test a couple weeks ago 
with my own 2-slot (Compact Flash and SD card) USB card reader after hearing 
about the CONFIG_SCSI_MULTI_LUN issue on one of these USB lists. My main 
machine (Slackware 9.1, no MULTI_LUN) failed to simultaneously detect a CF 
and SD card in the reader, but when I moved over to a machine with SuSE 8.2, 
I could mount/read CF and SD cards simultaneously. Of course, after checking, 
the MULTI_LUN flag _was_ set on that SuSE machine, which makes sense.

So, no, I would say that MULTI_LUN is clearly _not_ required to read the 
memory stick on the Sony DCR-TRV38, certainly not with Slackware 9.1.

> And do you know if there is a way of passing a parameter like that to an
> rpm kernel install? (I'm not really up to compiling my own kernel)

There's no way that I know of to do this, but I haven't tried RedHat in years. 
AFAIK, you must compile support into the kernel the old-fashioned way.

In lieu of rebuilding your kernel, is there any chance you could try a newer 
distribution than "RedHat 7.0 + various 7.3 patches"?

Do you have (or could you borrow) any other USB devices (like a flash RAM 
drive or a CF/SD/whatever card reader) that would mount as '/dev/sda1'?

By the way, you never answered this question from my first reply:

   Notice that the filesystem on the memory stick as originally 
   delivered is 'FAT12'. Are you getting something similar from 
   an 'fdisk -l /dev/sda' command?

> Also from scratching scsi0 is the first scsi controller.

Yes, that's normal.  I have 'scsi0' through 'scsi3' ('cat /proc/scsi/scsi').

--------------------

I've gone back and re-examined your output files and I cannot see anything 
really wrong or different from my successful attempt except for the final 
'SCSI disk error' messages that are showing up in the '/var/log/messages' 
file.

Are these errors showing up when you try to mount the device or only when your 
try to actually read from it? It looks like they're showing up on a mount, 
but since you were using the wrong device at one point (i.e. '/dev/sda' 
instead of '/dev/sda1'), I'm worried that we're confusing ourselves here.

Oh, a couple of follow-ups from my first reply, for completeness:

(1) I tried '-t vfat' on the 'mount' command for the memory stick and it 
worked fine, so no problems using that.

(2) I tried to (intentionally) erroneously mount the _drive_ (e.g. '/dev/sda') 
instead of the proper _partition_ ('/dev/sda1') and (as expected) got the 
same error you were getting:

   mount: wrong fs type, bad option, bad superblock on /dev/sdb, 
         or too many mounted file systems

So make sure to keep using '/dev/sda1'. I know you already knew that, but I 
wanted to be absolutely sure to clarify.

--------------------

I'm still optimistic that this can be solved. I assume that the errors you're 
seeing haven't changed since your first post the list, yes? If things have 
changed at all, it might be time to post some fresh logs of various things.

Maybe someone more familiar with the internals of the SCSI subsytem will jump 
in here with some advice/ideas....

Bill Marr



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to