8:01 a.m.
Hello,
I am trying to setup ofono on my PC again, unfortunatly ofono does not pick up the
connected huawei modem.
I have traced it down to plugins/udev.c - get_property function.
The udev rules seems to get ok, as I can see it in the udev logs:
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.1/usb1/1-3
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/001/016
DEVTYPE=usb_device
DEVICE=/proc/bus/usb/001/016
PRODUCT=12d1/1001/0
TYPE=0/0/0
BUSNUM=001
DEVNUM=016
SEQNUM=9847
ID_VENDOR=HUAWEI_Technology
ID_VENDOR_ENC=HUAWEI\x20Technology
ID_VENDOR_ID=12d1
ID_MODEL=HUAWEI_Mobile
ID_MODEL_ENC=HUAWEI\x20Mobile
ID_MODEL_ID=1001
ID_REVISION=0000
ID_SERIAL=HUAWEI_Technology_HUAWEI_Mobile
ID_BUS=usb
ID_USB_INTERFACES=:ffffff:
OFONO_DRIVER=huawei
MAJOR=189
MINOR=15
But get_property can not find the "OFONO_DRIVER" property.
It only find the properties below:
Sep 14 23:45:56 gandalf ofonod[19789]: plugins/udev.c:get_property() Name:UDEV_LOG
Sep 14 23:45:56 gandalf ofonod[19789]: plugins/udev.c:get_property() Name:DEVPATH
Sep 14 23:45:56 gandalf ofonod[19789]: plugins/udev.c:get_property() Name:MAJOR
Sep 14 23:45:56 gandalf ofonod[19789]: plugins/udev.c:get_property() Name:MINOR
Sep 14 23:45:56 gandalf ofonod[19789]: plugins/udev.c:get_property() Name:DEVNAME
Sep 14 23:45:56 gandalf ofonod[19789]: plugins/udev.c:get_property() Name:DEVTYPE
Sep 14 23:45:56 gandalf ofonod[19789]: plugins/udev.c:get_property() Name:DRIVER
Sep 14 23:45:56 gandalf ofonod[19789]: plugins/udev.c:get_property() Name:DEVICE
Sep 14 23:45:56 gandalf ofonod[19789]: plugins/udev.c:get_property() Name:PRODUCT
Sep 14 23:45:56 gandalf ofonod[19789]: plugins/udev.c:get_property() Name:TYPE
Sep 14 23:45:56 gandalf ofonod[19789]: plugins/udev.c:get_property() Name:BUSNUM
Sep 14 23:45:56 gandalf ofonod[19789]: plugins/udev.c:get_property() Name:DEVNUM
Sep 14 23:45:56 gandalf ofonod[19789]: plugins/udev.c:get_property() Name:SUBSYSTEM
Any ideas why it does not find some properties?
Thanks, Artem
6:49 p.m.
Hi Artem,
On 09/14/2011 05:01 PM, Artem Makhutov wrote:
Hello,
I am trying to setup ofono on my PC again, unfortunatly ofono does not
pick up the connected huawei modem.
I have traced it down to plugins/udev.c - get_property function.
Please note that huawei detection is now being done by plugins/udevng.c.
Regards,
-Denis
4:03 a.m.
Hi,
Denis Kenzior schrieb:
Hi Artem,
On 09/14/2011 05:01 PM, Artem Makhutov wrote:
> Hello,
>
> I am trying to setup ofono on my PC again, unfortunatly ofono does not
> pick up the connected huawei modem.
>
> I have traced it down to plugins/udev.c - get_property function.
>
Please note that huawei detection is now being done by plugins/udevng.c.
Thanks, this is good to know.
Regards, Artem
5:48 p.m.
Hi,
Artem Makhutov schrieb:
Hello,
I am trying to setup ofono on my PC again, unfortunatly ofono does not pick up the
connected huawei modem.
[...]
I have done some more testing. Looks like the "OFONO_DRIVER=huawei" is getting
removed somehow by udev.
With "udevadm monitor --property" I can see that OFONO_DRIVER=huawei was set for
/devices/pci0000:00/0000:00:02.1/usb1/1-3
But "udevadm info --query=all --path=/devices/pci0000:00/0000:00:02.1/usb1/1-3"
does not show it.
Ofono also can't find it.
Any ideas that to do to trace down the problem?
Some logs are attached.
Thanks, Artem
12:33 a.m.
Hi Artem,
Il 15/09/2011 9.48, Artem Makhutov ha scritto:
Hi,
Artem Makhutov schrieb:
> Hello,
>
> I am trying to setup ofono on my PC again, unfortunatly ofono
> does not pick up the connected huawei modem. [...]
I have done some more testing. Looks like the "OFONO_DRIVER=huawei"
is getting removed somehow by udev.
With "udevadm monitor --property" I can see that
OFONO_DRIVER=huawei was set for
/devices/pci0000:00/0000:00:02.1/usb1/1-3 But "udevadm info
--query=all --path=/devices/pci0000:00/0000:00:02.1/usb1/1-3" does
not show it. Ofono also can't find it.
Any ideas that to do to trace down the problem?
We incurred in a similar problem some months ago, but we thought the
issue was related to some specific udev library version we were using
(v153 if I remember well).
Here is a patch we applied to ofono.rules to fix the problem, maybe it
will solve your issue, too:
@@ -0,0 +1,25 @@
+diff --git a/plugins/ofono.rules b/plugins/ofono.rules
+index 5a36380..bff8102 100644
+--- a/plugins/ofono.rules
++++ b/plugins/ofono.rules
+@@ -362,8 +362,18 @@ KERNEL=="shrm0", ENV{OFONO_DRIVER}="u8500"
+
+ LABEL="ofono_isi_end"
+
+-SUBSYSTEM!="usb", GOTO="ofono_end"
+-ENV{DEVTYPE}!="usb_device", GOTO="ofono_end"
++# Possibly unmatched rules if CONFIG_USB_DEVICE_CLASS=y
++# (deprecated config option)
++# See http://permalink.gmane.org/gmane.linux.lfs.devel/5791
++SUBSYSTEM!="usb", GOTO="test_usb_device"
++ENV{DEVTYPE}!="usb_device", GOTO="test_usb_device"
++GOTO="set_ofono_driver"
++
++LABEL="test_usb_device"
++# Workaround in case the above rules do not match
++SUBSYSTEM!="usb_device", GOTO="ofono_end"
++
++LABEL="set_ofono_driver"
+
+ # Novatel Wireless
+ ATTRS{idVendor}=="1410", ENV{OFONO_DRIVER}="novatel"
Very likely it can be rewritten in some cleaner way.
It just falls back to checking usb_device as SUBSYSTEM in addition to
what it checks now (i.e., usb as SUBSYSTEM or usb_device as ENV{DEVTYPE}).
Also current checks could probably be removed as related to some
deprecated kernel configurations, but we left there for compatibility
reasons (they appear to be harmless after all).
Hope this patch may help! :)
Some logs are attached.
Thanks, Artem
Regards,
Paolo
4:24 a.m.
Hello Paolo,
Paolo Pellegrino schrieb:
Hi Artem,
Il 15/09/2011 9.48, Artem Makhutov ha scritto:
> Hi,
>
> Artem Makhutov schrieb:
>> Hello,
>>
>> I am trying to setup ofono on my PC again, unfortunatly ofono
>> does not pick up the connected huawei modem. [...]
>
> I have done some more testing. Looks like the "OFONO_DRIVER=huawei"
> is getting removed somehow by udev.
>
> With "udevadm monitor --property" I can see that
> OFONO_DRIVER=huawei was set for
> /devices/pci0000:00/0000:00:02.1/usb1/1-3 But "udevadm info
> --query=all --path=/devices/pci0000:00/0000:00:02.1/usb1/1-3" does
> not show it. Ofono also can't find it.
>
> Any ideas that to do to trace down the problem?
We incurred in a similar problem some months ago, but we thought the
issue was related to some specific udev library version we were using
(v153 if I remember well).
[...]
Yes this patch solved it. I am using udev 171-r2 on gentoo linux.
Thank you, Artem
4021
days inactive
4022
days old
5 comments
3 participants
participants (3)
-
Artem Makhutov -
Denis Kenzior -
Paolo Pellegrino