On 2010-12-15 16:19, DenverD wrote:
> Carlos E. R. wrote:
>> On 2010-12-15 11:31, DenverD wrote:
>>> what operating system, version, desktop environment and update status?
>>
>> He said “CLI”. >:-)
>
> oh!
> i don’t know…but, i think you will find the device in or near
>
>
> /dev/bus/001/005
>
>
> i say that because i just plugged in my cannon which dmesg calls “usb
> 3-8 … at address 4” and i find a new device entry timed just about
> now which is /dev/bus/usb/003/004
Let me see.
I just plugged a sub stick, which said:
<0.6> 2010-12-15 16:44:35 Telcontar kernel - - - [332117.259017] usb 1-6:
new high speed USB device using ehci_hcd and address 2
and "/dev/bus/usb/001/006 does not exist. Doing a “ls -ltr
/dev/bus/usb/00*/*” the last one is:
crw-rw-r-- 1 root root 189, 1 Dec 15 16:44 /dev/bus/usb/001/002
And it is not mountable:
Telcontar:~ # file -s /dev/bus/usb/001/002
/dev/bus/usb/001/002: data
Doing a “ls -ltr /dev/sd* | tail” reveals that the device node is:
brw-rw---- 1 root disk 8, 48 Dec 15 16:44 /dev/sdd
brw-rw---- 1 root disk 8, 49 Dec 15 16:44 /dev/sdd1
which do reveal as disks or partitions:
Telcontar:~ # file -s /dev/sdd /dev/sdd1
/dev/sdd: x86 boot sector; partition 1: ID=0xb, starthead 0, startsector
44, 15679396 sectors, extended partition table (last)\011, code offset 0x0
/dev/sdd1: x86 boot sector, code offset 0x0, OEM-ID " ",
sectors/cluster 64, Media descriptor 0xf8, heads 255, hidden sectors 44,
sectors 15679396 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 1914, serial
number 0xyyyyxxxx, label: "SANDISK_2 "
What I do is watch the log when I plug a device - something like this is
printed:
usb-storage: device scan complete
sd 12:0:0:0: [sdd] Attached SCSI removable disk
sd 12:0:0:0: [sdd] 15695871 512-byte logical blocks: (8.03 GB/7.48 GiB)
sd 12:0:0:0: [sdd] Assuming drive cache: write through
sd 12:0:0:0: [sdd] Assuming drive cache: write through
sdd: sdd1
which reveal the device name. If these entries do not appear, then the
device was not recognised as a disk. Some devices have two modes of
operations, one as a disk, another as something else that needs a special
program to connect to them. This happens to the the TomTom, to Nokia
phones, etc. A camera can behave in a similar way, I assume. Something has
to be done in the device to tell it to behave as a disk. Or a special
software used - if it exists for Linux.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)