Hey guys,
I've checked out the Network manager software from git repository
, but it's
unclear to me how I can build and start up the Network Manager daemon?
Cheers,
Morten
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.g
I was able to build NM 1.4.2 with G-I enabled, and have now moved up to
1.8/master.
But hitting a build failure (cross-compiling, in Yocto):
| make[2]: Entering directory
`/home/colin/100051-karo/fsl-community-bsp/build/tmp/work/cortexa9hf-neon-po
ky-linux-gnueabi/networkmanager/1.8-r0/build'
| gl
I have a USB cellular modem that will not show up in nm on boot. If the system
is started up and I unplug and plug it back in, it shows up then. These device
are deployed out in the field, so manual intervention is not a real option for
my use case unfortunately.
device is ttyUSB3 and does no
On Thu, 2017-03-30 at 09:56 +0200, Morten Albeck Nielsen wrote:
> Hey guys,
> I've checked out the Network manager software from git repository,
> but it's unclear to me how I can build and start up the Network
> Manager daemon?
>
> Cheers,
> Morten
Hi,
See https://wiki.gnome.org/Projects/Networ
On Thu, 2017-03-30 at 11:07 +0100, colin.helliw...@ln-systems.com
wrote:
> I was able to build NM 1.4.2 with G-I enabled, and have now moved up
> to
> 1.8/master.
> But hitting a build failure (cross-compiling, in Yocto):
>
> > make[2]: Entering directory
>
> `/home/colin/100051-karo/fsl-communit
> On 30 March 2017 at 16:09 Thomas Haller wrote:
>
> On Thu, 2017-03-30 at 11:07 +0100, colin.helliw...@ln-systems.com
> wrote:
>
> > I was able to build NM 1.4.2 with G-I enabled, and have now moved up
> > to
> > 1.8/master.
> > But hitting a build failure (cross-compiling, in Yocto):
> >
...
> On 30 March 2017 at 16:09 Thomas Haller wrote:
>
> On Thu, 2017-03-30 at 11:07 +0100, colin.helliw...@ln-systems.com
> wrote:
>
> > I was able to build NM 1.4.2 with G-I enabled, and have now moved up
> > to
> > 1.8/master.
> > But hitting a build failure (cross-compiling, in Yocto):
> >
...
I tried to analyze log files from one card having problematic connection.
First my set-up briefly:
1) Embedded Linux card behind Huawei E3131 modem connection + NM & MM.
2) Drivers: Option and huawei_cdc_ncm.
3) Connection monitor with following functionality:
- monitoring frequency 10 minutes
- mo
On Thu, 2017-03-30 at 17:05 +0100, Colin Helliwell wrote:
> > On 30 March 2017 at 16:09 Thomas Haller wrote:
> >
> > On Thu, 2017-03-30 at 11:07 +0100, colin.helliw...@ln-systems.com
> > wrote:
> >
> > > I was able to build NM 1.4.2 with G-I enabled, and have now moved
> > > up
> > > to
> > > 1.
On Wed, 2017-03-29 at 10:48 -0400, Liam Monahan wrote:
> I have a USB cellular modem that will not show up in nm on boot. If
> the system is started up and I unplug and plug it back in, it shows
> up then. These device are deployed out in the field, so manual
> intervention is not a real option f
> On 30 March 2017 at 17:34 Thomas Haller wrote:
>
> Hi,
>
> Not surprisingly, when cross compiling, you also need python and
> pygobject in the other architecture.
>
> That makes it rather cumbersome.
>
> As I wrote in the other email, you can pre-generate those files on
> another host, duri
Observed the same behavior with NM 1.6.2
On Thu, Mar 30, 2017 at 8:29 AM, Florin wrote:
> And here are the wpa_supplicant logs:
>
> Mar 27 14:20:30 cdeeb95 systemd[1]: Starting WPA supplicant...
> Mar 27 14:20:31 cdeeb95 wpa_supplicant[859]: Successfully initialized
> wpa_supplicant
> Mar 27 14:
12 matches
Mail list logo
