Arch Linux

dejy

Member

Registered: 2014-03-18

Posts: 67

Modprobe failing to resolve alias for Samsung S4

udevadm monitor --environment --udev

UDEV  [17679.339440] add      /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2 (usb)
ACTION=add
BUSNUM=003
DEVLINKS=/dev/libmtp /dev/libmtp-3-1.2
DEVNAME=/dev/bus/usb/003/024
DEVNUM=024
DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2
DEVTYPE=usb_device
ID_BUS=usb
ID_FOR_SEAT=usb-pci-0000_00_1a_0-usb-0_1_2
ID_MEDIA_PLAYER=1
ID_MODEL=SAMSUNG_Android
ID_MODEL_ENC=SAMSUNG_Android
ID_MODEL_FROM_DATABASE=GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1] , GT-I9500 [Galaxy S 4]
ID_MODEL_ID=6860
ID_MTP_DEVICE=1
ID_PATH=pci-0000:00:1a.0-usb-0:1.2
ID_PATH_TAG=pci-0000_00_1a_0-usb-0_1_2
ID_REVISION=0400
ID_SERIAL=SAMSUNG_SAMSUNG_Android_0aa40861
ID_SERIAL_SHORT=0aa40861
ID_USB_INTERFACES=:060101:020201:0a0000:
ID_VENDOR=SAMSUNG
ID_VENDOR_ENC=SAMSUNG
ID_VENDOR_FROM_DATABASE=Samsung Electronics Co., Ltd
ID_VENDOR_ID=04e8
MAJOR=189
MINOR=279
PRODUCT=4e8/6860/400
SEQNUM=1986
SUBSYSTEM=usb
TAGS=:seat:uaccess:
TYPE=0/0/0
UDEV_LOG=7
USEC_INITIALIZED=9206113

UDEV  [17679.405184] add      /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0
DEVTYPE=usb_interface
ID_MODEL_FROM_DATABASE=GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1] , GT-I9500 [Galaxy S 4]
ID_VENDOR_FROM_DATABASE=Samsung Electronics Co., Ltd
INTERFACE=6/1/1
MODALIAS=usb:v04E8p6860d0400dc00dsc00dp00ic06isc01ip01in00
PRODUCT=4e8/6860/400
SEQNUM=1987
SUBSYSTEM=usb
TYPE=0/0/0
UDEV_LOG=7
USEC_INITIALIZED=9207464

from journalctl

 
-- Logs begin at Mon 2014-03-17 23:17:24 EDT, end at Tue 2014-11-11 18:53:08 EST. --
Nov 11 18:53:08 l-pc systemd-udevd[4493]: seq 1987 processed with 0
Nov 11 18:53:08 l-pc systemd-udevd[4493]: passed -1 bytes to netlink monitor 0x7f053fe92600
Nov 11 18:53:08 l-pc systemd-udevd[4493]: Assertion 'rtnl' failed at src/libsystemd/sd-rtnl/sd-rtnl.c:144, function sd_rtn
Nov 11 18:53:08 l-pc systemd-udevd[4493]: 'lmt-udev force modules=runtime-pm devices=3-1.2:1.0' [4657] exit with return co
Nov 11 18:53:08 l-pc systemd-udevd[4493]: 'lmt-udev force modules=runtime-pm devices=3-1.2:1.0'(out) 'enabled, not active'
Nov 11 18:53:08 l-pc laptop-mode[4701]: enabled, not active
Nov 11 18:53:08 l-pc systemd-udevd[4493]: 'lmt-udev force modules=runtime-pm devices=3-1.2:1.0'(out) 'Laptop mode '
Nov 11 18:53:08 l-pc laptop-mode[4700]: Laptop mode
Nov 11 18:53:07 l-pc systemd-udevd[4657]: starting 'lmt-udev force modules=runtime-pm devices=3-1.2:1.0'
Nov 11 18:53:07 l-pc systemd-udevd[4493]: no module matches 'usb:v04E8p6860d0400dc00dsc00dp00ic06isc01ip01in00'
Nov 11 18:53:07 l-pc systemd-udevd[4493]: execute 'load' 'usb:v04E8p6860d0400dc00dsc00dp00ic06isc01ip01in00'
Nov 11 18:53:07 l-pc systemd-udevd[4493]: created db file '/run/udev/data/+usb:3-1.2:1.0' for '/devices/pci0000:00/0000:00
Nov 11 18:53:07 l-pc systemd-udevd[4493]: RUN 'lmt-udev force modules=runtime-pm devices=%k' /usr/lib/udev/rules.d/99-lapt
Nov 11 18:53:07 l-pc systemd-udevd[4493]: RUN 'kmod load $env{MODALIAS}' /usr/lib/udev/rules.d/80-drivers.rules:5
Nov 11 18:53:07 l-pc systemd-udevd[4493]: device 0x7f053fe7e010 filled with db file data
Nov 11 18:53:07 l-pc systemd-udevd[4493]: IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/50-udev-default.rules:11
Nov 11 18:53:07 l-pc systemd-udevd[4493]: device 0x7f053fe74930 has devpath '/devices/pci0000:00'
Nov 11 18:53:07 l-pc systemd-udevd[4493]: device 0x7f053fe74550 has devpath '/devices/pci0000:00/0000:00:1a.0'
Nov 11 18:53:07 l-pc systemd-udevd[4493]: device 0x7f053fe6d5c0 has devpath '/devices/pci0000:00/0000:00:1a.0/usb3'
Nov 11 18:53:07 l-pc systemd-udevd[4493]: device 0x7f053fe7e7f0 has devpath '/devices/pci0000:00/0000:00:1a.0/usb3/3-1'
Nov 11 18:53:07 l-pc systemd-udevd[4493]: device 0x7f053fe7e010 has devpath '/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1
Nov 11 18:53:07 l-pc systemd-udevd[4493]: no db file to read /run/udev/data/+usb:3-1.2:1.0: No such file or directory
Nov 11 18:53:07 l-pc systemd-udevd[4493]: seq 1987 running
Nov 11 18:53:07 l-pc systemd-udevd[171]: passed 312 bytes to netlink monitor 0x7f053fe65580
Nov 11 18:53:07 l-pc systemd-udevd[4493]: seq 1986 processed with 0
Nov 11 18:53:07 l-pc systemd-udevd[4493]: passed -1 bytes to netlink monitor 0x7f053fe92600
Nov 11 18:53:07 l-pc systemd-udevd[4493]: Assertion 'rtnl' failed at src/libsystemd/sd-rtnl/sd-rtnl.c:144, function sd_rtn
Nov 11 18:53:07 l-pc systemd-udevd[4493]: 'lmt-udev force modules=runtime-pm devices=3-1.2' [4602] exit with return code 0
Nov 11 18:53:07 l-pc systemd-udevd[4493]: 'lmt-udev force modules=runtime-pm devices=3-1.2'(out) 'enabled, not active'
Nov 11 18:53:07 l-pc laptop-mode[4644]: enabled, not active

