Bug 593469

Summary: Qualcomm 3G modem with Gobi driver does not connect
Product: [Fedora] Fedora Reporter: Dan <dcarruth2>
Component: ModemManagerAssignee: Dan Williams <dcbw>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: dcbw
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-22 03:58:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dan 2010-05-18 21:11:01 UTC
Description of problem:The qualcomm 3G modem in my AAO ZG8 that uses the gobi driver connects to ttyUSB0 but does not load in Network Manager so that it can be accessed. If I boot in to Windows XP first than reboot to F13 it will load and work through Network Manager.

Version-Release number of selected component (if applicable):
modemManager 0.3-13.git20100507.fc13
NetworkManager 0.8.1-0.1.git20100510.fc13
How reproducible:Turn off modem with kill switch, then turn back on there will be no 3G modem listed in network manager. To make work boot in to windows XP load 3G modem and pickup network then reboot in to F13.

Steps to Reproduce:
1.Load in windows XP reboot to F13 modem works.
2.Boot F13 turn on modem log view shows qualcomm usb modem converter attached to ttyUSB0 no connection in network manager.
Actual results:modem manager loads Gobi driver but does not make connection.

Expected results: To load in Network-manager so can make connect to mobile broadband network.

Additional info:

Comment 1 Dan Williams 2010-05-20 07:04:13 UTC
Have you installed the gobi_loader program, the udev rules, and the firmware necessary to load the gobi's firmware?

Comment 2 Dan 2010-05-22 03:58:23 UTC
I now have a working Qualcom modem in F13, just needed the gobi_loader and firmware. Now works like it should, and I'll now close this bug report.