Date: Thu, 7 Jul 2005 11:03:56 +1000 From: Robert Backhaus <robbak@gmail.com> To: KAYVEN RIESE <kayve@sfsu.edu> Cc: freeBSD bugs mailing list <freebsd-bugs@freebsd.org> Subject: Re: can't see SD card Message-ID: <d44995805070618032a1a7bea@mail.gmail.com> In-Reply-To: <Pine.GSO.4.44.0507061522350.11935-100000@libra.sfsu.edu> References: <Pine.GSO.4.44.0507061522350.11935-100000@libra.sfsu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the background.
On 7/7/05, KAYVEN RIESE <kayve@sfsu.edu> wrote:
> basically.. i can't see my SD card that came with the
> puter. my camera died but the two SD cards with my
> latest fotos on it should be able to be read by freeBSD,
> in that they fit nicely into my hardware.
>=20
>=20
> here is the result of the command "usbdevs"
>=20
> Path: /home/kayve <~~~~~~ .login i have uses a two line prompt.. this
> is line one
> (root@www) 103> usbdevs <~~~~~second line of prompt and the command
>=20
> addr 1: UHCI root hub, Intel <~~~~~~~~output starts here
> addr 1: UHCI root hub, Intel
> addr 2: Resolution 400/600/800 Changeable Combo Mouse, ACROX
> addr 1: UHCI root hub, Intel
> addr 1: EHCI root hub, Intel
>=20
> <---end of output----->
OK, big hint: I see not card reader device.
>=20
>=20
> next i was told to do the command "pciconf -l -v"
> and i did, and selected out "class =3D mass storage"
>=20
> i did thatmanually, here is the result
>=20
>=20
> atapci0@pci0:31:1: class=3D0x01018a card=3D0x18691043 chip=3D0x24ca8=
086
> rev=3D0x03
> hdr=3D0x00
> vendor =3D 'Intel Corporation'
> device =3D '82801DBM (ICH4-M) UltraATA/100 EIDE Controller'
> class =3D mass storage
> subclass =3D ATA
> none0@pci0:31:5: class=3D0x040100 card=3D0x17131043 chip=3D0x24c58=
086
> rev=3D0x03
> hdr=3D0x00
Again: no card reader
>=20
> i was told i am hosed.
>=20
>=20
> Path: /home/kayve
> (kayve@kayvetop) 101> su
> Password: <~~~~ becoming superuser
>=20
> kayvetop# sysctl kern.disks kern.rootdev <~~~ prompt =3D "kayvetop#"
> kern.disks: ad0
> kern.rootdev: ad0s2a
> kayvetop#
>=20
>=20
> kayvetop# grep "o d" /var/run/dmesg.boot
> pci1: <display, VGA> at device 0.0 (no driver attached)
> pci2: <network> at device 2.0 (no driver attached)
> pci0: <multimedia, audio> at device 31.5 (no driver attached)
> pci0: <simple comms, generic modem> at device 31.6 (no driver attached)
> pci1: <display, VGA> at device 0.0 (no driver attached)
> pci0: <serial bus, USB> at device 29.7 (no driver attached)
> pci2: <network> at device 2.0 (no driver attached)
> pci0: <multimedia, audio> at device 31.5 (no driver attached)
> pci0: <simple comms, generic modem> at device 31.6 (no driver attached)
> kayvetop#
>=20
> kayvetop# ls /dev/
> acd0 consolectl lpt0.ctl ptyp6 ttyv4
> acpi ctty mdctl random ttyv5
> ad0 cuaa0 mem stderr ttyv6
> ad0s1 cuaia0 net stdin ttyv7
> ad0s1a cuala0 net1 stdout ttyv8
> ad0s1c devctl net2 sysmouse ttyv9
> ad0s2 devstat net3 ttyd0 ttyva
> ad0s2a fd net4 ttyid0 ttyvb
> ad0s2c fido network ttyld0 ttyvc
> ad0s3 fw0 nfs4 ttyp0 ttyvd
> ad0s3b fw0.0 null ttyp1 ttyve
> ad0s3c fwmem0 pci ttyp2 ttyvf
> ad0s4 fwmem0.0 ppi0 ttyp3 ums0
> agpgart geom.ctl psm0 ttyp4 urandom
> apm io ptyp0 ttyp5 usb
> ata kbd0 ptyp1 ttyp6 usb0
> atkbd0 klog ptyp2 ttyv0 usb1
> bpf0 kmem ptyp3 ttyv1 usb2
> bpsm0 log ptyp4 ttyv2 xpt0
> console lpt0 ptyp5 ttyv3 zero
> kayvetop#
>=20
Nope, nothing there either. So, a little _more_ background is required
How are you trying to read this SD card? Are you using a USB card
reader, or is an inbuilt one? (in my experience, even inbuilt readers
are connected to USB) What happens when you plug it in? Basic stuff,
but we need to know it.
The device name you are looking for should be _umass_. Here's plugging
in a card reader on my system
Jul 7 10:52:42 computer9 kernel: umass0: SanDisk ImageMate 8 in 1,
rev 2.00/91.39, addr 2
Jul 7 10:52:43 computer9 kernel: da0 at umass-sim0 bus 0 target 0 lun 0
Jul 7 10:52:43 computer9 kernel: da0: <Generic STORAGE DEVICE 9139>
Removable Direct Access SCSI-0 device
Jul 7 10:52:43 computer9 kernel: da0: 1.000MB/s transfers
Jul 7 10:52:43 computer9 kernel: da0: Attempt to query device size
failed: NOT READY, Medium not present
Jul 7 10:52:43 computer9 kernel: (da0:umass-sim0:0:0:0): READ
CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
Jul 7 10:52:43 computer9 kernel: (da0:umass-sim0:0:0:0): CAM Status:
SCSI Status Error
Jul 7 10:52:43 computer9 kernel: (da0:umass-sim0:0:0:0): SCSI Status:
Check Condition
Jul 7 10:52:43 computer9 kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,=
0
Jul 7 10:52:43 computer9 kernel: (da0:umass-sim0:0:0:0): Medium not presen=
t
Jul 7 10:52:43 computer9 kernel: (da0:umass-sim0:0:0:0): Unretryable error
Jul 7 10:52:43 computer9 kernel: Opened disk da0 -> 6
Followed by failed attempts to query the cards that are not in any of
the other slots. I'd expect something similar.
A seperate /dev/da{n} device appears for each slot in the reader. At
least it did for me.
Nothing happens when you add a SD card. However, you will be able to
query it with fdisk ("fsidk /dev/da2" worked when I added a SD card.)
Before I could mount it, I had to convince the system to take another
look. "true > /dev/da2" has been suggested, and worked for me. Then I
could "mount -t msdos /dev/da2s1 /mnt", examine the files, umount it,
and remove it.
I hope this helps you find out what is happening your end.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d44995805070618032a1a7bea>