Bug 492709
| Summary: | sierra internal wwan and bluetooth card not detected in 2.6.29 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kevin R. Page <redhat-bugzilla> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 10 | CC: | kernel-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-12-18 09:07:57 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: | |||
|
Description
Kevin R. Page
2009-03-28 16:45:11 UTC
I've just noticed that my bluetooth module isn't detected either. It's internal, but I have a feeling this might be on the same daughterboard as wwan. I think it attaches over USB (thinkwiki is down, I'm afraid). Can you post the output of the lsusb command from that system? 2.6.27.12-170.2.5.fc10.i686: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 003: ID 1199:6813 Sierra Wireless, Inc. Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 003: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 2.6.29-3.fc10.i686: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 003: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub What's a little odd is that when I grabbed that last lsusb I noticed I had a detected bluetooth card. Yet right now (and on other occasions I guess, given comment #1, precluding madness), same kernel (2.6.29-3.fc10.i686): Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub No bluetooth. A race somewhere, perhaps? Bug still present in kernel-2.6.29.1-30.fc10 from updates-testing. No wwan present (or showing in lsusb) and no bluetooth (on this boot, at least). Can you attach /var/log/dmesg after booting working and broken kernels? Created attachment 340807 [details]
dmesg for 2.6.29.1-30.fc10.i686 (no bluetooth or wwan)
Created attachment 340808 [details]
dmesg for 2.6.27.12-170.2.5.fc10.i686 (bluetooth and wwan detected)
Created attachment 340810 [details]
dmesg 2.6.27.12-170.2.5.fc10.i686 (with NetworkManager kick)
With earlier kernels/NetworkManager versions (no longer installed) NM always detected the wwan module straight away. However with 2.6.27.12-170.2.5.fc10.i686 I have to:
modprobe -r sierra
modprobe sierra
service NetworkManager restart
for the wwan module to appear in NetworkManager. This is just to get it to appear in NM - the wwan and bluetooth are detected anyway (as per lsusb), but something must've changed somewhere, so I've included this just in case it's relevant.
The dmesg is the same as the earlier one for 2.6.27.12-170.2.5.fc10, but with the sierra modprobe and NM restart on the end.
Looking good so far with 2.6.29.1-42.fc10.i686. This should also be fixed in the latest 2.6.27 F-10 kernels. Running F11 now so can't check F10 - safe to close this bug, I'd have thought? This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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 Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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. |