|
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","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. 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,0<CR>' May 23 18:34:54 ThinClient modem-manager[2228]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): <-- '<CR><LF>OK<CR><LF>' May 23 18:34:54 ThinClient modem-manager[2228]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): --> 'AT_OWANCALL=2,0,1<CR>' May 23 18:34:54 ThinClient modem-manager[2228]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): <-- '<CR><LF>OK<CR><LF>' May 23 18:34:54 ThinClient modem-manager[2228]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): --> 'AT_OWANCALL=2,1,1<CR>' May 23 18:34:54 ThinClient modem-manager[2228]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): <-- '<CR><LF>OK<CR><LF>' May 23 18:34:55 ThinClient modem-manager[2228]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS0): <-- '_OWANCALL: 2, 1<CR><LF>' 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): <-- '<CR><LF>_OWCTI: 1<CR><LF><CR><LF>OK<CR><LF>' May 23 18:35:37 ThinClient modem-manager[2228]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS1): <-- '<CR><LF>_OSIGQ: 9,0<CR><LF>' May 23 18:35:40 ThinClient modem-manager[2228]: <debug> [mm-at-serial-port.c:298] debug_log(): (ttyHS1): <-- '<CR><LF>_OSIGQ: 8,0<CR><LF>' best regards, Harald Jung |