USB Sandisk SDDR-31 problems in 2.4.9 - 2.4.17

USB Sandisk SDDR-31 problems in 2.4.9 - 2.4.17

[Nelson Mok]

My system is currently an AMD Athlon with kernel 2.4.17, Adaptec 2940 PCI
SCSI card, Plextor 40X SCSI CD-ROM, Plextor 8x CD-R and the USB Sandisk
SDDR-31 compact flash reader.  With the 2.4.x series of the kernel, in
particular with RedHat's 2.4.9 kernel, 2.4.15, 2.4.16, and 2.4.17 I have
been experiencing the same two problems.

1. the SCSI CD-ROM on my system works fine, that is until I mount the USB
cf reader.  After doing so, any attempts to mount a CD in the CD-ROM gives
me the message "mount: wrong fs type, bad option, bad superblock on
/dev/cdrom, or too many mounted file systems".  If the CD-ROM is already
mounted and I then mount the USB cf reader, the CD-ROM will no longer
respond...  unmounting and mounting the CD-ROM at this point seems to work
but any attempt to access the information is futile.  The physical eject
on the CD-ROM also ceases to function after this.  Tried removing all the
USB modules followed by the SCSI modules and then modprobe them all again
but doing that does not affect anything.  Only way to access my CD-ROM
again is a reboot of the machine.  The wierd thing to this is, it does not
affect my CD-R drive as it continues to work fine.  This happens again if
I were to repeat the above mentioned steps.

2. after mounting the USB cf reader, the shutting down of the system
stalls for quite a bit at the point where it tries to unmount all the file
systems.  This occurs regardless of whether I unmounted the drive or not.


Lastly, I know both the CD-ROM and USB cf reader are fine as they have
worked fine under the later 2.2.x kernels, as well as in Windows.

Re: USB Sandisk SDDR-31 problems in 2.4.9 - 2.4.17

[Matthew Dharm]

