g_print ("get aps len=%d\n", aps->len);
}
}
On 09.06.2017 17:20, Harald Jung wrote:
Hi,
when an new access point is added it doesn't show up in nm-applet.
When I do a request with nmcli it shows up, while nm-applet always
shows t
Hi,
when an new access point is added it doesn't show up in nm-applet.
When I do a request with nmcli it shows up, while nm-applet always shows
the same list of access points after it got started.
The same problem when a access point disappears from NetworkManager it
is still shown in nm-app
Hi,
a firmware update fixes the problem:
The update did not work with windows 10-64bit, but with windows 7-32bit.
Firmware Update:
http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=5405133&swItemId=ob_152395_1&swEnvOid=4060
regards
Harald
___
inClient ModemManager[2164]: (ttyUSB0): <--
'^NDISSTAT: 1,,,"IPV4"'
Feb 17 13:21:42 ThinClient ModemManager[2164]: [/dev/cdc-wdm0] Received
message... >>>>>> RAW: >>>>>> length = 27 >>>>>> data =
01:1A:00:80:01:01:02:
Hi,
changing the ipv6 setting with nmcli didn't help :/
NetworkManager 1.0.10
ModemManager 1.4.12
Am 12.02.2016 um 17:23 schrieb Dan Williams:
On Fri, 2016-02-12 at 13:10 +0100, Harald Jung wrote:
Hi,
i was able to establish a connection via qmicli, but still not with
NetworkMa
Hi,
i was able to establish a connection via qmicli, but still not with
NetworkManager/ModemManager, maybe this information can help to solve
the problem:
ThinClient,initial:root:/sys/devices/pci:00/:00:14.0/usb3/3-11 $
qmicli -d /dev/cdc-wdm0 --wds-start-network=web.vodafone.de
-
't read SMS
messages: QMI protocol error (17): 'MissingArgument'
Feb 10 05:23:51 ThinClient ModemManager[2087]: Couldn't read SMS
messages: QMI protocol error (48): 'InvalidArgument'
Feb 10 05:23:51 ThinClient ModemManager[2087]: Couldn't read SMS
messages: QMI pro
, Harald Jung wrote:
Hi,
finally the notebook was sent to me and i have the same problems.
I use a SIM which has been succesfully used in other notebooks.
The problem is still the same:
Are you 100% sure the APN used is correct?
Also, does the SIM have a PIN enabled? I seem to recall some reports
14:52:44 ThinClient ModemManager[2146]: Modem
/org/freedesktop/ModemManager1/Modem/0: state changed (disconnecting ->
registered)
Feb 8 14:52:44 ThinClient NetworkManager[2243]: (cdc-wdm0):
modem state changed, 'disconnecting' --> 'registered' (reason:
user-requeste
ied with the installed Windows and it worked
with any SIM.
Harald
Am 06.01.2016 um 17:14 schrieb Dan Williams:
On Wed, 2016-01-06 at 17:11 +0100, Harald Jung wrote:
Hi Dan,
yeah the sim was tested with a mobile phone and in another notebook.
The SIM also works from the windows installation on
Hi,
we were in touch with a HP notebook which is shipped with a broadband
device.
The device should be a "HP hp3110 HSPA+ Mobile Broadband Module Modem"
which isn't visible on the usb bus nor the pci bus.
Booted up with windows the device is visible and working.
Have you ever heard about a pro
Hi,
nm-applet crashes if a broadband connection is an auto connection and no
other connection is available.
In this case devinfo is never filled with data, because this is
triggered in device_added which wasn't be invoced when the function
applet_get_device_icon_for_state (in applet.c) is ca
If I'd remove mbim support from the kernel, would ModemManager use the
cdc_acm data port?
Am 22.11.2013 14:59, schrieb Harald Jung:
Update:
When modemmanager is built with mbim support the activation und
registrationm works but it wasn't able to aquire an IP by dhcp.
Now
More information abot the device can be found here:
http://www.hjit.de/hwtest_T530.txt
Am 22.11.2013 15:04, schrieb Bjørn Mork:
Harald Jung writes:
Logfile: http://www.hjit.de/mm.log
Modem 0bdb:1926 doesn't find a valid data port
T: Bus=03 Lev=01 Prnt=01
Update:
When modemmanager is built with mbim support the activation und
registrationm works but it wasn't able to aquire an IP by dhcp.
Now i lost the connection to the notebook with the device and I can't do
any debugging for the next days.
In modemmanager 0.6x i was able to establish a connect
Hi,
Problems with several modems after upgrade to ModemManager-1
global infos:
Kernel 3.11.8
Kernel config: http://www.hjit.de/config
Modem 12d1:1001 needs a very long time to initialize and isn't able to
register:
T: Bus=01 Lev=02 Pr
Hi,
several "older" option broadband modems crash after the lock facility
MM_MODEM_3GPP_FACILITY_PH_SIM is queried via AT commands.
After that the USB serial ports doesn't respond anymore.
I'm shure there is a better place to fix this problem than my rude hack.
best regards
Harald
T: Bus=01
Am 03.04.2013 18:59, schrieb Aleksander Morgado:
´
Ah, the fun... :)
So I've got a MC8790 here which does *not* like the APP1 port for PPP.
It has the following revision:
'K2_0_7_35AP C:/WS/FW/K2_0_7_35AP/MSM6290/SRC 2010/03/04 17:37:08'
´
may we "grep" for the revision major revision number
Hi,
after a coldstart your hint worked.
Is there a possibility to pass manage this by udev?
modem-manager uses an enviroment variable and is triggered itself by dbus.
So it seems to be difficult in the first place.
Harald
Am 18.02.2013 12:24, schrieb Harald Jung:
the output looks a bit
x27;
modem-manager[6820]: [mm-at-serial-port.c:334] debug_log():
(ttyUSB3): <-- '+CIEV: 7,0'
modem-manager[6820]: [mm-serial-port.c:697] data_available():
(ttyUSB4) unexpected port hangup!
Harald
Am 15.02.2013 22:07, schrieb Dan Williams:
On Fri, 2013-02-15 at 09:26 +0100, Harald
I've cleaned up to log, because i have no access to the notebook at the
moment.
ipv6 should be deactived and is not activated in the config.
There is a lot of noise in the log. Could you please disable wifi and
wired connections and then attached a compressed version of it?
Also, are you tryi
tsbak wrote:
Den 14. feb. 2013 13:44, skrev Harald Jung - ECOS Technology:
Hi,
ups sorry... i've talked with Gerald and the modem never worked with
modem-manager.
The last time it worked was with our own scripts before we switched to
network-manager.
These scripts were based on AT init scri
liche Nachricht-
An:networkmanager-list@gnome.org;
Von:Marius Kotsbak
Gesendet:Do 14.02.2013 13:31
Betreff:Re: Problems with Sierra MC 8790 after kernel upgrade to 3.7.x
Den 14. feb. 2013 12:51, skrev Harald Jung - ECOS Technology:
> Hi,
>
> after upgrading to kernel 3.7.X (3.7.7) the
. 2013 12:51, skrev Harald Jung - ECOS Technology:
> Hi,
>
> after upgrading to kernel 3.7.X (3.7.7) the Sierra MC 8790 doesn't
> connect anymore, 3.6.11 was the last kernel the Sierre module worked with.
>
Does it work with 3.6.11 kernel now? What about 3.8
Hi,
after upgrading to kernel 3.7.X (3.7.7) the Sierra MC 8790 doesn't connect
anymore, 3.6.11 was the last kernel the Sierre module worked with.
Feb 14 09:56:28 MClient020 modem-manager[2233]: (ttyUSB0) closing
serial port...
Feb 14 09:56:28 MClient020 modem-manager[2233]: (ttyUSB0)
Hi,
we have problems with a Sierra MC7710, it isn't even recognized by the kernel.
The device should be included in the current kernel 3.6.11/3.7.2 and I think it
is caused by an usb issue.
When I take a look at the usb device, I see that there are only 2 subdevices:
T: Bus=01 Lev=02
Hi,
Am 17.01.2013 23:42, schrieb Bjørn Mork:
Great! Do you happen to know why the device was using configuration #2
by default? That's unexpected. Recent versions of usb_modeswitch will
do that if it sessions a MBIM configuration, but only if you have the
cdc_mbim driver. So I don't think that
Hi,
further informations about the device:
lsusb -v output:
http://pastebin.com/9u2wR3zs
Modem Info:
Manufacturer: Sierra Wireless, Incorporated
Model: MC7710
Revision: SWI9200X_03.05.19.04ap r5475 carmd-en-10527 2012/09/17 17:57:14
IMEI: 358178040532774
IMEI SV: 13
FSN: CCQ3042170110
3GPP Rele
Hi,
Am 17.01.2013 19:02, schrieb Bjørn Mork:
echo 1 >/sys/bus/usb/devices/1-1.5/bConfigurationValue
ha! that did the job.
Jan 17 23:11:32 ThinClient klogd: usbcore: registered new interface
driver usbserial
Jan 17 23:11:32 ThinClient klogd: usbcore: registered new interface
driver usbserial
Hi,
we have problems with a Sierra MC7710, it isn't even recognized by the
kernel.
The device should be included in the current kernel 3.6.11/3.7.2 and I
think it is caused by an usb issue.
When I take a look at the usb device, I see that there are only 2
subdevices:
T: Bus=01 Lev=02 Pr
Hi,
finally the reason was the missing udev rule 80-mm-candidate.rules
Harald
Am Dienstag, den 03.07.2012, 20:35 + schrieb Harald Jung:
> okay .. i got the debugging symbols, but:
>
> (gdb) bt
> #0 0xa3455c81 in poll () from /lib/libc.so.6
> #1 0xa35361b0 in g_poll (
?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
:(
Am Dienstag, den 03.07.2012, 20:21 + schrieb Dan Williams:
> On Tue, 2012-07-03 at 21:44 +0200, Harald Jung wrote:
> > strange thing.. i've used the unstripped version and i get:
> >
> > GNU g
strange thing.. i've used the unstripped version and i get:
GNU gdb (Gentoo 7.3.1 p2) 7.3.1
...blah.
Reading symbols from /tmp/modem-manager...(no debugging symbols
found)...done.
is there a special configure or Makefile hook?
Harald
Am Dienstag, den 03.07.2012, 19:30 + schrieb Dan
in ?? ()
Harald
Am Dienstag, den 03.07.2012, 17:50 + schrieb Dan Williams:
> On Tue, 2012-07-03 at 16:17 +0200, Harald Jung wrote:
> > Hi there,
> >
> > i've compiled the current modem-manager version 0.5.2.0 under a hardened
> > gentoo.
> > The kernel ver
Hi there,
i've compiled the current modem-manager version 0.5.2.0 under a hardened
gentoo.
The kernel version is 3.4.4
The modem-manager hangs while starting up
ThinClient,initial:root:/usr/lib $ modem-manager --debug
modem-manager[4195]: [1341328334.850996] [main.c:167] main():
ModemManager (v
Hi,
on systems with ro filesystems i create symlinks to a writeable (ramdisk)
/var/ or /tmp partition.
I know this problem for more config files inside /etc/ than the resolv.conf.
I think thats the safest and "cheapest" way .-)
best regards
Harald
Am Mittwoch, 3. August 2011, 10:29:53 schrieb
Hi,
i think my message got lost, could you please check again?
no there was no device node created named like /dev/hso0, but the sysfs
interface was created.
Inside the sysfs path i don't see the "file" "dev", which should contain the
device node information. So udev has no idea how to create t
Hi,
no there was no device node created named like /dev/hso0, but the sysfs
interface was created.
Inside the sysfs path i don't see the "file" "dev", which should contain the
device node information. So udev has no idea how to create this device node.
Dan: What does ls -l /dev/hso0 show for you
e index
Jun 4 08:52:09 ThinClient NetworkManager[2203]: (ttyHS0): new GSM/UMTS
device (driver: 'hso' ifindex: -1)
Jun 4 08:52:09 ThinClient NetworkManager[2203]: (ttyHS0): exported as
/org/freedesktop/NetworkManager/Devices/2
Jun 4 08:52:09 ThinClient NetworkManager[2203]: (ttyHS0)
ktop/ModemManager/Modems/0: state
changed (disconnecting -> registered)
Jun 3 15:13:00 ThinClient NetworkManager[24019]: [1307106780.961936]
[nm-system.c:1349] flush_routes(): (ttyHS0) failed to lookup interface index
Jun 3 15:13:00 ThinClient NetworkManager[24019]: [1307106780.962055]
[nm-
d)
Jun 3 15:13:00 ThinClient NetworkManager[24019]: [1307106780.961936]
[nm-system.c:1349] flush_routes(): (ttyHS0) failed to lookup interface index
Jun 3 15:13:00 ThinClient NetworkManager[24019]: [1307106780.962055]
[nm-system.c:1349] flush_routes(): (ttyHS0) failed to lookup interface in
Hi,
i think i was wrong with that speculation, the problem is not in the modem-
manager AT command stuff. But in the way network-manager gets its ip
configuration.
Networkmanager isn't able to query the ip-settigs from the hso network
interface.
best regards
Harald
Am Dienstag, 24. Mai 2011,
Hi,
Am Freitag, 20. Mai 2011, 15:27:33 schrieb Aleksander Morgado:
> On Fri, 2011-05-20 at 14:59 +0200, Harald Jung wrote:
> > May 20 14:41:21 ThinClient modem-manager[3764]:
> > [mm-at-serial-port.c:298] debug_log(): (ttyHS0): --> 'AT
> > +CPMS="ME","
HS0): --> 'AT_OPSYS?'
May 20 14:41:30 ThinClient modem-manager[3764]: [mm-at-serial-
port.c:298] debug_log(): (ttyHS0): --> 'AT+CSCS=?'
Then the connection is dropped with the following error:
May 20 14:41:33 ThinClient NetworkManager[3572]: GSM modem enable
failed: (32) Failed to find a usable modem character set
After that the device doesn't respond to any AT Commands unless i remove it
and plug it in again.
best regards
Harald Jung
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
module, the modem-manager tries to send a dhcp request
to a network-interface ttyACM0 which doesn't exist. The usb-wwan module brings
up a wwan0 interface.
I have no further logs for the dhcp issue at the moment.
best regards
Harald Jung
___
net
Hi,
i've tried with certain git versions and the last gentoo build, to establish a
mobile connection with the modem-manager.
After a succesffull pppd connection the modem-manager crashes.
The strange thing is that the modem-manager doesn't crash when there's a link
on the ethernet port.
best
Hi,
the networkmanager i've built from the current git isn't able to get the
aviable access points via the new wpa_supplicant api (0.7.3).
The scan request is initiated via dbus, but i think it doesn't listen for dbus
events from wpa_supplicant.
dbus: fi.w1.wpa_supplicant1.Interface.Scan
(/fi
Hi,
the networkmanager i've built from the current git isn't able to get the
aviable access points via the new wpa_supplicant api (0.7.3).
The scan request is initiated via dbus, but i think it doesn't listen for dbus
events from wpa_supplicant.
dbus: fi.w1.wpa_supplicant1.Interface.Scan
(/fi
48 matches
Mail list logo
