Wifi using ndiswrapper works only after suspend
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ndiswrapper (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: madwifi-tools
I have an LG LGR40 (R-400M) laptop with a network card that I can only get to work with ndiswrapper using the driver net5211. In Hardy Heron, it worked almost flawlessly---I could not get it to work with anything other than an open system on my home router---but when I upgraded to Jaunty, it stopped working.
It detects all available networks, and I am able to use NetworkManager to connect to my own network. However, when I try to actually use the connection, it does not work at all. The only way have found to get a working connection is to suspend to RAM and then resume.
On a perhaps related note, it completely fails to connect to local hosts using their host names. If I type:
ping <host>
PING <host> (2.1.168.192) 56(84) bytes of data.
WARNING: kernel is not very fresh, upgrade is recommended.
It does however work if I ping 192.168.1.2.
| affects: | madwifi-tools (Ubuntu) → ndiswrapper (Ubuntu) |
| Przemek K. (azrael) wrote | #1 |
| Changed in ndiswrapper (Ubuntu): | |
| status: | New → Incomplete |
| Przemek K. (azrael) wrote | #2 |
| Changed in ndiswrapper (Ubuntu): | |
| status: | Incomplete → Invalid |
| Roman V Andreev (rvandreev) wrote | #3 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version (10.04), this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 368104, and any other logs that are relevant for this particular issue.