can't see SD card
KAYVEN RIESE
kayve at sfsu.edu
Thu Jul 7 01:29:31 GMT 2005
hmm.. is this useful?
Path: /usr/ports/sysutils/cdrtools
(root at www) 109> sysctl -a | less
::clip::
dev.cbb.1.wake: 0
dev.cardbus.%parent: pci
dev.cardbus.0.%desc: CardBus bus
dev.cardbus.0.%driver: cardbus
dev.cardbus.0.%parent: cbb0
dev.cardbus.1.%desc: CardBus bus
dev.cardbus.1.%driver: cardbus
dev.cardbus.1.%parent: cbb1
dev.pccard.0.%desc: 16-bit PCCard bus
dev.pccard.0.%driver: pccard
dev.pccard.0.%parent: cbb0
dev.pccard.1.%desc: 16-bit PCCard bus
dev.pccard.1.%driver: pccard
dev.pccard.1.%parent: cbb1
dev.fwohci.0.%desc: Ricoh R5C552
dev.fwohci.0.%driver: fwohci
dev.fwohci.0.%location: slot=1 function=2 handle=\_SB_.PCI0.P0P2.ILNK
dev.fwohci.0.%pnpinfo: vendor=0x1180 device=0x0552 subvendor=0x1043
subdevice=0x
1867 class=0x0c0010
dev.fwohci.0.%parent: pci2
dev.firewire.0.%desc: IEEE1394(FireWire) bus
dev.firewire.0.%driver: firewire
:dev.sbp.0.%driver: sbp
dev.sbp.0.%parent: firewire0
dev.isab.0.%desc: PCI-ISA bridge
dev.isab.0.%driver: isab
dev.isab.0.%location: slot=31 function=0 handle=\_SB_.PCI0.SBRG
dev.isab.0.%pnpinfo: vendor=0x8086 device=0x24cc subvendor=0x0000
subdevice=0x00
00 class=0x060100
dev.isab.0.%parent: pci0
dev.isa.0.%desc: ISA bus
dev.isa.0.%driver: isa
dev.isa.0.%parent: isab0
dev.atapci.0.%desc: Intel ICH4 UDMA100 controller
dev.atapci.0.%driver: atapci
dev.atapci.0.%location: slot=31 function=1 handle=\_SB_.PCI0.IDE0
dev.atapci.0.%pnpinfo: vendor=0x8086 device=0x24ca subvendor=0x1043
subdevice=0x
1869 class=0x01018a
dev.atapci.0.%parent: pci0
dev.ata.0.%desc: ATA channel 0
:
On Thu, 7 Jul 2005, Robert Backhaus wrote:
> Thanks for the background.
>
> On 7/7/05, KAYVEN RIESE <kayve at 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.
> >
> >
> > here is the result of the command "usbdevs"
> >
> > Path: /home/kayve <~~~~~~ .login i have uses a two line prompt.. this
> > is line one
> > (root at www) 103> usbdevs <~~~~~second line of prompt and the command
> >
> > 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
> >
> > <---end of output----->
> OK, big hint: I see not card reader device.
> >
> >
> > next i was told to do the command "pciconf -l -v"
> > and i did, and selected out "class = mass storage"
> >
> > i did thatmanually, here is the result
> >
> >
> > atapci0 at pci0:31:1: class=0x01018a card=0x18691043 chip=0x24ca8086
> > rev=0x03
> > hdr=0x00
> > vendor = 'Intel Corporation'
> > device = '82801DBM (ICH4-M) UltraATA/100 EIDE Controller'
> > class = mass storage
> > subclass = ATA
> > none0 at pci0:31:5: class=0x040100 card=0x17131043 chip=0x24c58086
> > rev=0x03
> > hdr=0x00
>
> Again: no card reader
>
> >
> > i was told i am hosed.
> >
> >
> > Path: /home/kayve
> > (kayve at kayvetop) 101> su
> > Password: <~~~~ becoming superuser
> >
> > kayvetop# sysctl kern.disks kern.rootdev <~~~ prompt = "kayvetop#"
> > kern.disks: ad0
> > kern.rootdev: ad0s2a
> > kayvetop#
> >
> >
> > 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#
> >
> > 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#
> >
>
> 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 present
> 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.
> _______________________________________________
> freebsd-bugs at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
> To unsubscribe, send any mail to "freebsd-bugs-unsubscribe at freebsd.org"
>
More information about the freebsd-bugs
mailing list