For the record, my laptop has one of those (Fn+F2) button combinations that must be pushed to turn on the wireless card. However, this is done in Windows. The wireless led activated by these buttons, however, is typically on WIndows (unless I pull the battery and power cord). I push those two buttons to turn it on. When in Windows and the light is off, that means that card is not activated. I don't know if I need to activate the card with the buttons in Linux.
It seems I've come past step 4.
My problem with step four arose when I was trying to figure out which directory the files were used and assimilated in. After looking at what you did, I decided using Archive Manager was not a good idea.
I noticed before hand, however, that logging into root while doing this whole process was a good idea. I went back to the login screen (the screen when first signing in) and downloaded the file. I noticed Mozilla Firefox was downloading the files to the desktop (or some particular directory). I went to the directory with that file. That gunzip did wonders. The "zipped" file was placed into the desktop, and I "gunzipped" it there. Afterwards, I finally understood more about what I was doing.
I went into terminal with the root account already accessed (because I logged in) and went to the Desktop.
I copied the line of code you had...
Quote:
# gunzip -cd wl_apsta.o.tar.gz |tar -xvf-
wl_apsta.o
|
Afterwards, I noticed the file was on desktop. After noticing where everything was and how the files were being used, I understood the commands you were giving. Then I copied your text and pasted it:
Quote:
[root@localhost ]# bcm43xx-fwcutter -w /lib/firmware/ wl_apsta.o
bcm43xx-fwcutter can cut the firmware out of wl_apsta.o
|
I noticed I didn't need a .sys or .inf file. I just needed to do what was on the commands you gave. I suppose if I were doing some other flavor of wireless card setup, then they would be helpful.
But after going through step 5, I didn't have the results as expected. When doing step 5, the terminal didn't cough or spit an error at me. Nope. Instead, the terminal looked at my command, paused a second (for the first one) and then glanced at the second one. No lines of ERROR! or "huh?!" reponse were given for the following:
Quote:
[root@localhost Genecks]# /sbin/depmod -a
[root@localhost Genecks]# /sbin/modprobe bcm43xx
|
*Note: I returned to my username but under root this time. Last time I didn't.
I don't know if I'm suppose to be expecting nothing in return for this or not. But when it came to step 6, however, I did not get this:
Quote:
|
Broadcom Corporation BCM4306 802.11 b/g Wireless LAN Connection (eth1)
|
I got something more like this:
Nonetheless, I set it up and things didn't go as well when I restarted the computer.
Now I may have created a user error somewhere. But I thought that the options in the network would automatically detect my card. Is that right? Or do I need to set up SSID and everything else?
The main question: Why didn't it show
Broadcom Corporation BCM4306 802.11 b/g Wireless LAN Connection (eth1)
I haven't gone much farther, because I was unsure if I should continue or not.
Notice: I read this entire thread over once more. I discovered you suggested the 1.6 Kernel, as it was the Kernel of your choice for setting up the wireless card. I assume if I use the Kernel you used, then I would obtain the same results?
How would I go about downgrading my Kernel?
Question for Others: If you setup your card in 1.7+ (or the newest Kernel), did you see the
Broadcom Corporation... within the network settings?
SO support routines
Linear Mode
