Bugzilla – Bug 106888
strange ndiswrapper problems when running on battery
Last modified: 2005-09-06 09:24:34 UTC
Problems with ndiswrapper, on a Dell D600 using a broadcom wireless a/b/g card with builtin bluetooth If I power the laptop up on battery, then ndiswrapper doesn't work correctly. Here's the problem. In one window, i setup a ping to the default route. In in the other window, I did a "rmmod ndiswrapper; modprobe ndiswrapper" here's the output. From 192.168.25.180 icmp_seq=16 Destination Host Unreachable From 192.168.25.180 icmp_seq=17 Destination Host Unreachable From 192.168.25.180 icmp_seq=18 Destination Host Unreachable From 192.168.25.180 icmp_seq=19 Destination Host Unreachable ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable 64 bytes from 192.168.25.1: icmp_seq=26 ttl=255 time=8.16 ms 64 bytes from 192.168.25.1: icmp_seq=27 ttl=255 time=1.99 ms ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable This is reproducable over several boots. If I plug the power in, wait about 60 secconds. then do "rmmod ndiswrapper; modprobe ndiswrapper" then it all works OK. I'm expecting a "wontfix: get a better network card" on this one ;-)
I can also report that if the laptop goes into a light powersave mode (After say 10 mins of inactivity while running on battery) the wlan card then fails to work when you use it again, without putting it on mains, using the machine, and then reloading the ndiswrapper module.
This is really strange. Maybe it helps something to set WIRELESS_POWER='no' in the appropriate ifcfg-file, although I doubt it. If not, would you mind testing the latest ndiswrapper from http://sourceforge.net/projects/ndiswrapper/ ? I can also send you compiled kernel module if you don't want to compile yourself.
Will do. Probalby be middle of next week before I get back to you.
I have since rebuild my laptop from scratch with suse10b3. I have also donwloaded the windows drivers recomended by the ndiswrapper wiki for my card, and it *seems* to be working correctly. Previously, I was using a windows driver that worked fine with the 0.10 build of ndiswrapper, but wasn't the one recommended by the ndiswrapper wiki site. I'll mark this bug as resolved, invalid. I'll reopen it if the strange problems come back.
Sorry, I'll have to reopen it. It's started happeing again. I'll try to do some more info gathering and add something useful here tomorrow.
Could you also try it with other versions of the window driver?
Well, with beta4, I can't reproduce this problem. So I guess that's good news.