[SOLVED] broadom 4311 and broadom sta driver not working
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For ndiswrapper you will need to extract the files on a windows computer unless someone knows a better way.
Disabling security. I meant on your router. NO wep or wpa until you can get on the internet wireless. Then work on wpa/wep.
Have you tried iwconfig to set your essid again?
If you still have the firmware installed you could try removing the wl module.
Then do iwconfig to set your essid.
With the huge kernel the b43 drivers should already be loaded.
However I would still switch to generic kernel.
okay yeah i think thats a good idea to disable the security on the router...hopefully that will fix it temporarily
i do want to boot the generic kernel though...thats what i like about linux is that everything isn't preloaded in the kernel (or so i thought)
where should this file be at? I'm reading the readme and i've gotta install it but i can't seem to find it (hopefully just cause I'm looking in the wrong place)
Code:
root@darkstar:~# installpkg kernel-generic-2.6.29.5-i686-1.tgz
cannot install kernel-generic-2.6.29.5-i686-1.tgz: file not found
root@darkstar:~#
Do this for System.map and config to make the symbolic links point to the generic files.
Then you will need to make an initrd.
The command for this depends on your filesystem. (ext3 reiser etc).
then add a line to /etc/lilo.conf
check to see what the vmlinuz symbolic link is to.
Chances are your using the huge kernel with just about everything compiled into it. You will not be able to remove or blacklist anything.
The b43 drivers will be in the kernel. You need to switch to the generic kernel
make an initrd
then use broadcom-sta driver
Actually, 'huge' is not as huge as you think. The only real differences between huge and generic are that huge has non-standard disk drives (RAID and such), as well as filesystem drivers. The huge kernel still uses modules for nearly everything.
I was under the impression that the huge kernel had almost every kernel driver built-in and the generic kernel had almost everything compiled as a module. I`ve always used the generic kernels because I know whats loaded, it makes me feel more in control of my system.
Starting with generic here seemed worth a shot. I actually thought he got this working in his old thread with the b43 firmware/cutter.
I was under the impression that the huge kernel had almost every kernel driver built-in and the generic kernel had almost everything compiled as a module. I`ve always used the generic kernels because I know whats loaded, it makes me feel more in control of my system.
Starting with generic here seemed worth a shot. I actually thought he got this working in his old thread with the b43 firmware/cutter.
I use -generic as well, but the output of 'diff <(sort < config-generic-2.6.29.6) <(sort < config-huge-2.6.29.6)' is only 406 lines. Reading the output confirms that most things are installed modularly even for the -huge kernel.
To make initrd I need the kernel-generic files which I don't seem to have (whereis mkinitrd <version>.tgz returns nothing) ...any idea where I can download them?
Would this site work or do I need a specific mkinitrd file?
so looking at my kernel choices on the boot cd i used this is what i have...
hugesmp.s
speakup.s
huge.s
doesn't look like i have the generic option i'm going to burn a new disc with the generic and reinstall and try from the beginning...what would give me my best chances of getting this to work? the broadcom sta driver, or b43? correct me if i'm wrong here, but i only need to use b43-fwcutter if i'm using b43, right? (that sounds like a retarded question even saying it, but just wanted to check)
hey does anyone know if this is a serious problem? I get it when i'm reinstalling and setup is installing packages
Code:
There was a fatal error attempting to install /var/log/mount/slackware/kde/kdeedu-4.2.4-i486-1.txz. the package may be corrupt, the installation media may be bad, or something else has caused the package to be unable to read without error. You may hit enter to continue if you wish, but if this is an important required package then your installation may not work as-is.
so i did a fresh install and this is where I'm at - haven't made any changes, installed any packages, or otherwise done anything but poke around with what you see below...it looks like you are right - b43 is already preloaded...meaning i shouldn't need to download b43-fwcutter either right?
my question would be what i need to modify so when i run iwlist wlan0 scan i actually see the wifi networks. that would be a great start. if I can get to the point where i can actually see the networks i'm minutes away from figuring out how to connect to them (or so i would like to hope )
so i did a fresh install and this is where I'm at - haven't made any changes, installed any packages, or otherwise done anything but poke around with what you see below...it looks like you are right - b43 is already preloaded...meaning i shouldn't need to download b43-fwcutter either right?
my question would be what i need to modify so when i run iwlist wlan0 scan i actually see the wifi networks. that would be a great start. if I can get to the point where i can actually see the networks i'm minutes away from figuring out how to connect to them (or so i would like to hope )
Okay looks good, you have the correct *modules* loaded...and you get points for persisting...for this is the way of Slack...but you still need to install the *firmware* for your card before you can go any further...go here...
follow the instructions _exactly_ listed there for getting b43-fwcutter-012 and broadcom-wl-4.150.10.5.tar.bz2 installed...when you have that done report back for further assistance...you will be only a few simple steps away from slack wifi nirvana
so looking at my kernel choices on the boot cd i used this is what i have...
hugesmp.s
speakup.s
huge.s
doesn't look like i have the generic option i'm going to burn a new disc with the generic and reinstall and try from the beginning...what would give me my best chances of getting this to work? the broadcom sta driver, or b43? correct me if i'm wrong here, but i only need to use b43-fwcutter if i'm using b43, right? (that sounds like a retarded question even saying it, but just wanted to check)
If you do a full install without exempting kernel options then the 'generic' kernel will be installed.
...
I was trying to work with the ndiswrapper but its saying I need to download the windows driver for my wireless card and extract it but its an exe file which is unextractable. lol
That's correct: The exe file is, in fact, a ZIP file with a unzip pre-installed to automatically unpack it. You can usually just run unzip on the exe file to get its contents. Then you need to use the inf file as input to b43_fwcutter. Alternatively, you could go to the site listed in your dmesg output and get the input file from there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.