Dan,
I managed feeding --with-modem-manager-1 option to configuration and now
modem started fine.
What comes to that usb_modeswitch problem: there I were not careful enough.
Both versions of this distribution had same usb_modeswitch version -
identical installation. So, most likely that problem is
On Mon, 2016-11-14 at 16:28 +0200, matti kaasinen wrote:
> 2016-11-11 19:41 GMT+02:00 Dan Williams :
>
> >
> > This should be handled by usb_modeswitch. Either it's not getting
> > run
> > correctly from udev, or there's a bug in usb_modeswitch for your
> > device. The fact that you can run it
2016-11-11 19:41 GMT+02:00 Dan Williams :
> This should be handled by usb_modeswitch. Either it's not getting run
> correctly from udev, or there's a bug in usb_modeswitch for your
> device. The fact that you can run it manually probably means something
> udev related, probably the usb_modeswitc
On Fri, 2016-11-11 at 15:22 +0200, matti kaasinen wrote:
> Hi (again)!
>
> I discussed this problem originally in
> https://mail.gnome.org/archives/networkmanager-list/2016-March/msg000
> 79.html
>
> I had to upgrade my set-up that is currently as follows:
> I am using Huawei 3131 modem whose ID
Some more information:
nmcli d
DEVICE TYPE STATE CONNECTION
eth0ethernet connected eth0
lo loopback unmanaged --
wwan0 wwan unmanaged --
mmcli -m 0
/org/freedesktop/ModemManager1/Modem/0 (device id
'ec133b2df3dde8169aba5cddabc251e62f4601ec')
Hi (again)!
I discussed this problem originally in
https://mail.gnome.org/archives/networkmanager-list/2016-March/msg00079.html
I had to upgrade my set-up that is currently as follows:
I am using Huawei 3131 modem whose ID should switch from 14fe to 1506
Platform is yocto based am335x board runni