Just found that 12.2 will not mount my mobile phone as mass storage though 12.1 had no problem at all. hwinfo gives full details of it and /var/log/messages records identifying the device when plugged in but gives different accounts of what has happened after that:
Nov 9 21:58:13 linux-9btp kernel: usb 5-1: USB disconnect, device number 5Nov 9 21:58:20 linux-9btp kernel: usb 6-1: new full-speed USB device number 8 using uhci_hcd
Nov 9 21:58:20 linux-9btp kernel: usb 6-1: New USB device found, idVendor=0e8d, idProduct=0002
Nov 9 21:58:20 linux-9btp kernel: usb 6-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Nov 9 21:58:20 linux-9btp kernel: usb 6-1: Product: MT6225
Nov 9 21:58:20 linux-9btp kernel: usb 6-1: Manufacturer: MediaTek Inc
Nov 9 21:58:20 linux-9btp kernel: usb 6-1: SerialNumber: 68204310404626f
Nov 9 21:58:20 linux-9btp mtp-probe: checking bus 6, device 8: "/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1"
Nov 9 21:58:20 linux-9btp kernel: scsi14 : usb-storage 6-1:1.0
Nov 9 21:58:20 linux-9btp mtp-probe: bus: 6, device: 8 was not an MTP device
Nov 9 21:58:20 linux-9btp udevd[7831]: failed to execute '/lib/udev/udev-acl' 'udev-acl --action= --device=/dev/bus/usb/006/008': No such file or directory
Nov 9 21:58:20 linux-9btp udevd[7837]: failed to execute '/lib/udev/udev-acl' 'udev-acl --action= --device=': No such file or directory
Nov 9 21:58:20 linux-9btp udevd[7838]: failed to execute '/lib/udev/udev-acl' 'udev-acl --action= --device=': No such file or directory
Nov 9 21:58:20 linux-9btp udevd[7840]: failed to execute '/lib/udev/udev-acl' 'udev-acl --action= --device=': No such file or directory
Nov 9 21:58:20 linux-9btp dbus-daemon[564]: **** scsi_host ADDING /sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/host14/scsi_host/host14
Nov 9 21:58:20 linux-9btp dbus-daemon[564]: **** scsi_host IGNORING ADD /sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/host14/scsi_host/host14
Nov 9 21:58:21 linux-9btp usb_modeswitch: switching device 0e8d:0002 on 006/008
Nov 9 21:58:21 linux-9btp udevd[7842]: failed to execute '/lib/udev/udev-acl' 'udev-acl --action= --device=': No such file or directory
Nov 9 21:58:21 linux-9btp dbus-daemon[564]: **** scsi_host IGNORING REMOVE /sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/host14/scsi_host/host14
Nov 9 21:58:21 linux-9btp udevd[7843]: failed to execute '/lib/udev/udev-acl' 'udev-acl --action= --device=': No such file or directory
I recently had the same issue in Fedora and Ubuntu after buying a tablet with Android 4.0. The problem is Android went to the MTP without letting others know. Apparently the issue is in OSX, older Windows, and Linux. I have com across forums to fix it but I have not yet had success. For file transfer there is a work around using filezilla.
Read it from page 3 to page 5. Hopefully, it will give you the background on this. It could be that an upgraded (less aggressive and improved libmtp library) may fix this issue:
In your case, you want don’t want your device detected as a MTP device - it could be as simple as identifying and removing the matching (offending) udev rule.
Good luck with this. I’ll try to assist further if needed.
I read the earlier thread about the Samsung Galaxy but the symptoms and experiences don’t match my experiences - which was why I started a new thread. Also I get different messages on different occasions but they all appear to revolve round udev. I’ll keep on searching and trying things.
No, the symptoms don’t match, but the info I posted regarding the udev rules (supplied by libmtp9) are likely to be the cause of your issue. What I was hinting at, was the possibility to either
Identify the particular 51-android.rules entry relating to your device’s chipset, and remove it (or comment it out).
or
Try upgrading libmtp9. For reference I have ‘libmtp9-1.1.5-1.1’ installed, which includes ‘/lib/udev/rules.d/69-libmtp.rules’, as opposed to the earlier version, which includes 51-android.rules. You may find this changes the behaviour for you, allowing the device to be detected as a storage device.
Thanks for the suggestions but my investigations have gone in a completely different direction.
Inspecting some of the earlier messages, I noted a reference to udev-acl and installed this from the Build Service (it is systemvinit related and is not part of 12.2). This resulted in all the memory devices on the mobile phone being recognised:
Nov 12 22:42:55 linux-9btp kernel: sd 4:0:0:0: [sdb] No Caching mode page present
Nov 12 22:42:55 linux-9btp kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Nov 12 22:42:55 linux-9btp kernel: sdb: sdb1
Nov 12 22:42:55 linux-9btp kernel: sd 4:0:0:1: [sdc] No Caching mode page present
Nov 12 22:42:55 linux-9btp kernel: sd 4:0:0:1: [sdc] Assuming drive cache: write through
Nov 12 22:42:55 linux-9btp kernel: sdc:
Nov 12 22:42:55 linux-9btp usb_modeswitch: switching device 0e8d:0002 on 005/002
Nov 12 22:42:55 linux-9btp kernel: sd 4:0:0:0: [sdb] No Caching mode page present
Nov 12 22:42:55 linux-9btp kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Nov 12 22:42:55 linux-9btp kernel: sd 4:0:0:0: [sdb] Attached SCSI removable disk
Nov 12 22:42:55 linux-9btp kernel: sd 4:0:0:1: [sdc] No Caching mode page present
Nov 12 22:42:55 linux-9btp kernel: sd 4:0:0:1: [sdc] Assuming drive cache: write through
Nov 12 22:42:55 linux-9btp kernel: sd 4:0:0:1: [sdc] Attached SCSI removable disk
However, I then get the message
Nov 12 22:42:55 linux-9btp udevd[1383]: inotify_add_watch(6, /dev/sdb, 10) failed: No such file or directory
for each of the devices and they are each detached in turn.
I have discovered that inotify_add_watch is a kernel call but the man page for it does not give me any information on which I am able to proceed.
I wondered about checking whether the module that supplies inotify_add_watch is part of the openSUSE kernel but any other thoughts would be welcome.
Hi
inotify_add_watch is part of udev. The way I understand it is this should run after any RUN rules. So is libnotify installed? Are you running raid or lvm on the system your connecting to?
libnotify is installed and I’m not running RAID or LVM. What you say fits because usb_modeswitch contains a rule for the device and proceeds to mount the device; it is only when inotify_add_watch is run that the device is disconnected. So why is inotify_add_watch failing to connect to the device and prompting the disconnect?
Got the same issue with my mobile phone based on Mediatek chipset. I’ve paid attention on the line
usb_modeswitch: switching device 0e8d:0002 on 005/002
The problem appered in that mobile tries to switch usb mode but has no GSM-modem, so mass-storage device simply disapear. Changing the line in /etc/usb_modeswitch.conf to