some more research: /dev/ttyUSB2: AT+CGDCONT=1, "IP", "ISP.CINGULAR" OK
AT+CGDCONT=1,"IP","ISP.CINGULAR" OK /dev/ttyUSB0: AT+CGDCONT=1, "IP", "ISP.CINGULAR" ERROR AT+CGDCONT=1,"IP","ISP.CINGULAR" OK set_apn() in nm-gsm-device.c (#216) executes that command with white spaces, which would work for /dev/ttyUSB2 but not for /dev/ttyUSB0. Removing those white spaces in set_apn() fixes the problem, however, I am not sure if the white spaces are required for something else / some other devices. Oct 17 23:01:27 X31 NetworkManager: <info> (ttyUSB0): powering up... Oct 17 23:01:27 X31 NetworkManager: <info> Registered on Home network Oct 17 23:01:27 X31 NetworkManager: <info> Associated with network: +COPS: 0,0,"",2 Oct 17 23:01:27 X31 NetworkManager: <info> Connected, Woo! with the rest working just fine. However, the root cause of the problem is that /dev/ttyUSB0 is used and not /dev/ttyUSB2, which would be the correct device. As HAL is telling us that /dev/ttyUSB0 is the modem and not /dev/ttyUSB2 I assume either this is a HAL bug or something else I don't know/understand. For now I've attached a patch changing the AT command in nm-gsm-device.c ** Attachment added: "patch.gz" http://launchpadlibrarian.net/18655693/patch.gz -- NM 0.7 does not set APN for AT&T 3G connection https://bugs.launchpad.net/bugs/282207 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
