Re: nm-applet doesn't update access_point list
I've tried to initialize a new nm_client object, which didn't help either.
Could this be a dbus issue?
The accesss point list is only correct when i restart nm-applet.
pcl = nm_client_new(NULL, NULL);
devices = nm_client_get_devices (pcl);
for (i = 0; devices && (i < devices->len); i++)
{
pdev = NM_DEVICE (g_ptr_array_index (devices, i));
if(NM_IS_DEVICE_WIFI (pdev))
{
pwdev = NM_DEVICE_WIFI (pdev);
aps = nm_device_wifi_get_access_points (pwdev);
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 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-applet and i get a connection error that this ap
isn't inside the scan list.
nm-applet runs within xfce.
best regards
Harald
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
nm-applet doesn't update access_point list
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-applet and i get a connection error that this ap isn't inside the scan list. nm-applet runs within xfce. best regards Harald ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with gobi 4000 connecting via QMI
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=ob_152395_1=4060 regards Harald ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with gobi 4000 connecting via QMI
;>>> data =
01:1F:00:80:03:01:02:09:00:20:00:13:00:02:04:00:00:00:00:00:01:02:00:9F:05:10:04:00:01:00:83:02
Feb 17 13:21:40 ThinClient ModemManager[2164]: [/dev/cdc-wdm0] Received
message (translated)... >>>>>> QMUX: >>>>>> length = 31 >>>>>>
flags = 0x80 >>>>>> service = "nas" >>>>>> client = 1 >>>>>> QMI:
>>>>>> flags = "response" >>>>>> transaction = 9 >>>>>>
tlv_length = 19 >>>>>> message = "Get Signal Strength" (0x0020)
>>>>>> TLV: >>>>>> type = "Result" (0x02) >>>>>> length = 4
>>>>>> value = 00:00:00:00 >>>>>> translated = SUCCESS >>>>>>
TLV: >>>>>> type = "Signal Strength" (0x01) >>>>>> length = 2
>>>>>> value = 9F:05 >>>>>> translated = [ strength = '-97'
radio_interface = 'umts' ] >>>>>> TLV: >>>>>> type = "Strength
List" (0x10) >>>>>> length = 4 >>>>>> value = 01:00:83:02
>>>>>> translated = { [0] = '[ strength = '-125' radio_interface =
'cdma-1xevdo' ] '}
Feb 17 13:21:40 ThinClient ModemManager[2164]: Signal strength
(umts): -97 dBm
Feb 17 13:21:40 ThinClient ModemManager[2164]: Signal strength
(cdma-1xevdo): -125 dBm
Feb 17 13:21:40 ThinClient ModemManager[2164]: Signal strength:
-97 dBm --> 26%
Feb 17 13:21:40 ThinClient ModemManager[2164]: Modem
/org/freedesktop/ModemManager1/Modem/0: signal quality updated (26)
Feb 17 13:21:41 ThinClient ModemManager[2164]: (ttyUSB2): <--
'^MODE:5,9'
Feb 17 13:21:41 ThinClient ModemManager[2164]: (ttyUSB0): <--
'^MODE:5,9'
Feb 17 13:21:41 ThinClient ModemManager[2164]: [/dev/cdc-wdm0] Received
message... >>>>>> RAW: >>>>>> length = 38 >>>>>> data =
01:25:00:80:03:01:04:00:00:24:00:19:00:2A:01:00:07:28:02:00:1B:00:11:04:00:03:03:04:05:01:06:00:01:01:01:02:01:05
Feb 17 13:21:41 ThinClient ModemManager[2164]: [/dev/cdc-wdm0] Received
message (translated)... >>>>>> QMUX: >>>>>> length = 37 >>>>>>
flags = 0x80 >>>>>> service = "nas" >>>>>> client = 1 >>>>>> QMI:
>>>>>> flags = "indication" >>>>>> transaction = 0 >>>>>>
tlv_length = 25 >>>>>> message = "Serving System" (0x0024) >>>>>>
TLV: >>>>>> type = 0x2a >>>>>> length = 1 >>>>>> value = 07
>>>>>> TLV: >>>>>> type = "UMTS Primary Scrambling Code" (0x28)
>>>>>> length = 2 >>>>>> value = 1B:00 >>>>>> translated
= 27 >>>>>> TLV: >>>>>> type = "Data Service Capability" (0x11)
>>>>>> length = 4 >>>>>> value = 03:03:04:05 >>>>>>
translated = { [0] = 'hsdpa ' [1] = 'hsupa ' [2] = 'wcdma '} >>>>>> TLV:
>>>>>> type = "Serving System" (0x01) >>>>>> length = 6
>>>>>> value = 01:01:01:02:01:05 >>>>>> translated = [
registration_state = 'registered' cs_attach_state = 'attached'
ps_attach_state = 'attached' selected_network = '3g
Feb 17 13:21:41 ThinClient ModemManager[2164]: Processing 3GPP
info...
Feb 17 13:21:42 ThinClient ModemManager[2164]: (ttyUSB2): <--
'^NDISSTAT: 1,,,"IPV4"'
Feb 17 13:21:42 ThinClient 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:02:00:20:00:0E:00:02:04:00:00:00:00:00:01:04:00:30:26:D7:43
Feb 17 13:21:42 ThinClient ModemManager[2164]: [/dev/cdc-wdm0] Received
message (translated)... >>>>>> QMUX: >>>>>> length = 26 >>>>>>
flags = 0x80 >>>>>> service = "wds" >>>>>> client = 1 >>>>>> QMI:
>>>>>> flags = "response" >>>>>> transaction = 2 >>>>>>
tlv_length = 14 >>
Re: Problems with gobi 4000 connecting via QMI
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 NetworkManager/ModemManager, maybe this information can help to solve the problem: Good info actually; perhaps it's the IPv6 requests. If you set IPv6 method to "ignore" in NetworkManager does that make things work? Or with nmcli, something like: nmcli con mod ipv6.method ignore That should cause NM to stop requesting an IPV4V6 context. But also, what version of NetworkManager do you have? Recent versions of NM have fallback logic to try only IPV4 if V4V6 fails. Dan ThinClient,initial:root:/sys/devices/pci:00/:00:14.0/usb3/3- 11 $ qmicli -d /dev/cdc-wdm0 --wds-start-network=web.vodafone.de --client-no-release-cid [/dev/cdc-wdm0] Network started Packet data handle: '1138180728' [/dev/cdc-wdm0] Client ID not released: Service: 'wds' CID: '9' ThinClient,initial:root:/sys/devices/pci:00/:00:14.0/usb3/3- 11 $ /usr/sbin/dhcpcd -B -K -L -A -G -c /usr/libexec/nm-dhcp-helper -4 wwan0 wwan0: soliciting a DHCP lease wwan0: offered 109.46.87.132 from 109.46.87.129 wwan0: leased 109.46.87.132 for 7200 seconds wwan0: adding route to 109.46.87.128/29 ThinClient,initial:root:~ $ ifconfig wwan0 wwan0 Link encap:Ethernet HWaddr 1A:84:89:C5:C6:76 inet addr:109.46.87.132 Bcast:109.46.87.135 Mask:255.255.255.248 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:954 (954.0 B) TX bytes:1223 (1.1 KiB Harald ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with gobi 4000 connecting via QMI
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 --client-no-release-cid [/dev/cdc-wdm0] Network started Packet data handle: '1138180728' [/dev/cdc-wdm0] Client ID not released: Service: 'wds' CID: '9' ThinClient,initial:root:/sys/devices/pci:00/:00:14.0/usb3/3-11 $ /usr/sbin/dhcpcd -B -K -L -A -G -c /usr/libexec/nm-dhcp-helper -4 wwan0 wwan0: soliciting a DHCP lease wwan0: offered 109.46.87.132 from 109.46.87.129 wwan0: leased 109.46.87.132 for 7200 seconds wwan0: adding route to 109.46.87.128/29 ThinClient,initial:root:~ $ ifconfig wwan0 wwan0 Link encap:Ethernet HWaddr 1A:84:89:C5:C6:76 inet addr:109.46.87.132 Bcast:109.46.87.135 Mask:255.255.255.248 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:954 (954.0 B) TX bytes:1223 (1.1 KiB Harald ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with gobi 4000 connecting via QMI
NetworkManager[2186]: (cdc-wdm0): new Broadband device (carrier: UNKNOWN, driver: 'qcserial, qmi_wwan', ifindex: 0) Feb 10 05:23:31 ThinClient NetworkManager[2186]: (cdc-wdm0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Feb 10 05:23:31 ThinClient NetworkManager[2186]: (cdc-wdm0): modem state 'locked' Feb 10 05:23:31 ThinClient NetworkManager[2186]: (cdc-wdm0): device state change: unavailable -> disconnected (reason 'none') [20 30 0] Feb 10 05:23:49 ThinClient ModemManager[2087]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (locked -> initializing) Feb 10 05:23:49 ThinClient ModemManager[2087]: (ttyUSB0): port attributes not fully set Feb 10 05:23:49 ThinClient ModemManager[2087]: couldn't load list of Own Numbers: 'Couldn't get MSISDN: QMI protocol error (16): 'NotProvisioned'' Feb 10 05:23:50 ThinClient ModemManager[2087]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (initializing -> disabled) Feb 10 05:23:50 ThinClient NetworkManager[2186]: (cdc-wdm0): modem state changed, 'locked' --> 'disabled' (reason: unknown) Feb 10 05:23:50 ThinClient NetworkManager[2186]: (cdc-wdm0): modem state changed, 'disabled' --> 'enabling' (reason: user preference) Feb 10 05:23:50 ThinClient ModemManager[2087]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling) Feb 10 05:23:50 ThinClient ModemManager[2087]: (ttyUSB0): port attributes not fully set Feb 10 05:23:50 ThinClient ModemManager[2087]: (ttyUSB2): port attributes not fully set Feb 10 05:23:50 ThinClient ModemManager[2087]: Couldn't read SMS messages: QMI protocol error (17): 'MissingArgument' Feb 10 05:23:50 ThinClient ModemManager[2087]: Couldn't read SMS messages: QMI protocol error (52): 'DeviceNotReady' Feb 10 05:23:50 ThinClient ModemManager[2087]: Couldn't read SMS messages: QMI protocol error (52): 'DeviceNotReady' Feb 10 05:23:50 ThinClient ModemManager[2087]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> idle) Feb 10 05:23:50 ThinClient ModemManager[2087]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (idle -> registering) Feb 10 05:23:50 ThinClient ModemManager[2087]: Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home) Feb 10 05:23:50 ThinClient ModemManager[2087]: Couldn't read SMS messages: QMI protocol error (48): 'InvalidArgument' Feb 10 05:23:50 ThinClient ModemManager[2087]: Couldn't read SMS messages: QMI protocol error (48): 'InvalidArgument' Feb 10 05:23:50 ThinClient ModemManager[2087]: Couldn'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 protocol error (48): 'InvalidArgument' Feb 10 05:23:51 ThinClient ModemManager[2087]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered) Feb 10 05:23:51 ThinClient NetworkManager[2186]: (cdc-wdm0): modem state changed, 'enabling' --> 'registered' (reason: user-requested) Am 09.02.2016 um 18:59 schrieb Dan Williams: On Tue, 2016-02-09 at 05:57 +0100, Harald Jung wrote: yeah, its the vodafone apn i always use in my tests. It was running for weeks inside an arm based router with the same settings, before i took it back. The SIM has a PIN and was succesfully unlocked. How long is it between when the PIN unlocks and the connection attempt occurs? Also, any chance you can connect to the AT port with minicom and run "AT+CGDCONT?" for me? Dan Harald Am 08.02.2016 um 17:32 schrieb Dan Williams: On Mon, 2016-02-08 at 14:51 +0100, 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 that connections right after unblocking the SIM PIN fail, but waiting a bit makes things work. Dan Feb 8 14:52:40 ThinClient NetworkManager[2243]: keyfile: add connection /etc/NetworkManager/system-connections/1&1 Mobile Broadband (c29aa52c-56fa-47cd-b0b4-b44b00175d29,"1&1 Mobile Broadband") Feb 8 14:52:40 ThinClient NetworkManager[2243]: (cdc -wdm0): Activation: starting connection '1&1 Mobile Broadband' (c29aa52c-56fa-47cd-b0b4-b44b00175d29) Feb 8 14:52:40 ThinClient NetworkManager[2243]: (cdc -wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Feb 8 14:52:40 ThinClient NetworkManager[2243]: NetworkManager state is now CONNECTING Feb 8 14:52:40 ThinClient ModemManager[2146]: Simple connect started... Feb 8 14:52:40 ThinClient ModemManager[2146]: Simple connect stat
Re: Problems with gobi 4000 connecting via QMI
yeah, its the vodafone apn i always use in my tests. It was running for weeks inside an arm based router with the same settings, before i took it back. The SIM has a PIN and was succesfully unlocked. Harald Am 08.02.2016 um 17:32 schrieb Dan Williams: On Mon, 2016-02-08 at 14:51 +0100, 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 that connections right after unblocking the SIM PIN fail, but waiting a bit makes things work. Dan Feb 8 14:52:40 ThinClient NetworkManager[2243]: keyfile: add connection /etc/NetworkManager/system-connections/1&1 Mobile Broadband (c29aa52c-56fa-47cd-b0b4-b44b00175d29,"1&1 Mobile Broadband") Feb 8 14:52:40 ThinClient NetworkManager[2243]: (cdc-wdm0): Activation: starting connection '1&1 Mobile Broadband' (c29aa52c-56fa-47cd-b0b4-b44b00175d29) Feb 8 14:52:40 ThinClient NetworkManager[2243]: (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Feb 8 14:52:40 ThinClient NetworkManager[2243]: NetworkManager state is now CONNECTING Feb 8 14:52:40 ThinClient ModemManager[2146]: Simple connect started... Feb 8 14:52:40 ThinClient ModemManager[2146]: Simple connect state (4/8): Wait to get fully enabled Feb 8 14:52:40 ThinClient ModemManager[2146]: Simple connect state (5/8): Register Feb 8 14:52:40 ThinClient ModemManager[2146]: Simple connect state (6/8): Bearer Feb 8 14:52:40 ThinClient ModemManager[2146]: Simple connect state (7/8): Connect Feb 8 14:52:40 ThinClient ModemManager[2146]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting) Feb 8 14:52:40 ThinClient ModemManager[2146]: [/dev/cdc-wdm0] Allocating new client ID... Feb 8 14:52:40 ThinClient NetworkManager[2243]: (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user -requested) Feb 8 14:52:40 ThinClient ModemManager[2146]: [/dev/cdc-wdm0] Registered 'wds' (version 1.23) client with ID '1' Feb 8 14:52:43 ThinClient ModemManager[2146]: error: couldn't get current settings: QMI protocol error (15): 'OutOfCall' Feb 8 14:52:43 ThinClient ModemManager[2146]: [/dev/cdc-wdm0] Allocating new client ID... Feb 8 14:52:43 ThinClient ModemManager[2146]: [/dev/cdc-wdm0] Registered 'wds' (version 1.23) client with ID '2' Feb 8 14:52:43 ThinClient ModemManager[2146]: error: couldn't start network: QMI protocol error (64): '(null)' Feb 8 14:52:43 ThinClient ModemManager[2146]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected) Feb 8 14:52:43 ThinClient ModemManager[2146]: Simple connect state (8/8): All done Feb 8 14:52:43 ThinClient NetworkManager[2243]: (cdc-wdm0): modem state changed, 'connecting' --> 'connected' (reason: user -requested) Feb 8 14:52:43 ThinClient NetworkManager[2243]: (cdc-wdm0): failed to connect modem: invalid bearer IP configuration Feb 8 14:52:43 ThinClient NetworkManager[2243]: (cdc-wdm0): device state change: prepare -> failed (reason 'config-failed') [40 120 4] Feb 8 14:52:43 ThinClient NetworkManager[2243]: NetworkManager state is now DISCONNECTED Feb 8 14:52:43 ThinClient NetworkManager[2243]: (cdc-wdm0): Activation: failed for connection '1&1 Mobile Broadband' Feb 8 14:52:43 ThinClient ModemManager[2146]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connected -> disconnecting) Feb 8 14:52:43 ThinClient NetworkManager[2243]: (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0] Feb 8 14:52:43 ThinClient NetworkManager[2243]: (cdc-wdm0): modem state changed, 'connected' --> 'disconnecting' (reason: user-requested) Feb 8 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-requested regards Harald Am 20.01.2016 um 13:46 schrieb Harald Jung: Hi, when another SIM is used, the messages are "user request" oder "none", nm-applet gives a messages Creating object path '/org/freedesktop/NetworkManager/ActiveConnection/1" failed in nm -glib. But I have no logfile from that test. Anyway the connection was tried 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 the notebook. ModemManager is version 1.4.10 Do other SIMs work in the same modem? Dan Harald Am 06.01.2016 um 16:57 schrieb Dan Williams: On We
Re: Problems with gobi 4000 connecting via QMI
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: Feb 8 14:52:40 ThinClient NetworkManager[2243]: keyfile: add connection /etc/NetworkManager/system-connections/1&1 Mobile Broadband (c29aa52c-56fa-47cd-b0b4-b44b00175d29,"1&1 Mobile Broadband") Feb 8 14:52:40 ThinClient NetworkManager[2243]: (cdc-wdm0): Activation: starting connection '1&1 Mobile Broadband' (c29aa52c-56fa-47cd-b0b4-b44b00175d29) Feb 8 14:52:40 ThinClient NetworkManager[2243]: (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Feb 8 14:52:40 ThinClient NetworkManager[2243]: NetworkManager state is now CONNECTING Feb 8 14:52:40 ThinClient ModemManager[2146]: Simple connect started... Feb 8 14:52:40 ThinClient ModemManager[2146]: Simple connect state (4/8): Wait to get fully enabled Feb 8 14:52:40 ThinClient ModemManager[2146]: Simple connect state (5/8): Register Feb 8 14:52:40 ThinClient ModemManager[2146]: Simple connect state (6/8): Bearer Feb 8 14:52:40 ThinClient ModemManager[2146]: Simple connect state (7/8): Connect Feb 8 14:52:40 ThinClient ModemManager[2146]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting) Feb 8 14:52:40 ThinClient ModemManager[2146]: [/dev/cdc-wdm0] Allocating new client ID... Feb 8 14:52:40 ThinClient NetworkManager[2243]: (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested) Feb 8 14:52:40 ThinClient ModemManager[2146]: [/dev/cdc-wdm0] Registered 'wds' (version 1.23) client with ID '1' Feb 8 14:52:43 ThinClient ModemManager[2146]: error: couldn't get current settings: QMI protocol error (15): 'OutOfCall' Feb 8 14:52:43 ThinClient ModemManager[2146]: [/dev/cdc-wdm0] Allocating new client ID... Feb 8 14:52:43 ThinClient ModemManager[2146]: [/dev/cdc-wdm0] Registered 'wds' (version 1.23) client with ID '2' Feb 8 14:52:43 ThinClient ModemManager[2146]: error: couldn't start network: QMI protocol error (64): '(null)' Feb 8 14:52:43 ThinClient ModemManager[2146]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected) Feb 8 14:52:43 ThinClient ModemManager[2146]: Simple connect state (8/8): All done Feb 8 14:52:43 ThinClient NetworkManager[2243]: (cdc-wdm0): modem state changed, 'connecting' --> 'connected' (reason: user-requested) Feb 8 14:52:43 ThinClient NetworkManager[2243]: (cdc-wdm0): failed to connect modem: invalid bearer IP configuration Feb 8 14:52:43 ThinClient NetworkManager[2243]: (cdc-wdm0): device state change: prepare -> failed (reason 'config-failed') [40 120 4] Feb 8 14:52:43 ThinClient NetworkManager[2243]: NetworkManager state is now DISCONNECTED Feb 8 14:52:43 ThinClient NetworkManager[2243]: (cdc-wdm0): Activation: failed for connection '1&1 Mobile Broadband' Feb 8 14:52:43 ThinClient ModemManager[2146]: Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connected -> disconnecting) Feb 8 14:52:43 ThinClient NetworkManager[2243]: (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0] Feb 8 14:52:43 ThinClient NetworkManager[2243]: (cdc-wdm0): modem state changed, 'connected' --> 'disconnecting' (reason: user-requested) Feb 8 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-requested regards Harald Am 20.01.2016 um 13:46 schrieb Harald Jung: Hi, when another SIM is used, the messages are "user request" oder "none", nm-applet gives a messages Creating object path '/org/freedesktop/NetworkManager/ActiveConnection/1" failed in nm-glib. But I have no logfile from that test. Anyway the connection was tried 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 the notebook. ModemManager is version 1.4.10 Do other SIMs work in the same modem? Dan Harald Am 06.01.2016 um 16:57 schrieb Dan Williams: On Wed, 2016-01-06 at 16:01 +0100, Harald Jung wrote: Hi, the "HP lt4112 Gobi 4G Module" can't establish a network connection. The device is recognozied by the system, but the IP connection fails. Details and logs can be found here: http://www.hjit.de/lt4112.txt What version of ModemManager? I see a ModemManager errors there (like "ModemManager[2018]: (mm-broadband-modem -qmi.c:1238):dms_get_ids_ready: code should not be reached") but those are recovered.
Re: Problems with gobi 4000 connecting via QMI
Hi, when another SIM is used, the messages are "user request" oder "none", nm-applet gives a messages Creating object path '/org/freedesktop/NetworkManager/ActiveConnection/1" failed in nm-glib. But I have no logfile from that test. Anyway the connection was tried 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 the notebook. ModemManager is version 1.4.10 Do other SIMs work in the same modem? Dan Harald Am 06.01.2016 um 16:57 schrieb Dan Williams: On Wed, 2016-01-06 at 16:01 +0100, Harald Jung wrote: Hi, the "HP lt4112 Gobi 4G Module" can't establish a network connection. The device is recognozied by the system, but the IP connection fails. Details and logs can be found here: http://www.hjit.de/lt4112.txt What version of ModemManager? I see a ModemManager errors there (like "ModemManager[2018]: (mm-broadband-modem -qmi.c:1238):dms_get_ids_ready: code should not be reached") but those are recovered. In any case, your SIM is not provisioned for the operator: 'Couldn't get MSISDN: QMI protocol error (16): 'NotProvisioned'' Does the SIM work in a different device? Dan ___ ModemManager-devel mailing list modemmanager-de...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel !DSPAM:416,568d3d6423792141272438! ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
HP hp3110 HSPA+ Mobile Broadband Module Modem is not shown up
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 problem like this? Harald ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
nm-applet crashes if a broadband connection is an auto connection and no other connection is available
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 called.
So the function get_icon in applet-device-broadband.c gives an assertion
device_added:
/* Store device info */
g_object_set_data_full (G_OBJECT (modem),
devinfo,
info,
(GDestroyNotify)broadband_device_info_free);
At the moment this patch works for us:
--- src/applet-device-broadband.c.orig 2013-11-27 14:15:36.0 +0100
+++ src/applet-device-broadband.c 2013-11-27 14:16:04.0 +0100
@@ -631,6 +631,10 @@
BroadbandDeviceInfo *info;
info = g_object_get_data (G_OBJECT (device), devinfo);
+ if(info == 0)
+ {
+ return ;
+ }
g_assert (info);
return mobile_helper_get_icon (device,
Harald
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Problems with several modems after upgrade to ModemManager-1
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 Prnt=02 Port=01 Cnt=01 Dev#= 3 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=1001 Rev=00.00
S: Manufacturer=HUAWEI Technology
S: Product=HUAWEI Mobile
C: #Ifs= 3 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
Logfile: http://www.hjit.de/mm.log
Modem 0bdb:1926 doesn't find a valid data port
T: Bus=03 Lev=01 Prnt=01 Port=03 Cnt=03 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 4
P: Vendor=0bdb ProdID=1926 Rev=00.00
S: Manufacturer=Lenovo
S: Product=H5321 gw
S: SerialNumber=12924B04A98B48M0
C: #Ifs=11 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 0 Cls=02(commc) Sub=08 Prot=00 Driver=(none)
I: If#= 1 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm
/bin/usb-devices: line 79: printf: 0a: invalid number
I: If#= 0 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm
I: If#= 2 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm
I: If#= 3 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm
I: If#= 4 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm
I: If#= 5 Alt= 0 #EPs= 1 Cls=02(commc) Sub=09 Prot=01 Driver=cdc_wdm
I: If#= 6 Alt= 1 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim
I: If#= 7 Alt= 2 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim
/bin/usb-devices: line 79: printf: 08: invalid octal number
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=09 Prot=01 Driver=cdc_wdm
/bin/usb-devices: line 79: printf: 09: invalid octal number
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm
Logfile: http://www.hjit.de/nodataport.log
These modems crash when the lock facility MM_MODEM_3GPP_FACILITY_PH_SIM
is requested:
So the question is: for which modems the lock request should be excluded, it
seems that it effects more than one modem.
Udev Enviroment? by vendor/device id? global (if the request is not needed)?
for all option devices with serial ports?
T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0af0 ProdID=6600 Rev=00.01
S: Manufacturer=Option N.V.
S: Product=GlobeTrotter 3G+ Module
S: SerialNumber=Serial Number
C: #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1199 ProdID=683c Rev=00.05
S: Manufacturer=Sierra Wireless, Incorporated
S: Product=Mini Card
C: #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=sierra
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=sierra
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=sierra
I: If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=sierra
I: If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=sierra
I: If#= 5 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=sierra
I: If#= 6 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=sierra
temp. patch below
--- mm-broadband-modem.c~2013-07-19 07:41:30.0 +0200
+++ mm-broadband-modem.c2013-11-06 19:22:33.0 +0100
@@ -3309,6 +3309,8 @@
return;
}
+ctx-facilities = ~MM_MODEM_3GPP_FACILITY_PH_SIM;
+
/* Ignore facility locks specified by the plugins */
if (MM_BROADBAND_MODEM
(self)-priv-modem_3gpp_ignored_facility_locks) {
gchar *str;
Harald
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with several modems after upgrade to ModemManager-1
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 connection without mbim, how can i force ModemManager to that behaviour? Modem 0bdb:1926 doesn't find a valid data port T: Bus=03 Lev=01 Prnt=01 Port=03 Cnt=03 Dev#= 4 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 4 P: Vendor=0bdb ProdID=1926 Rev=00.00 S: Manufacturer=Lenovo S: Product=H5321 gw S: SerialNumber=12924B04A98B48M0 C: #Ifs=11 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 0 Cls=02(commc) Sub=08 Prot=00 Driver=(none) I: If#= 1 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm /bin/usb-devices: line 79: printf: 0a: invalid number I: If#= 0 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I: If#= 2 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I: If#= 3 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm I: If#= 4 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I: If#= 5 Alt= 0 #EPs= 1 Cls=02(commc) Sub=09 Prot=01 Driver=cdc_wdm I: If#= 6 Alt= 1 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim I: If#= 7 Alt= 2 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim /bin/usb-devices: line 79: printf: 08: invalid octal number I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=09 Prot=01 Driver=cdc_wdm /bin/usb-devices: line 79: printf: 09: invalid octal number I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm Logfile: http://www.hjit.de/nodataport.log ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with several modems after upgrade to ModemManager-1
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 supp...@ecos.de 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 Port=03 Cnt=03 Dev#= 4 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 4 P: Vendor=0bdb ProdID=1926 Rev=00.00 S: Manufacturer=Lenovo S: Product=H5321 gw S: SerialNumber=12924B04A98B48M0 C: #Ifs=11 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 0 Cls=02(commc) Sub=08 Prot=00 Driver=(none) I: If#= 1 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm /bin/usb-devices: line 79: printf: 0a: invalid number I: If#= 0 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I: If#= 2 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I: If#= 3 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm I: If#= 4 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I: If#= 5 Alt= 0 #EPs= 1 Cls=02(commc) Sub=09 Prot=01 Driver=cdc_wdm I: If#= 6 Alt= 1 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim I: If#= 7 Alt= 2 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim It's unclear to me whether you've tested this with a MBIM capable ModemManager. You might want to load cdc_ncm with the 'prefer_mbim=N' option until you are ready to use MBIM on this modem. /bin/usb-devices: line 79: printf: 08: invalid octal number Yes, and the usb-devices script is unfortunately a bad substitute for /proc/.../usb/devices. Not only does it barf on these interface numbers, but more importantly: It hides all inactive alternate interface settings and configurations. In this case I know that there are NCM alternate settings here, but that kind of information is usually crucial. The script is so incomplete that it is close to useless IMHO. It's much better to mount debugfs on /sys/kernel/debug and use /sys/kernel/debug/usb/devices. If you cannot do that, then use lsusb -vd. Bjørn ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with several modems after upgrade to ModemManager-1
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 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 connection without mbim, how can i force ModemManager to that behaviour? Modem 0bdb:1926 doesn't find a valid data port T: Bus=03 Lev=01 Prnt=01 Port=03 Cnt=03 Dev#= 4 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 4 P: Vendor=0bdb ProdID=1926 Rev=00.00 S: Manufacturer=Lenovo S: Product=H5321 gw S: SerialNumber=12924B04A98B48M0 C: #Ifs=11 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 0 Cls=02(commc) Sub=08 Prot=00 Driver=(none) I: If#= 1 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm /bin/usb-devices: line 79: printf: 0a: invalid number I: If#= 0 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I: If#= 2 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I: If#= 3 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm I: If#= 4 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I: If#= 5 Alt= 0 #EPs= 1 Cls=02(commc) Sub=09 Prot=01 Driver=cdc_wdm I: If#= 6 Alt= 1 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim I: If#= 7 Alt= 2 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim /bin/usb-devices: line 79: printf: 08: invalid octal number I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=09 Prot=01 Driver=cdc_wdm /bin/usb-devices: line 79: printf: 09: invalid octal number I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm Logfile: http://www.hjit.de/nodataport.log ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
querying lock facility crashes broadband modem
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 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0af0 ProdID=6600 Rev=00.01
S: Manufacturer=Option N.V.
S: Product=GlobeTrotter 3G+ Module
S: SerialNumber=Serial Number
C: #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
--- mm-broadband-modem.c~2013-07-19 07:41:30.0 +0200
+++ mm-broadband-modem.c2013-11-06 19:22:33.0 +0100
@@ -3309,6 +3309,8 @@
return;
}
+ctx-facilities = ~MM_MODEM_3GPP_FACILITY_PH_SIM;
+
/* Ignore facility locks specified by the plugins */
if (MM_BROADBAND_MODEM
(self)-priv-modem_3gpp_ignored_facility_locks) {
gchar *str;
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with Sierra MC 8790 with older firmware revision
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 instead 'K1_' ? ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with Sierra MC 8790 after kernel upgrade to 3.7.x
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 different but i wasn't able to establish a connection :( modem-manager[6820]: debug [mm-manager.c:859] device_added(): (net/ppp0): could not get port's parent device modem-manager[6820]: debug [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'CRLF+CIEV: 1,3CRLF' modem-manager[6820]: debug [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'CRLF+CIEV: 7,0CRLF' modem-manager[6820]: debug [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 Jung wrote: 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. Once you have access to the notebook again, can you stop MM the normal way: mv /usr/sbin/modem-manager / killall -TERM modem-manager and then run MM like this? MM_SIERRA_APP1_PPP_OK=1 /modem-manager --debug and attempt a connection? Older Sierra devices allow PPP on the APP1 port (ttyUSB4 on your device) but unfortunately we have to whitelist that. It's actually impossible to test which tty accepts PPP on most Sierra devices, so we really have no idea. For examply, my C885 and USB306 allow it, but none of my (four) 8775s or my 8781 allows it. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with Sierra MC 8790 after kernel upgrade to 3.7.x
the output looks a bit different but i wasn't able to establish a connection :( modem-manager[6820]: debug [mm-manager.c:859] device_added(): (net/ppp0): could not get port's parent device modem-manager[6820]: debug [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'CRLF+CIEV: 1,3CRLF' modem-manager[6820]: debug [mm-at-serial-port.c:334] debug_log(): (ttyUSB3): -- 'CRLF+CIEV: 7,0CRLF' modem-manager[6820]: debug [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 Jung wrote: 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. Once you have access to the notebook again, can you stop MM the normal way: mv /usr/sbin/modem-manager / killall -TERM modem-manager and then run MM like this? MM_SIERRA_APP1_PPP_OK=1 /modem-manager --debug and attempt a connection? Older Sierra devices allow PPP on the APP1 port (ttyUSB4 on your device) but unfortunately we have to whitelist that. It's actually impossible to test which tty accepts PPP on most Sierra devices, so we really have no idea. For examply, my C885 and USB306 allow it, but none of my (four) 8775s or my 8781 allows it. Dan modem.log.gz Description: GNU Zip compressed data ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with Sierra MC 8790 after kernel upgrade to 3.7.x
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 trying to use ipv6?: /proc/sys/net/ipv6/conf/ttyUSB3/accept_ra: (4) Datei »/proc/sys/net/ipv6/conf/ttyUSB3/accept_ra« konnte nicht geöffnet werden: No such file or directory sierra_clean.log.gz Description: GNU Zip compressed data ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Problems with Sierra MC 8790 after kernel upgrade to 3.7.x
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]: info (ttyUSB0) closing serial port... Feb 14 09:56:28 MClient020 modem-manager[2233]: info (ttyUSB0) serial port closed Feb 14 09:56:28 MClient020 modem-manager[2233]: info (ttyUSB0) opening serial port... Feb 14 09:56:28 MClient020 modem-manager[2233]: info (ttyUSB1) closing serial port... Feb 14 09:56:28 MClient020 modem-manager[2233]: info (ttyUSB1) serial port closed Feb 14 09:56:28 MClient020 modem-manager[2233]: info (ttyUSB1) opening serial port... Feb 14 09:56:28 MClient020 modem-manager[2233]: info (ttyUSB1) closing serial port... Feb 14 09:56:28 MClient020 modem-manager[2233]: info (ttyUSB1) serial port closed Feb 14 09:56:30 MClient020 slapd_2.3[2577]: @(#) $OpenLDAP: slapd 2.3.40 (Jan 23 2013 14:06:30) $ ^I@gentoo4:/usr/bbsrc/bbbuild/dev-pkg/std/portage/net-nds/openldap-2.3.40/work/openldap-2.3. Feb 14 09:56:32 MClient020 crond[2604]: crond: crond (busybox 1.20.2) started, log level 8 Feb 14 09:56:32 MClient020 sudo: root : TTY=unknown ; PWD=/ ; USER=ldap ; COMMAND=/bin/slapcat_2.3 -c -f /etc/openldap/slapd.conf_2.3 Feb 14 09:56:34 MClient020 modem-manager[2233]: info (ttyUSB0) closing serial port... Feb 14 09:56:34 MClient020 modem-manager[2233]: info (ttyUSB0) serial port closed Feb 14 09:56:35 MClient020 modem-manager[2233]: warn Couldn't probe for capabilities, probably not a GSM or CDMA modem Feb 14 09:56:35 MClient020 modem-manager[2233]: info (ttyUSB2) closing serial port... Feb 14 09:56:35 MClient020 modem-manager[2233]: info (ttyUSB2) serial port closed Feb 14 09:56:35 MClient020 modem-manager[2233]: info (ttyUSB3) opening serial port... Feb 14 09:56:35 MClient020 modem-manager[2233]: warn (ttyUSB3): port attributes not fully set Feb 14 09:56:35 MClient020 NetworkManager[2220]: warn (ttyUSB3): failed to look up interface index Feb 14 09:56:35 MClient020 NetworkManager[2220]: info (ttyUSB3): new GSM/UMTS device (driver: 'sierra' ifindex: 0) Feb 14 09:56:35 MClient020 NetworkManager[2220]: info (ttyUSB3): exported as /org/freedesktop/NetworkManager/Devices/2 Feb 14 09:56:35 MClient020 NetworkManager[2220]: info (ttyUSB3): now managed Feb 14 09:56:35 MClient020 NetworkManager[2220]: info (ttyUSB3): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Feb 14 09:56:35 MClient020 NetworkManager[2220]: info (ttyUSB3): deactivating device (reason 'managed') [2] Feb 14 09:56:35 MClient020 NetworkManager[2220]: info (ttyUSB3): device state change: unavailable - disconnected (reason 'none') [20 30 0] Feb 14 09:56:36 MClient020 modem-manager[2233]: info Modem /org/freedesktop/ModemManager/Modems/0: unlock no longer required Feb 14 09:56:36 MClient020 modem-manager[2233]: info (ttyUSB3) closing serial port... Feb 14 09:56:36 MClient020 modem-manager[2233]: info (ttyUSB3) serial port closed Feb 14 09:56:48 MClient020 NetworkManager[2220]: info Activation (ttyUSB3) starting connection 'Mobilfunk' Feb 14 09:56:48 MClient020 NetworkManager[2220]: info (ttyUSB3): device state change: disconnected - prepare (reason 'none') [30 40 0] Feb 14 09:56:48 MClient020 NetworkManager[2220]: info Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) scheduled... Feb 14 09:56:48 MClient020 NetworkManager[2220]: info Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) started... Feb 14 09:56:48 MClient020 NetworkManager[2220]: info Activation (ttyUSB3) Stage 1 of 5 (Device Prepare) complete. Feb 14 09:56:48 MClient020 modem-manager[2233]: info (ttyUSB3) opening serial port... Feb 14 09:56:48 MClient020 modem-manager[2233]: warn (ttyUSB3): port attributes not fully set Feb 14 09:56:48 MClient020 modem-manager[2233]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled - enabling) Feb 14 09:56:48 MClient020 modem-manager[2233]: info (ttyUSB4) opening serial port... Feb 14 09:56:48 MClient020 modem-manager[2233]: warn (ttyUSB4): port attributes not fully set Feb 14 09:56:48 MClient020 modem-manager[2233]: info (ttyUSB3): using PDU mode for SMS Feb 14 09:56:49 MClient020 modem-manager[2233]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabling - enabled) Feb 14 09:56:49 MClient020 NetworkManager[2220]: info WWAN now enabled by management service Feb 14 09:56:49 MClient020 modem-manager[2233]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabled - registered) Feb 14 09:56:49 MClient020 modem-manager[2233]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered - connecting) Feb 14 09:56:49 MClient020 modem-manager[2233]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting - registered) Feb 14 09:56:49 MClient020 NetworkManager[2220]: warn GSM connection failed: (32) No cause information
AW: Problems with Sierra MC 8790 after kernel upgrade to 3.7.x
It worked with the 3.6.11 but not with 3.7.6 and 3.7.7 But there where no tests with 3,8 yet. -Ursprüngliche Nachricht- An:networkmanager-list@gnome.org; Von:Marius Kotsbak mar...@kotsbak.com 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 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 kernels? -- Marius ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
AW: Problems with Sierra MC 8790 after kernel upgrade to 3.7.x
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 scripts and an pppd chat script. Harald -Ursprüngliche Nachricht- An:networkmanager-list@gnome.org; Von:Marius Kotsbak mar...@kotsbak.com 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 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 kernels? -- Marius ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Problems with Sierra LTE MC7710 Device
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 Prnt=02 Port=04 Cnt=03 Dev#= 7 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 2 P: Vendor=1199 ProdID=68a2 Rev=00.06 S: Manufacturer=Sierra Wireless, Incorporated S: Product=MC7710 C: #Ifs= 2 Cfg#= 2 Atr=e0 MxPwr=0mA /bin/usb-devices: line 79: printf: 0c: invalid number I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=(none) /bin/usb-devices: line 79: printf: 0d: invalid number I: If#= 0 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=02 Driver=(none) But it should look like this (found it in the net): T: Bus=01 Lev=02 Prnt=02 Port=04 Cnt=03 Dev#= 5 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1199 ProdID=68a2 Rev=00.06 S: Manufacturer=Sierra Wireless, Incorporated S: Product=MC7710 C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) I: If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) /usr/bin/usb-devices: line 79: printf: 08: invalid octal number I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) dmesg output: usb 1-1.5: new high-speed USB device number 7 using ehci_hcd usb 1-1.5: config 1 has an invalid interface number: 8 but max is 3 usb 1-1.5: config 1 has no interface number 1 usb 1-1.5: config 2 has an invalid interface number: 12 but max is 1 usb 1-1.5: config 2 has an invalid interface number: 13 but max is 1 usb 1-1.5: config 2 has an invalid interface number: 13 but max is 1 usb 1-1.5: config 2 has no interface number 0 usb 1-1.5: config 2 has no interface number 1 As far as I understand are there 4 subdevices, as it should be normally. 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) Maybe someone has seen something like this and knows a solution. best regards Harald ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Problems with Sierra LTE MC7710 Device
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 Prnt=02 Port=04 Cnt=03 Dev#= 7 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 2 P: Vendor=1199 ProdID=68a2 Rev=00.06 S: Manufacturer=Sierra Wireless, Incorporated S: Product=MC7710 C: #Ifs= 2 Cfg#= 2 Atr=e0 MxPwr=0mA /bin/usb-devices: line 79: printf: 0c: invalid number I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=(none) /bin/usb-devices: line 79: printf: 0d: invalid number I: If#= 0 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=02 Driver=(none) But it should look like this (found it in the net): T: Bus=01 Lev=02 Prnt=02 Port=04 Cnt=03 Dev#= 5 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1199 ProdID=68a2 Rev=00.06 S: Manufacturer=Sierra Wireless, Incorporated S: Product=MC7710 C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) I: If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) /usr/bin/usb-devices: line 79: printf: 08: invalid octal number I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) dmesg output: usb 1-1.5: new high-speed USB device number 7 using ehci_hcd usb 1-1.5: config 1 has an invalid interface number: 8 but max is 3 usb 1-1.5: config 1 has no interface number 1 usb 1-1.5: config 2 has an invalid interface number: 12 but max is 1 usb 1-1.5: config 2 has an invalid interface number: 13 but max is 1 usb 1-1.5: config 2 has an invalid interface number: 13 but max is 1 usb 1-1.5: config 2 has no interface number 0 usb 1-1.5: config 2 has no interface number 1 As far as I understand are there 4 subdevices, as it should be normally. 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) Maybe someone has seen something like this and knows a solution. best regards Harald ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with Sierra LTE MC7710 Device
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_generic Jan 17 23:11:32 ThinClient klogd: USB Serial support registered for generic Jan 17 23:11:32 ThinClient klogd: usbserial: USB Serial Driver core Jan 17 23:11:32 ThinClient klogd: usbcore: registered new interface driver cdc_wdm Jan 17 23:11:32 ThinClient klogd: usbcore: registered new interface driver qcserial Jan 17 23:11:32 ThinClient klogd: USB Serial support registered for Qualcomm USB modem Jan 17 23:11:32 ThinClient klogd: qcserial 1-1.5:1.0: Qualcomm USB modem converter detected Jan 17 23:11:32 ThinClient klogd: usb 1-1.5: Qualcomm USB modem converter now attached to ttyUSB0 Jan 17 23:11:32 ThinClient klogd: qcserial 1-1.5:1.2: Qualcomm USB modem converter detected Jan 17 23:11:32 ThinClient klogd: usb 1-1.5: Qualcomm USB modem converter now attached to ttyUSB1 Jan 17 23:11:32 ThinClient klogd: qcserial 1-1.5:1.3: Qualcomm USB modem converter detected Jan 17 23:11:32 ThinClient klogd: usb 1-1.5: Qualcomm USB modem converter now attached to ttyUSB2 Jan 17 23:11:32 ThinClient klogd: qmi_wwan 1-1.5:1.8: cdc-wdm0: USB WDM device Jan 17 23:11:32 ThinClient klogd: qmi_wwan 1-1.5:1.8: wwan0: register 'qmi_wwan' at usb-:00:1a.0-1.5, WWAN/QMI device, 6e:1c:71:79:b3:45 Jan 17 23:11:32 ThinClient klogd: usbcore: registered new interface driver qmi_wwan . blah . Jan 17 23:12:49 ThinClient pppd[3878]: Plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded. Jan 17 23:12:49 ThinClient pppd[3878]: pppd 2.4.5 started by root, uid 0 Jan 17 23:12:49 ThinClient pppd[3878]: Using interface ppp0 Jan 17 23:12:49 ThinClient pppd[3878]: Connect: ppp0 -- /dev/ttyUSB2 Jan 17 23:12:49 ThinClient NetworkManager[2146]: warn /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring... Jan 17 23:12:49 ThinClient pppd[3878]: CHAP authentication succeeded Jan 17 23:12:49 ThinClient pppd[3878]: CHAP authentication succeeded Jan 17 23:12:56 ThinClient pppd[3878]: Could not determine remote IP address: defaulting to 10.64.64.64 Jan 17 23:12:56 ThinClient pppd[3878]: local IP address 88.128.183.22 Jan 17 23:12:56 ThinClient pppd[3878]: remote IP address 10.64.64.64 Jan 17 23:12:56 ThinClient pppd[3878]: primary DNS address 10.74.210.210 Jan 17 23:12:56 ThinClient pppd[3878]: secondary DNS address 10.74.210.211 Harald ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with Sierra LTE MC7710 Device
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 Release 8 +GCAP: +CGSM,+DS,+ES Harald ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with Sierra LTE MC7710 Device
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 can explain this. Bjørn
I don't have an idea but I speculate that the usb controller on the
fujitsu notebook could cause the problem.
Until we'll know what causes the unexpected behaviour i did a QD hack
to solve the problem for now.
#
/lib/udev/rules.d/77-mm-fix-unexpected.rules:
ACTION!=add|change, GOTO=mm_fix_end
SUBSYSTEM!=usb, GOTO=mm_fix_end
ENV{DEVTYPE}!=usb_device, GOTO=mm_fix_end
# Sierre LTE MC 7710
ATTRS{idVendor}==1199, ATTRS{idProduct}==68a2, RUN+=fix-unexpected
LABEL=mm_fix_end
#
#
/lib/udev/fix-unexpected:
#!/usr/bin/perl
use File::Basename;
my $product = $ENV{PRODUCT};
if($product =~ /^1199\/68a2/)
{
my $sys_dir = '/sys' . $ENV{DEVPATH};
my $bus_node = basename($sys_dir);
my $dirs = 0;
opendir DH, $sys_dir;
map {$dirs++} (grep /$bus_node/, readdir DH);
closedir DH;
if($dirs = 2)
{
open FH , $sys_dir/bConfigurationValue;
print FH 1\n;
close FH;
}
}
#
Harald
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: modem-manager hangs while starting up
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 () from /usr/lib/libglib-2.0.so.0 #2 0x0011 in ?? () #3 0x in ?? () #4 0xa356c775 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #5 0xb044ca04 in ?? () 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 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? Not specifically, but you could use CFLAGS including -g -O0 to build the debugging into and turn off optimization. That's usually enough to get at least function names in the stack traces. Dan Harald Am Dienstag, den 03.07.2012, 19:30 + schrieb Dan Williams: Any chance you could get some debug symbols there? Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
modem-manager hangs while starting up
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]: info [1341328334.850996] [main.c:167] main():
ModemManager (version 0.5.2.0) starting...
modem-manager[4195]: info [1341328334.853851] [mm-manager.c:120]
load_plugin(): Loaded plugin AnyData
modem-manager[4195]: info [1341328334.854050] [mm-manager.c:120]
load_plugin(): Loaded plugin Generic
modem-manager[4195]: info [1341328334.854316] [mm-manager.c:120]
load_plugin(): Loaded plugin Gobi
modem-manager[4195]: info [1341328334.854539] [mm-manager.c:120]
load_plugin(): Loaded plugin Option High-Speed
modem-manager[4195]: info [1341328334.854826] [mm-manager.c:120]
load_plugin(): Loaded plugin Huawei
modem-manager[4195]: info [1341328334.855023] [mm-manager.c:120]
load_plugin(): Loaded plugin Longcheer
modem-manager[4195]: info [1341328334.855242] [mm-manager.c:120]
load_plugin(): Loaded plugin Ericsson MBM
modem-manager[4195]: info [1341328334.855430] [mm-manager.c:120]
load_plugin(): Loaded plugin MotoC
modem-manager[4195]: info [1341328334.855700] [mm-manager.c:120]
load_plugin(): Loaded plugin Nokia
modem-manager[4195]: info [1341328334.855975] [mm-manager.c:120]
load_plugin(): Loaded plugin Novatel
modem-manager[4195]: info [1341328334.856185] [mm-manager.c:120]
load_plugin(): Loaded plugin Option
modem-manager[4195]: info [1341328334.856507] [mm-manager.c:120]
load_plugin(): Loaded plugin Sierra
modem-manager[4195]: info [1341328334.856715] [mm-manager.c:120]
load_plugin(): Loaded plugin SimTech
modem-manager[4195]: info [1341328334.856995] [mm-manager.c:120]
load_plugin(): Loaded plugin ZTE
if i run a strace, the last lines are:
open(/dev/.udev/data/n4, O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 21
fstat64(21, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb145c000
read(21, , 4096) = 0
close(21) = 0
munmap(0xb145c000, 4096)= 0
poll([{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=7,
events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN}, {fd=10,
events=POLLIN}, {fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=13,
events=POLLIN}, {fd=14, events=POLLIN}, {fd=15, events=POLLIN}, {fd=16,
events=POLLIN}, {fd=17, events=POLLIN}, {fd=18, events=POLLIN}, {fd=19,
events=POLLIN}, {fd=20, events=POLLIN}, {fd=6, events=POLLIN}], 17, -1)
= 1 ([{fd=4, revents=POLLIN}])
read(5, 0xbfd6ca7c, 16) = -1 EAGAIN (Resource
temporarily unavailable)
write(5, \1\0\0\0\0\0\0\0, 8) = 8
recvmsg(4, {msg_name(0)=NULL, msg_iov(1)=[{l\4\1\1\36\0\0\0\7\0\0\0\211
\0\0\0\1\1o\0\25\0\0\0/org/fre..., 2048}], msg_controllen=0,
msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 806
write(5, \1\0\0\0\0\0\0\0, 8) = 8
write(5, \1\0\0\0\0\0\0\0, 8) = 8
write(5, \1\0\0\0\0\0\0\0, 8) = 8
write(5, \1\0\0\0\0\0\0\0, 8) = 8
recvmsg(4, 0xbfd6c838, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource
temporarily unavailable)
write(5, \1\0\0\0\0\0\0\0, 8) = 8
poll([{fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=10, events=POLLIN}, {fd=11,
events=POLLIN}, {fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
events=POLLIN}, {fd=15, events=POLLIN}, {fd=16, events=POLLIN}, {fd=17,
events=POLLIN}, {fd=18, events=POLLIN}, {fd=19, events=POLLIN}, {fd=20,
events=POLLIN}, {fd=6, events=POLLIN}, {fd=4, events=POLLIN}], 17, 0) =
1 ([{fd=5, revents=POLLIN}])
read(5, \6\0\0\0\0\0\0\0, 16) = 8
poll([{fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=10, events=POLLIN}, {fd=11,
events=POLLIN}, {fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
events=POLLIN}, {fd=15, events=POLLIN}, {fd=16, events=POLLIN}, {fd=17,
events=POLLIN}, {fd=18, events=POLLIN}, {fd=19, events=POLLIN}, {fd=20,
events=POLLIN}, {fd=6, events=POLLIN}, {fd=4, events=POLLIN}], 17, 0) =
0 (Timeout)
read(5, 0xbfd6ca7c, 16) = -1 EAGAIN (Resource
temporarily unavailable)
poll([{fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=10, events=POLLIN}, {fd=11,
events=POLLIN}, {fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
events=POLLIN}, {fd=15, events=POLLIN}, {fd=16, events=POLLIN}, {fd=17,
events=POLLIN}, {fd=18, events=POLLIN}, {fd=19, events=POLLIN}, {fd=20,
events=POLLIN}, {fd=6, events=POLLIN}, {fd=4, events=POLLIN}], 17, 0) =
0 (Timeout)
read(5, 0xbfd6ca7c, 16) = -1 EAGAIN (Resource
temporarily unavailable)
poll([{fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=10, events=POLLIN}, {fd=11,
events=POLLIN}, {fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
events=POLLIN}, {fd=15, events=POLLIN}, {fd=16,
Re: modem-manager hangs while starting up
T: Bus=01 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#= 3 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=12d1 ProdID=1001 Rev= 0.00 S: Manufacturer=HUAWEI Technology S: Product=HUAWEI Mobile C:* #Ifs= 3 Cfg#= 1 Atr=e0 MxPwr=500mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=2ms E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option E: Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms Jul 3 22:23:14 ThinClient klogd: usbcore: registered new interface driver usbserial Jul 3 22:23:14 ThinClient klogd: usbcore: registered new interface driver usbserial_generic Jul 3 22:23:14 ThinClient klogd: USB Serial support registered for generic Jul 3 22:23:14 ThinClient klogd: usbserial: USB Serial Driver core Jul 3 22:23:14 ThinClient klogd: usbcore: registered new interface driver option Jul 3 22:23:14 ThinClient klogd: USB Serial support registered for GSM modem (1-port) Jul 3 22:23:14 ThinClient klogd: option 1-1.2:1.0: GSM modem (1-port) converter detected Jul 3 22:23:14 ThinClient klogd: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB0 Jul 3 22:23:14 ThinClient klogd: option 1-1.2:1.1: GSM modem (1-port) converter detected Jul 3 22:23:14 ThinClient klogd: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1 Jul 3 22:23:14 ThinClient klogd: option 1-1.2:1.2: GSM modem (1-port) converter detected Jul 3 22:23:14 ThinClient klogd: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2 (gdb) backtrace #0 0x9d447c81 in poll () from /lib/libc.so.6 #1 0x9d5281b0 in g_poll () from /usr/lib/libglib-2.0.so.0 #2 0x0011 in ?? () #3 0x in ?? () #4 0x9d55e775 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #5 0xb38358c4 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 version is 3.4.4 The modem-manager hangs while starting up Can you gdb attach to ModemManager and get a backtrace of where it's at? Also, what kind of modem is attached? There are some devices that (due to kernel bugs) block various file operations for about 5 or 10 seconds, and that needs to be fixed in the kernel (option send setup blacklist, to be specific). This might be one of those. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: modem-manager hangs while starting up
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 Williams: Any chance you could get some debug symbols there? Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: modem-manager hangs while starting up
okay .. i got the debugging symbols, but: (gdb) bt #0 0xa3455c81 in poll () from /lib/libc.so.6 #1 0xa35361b0 in g_poll () from /usr/lib/libglib-2.0.so.0 #2 0x0011 in ?? () #3 0x in ?? () #4 0xa356c775 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #5 0xb044ca04 in ?? () 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 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? Not specifically, but you could use CFLAGS including -g -O0 to build the debugging into and turn off optimization. That's usually enough to get at least function names in the stack traces. Dan Harald Am Dienstag, den 03.07.2012, 19:30 + schrieb Dan Williams: Any chance you could get some debug symbols there? Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Moving resolv.conf to /var
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 Micha?? Górny: Hello, AFAIK NetworkManager is the most common tool which keeps writing to /etc/resolv.conf file during runtime. Such a solution makes it hard to support configurations where rootfs in read-only most of the time. That's why I'm considering moving the resolv.conf file to /var. I'm not sure about the exact location there but /var seems much better for non-static resolver configs. I think that the best solution would be to patch glibc so it will first try to load 'dynamic' resolv.conf from /var, and then fallback to static configs in /etc. I'd really appreciate any kind of feedback on that idea. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: UMTS Device - T Mobile Web And Walk
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 this device node. Dan: What does ls -l /dev/hso0 show for your device? --snip-- #cd /sys/class/net/hso0/ /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/net/hso0 $ ls -l -r--r--r--1 root root 4096 Jun 7 09:46 addr_assign_type -r--r--r--1 root root 4096 Jun 7 2011 addr_len -r--r--r--1 root root 4096 Jun 7 09:46 address -r--r--r--1 root root 4096 Jun 7 09:46 broadcast -r--r--r--1 root root 4096 Jun 7 09:46 carrier -r--r--r--1 root root 4096 Jun 7 09:46 dev_id lrwxrwxrwx1 root root 0 Jun 7 09:46 device - ../../../1-1.1:1.0 -r--r--r--1 root root 4096 Jun 7 09:46 dormant -r--r--r--1 root root 4096 Jun 7 09:46 duplex -r--r--r--1 root root 4096 Jun 7 09:46 features -rw-r--r--1 root root 4096 Jun 7 2011 flags -rw-r--r--1 root root 4096 Jun 7 09:46 ifalias -r--r--r--1 root root 4096 Jun 7 2011 ifindex -r--r--r--1 root root 4096 Jun 7 09:46 iflink -r--r--r--1 root root 4096 Jun 7 09:46 link_mode -rw-r--r--1 root root 4096 Jun 7 09:46 mtu -r--r--r--1 root root 4096 Jun 7 09:46 operstate drwxr-xr-x2 root root 0 Jun 7 09:46 power drwxr-xr-x4 root root 0 Jun 7 09:46 queues -r--r--r--1 root root 4096 Jun 7 09:46 speed drwxr-xr-x2 root root 0 Jun 7 09:46 statistics lrwxrwxrwx1 root root 0 Jun 7 2011 subsystem - ../../../../../../../../../class/net -rw-r--r--1 root root 4096 Jun 7 09:46 tx_queue_len -r--r--r--1 root root 4096 Jun 7 2011 type -rw-r--r--1 root root 4096 Jun 7 2011 uevent /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/net/hso0 $ ls device/dev ls: device/dev: No such file or directory --snip-- Harald Am Montag, 6. Juni 2011, 23:48:42 schrieb Dan Williams: Just to confirm, you do *not* have a /dev/hso0? Do you have /sys/class/net/hso0 after plugging the device in? I just tried out my iCON 452 and it does provide the hso0 interface that we'd expect, and that's what ModemManager expects too. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: UMTS Device - T Mobile Web And Walk
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 your device? --snip-- #cd /sys/class/net/hso0/ /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/net/hso0 $ ls -l -r--r--r--1 root root 4096 Jun 7 09:46 addr_assign_type -r--r--r--1 root root 4096 Jun 7 2011 addr_len -r--r--r--1 root root 4096 Jun 7 09:46 address -r--r--r--1 root root 4096 Jun 7 09:46 broadcast -r--r--r--1 root root 4096 Jun 7 09:46 carrier -r--r--r--1 root root 4096 Jun 7 09:46 dev_id lrwxrwxrwx1 root root 0 Jun 7 09:46 device - ../../../1-1.1:1.0 -r--r--r--1 root root 4096 Jun 7 09:46 dormant -r--r--r--1 root root 4096 Jun 7 09:46 duplex -r--r--r--1 root root 4096 Jun 7 09:46 features -rw-r--r--1 root root 4096 Jun 7 2011 flags -rw-r--r--1 root root 4096 Jun 7 09:46 ifalias -r--r--r--1 root root 4096 Jun 7 2011 ifindex -r--r--r--1 root root 4096 Jun 7 09:46 iflink -r--r--r--1 root root 4096 Jun 7 09:46 link_mode -rw-r--r--1 root root 4096 Jun 7 09:46 mtu -r--r--r--1 root root 4096 Jun 7 09:46 operstate drwxr-xr-x2 root root 0 Jun 7 09:46 power drwxr-xr-x4 root root 0 Jun 7 09:46 queues -r--r--r--1 root root 4096 Jun 7 09:46 speed drwxr-xr-x2 root root 0 Jun 7 09:46 statistics lrwxrwxrwx1 root root 0 Jun 7 2011 subsystem - ../../../../../../../../../class/net -rw-r--r--1 root root 4096 Jun 7 09:46 tx_queue_len -r--r--r--1 root root 4096 Jun 7 2011 type -rw-r--r--1 root root 4096 Jun 7 2011 uevent /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/net/hso0 $ ls device/dev ls: device/dev: No such file or directory --snip-- Harald Am Montag, 6. Juni 2011, 23:48:42 schrieb Dan Williams: Just to confirm, you do *not* have a /dev/hso0? Do you have /sys/class/net/hso0 after plugging the device in? I just tried out my iCON 452 and it does provide the hso0 interface that we'd expect, and that's what ModemManager expects too. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: UMTS Device - T Mobile Web And Walk
ThinClient NetworkManager[2203]: info (ttyHS0): exported as /org/freedesktop/NetworkManager/Devices/2 Jun 4 08:52:09 ThinClient NetworkManager[2203]: info (ttyHS0): now managed Jun 4 08:52:09 ThinClient NetworkManager[2203]: info (ttyHS0): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Jun 4 08:52:09 ThinClient NetworkManager[2203]: info (ttyHS0): deactivating device (reason: 2). Jun 4 08:52:09 ThinClient NetworkManager[2203]: info (ttyHS0): device state change: unavailable - disconnected (reason 'none') [20 30 0] Harald Am Freitag, 3. Juni 2011, 20:56:20 schrieben Sie: On Fri, 2011-06-03 at 15:24 +0200, Harald Jung wrote: Hi, i've done some tests again with the device, without beeing able to get the problem. Can you stop NetworkManager, killall -TERM ModemManager, then run ModemManager like so? modem-manager --debug when the modem is plugged in, do you have a /dev/hs0 port? What does 'ifconfig -a' say? dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: UMTS Device - T Mobile Web And Walk
to open file '/proc/sys/net/ipv6/conf/ttyHS0/accept_ra': No such file or directory Jun 3 15:13:00 ThinClient NetworkManager[24019]: info Activation (ttyHS0) Stage 3 of 5 (IP Configure Start) complete. Jun 3 15:13:00 ThinClient NetworkManager[24019]: warn retrieving IP4 configuration failed: (32) Sending command failed: device is connected Jun 3 15:13:00 ThinClient NetworkManager[24019]: info (ttyHS0): device state change: ip-config - failed (reason 'ip-config-unavailable') [70 120 5] Jun 3 15:13:00 ThinClient NetworkManager[24019]: warn Activation (ttyHS0) failed. Jun 3 15:13:00 ThinClient modem-manager[2227]: info [mm-modem.c:761] mm_modem_set_state(): Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected - disconnecting) Jun 3 15:13:00 ThinClient modem-manager[2227]: debug [mm-port.c:181] mm_port_set_connected(): (ttyHS0): port now disconnected Jun 3 15:13:00 ThinClient NetworkManager[24019]: debug [1307106780.961814] [nm-device.c:3655] failed_to_disconnected(): (ttyHS0): running failed- disconnected transition Jun 3 15:13:00 ThinClient NetworkManager[24019]: info (ttyHS0): device state change: failed - disconnected (reason 'none') [120 30 0] Jun 3 15:13:00 ThinClient NetworkManager[24019]: info (ttyHS0): deactivating device (reason: 0). Jun 3 15:13:00 ThinClient modem-manager[2227]: info [mm-modem.c:761] mm_modem_set_state(): Modem /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting - registered) Jun 3 15:13:00 ThinClient NetworkManager[24019]: debug [1307106780.961936] [nm-system.c:1349] flush_routes(): (ttyHS0) failed to lookup interface index Jun 3 15:13:00 ThinClient NetworkManager[24019]: debug [1307106780.962055] [nm-system.c:1349] flush_routes(): (ttyHS0) failed to lookup interface index Jun 3 15:13:00 ThinClient NetworkManager[24019]: info Policy set 'Internet' (eth0) as default for IPv4 routing and DNS. Am Donnerstag, 26. Mai 2011, 20:28:29 schrieb Dan Williams: On Tue, 2011-05-24 at 18:28 +0200, Harald Jung wrote: 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. Which device is this? Option devices don't normally use PPP so ModemManager indicates that the configuration mode is static and should be requesting the details from the modem using AT_OPxxx commands. Those details get passed back to NetworkManager which should then be setting them onto the hso0 netdevice just like setting static IP details on eth0. Can you grab some logs from /var/log/messages or /var/log/daemon.log showing the problem? Dan best regards Harald Am Dienstag, 24. Mai 2011, 16:40:59 schrieb Aleksander Morgado: Hi Harald, May 20 14:41:21 ThinClient modem-manager[3764]: debug [mm-at-serial-port.c:298] debug_log(): (ttyHS0): -- 'AT +CPMS=ME,ME,MECR' I have removed the CPMS setting from the source code, I don't need any sms support and the AT command caused the modem device to hang. After submitting this command to the device, it isn't possible to communicate via the tty port anymore. Could you provide the output of AT+CPMS=? so that we know why the modem didn't like the CPMS configuration? Also the model string as reported by the modem in AT+CGMM or AT+GMM could help to try to look for the appropriate AT command reference. After that i was running into the next problem, it seems that the device is blocked by modem-managers frequent status request. So pppd doesn't come up: You mean that the rate of status queries is too high for the modem? AFAIK the rate is really several seconds between queries, so I'm not sure how this could affect here. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: UMTS Device - T Mobile Web And Walk
NetworkManager[24019]: info Activation (ttyHS0) Stage 3 of 5 (IP Configure Start) scheduled. Jun 3 15:13:00 ThinClient NetworkManager[24019]: info Activation (ttyHS0) Stage 2 of 5 (Device Configure) complete. Jun 3 15:13:00 ThinClient NetworkManager[24019]: info Activation (ttyHS0) Stage 3 of 5 (IP Configure Start) started... Jun 3 15:13:00 ThinClient NetworkManager[24019]: info (ttyHS0): device state change: config - ip-config (reason 'none') [50 70 0] Jun 3 15:13:00 ThinClient NetworkManager[24019]: debug [1307106780.960744] [NetworkManagerUtils.c:816] nm_utils_get_proc_sys_net_value(): (ttyHS0): error reading /proc/sys/net/ipv6/conf/ttyHS0/accept_ra: (4) Failed to open file '/proc/sys/net/ipv6/conf/ttyHS0/accept_ra': No such file or directory Jun 3 15:13:00 ThinClient NetworkManager[24019]: info Activation (ttyHS0) Stage 3 of 5 (IP Configure Start) complete. Jun 3 15:13:00 ThinClient NetworkManager[24019]: warn retrieving IP4 configuration failed: (32) Sending command failed: device is connected Jun 3 15:13:00 ThinClient NetworkManager[24019]: info (ttyHS0): device state change: ip-config - failed (reason 'ip-config-unavailable') [70 120 5] Jun 3 15:13:00 ThinClient NetworkManager[24019]: warn Activation (ttyHS0) failed. Jun 3 15:13:00 ThinClient modem-manager[2227]: info [mm-modem.c:761] mm_modem_set_state(): Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected - disconnecting) Jun 3 15:13:00 ThinClient modem-manager[2227]: debug [mm-port.c:181] mm_port_set_connected(): (ttyHS0): port now disconnected Jun 3 15:13:00 ThinClient NetworkManager[24019]: debug [1307106780.961814] [nm-device.c:3655] failed_to_disconnected(): (ttyHS0): running failed- disconnected transition Jun 3 15:13:00 ThinClient NetworkManager[24019]: info (ttyHS0): device state change: failed - disconnected (reason 'none') [120 30 0] Jun 3 15:13:00 ThinClient NetworkManager[24019]: info (ttyHS0): deactivating device (reason: 0). Jun 3 15:13:00 ThinClient modem-manager[2227]: info [mm-modem.c:761] mm_modem_set_state(): Modem /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting - registered) Jun 3 15:13:00 ThinClient NetworkManager[24019]: debug [1307106780.961936] [nm-system.c:1349] flush_routes(): (ttyHS0) failed to lookup interface index Jun 3 15:13:00 ThinClient NetworkManager[24019]: debug [1307106780.962055] [nm-system.c:1349] flush_routes(): (ttyHS0) failed to lookup interface index Jun 3 15:13:00 ThinClient NetworkManager[24019]: info Policy set 'Internet' (eth0) as default for IPv4 routing and DNS. Am Donnerstag, 26. Mai 2011, 20:28:29 schrieb Dan Williams: On Tue, 2011-05-24 at 18:28 +0200, Harald Jung wrote: 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. Which device is this? Option devices don't normally use PPP so ModemManager indicates that the configuration mode is static and should be requesting the details from the modem using AT_OPxxx commands. Those details get passed back to NetworkManager which should then be setting them onto the hso0 netdevice just like setting static IP details on eth0. Can you grab some logs from /var/log/messages or /var/log/daemon.log showing the problem? Dan best regards Harald Am Dienstag, 24. Mai 2011, 16:40:59 schrieb Aleksander Morgado: Hi Harald, May 20 14:41:21 ThinClient modem-manager[3764]: debug [mm-at-serial-port.c:298] debug_log(): (ttyHS0): -- 'AT +CPMS=ME,ME,MECR' I have removed the CPMS setting from the source code, I don't need any sms support and the AT command caused the modem device to hang. After submitting this command to the device, it isn't possible to communicate via the tty port anymore. Could you provide the output of AT+CPMS=? so that we know why the modem didn't like the CPMS configuration? Also the model string as reported by the modem in AT+CGMM or AT+GMM could help to try to look for the appropriate AT command reference. After that i was running into the next problem, it seems that the device is blocked by modem-managers frequent status request. So pppd doesn't come up: You mean that the rate of status queries is too high for the modem? AFAIK the rate is really several seconds between queries, so I'm not sure how this could affect here. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman
Re: UMTS Device - T Mobile Web And Walk
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, 16:40:59 schrieb Aleksander Morgado: Hi Harald, May 20 14:41:21 ThinClient modem-manager[3764]: debug [mm-at-serial-port.c:298] debug_log(): (ttyHS0): -- 'AT +CPMS=ME,ME,MECR' I have removed the CPMS setting from the source code, I don't need any sms support and the AT command caused the modem device to hang. After submitting this command to the device, it isn't possible to communicate via the tty port anymore. Could you provide the output of AT+CPMS=? so that we know why the modem didn't like the CPMS configuration? Also the model string as reported by the modem in AT+CGMM or AT+GMM could help to try to look for the appropriate AT command reference. After that i was running into the next problem, it seems that the device is blocked by modem-managers frequent status request. So pppd doesn't come up: You mean that the rate of status queries is too high for the modem? AFAIK the rate is really several seconds between queries, so I'm not sure how this could affect here. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: UMTS Device - T Mobile Web And Walk
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]: debug [mm-at-serial-port.c:298] debug_log(): (ttyHS0): -- 'AT +CPMS=ME,ME,MECR' I have removed the CPMS setting from the source code, I don't need any sms support and the AT command caused the modem device to hang. After submitting this command to the device, it isn't possible to communicate via the tty port anymore. After that i was running into the next problem, it seems that the device is blocked by modem-managers frequent status request. So pppd doesn't come up: May 23 18:34:54 ThinClient modem-manager[2228]: debug [mm-at-serial- port.c:298] debug_log(): (ttyHS0): -- 'AT$QCPDPP=2,0CR' May 23 18:34:54 ThinClient modem-manager[2228]: debug [mm-at-serial- port.c:298] debug_log(): (ttyHS0): -- 'CRLFOKCRLF' May 23 18:34:54 ThinClient modem-manager[2228]: debug [mm-at-serial- port.c:298] debug_log(): (ttyHS0): -- 'AT_OWANCALL=2,0,1CR' May 23 18:34:54 ThinClient modem-manager[2228]: debug [mm-at-serial- port.c:298] debug_log(): (ttyHS0): -- 'CRLFOKCRLF' May 23 18:34:54 ThinClient modem-manager[2228]: debug [mm-at-serial- port.c:298] debug_log(): (ttyHS0): -- 'AT_OWANCALL=2,1,1CR' May 23 18:34:54 ThinClient modem-manager[2228]: debug [mm-at-serial- port.c:298] debug_log(): (ttyHS0): -- 'CRLFOKCRLF' May 23 18:34:55 ThinClient modem-manager[2228]: debug [mm-at-serial- port.c:298] debug_log(): (ttyHS0): -- '_OWANCALL: 2, 1CRLF' May 23 18:34:55 ThinClient modem-manager[2228]: debug [mm-port.c:181] mm_port_set_connected(): (ttyHS0): port now connected May 23 18:34:55 ThinClient modem-manager[2228]: info [mm-modem.c:761] mm_modem_set_state(): Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting - connected) May 23 18:34:55 ThinClient modem-manager[2228]: debug [mm-generic- gsm.c:4739] simple_state_machine(): (ttyHS0): simple connect state 6 May 23 18:34:55 ThinClient NetworkManager[2216]: info Activation (ttyHS0) Stage 2 of 5 (Device Configure) scheduled... May 23 18:34:55 ThinClient NetworkManager[2216]: info Activation (ttyHS0) Stage 2 of 5 (Device Configure) starting... May 23 18:34:55 ThinClient NetworkManager[2216]: info (ttyHS0): device state change: prepare - config (reason 'none') [40 50 0] May 23 18:34:55 ThinClient NetworkManager[2216]: info Activation (ttyHS0) Stage 2 of 5 (Device Configure) successful. May 23 18:34:55 ThinClient NetworkManager[2216]: info Activation (ttyHS0) Stage 3 of 5 (IP Configure Start) scheduled. May 23 18:34:55 ThinClient NetworkManager[2216]: info Activation (ttyHS0) Stage 2 of 5 (Device Configure) complete. May 23 18:34:55 ThinClient NetworkManager[2216]: info Activation (ttyHS0) Stage 3 of 5 (IP Configure Start) started... May 23 18:34:55 ThinClient NetworkManager[2216]: info (ttyHS0): device state change: config - ip-config (reason 'none') [50 70 0] May 23 18:34:55 ThinClient NetworkManager[2216]: info Activation (ttyHS0) Stage 3 of 5 (IP Configure Start) complete. May 23 18:34:55 ThinClient NetworkManager[2216]: warn retrieving IP4 configuration failed: (32) Sending command failed: device is connected May 23 18:34:55 ThinClient NetworkManager[2216]: info (ttyHS0): device state change: ip-config - failed (reason 'ip-config-unavailable') [70 120 5] May 23 18:34:55 ThinClient NetworkManager[2216]: warn Activation (ttyHS0) failed. May 23 18:34:55 ThinClient NetworkManager[2216]: info (ttyHS0): device state change: failed - disconnected (reason 'none') [120 30 0] May 23 18:34:55 ThinClient NetworkManager[2216]: info (ttyHS0): deactivating device (reason: 0). I see frequent requests in the modem log, on both tty Ports: May 23 18:35:21 ThinClient modem-manager[2228]: debug [mm-at-serial- port.c:298] debug_log(): (ttyHS0): -- 'AT_OWCTI?CR' May 23 18:35:21 ThinClient modem-manager[2228]: debug [mm-at-serial- port.c:298] debug_log(): (ttyHS0): -- 'CRLF_OWCTI: 1CRLFCRLFOKCRLF' May 23 18:35:37 ThinClient modem-manager[2228]: debug [mm-at-serial- port.c:298] debug_log(): (ttyHS1): -- 'CRLF_OSIGQ: 9,0CRLF' May 23 18:35:40 ThinClient modem-manager[2228]: debug [mm-at-serial- port.c:298] debug_log(): (ttyHS1): -- 'CRLF_OSIGQ: 8,0CRLF' best regards, Harald Jung ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Problems with Sony Ericsson F3307
Hi, I've problems establishing an umts connection with a Sony Ericsson F3307. P: Vendor=0bdb ProdID=190a Rev= 0.00 S: Manufacturer=F3307 S: Product=F3307 modem-manager tries to communicate via the serial tty node of the device, which causes following error. May 17 11:13:37 ThinClient modem-manager[2331]: info (ttyACM0) opening serial port... May 17 11:13:37 ThinClient modem-manager[2331]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled - enabling) May 17 11:13:38 ThinClient modem-manager[2331]: Invalid error code: 272 May 17 11:13:38 ThinClient modem-manager[2331]: info Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabling - disabled) May 17 11:13:38 ThinClient modem-manager[2331]: info (ttyACM0) closing serial port... May 17 11:13:38 ThinClient modem-manager[2331]: info (ttyACM0) serial port closed If i load the usb-wwan 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 ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
UMTS Device - T Mobile Web And Walk
:30 ThinClient modem-manager[3764]: debug [mm-at-serial- port.c:298] debug_log(): (ttyHS0): -- 'AT+CSCS=?CR' Then the connection is dropped with the following error: May 20 14:41:33 ThinClient NetworkManager[3572]: warn 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
modem-manager crashes when umts connections is established
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 regards Harald ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Problems with new dbus wpa_supplicant api
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/w1/wpa_supplicant1/Interfaces/1) . dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/1 Has anyone an idea about that problem? best regards Harald ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
