ndiswrapper can scan for SSIDs but cannot connect on any kernel newer than 2.6.34-5.14
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Leann Ogasawara | ||
ndiswrapper (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Even though the ndiswrapper package was just fixed to not complain about 2.6.35 kernels, this problem persists with my Intel 3945abg.
The ndiswrapper module will load and if fed the proper XP drivers, will scan for networks without any problems.
However, as soon as I try to connect to a network (unsecured or secured), ndiswrapper can never finish the connection. If secured, I keep getting asked for the SSID password. Doesn't matter if I use Network Manager, Wicd, or command line.
This does not affect any 2.6.34 kernels that I've used so far.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ndiswrapper-common 1.56-2
ProcVersionSign
Uname: Linux 2.6.35-13-generic i686
Architecture: i386
Date: Thu Aug 5 06:17:19 2010
Dependencies:
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ndiswrapper
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in ndiswrapper (Ubuntu): | |
status: | Fix Committed → Incomplete |
status: | Incomplete → Confirmed |
Changed in linux (Ubuntu): | |
assignee: | nobody → Leann Ogasawara (leannogasawara) |
status: | New → In Progress |
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Committed |
> Even though the ndiswrapper package was just fixed to not complain
> about 2.6.35 kernels, this problem persists with my Intel 3945abg.
I don't support ndiswrapper on cards where native drivers (iwl3945) are available; as ndiswrapper should only be a temporary solution and not used in long-term situations (i.e. users should buy compatible hardware).
You are free to find the problem yourself though, and provide a patch (take a look at dmesg, are there errors?). If you do so, you should forward the patch to upstream, as I don't communicate with them (the project appears to be dead anyway).