On Tue, 2005-08-02 at 05:23 -0700, Craig White wrote:
> On Tue, 2005-08-02 at 19:40 +0900, Dave Gutteridge wrote:
> > >Well, could try building the latest FC3 or FC4 kernel under CentOS.
> > >
> > Hmm... I'm wary of that since there were so many other issues with
> > Fedora that I encountered which motivated me to come to CentOS in the
> > first place.
Yes - understood.
> > >Can also try (as root):
> > ># tail -f /var/log/messages
> > >then insert card. (Ctrl-C to exit - otherwise runs "forever".)
> > >
> > >
> > Nothing happens if I run the command and then insert a card.
> > However, if I remove the card reader from the USB Port and put it back
> > in, I get this:
> >
> > Aug 2 19:34:51 localhost kernel: usb 1-1.1: new full speed USB device
> > using address 9
> > Aug 2 19:34:51 localhost kernel: scsi2 : SCSI emulation for USB Mass
> > Storage devices
> > Aug 2 19:35:03 localhost kernel: Vendor: BUFFALO Model: CF CARD
> > Reader Rev: 3.06
> > Aug 2 19:35:03 localhost kernel: Type:
> > Direct-Access ANSI SCSI revision: 02
> > Aug 2 19:35:03 localhost kernel: Attached scsi removable disk sdb at
> > scsi2, channel 0, id 0, lun 0
> > Aug 2 19:35:04 localhost scsi.agent[4367]: disk at
> > /devices/pci0000:00/0000:00:1f.2/usb1/1-1/1-1.1/1-1.1:1.0/host2/target2:0:0/2:0:0:0
> > Aug 2 19:35:06 localhost kernel: Device not ready. Make sure there is
> > a disc in the drive.
Looks familiar - so, presuming you are running the centosplus
unsupported kernel, it is no help.
> >
> > Judging by that last line, it might seem as though something is wrong
> > with the card. So I tested other cards, and also verified that the cards
> > could be read by both Windows and my Palm Pilot. The cards definitely
> > have data on them. It's CentOS that can not read them.
Yes - still looks like a kernel-driver problem.
> >
> > >If something shows up in the output, try
> > >
> > ># fdisk -l
> > >
> > >
> > Here is the output from that:
> >
> > [root@localhost dave]# fdisk -l
> > Disk /dev/hda: 30.0 GB, 30020272128 bytes
> > 255 heads, 63 sectors/track, 3649 cylinders
> > Units = cylinders of 16065 * 512 = 8225280 bytes
> > Device Boot Start End Blocks Id System
> > /dev/hda1 * 1 3649 29310561 7 HPFS/NTFS
> > Disk /dev/hdb: 30.7 GB, 30738677760 bytes
> > 255 heads, 63 sectors/track, 3737 cylinders
> > Units = cylinders of 16065 * 512 = 8225280 bytes
> > Device Boot Start End Blocks Id System
> > /dev/hdb1 * 1 3644 29270398+ 83 Linux
> > /dev/hdb2 3645 3737 747022+ f W95 Ext'd (LBA)
> > Disk /dev/sda: 40.0 GB, 40007761920 bytes
> > 255 heads, 63 sectors/track, 4864 cylinders
> > Units = cylinders of 16065 * 512 = 8225280 bytes
> > Device Boot Start End Blocks Id System
> > /dev/sda1 1 4864 39070048+ c W95 FAT32 (LBA)
> ----
> unless /dev/sda1 was something else, it appears that this was your card
> and thus when you pushed it in, then pulled it out - it then saw
> that /dev/sda was already in use so the second time, it tried to assign
> it /dev/sdb where it failed.
I thought that could be it until noticing the 40.0 GB capacity.
> You might simply want to reboot...
>
> mkdir /home/sdcard
> # insert the card/card reader
> mount /dev/sda1 /home/sdcard
> ls -l /home/sdcard
>
> and I would guess that you would see something there.
>
> of course this is as root and if you got that far, you could then create
> the entry to /etc/fstab to allow mounting (or automount) as a user.
Don't think so - the device is not showing up, so it can't be mounted.
Should have asked before: What does "lsusb" show? Might find something
by googling the USB device information.
Phil
