OK, problem solved. I have performed full research, readed other similiar bugs, searched over windows driver to this kind of device and this is what I found:
All Sagem cellphones share the same modem chip and share the same driver (I didn't found any unusual drivers for those cellphones). Some USB PID and MI with names (vendor is of course 0x079b): PID: 0030 = USB Mobile Communication Device PID: 002F MI: 00 = USB Mobile Pseudo CDC Modem PID: 002F MI: 01 = USB Mobile Pseudo CDC Trace PID: 002F MI: 02 = USB Mobile Pseudo CDC Chimera PID: 005D MI: 01 = USB Mobile Mass Storage Pseudo CDC Trace PID: 005D MI: 02 = USB Mobile Mass Storage Pseudo CDC Chimera PID: 0042 MI: 02 = USB Mobile Video Pseudo CDC Trace Sagem in modem mode is identified as device of PID 0030, but is not correctly recognized by hal. After lurking into hal fdi files (and readed a lot's of documentation and other bugs) I have added file 10-sagem.fdi. After restart of hal and when connected cellphone - tada - it has been correctly detected and I have established valid internet connection thru GSM network. Name in network-manager is not amazing, but nothing relays on it. It would be nice if somebody merge those changes with distribution (and usb.ids files), to have somebody amazed like I was first time when I connected cellphone with usb-cable to my Ubuntu driven laptop. ** Attachment added: "10-sagem.fdi" http://launchpadlibrarian.net/20964412/10-sagem.fdi -- Sagem my411x not detected as modem when connected by USB cable https://bugs.launchpad.net/bugs/313333 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
