Bug 526086
| Summary: | Network Manager doesn't show 3G Huawei e156g modem. Cannot connect to the 3G network. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Piotr Czekalski <piotr.czekalski> | ||||||
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 11 | CC: | dcbw, piotr.czekalski | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-05-04 19:23:53 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 362922 [details]
Messages log.
Watch the last few lines, please. AFAIK modem is recognized (but as E220 instead of e156g) and connected as ttyUSB0 and ttyUSB1, anyway during Windows XP detection there are four devices recognized (two of them may be not recognized / connected USB drives as stated in the last two lines of the message log).
Please try this update: NetworkManager-0.7.1.998-1.fc11 If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager mobile-broadband-provider-info'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10696 It has fixes for Huawei devices. If you still have problems, please attach /var/log/messages when you see the problem. However, I've heard of one case where the modem was found by the drivers but didn't work, and usb_modeswitch made the modem work after that. So please try using usb_modeswitch as well. Thanks! Hell Dan! Thanks for your reply. I've installed NM as figured above but still no luck. I've also installed and tried USB_modeswitch and I've found that modem works in 'modem' mode instead of 'storage' mode that seems to be perfectly OK. I've forced reset on the device plenty of times but still no impact on NM - there is no modem to choose when creating a new 3G connection (no device in the dropdown list). Any further help would be really appreciated. Thanks in advance, Piotr Ok, in this case we get to debug a bit further. Open up this file:
/lib/udev/rules.d/77-nm-probe-modem-capabilities.rules
and you'll see a line like this:
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="?*", ATTRS{idProduct}=="?*", IMPORT{program}="nm-modem-probe --vid 0x$attr{idVendor} --pid 0x$attr{idProduct} --usb-interface $env{NM_MODEM_USB_INTERFACE_NUMBER} --driver $env{NM_MODEM_DRIVER} --delay 1000 --timeout 5000 --export $tempnode", GOTO="nm_modem_probe_end"
(it'll all be on one line)
right after the "--export", add the arguments "--verbose --log /tmp/probe.log" so that the whole line looks like this:
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="?*", ATTRS{idProduct}=="?*", IMPORT{program}="nm-modem-probe --vid 0x$attr{idVendor} --pid 0x$attr{idProduct} --usb-interface $env{NM_MODEM_USB_INTERFACE_NUMBER} --driver $env{NM_MODEM_DRIVER} --delay 1000 --timeout 5000 --export --verbose --log /tmp/probe.log $tempnode", GOTO="nm_modem_probe_end"
Then save it (again make sure it's all on one line), unplug your modem, and replug it. Then wait about 30 seconds, and attach /tmp/probe.log to this bug report.
Also, are you *sure* you have the SIM correctly inserted? I have an E160G and the first time I used it, I got the SIM wrong side up. The modem didn't like that.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Closing as no response from the reporter has been received in 5 months. |
Created attachment 362921 [details] List of usb devices. Description of problem: 3G Huawei e156g modem do not show in Network Manager in the installed distro but works out of the box with LiveCD distro. Version-Release number of selected component (if applicable): Aplet NetworkManager 0.7.1 How reproducible: Always Steps to Reproduce: 1. Connect Huawei e156g modem to the USB 2. View NM connections (none) 3. Try to add a new boradband connection -> no device occurs Actual results: Cannot connect to the 3G network on other than LiveCD distros. Expected results: Possibility to connect to the 3G network. Additional info: As googled around found some people to have similar problem with other 3G modems. AFAIK this is not the usb_modeswith problem because modem is detected (lsusb) and properly recognized (dmesg) as ttyUSB0 and ttyUSB1 devices.