since modprobe -R also fails to resolve the alias, I don't actually know which module it was supposed to load, so I'm not sure how to handle this one. If anyone else is connecting said device, I could try loading that through a script rather than udev rules (I know udev is calling libkmod, but the result is the same).

Last edited by dejy (2014-11-12 00:07:12)

dejy

Member

Registered: 2014-03-18

Posts: 67

Re: Modprobe failing to resolve alias for Samsung S4

Still haven't solved this - can anyone loading an android device inform me which kernel module libkmod normally calls for them?

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: Modprobe failing to resolve alias for Samsung S4

My current Android 4.4 device - HTC One M8 - works just fine with no kernel modules at all, since it uses MTP for file management. It might help if you define exactly what "loading an android device" means to you - to me, it means "mounting an android device".

dejy

Member

Registered: 2014-03-18

Posts: 67

Re: Modprobe failing to resolve alias for Samsung S4

My current Android 4.4 device - HTC One M8 - works just fine with no kernel modules at all, since it uses MTP for file management. It might help if you define exactly what "loading an android device" means to you - to me, it means "mounting an android device".

I don't see how that's possible, udev itself doesn't load devices, just executes rules and calls libkmod for the appropriate kernel modules, my problem is that certain specific mpt implementations (specifically simple-mtpfs) work, but none of the other one's do, and neither does the default lib udev mounting rule (which used to work pre 3.17)- you can see the call here:
p.s.(I don't know much about how libmtp works, but I suspect that's not the problem here, feel free to correct me if I'm wrong).

Nov 11 18:53:07 l-pc systemd-udevd[4493]: no module matches 'usb:v04E8p6860d0400dc00dsc00dp00ic06isc01ip01in00'
Nov 11 18:53:07 l-pc systemd-udevd[4493]: execute 'load' 'usb:v04E8p6860d0400dc00dsc00dp00ic06isc01ip01in00'

The relevant call being from udev-builtin-kmod.c load module:

err = kmod_module_new_from_lookup(ctx, alias, &list);
if (err < 0)
return err;
if (list == NULL)
log_debug("no module matches '%s'", alias);

If someone for whom udev loads android devicies / samsung phones properly can post their udev output from journalctl with udev.conf logging level set on debug, that might help me a lot.

Last edited by dejy (2014-11-19 00:05:29)

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: Modprobe failing to resolve alias for Samsung S4

A few things:
- what exactly do you mean by the phrase "load an android device"? I asked already, but you didn't answer.
- what exactly are you trying to do with your android device?
- if you've found one MTP utility that works for you, congratulations - just go ahead and use it. MTP is a horribly flaky experience for all of us, you've just joined the club.

dejy

Member

Registered: 2014-03-18

Posts: 67

Re: Modprobe failing to resolve alias for Samsung S4

A few things:
- what exactly do you mean by the phrase "load an android device"? I asked already, but you didn't answer.
- what exactly are you trying to do with your android device?
- if you've found one MTP utility that works for you, congratulations - just go ahead and use it. MTP is a horribly flaky experience for all of us, you've just joined the club.

I'm trying to get udev to auto mount it =/ It used to work with pcmanfm pre 3.17 - but as you can see udev (libkmod) fails to resolve the modalias (which is a new problem).

I don't think things that don't work clubs - it's 2014 not 97' >_>

Last edited by dejy (2014-11-20 21:17:35)