SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I currently am trying to connect to a wireless network(currently im runing 50ft of lan cable to get this to work)and i have the 220.127.116.11 kernel with the bcm4306 module installed. I also used the FW-cutter to install the rest of the module. now it says that it isworking yet i cant connect to anything.
-heres my iwlist
# iwlist scanning
lo Interface doesn't support scanning.
sit0 Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
eth1 No scan results
lo no wireless extensions.
sit0 no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11b/g ESSID:off/any Nickname:"*************"
Mode:Managed Frequency=2.484 GHz Access Point: Invalid
Bit Rate=1 Mb/s Tx-Power=19 dBm
RTS thr:off Fragment thr:off
Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
and the ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:B0:6C:37:C0
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:b0ff:fe6c:37c0/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1429 errors:0 dropped:0 overruns:0 frame:0
TX packets:1308 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:1485371 (1.4 MiB) TX bytes:219557 (214.4 KiB)
Interrupt:20 Base address:0x2000
eth1 Link encap:Ethernet HWaddr 00:90:4B:AC:B2:E5
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 b) TX bytes:2352 (2.2 KiB)
Interrupt:10 Base address:0x4000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Your goal is to use iwconfig to give information about the network you want to join until "iwconfig eth1" shows that the access point has been found. If there's a WEP key, e.g., you need to supply it. You may need to supply the SSID, and other info.
It may help to say "ifconfig eth1 up" before calls to iwconfig. I suggest you use iwconfig to supply the key and the SSID -- "man iwconfig" will tell you how. Look at the output of "iwconfig eth1" to check the info you supplied was correctly understood. (And later, when all that's working, then figure out how to use the higher level interface to accomplish the same thing.)
If your iwlist is telling you that you can't scan, you might not have the wireless card really supported, but you kind of tricked iwconfig into thinking you do. I learned that the hard way after toying with one for some three days, and I thought I might save you some trouble As a suggestion, broadcom doesn't seem to like Linux very much, so perhaps try ndiswrapper if nothing else works. It does a pretty good job about things. I would listen to these other people first though before installing stuff. They might have some neat tricks.
well all i know is that i followed a few steps on a website and i was able to enable the BCM43xx support through the kernel when i was recompiling it. Then i had to use the FW-cutter to get it fully installed using the wl_apsta.o file.
and i havent installed anything for the keys and SSID i was just using the standard X11 interface. menu-> settings-> internet and network -> wireless network
you need to install wireless network tools when you install slackware for that to show in the menu, i have the same card and i have it all working but for some strange reason it never seems to pick up the gateway, all other information is there ip netmask just not the gateway all is set correctly in wiress and rc.inet1.conf, and it does say its connected and i can browse the network just not the net :/