although my network card loads correctly and works at first, if i stop using my network for a couple of hours i am no longer able to send or recieve packets. this problem doesn't occur with the 0.12-r3 version of ndiswrapper Reproducible: Always Steps to Reproduce: 1. install ndiswrapper-1.0_rc4 with the airlink wireless card 2. install the driver from the cd (tnet1130) 3. leave your computer for 8 to 10 hours Actual Results: ifconfig/iwconfig shows that the interface is available, but packets are not sent or received Expected Results: network should work correctly
provide emerge info. compile this with debug. provide dmesg output of when this happens. or log files. we need to see something. There's nothing I can do about this problem based on this info.. Once you do all those steps, you can go into irc.freenode.net and go on the channel #ndiswrapper and talk to giri.
btw. there is a newer version of ndiswrapper in the tree, you might want to try version 1.0
Same problem here, I've ndiswrapper-1.0 and kernel 2.6.10, after 8-10 hours net goes down... No log from kernel, no log from anywhere: must unload ndiswrapper module, remove pcmpcia card, reload ndiswrapper module, reinsert pcmpcia card. Any other sequences doesn't work. I had no problem with 0.12 version, don't remember with 1.0_rc4 (I had it for really few time).
I was having similar problems, but ndiswrapper 1.1 (see bug #84219) solved them for me. Once the ndiswrapper is updated, see if it works for you.
Reporter, please see if net-wireless/ndiswrapper-1.1 fixes this issue.
the new version of ndis doesnt seem to like my driver.
It seems that some regressive behavior was introduced around version 1.0rc(?). Digging around a bit it appears that a number of people are reporting just plain flaky behavior with new versions that is not present in 0.12. I've had a number of problems including total failure, inability to connect to my AP even though it shows up in a scan -- none of the problems occurs under 0.12 and there is no real diagnostic information. I'd favor leaving ndiswrapper-0.12-r3 in portage for awhile rather than just assuming a lack of diagnostic information means everything is OK.
