I have Slack 10.2 install on a new PC.
All work OK except I can't seem to mount a Compact Flash memory card.
I can mount my mp3 player on /dev/sdb1 OK, but I don't get any reports in
dmesg.
I was able to mount the memory card under /dev/sda1 in 10.1, but after a
complete install of 10.2 I can't find anything.
In Info center it is seen as
Attached devices
Host: scsi2 Channel: 00 Id: 00 Lun:00
Vendor: IC Model: USB Storage-CFC Rev: 30Ib
Type: Direct-Access ANSI SCSI revision: 02

Sorry if this is a bit vague as I don't know where to start.

Thanks

Lezo

Lezo wrote:
> I have Slack 10.2 install on a new PC.
> All work OK except I can't seem to mount a Compact Flash memory card.
> I can mount my mp3 player on /dev/sdb1 OK, but I don't get any reports in
> dmesg.
> I was able to mount the memory card under /dev/sda1 in 10.1, but after a
> complete install of 10.2 I can't find anything.
> In Info center it is seen as
> Attached devices
> Host: scsi2 Channel: 00 Id: 00 Lun:00
> Vendor: IC Model: USB Storage-CFC Rev: 30Ib
> Type: Direct-Access ANSI SCSI revision: 02
>
> Sorry if this is a bit vague as I don't know where to start.
>
> Thanks
>
> Lezo
You may have to check if usb-storage is loaded ... if not, try 'modprobe
usb-storage'

-pbh-

Lezo <not@all.com> wrote:
> I have Slack 10.2 install on a new PC.
> All work OK except I can't seem to mount a Compact Flash memory card.

2.4 or 2.6 kernel?
And what does 'cat /proc/scsi/scsi' report (after you plugged in the
memory card, of course).

> I can mount my mp3 player on /dev/sdb1 OK, but I don't get any reports in
> dmesg.

I'm more used to the 2.6 kernel, but in 2.4 it was:
device, once given, STAY with the same device, so when "something" is sda,
and your memory stick is sdb, the memory CARD may have been given sdc(1).

> I was able to mount the memory card under /dev/sda1 in 10.1, but after a
> complete install of 10.2 I can't find anything.
> In Info center it is seen as
> Attached devices
> Host: scsi2 Channel: 00 Id: 00 Lun:00
> Vendor: IC Model: USB Storage-CFC Rev: 30Ib
> Type: Direct-Access ANSI SCSI revision: 02

Without seeing the "other scsi" devices, you don't know the device
assignments, but it seems as two other scsi (emulated) devices were
there first (scsi0 and scsi1).

Example (note: this is 2.6, that "forgets about" unplugged devices):
Attached devices:
Host: scsi1 Channel: 00 Id: 04 Lun: 00
Vendor: HP Model: C5683A Rev: C005
Type: Sequential-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 06 Lun: 00
Vendor: IOMEGA Model: ZIP 100 Rev: D.09
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi24 Channel: 00 Id: 00 Lun: 00
Vendor: USB 2.0 Model: Flash Disk Rev: PROL
Type: Direct-Access ANSI SCSI revision: 02

In this "scsi1" is NOT a disk (type Sequential-Access), but a tape, so
has been given the name "st0", scsi2 is sda (and as ZIP disks have
partition 4: sda4) and the Flash Disk is sdb (this one does NOT have
partitions, superfloppy format).
When I plugin my USB disk (which DOES have partitions), it will become
sdc (the disk) and sdc1 (the 1st partition ON that disk), unless I
unplug the memory stick first, because then sdb is free again (but only
in a 2.6 kernel).

For the 2.4 kernel, normally count disks (type Direct-Access) from the
top, the first is (and WILL stay) sda, etc.
Only by unloaded USB support or rebooting the system will restart at sda.

PS: scsi0 in the above was a IOmega REV-drive, which is currently unplugged,
3 through 23 were "previous plugins" of memory sticks etc. (as I said,
the 2.6 kernel will remove those device names at unplugging).
2.4 will remove the "scsiXX" entry, but will NOT remove its corresponding
device name, so when the SAME device is plugged-in again, it will get
the SAME device name, but a different device will get a new one.
The device is recognized again on Vendor and Model (and will stay in
the kernel /proc/scsi/sci table).
--
************************************************** ******************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M.Hartman@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** ******************

Thanks for the reply

2.6 kernel

les@ez:~$ cat /proc/scsi/scsi
Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: IC Model: USB Storage-CFC Rev: 301b
Type: Direct-Access ANSI SCSI revision: 02

I have no other SCSI devices attached

Does any of this make sense.

Lezo

I had similar fun with several usb devices: you might want to plug the
offending card into the slot and then type dmesg in a terminal window.
That should tell you where the system is putting the device.

Hope this helps!

Fred

"CatGrampy" <Frederick.Armstrong@gmail.com> wrote:
>I had similar fun with several usb devices: you might want to plug the
>offending card into the slot and then type dmesg in a terminal window.
>That should tell you where the system is putting the device.
>
>Hope this helps!

That will do it, but

dmesg | tail

is better, or

tail /var/log/messages

will also do it.

Here are the results of looking at dmesg output, incrementally.
First a USB card reader is plugged in:

usb 2-3: new full speed USB device using ohci_hcd and address 13
usb 2-3: not running at top speed; connect to a high speed hub
scsi12 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 13
usb-storage: waiting for device to settle before scanning
Vendor: Generic Model: STORAGE DEVICE Rev: 9144
Type: Direct-Access ANSI SCSI revision: 00
Attached scsi removable disk sdc at scsi12, channel 0, id 0, lun 0
Attached scsi generic sg1 at scsi12, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete

Note that if you don't wait a few seconds, that output will
pause at the 5th line, and at least one more read is necessary.

When a CF card is plugged in no additional output will be
available. But when the CF card is mounted, this information is
then in the buffer,

SCSI device sdb: 501760 512-byte hdwr sectors (257 MB)
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
SCSI device sdb: 501760 512-byte hdwr sectors (257 MB)
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
sdb: sdb1

Note that if the CF card is inserted into the reader *before* it
is connected to the USB bus, the seven lines above will be be
inserted before the last three in the previous dump; and then
mounting the filesystem on the CF card will not produce any
additional information.

--
Floyd L. Davidson <http://www.apaflo.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) floyd@apaflo.com

Most excellent, Floyd--I had forgotten about tail and var/log/messages!
Sometimes I use a bludgeon when a scalpel will do--an unfortunate
character flaw.
Stay warm up there, brother.

Fred

CatGrampy wrote:

> I had similar fun with several usb devices: you might want to plug the
> offending card into the slot and then type dmesg in a terminal window.
> That should tell you where the system is putting the device.
>
> Hope this helps!
>
> Fred

Sorry dmesg does not show the card at all!

That is the problem.
I can see the card in Slack 10.1 using a 2.4 kernel, but not with 10.2 with
a 2.6!

Thanks Lezo

On Fri, 06 Jan 2006 10:01:09 +0000, Lezo <not@all.com> wrote:

>Sorry dmesg does not show the card at all!
>
Have you told SCSI to probe all LUNs?

Grant.

Grant wrote:

> Have you told SCSI to probe all LUNs

Sorry, but how do I do that.

Lezo