Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in 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.
I'm running FC5 (2.6.18) on a Thinkpad R52 with an Intel wireless card. ipw2200 + firmware are installed using yum. But during boot, I get told that eth1's initialization got delayed (and that I should check the cabel ). In other threads about this, it was recommended to turn on the device using system-config-network after installing ipw2200 + firmware. But when I run Fedora's system-config-network, the interface is shown as deactivated and when I try to activate it, I get the same message (initialization delayed).
When I run iwconfig (I have the latest wireless-tools package installed) directly, I found this warning:
Code:
[root@localhost ~]# iwconfig
lo no wireless extensions.
Warning: Driver for device eth1 has been compiled with version 20
of Wireless Extension, while this program supports up to version 19.
Some things may be broken...
eth1 unassociated ESSID:off/any Nickname:"localhost.localdomain"
Mode:Managed Frequency=2.462 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
eth0 no wireless extensions.
sit0 no wireless extensions.
[root@localhost ~]# iwconfig --version
iwconfig Wireless-Tools version 28
Compatible with Wireless Extension v11 to v19.
Kernel Currently compiled with Wireless Extension v20.
eth1 Recommend Wireless Extension v18 or later,
Currently compiled with Wireless Extension v20.
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
Sometime it is also required to setup the /etc/resolv.conf file by hand as root using any text editor (vi, gedit, nedit, kwrite or whatever). The format is fairly simple;
nameserver XXX.XXX.XXX.XXX
nameserver XXX.XXX.XXX.XXX
nameserver <the IP address of the wireless router>
The XXX.XXX.XXX.XXX values come from you ISP and are normally listed on the wireless routers web based interface.
My laptop has an ipw2200, and every time I've had problems it's been the driver/firmware. With various distros, I've had wireless NIC not detected at all, or detected and configurable but just doesn't work, or works "out-the-box" with no problems.
The ultimate fix every time has been download the latest driver source, download the latest firmware, eradicate the existing installation, and rebuild everything.
Not as hard as it sounds, and it's worked every time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.