Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Thu, 2008-12-04 at 10:40 -0800, Bert Haverkamp wrote: Hello Dan, So, I strongly suggest to hold off playing with PPP and instead wait for some shiny glittering features coming out soon... I'm a bit confused by this threat's ending. What is this spiffy feautre we are waiting for exactly. Can you give us an update on the support of this modem (the Dell 5530 in my case) with network-manager? You can use this modem in two ways: 1) traditional style, with PPP: should work, though there may be a bug where the modem echos garbage before it sends the CONNECT message, which confuses NM. 2) using the 'mbm' driver: much higher throughput than using PPP, but: a) the driver is not usptream in the kernel yet b) requires ModemManager, which won't be added to NM until NM 0.8 What Per is saying is that you should wait for #2. However, if #1 doesn't work for you, I'd like to know about it, so I can fix it. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
Hello Dan, So, I strongly suggest to hold off playing with PPP and instead wait for some shiny glittering features coming out soon... I'm a bit confused by this threat's ending. What is this spiffy feautre we are waiting for exactly. Can you give us an update on the support of this modem (the Dell 5530 in my case) with network-manager? Regards, Bert -- View this message in context: http://www.nabble.com/Mobile-Broadband---how-do-I-trace-debug-the-modem-initialisation--tp20046325p20839711.html Sent from the Gnome - NetworkManager mailing list archive at Nabble.com. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Mobile Broadband - how do I trace/debug the modem initialisation?
On Wed, 2008-10-22 at 00:38 +0100, Rick Jones wrote: --On Tuesday, October 21, 2008 14:08:25 -0400 Dan Williams [EMAIL PROTECTED] wrote: ¦ On Tue, 2008-10-21 at 19:16 +0200, Main, Craig wrote: .. ¦ -- Modem initialized. ¦ -- Sending: ATDT*99***1# ¦ -- Waiting for carrier. ¦ ATDT*99***1# ¦ [EMAIL PROTECTED] }9}#}%B#}%}(}}' } } } }%}mG!;J[1d]~ ¦ ¦ Holy crap, WTF is that??? I know you don't know, but wow. That can't ¦ be a valid standards-compliant implementation. AFAIK that's the PPP negotiation. If you manually open a connection to any PPP wserver with minicom or equiv. that stuff comes back. Usually the modem returns CONNECT first, and the device is handed over to the PPP code so this doesn't get traced, but here CONNECT comes later, and then we see that PPP is correctly detected: Correct, that is the ppp negotiation ¦ CONNECT ¦ -- Carrier detected. Waiting for prompt. ¦ [EMAIL PROTECTED]} }9}#}%B#}%}(}}' } } } }%}mG!;[06]p~ ¦ -- PPP negotiation detected. To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Mobile Broadband - how do I trace/debug the modem initialisation?
On Wed, 2008-10-22 at 08:39 +0200, Craig Main wrote: On Wed, 2008-10-22 at 00:38 +0100, Rick Jones wrote: --On Tuesday, October 21, 2008 14:08:25 -0400 Dan Williams [EMAIL PROTECTED] wrote: ¦ On Tue, 2008-10-21 at 19:16 +0200, Main, Craig wrote: .. ¦ -- Modem initialized. ¦ -- Sending: ATDT*99***1# ¦ -- Waiting for carrier. ¦ ATDT*99***1# ¦ [EMAIL PROTECTED] }9}#}%B#}%}(}}' } } } }%}mG!;J[1d]~ ¦ ¦ Holy crap, WTF is that??? I know you don't know, but wow. That can't ¦ be a valid standards-compliant implementation. AFAIK that's the PPP negotiation. If you manually open a connection to any PPP wserver with minicom or equiv. that stuff comes back. Usually the modem returns CONNECT first, and the device is handed over to the PPP code so this doesn't get traced, but here CONNECT comes later, and then we see that PPP is correctly detected: Correct, that is the ppp negotiation Cute, so pppd will now miss the first part of the negotiation, simply because the card is too damn slow with CONNECT? That's a great experience for fast, reliable connections :) Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
Dan Williams wrote: On Wed, 2008-10-22 at 08:39 +0200, Craig Main wrote: On Wed, 2008-10-22 at 00:38 +0100, Rick Jones wrote: --On Tuesday, October 21, 2008 14:08:25 -0400 Dan Williams [EMAIL PROTECTED] wrote: ¦ On Tue, 2008-10-21 at 19:16 +0200, Main, Craig wrote: .. ¦ -- Modem initialized. ¦ -- Sending: ATDT*99***1# ¦ -- Waiting for carrier. ¦ ATDT*99***1# ¦ [EMAIL PROTECTED] }9}#}%B#}%}(}}' } } } }%}mG!;J[1d]~ ¦ ¦ Holy crap, WTF is that??? I know you don't know, but wow. That can't ¦ be a valid standards-compliant implementation. AFAIK that's the PPP negotiation. If you manually open a connection to any PPP wserver with minicom or equiv. that stuff comes back. Usually the modem returns CONNECT first, and the device is handed over to the PPP code so this doesn't get traced, but here CONNECT comes later, and then we see that PPP is correctly detected: Correct, that is the ppp negotiation Cute, so pppd will now miss the first part of the negotiation, simply because the card is too damn slow with CONNECT? That's a great experience for fast, reliable connections :) Well it really has a fast and reliable connection, but only if people will stop using it with PPP and do a cdc-ether bringup instead and run usb/ethernet connection directly to the module. ;-) But ok, that can't happen until next week or so when we've been able to publish all stuff... ;-) So, I strongly suggest to hold off playing with PPP and instead wait for some shiny glittering features coming out soon... Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Mon, 2008-10-20 at 13:26 -0400, Dan Williams wrote: On Mon, 2008-10-20 at 17:55 +0300, Tambet Ingo wrote: On Sat, Oct 18, 2008 at 2:59 PM, Rick Jones [EMAIL PROTECTED] wrote: Where are the actual dialling protocol exchanges defined - are they hard-coded? Not being able to script this bit of the connection seems to be problematic, compared to pppd. I'd really like to move to NM instead of messing with pppd, pon, poff etc. but I can't get past the first hurdle :( If you have recent enough NM (r4155 or newer), you can turn on serial debug with NM_SERIAL_DEBUG environment variable. The AT commands are hard coded and there are no plans to leave it to users to figure out. I actually converted NM_SERIAL_DEBUG into an environment variable about 2 weeks ago or something. No longer need to ask uses to rebuild, but can simply NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon and have them test out and report results. Dan Hi, I am having a similar issue on my Dell Latitude E6500 which has a Broadcom 5530 buildin hsdpa minicard. This device gives an ERROR when sent an ATZ command. Using a chat script or wvdial with a cusomized wvdial.conf file which leaves out the ATZ command, the modem works flawlessly. When using NetworkManager however it does not. Here is the trace from NetworkManager DEBUG: NetworkManager: info Activation (ttyACM0) starting connection 'Vodacom' NetworkManager: info (ttyACM0): device state change: 3 - 4 NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) started... NetworkManager: debug [1224572376.061516] nm_serial_device_open(): (ttyACM0) opening device... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: debug [1224572376.169089] nm_serial_debug(): Sending: 'ATZ E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224572376.196931] nm_serial_debug(): Got: 'ATZ E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224572376.246578] nm_serial_debug(): Got: 'ATZ E0 V1 X4 C1 +FCLASS=0 ERROR ' NetworkManager: WARN init_done(): Modem initialization failed NetworkManager: info (ttyACM0): device state change: 4 - 9 NetworkManager: debug [1224572376.247018] nm_serial_device_close(): Closing device 'ttyACM0' NetworkManager: info Marking connection 'Vodacom' invalid. NetworkManager: info Activation (ttyACM0) failed. NetworkManager: info (ttyACM0): device state change: 9 - 3 NetworkManager: info (ttyACM0): deactivating device (reason: 0). As you can see, the ATZ gives an ERROR. Is there some work around to fix this? Thanks Craig To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, Oct 21, 2008 at 10:47 AM, Craig Main [EMAIL PROTECTED] wrote: I am having a similar issue on my Dell Latitude E6500 which has a Broadcom 5530 buildin hsdpa minicard. This device gives an ERROR when sent an ATZ command. Using a chat script or wvdial with a cusomized wvdial.conf file which leaves out the ATZ command, the modem works flawlessly. When using NetworkManager however it does not. Here is the trace from NetworkManager DEBUG: NetworkManager: info Activation (ttyACM0) starting connection 'Vodacom' NetworkManager: info (ttyACM0): device state change: 3 - 4 NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) started... NetworkManager: debug [1224572376.061516] nm_serial_device_open(): (ttyACM0) opening device... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: debug [1224572376.169089] nm_serial_debug(): Sending: 'ATZ E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224572376.196931] nm_serial_debug(): Got: 'ATZ E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224572376.246578] nm_serial_debug(): Got: 'ATZ E0 V1 X4 C1 +FCLASS=0 ERROR ' The init string has more commands than (AT)Z (reset): It turns off echo (E0), sets verbose mode (V1) etc... Can you try to send only ATZ and ATZ E0 V1 to your modem (using minicom or kermit or wvdial) and see if that works? Or if it's specifically Z command that doesn't work, does this command work: ATE1 V1 X4 C1 +FCLASS=0 ? I've seen a device which doesn't like +FCLASS command. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 11:03 +0300, Tambet Ingo wrote: On Tue, Oct 21, 2008 at 10:47 AM, Craig Main [EMAIL PROTECTED] wrote: I am having a similar issue on my Dell Latitude E6500 which has a Broadcom 5530 buildin hsdpa minicard. This device gives an ERROR when sent an ATZ command. Using a chat script or wvdial with a cusomized wvdial.conf file which leaves out the ATZ command, the modem works flawlessly. When using NetworkManager however it does not. Here is the trace from NetworkManager DEBUG: NetworkManager: info Activation (ttyACM0) starting connection 'Vodacom' NetworkManager: info (ttyACM0): device state change: 3 - 4 NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) started... NetworkManager: debug [1224572376.061516] nm_serial_device_open(): (ttyACM0) opening device... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: debug [1224572376.169089] nm_serial_debug(): Sending: 'ATZ E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224572376.196931] nm_serial_debug(): Got: 'ATZ E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224572376.246578] nm_serial_debug(): Got: 'ATZ E0 V1 X4 C1 +FCLASS=0 ERROR ' The init string has more commands than (AT)Z (reset): It turns off echo (E0), sets verbose mode (V1) etc... Can you try to send only ATZ and ATZ E0 V1 to your modem (using minicom or kermit or wvdial) and see if that works? Or if it's specifically Z command that doesn't work, does this command work: ATE1 V1 X4 C1 +FCLASS=0 ? I've seen a device which doesn't like +FCLASS command. --Minicom Trace-- Welcome to minicom 2.3 OPTIONS: I18n Compiled on May 3 2008, 10:44:23. Port /dev/ttyACM0 Press CTRL-A Z for help on special keys AT S7=45 S0=0 L1 V1 X4 c1 E1 Q0 OK atz ERROR ATE1 V1 X4 C1 +FCLASS=0 OK ATZ E0 V1 ERROR --End Trace-- On a slightly related note, this modem also requires that the RF circuit gets turned on with AT+CFUN=1 Thanks Craig To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, Oct 21, 2008 at 11:17 AM, Craig Main [EMAIL PROTECTED] wrote: atz ERROR ATE1 V1 X4 C1 +FCLASS=0 OK ATZ E0 V1 ERROR Ah, so it is the reset command, thank you. We've been trying to avoid workarounds for different modems to NetworkManager so unfortunately for now, you'll need to change the init string in the code and recompile NM. I am working on another code base which has plugins (sort of drivers) to allow special handling of non-standard modems. I'd like to add support for your modem, can you please send me the output of 'lshal' (either privately or to list)? Thanks ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
Hi, The 5530 string triggers me... :-) I would believe it to be some other vendor than broadcom. It probably would be supported by the mbm plugin. The reason you get errors on atz is because it uses atf instead (an alias sort of to atz) Also, the modem comes up with cfun=4 (rf disabled) and an cfun=1 makes rf enabled. Doing a cfun=0, which modemmanager currently does as close down, will power off the modem... Tambet Ingo wrote: On Tue, Oct 21, 2008 at 11:17 AM, Craig Main [EMAIL PROTECTED] wrote: atz ERROR ATE1 V1 X4 C1 +FCLASS=0 OK ATZ E0 V1 ERROR Ah, so it is the reset command, thank you. We've been trying to avoid workarounds for different modems to NetworkManager so unfortunately for now, you'll need to change the init string in the code and recompile NM. I am working on another code base which has plugins (sort of drivers) to allow special handling of non-standard modems. I'd like to add support for your modem, can you please send me the output of 'lshal' (either privately or to list)? Thanks ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
The issue is that you have enabled unsolicited response codes. Several possable solutions 1) add +CREG=0 to your init string to disable. 2) perhaps nm should be able to parse the response string and match it to a regex expression rather than a fixed string. What is important is the the modem is registered to a network so a response of 1 or 5 would be valid Full command definition 3GPP 27007 defines +CREG Command Possible response(s) +CREG=[n] +CREG? +CREG: n,stat[,lac,ci[,AcT]] *+CME ERROR: err* +CREG=? +CREG: (list of supported ns) * * *Description* Set command controls the presentation of an unsolicited result code +CREG: stat when n=1 and there is a change in the MT network registration status, or code +CREG: stat[,lac,ci[,AcT]] when n=2 and there is a change of the network cell. Read command returns the status of result code presentation and an integer stat which shows whether the network has currently indicated the registration of the MT. Location information elements lac, ci and AcTare returned only when n=2 and MT is registered in the network. Refer subclause 9.2 for possible err values. *Defined values* n: *0*disable network registration unsolicited result code 1enable network registration unsolicited result code +CREG: stat 2enable network registration and location information unsolicited result code +CREG: stat[,lac,ci[,AcT]] stat: registration status 0not registered, MT is not currently searching a new operator to register to 1registered, home network 2not registered, but MT is currently searching a new operator to register to 3registration denied 4unknown 5registered, roaming lac: string type; two byte location area code in hexadecimal format (e.g. 00C3 equals 195 in decimal) ci: string type; four byte UTRAN/GERAN cell ID in hexadecimal format AcT: access technology of the registered network 0GSM 1GSM Compact 2UTRAN 3GSM w/EGPRS (see NOTE 1) 4UTRAN w/HSDPA (see NOTE 2) 5UTRAN w/HSUPA (see NOTE 2) 6UTRAN w/HSDPA and HSUPA (see NOTE 2) -- Stuart Ward M +44 7782325143 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 10:47 +0200, Per Hallsmark wrote: Hi, The 5530 string triggers me... :-) I would believe it to be some other vendor than broadcom. It probably would be supported by the mbm plugin. The reason you get errors on atz is because it uses atf instead (an alias sort of to atz) Also, the modem comes up with cfun=4 (rf disabled) and an cfun=1 makes rf enabled. Doing a cfun=0, which modemmanager currently does as close down, will power off the modem... My apologies, you are quite correct, it is a Dell Device: Bus 008 Device 004: ID 413c:8147 Dell Computer Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass2 Communications bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x413c Dell Computer Corp. idProduct 0x8147 bcdDevice0.00 iManufacturer 1 Dell iProduct2 Dell Wireless 5530 HSPA Mobile Broadband Minicard Device The modem defaults to cfun=4 on startup, so one needs to issue a cfun=1 before using it to connect. You are also correct about ATF working. What is the mbm plugin? Thanks Craig To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, Oct 21, 2008 at 11:50 AM, Stuart Ward [EMAIL PROTECTED] wrote: The issue is that you have enabled unsolicited response codes. Several possable solutions 1) add +CREG=0 to your init string to disable. 2) perhaps nm should be able to parse the response string and match it to a regex expression rather than a fixed string. What is important is the the modem is registered to a network so a response of 1 or 5 would be valid What? The issue is that there's a modem that does not like 'Z' (reset) command. It has nothing to do with +CREG or unsolicited response codes. We're talking about modem initialization, registration comes way later _after_ modem is initialized. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
Hello Craig, Yes, this is definitly a modem that falls into the mbm plugin. I've submitted a patch for it earlier to this list, although that one requires another NetworkManager patch (changing a bit how iface/ip_iface is used) as well as a driver which unfortunally isn't submitted yet (but will hopefully be in the nearest days!) If you can be patient until next week, I hopefully can describe howto get this modem going here. I'm dependant on the driver to be released first. It's not really a Dell device either, they oem it... ;-) Tambet, what about the plugins beeing able to specify a init string and close string? (if the standard wont work that is) /Per Craig Main wrote: On Tue, 2008-10-21 at 10:47 +0200, Per Hallsmark wrote: Hi, The 5530 string triggers me... :-) I would believe it to be some other vendor than broadcom. It probably would be supported by the mbm plugin. The reason you get errors on atz is because it uses atf instead (an alias sort of to atz) Also, the modem comes up with cfun=4 (rf disabled) and an cfun=1 makes rf enabled. Doing a cfun=0, which modemmanager currently does as close down, will power off the modem... My apologies, you are quite correct, it is a Dell Device: Bus 008 Device 004: ID 413c:8147 Dell Computer Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass2 Communications bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x413c Dell Computer Corp. idProduct 0x8147 bcdDevice0.00 iManufacturer 1 Dell iProduct2 Dell Wireless 5530 HSPA Mobile Broadband Minicard Device The modem defaults to cfun=4 on startup, so one needs to issue a cfun=1 before using it to connect. You are also correct about ATF working. What is the mbm plugin? Thanks Craig To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] and we will send you a copy of the Disclaimer. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
-- Stuart Ward M +44 7782325143 On Tue, Oct 21, 2008 at 9:58 AM, Tambet Ingo [EMAIL PROTECTED] wrote: On Tue, Oct 21, 2008 at 11:50 AM, Stuart Ward [EMAIL PROTECTED] wrote: The issue is that you have enabled unsolicited response codes. Several possable solutions 1) add +CREG=0 to your init string to disable. 2) perhaps nm should be able to parse the response string and match it to a regex expression rather than a fixed string. What is important is the the modem is registered to a network so a response of 1 or 5 would be valid What? The issue is that there's a modem that does not like 'Z' (reset) command. It has nothing to do with +CREG or unsolicited response codes. We're talking about modem initialization, registration comes way later _after_ modem is initialized. With some delicate footwork I've been able to get it past that point, but it hits another one. It responds to AT+CREG? with +CREG: 1,1, but nm-gsm-device.c only accepts 0,1. I'm not an expert on these GSM commands, and a quick google only turned up this: http://doc.trolltech.com/qtopia4.2/modememulator-network.html From this I don't see why the modem shouldn't respond 1,1, or even 2,1. I did a quick hex-edit patch to NetworkManager, changing 0,1 to 1,1, and finally it connected! This is the point I was responding to. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 11:14 +0200, Per Hallsmark wrote: Hello Craig, Yes, this is definitly a modem that falls into the mbm plugin. I've submitted a patch for it earlier to this list, although that one requires another NetworkManager patch (changing a bit how iface/ip_iface is used) as well as a driver which unfortunally isn't submitted yet (but will hopefully be in the nearest days!) If you can be patient until next week, I hopefully can describe howto get this modem going here. I'm dependant on the driver to be released first. It's not really a Dell device either, they oem it... ;-) Tambet, what about the plugins beeing able to specify a init string and close string? (if the standard wont work that is) /Per Thanks Per, let me know if you need info from me. I can wait as I have it working manually via wvdial. Regards Craig To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
--On Tuesday, October 21, 2008 11:58:58 +0300 Tambet Ingo [EMAIL PROTECTED] wrote: ¦ What? The issue is that there's a modem that does not like 'Z' (reset) ¦ command. It has nothing to do with +CREG or unsolicited response ¦ codes. We're talking about modem initialization, registration comes ¦ way later _after_ modem is initialized. There are two problems here, one from me and one from Stuart Ward. Mine started as a failure to respond to AT at all, and then moved onto a problem with +CREG responses. Stuart's seems to be mainly a problem with ATZ not supported. Hope that clears up the confusion! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, Oct 21, 2008 at 12:14 PM, Per Hallsmark [EMAIL PROTECTED] wrote: Yes, this is definitly a modem that falls into the mbm plugin. I've submitted a patch for it earlier to this list, although that one requires another NetworkManager patch (changing a bit how iface/ip_iface is used) as well as a driver which unfortunally isn't submitted yet (but will hopefully be in the nearest days!) I committed your patches from last week yesterday. Tambet, what about the plugins beeing able to specify a init string and close string? (if the standard wont work that is) Yeah, it's probably a good idea. Overriding the whole Enable() is a bit too much work if you only need to use a different init string. I'll have that later today. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 10:39 +0100, Rick Jones wrote: --On Tuesday, October 21, 2008 09:50:35 +0100 Stuart Ward [EMAIL PROTECTED] wrote: ¦ The issue is that you have enabled unsolicited response codes. Several possable solutions ¦ 1) add +CREG=0 to your init string to disable. ¦ 2) perhaps nm should be able to parse the response string and match it to a regex expression rather than a fixed string. What is important is the the modem is registered to a network so a response of 1 or 5 would be valid Thanks, that's beginning to make sense. Do I understand unsolicited response string to mean the modem can send a +CREG code at any time, not just in response to an AT query? If so then i can see why it's better not enabled. Inelegant though it is, i think NM does need a way to define custom init ( de-init?) strings externally. This has been the bane of God no. It's like adding text boxes for arbitrary command line arguments for openvpn. How are you supposed to know what goes in there? Do you just google around and find something that some random user reported worked for them and then try it? Or if that doesn't work try something else? Then you've just wasted 4 hours for something that should Just Work. We don't need to do this, because most of the differences between hardware can be handled with quirks. Adding an arbitrary enter some command strings means you've completely lost. Mobile broadband parts are a lot more standardized than Hayes-compatible modems. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 10:54 +0200, Craig Main wrote: On Tue, 2008-10-21 at 10:47 +0200, Per Hallsmark wrote: Hi, The 5530 string triggers me... :-) I would believe it to be some other vendor than broadcom. It probably would be supported by the mbm plugin. The reason you get errors on atz is because it uses atf instead (an alias sort of to atz) Also, the modem comes up with cfun=4 (rf disabled) and an cfun=1 makes rf enabled. Doing a cfun=0, which modemmanager currently does as close down, will power off the modem... My apologies, you are quite correct, it is a Dell Device: Bus 008 Device 004: ID 413c:8147 Dell Computer Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass2 Communications bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x413c Dell Computer Corp. idProduct 0x8147 bcdDevice0.00 iManufacturer 1 Dell iProduct2 Dell Wireless 5530 HSPA Mobile Broadband Minicard Device The modem defaults to cfun=4 on startup, so one needs to issue a cfun=1 before using it to connect. You are also correct about ATF working. NM SVN since late september will power on the device with AT+CFUN=1 before trying to use it. NM SVN won't try to set the device off with CFUN=0 at all. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
Dan Williams wrote: Mobile broadband parts are a lot more standardized than Hayes-compatible modems. Ehm... not sure I agree... How many different type of broadband modems does NM/MM support? (note not rebranded but *different*...) /Per ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 15:48 +0200, Per Hallsmark wrote: Dan Williams wrote: Mobile broadband parts are a lot more standardized than Hayes-compatible modems. Ehm... not sure I agree... How many different type of broadband modems does NM/MM support? (note not rebranded but *different*...) My main point with this is that the _entire_ flow is more standardized. You generally do not need extensive chat scripts, you don't have heavily customized PPP implementations or login methods based on provider, and you don't have every provider using a different network selection method for example. It used to be with 56k dialup that every single ISP had a different implementation of SLIP or PPP and required manual login, or custom login scripts to auth yourself, or some supported K56flex and others X2, etc. More direct hardware stuff will always be different, but overall the system is much simpler because everybody standardized everything else (ok, except Option with AT_OWANCALL...). Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
Dan Williams wrote: On Tue, 2008-10-21 at 15:48 +0200, Per Hallsmark wrote: Dan Williams wrote: Mobile broadband parts are a lot more standardized than Hayes-compatible modems. Ehm... not sure I agree... How many different type of broadband modems does NM/MM support? (note not rebranded but *different*...) My main point with this is that the _entire_ flow is more standardized. You generally do not need extensive chat scripts, you don't have heavily customized PPP implementations or login methods based on provider, and you don't have every provider using a different network selection method for example. It used to be with 56k dialup that every single ISP had a different implementation of SLIP or PPP and required manual login, or custom login scripts to auth yourself, or some supported K56flex and others X2, etc. Ah, well then I agree also :-) More direct hardware stuff will always be different, but overall the system is much simpler because everybody standardized everything else (ok, except Option with AT_OWANCALL...). Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Mobile Broadband - how do I trace/debug the modem initialisation?
-Original Message- From: Tambet Ingo [mailto:[EMAIL PROTECTED] Sent: Tue 10/21/2008 11:19 AM To: Per Hallsmark Cc: Main, Craig; networkmanager-list@gnome.org Subject: Re: Mobile Broadband - how do I trace/debug the modem initialisation? On Tue, Oct 21, 2008 at 12:14 PM, Per Hallsmark [EMAIL PROTECTED] wrote: Yes, this is definitly a modem that falls into the mbm plugin. I've submitted a patch for it earlier to this list, although that one requires another NetworkManager patch (changing a bit how iface/ip_iface is used) as well as a driver which unfortunally isn't submitted yet (but will hopefully be in the nearest days!) I committed your patches from last week yesterday. Tambet, what about the plugins beeing able to specify a init string and close string? (if the standard wont work that is) Yeah, it's probably a good idea. Overriding the whole Enable() is a bit too much work if you only need to use a different init string. I'll have that later today. Don't know if this will help... I patched the version that comes with Ubuntu Intrepid (0.7~~svn20081018t105859-0ubuntu1) and replaced all ATZ commands with ATF. This time things got further, here is the output from the debug trace NetworkManager: info Activation (ttyACM0) starting connection 'Vodacom' NetworkManager: info (ttyACM0): device state change: 3 - 4 NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) started... NetworkManager: debug [1224608780.039115] nm_serial_device_open(): (ttyACM0) opening device... NetworkManager: info Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: debug [1224608780.142898] nm_serial_debug(): Sending: 'ATF E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224608780.172375] nm_serial_debug(): Got: 'ATF E0 V1 X4 C1 +FCLASS=0 ' NetworkManager: debug [1224608780.201187] nm_serial_debug(): Got: 'ATF E0 V1 X4 C1 +FCLASS=0 OK ' NetworkManager: debug [1224608780.201297] nm_serial_debug(): Sending: 'AT+CPIN? ' NetworkManager: debug [1224608780.216403] nm_serial_debug(): Got: ' +CPIN: READY ' NetworkManager: debug [1224608780.218096] nm_serial_debug(): Got: ' +CPIN: READY OK ' NetworkManager: info (ttyACM0): powering up... NetworkManager: debug [1224608780.218226] nm_serial_debug(): Sending: 'AT+CFUN=1 ' NetworkManager: debug [1224608780.231653] nm_serial_debug(): Got: ' OK ' NetworkManager: debug [1224608780.231737] nm_serial_debug(): Sending: 'AT+CREG? ' NetworkManager: debug [1224608780.246281] nm_serial_debug(): Got: ' +CREG: 0,1 ' NetworkManager: debug [1224608780.247648] nm_serial_debug(): Got: ' +CREG: 0,1 OK ' NetworkManager: info Registered on Home network NetworkManager: debug [1224608780.247765] nm_serial_debug(): Sending: 'AT+COPS? ' NetworkManager: debug [1224608780.355308] nm_serial_debug(): Got: ' +COPS: 0,0,VodaCom,2 ' NetworkManager: debug [1224608780.356733] nm_serial_debug(): Got: ' +COPS: 0,0,VodaCom,2 OK ' NetworkManager: info Associated with network: +COPS: 0,0,VodaCom,2 NetworkManager: debug [1224608780.356885] nm_serial_debug(): Sending: 'AT+CGDCONT=1, IP, internet ' NetworkManager: debug [1224608780.429051] nm_serial_debug(): Got: ' OK ' NetworkManager: debug [1224608780.429255] nm_serial_debug(): Sending: 'ATD*99***1# ' NetworkManager: debug [1224608780.474146] nm_serial_debug(): Got: '~' NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: Invalid byte sequence in conversion input NetworkManager: WARN dial_done(): Dialing timed out NetworkManager: info (ttyACM0): device state change: 4 - 9 NetworkManager: debug [1224608841.000446] nm_serial_device_close(): Closing device 'ttyACM0' NetworkManager: info Marking connection 'Vodacom' invalid. NetworkManager: info Activation (ttyACM0) failed. NetworkManager: info (ttyACM0): device state change: 9 - 3 NetworkManager: info (ttyACM0): deactivating device (reason: 0). This looks much more promising, but there still seems to be an issue when it tries to dial. Here is the trace of my wvdial exchange that works... [EMAIL PROTECTED]:~$ wvdial 5530 -- Ignoring malformed input line: aler Defaults] -- WvDial: Internet dialer version 1.60 -- Cannot get information for serial port. -- Initializing modem. -- Sending: AT AT OK -- Sending: ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 OK -- Modem initialized
RE: Mobile Broadband - how do I trace/debug the modem initialisation?
On Tue, 2008-10-21 at 19:16 +0200, Main, Craig wrote: -Original Message- From: Tambet Ingo [mailto:[EMAIL PROTECTED] Sent: Tue 10/21/2008 11:19 AM To: Per Hallsmark Cc: Main, Craig; networkmanager-list@gnome.org Subject: Re: Mobile Broadband - how do I trace/debug the modem initialisation? On Tue, Oct 21, 2008 at 12:14 PM, Per Hallsmark [EMAIL PROTECTED] wrote: Yes, this is definitly a modem that falls into the mbm plugin. I've submitted a patch for it earlier to this list, although that one requires another NetworkManager patch (changing a bit how iface/ip_iface is used) as well as a driver which unfortunally isn't submitted yet (but will hopefully be in the nearest days!) I committed your patches from last week yesterday. Tambet, what about the plugins beeing able to specify a init string and close string? (if the standard wont work that is) Yeah, it's probably a good idea. Overriding the whole Enable() is a bit too much work if you only need to use a different init string. I'll have that later today. Don't know if this will help... I patched the version that comes with Ubuntu Intrepid (0.7~~svn20081018t105859-0ubuntu1) and replaced all ATZ commands with ATF. This time things got further, here is the output from the debug trace ... This looks much more promising, but there still seems to be an issue when it tries to dial. Here is the trace of my wvdial exchange that works... [EMAIL PROTECTED]:~$ wvdial 5530 -- Ignoring malformed input line: aler Defaults] -- WvDial: Internet dialer version 1.60 -- Cannot get information for serial port. -- Initializing modem. -- Sending: AT AT OK -- Sending: ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 OK -- Modem initialized. -- Sending: ATDT*99***1# -- Waiting for carrier. ATDT*99***1# [EMAIL PROTECTED] }9}#}%B#}%}(}}' } } } }%}mG!;J[1d]~ Holy crap, WTF is that??? I know you don't know, but wow. That can't be a valid standards-compliant implementation. Dan CONNECT -- Carrier detected. Waiting for prompt. [EMAIL PROTECTED]} }9}#}%B#}%}(}}' } } } }%}mG!;[06]p~ -- PPP negotiation detected. -- Starting pppd at Tue Oct 21 19:10:07 2008 -- Warning: Could not modify /etc/ppp/pap-secrets: Permission denied -- -- PAP (Password Authentication Protocol) may be flaky. -- Warning: Could not modify /etc/ppp/chap-secrets: Permission denied -- -- CHAP (Challenge Handshake) may be flaky. -- Pid of pppd: 27901 Thanks Craig To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
--On Tuesday, October 21, 2008 09:21:36 -0400 Dan Williams [EMAIL PROTECTED] wrote: ¦ Inelegant though it is, i think NM does need a way to define custom ¦ init ( de-init?) strings externally. This has been the bane of ¦ ¦ God no. It's like adding text boxes for arbitrary command line ¦ arguments for openvpn. How are you supposed to know what goes in there? ¦ Do you just google around and find something that some random user ¦ reported worked for them and then try it? Or if that doesn't work try ¦ something else? Then you've just wasted 4 hours for something that ¦ should Just Work. We don't need to do this, because most of the ¦ differences between hardware can be handled with quirks. Adding an ¦ arbitrary enter some command strings means you've completely lost. ¦ Mobile broadband parts are a lot more standardized than ¦ Hayes-compatible modems. i'm not saying it should be an up-front configuration for the user, but neither should it be embedded in C source. I agree that the general protocol has been well-established, but there are clearly issues with initialisation, as this thread has shown (for 2 cases). Even if these cases are dealt with in source, what happens when a future modem needs something else a bit different? Do you change the init string in source, then regression test against every modem that worked before to make sure nothing's broken, then wait for it to be pushed out to the different distros? It seems to me an external resource file, pre-built for all known cases, but editable by expert users and/or quickly updateable independently of the whole package, is much more maintainable. It's how I'd do it anyway ... Cheers, Rick ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: Mobile Broadband - how do I trace/debug the modem initialisation?
--On Tuesday, October 21, 2008 14:08:25 -0400 Dan Williams [EMAIL PROTECTED] wrote: ¦ On Tue, 2008-10-21 at 19:16 +0200, Main, Craig wrote: .. ¦ -- Modem initialized. ¦ -- Sending: ATDT*99***1# ¦ -- Waiting for carrier. ¦ ATDT*99***1# ¦ [EMAIL PROTECTED] }9}#}%B#}%}(}}' } } } }%}mG!;J[1d]~ ¦ ¦ Holy crap, WTF is that??? I know you don't know, but wow. That can't ¦ be a valid standards-compliant implementation. AFAIK that's the PPP negotiation. If you manually open a connection to any PPP wserver with minicom or equiv. that stuff comes back. Usually the modem returns CONNECT first, and the device is handed over to the PPP code so this doesn't get traced, but here CONNECT comes later, and then we see that PPP is correctly detected: ¦ CONNECT ¦ -- Carrier detected. Waiting for prompt. ¦ [EMAIL PROTECTED]} }9}#}%B#}%}(}}' } } } }%}mG!;[06]p~ ¦ -- PPP negotiation detected. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Sat, Oct 18, 2008 at 2:59 PM, Rick Jones [EMAIL PROTECTED] wrote: Where are the actual dialling protocol exchanges defined - are they hard-coded? Not being able to script this bit of the connection seems to be problematic, compared to pppd. I'd really like to move to NM instead of messing with pppd, pon, poff etc. but I can't get past the first hurdle :( If you have recent enough NM (r4155 or newer), you can turn on serial debug with NM_SERIAL_DEBUG environment variable. The AT commands are hard coded and there are no plans to leave it to users to figure out. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Sat, 2008-10-18 at 12:59 +0100, Rick Jones wrote: I have NM 0.7 running on Ubuntu - works fine with LAN wireless, but I can't get it to talk to a GPRS modem properly. Here's the scenario: The device is a Palm Treo with Mobile Stream's USB Modem installed. This offers a standard modem interface on the USB port, and I can make this work fine using pppd with a conventional chat script. All it needs is AT to kick it off, then AT+CGDCONT=1. etc., all standard stuff. NM recognises the modem when it's connected, and allows me to setup a Mobile Broadband entry. But when I try to connect I just get connection failed. Looking at the logs I get: Activation (ttyACM0) Stage 1 of 5 (Device Prepare) complete init_done(): Modem initialization timed out (ttyACM0): device state change: 4 - 9 [various failure / closedown messages ] It seems to get no response from the modem. This doesn't make sense, as I can minicom to ttyACM0 and manually go through the AT dialling sequence! It depends on what that sequence is, and whether the modem actually does GSM standard sequences... What does AT+GCAP? and ATI return for your device? I've looked at 10-modem.fdi, and I assume it's using the generic GPRS entry at the bottom. I've tried adding an entry with explicit USB IDs but this doesn't make any difference. Using lsusb -v, the device reports that it supports V25ter, which I guess is covered by V250 in the fdi file. With recent SVN, become root, then: NM_SERIAL_DEBUG=1 NM_PPP_DEBUG=1 /usr/sbin/NetworkManager --no-daemon and try to connect. Please respond with the output that NM returns, removing any PIN/PUK and such of course :) I'm quite curious. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Mon, 2008-10-20 at 17:12 +0100, Rick Jones wrote: --On Monday, October 20, 2008 17:55:12 +0300 Tambet Ingo [EMAIL PROTECTED] wrote: ¦ If you have recent enough NM (r4155 or newer), you can turn on serial ¦ debug with NM_SERIAL_DEBUG environment variable. The AT commands are ¦ hard coded and there are no plans to leave it to users to figure out. Thanks, that worked, and confirmed what i'd begun to suspect. I've also had a rummage in the source code to see what it's doing. With careful use of minicom it turns out that the modem software in the Palm device doesn't respond to the first AT command, but after a second command it returns two OK responses - the first response gets delayed for some reason. NM doesn't appear to allow any retries in its exchanges, unlike chat scripts which can deal with this kind of thing. So it's a bug in the Palm - I'll have to chase it up with the authors. Probably; NM does retries for some commands that time out. Whats the command that times out for you, the first ATZ E0 or something? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
On Mon, 2008-10-20 at 17:55 +0300, Tambet Ingo wrote: On Sat, Oct 18, 2008 at 2:59 PM, Rick Jones [EMAIL PROTECTED] wrote: Where are the actual dialling protocol exchanges defined - are they hard-coded? Not being able to script this bit of the connection seems to be problematic, compared to pppd. I'd really like to move to NM instead of messing with pppd, pon, poff etc. but I can't get past the first hurdle :( If you have recent enough NM (r4155 or newer), you can turn on serial debug with NM_SERIAL_DEBUG environment variable. The AT commands are hard coded and there are no plans to leave it to users to figure out. I actually converted NM_SERIAL_DEBUG into an environment variable about 2 weeks ago or something. No longer need to ask uses to rebuild, but can simply NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon and have them test out and report results. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Mobile Broadband - how do I trace/debug the modem initialisation?
--On Monday, October 20, 2008 13:25:37 -0400 Dan Williams [EMAIL PROTECTED] wrote: ¦ ¦ So it's a bug in the Palm - I'll have to chase it up with the authors. ¦ ¦ Probably; NM does retries for some commands that time out. Whats the ¦ command that times out for you, the first ATZ E0 or something? The first AT-anything times out, it needs to receive a 2nd to prompt a response (and then returns both responses). With some delicate footwork I've been able to get it past that point, but it hits another one. It responds to AT+CREG? with +CREG: 1,1, but nm-gsm-device.c only accepts 0,1. I'm not an expert on these GSM commands, and a quick google only turned up this: http://doc.trolltech.com/qtopia4.2/modememulator-network.html From this I don't see why the modem shouldn't respond 1,1, or even 2,1. I did a quick hex-edit patch to NetworkManager, changing 0,1 to 1,1, and finally it connected! I'd put the initial timeout problem down to the Palm software, but is the 1,1 response actually incorrect, or should NM be more tolerant? Rick ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
