Mobile phone won't mount any more

Llama · 2013-07-30 05:12:49

Hi,

A Samsung mobile phone won't mount any more.

$ lsusb
Bus 002 Device 003: ID 04e8:0300 Samsung Electronics Co., Ltd E2530 Phone (Mass storage mode)

Until recently it used to mount trouble free, like any USB stick. USB sticks still mount just fine. No new device appears in /dev, nothing to show with fdisk or lsblk. Where do I start my research?

KDE, stock kernel, the rest also vanilla, give or take.

Last edited by Llama (2013-07-30 06:51:45)

kokoko3k · 2013-07-30 06:37:27

Dit you use to mount it in mass storage mode?
If not, maybe this is related:
https://bbs.archlinux.org/viewtopic.php?id=167282

Llama · 2013-07-30 06:51:03

kokoko3k wrote:

Dit you use to mount it in mass storage mode?

Yes, in mass storage mode, exclusively.

drcouzelis · 2013-07-30 13:31:02

Llama wrote:

Until recently...

Did it stop working after an Arch Linux update?

If an update wasn't the problem, then my guess is your USB cable is broken. I never think it's the cable, but it always seems to be the cable.

laloch · 2013-07-30 14:27:49

Hi, did you reboot the computer after last kernel update? If you forgot, the modalias magic used by udev does not work until reboot. It happens to me quite often.

Last edited by laloch (2013-07-30 14:28:32)

falconindy · 2013-07-30 16:28:42

laloch wrote:

Hi, did you reboot the computer after last kernel update? If you forgot, the modalias magic used by udev does not work until reboot. It happens to me quite often.

Err, installing a new kernel deletes all the modules for the currently running kernel. This has nothing to do with udev -- it's the simple fact that trying to load a new module post-upgrade will fail because the modules simply do not exist.

laloch · 2013-07-31 07:50:29

falconindy wrote:

This has nothing to do with udev -- it's the simple fact that trying to load a new module post-upgrade will fail because the modules simply do not exist.

Yes, and that's exactly why udev can't load them.

falconindy wrote:

Err, installing a new kernel deletes all the modules for the currently running kernel.

This, btw, is not only anoying. Deleting running kernel with all modules is what I would call a bad design (no offense meant).

Llama · 2013-07-31 09:51:10

drcouzelis wrote:

Llama wrote:
Until recently...
Did it stop working after an Arch Linux update?
If an update wasn't the problem, then my guess is your USB cable is broken. I never think it's the cable, but it always seems to be the cable.

The effect is demonstrated on two different Arch installations and two different cables. So it's either a software update or a subtle phone malfunction. It would be nice to figure out which.

Legogris · 2013-07-31 10:46:45

I think there's something going on here.
I have two Arch laptops, "adb devices" will not show anything when my Android phone is connected to either of them.
dmesg shows:

usb 1-2: new high-speed USB device number 8 using xhci_hcd
usb 1-2: can' set config #1, error -110

I've used this phone for debugging Android apps under Linux before without issues.
Same phone, same cable, same computer, same USB port shows up fine under adb devices if I reboot to Windows 8.
I'll try to roll back to a previous kernel and see if that makes any difference.

[EDIT]
/etc/udev/rules.d/51-android.rules

SUBSYSTEM=="usb",ATTR{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="0fce",ATTR{idProduct}=="6186",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="0fce",ATTR{idProduct}=="6186",SYMLINK+="android_fastboot"

Last edited by Legogris (2013-07-31 10:50:07)

Legogris · 2013-07-31 11:10:23

I tried with downgrading to linux 3.9.4, als tried the udev rukes here: https://code.google.com/p/51-android/

Whatever this is, I don't think it has to do with a recent kernel update.

msthev · 2013-07-31 13:00:22

It's definitely something with the kernel, 3.10.3 specifically:
https://bugs.archlinux.org/task/36296

I have the same issue, and downgrading (either to 3.9.9 or 3.10.2) fixes it — although in my case the problem is with USB 2.

Last edited by msthev (2013-07-31 13:04:35)

Llama · 2013-08-01 05:10:32

msthev wrote:

It's definitely something with the kernel, 3.10.3 specifically:
https://bugs.archlinux.org/task/36296
I have the same issue, and downgrading (either to 3.9.9 or 3.10.2) fixes it — although in my case the problem is with USB 2.

Right you are. 3.10.2 is the solution in my case.

Arch Linux

#1 2013-07-30 05:12:49

Mobile phone won't mount any more

#2 2013-07-30 06:37:27

Re: Mobile phone won't mount any more

#3 2013-07-30 06:51:03

Re: Mobile phone won't mount any more

#4 2013-07-30 13:31:02

Re: Mobile phone won't mount any more

#5 2013-07-30 14:27:49

Re: Mobile phone won't mount any more

#6 2013-07-30 16:28:42

Re: Mobile phone won't mount any more

#7 2013-07-31 07:50:29

Re: Mobile phone won't mount any more

#8 2013-07-31 09:51:10

Re: Mobile phone won't mount any more

#9 2013-07-31 10:46:45

Re: Mobile phone won't mount any more

#10 2013-07-31 11:10:23

Re: Mobile phone won't mount any more

#11 2013-07-31 13:00:22

Re: Mobile phone won't mount any more

#12 2013-08-01 05:10:32

Re: Mobile phone won't mount any more

Board footer