Latest upstream release: 20121109 Current version in Fedora Rawhide: 20120815 URL: http://www.draisberghof.de/usb_modeswitch/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
20121109: Added devices: Nokia CS-7M-01, LG LUU-2110TI, LG VL600, LG L-03D LTE/3G, Option Beemo/Pantech P4200 LTE, Vodafone/Huawei K3772, Vodafone/Huawei K3773, Huawei E171, Huawei E173s, Huawei E177, Huawei EC156, Huawei E372u-8, Huawei E392u-12, Huawei ET8282, Huawei ET127, ZTE-T A356, ZTE MF192+, ZTE MF190J, Vodafone/ZTE K3770-Z, T-Mobile/ZTE MF591, Aircard 901, ETCOM E300, Archos G9 3G Key, Onda MW833UP, Onda MW836UP-K, Onda MW875UP, Franklin Wireless U600 (Thanks for the contribution of most new devices goes to Nicolas Carrier from the Parrot company) Preparation for future MBIM devices: new "NoMBIMCheck" config parameter, change in modem rules (match devices, not interfaces), best used with usb_modeswitch 1.2.5 and up
usb_modeswitch-data-20121109-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/usb_modeswitch-data-20121109-1.fc18
usb_modeswitch-data-20121109-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/usb_modeswitch-data-20121109-1.fc17
Package usb_modeswitch-data-20121109-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing usb_modeswitch-data-20121109-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-18104/usb_modeswitch-data-20121109-1.fc18 then log in and leave karma (feedback).
usb_modeswitch-data-20121109-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.