I am running Suse 13.2. When insering my Casio still camera in a USB port the device is recognized and to some extent processed. Part of the /var/log/messages shows
usb 11-4: new full-speed USB device number 2 using ohci-pci
usb 11-4: New USB device found, idVendor=07cf, idProduct=1001
usb 11-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 11-4: Product: CASIO QV DIGITAL
usb 11-4: Manufacturer: CASIO COMPUTER
linux mtp-probe: checking bus 11, device 2: "/sys/devices/pci0000:00/0000:00:16.0/usb11/11-4"
linux mtp-probe: bus: 11, device: 2 was not an MTP device
colord: Device added: sysfs-CASIO_COMPUTER-CASIO_QV_DIGITAL
usb-storage 11-4:1.0: USB Mass Storage device detected
usb-storage 11-4:1.0: Quirks match for vid 07cf pid 1001: a
scsi7 : usb-storage 11-4:1.0
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver uas
In earlier versions a filessystem was mounted under /media,
now reputedly somewhere under /run/media but I can find no no such directory.
Do I have to mount the device myself somewhere? I am lost and would appreciate help.
This is in fact about mounting a mass storage device (if it is alkso a camera or not is of no consequence).
Mass storage devices connected during a users GUI session, are offered to the usert (“in the seat”, there can be more users loged in of course), through a pop-up notifier. The user can then access the file system(s) on the device by e.g. saying it wants to start a file manager for it. There is no need for the user to have any knowledge about the mount point the system uses to facilitate this.
BTW, does this not happen in your case?
According to this reasoning, the change of the algorithm behind the creation of such a mount point is internal and not something the user should bother about.
When you, on the other hand, want to have such a device mounted on a mount point of your own choice, you can create an entry in etc/fstab for it.
The device must then be identified by e.g. using a label or UUID (and not /dev/sdXN);
Do not forget to add the noauto option (else the system will want to mount the device n boot).
you may want to add the users option to allow the user to mount/umount .
Do not forget to create the mount point (e.g. within /mnt) a root and to give it enough permissions to allow normal users to use the mounted file system.
When there is such an /etc/fstab entry, the desktop pop-up will not happen.
On 2015-04-22 10:16, fennema wrote:
>
> I am running Suse 13.2. When insering my Casio still camera in a USB
> port the device is recognized and to some extent processed. Part of the
> /var/log/messages shows
A friend of mine has that camera or very similar. CASIO QV DIGITAL, idVendor=07cf, idProduct=115a. Some days the disk appears, some days it doesn’t. Not in her computer using Windows, nor in mine using Linux. I think I even tried Windows on my laptop.
Sometimes it works fine, some times it simply does not.
The problem is that the partition table does not appear.
What I do is remove the internal memory card from the camera, and insert it directly into my laptop, which has a card reader. Or use an external reader, they are very cheap.
I reply specifically to Henk van Velden but note and will also look into the other replies. Thanks.to all.
No. For an ‘ordinary’ USB mass storage sticks the popup works (and the /run/media/<user>… entry appears) but it doesn’t for the camera mass storage device.
I have no special entry in /etc/fstab.
While I will accept your answer as satisfying, it is not what I asked for. My advice is that you answer people, who try to help you here, which what they ask for as further information. And when you, for whatever reason, are not able/willing to provide it, then please explain why you don’t. Else they might ignore your thread from then on.
And when you post computer text, please do so between CODE tags. it is the # button in the tool bar of the post editor.
And for your problem, I am a bit at lost at the moment. Your first post says:
usb-storage 11-4:1.0: USB Mass Storage device detected
but no device file seems to be created for it.
Let me think this over a bit (or maybe another one tunes in here).
Hm, wait re-reading what you say is that you have normaly sda and sdb, but what then is scd where you have some output from.
Sorry, my answer suffered from some technical problems with the web-site. And I could not correct it anymore before posting.
I understand that sdc is some other USB mass-storage. so my last question is futile. But I still think it is better to post the full fdisk list for all that want to help you here.
On 2015-04-25 19:26, hcvv wrote:
>
> Sorry, my answer suffered from some technical problems with the
> web-site. And I could not correct it anymore before posting.
>
> I understand that sdc is some other USB mass-storage. so my last
> question is futile. But I still think it is better to post the full
> fdisk list for all that want to help you here.
What he says is that there is no output from fdisk related to the
camera. Which matches what I said about my friend’s camera: the computer
sees the “disk”, but not the partitions in it.
When he plugs an usb stick he gets what is expected from fdisk:
Device Boot Start End Sectors Size Id Type
/dev/sdc1 8064 15495167 15487104 7.4G c W95 FAT32 (LBA)
When he plugs in the camera, there are no entries.
And this is exactly the same that happens to me.
Hmmm… I note that the uas driver is loaded too. This is a USB 3 protocol for USB attached SCSI devices, but maybe the Casio camera doesn’t support UAS? It is detected only as a full-speed device, so it’s not clear to me why uas is loaded with regards to this device.
usb-storage 11-4:1.0: USB Mass Storage device detected
usb-storage 11-4:1.0: Quirks match for vid 07cf pid 1001: a
scsi7 : usb-storage 11-4:1.0
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver uas
I’d be tempted to blacklist the module and observe whether this then problem goes away. It might be that a bug report is needed.
Apologies I hadn’t seen the reply from deano_ferrari. The original text of this message may well become totally irrelevant. I will first look into his very reasonable suggestion.
Enno
I have no idea why you post this. That is all clear. I have read what he says. But, as you know very well, we are always suspicious when people tell their conclusions and interpretations instead of showing the computer facts. If I remember correctly, it was you that, joking, once said: we do not trust people, we trust computers. And if somebody asks for an fdisk -l listing, he waits for an fdisk -l listing and not for just one line of it without any coherency.
In many cases, like this one, people who try to help want to see the same things they would try when it was their own system. Just for gathering information until on some point the “Aha” sounds. This does not work when that information is first filtered with the best intentions.
I didn’t try to filter information. I wrote my first program in 1968 for an
Electrologica X8 computer which had a drum memory of 10,000 27 bit words. I
can’t remember how big, or small, the main memory was. I am still surprised
about todays storage capacities, memory sizes and try to keep programs, files
and postings small. Probably I shouldn’t.
Quite likely Casio struggles with USB3.0 as lsusb -v shows
Bus 011 Device 002: ID 07cf:1001 Casio Computer Co., Ltd QV-8000SX/5700/3000EX Digicam; Exilim EX-M20
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x07cf Casio Computer Co., Ltd
idProduct 0x1001 QV-8000SX/5700/3000EX Digicam; Exilim EX-M20
bcdDevice 10.00
iManufacturer 1 CASIO COMPUTER
iProduct 2 CASIO QV DIGITAL
iSerial 0
bNumConfigurations 2
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 69
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 5 SFF-8070i
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 5
bInterfaceProtocol 1
iInterface 3 DirectPrintPULL_0100
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 32
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 2
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 6 Imaging
bInterfaceSubClass 1 Still Image Capture
bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470)
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 100
Device Status: 0x0001
Self Powered
Anyway, I have added a line ‘blacklist uas’ to /etc/modprobe.d/99-local.conf,
rebooted (lsmod confirms uas not loaded) and then inserted the Casio (lsmod
shows uas now loaded).
linux:/home/enno # lsmod
Module Size Used by
uas 27255 0
usb_storage 62302 1 uas
bnep 19624 2
bluetooth 483238 5 bnep
...
Kernel messages show uas pulled in and registered as a driver.as before
2015-04-26T13:23:06.233906+02:00 linux kernel: 62.271642] nouveau E PFIFO][0000:01:00.0] PBDMA0: ch 1 [DRM] subc 5 mthd 0x0500 data 0x00000000
2015-04-26T13:24:07.837643+02:00 linux kernel: 123.972504] usb 11-4: new full-speed USB device number 2 using ohci-pci
2015-04-26T13:24:07.989572+02:00 linux kernel: 124.124777] usb 11-4: New USB device found, idVendor=07cf, idProduct=1001
2015-04-26T13:24:07.989592+02:00 linux kernel: 124.124784] usb 11-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
2015-04-26T13:24:07.989596+02:00 linux kernel: 124.124789] usb 11-4: Product: CASIO QV DIGITAL
2015-04-26T13:24:07.989598+02:00 linux kernel: 124.124793] usb 11-4: Manufacturer: CASIO COMPUTER
2015-04-26T13:24:07.995080+02:00 linux mtp-probe: checking bus 11, device 2: "/sys/devices/pci0000:00/0000:00:16.0/usb11/11-4"
2015-04-26T13:24:08.005905+02:00 linux mtp-probe: bus: 11, device: 2 was not an MTP device
2015-04-26T13:24:08.008108+02:00 linux colord: Device added: sysfs-CASIO_COMPUTER-CASIO_QV_DIGITAL
2015-04-26T13:24:08.058567+02:00 linux kernel: 124.194667] usb-storage 11-4:1.0: USB Mass Storage device detected
2015-04-26T13:24:08.059565+02:00 linux kernel: 124.194877] usb-storage 11-4:1.0: Quirks match for vid 07cf pid 1001: a
2015-04-26T13:24:08.059579+02:00 linux kernel: 124.194935] scsi7 : usb-storage 11-4:1.0
2015-04-26T13:24:08.059582+02:00 linux kernel: 124.195118] usbcore: registered new interface driver usb-storage
2015-04-26T13:24:08.064573+02:00 linux kernel: 124.200202] usbcore: registered new interface driver uas
2015-04-26T13:27:19.034082+02:00 linux org.gnome.Caribou.Daemon[1173]: ** (caribou:1406): WARNING **: daemon.vala:119: error in focus handler: Method "GetRole" with signature "" on interface "org.a11y.atspi.Accessible" could not be processed as object /org/a11y/atspi/accessible/972 does not exist
2015-04-26T13:27:19.187469+02:00 linux kernel: 315.627390] nouveau E PFIFO][0000:01:00.0] PBDMA0: LBREQ
The usb_storage module appears to pull in uas and my blacklist attempt failed.
What can I try now?
My answer was mainly to Carlos. But in fact you did. And as I said above “with the best intentions”. And I try to get the message through that a copy/paste of the complete prompt, command, output, next prompt sequence is almost as easy (when not easier) then picking out some lines you think are important. It nevertheless will give much more information to those who try to help. This is the general case. And I already said that I accept your cut down info in this case.
I see in that USB listing that the device also supports the PTP (Picture Transfer Protocol). Could it be that Digicam works with it in this case?
I know of cameras where you can switch from mass-storage to PTP (and v.v. of course) on the camera (see the camera manual). But I always thought that only one of those features at a time would show up. Not sure about it now.
Yes, that’s what I’m saying, it is a camera issue. As I said, the Casio
camera I tested doesn’t work in Linux nor Windows (tested on two
computers). And then, next week it works in both. My friend is not aware
of having done anything (and she is non-technical).
The symptom in Linux is that the mass storage device appears, but Linux
is unable to see the partitions, fdisk fails.
The one I tried is USB2 only.
(I also tried shotwell, no go)
Yes, I remember saying that I’m a non believer
But this time I have the advantage of having played with the same issue
and being baffled by it.
I do not see you anywhere saying “Check the camera for PTP/mass-storage setting” or similar. But I may misinterprete what you try to explain. Or maybe I missed some of your NNTP smileys :\
I have checked the camera and there is a menu allowing selection of either USB-Direct alias mass storage or PictBridge alias PTP.
Changing the setting to PTP caused the popup to pop up on inseretion. Gimp now recognizes a place ‘CASIO QV DIGITAL PTP’ and can read files from there.
