|
Hi, i've done some tests again with the device, without beeing able to get the problem. Now I've got some more verbose logs: Jun 3 15:12:58 ThinClient NetworkManager[24019]: <info> Activation (ttyHS0) Stage 1 of 5 (Device Prepare) complete. Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-generic-gsm.c:4850] simple_connect(): (ttyHS0): number => "*99#" Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-generic-gsm.c:4850] simple_connect(): (ttyHS0): network_mode => 0 Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-generic-gsm.c:4850] simple_connect(): (ttyHS0): apn => "internet.t-d1.de" Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-generic-gsm.c:4850] simple_connect(): (ttyHS0): allowed_mode => 0 Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-generic-gsm.c:4739] simple_state_machine(): (ttyHS0): simple connect state 0 Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-generic-gsm.c:4739] simple_state_machine(): (ttyHS0): simple connect state 2 Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): --> 'AT+CREG?<CR>' Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): <-- '<CR><LF>+CREG: 2,1,"19D3","7C5A"<CR><LF><CR><LF>OK<CR><LF>' Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-generic-gsm.c:4739] simple_state_machine(): (ttyHS0): simple connect state 4 Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): --> 'AT+CGDCONT?<CR>' Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): <-- '<CR><LF>+CGDCONT: 1,"IP","web.vodafone.de","0.0.0.0",0,0<CR><LF>+CGDCONT: 2,"IP","internet.t-d1.de","0.0.0.0",0,0<CR><LF><CR><LF>OK<CR><LF>' Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-generic-gsm.c:4739] simple_state_machine(): (ttyHS0): simple connect state 5 Jun 3 15:12:58 ThinClient modem-manager[2227]: <info> [mm-modem.c:761] mm_modem_set_state(): Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered -> connecting) Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): --> 'AT$QCPDPP=2,0<CR>' Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): <-- '<CR><LF>OK<CR><LF>' Jun 3 15:12:58 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): --> 'AT_OWANCALL=2,0,1<CR>' Jun 3 15:12:59 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): <-- '<CR><LF>OK<CR><LF>' Jun 3 15:12:59 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): --> 'AT_OWANCALL=2,1,1<CR>' Jun 3 15:12:59 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): <-- '<CR><LF>OK<CR><LF>' Jun 3 15:13:00 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS1): <-- '<CR><LF>_OSIGQ: 6,0<CR><LF>' Jun 3 15:12:59 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): <-- '<CR><LF>OK<CR><LF>' Jun 3 15:13:00 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS1): <-- '<CR><LF>_OSIGQ: 6,0<CR><LF>' Jun 3 15:13:00 ThinClient modem-manager[2227]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): <-- '_OWANCALL: 2, 1<CR><LF>' Jun 3 15:13:00 ThinClient modem-manager[2227]: <debug> [mm-port.c:181] mm_port_set_connected(): (ttyHS0): port now connected 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 (connecting -> connected) Jun 3 15:13:00 ThinClient modem-manager[2227]: <debug> [mm-generic-gsm.c:4739] simple_state_machine(): (ttyHS0): simple connect state 6 Jun 3 15:13:00 ThinClient NetworkManager[24019]: <info> Activation (ttyHS0) Stage 2 of 5 (Device Configure) scheduled... Jun 3 15:13:00 ThinClient NetworkManager[24019]: <info> Activation (ttyHS0) Stage 2 of 5 (Device Configure) starting... Jun 3 15:13:00 ThinClient NetworkManager[24019]: <info> (ttyHS0): device state change: prepare -> config (reason 'none') [40 50 0] Jun 3 15:13:00 ThinClient NetworkManager[24019]: <info> Activation (ttyHS0) Stage 2 of 5 (Device Configure) successful. Jun 3 15:13:00 ThinClient 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","ME"<CR>' > > > > > > > > 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 |