Re: RS232 GSM Modem - Solved!
Hi Dan, On Tue, 2010-06-22 at 17:21 -0700, Dan Williams wrote: i set these options in my sytem-connection ( under [ppp] ), but the connection doesn't work (i use the latest git snapshot (962a6b0939cd4b3ea7306492cb25f88b77668ef5). Output is: Do you happen to have the NM_PPP_DEBUG output from NetworkManager when this happens? Thanks for the help. The modem works now! My configuration for the TC63 Modem looks like this: [connection] id=TC63New uuid=57929095-bcf5-40b1-9690-3bf54b4dc6c4 type=gsm autoconnect=false timestamp=0 [ppp] noauth=true refuse-eap=false refuse-pap=false refuse-chap=false refuse-mschap=false refuse-mschapv2=false nobsdcomp=true nodeflate=true no-vj-comp=true require-mppe=false require-mppe-128=false mppe-stateful=false crtscts=false baud=0 mru=0 mtu=0 lcp-echo-failure=0 lcp-echo-interval=0 [ipv4] method=auto ignore-auto-routes=false ignore-auto-dns=false dhcp-send-hostname=false never-default=false [gsm] number=*99# username=vodafone password=vodafone apn=web.vodafone.de network-type=-1 band=-1 pin=2607 allowed-bands=1 [serial] baud=115200 bits=8 parity=110 stopbits=1 send-delay=0 Cheers, Tom Dan ** Message: (ttyUSB0) opening serial device... ** (modem-manager:13917): DEBUG: 1276525287.302163 (ttyUSB0) device open count is 1 (open) ** (modem-manager:13917): DEBUG: 1276525287.302232 Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled - enabling) ** (modem-manager:13917): DEBUG: 1276525287.403710 (ttyUSB0): -- 'ATZ E0 V1CR' ** (modem-manager:13917): DEBUG: 1276525287.414792 (ttyUSB0): -- 'A' ** (modem-manager:13917): DEBUG: 1276525287.453485 (ttyUSB0): -- 'TZ E0 V1CR' ** (modem-manager:13917): DEBUG: 1276525287.545502 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.545610 (ttyUSB0): -- 'ATE0CR' ** (modem-manager:13917): DEBUG: 1276525287.605486 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.605578 (ttyUSB0): -- 'AT +CMEE=1CR' ** (modem-manager:13917): DEBUG: 1276525287.665467 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.665554 (ttyUSB0): -- 'ATX4 C1CR' ** (modem-manager:13917): DEBUG: 1276525287.737513 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.737641 (ttyUSB0): -- 'AT +CFUN=1CR' ** (modem-manager:13917): DEBUG: 1276525287.797539 (ttyUSB0): -- 'CRLFO' ** (modem-manager:13917): DEBUG: 1276525287.797674 (ttyUSB0): -- 'K' ** (modem-manager:13917): DEBUG: 1276525287.797778 (ttyUSB0): -- 'CR' ** (modem-manager:13917): DEBUG: 1276525287.801477 (ttyUSB0): -- 'LF' ** (modem-manager:13917): DEBUG: 1276525287.801608 (ttyUSB0): -- 'AT +IFC=1,1CR' ** (modem-manager:13917): DEBUG: 1276525287.869490 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.869620 (ttyUSB0): -- 'AT +GMICR' ** (modem-manager:13917): DEBUG: 1276525287.929498 (ttyUSB0): -- 'CRLFSIEMENSCRLF' ** (modem-manager:13917): DEBUG: 1276525287.933529 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.933646 (ttyUSB0): -- 'AT +GMMCR' ** (modem-manager:13917): DEBUG: 1276525287.985476 (ttyUSB0): -- 'CRLFTC63CRLF' ** (modem-manager:13917): DEBUG: 1276525287.993993 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.994141 (ttyUSB0): -- 'AT +GMRCR' ** (modem-manager:13917): DEBUG: 1276525288.57549 (ttyUSB0): -- 'CRLFREVISION 02.500CR' ** (modem-manager:13917): DEBUG: 1276525288.61458 (ttyUSB0): -- 'LFCRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.61558 (ttyUSB0): -- 'AT +CGMICR' ** (modem-manager:13917): DEBUG: 1276525288.125511 (ttyUSB0): -- 'CRLFSIEMENS' ** (modem-manager:13917): DEBUG: 1276525288.125653 (ttyUSB0): -- 'CR' ** (modem-manager:13917): DEBUG: 1276525288.129464 (ttyUSB0): -- 'LFCRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.129564 (ttyUSB0): -- 'AT +CGMMCR' ** (modem-manager:13917): DEBUG: 1276525288.181520 (ttyUSB0): -- 'CRLFTC63CRLF' ** (modem-manager:13917): DEBUG: 1276525288.189971 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.190108 (ttyUSB0): -- 'AT +CGMRCR' ** (modem-manager:13917): DEBUG: 1276525288.253481 (ttyUSB0): -- 'CRLFREVISIO' ** (modem-manager:13917): DEBUG: 1276525288.253638 (ttyUSB0): -- 'N' ** (modem-manager:13917): DEBUG: 1276525288.253728 (ttyUSB0): -- ' ' ** (modem-manager:13917): DEBUG: 1276525288.257477 (ttyUSB0): -- '02.500CRLFCRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.257604 (ttyUSB0): -- 'AT +CSCS=?CR' ** (modem-manager:13917): DEBUG: 1276525288.313553 (ttyUSB0): -- 'CRLF+CSCS: (GSM,UCS2)' ** (modem-manager:13917): DEBUG: 1276525288.313693 (ttyUSB0): -- 'CR' ** (modem-manager:13917): DEBUG: 1276525288.313801 (ttyUSB0): -- 'LF' ** (modem-manager:13917): DEBUG: 1276525288.322067 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.322253 (ttyUSB0): -- 'AT
Re: RS232 GSM Modem
On Mon, 2010-06-14 at 16:23 +0200, Tom wrote: Hi Dan, sorry for the delay (had holidays). On Fri, 2010-06-04 at 19:29 -0700, Dan Williams wrote: Looks like the remote side doesn't like use of Compression Control Protocol. Try: nobsdcomp=true nodeflate=true no-vj-comp=true And see if that works? i set these options in my sytem-connection ( under [ppp] ), but the connection doesn't work (i use the latest git snapshot (962a6b0939cd4b3ea7306492cb25f88b77668ef5). Output is: Do you happen to have the NM_PPP_DEBUG output from NetworkManager when this happens? Dan ** Message: (ttyUSB0) opening serial device... ** (modem-manager:13917): DEBUG: 1276525287.302163 (ttyUSB0) device open count is 1 (open) ** (modem-manager:13917): DEBUG: 1276525287.302232 Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled - enabling) ** (modem-manager:13917): DEBUG: 1276525287.403710 (ttyUSB0): -- 'ATZ E0 V1CR' ** (modem-manager:13917): DEBUG: 1276525287.414792 (ttyUSB0): -- 'A' ** (modem-manager:13917): DEBUG: 1276525287.453485 (ttyUSB0): -- 'TZ E0 V1CR' ** (modem-manager:13917): DEBUG: 1276525287.545502 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.545610 (ttyUSB0): -- 'ATE0CR' ** (modem-manager:13917): DEBUG: 1276525287.605486 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.605578 (ttyUSB0): -- 'AT +CMEE=1CR' ** (modem-manager:13917): DEBUG: 1276525287.665467 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.665554 (ttyUSB0): -- 'ATX4 C1CR' ** (modem-manager:13917): DEBUG: 1276525287.737513 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.737641 (ttyUSB0): -- 'AT +CFUN=1CR' ** (modem-manager:13917): DEBUG: 1276525287.797539 (ttyUSB0): -- 'CRLFO' ** (modem-manager:13917): DEBUG: 1276525287.797674 (ttyUSB0): -- 'K' ** (modem-manager:13917): DEBUG: 1276525287.797778 (ttyUSB0): -- 'CR' ** (modem-manager:13917): DEBUG: 1276525287.801477 (ttyUSB0): -- 'LF' ** (modem-manager:13917): DEBUG: 1276525287.801608 (ttyUSB0): -- 'AT +IFC=1,1CR' ** (modem-manager:13917): DEBUG: 1276525287.869490 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.869620 (ttyUSB0): -- 'AT +GMICR' ** (modem-manager:13917): DEBUG: 1276525287.929498 (ttyUSB0): -- 'CRLFSIEMENSCRLF' ** (modem-manager:13917): DEBUG: 1276525287.933529 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.933646 (ttyUSB0): -- 'AT +GMMCR' ** (modem-manager:13917): DEBUG: 1276525287.985476 (ttyUSB0): -- 'CRLFTC63CRLF' ** (modem-manager:13917): DEBUG: 1276525287.993993 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.994141 (ttyUSB0): -- 'AT +GMRCR' ** (modem-manager:13917): DEBUG: 1276525288.57549 (ttyUSB0): -- 'CRLFREVISION 02.500CR' ** (modem-manager:13917): DEBUG: 1276525288.61458 (ttyUSB0): -- 'LFCRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.61558 (ttyUSB0): -- 'AT +CGMICR' ** (modem-manager:13917): DEBUG: 1276525288.125511 (ttyUSB0): -- 'CRLFSIEMENS' ** (modem-manager:13917): DEBUG: 1276525288.125653 (ttyUSB0): -- 'CR' ** (modem-manager:13917): DEBUG: 1276525288.129464 (ttyUSB0): -- 'LFCRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.129564 (ttyUSB0): -- 'AT +CGMMCR' ** (modem-manager:13917): DEBUG: 1276525288.181520 (ttyUSB0): -- 'CRLFTC63CRLF' ** (modem-manager:13917): DEBUG: 1276525288.189971 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.190108 (ttyUSB0): -- 'AT +CGMRCR' ** (modem-manager:13917): DEBUG: 1276525288.253481 (ttyUSB0): -- 'CRLFREVISIO' ** (modem-manager:13917): DEBUG: 1276525288.253638 (ttyUSB0): -- 'N' ** (modem-manager:13917): DEBUG: 1276525288.253728 (ttyUSB0): -- ' ' ** (modem-manager:13917): DEBUG: 1276525288.257477 (ttyUSB0): -- '02.500CRLFCRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.257604 (ttyUSB0): -- 'AT +CSCS=?CR' ** (modem-manager:13917): DEBUG: 1276525288.313553 (ttyUSB0): -- 'CRLF+CSCS: (GSM,UCS2)' ** (modem-manager:13917): DEBUG: 1276525288.313693 (ttyUSB0): -- 'CR' ** (modem-manager:13917): DEBUG: 1276525288.313801 (ttyUSB0): -- 'LF' ** (modem-manager:13917): DEBUG: 1276525288.322067 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.322253 (ttyUSB0): -- 'AT +CSCS=UCS2CR' ** (modem-manager:13917): DEBUG: 1276525288.381501 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.381612 (ttyUSB0): -- 'AT +CSCS?CR' ** (modem-manager:13917): DEBUG: 1276525288.433501 (ttyUSB0): -- 'CRLF+CSC' ** (modem-manager:13917): DEBUG: 1276525288.433614 (ttyUSB0): -- 'S' ** (modem-manager:13917): DEBUG: 1276525288.433669 (ttyUSB0): -- ':' ** (modem-manager:13917): DEBUG: 1276525288.437558 (ttyUSB0): -- ' UCS2CRLF' ** (modem-manager:13917): DEBUG: 1276525288.441570 (ttyUSB0): -- 'CRLF' ** (modem-manager:13917): DEBUG: 1276525288.445968 (ttyUSB0): -- 'OKCRLF' ** (modem-manager:13917):
Re: RS232 GSM Modem
Hi Dan, sorry for the delay (had holidays). On Fri, 2010-06-04 at 19:29 -0700, Dan Williams wrote: Looks like the remote side doesn't like use of Compression Control Protocol. Try: nobsdcomp=true nodeflate=true no-vj-comp=true And see if that works? i set these options in my sytem-connection ( under [ppp] ), but the connection doesn't work (i use the latest git snapshot (962a6b0939cd4b3ea7306492cb25f88b77668ef5). Output is: ** Message: (ttyUSB0) opening serial device... ** (modem-manager:13917): DEBUG: 1276525287.302163 (ttyUSB0) device open count is 1 (open) ** (modem-manager:13917): DEBUG: 1276525287.302232 Modem /org/freedesktop/ModemManager/Modems/1: state changed (disabled - enabling) ** (modem-manager:13917): DEBUG: 1276525287.403710 (ttyUSB0): -- 'ATZ E0 V1CR' ** (modem-manager:13917): DEBUG: 1276525287.414792 (ttyUSB0): -- 'A' ** (modem-manager:13917): DEBUG: 1276525287.453485 (ttyUSB0): -- 'TZ E0 V1CR' ** (modem-manager:13917): DEBUG: 1276525287.545502 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.545610 (ttyUSB0): -- 'ATE0CR' ** (modem-manager:13917): DEBUG: 1276525287.605486 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.605578 (ttyUSB0): -- 'AT +CMEE=1CR' ** (modem-manager:13917): DEBUG: 1276525287.665467 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.665554 (ttyUSB0): -- 'ATX4 C1CR' ** (modem-manager:13917): DEBUG: 1276525287.737513 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.737641 (ttyUSB0): -- 'AT +CFUN=1CR' ** (modem-manager:13917): DEBUG: 1276525287.797539 (ttyUSB0): -- 'CRLFO' ** (modem-manager:13917): DEBUG: 1276525287.797674 (ttyUSB0): -- 'K' ** (modem-manager:13917): DEBUG: 1276525287.797778 (ttyUSB0): -- 'CR' ** (modem-manager:13917): DEBUG: 1276525287.801477 (ttyUSB0): -- 'LF' ** (modem-manager:13917): DEBUG: 1276525287.801608 (ttyUSB0): -- 'AT +IFC=1,1CR' ** (modem-manager:13917): DEBUG: 1276525287.869490 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.869620 (ttyUSB0): -- 'AT +GMICR' ** (modem-manager:13917): DEBUG: 1276525287.929498 (ttyUSB0): -- 'CRLFSIEMENSCRLF' ** (modem-manager:13917): DEBUG: 1276525287.933529 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.933646 (ttyUSB0): -- 'AT +GMMCR' ** (modem-manager:13917): DEBUG: 1276525287.985476 (ttyUSB0): -- 'CRLFTC63CRLF' ** (modem-manager:13917): DEBUG: 1276525287.993993 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525287.994141 (ttyUSB0): -- 'AT +GMRCR' ** (modem-manager:13917): DEBUG: 1276525288.57549 (ttyUSB0): -- 'CRLFREVISION 02.500CR' ** (modem-manager:13917): DEBUG: 1276525288.61458 (ttyUSB0): -- 'LFCRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.61558 (ttyUSB0): -- 'AT +CGMICR' ** (modem-manager:13917): DEBUG: 1276525288.125511 (ttyUSB0): -- 'CRLFSIEMENS' ** (modem-manager:13917): DEBUG: 1276525288.125653 (ttyUSB0): -- 'CR' ** (modem-manager:13917): DEBUG: 1276525288.129464 (ttyUSB0): -- 'LFCRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.129564 (ttyUSB0): -- 'AT +CGMMCR' ** (modem-manager:13917): DEBUG: 1276525288.181520 (ttyUSB0): -- 'CRLFTC63CRLF' ** (modem-manager:13917): DEBUG: 1276525288.189971 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.190108 (ttyUSB0): -- 'AT +CGMRCR' ** (modem-manager:13917): DEBUG: 1276525288.253481 (ttyUSB0): -- 'CRLFREVISIO' ** (modem-manager:13917): DEBUG: 1276525288.253638 (ttyUSB0): -- 'N' ** (modem-manager:13917): DEBUG: 1276525288.253728 (ttyUSB0): -- ' ' ** (modem-manager:13917): DEBUG: 1276525288.257477 (ttyUSB0): -- '02.500CRLFCRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.257604 (ttyUSB0): -- 'AT +CSCS=?CR' ** (modem-manager:13917): DEBUG: 1276525288.313553 (ttyUSB0): -- 'CRLF+CSCS: (GSM,UCS2)' ** (modem-manager:13917): DEBUG: 1276525288.313693 (ttyUSB0): -- 'CR' ** (modem-manager:13917): DEBUG: 1276525288.313801 (ttyUSB0): -- 'LF' ** (modem-manager:13917): DEBUG: 1276525288.322067 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.322253 (ttyUSB0): -- 'AT +CSCS=UCS2CR' ** (modem-manager:13917): DEBUG: 1276525288.381501 (ttyUSB0): -- 'CRLFOKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.381612 (ttyUSB0): -- 'AT +CSCS?CR' ** (modem-manager:13917): DEBUG: 1276525288.433501 (ttyUSB0): -- 'CRLF+CSC' ** (modem-manager:13917): DEBUG: 1276525288.433614 (ttyUSB0): -- 'S' ** (modem-manager:13917): DEBUG: 1276525288.433669 (ttyUSB0): -- ':' ** (modem-manager:13917): DEBUG: 1276525288.437558 (ttyUSB0): -- ' UCS2CRLF' ** (modem-manager:13917): DEBUG: 1276525288.441570 (ttyUSB0): -- 'CRLF' ** (modem-manager:13917): DEBUG: 1276525288.445968 (ttyUSB0): -- 'OKCRLF' ** (modem-manager:13917): DEBUG: 1276525288.446162 Modem /org/freedesktop/ModemManager/Modems/1: state changed (enabling - enabled) ** (modem-manager:13917): DEBUG: 1276525288.446433 (ttyUSB0): -- 'AT +CREG=2CR' ** (modem-manager:13917): DEBUG: 1276525288.505995 (ttyUSB0): --
Re: RS232 GSM Modem - wvdial works
When i use wvdial, the modem works. /etc/wvdial.conf looks like: [Dialer Defaults] Init1 = AT+CGDCONT=1,IP,web.vodafone.de Modem Type = USB Modem Phone = *99***1# Username = vodafone Password = vodafone ISDN = 0 New PPPD = yes Modem = /dev/ttyUSB0 Baud = 57600 Stupid Mode = 1 Auto DNS = 1 Cheers, Tom On Wed, 2010-04-28 at 09:37 +0200, toabctl wrote: Hi, i want to use network-manager 0.8 in debian embedded system. I want to connect the system with network/modem manager to the gsm network and have a Siemens TC63i modem for that available. I can manually use the modem with the AT-Commands, but i don't know how to setup the connection with network/modem manager. Question: 1) How does network-manager detect that the modem is connected? Or how can i tell networkmanager on which port the modem is attached? I use a rs232-usb adapter so the port is /dev/ttyUSB0 . 2) How does the connection-config looks like? Cheers, Tom ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RS232 GSM Modem
On Wed, 2010-06-02 at 12:09 +0200, Tom wrote: On Wed, 2010-06-02 at 00:54 -0700, Dan Williams wrote: Hmm, what are you using to connect with PPP? If you're using NetworkManager, you can: NM_PPP_DEBUG=1 NetworkManager --no-daemon and get verbose PPP output which could help to debug the issue. Note that PPP uses it's *own* baudrate, which you have to send to pppd on the command line. So if we dont' set that correctly, PPP may not work. But debug output from pppd including it's command-line options might help us figure that out. i set the baudrate for ppp (in my system-settings connection). The output of NetworkManager (0.8 from debian testing repository) follows. In this case i used the modem with a usb-adapter on my Lenovo R400 laptop. But this should work, too. Looks like the remote side doesn't like use of Compression Control Protocol. Try: nobsdcomp=true nodeflate=true no-vj-comp=true And see if that works? Dan NetworkManager: info Activation (ttyUSB1) starting connection 'TC63' NetworkManager: info (ttyUSB1): device state change: 3 - 4 (reason 0) NetworkManager: info Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started... NetworkManager: info Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete. NetworkManager: info Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: info Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting... NetworkManager: info (ttyUSB1): device state change: 4 - 5 (reason 0) NetworkManager: info Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful. NetworkManager: info Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager: info Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete. NetworkManager: info Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started... NetworkManager: info (ttyUSB1): device state change: 5 - 7 (reason 0) NetworkManager: info Starting pppd connection NetworkManager: debug [1275473061.909184] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock nodefaultroute debug user vodafone ttyUSB1 noipdefault 57600 noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so NetworkManager: debug [1275473061.971552] nm_ppp_manager_start(): ppp started with pid 7242 NetworkManager: info Activation (ttyUSB1) Stage 4 of 5 (IP6 Configure Get) scheduled... NetworkManager: info Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete. NetworkManager: info Activation (ttyUSB1) Stage 4 of 5 (IP6 Configure Get) started... NetworkManager: info Activation (ttyUSB1) Stage 4 of 5 (IP6 Configure Get) complete. Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded. ** Message: nm-ppp-plugin: (plugin_init): initializing ** Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' using channel 1 Using interface ppp0 Connect: ppp0 -- /dev/ttyUSB1 ** Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' sent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x74efb434 pcomp accomp] NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) NetworkManager:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. rcvd [LCP ConfNak id=0x1 asyncmap 0xa] sent [LCP ConfReq id=0x2 asyncmap 0xa magic 0x74efb434 pcomp accomp] rcvd [LCP ConfAck id=0x2 asyncmap 0xa magic 0x74efb434 pcomp accomp] rcvd [LCP ConfReq id=0x3 mru 1600 auth pap magic 0xb9051aaa asyncmap 0xa pcomp accomp] sent [LCP ConfAck id=0x3 mru 1600 auth pap magic 0xb9051aaa asyncmap 0xa pcomp accomp] ** Message: nm-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate' ** Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials... ** Message: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager sent [PAP AuthReq id=0x1 user=vodafone password=hidden] rcvd [PAP AuthAck id=0x1 TTP Com PPP - Password Verified OK] Remote message: TTP Com PPP - Password Verified OK PAP authentication succeeded ** Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase 'network' sent [CCP ConfReq id=0x1 deflate 15 deflate(old#) 15 bsd v1 15] sent [IPCP ConfReq id=0x1 compress VJ 0f 01 addr 0.0.0.0 ms-dns1 0.0.0.0 ms-dns3 0.0.0.0] rcvd [LCP ProtRej id=0x0 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f 32] Protocol-Reject for 'Compression Control Protocol' (0x80fd) received rcvd [LCP TermReq id=0x0 Normal Termination by NCP] LCP terminated by peer (Normal Termination by NCP) ** Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' sent [LCP TermAck id=0x0] ** Message: nm-ppp-plugin:
Re: RS232 GSM Modem
On Thu, 2010-05-27 at 18:34 +0200, Tom wrote: Hi Dan, i think the important line from debug output is: ** (modem-manager:17984): DEBUG: (net/ppp0): could not get port's parent device i tried to understand/change the source in src/mm-manager.c but without any results. That line is actually harmless. Dan any ideas? cheers, tom On Wed, 2010-05-26 at 17:59 +0200, Tom wrote: Hi Dan, On Wed, 2010-05-26 at 02:08 -0700, Dan Williams wrote: If you manually set the modem to 57600 and then run modem-manager, does that work? as mentioned in the last mail, the modem is detected. But i can not connect to the internet over ppp. Output is: ** Message: (ttyUSB1) opening serial device... ** (modem-manager:17984): DEBUG: 1274889434.174622 (ttyUSB1) device open count is 1 (open) ** (modem-manager:17984): DEBUG: (ttyUSB1): probe requested by plugin 'Generic' ** (modem-manager:17984): DEBUG: 1274889434.275168 (ttyUSB1): -- 'AT +GCAPCR' ** (modem-manager:17984): DEBUG: 1274889435.76137 (ttyUSB1): -- 'CRLF+GCAP: +CGSM,+FCLASSCRLFCRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889435.76290 (ttyUSB1) device open count is 0 (close) ** Message: (ttyUSB1) closing serial device... ** Message: (ttyUSB1) type primary claimed by /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 ** Message: (ttyUSB1) opening serial device... ** (modem-manager:17984): DEBUG: 1274889435.78881 (ttyUSB1) device open count is 1 (open) ** Message: (Generic): GSM modem /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 claimed port ttyUSB1 ** (modem-manager:17984): DEBUG: Added modem /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 ** (modem-manager:17984): DEBUG: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 ** (modem-manager:17984): DEBUG: 1274889435.79125 (ttyUSB1): -- 'AT +CPIN?CR' ** (modem-manager:17984): DEBUG: 1274889435.148615 (ttyUSB1): -- 'CRLF+CPIN: READYCRLF' ** (modem-manager:17984): DEBUG: 1274889435.152584 (ttyUSB1): -- 'CRLFOK' ** (modem-manager:17984): DEBUG: 1274889435.157066 (ttyUSB1): -- 'CRLF' ** (modem-manager:17984): DEBUG: 1274889435.157150 (ttyUSB1) device open count is 0 (close) ** Message: (ttyUSB1) closing serial device... ** (modem-manager:17984): DEBUG: Exported modem /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 as /org/freedesktop/ModemManager/Modems/4 ** (modem-manager:17984): DEBUG: (/org/freedesktop/ModemManager/Modems/4): data port is ttyUSB1 ** Message: (ttyUSB1) opening serial device... ** (modem-manager:17984): DEBUG: 1274889474.123884 (ttyUSB1) device open count is 1 (open) ** (modem-manager:17984): DEBUG: 1274889474.123947 Modem /org/freedesktop/ModemManager/Modems/4: state changed (disabled - enabling) ** (modem-manager:17984): DEBUG: 1274889474.224318 (ttyUSB1): -- 'ATZ E0 V1CR' ** (modem-manager:17984): DEBUG: 1274889474.368589 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.368738 (ttyUSB1): -- 'ATE0CR' ** (modem-manager:17984): DEBUG: 1274889474.428616 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.428741 (ttyUSB1): -- 'AT +CMEE=1CR' ** (modem-manager:17984): DEBUG: 1274889474.504607 (ttyUSB1): -- 'CRLFERRORCRLF' ** (modem-manager:17984): DEBUG: Got failure code 100: Unknown error ** (modem-manager:17984): DEBUG: 1274889474.504762 (ttyUSB1): -- 'ATX4 C1CR' ** (modem-manager:17984): DEBUG: 1274889474.580632 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.580757 (ttyUSB1): -- 'AT +CFUN=1CR' ** (modem-manager:17984): DEBUG: 1274889474.640615 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.640775 (ttyUSB1): -- 'AT +IFC=1,1CR' ** (modem-manager:17984): DEBUG: 1274889474.708594 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.708714 (ttyUSB1): -- 'AT +GMICR' ** (modem-manager:17984): DEBUG: 1274889474.772586 (ttyUSB1): -- 'CRLFSIEMENSCR' ** (modem-manager:17984): DEBUG: 1274889474.776565 (ttyUSB1): -- 'LFCRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.776670 (ttyUSB1): -- 'AT +GMMCR' ** (modem-manager:17984): DEBUG: 1274889474.832606 (ttyUSB1): -- 'CRLFTC63CRLF' ** (modem-manager:17984): DEBUG: 1274889474.840584 (ttyUSB1): -- 'CR' ** (modem-manager:17984): DEBUG: 1274889474.844586 (ttyUSB1): -- 'LFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.844683 (ttyUSB1): -- 'AT +GMRCR' ** (modem-manager:17984): DEBUG: 1274889474.904630 (ttyUSB1): -- 'CRLF' ** (modem-manager:17984): DEBUG: 1274889474.908557 (ttyUSB1): -- 'REVISION 02.500CRLF' ** (modem-manager:17984): DEBUG: 1274889474.912571 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.912669 (ttyUSB1): -- 'AT +CGMICR' ** (modem-manager:17984): DEBUG: 1274889474.976609 (ttyUSB1): -- 'CRLFSIEMENSCRLF' **
Re: RS232 GSM Modem
On Wed, 2010-06-02 at 00:53 -0700, Dan Williams wrote: What do you mean with Hardware IDs? It's possible to use the following commands: AT+CGMI - Request manufacturer identification AT+CGMM - Request model identification AT+CGMR - Request revision identification of software status Section Right, but sending those commands requires that we already know what baudrate we need, which I'd like to get from hardware IDs before talking to the device in the first place. It's possible to change the baudrate of the device, so IDs don't solve the problem. I think it would be best to probe the baudrate. I mean stuff like USB VID/PID, PCI VID/PID, SDIO IDs, etc. Even parallel-port devices like printers have IDs. But for serial ports, they might not. i don't know that. sorry. Cheers, Tom ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RS232 GSM Modem
On Wed, 2010-06-02 at 00:54 -0700, Dan Williams wrote: Hmm, what are you using to connect with PPP? If you're using NetworkManager, you can: NM_PPP_DEBUG=1 NetworkManager --no-daemon and get verbose PPP output which could help to debug the issue. Note that PPP uses it's *own* baudrate, which you have to send to pppd on the command line. So if we dont' set that correctly, PPP may not work. But debug output from pppd including it's command-line options might help us figure that out. i set the baudrate for ppp (in my system-settings connection). The output of NetworkManager (0.8 from debian testing repository) follows. In this case i used the modem with a usb-adapter on my Lenovo R400 laptop. But this should work, too. NetworkManager: info Activation (ttyUSB1) starting connection 'TC63' NetworkManager: info (ttyUSB1): device state change: 3 - 4 (reason 0) NetworkManager: info Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started... NetworkManager: info Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete. NetworkManager: info Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: info Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting... NetworkManager: info (ttyUSB1): device state change: 4 - 5 (reason 0) NetworkManager: info Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful. NetworkManager: info Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager: info Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete. NetworkManager: info Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started... NetworkManager: info (ttyUSB1): device state change: 5 - 7 (reason 0) NetworkManager: info Starting pppd connection NetworkManager: debug [1275473061.909184] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock nodefaultroute debug user vodafone ttyUSB1 noipdefault 57600 noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so NetworkManager: debug [1275473061.971552] nm_ppp_manager_start(): ppp started with pid 7242 NetworkManager: info Activation (ttyUSB1) Stage 4 of 5 (IP6 Configure Get) scheduled... NetworkManager: info Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete. NetworkManager: info Activation (ttyUSB1) Stage 4 of 5 (IP6 Configure Get) started... NetworkManager: info Activation (ttyUSB1) Stage 4 of 5 (IP6 Configure Get) complete. Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded. ** Message: nm-ppp-plugin: (plugin_init): initializing ** Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' using channel 1 Using interface ppp0 Connect: ppp0 -- /dev/ttyUSB1 ** Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' sent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x74efb434 pcomp accomp] NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) NetworkManager:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. rcvd [LCP ConfNak id=0x1 asyncmap 0xa] sent [LCP ConfReq id=0x2 asyncmap 0xa magic 0x74efb434 pcomp accomp] rcvd [LCP ConfAck id=0x2 asyncmap 0xa magic 0x74efb434 pcomp accomp] rcvd [LCP ConfReq id=0x3 mru 1600 auth pap magic 0xb9051aaa asyncmap 0xa pcomp accomp] sent [LCP ConfAck id=0x3 mru 1600 auth pap magic 0xb9051aaa asyncmap 0xa pcomp accomp] ** Message: nm-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate' ** Message: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials... ** Message: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager sent [PAP AuthReq id=0x1 user=vodafone password=hidden] rcvd [PAP AuthAck id=0x1 TTP Com PPP - Password Verified OK] Remote message: TTP Com PPP - Password Verified OK PAP authentication succeeded ** Message: nm-ppp-plugin: (nm_phasechange): status 8 / phase 'network' sent [CCP ConfReq id=0x1 deflate 15 deflate(old#) 15 bsd v1 15] sent [IPCP ConfReq id=0x1 compress VJ 0f 01 addr 0.0.0.0 ms-dns1 0.0.0.0 ms-dns3 0.0.0.0] rcvd [LCP ProtRej id=0x0 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f 32] Protocol-Reject for 'Compression Control Protocol' (0x80fd) received rcvd [LCP TermReq id=0x0 Normal Termination by NCP] LCP terminated by peer (Normal Termination by NCP) ** Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' sent [LCP TermAck id=0x0] ** Message: nm-ppp-plugin: (nm_phasechange): status 11 / phase 'disconnect' Connection terminated. NetworkManager: info (ttyUSB1): device state change: 7 - 9 (reason 13) NetworkManager: info Marking connection 'TC63' invalid. NetworkManager: info Activation (ttyUSB1) failed. NetworkManager: info (ttyUSB1): device state change: 9 - 3 (reason 0)
Re: RS232 GSM Modem
Hi Dan, i think the important line from debug output is: ** (modem-manager:17984): DEBUG: (net/ppp0): could not get port's parent device i tried to understand/change the source in src/mm-manager.c but without any results. any ideas? cheers, tom On Wed, 2010-05-26 at 17:59 +0200, Tom wrote: Hi Dan, On Wed, 2010-05-26 at 02:08 -0700, Dan Williams wrote: If you manually set the modem to 57600 and then run modem-manager, does that work? as mentioned in the last mail, the modem is detected. But i can not connect to the internet over ppp. Output is: ** Message: (ttyUSB1) opening serial device... ** (modem-manager:17984): DEBUG: 1274889434.174622 (ttyUSB1) device open count is 1 (open) ** (modem-manager:17984): DEBUG: (ttyUSB1): probe requested by plugin 'Generic' ** (modem-manager:17984): DEBUG: 1274889434.275168 (ttyUSB1): -- 'AT +GCAPCR' ** (modem-manager:17984): DEBUG: 1274889435.76137 (ttyUSB1): -- 'CRLF+GCAP: +CGSM,+FCLASSCRLFCRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889435.76290 (ttyUSB1) device open count is 0 (close) ** Message: (ttyUSB1) closing serial device... ** Message: (ttyUSB1) type primary claimed by /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 ** Message: (ttyUSB1) opening serial device... ** (modem-manager:17984): DEBUG: 1274889435.78881 (ttyUSB1) device open count is 1 (open) ** Message: (Generic): GSM modem /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 claimed port ttyUSB1 ** (modem-manager:17984): DEBUG: Added modem /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 ** (modem-manager:17984): DEBUG: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 ** (modem-manager:17984): DEBUG: 1274889435.79125 (ttyUSB1): -- 'AT +CPIN?CR' ** (modem-manager:17984): DEBUG: 1274889435.148615 (ttyUSB1): -- 'CRLF+CPIN: READYCRLF' ** (modem-manager:17984): DEBUG: 1274889435.152584 (ttyUSB1): -- 'CRLFOK' ** (modem-manager:17984): DEBUG: 1274889435.157066 (ttyUSB1): -- 'CRLF' ** (modem-manager:17984): DEBUG: 1274889435.157150 (ttyUSB1) device open count is 0 (close) ** Message: (ttyUSB1) closing serial device... ** (modem-manager:17984): DEBUG: Exported modem /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 as /org/freedesktop/ModemManager/Modems/4 ** (modem-manager:17984): DEBUG: (/org/freedesktop/ModemManager/Modems/4): data port is ttyUSB1 ** Message: (ttyUSB1) opening serial device... ** (modem-manager:17984): DEBUG: 1274889474.123884 (ttyUSB1) device open count is 1 (open) ** (modem-manager:17984): DEBUG: 1274889474.123947 Modem /org/freedesktop/ModemManager/Modems/4: state changed (disabled - enabling) ** (modem-manager:17984): DEBUG: 1274889474.224318 (ttyUSB1): -- 'ATZ E0 V1CR' ** (modem-manager:17984): DEBUG: 1274889474.368589 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.368738 (ttyUSB1): -- 'ATE0CR' ** (modem-manager:17984): DEBUG: 1274889474.428616 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.428741 (ttyUSB1): -- 'AT +CMEE=1CR' ** (modem-manager:17984): DEBUG: 1274889474.504607 (ttyUSB1): -- 'CRLFERRORCRLF' ** (modem-manager:17984): DEBUG: Got failure code 100: Unknown error ** (modem-manager:17984): DEBUG: 1274889474.504762 (ttyUSB1): -- 'ATX4 C1CR' ** (modem-manager:17984): DEBUG: 1274889474.580632 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.580757 (ttyUSB1): -- 'AT +CFUN=1CR' ** (modem-manager:17984): DEBUG: 1274889474.640615 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.640775 (ttyUSB1): -- 'AT +IFC=1,1CR' ** (modem-manager:17984): DEBUG: 1274889474.708594 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.708714 (ttyUSB1): -- 'AT +GMICR' ** (modem-manager:17984): DEBUG: 1274889474.772586 (ttyUSB1): -- 'CRLFSIEMENSCR' ** (modem-manager:17984): DEBUG: 1274889474.776565 (ttyUSB1): -- 'LFCRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.776670 (ttyUSB1): -- 'AT +GMMCR' ** (modem-manager:17984): DEBUG: 1274889474.832606 (ttyUSB1): -- 'CRLFTC63CRLF' ** (modem-manager:17984): DEBUG: 1274889474.840584 (ttyUSB1): -- 'CR' ** (modem-manager:17984): DEBUG: 1274889474.844586 (ttyUSB1): -- 'LFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.844683 (ttyUSB1): -- 'AT +GMRCR' ** (modem-manager:17984): DEBUG: 1274889474.904630 (ttyUSB1): -- 'CRLF' ** (modem-manager:17984): DEBUG: 1274889474.908557 (ttyUSB1): -- 'REVISION 02.500CRLF' ** (modem-manager:17984): DEBUG: 1274889474.912571 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.912669 (ttyUSB1): -- 'AT +CGMICR' ** (modem-manager:17984): DEBUG: 1274889474.976609 (ttyUSB1): -- 'CRLFSIEMENSCRLF' ** (modem-manager:17984): DEBUG: 1274889474.980569 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.980669 (ttyUSB1): -- 'AT +CGMMCR' ** (modem-manager:17984): DEBUG: 1274889475.36619
Re: RS232 GSM Modem
On Thu, 2010-05-13 at 23:36 -0700, Dan Williams wrote:
When MM is probing the port, try
stty -F /dev/ttyS1 -a
and lets see what the port settings are. Does the modem require those
specific speed and flow control settings?
Hi Dan,
sorry for the late answer.
Output is:
r...@banane:~# stty -F /dev/ttyS1 -a
speed 115200 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^A; eol = undef;
eol2 = undef; swtch = undef; start = ^Q; stop = ^S; susp = ^Z; rprnt
= ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 5;
-parenb -parodd cs8 -hupcl -cstopb cread clocal -crtscts
ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon
-ixoff
-iuclc -ixany -imaxbel -iutf8
-opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0
bs0 vt0 ff0
-isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop
-echoprt
-echoctl -echoke
I think the modem does not need any special flow control settings. The
baudrate can be set with AT+IPR=38400 (or another value like 115200).
But eg. with minicom i can only communicate with the modem when i use
the right baudrate. There is no autodetection or something like this.
What does ModemManager? Which Baudrate will be used when ModemManager
tries to detect the modem?
Cheers,
Tom
Dan
### BEGIN MINICOM ###
at
OK
atv
ACTIVE PROFILE:
E1 Q0 V1 X4 C0 D2 S0 \Q0 \V1
S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002 S18:000
+CBST: 7,0,1
+CRLP: 61,61,78,6
+CR: 0
+FCLASS: 0
+ICF: 3
+IFC: 0,0
+ILRR:
0
+IPR:
115200
+CMEE:
0
^SCKS:
0,1
^SSET:
0
OK
### END MINICOM ###
Hope this helps,
Cheers
Tom
Cheers,
Tom
Dan
The information about the device ( /dev/ttyS1 ):
# udevadm info --query=all -n /dev/ttyS1
P: /devices/platform/atmel_usart.1/tty/ttyS1
N: ttyS1
S: char/4:65
E: UDEV_LOG=3
E:
DEVPATH=/devices/platform/atmel_usart.1/tty/ttyS1
E: MAJOR=4
E: MINOR=65
E: DEVNAME=/dev/ttyS1
E: SUBSYSTEM=tty
E: DEVLINKS=/dev/char/4:65
# udevadm info --query=all -n /dev/ttyS1
--attribute-walk
...
looking at device
'/devices/platform/atmel_usart.1/tty/ttyS1':
KERNEL==ttyS1
SUBSYSTEM==tty
DRIVER==
looking at parent device
'/devices/platform/atmel_usart.1':
KERNELS==atmel_usart.1
SUBSYSTEMS==platform
DRIVERS==atmel_usart
ATTRS{modalias}==platform:atmel_usart
looking at parent device '/devices/platform':
KERNELS==platform
SUBSYSTEMS==
DRIVERS==
How can i use this port with ModemManager? The
modem is
connected and
AT-Commands works.
There are a number of requirements of the
port
though; it
verifies that the kernel has assigned a
driver name
to the
port or one
of the port's parents, and it attempts to
grab the
port's
physical
device. Given that it's USB, it *should*
work. But
if it
doesn't, and
you have a chance to grab the ModemManager
source
[1], there's
a tool
called 'lsudev' in the test/ directory
that can give
us an
idea of the
udev-provided information of the device.
Re: RS232 GSM Modem
On Wed, 2010-05-26 at 09:47 +0200, Tom wrote:
On Thu, 2010-05-13 at 23:36 -0700, Dan Williams wrote:
When MM is probing the port, try
stty -F /dev/ttyS1 -a
and lets see what the port settings are. Does the modem require those
specific speed and flow control settings?
Hi Dan,
sorry for the late answer.
Output is:
r...@banane:~# stty -F /dev/ttyS1 -a
speed 115200 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^A; eol = undef;
eol2 = undef; swtch = undef; start = ^Q; stop = ^S; susp = ^Z; rprnt
= ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 5;
-parenb -parodd cs8 -hupcl -cstopb cread clocal -crtscts
ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon
-ixoff
-iuclc -ixany -imaxbel -iutf8
-opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0
bs0 vt0 ff0
-isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop
-echoprt
-echoctl -echoke
I think the modem does not need any special flow control settings. The
baudrate can be set with AT+IPR=38400 (or another value like 115200).
But eg. with minicom i can only communicate with the modem when i use
the right baudrate. There is no autodetection or something like this.
What does ModemManager? Which Baudrate will be used when ModemManager
tries to detect the modem?
By default MM uses 57600, but this can be changed by a modem plugin,
except your device doesn't have a plugin and this sort of thing should
probably be solved in a more generic manner. Unfortunately I don't
really know if we can get any hardware IDs off your modem?
We could, for generic devices run by platform drivers attempt to do what
wvdial sort of does, which is try sending 'AT' at different speeds until
it gets an OK. Then use that speed. That might solve the problem
generically.
If you manually set the modem to 57600 and then run modem-manager, does
that work?
Dan
Cheers,
Tom
Dan
### BEGIN MINICOM ###
at
OK
atv
ACTIVE PROFILE:
E1 Q0 V1 X4 C0 D2 S0 \Q0 \V1
S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002 S18:000
+CBST: 7,0,1
+CRLP: 61,61,78,6
+CR: 0
+FCLASS: 0
+ICF: 3
+IFC: 0,0
+ILRR:
0
+IPR:
115200
+CMEE:
0
^SCKS:
0,1
^SSET:
0
OK
### END MINICOM ###
Hope this helps,
Cheers
Tom
Cheers,
Tom
Dan
The information about the device ( /dev/ttyS1 ):
# udevadm info --query=all -n /dev/ttyS1
P: /devices/platform/atmel_usart.1/tty/ttyS1
N: ttyS1
S: char/4:65
E: UDEV_LOG=3
E:
DEVPATH=/devices/platform/atmel_usart.1/tty/ttyS1
E: MAJOR=4
E: MINOR=65
E: DEVNAME=/dev/ttyS1
E: SUBSYSTEM=tty
E: DEVLINKS=/dev/char/4:65
# udevadm info --query=all -n /dev/ttyS1
--attribute-walk
...
looking at device
'/devices/platform/atmel_usart.1/tty/ttyS1':
KERNEL==ttyS1
SUBSYSTEM==tty
DRIVER==
looking at parent device
'/devices/platform/atmel_usart.1':
KERNELS==atmel_usart.1
SUBSYSTEMS==platform
DRIVERS==atmel_usart
ATTRS{modalias}==platform:atmel_usart
looking at parent device '/devices/platform':
KERNELS==platform
SUBSYSTEMS==
DRIVERS==
How can i use this port with ModemManager? The
modem is
connected and
AT-Commands works.
There are a number of requirements of the
port
though; it
verifies that the kernel has assigned a
Re: RS232 GSM Modem
On Wed, 2010-05-26 at 02:08 -0700, Dan Williams wrote: r...@banane:~# stty -F /dev/ttyS1 -a speed 115200 baud; rows 0; columns 0; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^A; eol = undef; eol2 = undef; swtch = undef; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 5; -parenb -parodd cs8 -hupcl -cstopb cread clocal -crtscts ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff -iuclc -ixany -imaxbel -iutf8 -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt -echoctl -echoke I think the modem does not need any special flow control settings. The baudrate can be set with AT+IPR=38400 (or another value like 115200). But eg. with minicom i can only communicate with the modem when i use the right baudrate. There is no autodetection or something like this. What does ModemManager? Which Baudrate will be used when ModemManager tries to detect the modem? By default MM uses 57600, but this can be changed by a modem plugin, except your device doesn't have a plugin and this sort of thing should probably be solved in a more generic manner. Unfortunately I don't really know if we can get any hardware IDs off your modem? The modem will be detected if i set the baudrate to 57600. Great! I'll try out if all works with ModemManager and let you know if there are more problems:) What do you mean with Hardware IDs? It's possible to use the following commands: AT+CGMI - Request manufacturer identification AT+CGMM - Request model identification AT+CGMR - Request revision identification of software status Section We could, for generic devices run by platform drivers attempt to do what wvdial sort of does, which is try sending 'AT' at different speeds until it gets an OK. Then use that speed. That might solve the problem generically. Good idea. but for me it's enough to know that i have to set the baudrate to 57600. i'm not very good in C so i can not provide some code to do the baudrate-probe. Sorry. If you manually set the modem to 57600 and then run modem-manager, does that work? yes. output is: BEGIN ** Message: ModemManager (version 0.3.997) starting... ** Message: Loaded plugin Generic ** Message: Loaded plugin Huawei ** Message: Loaded plugin Option ** Message: Loaded plugin Option High-Speed ** Message: Loaded plugin ZTE ** Message: Loaded plugin Longcheer ** Message: Loaded plugin Novatel ** Message: Loaded plugin MotoC ** Message: Loaded plugin Ericsson MBM ** Message: Loaded plugin Gobi ** Message: Loaded plugin AnyData ** Message: Loaded plugin SimTech ** Message: Loaded plugin Nokia ** Message: Loaded plugin Sierra ** (modem-manager:1833): DEBUG: (tty/ttyS0): port's parent platform driver is not whitelisted ** (modem-manager:1833): DEBUG: (tty/ttyS2): port's parent platform driver is not whitelisted ** (modem-manager:1833): DEBUG: (net/usb0): port's parent platform driver is not whitelisted ** (modem-manager:1833): DEBUG: (net/pan0): could not get port's parent device ** Message: (ttyS1) opening serial device... ** (modem-manager:1833): DEBUG: 1274880815.551890 (ttyS1) device open count is 1 (open) ** (modem-manager:1833): DEBUG: (ttyS1): probe requested by plugin 'Generic' ** (modem-manager:1833): DEBUG: 1274880815.654998 (ttyS1): -- 'AT +GCAPCR' ** (modem-manager:1833): DEBUG: 1274880816.534742 (ttyS1): -- 'AT +GCAPCRCRLF+GCAP: +CGSM,+FCLASSCRLFCRLFOKCRLF' ** (modem-manager:1833): DEBUG: 1274880816.536649 (ttyS1) device open count is 0 (close) ** Message: (ttyS1) closing serial device... ** Message: (ttyS1) type primary claimed by /sys/devices/platform/atmel_usart.1 ** Message: (ttyS1) opening serial device... ** (modem-manager:1833): DEBUG: 1274880816.566765 (ttyS1) device open count is 1 (open) ** Message: (Generic): GSM modem /sys/devices/platform/atmel_usart.1 claimed port ttyS1 ** (modem-manager:1833): DEBUG: Added modem /sys/devices/platform/atmel_usart.1 ** (modem-manager:1833): DEBUG: (tty/ttyS1): outstanding support task prevents export of /sys/devices/platform/atmel_usart.1 ** (modem-manager:1833): DEBUG: 1274880816.570255 (ttyS1): -- 'AT +CPIN?CR' ** (modem-manager:1833): DEBUG: 1274880816.654537 (ttyS1): -- 'AT +CPI' ** (modem-manager:1833): DEBUG: 1274880816.664273 (ttyS1): -- 'N?CR' ** (modem-manager:1833): DEBUG: 1274880816.694245 (ttyS1): -- 'CRLF+CPIN: READYCRLFCRLFOKCRLF' ** (modem-manager:1833): DEBUG: 1274880816.695440 (ttyS1) device open count is 0 (close) ** Message: (ttyS1) closing serial device... ** (modem-manager:1833): DEBUG: Exported modem /sys/devices/platform/atmel_usart.1 as /org/freedesktop/ModemManager/Modems/0 ** (modem-manager:1833): DEBUG: (/org/freedesktop/ModemManager/Modems/0): data port is ttyS1 # END Cheers, Tom Dan Cheers,
Re: RS232 GSM Modem
Hi Dan, On Wed, 2010-05-26 at 02:08 -0700, Dan Williams wrote: If you manually set the modem to 57600 and then run modem-manager, does that work? as mentioned in the last mail, the modem is detected. But i can not connect to the internet over ppp. Output is: ** Message: (ttyUSB1) opening serial device... ** (modem-manager:17984): DEBUG: 1274889434.174622 (ttyUSB1) device open count is 1 (open) ** (modem-manager:17984): DEBUG: (ttyUSB1): probe requested by plugin 'Generic' ** (modem-manager:17984): DEBUG: 1274889434.275168 (ttyUSB1): -- 'AT +GCAPCR' ** (modem-manager:17984): DEBUG: 1274889435.76137 (ttyUSB1): -- 'CRLF+GCAP: +CGSM,+FCLASSCRLFCRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889435.76290 (ttyUSB1) device open count is 0 (close) ** Message: (ttyUSB1) closing serial device... ** Message: (ttyUSB1) type primary claimed by /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 ** Message: (ttyUSB1) opening serial device... ** (modem-manager:17984): DEBUG: 1274889435.78881 (ttyUSB1) device open count is 1 (open) ** Message: (Generic): GSM modem /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 claimed port ttyUSB1 ** (modem-manager:17984): DEBUG: Added modem /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 ** (modem-manager:17984): DEBUG: (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 ** (modem-manager:17984): DEBUG: 1274889435.79125 (ttyUSB1): -- 'AT +CPIN?CR' ** (modem-manager:17984): DEBUG: 1274889435.148615 (ttyUSB1): -- 'CRLF+CPIN: READYCRLF' ** (modem-manager:17984): DEBUG: 1274889435.152584 (ttyUSB1): -- 'CRLFOK' ** (modem-manager:17984): DEBUG: 1274889435.157066 (ttyUSB1): -- 'CRLF' ** (modem-manager:17984): DEBUG: 1274889435.157150 (ttyUSB1) device open count is 0 (close) ** Message: (ttyUSB1) closing serial device... ** (modem-manager:17984): DEBUG: Exported modem /sys/devices/pci:00/:00:1d.7/usb3/3-1/3-1.1 as /org/freedesktop/ModemManager/Modems/4 ** (modem-manager:17984): DEBUG: (/org/freedesktop/ModemManager/Modems/4): data port is ttyUSB1 ** Message: (ttyUSB1) opening serial device... ** (modem-manager:17984): DEBUG: 1274889474.123884 (ttyUSB1) device open count is 1 (open) ** (modem-manager:17984): DEBUG: 1274889474.123947 Modem /org/freedesktop/ModemManager/Modems/4: state changed (disabled - enabling) ** (modem-manager:17984): DEBUG: 1274889474.224318 (ttyUSB1): -- 'ATZ E0 V1CR' ** (modem-manager:17984): DEBUG: 1274889474.368589 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.368738 (ttyUSB1): -- 'ATE0CR' ** (modem-manager:17984): DEBUG: 1274889474.428616 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.428741 (ttyUSB1): -- 'AT +CMEE=1CR' ** (modem-manager:17984): DEBUG: 1274889474.504607 (ttyUSB1): -- 'CRLFERRORCRLF' ** (modem-manager:17984): DEBUG: Got failure code 100: Unknown error ** (modem-manager:17984): DEBUG: 1274889474.504762 (ttyUSB1): -- 'ATX4 C1CR' ** (modem-manager:17984): DEBUG: 1274889474.580632 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.580757 (ttyUSB1): -- 'AT +CFUN=1CR' ** (modem-manager:17984): DEBUG: 1274889474.640615 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.640775 (ttyUSB1): -- 'AT +IFC=1,1CR' ** (modem-manager:17984): DEBUG: 1274889474.708594 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.708714 (ttyUSB1): -- 'AT +GMICR' ** (modem-manager:17984): DEBUG: 1274889474.772586 (ttyUSB1): -- 'CRLFSIEMENSCR' ** (modem-manager:17984): DEBUG: 1274889474.776565 (ttyUSB1): -- 'LFCRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.776670 (ttyUSB1): -- 'AT +GMMCR' ** (modem-manager:17984): DEBUG: 1274889474.832606 (ttyUSB1): -- 'CRLFTC63CRLF' ** (modem-manager:17984): DEBUG: 1274889474.840584 (ttyUSB1): -- 'CR' ** (modem-manager:17984): DEBUG: 1274889474.844586 (ttyUSB1): -- 'LFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.844683 (ttyUSB1): -- 'AT +GMRCR' ** (modem-manager:17984): DEBUG: 1274889474.904630 (ttyUSB1): -- 'CRLF' ** (modem-manager:17984): DEBUG: 1274889474.908557 (ttyUSB1): -- 'REVISION 02.500CRLF' ** (modem-manager:17984): DEBUG: 1274889474.912571 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.912669 (ttyUSB1): -- 'AT +CGMICR' ** (modem-manager:17984): DEBUG: 1274889474.976609 (ttyUSB1): -- 'CRLFSIEMENSCRLF' ** (modem-manager:17984): DEBUG: 1274889474.980569 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889474.980669 (ttyUSB1): -- 'AT +CGMMCR' ** (modem-manager:17984): DEBUG: 1274889475.36619 (ttyUSB1): -- 'CRLFTC63CRLF' ** (modem-manager:17984): DEBUG: 1274889475.44553 (ttyUSB1): -- 'CRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889475.44654 (ttyUSB1): -- 'AT +CGMRCR' ** (modem-manager:17984): DEBUG: 1274889475.108584 (ttyUSB1): -- 'CRLFREVISION' ** (modem-manager:17984): DEBUG: 1274889475.112567 (ttyUSB1): -- ' 02.500CRLFCRLFOKCRLF' ** (modem-manager:17984): DEBUG: 1274889475.112683 (ttyUSB1): --
Re: RS232 GSM Modem
On Wed, 2010-05-12 at 09:38 +0200, toabctl wrote: i can not find the code from: commit 1864d8da0766e615c37a13f30bcacb72d381aa69 Author: Dan Williams d...@redhat.com Date: Thu Apr 29 12:17:56 2010 -0700 core: add platform device support and whitelist anymore. i would like to test the modem at the uart port again. @Dan: can you post the patch again, please? Sorry for the delay... http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=1864d8da0766e615c37a13f30bcacb72d381aa69 that should be the commit you're looking for. Dan Cheers, Tom 2010/5/7 toabctl toab...@googlemail.com @Dan: Do you need more information about the modem? Or any other information? 2010/5/3 toabctl toab...@googlemail.com 2010/5/2 Dan Williams d...@redhat.com On Fri, 2010-04-30 at 14:05 +0200, toabctl wrote: 2010/4/29 Dan Williams d...@redhat.com On Thu, 2010-04-29 at 09:53 +0200, toabctl wrote: 2010/4/28 Dan Williams d...@redhat.com On Wed, 2010-04-28 at 09:37 +0200, toabctl wrote: 1) How does network-manager detect that the modem is connected? Or how can i tell networkmanager on which port the modem is attached? I use a rs232-usb adapter so the port is /dev/ttyUSB0 . ModemManager uses udev for device detection. It listens for udev events (which you can also listen for with udevmonitor) and when it receives a notification of a new serial port, it will inspect that port and attempt to probe it. How does ModemManager probe the port? I want to use modem manager also with a rs232 device and there are no uevents because rs232 has no hotplug. but i could emit a uevent by hand. At the moment we don't probe platform devices for a few reasons, one that (a) the code isn't there, and (b) older devices like those connected to platform serial ports on normal PCs often get upset precisely because they are older and either aren't modems, or aren't standards compliant in any way. But check out this commit: commit 1864d8da0766e615c37a13f30bcacb72d381aa69 Author: Dan Williams d...@redhat.com Date: Thu Apr 29 12:17:56 2010 -0700 core: add platform device support and whitelist and see if that works for you. It uses a whitelist for platform drivers. Let me know! does not work for me. But i'm not sure hot to
Re: RS232 GSM Modem
On Mon, 2010-05-03 at 10:58 +0200, toabctl wrote: 2010/5/2 Dan Williams d...@redhat.com On Fri, 2010-04-30 at 14:05 +0200, toabctl wrote: 2010/4/29 Dan Williams d...@redhat.com On Thu, 2010-04-29 at 09:53 +0200, toabctl wrote: 2010/4/28 Dan Williams d...@redhat.com On Wed, 2010-04-28 at 09:37 +0200, toabctl wrote: 1) How does network-manager detect that the modem is connected? Or how can i tell networkmanager on which port the modem is attached? I use a rs232-usb adapter so the port is /dev/ttyUSB0 . ModemManager uses udev for device detection. It listens for udev events (which you can also listen for with udevmonitor) and when it receives a notification of a new serial port, it will inspect that port and attempt to probe it. How does ModemManager probe the port? I want to use modem manager also with a rs232 device and there are no uevents because rs232 has no hotplug. but i could emit a uevent by hand. At the moment we don't probe platform devices for a few reasons, one that (a) the code isn't there, and (b) older devices like those connected to platform serial ports on normal PCs often get upset precisely because they are older and either aren't modems, or aren't standards compliant in any way. But check out this commit: commit 1864d8da0766e615c37a13f30bcacb72d381aa69 Author: Dan Williams d...@redhat.com Date: Thu Apr 29 12:17:56 2010 -0700 core: add platform device support and whitelist and see if that works for you. It uses a whitelist for platform drivers. Let me know! does not work for me. But i'm not sure hot to test it. i just use the python script from test/mm-test.py and the result is: no modems found. But the device is available (checked with minicom) and /lib/udev/rules.d/77-mm-platform-serial-whitelist.rules is available. What to do next? Do you need more information? Yeah, what logs do you get from 'modem-manager --debug', and can you run the lsudev tool in tests/ like this for me when the device is connected? lsudev tty Thanks! Dan Hi Dan, see attachments for the 'lsudev tty' and 'modem-manager --debug' . The Modem is a Siemens TC63i connected to /dev/ttyS1 . A minicom session looks like this (Baudrate 115200; 8N1; Hardware Flow Control: No; Software Flow Control: No;) When MM is probing the port, try stty -F /dev/ttyS1 -a and lets see what the port settings are. Does the modem require those specific speed and flow control settings? Dan ### BEGIN MINICOM ### at OK atv ACTIVE PROFILE: E1 Q0 V1 X4 C0 D2 S0 \Q0 \V1 S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002 S18:000 +CBST: 7,0,1 +CRLP: 61,61,78,6 +CR: 0 +FCLASS: 0 +ICF: 3 +IFC: 0,0 +ILRR: 0 +IPR: 115200 +CMEE: 0 ^SCKS: 0,1 ^SSET: 0 OK ### END MINICOM ### Hope this helps, Cheers Tom Cheers, Tom Dan The information about the device ( /dev/ttyS1 ): # udevadm info --query=all -n /dev/ttyS1 P:
Re: RS232 GSM Modem
i can not find the code from:
commit 1864d8da0766e615c37a13f30bcacb72d381aa69
Author: Dan Williams d...@redhat.com
Date: Thu Apr 29 12:17:56 2010 -0700
core: add platform device support and whitelist
anymore. i would like to test the modem at the uart port again.
@Dan: can you post the patch again, please?
Cheers,
Tom
2010/5/7 toabctl toab...@googlemail.com
@Dan: Do you need more information about the modem? Or any other
information?
2010/5/3 toabctl toab...@googlemail.com
2010/5/2 Dan Williams d...@redhat.com
On Fri, 2010-04-30 at 14:05 +0200, toabctl wrote:
2010/4/29 Dan Williams d...@redhat.com
On Thu, 2010-04-29 at 09:53 +0200, toabctl wrote:
2010/4/28 Dan Williams d...@redhat.com
On Wed, 2010-04-28 at 09:37 +0200, toabctl wrote:
1) How does network-manager detect that the modem
is
connected? Or how
can i tell networkmanager on which port the modem
is
attached? I use a
rs232-usb adapter so the port is /dev/ttyUSB0 .
ModemManager uses udev for device detection. It
listens for
udev events
(which you can also listen for with udevmonitor) and
when it
receives a
notification of a new serial port, it will inspect
that port
and attempt
to probe it.
How does ModemManager probe the port? I want to use modem
manager also
with a rs232 device and there are no uevents because rs232
has no
hotplug. but i could emit a uevent by hand.
At the moment we don't probe platform devices for a few
reasons, one
that (a) the code isn't there, and (b) older devices like
those
connected to platform serial ports on normal PCs often get
upset
precisely because they are older and either aren't modems, or
aren't
standards compliant in any way.
But check out this commit:
commit 1864d8da0766e615c37a13f30bcacb72d381aa69
Author: Dan Williams d...@redhat.com
Date: Thu Apr 29 12:17:56 2010 -0700
core: add platform device support and whitelist
and see if that works for you. It uses a whitelist for
platform
drivers. Let me know!
does not work for me. But i'm not sure hot to test it. i just use the
python script from test/mm-test.py and the result is: no modems
found. But the device is available (checked with minicom)
and /lib/udev/rules.d/77-mm-platform-serial-whitelist.rules is
available.
What to do next? Do you need more information?
Yeah, what logs do you get from 'modem-manager --debug', and can you run
the lsudev tool in tests/ like this for me when the device is connected?
lsudev tty
Thanks!
Dan
Hi Dan,
see attachments for the 'lsudev tty' and 'modem-manager --debug' . The
Modem is a Siemens TC63i connected to /dev/ttyS1 .
A minicom session looks like this (Baudrate 115200; 8N1; Hardware Flow
Control: No; Software Flow Control: No;)
### BEGIN MINICOM ###
at
OK
atv
ACTIVE PROFILE:
E1 Q0 V1 X4 C0 D2 S0 \Q0 \V1
S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002 S18:000
+CBST: 7,0,1
+CRLP: 61,61,78,6
+CR: 0
+FCLASS: 0
+ICF: 3
+IFC: 0,0
+ILRR:
0
+IPR:
115200
+CMEE:
0
^SCKS:
0,1
^SSET:
0
OK
### END MINICOM ###
Hope this helps,
Cheers
Tom
Cheers,
Tom
Dan
The information about the device ( /dev/ttyS1 ):
# udevadm info --query=all -n /dev/ttyS1
P: /devices/platform/atmel_usart.1/tty/ttyS1
N: ttyS1
S: char/4:65
E: UDEV_LOG=3
E: DEVPATH=/devices/platform/atmel_usart.1/tty/ttyS1
E: MAJOR=4
E: MINOR=65
E: DEVNAME=/dev/ttyS1
E: SUBSYSTEM=tty
E: DEVLINKS=/dev/char/4:65
# udevadm info --query=all -n /dev/ttyS1 --attribute-walk
...
looking at device
'/devices/platform/atmel_usart.1/tty/ttyS1':
KERNEL==ttyS1
SUBSYSTEM==tty
DRIVER==
looking at parent device
'/devices/platform/atmel_usart.1':
KERNELS==atmel_usart.1
SUBSYSTEMS==platform
DRIVERS==atmel_usart
ATTRS{modalias}==platform:atmel_usart
looking at parent device '/devices/platform':
KERNELS==platform
SUBSYSTEMS==
DRIVERS==
How can i use this port with ModemManager? The modem is
connected and
Re: RS232 GSM Modem
@Dan: Do you need more information about the modem? Or any other
information?
2010/5/3 toabctl toab...@googlemail.com
2010/5/2 Dan Williams d...@redhat.com
On Fri, 2010-04-30 at 14:05 +0200, toabctl wrote:
2010/4/29 Dan Williams d...@redhat.com
On Thu, 2010-04-29 at 09:53 +0200, toabctl wrote:
2010/4/28 Dan Williams d...@redhat.com
On Wed, 2010-04-28 at 09:37 +0200, toabctl wrote:
1) How does network-manager detect that the modem
is
connected? Or how
can i tell networkmanager on which port the modem
is
attached? I use a
rs232-usb adapter so the port is /dev/ttyUSB0 .
ModemManager uses udev for device detection. It
listens for
udev events
(which you can also listen for with udevmonitor) and
when it
receives a
notification of a new serial port, it will inspect
that port
and attempt
to probe it.
How does ModemManager probe the port? I want to use modem
manager also
with a rs232 device and there are no uevents because rs232
has no
hotplug. but i could emit a uevent by hand.
At the moment we don't probe platform devices for a few
reasons, one
that (a) the code isn't there, and (b) older devices like
those
connected to platform serial ports on normal PCs often get
upset
precisely because they are older and either aren't modems, or
aren't
standards compliant in any way.
But check out this commit:
commit 1864d8da0766e615c37a13f30bcacb72d381aa69
Author: Dan Williams d...@redhat.com
Date: Thu Apr 29 12:17:56 2010 -0700
core: add platform device support and whitelist
and see if that works for you. It uses a whitelist for
platform
drivers. Let me know!
does not work for me. But i'm not sure hot to test it. i just use the
python script from test/mm-test.py and the result is: no modems
found. But the device is available (checked with minicom)
and /lib/udev/rules.d/77-mm-platform-serial-whitelist.rules is
available.
What to do next? Do you need more information?
Yeah, what logs do you get from 'modem-manager --debug', and can you run
the lsudev tool in tests/ like this for me when the device is connected?
lsudev tty
Thanks!
Dan
Hi Dan,
see attachments for the 'lsudev tty' and 'modem-manager --debug' . The
Modem is a Siemens TC63i connected to /dev/ttyS1 .
A minicom session looks like this (Baudrate 115200; 8N1; Hardware Flow
Control: No; Software Flow Control: No;)
### BEGIN MINICOM ###
at
OK
atv
ACTIVE PROFILE:
E1 Q0 V1 X4 C0 D2 S0 \Q0 \V1
S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002 S18:000
+CBST: 7,0,1
+CRLP: 61,61,78,6
+CR: 0
+FCLASS: 0
+ICF: 3
+IFC: 0,0
+ILRR:
0
+IPR:
115200
+CMEE:
0
^SCKS:
0,1
^SSET:
0
OK
### END MINICOM ###
Hope this helps,
Cheers
Tom
Cheers,
Tom
Dan
The information about the device ( /dev/ttyS1 ):
# udevadm info --query=all -n /dev/ttyS1
P: /devices/platform/atmel_usart.1/tty/ttyS1
N: ttyS1
S: char/4:65
E: UDEV_LOG=3
E: DEVPATH=/devices/platform/atmel_usart.1/tty/ttyS1
E: MAJOR=4
E: MINOR=65
E: DEVNAME=/dev/ttyS1
E: SUBSYSTEM=tty
E: DEVLINKS=/dev/char/4:65
# udevadm info --query=all -n /dev/ttyS1 --attribute-walk
...
looking at device
'/devices/platform/atmel_usart.1/tty/ttyS1':
KERNEL==ttyS1
SUBSYSTEM==tty
DRIVER==
looking at parent device
'/devices/platform/atmel_usart.1':
KERNELS==atmel_usart.1
SUBSYSTEMS==platform
DRIVERS==atmel_usart
ATTRS{modalias}==platform:atmel_usart
looking at parent device '/devices/platform':
KERNELS==platform
SUBSYSTEMS==
DRIVERS==
How can i use this port with ModemManager? The modem is
connected and
AT-Commands works.
There are a number of requirements of the port
though; it
verifies that the kernel has assigned a driver name
to the
port or one
of the port's parents, and it attempts to grab the
port's
physical
device. Given that it's
Re: RS232 GSM Modem
2010/4/29 Dan Williams d...@redhat.com
On Thu, 2010-04-29 at 09:53 +0200, toabctl wrote:
2010/4/28 Dan Williams d...@redhat.com
On Wed, 2010-04-28 at 09:37 +0200, toabctl wrote:
1) How does network-manager detect that the modem is
connected? Or how
can i tell networkmanager on which port the modem is
attached? I use a
rs232-usb adapter so the port is /dev/ttyUSB0 .
ModemManager uses udev for device detection. It listens for
udev events
(which you can also listen for with udevmonitor) and when it
receives a
notification of a new serial port, it will inspect that port
and attempt
to probe it.
How does ModemManager probe the port? I want to use modem manager also
with a rs232 device and there are no uevents because rs232 has no
hotplug. but i could emit a uevent by hand.
At the moment we don't probe platform devices for a few reasons, one
that (a) the code isn't there, and (b) older devices like those
connected to platform serial ports on normal PCs often get upset
precisely because they are older and either aren't modems, or aren't
standards compliant in any way.
But check out this commit:
commit 1864d8da0766e615c37a13f30bcacb72d381aa69
Author: Dan Williams d...@redhat.com
Date: Thu Apr 29 12:17:56 2010 -0700
core: add platform device support and whitelist
and see if that works for you. It uses a whitelist for platform
drivers. Let me know!
does not work for me. i used the latest git master source. But i'm not sure
hot to test it. i just use the python script from test/mm-test.py and the
result is: no modems found. But the device is available (checked with
minicom) and /lib/udev/rules.d/77-mm-
platform-serial-whitelist.rules is available.
What to do next? Do you need more information?
Cheers,
Tom
Dan
The information about the device ( /dev/ttyS1 ):
# udevadm info --query=all -n /dev/ttyS1
P: /devices/platform/atmel_usart.1/tty/ttyS1
N: ttyS1
S: char/4:65
E: UDEV_LOG=3
E: DEVPATH=/devices/platform/atmel_usart.1/tty/ttyS1
E: MAJOR=4
E: MINOR=65
E: DEVNAME=/dev/ttyS1
E: SUBSYSTEM=tty
E: DEVLINKS=/dev/char/4:65
# udevadm info --query=all -n /dev/ttyS1 --attribute-walk
...
looking at device '/devices/platform/atmel_usart.1/tty/ttyS1':
KERNEL==ttyS1
SUBSYSTEM==tty
DRIVER==
looking at parent device '/devices/platform/atmel_usart.1':
KERNELS==atmel_usart.1
SUBSYSTEMS==platform
DRIVERS==atmel_usart
ATTRS{modalias}==platform:atmel_usart
looking at parent device '/devices/platform':
KERNELS==platform
SUBSYSTEMS==
DRIVERS==
How can i use this port with ModemManager? The modem is connected and
AT-Commands works.
There are a number of requirements of the port though; it
verifies that the kernel has assigned a driver name to the
port or one
of the port's parents, and it attempts to grab the port's
physical
device. Given that it's USB, it *should* work. But if it
doesn't, and
you have a chance to grab the ModemManager source [1], there's
a tool
called 'lsudev' in the test/ directory that can give us an
idea of the
udev-provided information of the device.
i guess 'lsudev' does the same as my 2 commands with 'udevadm', right?
or does 'lsudev' something more special?
2) How does the connection-config looks like?
ModemManager is just a tool to control the modem, it doesn't
store any
configuration about it. The configuration is provided by a
program that
tells ModemManager what to do. There are a few ways to do
that;
NetworkManager provides a general modem control solution, but
you can
also write your own app that uses D-Bus to tell ModemManager
what to do
with the modem. See test/mm-test.py for a short example of
how to use
python and D-Bus to make MM connect the modem and get
information out of
it.
ah. that's great. i need to control the modem over a web-interface so
no nm-applet available.
Cheers,
Tom
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RS232 GSM Modem
Hi Dan,
i realized that ModemManager does something with the serial port, but with
the wrong port. I have /dev/ttyS= which is connected over a serial line to
my PC. Getty listen on this port.
And i have /dev/ttyS1 where the modem is connected.
When i reboot the device, some AT-Commands will be written to ttyS0.
# Start boot process ###
.
Starting network connection manager: NetworkManagerBridge firewalling
registered
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
.
0`枆~0 0怘�ADebian GNU/Linux squeeze/sid banane ttyS0
AT+GCAPlogin: P
Debian GNU/Linux squeeze/sid banane ttyS0
banane login: AT+GCAP
Debian GNU/Linux squeeze/sid banane ttyS0
banane login: x�~
Debian GNU/Linux squeeze/sid banane ttyS0
banane login: x�~
Debian GNU/Linux squeeze/sid banane ttyS0
# END boot process ###
I pressed sometimes 'ENTER' because otherwise you wouldn't see the output
(new message would overwrite old messages).
Hope this information helps!
Cheers,
Tom
2010/4/30 toabctl toab...@googlemail.com
2010/4/29 Dan Williams d...@redhat.com
On Thu, 2010-04-29 at 09:53 +0200, toabctl wrote:
2010/4/28 Dan Williams d...@redhat.com
On Wed, 2010-04-28 at 09:37 +0200, toabctl wrote:
1) How does network-manager detect that the modem is
connected? Or how
can i tell networkmanager on which port the modem is
attached? I use a
rs232-usb adapter so the port is /dev/ttyUSB0 .
ModemManager uses udev for device detection. It listens for
udev events
(which you can also listen for with udevmonitor) and when it
receives a
notification of a new serial port, it will inspect that port
and attempt
to probe it.
How does ModemManager probe the port? I want to use modem manager also
with a rs232 device and there are no uevents because rs232 has no
hotplug. but i could emit a uevent by hand.
At the moment we don't probe platform devices for a few reasons, one
that (a) the code isn't there, and (b) older devices like those
connected to platform serial ports on normal PCs often get upset
precisely because they are older and either aren't modems, or aren't
standards compliant in any way.
But check out this commit:
commit 1864d8da0766e615c37a13f30bcacb72d381aa69
Author: Dan Williams d...@redhat.com
Date: Thu Apr 29 12:17:56 2010 -0700
core: add platform device support and whitelist
and see if that works for you. It uses a whitelist for platform
drivers. Let me know!
does not work for me. i used the latest git master source. But i'm not sure
hot to test it. i just use the python script from test/mm-test.py and the
result is: no modems found. But the device is available (checked with
minicom) and /lib/udev/rules.d/77-mm-
platform-serial-whitelist.rules is available.
What to do next? Do you need more information?
Cheers,
Tom
Dan
The information about the device ( /dev/ttyS1 ):
# udevadm info --query=all -n /dev/ttyS1
P: /devices/platform/atmel_usart.1/tty/ttyS1
N: ttyS1
S: char/4:65
E: UDEV_LOG=3
E: DEVPATH=/devices/platform/atmel_usart.1/tty/ttyS1
E: MAJOR=4
E: MINOR=65
E: DEVNAME=/dev/ttyS1
E: SUBSYSTEM=tty
E: DEVLINKS=/dev/char/4:65
# udevadm info --query=all -n /dev/ttyS1 --attribute-walk
...
looking at device '/devices/platform/atmel_usart.1/tty/ttyS1':
KERNEL==ttyS1
SUBSYSTEM==tty
DRIVER==
looking at parent device '/devices/platform/atmel_usart.1':
KERNELS==atmel_usart.1
SUBSYSTEMS==platform
DRIVERS==atmel_usart
ATTRS{modalias}==platform:atmel_usart
looking at parent device '/devices/platform':
KERNELS==platform
SUBSYSTEMS==
DRIVERS==
How can i use this port with ModemManager? The modem is connected and
AT-Commands works.
There are a number of requirements of the port though; it
verifies that the kernel has assigned a driver name to the
port or one
of the port's parents, and it attempts to grab the port's
physical
device. Given that it's USB, it *should* work. But if it
doesn't, and
you have a chance to grab the ModemManager source [1], there's
a tool
called 'lsudev' in the test/ directory that can give us an
idea of the
udev-provided information of the device.
i guess 'lsudev' does the same as my 2 commands with 'udevadm', right?
or does 'lsudev' something more special?
2) How does the connection-config looks like?
ModemManager is just a tool to control the modem, it doesn't
store any
configuration about it. The configuration is provided by a
program that
tells ModemManager what to do. There are a few ways to do
that;
NetworkManager provides a general modem control solution,
Re: RS232 GSM Modem
2010/4/28 Dan Williams d...@redhat.com
On Wed, 2010-04-28 at 09:37 +0200, toabctl wrote:
1) How does network-manager detect that the modem is connected? Or how
can i tell networkmanager on which port the modem is attached? I use a
rs232-usb adapter so the port is /dev/ttyUSB0 .
ModemManager uses udev for device detection. It listens for udev events
(which you can also listen for with udevmonitor) and when it receives a
notification of a new serial port, it will inspect that port and attempt
to probe it.
How does ModemManager probe the port? I want to use modem manager also with
a rs232 device and there are no uevents because rs232 has no hotplug. but i
could emit a uevent by hand.
The information about the device ( /dev/ttyS1 ):
# udevadm info --query=all -n /dev/ttyS1
P: /devices/platform/atmel_usart.1/tty/ttyS1
N: ttyS1
S: char/4:65
E: UDEV_LOG=3
E: DEVPATH=/devices/platform/atmel_usart.1/tty/ttyS1
E: MAJOR=4
E: MINOR=65
E: DEVNAME=/dev/ttyS1
E: SUBSYSTEM=tty
E: DEVLINKS=/dev/char/4:65
# udevadm info --query=all -n /dev/ttyS1 --attribute-walk
...
looking at device '/devices/platform/atmel_usart.1/tty/ttyS1':
KERNEL==ttyS1
SUBSYSTEM==tty
DRIVER==
looking at parent device '/devices/platform/atmel_usart.1':
KERNELS==atmel_usart.1
SUBSYSTEMS==platform
DRIVERS==atmel_usart
ATTRS{modalias}==platform:atmel_usart
looking at parent device '/devices/platform':
KERNELS==platform
SUBSYSTEMS==
DRIVERS==
How can i use this port with ModemManager? The modem is connected and
AT-Commands works.
There are a number of requirements of the port though; it
verifies that the kernel has assigned a driver name to the port or one
of the port's parents, and it attempts to grab the port's physical
device. Given that it's USB, it *should* work. But if it doesn't, and
you have a chance to grab the ModemManager source [1], there's a tool
called 'lsudev' in the test/ directory that can give us an idea of the
udev-provided information of the device.
i guess 'lsudev' does the same as my 2 commands with 'udevadm', right? or
does 'lsudev' something more special?
2) How does the connection-config looks like?
ModemManager is just a tool to control the modem, it doesn't store any
configuration about it. The configuration is provided by a program that
tells ModemManager what to do. There are a few ways to do that;
NetworkManager provides a general modem control solution, but you can
also write your own app that uses D-Bus to tell ModemManager what to do
with the modem. See test/mm-test.py for a short example of how to use
python and D-Bus to make MM connect the modem and get information out of
it.
ah. that's great. i need to control the modem over a web-interface so no
nm-applet available.
Cheers,
Tom
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RS232 GSM Modem
On Thu, 2010-04-29 at 09:53 +0200, toabctl wrote:
2010/4/28 Dan Williams d...@redhat.com
On Wed, 2010-04-28 at 09:37 +0200, toabctl wrote:
1) How does network-manager detect that the modem is
connected? Or how
can i tell networkmanager on which port the modem is
attached? I use a
rs232-usb adapter so the port is /dev/ttyUSB0 .
ModemManager uses udev for device detection. It listens for
udev events
(which you can also listen for with udevmonitor) and when it
receives a
notification of a new serial port, it will inspect that port
and attempt
to probe it.
How does ModemManager probe the port? I want to use modem manager also
with a rs232 device and there are no uevents because rs232 has no
hotplug. but i could emit a uevent by hand.
At the moment we don't probe platform devices for a few reasons, one
that (a) the code isn't there, and (b) older devices like those
connected to platform serial ports on normal PCs often get upset
precisely because they are older and either aren't modems, or aren't
standards compliant in any way.
But check out this commit:
commit 1864d8da0766e615c37a13f30bcacb72d381aa69
Author: Dan Williams d...@redhat.com
Date: Thu Apr 29 12:17:56 2010 -0700
core: add platform device support and whitelist
and see if that works for you. It uses a whitelist for platform
drivers. Let me know!
Dan
The information about the device ( /dev/ttyS1 ):
# udevadm info --query=all -n /dev/ttyS1
P: /devices/platform/atmel_usart.1/tty/ttyS1
N: ttyS1
S: char/4:65
E: UDEV_LOG=3
E: DEVPATH=/devices/platform/atmel_usart.1/tty/ttyS1
E: MAJOR=4
E: MINOR=65
E: DEVNAME=/dev/ttyS1
E: SUBSYSTEM=tty
E: DEVLINKS=/dev/char/4:65
# udevadm info --query=all -n /dev/ttyS1 --attribute-walk
...
looking at device '/devices/platform/atmel_usart.1/tty/ttyS1':
KERNEL==ttyS1
SUBSYSTEM==tty
DRIVER==
looking at parent device '/devices/platform/atmel_usart.1':
KERNELS==atmel_usart.1
SUBSYSTEMS==platform
DRIVERS==atmel_usart
ATTRS{modalias}==platform:atmel_usart
looking at parent device '/devices/platform':
KERNELS==platform
SUBSYSTEMS==
DRIVERS==
How can i use this port with ModemManager? The modem is connected and
AT-Commands works.
There are a number of requirements of the port though; it
verifies that the kernel has assigned a driver name to the
port or one
of the port's parents, and it attempts to grab the port's
physical
device. Given that it's USB, it *should* work. But if it
doesn't, and
you have a chance to grab the ModemManager source [1], there's
a tool
called 'lsudev' in the test/ directory that can give us an
idea of the
udev-provided information of the device.
i guess 'lsudev' does the same as my 2 commands with 'udevadm', right?
or does 'lsudev' something more special?
2) How does the connection-config looks like?
ModemManager is just a tool to control the modem, it doesn't
store any
configuration about it. The configuration is provided by a
program that
tells ModemManager what to do. There are a few ways to do
that;
NetworkManager provides a general modem control solution, but
you can
also write your own app that uses D-Bus to tell ModemManager
what to do
with the modem. See test/mm-test.py for a short example of
how to use
python and D-Bus to make MM connect the modem and get
information out of
it.
ah. that's great. i need to control the modem over a web-interface so
no nm-applet available.
Cheers,
Tom
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RS232 GSM Modem
On Wed, 2010-04-28 at 09:37 +0200, toabctl wrote: Hi, i want to use network-manager 0.8 in debian embedded system. I want to connect the system with network/modem manager to the gsm network and have a Siemens TC63i modem for that available. I can manually use the modem with the AT-Commands, but i don't know how to setup the connection with network/modem manager. Question: 1) How does network-manager detect that the modem is connected? Or how can i tell networkmanager on which port the modem is attached? I use a rs232-usb adapter so the port is /dev/ttyUSB0 . ModemManager uses udev for device detection. It listens for udev events (which you can also listen for with udevmonitor) and when it receives a notification of a new serial port, it will inspect that port and attempt to probe it. There are a number of requirements of the port though; it verifies that the kernel has assigned a driver name to the port or one of the port's parents, and it attempts to grab the port's physical device. Given that it's USB, it *should* work. But if it doesn't, and you have a chance to grab the ModemManager source [1], there's a tool called 'lsudev' in the test/ directory that can give us an idea of the udev-provided information of the device. 2) How does the connection-config looks like? ModemManager is just a tool to control the modem, it doesn't store any configuration about it. The configuration is provided by a program that tells ModemManager what to do. There are a few ways to do that; NetworkManager provides a general modem control solution, but you can also write your own app that uses D-Bus to tell ModemManager what to do with the modem. See test/mm-test.py for a short example of how to use python and D-Bus to make MM connect the modem and get information out of it. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
