Description of problem: Modem that works perfectly in F14 isn't even seen by Network Manager in F16. I properly configured the modem in nm-connection-editor but it never shows up as a selectable device in Network Manager. Version-Release number of selected component (if applicable): I suspect it's usb_modeswitch, but I'm not sure. How reproducible: plug in modem and wait Steps to Reproduce: 1. 2. 3. Actual results: Nov 30 09:16:33 box2 kernel: [ 142.052036] usb 5-1: new full speed USB device number 7 using ohci_hcd Nov 30 09:16:33 box2 kernel: [ 142.200613] usb 5-1: New USB device found, idVendor=1c9e, idProduct=1001 Nov 30 09:16:33 box2 kernel: [ 142.200623] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 30 09:16:33 box2 kernel: [ 142.200629] usb 5-1: Product: USB MMC Storage Nov 30 09:16:33 box2 kernel: [ 142.200633] usb 5-1: Manufacturer: USB Modem Nov 30 09:16:33 box2 kernel: [ 142.200637] usb 5-1: SerialNumber: 000000000002 Nov 30 09:16:33 box2 mtp-probe: checking bus 5, device 7: "/sys/devices/pci0000:00/0000:00:13.0/usb5/5-1" Nov 30 09:16:33 box2 mtp-probe: bus: 5, device: 7 was not an MTP device Nov 30 09:16:34 box2 logger: usb_modeswitch: using overriding config file /etc/usb_modeswitch.d/1c9e:1001; make sure this is intended Nov 30 09:16:34 box2 logger: usb_modeswitch: please report any new or corrected settings; otherwise, check for outdated files Nov 30 09:16:34 box2 usb_modeswitch: switching 1c9e:1001 (USB Modem: USB MMC Storage) Nov 30 09:16:34 box2 kernel: [ 143.028816] usb 5-1: USB disconnect, device number 7 Nov 30 09:16:35 box2 kernel: [ 144.462046] usb 5-1: new full speed USB device number 8 using ohci_hcd Nov 30 09:16:35 box2 kernel: [ 144.608585] usb 5-1: New USB device found, idVendor=1c9e, idProduct=6061 Nov 30 09:16:35 box2 kernel: [ 144.608594] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Nov 30 09:16:35 box2 kernel: [ 144.608600] usb 5-1: Product: USB Modem Nov 30 09:16:35 box2 kernel: [ 144.608605] usb 5-1: Manufacturer: USB Modem Nov 30 09:16:36 box2 usb_modeswitch: switched to 1c9e:6061 (USB Modem: USB Modem) Nov 30 09:16:36 box2 kernel: [ 145.286046] usbcore: registered new interface driver uas Nov 30 09:16:36 box2 kernel: [ 145.290480] Initializing USB Mass Storage driver... Nov 30 09:16:36 box2 kernel: [ 145.290654] usbcore: registered new interface driver usb-storage Nov 30 09:16:36 box2 kernel: [ 145.290658] USB Mass Storage support registered. Nov 30 09:16:36 box2 mtp-probe: checking bus 5, device 8: "/sys/devices/pci0000:00/0000:00:13.0/usb5/5-1" Nov 30 09:16:36 box2 mtp-probe: bus: 5, device: 8 was not an MTP device Expected results: Additional info: Notice that Network Manager doesn't get involved. This may be a timing issue as it looks like the kernel sees the device as a drive. usb_modeswitch is properly detecting the 1c9e:1001 and converting to 1c9e:6061 but then the ball gets dropped.
I Have now tried this under 3 separate installs, Xfce, KDE, and Gnome 3. None of them allow the modem to work. I tested another brand of modem (from a friend) and got a connection. I believe the problem is in Network Manager not seeing my modem as a viable device. My modem that is NOT working identifies itself via 1c9e:1001 -> 1c9e:6061 conversion via usb_modeswitch. The conversion is working.
This bug is preventing me from migrating several boxes from F14 to F16, as we can't function without an Internet connection. As F14 is now end of life, I'd like to move on. My options are to go buy new modems that don't suffer from this bug or wait for a fix. Can anyone suggest a time frame for when this bug might get some attention? Thank You.
*** Bug 757439 has been marked as a duplicate of this bug. ***
It looks like usb_modeswitch properly switched the device, but didn't load the modem driver. There's a similar bug (though for other modem) indicating that older usb_modeswitch work: bug 754904 Could you try older versions of usb_modeswitch? Please report: $ rpm -q usb_modeswitch $ rpm -q usb_modeswitch-data $ rpm -q kernel As a workaround, you could load the driver manually: # modprobe option # echo "1c9e 6061" > /sys/bus/usb-serial/drivers/option1/new_id
this is occurring on both 32 & 64 bit systems. Here is the requested data from a 64 bit box root@box2 ~# rpm -q usb_modeswitch usb_modeswitch-data kernel usb_modeswitch-1.2.0-1.fc16.x86_64 usb_modeswitch-data-20111023-1.fc16.noarch kernel-3.1.2-1.fc16.x86_64 kernel-3.1.4-1.fc16.x86_64 kernel-3.1.5-2.fc16.x86_64 I'll get data from a 32 bit box and try the manual method later today.
Manually loading option driver and echo works on 64 bit box! Will test 32 bit box later today. How do I load the older version of usb_modeswitch? Is there a generic method for loading a -1 release or do I have to specifically erase the current, find an older one and load it manually? Thanks so much for giving me a way to migrate from F14 to F16.
Kernel 3.2.3-2.fc16.x86_64 breaks the work around presented here. The previous kernel 3.2.2-1.fc16.x86_64 works just fine. I've been waiting for this bug to get fixed, and have been using the # modprobe option # echo "1c9e 6061" > /sys/bus/usb-serial/drivers/option1/new_id method to get my modem to function. The patches I applied this morning caused this "trick" to no longer work. Reverting back to the previous kernel again allows my modem to function.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.