On Tuesday 30 November 2004 11:12 am, Jan Elders wrote:
1 of 2 configured routes for interface wlan0 up wlan0 IEEE 802.11g ESSID:"" Nickname:"MEDION" Mode:Managed Frequency:2.437GHz Access Point: FF:FF:FF:FF:FF:FF Bit Rate=2Mb/s Tx-Power:32 dBm RTS thr=2347 B Fragment thr=2346 B Encryption key:FABE-DEC5-12 Security mode:restricted Power Management:off Link Quality:100 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Apparently it does not see the Access Point, which is 100% certain functioning all-right. Also "Signal level:0" suggests to me that the card is not transmitting any radio signal.
More likely not Receiving any signal, as there would be no point in monitoring your own transmission signal level. Maybe, but then it would still be a card problem because the Access Point is certainly sending. It is continuously serving other PCs without any problem. And, as I said, the card is technically OK because it works fine under Windows and for some time with DriverLoader as well. So, why would it remain dark although the system "sees" the card with Ndiswrapper, which has loaded the correct driver (2835wicb.sys) ? Have you tried fiddeling with the encription and security mode? And are you sure you have the right Essid? No offence, but I am 100% certain that the encryption, security mode, ESSID, channel, etc. etc. are configured all-right.
Using the same card on the same laptop before with Linuxant DriverLoader did work correctly, but I abandoned that solution for other reasons. I like DriverLoader, Its always worked better than Ndiswrapper. Since the approach they use is virtually identical, why abandon the one the works? Surely its not the $19 the bugs you? Certainly not. I tried DriverLoader and it worked fine initially, until I experienced that it "froze" my system at irregular random times. Nobody could give me help with
On Wednesday 01 December 2004 09:32, John Andersen wrote: that problem. That's why I abandoned it and started looking for another solution, i.e. Ndiswrapper. If I could solve the "freeze" problem I would certainly hurry back to DriverLoader. Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"