[SOLVED] SD chip does not show with lsusb

waddles · 12-14-2013, 10:13 PM

Have a vivitar 880 hd DVR with 4GB SD chip.
Pulled SD from camera an put into my DigiPower card reader and plugged it into a port on my USB
extender. I see nothing when I run lsusb.
It shows the card is locked. How do I unlock it? I do not see this in the menus.

Shadow_7 · 12-15-2013, 12:31 AM

Does it show up in /proc/partitions?

$ cat /proc/partitions

Assuming that you want to mount it and copy the contents. If you have another usb-storage device on the same bus it could be in the way per say. If you have another bus to plug it into, see if it shows up there.

waddles · 12-15-2013, 04:46 AM

Only sda & sdb show up with cat /proc/partitions.
Removed the other flash drives from the bus and still it is not showing up.
BTW the other flash drive do show up with or without the usb card reader.
Tried on another bus and still not recognized.
I had read that if the SD is "locked" (not sure of the implications) this sort of thing can happen.
Does someone know how to unlock it (DVR says it's locked but can't find how to unlock with DVR) from computer? Not sure how that would be done if the computer can't see it.
PS
I see the word lock with an arrow head pointing away from the contacts on the SD label. Don't know if this relates to the same lock as seen in the camera. I do not see any tiny micro switches on the SD (PNY 4GB) at all so cannot relate the label's lock to anything.

Shadow_7 · 12-15-2013, 07:48 AM

Does any dmesg stuff appear when plugging or unplugging that device?

# tail -f /var/log/dmesg
or
$ dmesg
(before)
$ dmesg
(after)

Or any system log info?

# tail -f /var/log/syslog

Not that it'll solve anything, but it might shine some light on possibilities. It could be unpartitioned and with some proprietary filesystem. Anybody's guess.

qlue · 12-15-2013, 09:45 AM

Linux can only read SD cards as MMC storage. If the built-in SD encryption has been activated, you'll have to open it in an SD capable device first and either copy over the content or remove the encryption.
Either way, you'll need the Secure Digital pin code to access the card.

The Secure part of the SD protocol is propriety and only available to paid members of the SD group.
There is no FOSS solution that I know of.

waddles · 12-15-2013, 07:17 PM

Not sure of what is meant by "built-in SD encryption" is that what I have referred to as "locked" i.e. as a message in the camera window or to "lock" on the SD label and is different i.e. just encoding?

Is there a general way to "unlock" the SD as the instructions that came with the camera did not discuss it? The manual is WINDOS only so cannot read it as I expunged all M$ software awhile ago.

Where do I get the secure digital pin code I was not given that when I purchased the SD. Was it supposed to be on the documentation/labels/packaging?

I turned off the "lock" with the camera. I get the same results with lsusb.
With tail -f /var/log/syslog:
After insertion:

Code:

[    6.609742] fuse init (API version 7.15)
[    7.646153] EXT4-fs (sda1): re-mounted. Opts: (null)
[    7.704765] EXT4-fs (sda1): re-mounted. Opts: (null)
[    8.158097] lp0: using parport0 (interrupt-driven).
[    8.158133] lp0: console ready
[   12.016185] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[   12.053922] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[   12.085860] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[   12.113382] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
[   12.152313] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)

After removal:

Code:

[    6.609742] fuse init (API version 7.15)
[    7.646153] EXT4-fs (sda1): re-mounted. Opts: (null)
[    7.704765] EXT4-fs (sda1): re-mounted. Opts: (null)
[    8.158097] lp0: using parport0 (interrupt-driven).
[    8.158133] lp0: console ready
[   12.016185] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[   12.053922] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[   12.085860] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[   12.113382] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
[   12.152313] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)

Sorry for length and rambling but my service provider is having problems and that gets passed down hill.

waddles · 12-16-2013, 12:33 AM

On re-examining the SD I discovered why the "lock" had an arrowhead on it. On the edge was a like colored tiny "MOVEABLE" tab which allows me to lock or unlock the SD chip. Moving the tab away from the arrowhead direction, I presume I have unlocked the hardware. I then used the camera to unlock images and video.
Now when I run tail -f /var/log/syslog I get:
After insertion:

Code:

[    6.786388] fuse init (API version 7.15)
[    7.480146] EXT4-fs (sda1): re-mounted. Opts: (null)
[    7.538188] EXT4-fs (sda1): re-mounted. Opts: (null)
[    7.984249] lp0: using parport0 (interrupt-driven).
[    7.984284] lp0: console ready
[   17.955710] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[   18.001806] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[   18.042059] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[   18.069576] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
[   18.116849] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)

While different they seem the same.

The card reader I was sold is marked sd/mmc not sdhc. Apparently, this is for the older chips up to 2GB. The chip I have is 4GB so I presume this card reader to be the problem, i.e. not sdhc compatible.

Shadow_7 · 12-16-2013, 10:08 AM

You may have a card reader built into a usb printer or on some computers. As long as it's not tooo old it should have SDHC read ability. I have a usb reader that is up to 8GB and one that is up to 16GB, but it functions with larger cards, it just can't write to the cards past their limits. If it goes into a camcorder, you might have a USB cable from the camcorder you can attach and use a PTP or other protocol, to do transfers. Sometimes camcorders will function as usb-storage devices. Take a look at gphoto2 or other options depending on the hardware in question.

http://www.vivitar.com/products/2/di...1051/dvr-880hd

It seems to have a usb cable to connect from the camcorder to the computer. And may have webcam capabilities. If you have that cable, connect it and check dmesg. Perhaps wait to turn it on until after the usb cable is connected. My camcorder Sanyo-FH1 gives you a menu when you connect this route. With various options to choose usb-storage, PTP, or camcorder modes.

waddles · 12-16-2013, 01:47 PM

Thanks 4 the help. I will look into gphoto2, thanks. Am fairly convinced now that the slot markings are SD/MMC are excluding SDHC, or it was designed for <= 2GB. So will try another reader. One last query, am I correct to think if it doesn't say writer that a card reader does not or probably doesn't write to the SD?

qlue · 12-16-2013, 04:01 PM

Quote:

Originally Posted by waddles

One last query, am I correct to think if it doesn't say writer that a card reader does not or probably doesn't write to the SD?

While that is possible, I think that it is more likely that a USB to SD card adaptor is really just an adaptor and can both read and write.
One issue though is that some adaptors may need special firmware to work at all.
My laptops all have built-in card readers which also write, so I've never needed to mess around with USB adaptors.

waddles · 12-19-2013, 06:03 PM

Solution, gave the memory card reader to a friend to check out.
It is toast.