|
楼主 |
发表于 2004-9-17 13:47:08
|
显示全部楼层
Fedora Core 2 and IPW2200 Wire
Fedora Core 2 and IPW2200 Wireless Driver
Bill Moss
Updated September 6, 2004
Introduction
The purpose of this note is to outline the installation steps for the IPW2200 driver for the Intel Pro 2200BG wireless adapter under Fedora Core 2 (FC2). The experiments reported on below were done on an IBM Thinkpad T42.
The previously posted article, Dual Booting, Part 1 covered hard disk partitioning and installation of FC2, the article Dual Booting, Part 2 covered post-installation configuration, and the article Ndiswrapper Wireless Driver covered the use of the ndiswrapper module as an interface to the Windows XP 2200BG driver. The 2.6 kernels used in the initial release of FC2 and in subsequent updates have the 4kstack option hardwired, but ndiswrapper requires an 8kstack option. Consequently, a stock FC2 kernel could not be used with the ndiswrapper module. The IPW2200 driver will work with stock kernels
On May 4, 2004 Intel launched an open source project to create a Linux driver (ipw2200) for the 2200BG wireless adapter. On May 28, 2004 version 0.1 was released and on September 3, 2004 version 0.7 was released. Here are the steps to install and configure version 0.7 on FC2.
Two methods of installation will work. The initscripts upgrade method fixes a bug (#112824) in the original FC2 release, while the legacy firmware loading method uses the rpm's provided by Axel Thimm at ATrpms.net.
Stock Kernel
I used the stock kernel and source:
kernel-2.6.8-1.521.i686
kernel-sourcecode-2.6.8-1.521.noarch
Hotplug support is compile into the kernel and is not a loadable module.
Initscripts Upgrade Method
The FC2 release contained the package hotplug-2004_04_01-1. This rpm appears to be missing the hotplug initscript. This omission was intentional. The hotplug.spec found in the source rpm says
# We don't use this
rm -f $RPM_BUILD_ROOT/etc/init.d/hotplug
The bug was not the omission of the hotplug initscript, but rather was in the package initscripts-7.55.1-1 contained in the initial FC2 release.
The solution then is to upgrade the initscripts package. The first thing to do is to remove the hotplug script if you previously installed it.
# /etc/rc.d/rc5.d/S01hotplug stop
# chkconfig --del hotplug
# rm /etc/rc.d/init.d/hotplug
Download the lastest development initscripts and mkinitrd rpm's from
http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/Fedora/RPMS/
but be forewarned that development rpm's can break your system. The current versions as of September 6, 2004 are
initscripts-7.77-1.i386.rpm
mkinitrd-4.1.9-1.i386.rpm
Install
rpm -Uvh mkinitrd-4.1.9-1.i386.rpm
rpm -Uvh initscripts-7.77-1.i386.rpm
The initscripts changelog has some useful information. The command
rpm -q --changelog initscripts-7.77-1.i386 | more
shows that important changes were made at version 7.70-1:
7.70-1
autoload hardware modules on startup
fix firmware loading #129155
Now we are ready to install the driver. Download ipw2200-0.7.tgz from
http://ipw2200.sourceforge.net/
Unarchive, enter the directory ipw2200-0.7, and then do
# make install
Download the adapter firmware ipw2200-fw-2.0.tgz from
http://ipw2200.sourceforge.net/firmware.php
and unarchive in the directory /usr/lib/hotplug/firmware.
Reboot and when the new hardware dialog box comes up, choose dhcp or set an ip address.
Configure the wireless interface using the System Settings -> Network utility. Set ESSID, Mode, and WEP key. Check to see if the following two files have been created.
/etc/sysconfig/network-scripts/ifcfg-eth1
IPV6INIT=no
ONBOOT=no
USERCTL=yes
PEERDNS=yes
GATEWAY=
TYPE=Wireless
DEVICE=eth1
HWADDR=XX:XX:XX:XX:XX:XX
BOOTPROTO=dhcp
NETMASK=
DHCP_HOSTNAME=
IPADDR=
DOMAIN=
ESSID=XXXXXX
CHANNEL=1
MODE=Managed
RATE=54Mb/s
and
/etc/sysconfig/network-scripts/keys-eth1
KEY=XXXXXXXXXXXXXXXXXXXXXXXXXX
Your MAC address, ESSID, and WEP key should appear in these files. Note that my wireless network uses a WEP key with 26 hex characters.
Activate the wireless inferface using the Systems Settings -> Network utility as root or the System Tools -> Network Device Control utility as a non-root user.
Check the configuration with iwconfig.
# iwconfig eth1
ieee 802.11b ESSID:"cuairnet" Nickname:"localhost.localdomain"
Mode:Managed Channel:6 Access Point: 00:01:24:F0:40:5A
Bit Rate=1Mb/s
RTS thrff
Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX Security mode:restricted
Power Managementff
Link Quality:18/100 Signal level:-186 dBm Noise level:-144 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:1
Legacy Firmware Loading Method
Download
ipw2200-firmware-2.0-2.at.noarch.rpm
from http://atrpms.net/dist/common/ipw2200-firmware/ and install.
Download
kernel-module-ipw2200-2.6.8-1.521-0.7-6.rhfc2.at.i686.rpm
ipw2200-0.7-6.rhfc2.at.i386.rpm
from
http://atrpms.net/dist/fc2/ipw2200/
and install.
Cisco VPN Client Installation.
Beginning with the initial release of FC2, I upgraded to the Cisco VPN client version 4.0.4 (A). After installing and testing the IPW2200 driver, I installed the latest version 4.6. The VPN client would not start and the system hung. I tried version 4.0.5 and the same thing happened. I successfully reinstalled version 4.0.4 (A). |
|