Bug 1024551 - iwl3945 and Sierra MC8755 shows as "hardware disabled", unable re-enable after disabling from NetworkManager
Summary: iwl3945 and Sierra MC8755 shows as "hardware disabled", unable re-enable afte...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 19
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-29 22:32 UTC by Jouni Kivilahti
Modified: 2015-02-17 18:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 18:57:09 UTC
Type: Bug


Attachments (Terms of Use)
Output of dmidecode (10.41 KB, text/plain)
2013-10-29 22:32 UTC, Jouni Kivilahti
no flags Details
Output of dmesg after fiddling around (138.84 KB, text/plain)
2013-10-29 22:34 UTC, Jouni Kivilahti
no flags Details

Description Jouni Kivilahti 2013-10-29 22:32:09 UTC
Created attachment 817196 [details]
Output of dmidecode

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Disable WIFI or mobile broadband from NetworkManager
2. 
3.

Actual results:

NetworkManager says: "hardware disabled" for WIFI and "unavailable" for 3g card.

Expected results:

Ability to re-enable from NetworkManager menu.

Additional info:

hardware: Fujitsu Amilo Pro v3525

I managed to get the wifi working by:

rmmod iwl3945
modprobe iwl3945
service NetworkManager restart

But.. this did not quite work second time when i tried to redo these steps. 

Weird thing, sometimes when i stop the NetworkManager service, I can get the 3g card visible again.

Comment 1 Jouni Kivilahti 2013-10-29 22:34:16 UTC
Created attachment 817197 [details]
Output of dmesg after fiddling around

Comment 2 Jouni Kivilahti 2013-10-29 22:42:27 UTC
I cannot find any logic for this, now when I stopped the NetworkManager service, the WIFI reappeared and cannot enable the 3g card.

Comment: I was unaware that the NetworkService restarts when trying to stop it. Systemd is not very familiar for me.

Comment 3 Jouni Kivilahti 2013-10-29 22:43:33 UTC
Correction to previous: NetworkManager, NOT NetworkService.

Comment 4 Fedora End Of Life 2015-01-09 20:24:14 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 5 Fedora End Of Life 2015-02-17 18:57:09 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.