I downloaded the windows driver and the ndiswrapper utility, it’s telling me to run these commands to install the ndiswrapper :
make distclean clean
make
sudo make install
and my terminal is telling me that there is no make command.
This is the information I got after looking up the information the sticky on this board said to look up to get information about the wireless card I’m using:
05:00.0 BCM4311 802.11 b/g WLAN (rev 01)
00:05.0 0604: 1002:5a37
any idea why the make command isn’t working for me?
On 12/20/2012 12:36 PM, blincolnw wrote:
>
> I found this article about installing the windows driver with
> ndiswrapper: 'Installing A Wireless Driver With NDISWrapper ’
> (http://tinyurl.com/6ogven)
>
> I downloaded the windows driver and the ndiswrapper utility, it’s
> telling me to run these commands to install the ndiswrapper :
>
>
>
> - make distclean clean
> - make
> - sudo make install
>
> and my terminal is telling me that there is no make command.
>
> This is the information I got after looking up the information the
> sticky on this board said to look up to get information about the
> wireless card I’m using:
>
> 05:00.0 BCM4311 802.11 b/g WLAN (rev 01)
>
>
> 00:05.0 0604: 1002:5a37
>
> any idea why the make command isn’t working for me?
Because make is not installed.
For a BCM4311, the Windows driver with ndiswrapper is about the worst possible
solution! Using b43 is much more sensible. You only need to install the firmware.
If you have access to the network while running Linux, then run the command
sudo /usr/sbin/install_bcm43xx_firmware
Your system might suffer an oops, but if you reboot, you should have wireless.
If you do not have a network connection while running Linux, then report back
and I will give you the instructions for using sneakernet.
Ok, now I’m copying and pasting the command and then it’s asking me for the root password which I enter and it gives me ’ sudo: /usr/sbin/install_bcm4311_firmware: command not found
I copied and pasted the command. It asked for the root password and after entering it I am now seeing my wireless adapter! Thanks for the help you’ve solved my wireless problem.
On 01/03/2013 11:26 PM, caf4926 wrote:
>
> Let us see
>
> Code:
> --------------------
> /sbin/lspci -nnk | grep -iA2 net
> --------------------
>
>
>
> You could try
>
>
> Code:
> --------------------
> sudo /sbin/modprobe -rv b43
>
> --------------------
>
> Code:
> --------------------
> sudo /sbin/modprobe -v b43
>
> --------------------
>
>
> You may need to install rfkill and post the result of
>
> Code:
> --------------------
> /usr/sbin/rfkill list
> --------------------
Have you ever fooled around with wl? If so, b43 or ssb may be blacklisted. Check
the files in /etc/modprobe.d/.
The result of:
/usr/sbin/rfkill list
is:
Wood@linux-6hv0:~> /usr/sbin/rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
Wood@linux-6hv0:~>
On 01/04/2013 11:06 AM, blincolnw wrote:
>
> When I run
>
> /sbin/lspci -nnk | grep -iA2 net
>
> This is what I Get: https://www.box.com/s/8z55fui0fawpckharj91
>
> The result of:
> /usr/sbin/rfkill list
> is:
> Wood@linux-6hv0:~> /usr/sbin/rfkill list
> 0: dell-wifi: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> Wood@linux-6hv0:~>
Both of the above are normal. What about the other two commands that caf4926
asked about, or the blacklisting?
What I am finding now is that if I boot up and have no wifi I can run the code to install the firmware and then of course the download fails but because it was already installed it installs, remembers my wifi router and password and connects me. Then next time I reboot or shut down I have to start again. For some reason it’s losing the firmware after a reboot.
On 01/04/2013 02:26 PM, blincolnw wrote:
>
> What I am finding now is that if I boot up and have no wifi I can run
> the code to install the firmware and then of course the download fails
> but because it was already installed it installs, remembers my wifi
> router and password and connects me. Then next time I reboot or shut
> down I have to start again. For some reason it’s losing the firmware
> after a reboot.
It is NOT losing the firmware. The file that was downloaded was discarded, but
the extracted files in /lib/firmware/b43/ are still there. If you don’t believe
me, then check.
The reason that running the script gets you wireless is that the script ends
with ‘sudo /sbin/modprobe b43’. You can accomplish the same result by running
that command, OR you can remove the blacklisting of b43 and/or ssb, which is
probably in /etc/modprobe.d/50-blacklist.conf.
I ran the other two commands and still I lose the wireless at reboot. I’m searching the /etc/modprobe.d/ directory and there is a file there called 50-blacklist.conf but searching the file there is no b43 or ssb listed there. Is there anywhere else that they might put that device if it was blacklisted?
On 01/04/2013 03:06 PM, blincolnw wrote:
> I ran the other two commands and still I lose the wireless at reboot.
> I’m searching the /etc/modprobe.d/ directory and there is a file there
> called 50-blacklist.conf but searching the file there is no b43 or ssb
> listed there. Is there anywhere else that they might put that device if
> it was blacklisted?
Those commands were not to get you wireless at boot, but to get you wireless
after you boot.
The blacklisting could be in any file in /etc/modprobe.d/.
Run ‘egrep “b43|ssb” /etc/modprobe.d/*’ and report what shows up.
After booting, did you check to see if ‘sudo /sbin/modprobe b43’ is enough to
get you wifi?