Re: [SLUG] Something broke

From: Paul M Foster (paulf@quillandmouse.com)
Date: Mon Jan 15 2007 - 15:22:31 EST


Chuck Hast wrote:

> On 1/15/07, Paul M Foster <paulf@quillandmouse.com> wrote:

<snip>

> It is a USB card reader.... Here is the messages tail from when the SD
> card is inserted
> in the card reader:
>
> Jan 15 13:50:42 RF-mobile kernel: SCSI device sdc: 2012160 512-byte
> hdwr sectors (1030 MB)
> Jan 15 13:50:42 RF-mobile kernel: sdc: Write Protect is off
> Jan 15 13:50:42 RF-mobile kernel: sdc: Mode Sense: 02 00 00 00
> Jan 15 13:50:42 RF-mobile kernel: sdc: assuming drive cache: write through
> Jan 15 13:50:42 RF-mobile kernel: SCSI device sdc: 2012160 512-byte
> hdwr sectors (1030 MB)
> Jan 15 13:50:42 RF-mobile kernel: sdc: Write Protect is off
> Jan 15 13:50:42 RF-mobile kernel: sdc: Mode Sense: 02 00 00 00
> Jan 15 13:50:42 RF-mobile kernel: sdc: assuming drive cache: write through
> Jan 15 13:50:42 RF-mobile kernel: sdc: sdc1
>
>
>> You say you can plug in the PCMCIA card and "the card" will be given a
>> device node assignment of hde? Which "card" are you talking about that
>> gets this assignment? Are you plugging in the PCMCIA card with the SD
>> card inserted and getting the assignment that way? Or are you saying
>> that the PCMCIA card gets this assignment by itself? Assuming the SD
>> card is getting this hde assignment, it doesn't make sense that you
>> can't mount it if you're trying to do so as root, and using the proper
>> options for the mount command. What error message do you get when you
>> try to mount the SD card while it's inserted into the PCMCIA card?
>> Anything in syslog or /var/log/messages?
>>
>
> I should have defined things more clearly. 'The Card" should be the SD card
> and the other is the pcmcia card which I should have just called the pc
> card...
>
> Here is the messages tail of the insertion of the SD card into the PC
> card...
>
>
> Jan 15 13:59:29 RF-mobile kernel: pccard: PCMCIA card inserted into slot 0
> Jan 15 13:59:29 RF-mobile kernel: pcmcia: registering new device pcmcia0.0
> Jan 15 13:59:31 RF-mobile kernel: Probing IDE interface ide2...
> Jan 15 13:59:31 RF-mobile kernel: hde: CF Card, CFA DISK drive
> Jan 15 13:59:31 RF-mobile kernel: hdf: probing with STATUS(0x00)
> instead of ALTSTATUS(0x0a)
> Jan 15 13:59:33 RF-mobile kernel: hdf: probing with STATUS(0x00)
> instead of ALTSTATUS(0x0a)
> Jan 15 13:59:34 RF-mobile kernel: ide2 at 0x4100-0x4107,0x410e on irq 3
> Jan 15 13:59:34 RF-mobile kernel: hde: max request size: 128KiB
> Jan 15 13:59:34 RF-mobile kernel: hde: 0 sectors (0 MB) w/1KiB Cache,
> CHS=0/0/0
> Jan 15 13:59:34 RF-mobile kernel: ide-cs: hde: Vcc = 3.3, Vpp = 0.0
>
>
>
>
> the card I was trying was a 128Mb card, this is a 1Gb card and I see some-
> thing that makes me suspect in the last line there where it indicated 0
> sectors.
> The other card also showed 0 (I went off and left it at home so I am
> using the
> one I have at hand), here is what I found from messages on it:
>
> Jan 14 22:01:00 RF-mobile kernel: hde: CF Card, CFA DISK drive
> Jan 14 22:01:00 RF-mobile kernel: hdf: probing with STATUS(0x00)
> instead of ALTSTATUS(0x0a)
> Jan 14 22:01:02 RF-mobile kernel: hdf: probing with STATUS(0x00)
> instead of ALTSTATUS(0x0a)
> Jan 14 22:01:04 RF-mobile kernel: ide2 at 0x4100-0x4107,0x410e on irq 3
> Jan 14 22:01:04 RF-mobile kernel: hde: max request size: 128KiB
> Jan 14 22:01:04 RF-mobile kernel: hde: 0 sectors (0 MB) w/1KiB Cache,
> CHS=0/0/0
> Jan 14 22:01:04 RF-mobile kernel: ide-cs: hde: Vcc = 3.3, Vpp = 0.0
>

<snip>

Only two things jump out at me. First, the USB card reader is trying to
mount things with the SCSI interface (sdc, sdc1). The PCMCIA card is
trying to mount things using the IDE interface (hde, hdf, ide2). Odd.
The other thing is that you're calling this an SD card, but the driver
is calling it a CF card. May be an artifact of the text the programmer
using in coding the driver. Dunno. My normal assumption would be that
running

mount -t vfat /dev/hd[e|f] /media/[existing_mount_point]

or

mount -t vfat /dev/sdc1 /media/[existing_mount_point]

would either succeed or fail, but produce some sort of reasonable clues.

Naturally, I'd also suggest trying more than one SD card in the same
circumstances to see if it's just the SD card itself for some bizarre
reason.

Paul

-- 
Paul M. Foster
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS).  Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:34:26 EDT