• Intel Wireless Wifi Link 3945abg

After installing Mint15 on my old Dell laptop in early June, I had some trouble getting my wireless to work. After a lot of searching and reading and downloading and trial and error I got it up and running, though I no longer remember a fraction of what I did.

Not that it mattered much, since I was using a cable for my net access. However, I've since then moved, and find myself more dependent on using WiFi. A WiFi that suddenly refuses to cooperate. The WiFi is active, and can find dozens of nearby networks, but absolutely refuses to establish any connexion to the router. When attempting to connect, it takes about 30 seconds before it asks for the password; entering the password triggers another 30 second wait before it asks again. Repeat ad infinitum. Removing the authentication on the network does not help at all; it just ends up with the same 30 second wait before it gives up.

It worked fine at my local library a week ago, and apart from the updates from Update Manager nothing has been tinkered with for ages. It works equally fine when booting the XP partition, or booting from the live DVD I used when initially installing Mint. (And my roommate's Mac connects without issue.) In short, somewhere in my mucking around I've managed to do something that works with some connexions, but absolutely refuses to cooperate at my current location. Trouble is, I'm absolutely clueless as to what it might be, and the more I read and the more suggestions I try, the more confused I get. It does of course not help that the closest I get to any prior Linux experience is some fiddling around with Unix in the mid-early nineties. Any fresh ideas would be extremely welcome at this point.

Output from /usr/lib/linuxmint/mintWifi/mintWifi.py (with cable plugged in, in case it matters). Code: -. I. Scanning WIFI PCI devices. Intel Corporation PRO/Wireless 3945ABG Golan Network Connection (rev 02) PCI ID = 8086:4222 (rev 02) -. II. Querying ndiswrapper.

Netw39x5: driver installed device (8086:4222) present (alternate driver: iwl3945) -. III. Querying iwconfig. Wlan0 IEEE 802.11g ESSID:'Oddiii' Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated Bit Rate:54 Mb/s Fragment thr:-211403072 B Encryption key:off Power Management:off Link Quality:0 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 lo no wireless extensions. Eth0 no wireless extensions. IV.

Querying ifconfig. Visit and if no love, google some more + I have the same wireless you do (3945ABG) in my Thinkpad, which is running Linux Mint Olivia Xfce 32-bit at present, but my problem is a little bit different. I can establish a connection, but it disconnects after about an hour or so. But I may have fixed it with the above solution. Not sure yet. I'll be surer tomorrow if I'm still connected! However, the fact you can connect at the library but not at home points the finger at your router and its settings.

Webpack dev server invalid host header. Step 03: Installing required modules.

What is different between the library's wifi and your home wifi? Good news: My Thinkpad used to connect fine via wifi on Linux Mint Nadia KDE. I think I lost some config when I installed the new OS. I seem to remember having this problem last year when I first began running LM KDE. How I solved it, I don't recall, but it is solvable.

After posting the above message, I continued using the net without any problems. My fix was simple. As per the ubuntu link, I created a file in /etc/modprobe.d called iwl3945.conf and inserted this line: options iwl3945 disablehwscan=0 Rebooted and had no more disconnects.

I experienced your exact problem at one location in recent memory. The Thinkpad could find the network, but there was that accursed 30 second delay, and when I entered the password-the correct password-it denied access.

Something to do with the way their router is configured I believe. I tried connecting for a long time with no luck. Of course, if the computer cannot connect, then there is no going to the Internet for help. Pretty much a brick wall at that point.

I rediscovered reading. I will be interested to know what you discover as a solution, because it is possible I will be at that same location again. I remember reading something to the effect that there is a bug in relation to the n protocol. Something to do with wifi. I have no idea what that means.

However, not all networks use that n protocol. I think some do because the nerd that configured the network thinks the n protocol is faster and who cares about old hardware and old computers, right? Let's just support the new I-junk. That is my hunch. Code: ndiswrapper 192638 0 (For some reason, the 'ndis' part is written in red, while the rest is standard white-on-black.) Good news is that -r ndiswrapper and iwl3945 now has me online and happy. Thanks a bunch!

Intel Wireless Wifi Link 3945abg

All that remains is to make it permanent. It should be noted that this was very much a problem of my own making: The reason I started mucking around with the wireless in the first place was that the WiFi light was off, and refused to get turned on. Only later, after trying every suggested solution under the sun, did I accidentally discover that unlike under Windows, where the WiFi light is either on or off, Mint has it blinking.

What fooled me is that the blinking is extremely slow if I'm not connected to anything, leading to the impression that it is actually turned off. ETA: As for the mysterious ability to use the library connexion when nothing else worked (and I tried several other routers as well with no success), I suspect igor83's hunch is close to the mark; the library is probably using some old protocol they set up a decade ago and haven't touched since. DeForest wrote:It should be noted that this was very much a problem of my own making: The reason I started mucking around with the wireless in the first place was that the WiFi light was off, and refused to get turned on.

Only later, after trying every suggested solution under the sun, did I accidentally discover that unlike under Windows, where the WiFi light is either on or off, Mint has it blinking. What fooled me is that the blinking is extremely slow if I'm not connected to anything, leading to the impression that it is actually turned off. That's actually a feature, I think. The blinking gives a rough approximation of the network activity. So if you see a bunch of blinking and you're not doing anything on the Net, and Update Manager isn't checking for new updates, or something like that, then that may be cause for concern. In Linux Mint Xfce, by the way, no blinking.

My wifi indicator just shows bars indicating how strong a signal it is receiving. Right now, I'm at 58%. Oh and by the way, the problem where my connection was dropping on a random basis-totally solved, looks like. Thank goodness for all these Linux forums and the smart people that visit them! DeForest wrote:ETA: As for the mysterious ability to use the library connexion when nothing else worked (and I tried several other routers as well with no success), I suspect igor83's hunch is close to the mark; the library is probably using some old protocol they set up a decade ago and haven't touched since. There's some kind of fix available that will resolve that problem, by disabling the n protocol I think.

I had better look into that before I find myself at that problem location again. I typed in about 30 different variations of what I thought to be the password before finally giving up. I learned later that my password was correct.

It's a network issue. 3945abg, does not support 802.11n, so I am disabling it What, specifically, did you do? You don't need to disable it at all.

It's not supported by your card, so won't be used. The iwlwifi driver that is listed at '2' on the linked web page, is not even used for your card, it's only for newer Intel cards. What's more, there is a typo in one of the commands so it may not work as it should even if you had the right hardware (iwlwif would be iwlwifi, in the first command). Thanks for the info.

Well, it didn't do any harm, and I really didn't notice any difference.