Tag Archives: ubuntu

Linux and the WNA3100 Wireless Adapter

The good news is, it is possible to get the Netgear WNA 3100 N-300 Wireless Adapter to work in Linux (at least in anything Ubuntu-based, but the method below should work with most distros), but the bad news is that it’s not exactly a walk in the park to get there. I have put together a quick tutorial here on how to get the adapter recognised and running on my 64-bit Linux Mint 13, with the help from various online sources, forum messages and technical support pages.

First up, under the hood the WNA3100 is a Broadcom 43231 device, which you can see when you type lsusb on the command line (if your system recognizes it, which it should). As far as I can see, any distro-based driver files, like the STA Broadcom packages that are available in the repositories, do not work with this device. So to make this work, we need software called Ndiswrapper, to be able to use the original Windows driver in Linux. Install Ndiswrapper from the repositories, it doesn’t matter which version, as long as it’s a fairly recent one. Then, as I learned on this site, we need to have a package called bcmwl-kernel-source deinstalled via the Synaptic packet manager, and also make sure that the packages b43-fwcutter and firmware-b43-installer are there. Then, sudo gedit on the command line, open /etc/modules.d/blacklist.conf, and check that there is no entry “blacklist bcm43xx”. If there is, put a # in front of it.

With this you should be all good to go. Now, my problem was that the drivers that were suggested in the forums, the bcmwl5.inf for 32-bit, and bcmwl6.inf for 64-bit, did not work on my machine, when I tried to install them with ndiswrapper it gave me an error message that this was the wrong driver file (I suggest you install any driver on the command line via sudo ndiswrapper -i, and check if your device is then working or present via ndiswrapper -l, that way you get to see any error messages, as opposed to when using the graphical ndiswrapper frontend ndisgtk). So I eventually found the right driver here via this website, and that one installed flawlessly, and after reboot the WNA3100 was recognized and working, the wireless network was there, and now Bob’s your uncle. Hope this helps.

—————————————————————————-

Update : Of course, if you just want a working USB Wireless adapter that does plug-and-play and doesn’t take a week to get to work, you could just buy the TP-Link WN822N adapter for 30 bucks. Which, as I will happily admit, I did today, after consulting this Ubuntu Wireless compatibility website.

Mint madness

So. I have been using Linux Mint 12 for the last few months, after changing over from Ubuntu because the Unity Desktop drove me insane. And I was alerted to an available distribution upgrade for Mint, LinuxMint 13, codename Maya, the other day, so I went to work to upgrade my Mint distro today. Surely a walk in the park, if the experience with upgrading Ubuntu was anything to go by, bring up the command line, type “update-manager -d”, and let the good bytes flow.

Not so. No such luck. Because apparently, that would be too easy and convenient. Mint does not recognize the “update-manager -d” command, no such thing. So I googled the matter. There are a few posts on the Mint forums hinting on using the “apt-get dist-upgrade” command, but they all seem to come with a “will break your system, too unreliable, that’s the crap Ubuntu uses and it never works, too dangerous it may cause your system to stop working” and similar disclaimers.

And the alternative to a simple and convenient command line upgrade for the folks at Mint is regrettably, and ridiculously, a new install from LiveCD. Now, I wanted to try the new Cinnamon desktop, so I went along with this madness and actually downloaded and installed the iso of Mint 13 over my existing system tonight.

On the bright side, it installs eventually. But there are issues. For the first two attempts, it wouldn’t go past the “set up username and password” screen, and dog knows why. Then, the installer would grind to a halt for 10 minutes or so while installing language packs, which seems peculiar, since on the very first screen one is asked to choose a language and keyboard, so I am not certain why I would still have to download a Croatian, Urdu or Russian language pack. Then once the installation is complete, for some reason bookmarks, wallpaper and other Desktop settings are preserved, but half the software is missing, including such programs as Skype, K3b and streamtuner.

Mint people, this is fucked. To not make easily available or encourage an upgrade from an existing distro is ludicrous, and the arguments professed for this lunacy in the forums, that a command-line install may break your system, is your problem to fix, really. I have been upgrading Ubuntu on the command line for years, and never had any issue at all. If your way of doing it isn’t working, then fix it, instead of forcing your customers to run awkward new installs (with backing up of your settings, software and data) over their existing systems as the only way to upgrade.

The plot thickens

So. Installed Linux Mint. Still crappy internet. But I know what’s the problem now, ha ! At least I think so. Half the fun with Linux, isn’t it, getting stuff to work, because it’s not that I have two other jobs or anything !
I like the Mint interface, the Desktop, the absence of Unity etc, but the internet interruptions were not Ubuntu’s fault after all. It’s the driver used in Ubuntu (and hence also Mint) to work with the Realtek RTL 8111E/8168B LAN device that is used in my Gigabyte Z68XP-UD3R motherboard. They don’t like each other, and consequently you get frequent dropouts, and generally low data speeds of below 100 Kbit/s.
So far I have seen 2 possible solutions, and I’m going to try them tonight. One is to update the linux-backports-modules package (via your software manager or apt), the other is mentioned and explained here, and involves blacklisting the Ubuntu r8168/r8169 driver, and replacing it with the original one from Realtek, which can be found here.
I’ll let you know how I go. If you get blog posts, it probably worked.

—————————————————————————
Update : Problem solved and internet fixed with method number 2.