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
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
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
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
Thanks Aleksander. I checked build logs and indeed, configure log said:
modemmanager-1: no
I re-run networkmanager recipe and it switched to "yes". I don't know how
this can happen.
There is no explicit "--with-modem-manager-1" in the networkmanager recipe
(meta-openembedded layer), so most
On Mon, Mar 14, 2016 at 2:55 PM, matti kaasinen
wrote:
> In fact there are two more messages preceding those ones I mentioned before,
> but I guess they have nothing to do with this problem. I'll get following
> messages, if I have MM running from boot:
>
>
Yes, mmcli seems workin quite nicely - no problems at all.
2016-03-14 16:27 GMT+02:00 Dan Williams :
> On Mon, 2016-03-14 at 15:55 +0200, matti kaasinen wrote:
> > In fact there are two more messages preceding those ones I mentioned
> > before, but I guess they have nothing to
On Mon, 2016-03-14 at 15:55 +0200, matti kaasinen wrote:
> In fact there are two more messages preceding those ones I mentioned
> before, but I guess they have nothing to do with this problem. I'll
> get
> following messages, if I have MM running from boot:
>
> src/nm-udev-manager.c:568]
In fact there are two more messages preceding those ones I mentioned
before, but I guess they have nothing to do with this problem. I'll get
following messages, if I have MM running from boot:
src/nm-udev-manager.c:568] handle_uevent(): UDEV event: action 'add' subsys
'net' device 'wwan0'
There was also other one besides these (re)launch messages. The first
message was:
modem_manager_disappeared(): trying to start the modem manager...
then repeating gradually:
Requesting to (re)launch modem-manager...
2016-03-14 15:35 GMT+02:00 matti kaasinen :
> I
I tried it now: NM can't communicate with MM. There is only one type of
message related to modem-manager:
src/modem-manager/nm-modem-manager.c:280] poke_modem_cb(): Requesting to
(re)launch modem-manager...
-Matti
2016-03-14 15:01 GMT+02:00 Aleksander Morgado :
> On
On Mon, Mar 14, 2016 at 1:57 PM, matti kaasinen
wrote:
> 2016-03-14 14:53 GMT+02:00 Thomas Haller :
>>
>> > I can't get modem device listed with
>> > nmcli c
>>
>> do you mean `nmcli d` (for [d]evice)?
>
>
>
> Yes, indeed.
> BTW, I just monitored dbus
2016-03-14 14:53 GMT+02:00 Thomas Haller :
> > I can't get modem device listed with
> > nmcli c
>
> do you mean `nmcli d` (for [d]evice)?
>
Yes, indeed.
BTW, I just monitored dbus traffic (dbus-monitor --system) and it seems
that all the information received by mmcli is seen
On Mon, 2016-03-14 at 13:48 +0200, matti kaasinen wrote:
> Hi!
>
> I can't get modem device listed with
> nmcli c
do you mean `nmcli d` (for [d]evice)?
> command. So, NM does not see it and therefore it can't start
> connection with NM.
> Last week it worked fine. I wrote python code for
Hi!
I can't get modem device listed with
nmcli c
command. So, NM does not see it and therefore it can't start connection
with NM.
Last week it worked fine. I wrote python code for bringing gathering up
data from from modem interfrace for NM. Then NM could identify this modem
and I got
17 matches
Mail list logo