After switching it is possible to get the modem detected by network- manager by adding information to a HAL FDI file. I created one called 20 -wwan-quirk.fdi in /usr/share/hal/fdi/information/20thirdparty but it could probably be integrated into 10-modem.fdi.
The kernel detects three modems with usb addresses 1.0, 1.1, 1.3 and creates ttys for each (/dev/ttyUSB[0-2]). However, no matter which interface is picked in 20-wwan-quirk (0,1,3) the modem fails to initialise. This sequence is the same for each ttyUSB0, ttyUSB1, ttyUSB2. Finally, I can't chat or screen to any of the /dev/ttyUSB[0-2] - it hangs and does nothing. Dec 21 12:50:06 t7200 NetworkManager: <info> Activation (ttyUSB1) starting connection '3' Dec 21 12:50:06 t7200 NetworkManager: <info> (ttyUSB1): device state change: 3 -> 4 Dec 21 12:50:06 t7200 NetworkManager: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled... Dec 21 12:50:06 t7200 NetworkManager: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started... Dec 21 12:50:06 t7200 NetworkManager: <debug> [1229863806.250497] nm_serial_device_open(): (ttyUSB1) opening device... Dec 21 12:50:06 t7200 NetworkManager: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete. Dec 21 12:50:06 t7200 NetworkManager: <WARN> init_done(): Modem initialization failed Dec 21 12:50:06 t7200 NetworkManager: <info> (ttyUSB1): device state change: 4 -> 9 Dec 21 12:50:06 t7200 NetworkManager: <debug> [1229863806.393000] nm_serial_device_close(): Closing device 'ttyUSB1' Dec 21 12:50:06 t7200 NetworkManager: <info> Marking connection '3' invalid. Dec 21 12:50:06 t7200 NetworkManager: <info> Activation (ttyUSB1) failed. Dec 21 12:50:06 t7200 NetworkManager: <info> (ttyUSB1): device state change: 9 -> 3 Dec 21 12:50:06 t7200 NetworkManager: <info> (ttyUSB1): deactivating device (reason: 0). ** Attachment added: "20-wwan-quirk.fdi" http://launchpadlibrarian.net/20614638/20-wwan-quirk.fdi -- ZTE MF627 USB 3G modem not detected by NM0.7 https://bugs.launchpad.net/bugs/310025 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
