LinuxQuestions.org - Install wireless card on Centos5.

- Red Hat (https://www.linuxquestions.org/questions/red-hat-31/)

- - Install wireless card on Centos5. (https://www.linuxquestions.org/questions/red-hat-31/install-wireless-card-on-centos5-608975/)

Install wireless card on Centos5.

Hi, all

I wander if my centos5 can recognize my wireless card? Please see below:

Code:

[root@localhost ~]# lspci

00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)

00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)

00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)

00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)

00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)

00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 03)

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)

00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 03)

00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 03)

00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03)

00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)

00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03)

02:01.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)

02:04.0 CardBus bridge: Texas Instruments PCI7420 CardBus Controller

02:04.1 CardBus bridge: Texas Instruments PCI7420 CardBus Controller

02:04.2 FireWire (IEEE 1394): Texas Instruments PCI7x20 1394a-2000 OHCI Two-Port PHY/Link-Layer Controller

02:04.3 Mass storage controller: Texas Instruments PCI7420/7620 Combo CardBus, 1394a-2000 OHCI and SD/MS-Pro Controller

02:05.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)

[root@localhost ~]#

Any help will be appreciated, :D

I don't see why not. The kernel has a driver for the Intel PRO/Wireless 2200 chipset. Also, you didn't need to include the entire output from lspci, just the relevant line.

Thanks, Nylex.

My network info below:

Code:

[root@localhost ~]# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:12:3F:7F:75:9C

          inet addr:10.64.1.183  Bcast:10.64.1.255  Mask:255.255.255.0

          inet6 addr: fe80::212:3fff:fe7f:759c/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:226 errors:0 dropped:0 overruns:0 frame:0

          TX packets:132 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:23055 (22.5 KiB)  TX bytes:18844 (18.4 KiB)

          Interrupt:10



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:8 errors:0 dropped:0 overruns:0 frame:0

          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)

I wander if my kernel don't include the driver for the Intel PRO/Wireless 2200 chipset. How can I check?

Try a "modprobe ipw2200".

Code:

[root@localhost ~]# modprobe ipw2200

[root@localhost ~]#

Now run "ifconfig -a" and see if there's a wlan0 (or something else other than your eth0 and lo).

[CODE]
[root@localhost ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:12:3F:7F:75:9C
inet addr:10.64.1.183 Bcast:10.64.1.255 Mask:255.255.255.0
inet6 addr: fe80::212:3fff:fe7f:759c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:790 errors:0 dropped:0 overruns:0 frame:0
TX packets:141 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:71271 (69.6 KiB) TX bytes:19611 (19.1 KiB)
Interrupt:10

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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[root@localhost ~]#
[CODE]

Not convinced that that's correct. What does the end of dmesg say?

ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
SCSI subsystem initialized
ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
ipw2200: Unable to load firmware: -2
ipw2200: failed to register network device

Try downloading the firmware and installing it: http://ipw2200.sourceforge.net/firmware.php

Could you please teach how to install and which firmware version I should choose?

Thanks a lot, :D

After you loaded the driver, there should have been more info in the dmesg output, including the version. Download the appropriate version of the firmware based on that. There are instructions on what to do with the firmware here (see section 10, though you might want to read the rest of it as well).

Sorry for late reply.

According to the instruction, I need to upgrade my hotplug scripts. I did following:
1.download hotplug-2004_03_29.tar.gz from http://sourceforge.net/project/showf...ease_id=227366 to /root
2.unzip it and go into /root/hotplug-2004_03_29, make install and then I can't find /var/log/hotplug/events or /var/log/hotplug/input.events mentioned in the README file

I'm not sure about this to be honest.