[-- Attachment #1: Type: text/plain, Size: 2541 bytes --]

The "stall at shutdown" is a known problem.  I'm testing a patch now... as
soon as I see my last patchset incorporated into the kernels, I'll send it
out for inclusion.

As for the USB device "hiding" your SCSI device... how odd.   I've never
heard of that before.

Matt

On Thu, Jan 10, 2002 at 04:30:53AM -0500, Nelson Mok wrote:
> My system is currently an AMD Athlon with kernel 2.4.17, Adaptec 2940 PCI
> SCSI card, Plextor 40X SCSI CD-ROM, Plextor 8x CD-R and the USB Sandisk
> SDDR-31 compact flash reader.  With the 2.4.x series of the kernel, in
> particular with RedHat's 2.4.9 kernel, 2.4.15, 2.4.16, and 2.4.17 I have
> been experiencing the same two problems.
> 
> 1. the SCSI CD-ROM on my system works fine, that is until I mount the USB
> cf reader.  After doing so, any attempts to mount a CD in the CD-ROM gives
> me the message "mount: wrong fs type, bad option, bad superblock on
> /dev/cdrom, or too many mounted file systems".  If the CD-ROM is already
> mounted and I then mount the USB cf reader, the CD-ROM will no longer
> respond...  unmounting and mounting the CD-ROM at this point seems to work
> but any attempt to access the information is futile.  The physical eject
> on the CD-ROM also ceases to function after this.  Tried removing all the
> USB modules followed by the SCSI modules and then modprobe them all again
> but doing that does not affect anything.  Only way to access my CD-ROM
> again is a reboot of the machine.  The wierd thing to this is, it does not
> affect my CD-R drive as it continues to work fine.  This happens again if
> I were to repeat the above mentioned steps.
> 
> 2. after mounting the USB cf reader, the shutting down of the system
> stalls for quite a bit at the point where it tries to unmount all the file
> systems.  This occurs regardless of whether I unmounted the drive or not.
> 
> 
> Lastly, I know both the CD-ROM and USB cf reader are fine as they have
> worked fine under the later 2.2.x kernels, as well as in Windows.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
Maintainer, Linux USB Mass Storage Driver

What, are you one of those Microsoft-bashing Linux freaks?
					-- Customer to Greg
User Friendly, 2/10/1999

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

SCSI ID wars [was: USB Sandisk SDDR-31 problems in 2.4.9 - 2.4.17]

[Timothy Covell]

On Thursday 10 January 2002 15:35, Matthew Dharm wrote:
> The "stall at shutdown" is a known problem.  I'm testing a patch now... as
> soon as I see my last patchset incorporated into the kernels, I'll send it
> out for inclusion.
>
> As for the USB device "hiding" your SCSI device... how odd.   I've never
> heard of that before.
>
> Matt

Does it hide your SCSI device or just shift the SCSI IDs such that
/dev/scd0 becomes /dev/scd1?   


And that brings up a question concerning whether there is a defined
way of assigning SCSI IDs.    I'm assume that it's "every driver for
itself".


---
timothy.covell@ashavan.org.

Re: SCSI ID wars [was: USB Sandisk SDDR-31 problems in 2.4.9 - 2.4.17]

[Matthew Dharm]

[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]

Actually, device IDs are handed out by the SCSI mid-layer.  The low-level
drivers don't even have an easy way to figure it out.

Matt

On Thu, Jan 10, 2002 at 04:33:22PM -0600, Timothy Covell wrote:
> On Thursday 10 January 2002 15:35, Matthew Dharm wrote:
> > The "stall at shutdown" is a known problem.  I'm testing a patch now... as
> > soon as I see my last patchset incorporated into the kernels, I'll send it
> > out for inclusion.
> >
> > As for the USB device "hiding" your SCSI device... how odd.   I've never
> > heard of that before.
> >
> > Matt
> 
> Does it hide your SCSI device or just shift the SCSI IDs such that
> /dev/scd0 becomes /dev/scd1?   
> 
> 
> And that brings up a question concerning whether there is a defined
> way of assigning SCSI IDs.    I'm assume that it's "every driver for
> itself".
> 
> 
> ---
> timothy.covell@ashavan.org.

-- 
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
Maintainer, Linux USB Mass Storage Driver

G:  Money isn't everything, A.J.
AJ: Who convinced you of that?
G:  The Chief, at my last salary review.
					-- Mike and Greg
User Friendly, 11/3/1998

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: SCSI ID wars [was: USB Sandisk SDDR-31 problems in 2.4.9 - 2.4.17]

[Nelson Mok]

On Thu, 10 Jan 2002, Timothy Covell wrote:

> On Thursday 10 January 2002 15:35, Matthew Dharm wrote:
> > The "stall at shutdown" is a known problem.  I'm testing a patch now... as
> > soon as I see my last patchset incorporated into the kernels, I'll send it
> > out for inclusion.
> >
> > As for the USB device "hiding" your SCSI device... how odd.   I've never
> > heard of that before.
> >
> > Matt
>
> Does it hide your SCSI device or just shift the SCSI IDs such that
> /dev/scd0 becomes /dev/scd1?
>
>
> And that brings up a question concerning whether there is a defined
> way of assigning SCSI IDs.    I'm assume that it's "every driver for
> itself".
>
>
> ---
> timothy.covell@ashavan.org.

Well after having this happen to me again, I checked to see whether the
SCSI IDs were shifted or not...  from what I gather, they haven't because
the CD-ROM is assigned ID 3 and the CD-R is assigned ID 4 and I am still
able to mount a CD as /dev/scd1 if the disc was placed in the CD-R drive.

Re: USB Sandisk SDDR-31 problems in 2.4.9 - 2.4.17

[Nelson Mok]

On Thu, 10 Jan 2002, Nelson Mok wrote:

> My system is currently an AMD Athlon with kernel 2.4.17, Adaptec 2940 PCI
> SCSI card, Plextor 40X SCSI CD-ROM, Plextor 8x CD-R and the USB Sandisk
> SDDR-31 compact flash reader.  With the 2.4.x series of the kernel, in
> particular with RedHat's 2.4.9 kernel, 2.4.15, 2.4.16, and 2.4.17 I have
> been experiencing the same two problems.
>
> 1. the SCSI CD-ROM on my system works fine, that is until I mount the USB
> cf reader.  After doing so, any attempts to mount a CD in the CD-ROM gives
> me the message "mount: wrong fs type, bad option, bad superblock on
> /dev/cdrom, or too many mounted file systems".  If the CD-ROM is already
> mounted and I then mount the USB cf reader, the CD-ROM will no longer
> respond...  unmounting and mounting the CD-ROM at this point seems to work
> but any attempt to access the information is futile.  The physical eject
> on the CD-ROM also ceases to function after this.  Tried removing all the
> USB modules followed by the SCSI modules and then modprobe them all again
> but doing that does not affect anything.  Only way to access my CD-ROM
> again is a reboot of the machine.  The wierd thing to this is, it does not
> affect my CD-R drive as it continues to work fine.  This happens again if
> I were to repeat the above mentioned steps.
>
> 2. after mounting the USB cf reader, the shutting down of the system
> stalls for quite a bit at the point where it tries to unmount all the file
> systems.  This occurs regardless of whether I unmounted the drive or not.
>
>
> Lastly, I know both the CD-ROM and USB cf reader are fine as they have
> worked fine under the later 2.2.x kernels, as well as in Windows.

To add to this, even after the system refuses to mount the CD-ROM, I can
still control a musical CD through xmms...  skip tracks, play, stop, and
pause the musical CD.