Linux Mint Forums

1. I don't have mint installed yet, using LiveDVD.
2. Network dongle isn't supported, have to ndiswrapper it; got the .inf file using Step 1 from here: http://growingtheneurons.blogspot.com/2 ... rk-on.html
3. Following this video to walk me through ndiswrapper, starting at 7:13: http://www.youtube.com/watch?v=5p59xfRt ... re=related

(Note: I'm performing all terminal commands with sudo because without it I get told permission denied.)
After the video does 'ndiswrapper -m', he does 'ifconfig wlan0 up', but this step doesn't work for me. I get the error "wlan0: no interface flag, no such device" or something like that.

Help?

Wireless adapter: USB dongle, Netgear WNDA3100v2 (bcm4323 chipset)
Linux: Mint 13 XFCE

Installed driver bcmwlhigh5.inf via ndiswrapper and ndiswraper -m'd it. Next step taken is 'ifconfig wlan0 up', but... "wlan0: ERROR while getting interface flags: No such device".

Results of mintWifi.py (transcribed because I'm doing this between two computers, one without internet):
ndiswrapper -driver installed, device present
iwconfig - only shows lo and eth0, no wireless extensions
ifconfig - only shows eth0 and lo - gobbledygook for each one (do not have an ethernet connection, or whatever lo is)

The problem: wlan does not seem to be being registered? The light on the dongle is on, linux recognizes it as being in the system... but no wlan in iwconfig/ifconfig?

Please see SECOND POST for updated issue

Originally, I was trying to do everything off a livedvd. No longer the case. Dualbooting now, so I can download stuff on my Windows partition then use/install it on my Linux partition if need be.

Well, this issue is fixed.

As reported here: http://askubuntu.com/questions/132894/h ... -not-found, there's a bug(?) in Ubuntu 12, which Mint 13 is based off, where ndiswrapper is not registered(?) as a module (whatever that is). One suggested solution was to install ndiswrapper-dkms, which I did by manually downloading it from here: http://packages.ubuntu.com/precise/all/ ... s/download and then double-clicking the file to install it (yay for gui installation!!)... and then typing 'sudo modprobe ndiswrapper' in the terminal.



Now: wlan0 comes up, but I can't connect to a network... that is [WPA2-PSK] security enabled. I can connect to and have internet access with a non-secured network, but when trying with my actual network, it gets stuck on the "Requesting a wireless network address for [my network's name]" - "gets stuck" meaning it tries for a few seconds then gives up then restarts the process ("Configuring [blah blah], then "Requesting a wireless network [blah blah]"). Since this is a totally separate issue, I'll either make a new thread in a day or so after I try to solve the problem on my own, or if anyone wants to go ahead and offer help in this thread that'd be perfectly fine by me.

I have the same issue with my netbook. My wireless (Broadcom) seems to be working as it detects my network. However when I attempt to connect it keeps saying "Requesting a wireless network address for [network name]" I am beyond frustrated. Have you been able to solve this issue yet?

Thanks in advance.

misce wrote:Well, this issue is fixed.

As reported here: http://askubuntu.com/questions/132894/h ... -not-found, there's a bug(?) in Ubuntu 12, which Mint 13 is based off, where ndiswrapper is not registered(?) as a module (whatever that is). One suggested solution was to install ndiswrapper-dkms, which I did by manually downloading it from here: http://packages.ubuntu.com/precise/all/ ... s/download and then double-clicking the file to install it (yay for gui installation!!)... and then typing 'sudo modprobe ndiswrapper' in the terminal.



Now: wlan0 comes up, but I can't connect to a network... that is [WPA2-PSK] security enabled. I can connect to and have internet access with a non-secured network, but when trying with my actual network, it gets stuck on the "Requesting a wireless network address for [my network's name]" - "gets stuck" meaning it tries for a few seconds then gives up then restarts the process ("Configuring [blah blah], then "Requesting a wireless network [blah blah]"). Since this is a totally separate issue, I'll either make a new thread in a day or so after I try to solve the problem on my own, or if anyone wants to go ahead and offer help in this thread that'd be perfectly fine by me.