Quote:
|
Originally Posted by mobin
done as shown and the wireless is up..
now want it to be enabled during boot.. should i add line to /etc/rc.d/rc.modules??
i cant find any other modules enabled there..
also help me configure the wifi and auto find the network..
|
Quote:
|
Originally Posted by mobin
i cant connect to lan through wireless in slackware..
i have a wireless(802.11g) enabled utstarcom router.i have enabled dhcp.
|
Ok, looking good so far. But I'm not sure if the two quotes above are conflicting. Can you, or can't you, connect and use the wireless connection?
Either way, here's where I'd go next:
Quote:
|
Originally Posted by mobin
now want it to be enabled during boot..
|
OK, first, let's assume you took Onebuck's advice above, and blacklisted any other existing BCM drivers that may exist on your machine.
Second: For the sake of this conversation, I am not dealing with any wireless encryption that may be involved here. I don't know personally whether the broadcom driver fully supports encryption on Linux -- I presume it does, because the driver is from Broadcom itself, but let's work on getting you connected first, then THEN you can deal with enabling encryption.
So, next step: Making the device enable automatically at boot, so:
1) create a file inside /etc/modprobe.d and call it "broadcom" or "wireless" or something like this, so that you know what it's used for.
2) inside that file, you'll put two lines, like so:
Code:
alias eth1 <modulename>
options <modulename> blah blah blah
..and now, save the file, and delete any automatically created backups of that file.
Explanation of the above code:
The first line tells the kernel that when it finds
eth1 it should modprobe your new BCM driver that you just built. To know exactly what <drivername> should be, you can use the
lsmod command, and note the exact name of the broadcom kernel module.
The second line, is optional; it is where you can put any OPTIONS that you would like the kernel to give to the module, when inserting it. I don't know what options you might want to use, or if any are necessary at all. To identify any possible options that the module accepts, use the command:
shell#
modinfo -P <modulename>
again putting the name of the module instead of <modulename>
That will show you the "optional parameters" that the module accepts. If there are none, then don't worry about this. If there ARE some, then do a bit of Googling, or check the Broadcom website, to learn what the parameters do, and if you need them or not.
------------------------------------------------------
Ok, so now, the module should automatically be inserted during boot.
The next step is to configure the network connection in the file called /etc/rc.d/
rc.inet1.conf because that is the file that configures networking in Slackware.
I currently don't use a wireless device on Slackware, so i am hesitant to provide you ideas as to what exactly to put there. Hopefully someone else more familiar, will step in here and provide an example of what you want to have there. Also, note that by default, the
rc.inet1.conf file contains a detailed example of a wireless configuration, which you can probably adjust and tailor to your needs, by uncommenting the lines you want, and editing them appropriately.
Best of success! If you need further help, we're around here somewhere
Sasha
