Bug 797429 - Intel wireless 3945 still uses iwl3945-driver instead of newer iwlwifi
Summary: Intel wireless 3945 still uses iwl3945-driver instead of newer iwlwifi
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stanislaw Gruszka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-25 19:31 UTC by Stefan Neufeind
Modified: 2012-02-26 14:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-26 14:04:45 UTC
Type: ---


Attachments (Terms of Use)

Description Stefan Neufeind 2012-02-25 19:31:13 UTC
What I found on the net is that iwl3945 seems to be "legacy" now and iwlwifi should be able to support that hardware still. However using kernel-3.2.7-1.fc16.x86_64 it still loads the iwl3945-module for me. Manually unloading that and trying to load iwlwifi doesn't seem to recognise that network-interface. I saw that device listed in the udev-rules - but didn't see any driver-name linked to it (which I might want to change to iwlwifi to try it out).

Is there a reason why still that legacy-driver is used, which is also declared legacy on Intel's webpages?

Comment 1 Stanislaw Gruszka 2012-02-26 13:36:35 UTC
Yes, iwlwifi do not support 3945 and 4965. Intel split one iwlwifi driver into two drivers iwlegacy and iwlagn (former renamed lately again to iwlwifi). They do not want to maintain/support 3945 and 4965 any longer.

Do you have any problems with iwl3945/iwlegacy ?

Comment 2 Stefan Neufeind 2012-02-26 14:04:45 UTC
Okay sorry, my fault then. I read that those two chipsets were also part of iwlwifi. But it appears it was split out some time in the late 2.x-series into this iwlegacy-driver.

I was hoping to get hostap to work because of mac80211/nl80211. And it seems that iwlwifi might be able to work with hostap. Unfortunately with the legacy-driver I can't seem to get that working. The driver itself does not support AP-mode but I read that through the generic mac80211-support it might be possible that a "software-solution" for creating an AP might be available.

Hmm, then I don't think I'll ever have luck with those "legacy"-drivers, right? :-(


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