Bug 767180

Summary: 3g modem doesn't switch in high power mode when enabling mobile broadband
Product: [Fedora] Fedora Reporter: pascal <pascal>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: dcbw, jklimes
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: 2013-02-13 13:49:48 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 pascal 2011-12-13 13:55:41 UTC
Description of problem:
Novatel Wireless HSDPA Modem doesn't get switched in high power mode before setting up the mobile broadband connection to the telco.
In ubuntu toshiba-acpi.ko provides toshset the ability to switch modem in high power mode. No such thing in Fedora.

Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1.By a toshiba laptop with 3g modem
2.Try to connect to telcom
3.
  
Actual results:
No connection

Expected results:
Have a connection to telco

Additional info:

Dec 13 14:50:58 pascal-laptop dbus-daemon[932]: modem-manager[968]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled -> enabling)
Dec 13 14:50:58 pascal-laptop modem-manager[968]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled -> enabling)
Dec 13 14:50:58 pascal-laptop modem-manager[968]: <info>  (ttyUSB3) opening serial port...
Dec 13 14:50:58 pascal-laptop dbus-daemon[932]: modem-manager[968]: <info>  (ttyUSB3) opening serial port...
Dec 13 14:50:58 pascal-laptop modem-manager[968]: Invalid error code: 303
Dec 13 14:50:58 pascal-laptop dbus-daemon[932]: modem-manager[968]: Invalid error code: 303

Comment 1 Jirka Klimes 2012-02-01 07:58:58 UTC
Would you grab output of commands
$ lsusb -v
$ dmesg

Also, detailed logs would help to debug the issue:
http://live.gnome.org/NetworkManager/Debugging#NM_3G_08_09

Comment 2 Fedora End Of Life 2013-01-16 13:08:41 UTC
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

Comment 3 Fedora End Of Life 2013-02-13 13:49:51 UTC
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.