 |
 |
 |
 |
| Servers & Networking Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc. |
26th October 2006, 09:01 AM
|
|
Registered User
|
|
Join Date: Sep 2006
Posts: 11
|
|
|
FC6 wireless IPW2200
I have been running fc5 wirelessly no probs on a T42 with ipw2200. However did a fresh install of fc6 last night and can't get the wireless to work coppied the firmware over to lib/firmware and downloaded the ipw2200 driver and ieee80211 driver but still no joy
When I try and extract the contents of ieee80211 and try to make the file I get the error /lib/modules/2.------fc6/build does not exist
can anyone suggest what is happening here or point me in the right direction
|
26th October 2006, 03:04 PM
|
 |
Registered User
|
|
Join Date: Jul 2005
Location: Ft Huachuca, AZ
Posts: 3,762
|
|
|
You don't need the driver and ieee80211, they are included. What version of firmware are you using?? You need 3.0 firmware
|
26th October 2006, 06:54 PM
|
|
Registered User
|
|
Join Date: Sep 2006
Posts: 11
|
|
|
Yes version 3 just going to look at it now as I am home.
|
26th October 2006, 07:51 PM
|
|
Registered User
|
|
Join Date: Sep 2006
Posts: 11
|
|
|
Is there a series of steps i need to follow to get FC6 to use the wireless network how can I test whats happening?
|
26th October 2006, 08:42 PM
|
|
Registered User
|
|
Join Date: Sep 2006
Posts: 11
|
|
|
ok I now have it running and scanning but it never connects but when I try and activate the eth1 device I get the following error
ipw2200 device eth1 does not seem to be present
|
26th October 2006, 11:21 PM
|
|
Registered User
|
|
Join Date: Jul 2005
Location: Ft Huachuca, AZ
Posts: 3,762
|
|
|
Open a terminal window and type su - That is SU dash, type system-config-network. Is your wireless listed??? Is it listed as wireless or ethernet??? If it is not listed, click the "new" tab and select wireless, is your card listed, if not it is not seeing the firmware. Are you using NetworkManager?? If not try starting the NM services and try connecting that way....
|
27th October 2006, 02:00 AM
|
|
Registered User
|
|
Join Date: Feb 2006
Posts: 48
|
|
|
I have the same problem
I have downloaded the firmware from livna
But it is listed as an ethernet card not a wirless card
I deleted the eth1 (the 2200 card) but can not add a wireless card just like cyart i get
ipw2200 device eth1 does not seem to be present
Any advise
I think you are right that Network Manger will set it up correctly, but I do need to use network manger as I have one wireless network that need to have a manual IP address - networkmanger does not support manual configuration.
Steven
|
27th October 2006, 02:47 AM
|
|
Registered User
|
|
Join Date: Jul 2005
Location: Ft Huachuca, AZ
Posts: 3,762
|
|
|
Post the contents of your /lib/firmware directory
|
27th October 2006, 04:39 AM
|
|
Registered User
|
|
Join Date: Oct 2006
Posts: 6
|
|
I'm running FC6 on a dell 600m running IPW2100 wireless, getting the 2200 wireless to work is similar:
1. for 2200: http://ipw2200.sourceforge.net/firmware.php and download the appropriate firmware
If you have 2100 intel wireless drivers go to http://ipw2100.sourceforge.net/firmware.php
2. untar the files to the desktop
3. Copy files to the lib/firmware folder
Code:
mv *.fw /lib/firmware
4. remove any modules (sub 2100 if using 2100 drivers)
Code:
/sbin/modprobe -r ipw2200
5. install ipw modules
Code:
/sbin/modprobe ipw2200
6. reboot
once booted, go to the network manager and select new wireless settings, your card should now be displayed, if not try to download and use another version of the firmware (I'm running on the 1.3 version for the 2100)
That should do it!
Last edited by mmattax; 27th October 2006 at 04:53 AM.
|
27th October 2006, 04:52 AM
|
|
Registered User
|
|
Join Date: Apr 2004
Location: Daytona Beach, FL
Age: 47
Posts: 423
|
|
Quote:
|
Originally Posted by mmattax
I'm running FC6 on a dell 600m running IPW2100 wireless, getting the 2200 wireless to work is similar:
|
I'm using the latest 3.0 firmware without any issues. Still working out WPA tho...
__________________
Registered Linux user: 358599
|
27th October 2006, 04:54 AM
|
|
Registered User
|
|
Join Date: Apr 2004
Location: Daytona Beach, FL
Age: 47
Posts: 423
|
|
|
The how to I posted on my site couple days ago...
1 Description
Intel PRO/Wireless 2200BG and 2915ABG Network Connection miniPCI adapters open source wireless driver.
2 Installing Drivers
The Drivers are already included with FC6 without any additional effort on the end users part.
3 Obtaining Firmware
For legal issues the firmware is not included with the default FC6 installation. First obtain version 3 of the firmware here after scrolling all the way to the bottom of the page and click on the "I Agree" text link.
Extract the file to your Desktop. You will see an ipw2200-fw-3.0 folder get created.
4 Installing the Firmware
Open a terminal session and switch to the root user and then copy the files to the firmware diredtory:
su -
cd /lib/firmware/
cp /home/shawn/Desktop/ipw2200-fw-3.0/* ./
5 Restarting the Kernal Module
Next, while still working as the root user retart the module by entering the folowing lines:
rmmod ipw2200
modprobe ipw2200
6 Adding a Wireless device
Still working as root, you can run the 'neat' command to add the wireless device. Typically we did not find this necessary as the default install of Fedora Core 6 has already detected the card (it just lacked the necesary firmware)
7 Activating the device
We recommend your using NetworkManager. Reboot is not necessary.
__________________
Registered Linux user: 358599
|
27th October 2006, 05:00 AM
|
|
Registered User
|
|
Join Date: Oct 2006
Posts: 6
|
|
Quote:
|
Originally Posted by wshawn
I'm using the latest 3.0 firmware without any issues. Still working out WPA tho...
|
are you using wifi-radar to handle your wireless connections?
If not, install it from the add/delete software option ( you may have to search fro wifi-radar). I find that wifi-radar is the best wifi manager for linux and handles WEP / WPA well.
|
27th October 2006, 02:39 PM
|
|
Registered User
|
|
Join Date: Oct 2006
Posts: 20
|
|
I'm having problems too.. I have the ipw2200, it worked find in FC5, now with FC6 it doesn't.. I installed the latest firmware through yum 3.0-9 and followed the steps that mmattax posted as well what was posted by snoze at http://forums.fedoraforum.org/showth...hlight=ipw2200. When I did what snoze said it worked my ipw2200 showed up under wireless and was active, when after I rebooted it no longer activates the device, I tried both steps again no luck, even through network manager it doesn't work. I get the following error
Error for wireless request "Set Bit Rate" (8B20) :
SET failed on device eth1 ; Invalid argument.
Determining IP information for eth1... failed; no link present. Check cable?
Any idea why? Please help
|
27th October 2006, 05:46 PM
|
|
Registered User
|
|
Join Date: Jul 2006
Posts: 30
|
|
|
Wireless woes continue with ipw2200
I was inspired by this article to replace my BCM4318 wireless card with an IPW2200, but am running into similar issues. An lspci | grep -i wireless shows that the device is detected correctly:
Code:
02:03.0 Network controller: Intel Corporation PRO/Wireless 2200BG (rev 05)
An lsmod | grep ipw shows that the kernel modules are installed as well:
Code:
ipw2200 108197 0
ieee80211 31113 1 ipw2200
Still, NetworkManager fails to detect the wireless connection. An edited /var/log/messages follows:
Code:
Oct 27 04:54:26 localhost syslogd 1.4.1: restart.
Oct 27 04:54:27 localhost kernel: klogd 1.4.1, log source = /proc/kmsg started.
Oct 27 04:54:45 localhost kernel: b44.c:v1.01 (Jun 16, 2006)
Oct 27 04:54:45 localhost kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 18 (level, low) -> IRQ 209
Oct 27 04:54:45 localhost kernel: eth0: Broadcom 4400 10/100BaseT Ethernet 00:14:22:95:19:f8
Oct 27 04:54:45 localhost kernel: ieee80211: 802.11 data/management/control stack, git-1.1.13
Oct 27 04:54:45 localhost kernel: ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
Oct 27 04:54:45 localhost kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.2kmprq
Oct 27 04:54:45 localhost kernel: ipw2200: Copyright(c) 2003-2006 Intel Corporation
Oct 27 04:54:45 localhost kernel: ACPI: PCI Interrupt 0000:02:03.0[A] -> GSI 17 (level, low) -> IRQ 217
Oct 27 04:54:45 localhost kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
Oct 27 04:54:45 localhost kernel: ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 169
Oct 27 04:54:45 localhost kernel: ipw2200: Radio Frequency Kill Switch is On:
Oct 27 04:54:45 localhost kernel: Kill switch must be turned off for wireless networking to work.
Oct 27 04:54:45 localhost kernel: ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
Oct 27 04:54:45 localhost kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 169
Oct 27 04:54:50 localhost NetworkManager: <information> starting...
Oct 27 04:54:51 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 27 04:54:51 localhost NetworkManager: <information> eth0: Device is fully-supported using driver 'b44'.
Oct 27 04:54:51 localhost NetworkManager: <information> nm_device_init(): waiting for device's worker thread to start
Oct 27 04:54:51 localhost NetworkManager: <information> nm_device_init(): device's worker thread started, continuing.
Oct 27 04:54:51 localhost NetworkManager: <information> Now managing wired Ethernet (802.3) device 'eth0'.
Oct 27 04:54:51 localhost NetworkManager: <information> Deactivating device eth0.
Oct 27 04:54:51 localhost kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct 27 04:54:51 localhost NetworkManager: <information> eth1: Device is fully-supported using driver 'ipw2200'.
Oct 27 04:54:51 localhost NetworkManager: <information> nm_device_init(): waiting for device's worker thread to start
Oct 27 04:54:51 localhost NetworkManager: <information> nm_device_init(): device's worker thread started, continuing.
Oct 27 04:54:52 localhost NetworkManager: <information> Now managing wireless (802.11) device 'eth1'.
Oct 27 04:54:52 localhost NetworkManager: <information> Deactivating device eth1.
Oct 27 04:56:16 localhost NetworkManager: <information> User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / NETGEAR
Oct 27 04:56:16 localhost NetworkManager: <information> Deactivating device eth1.
Oct 27 04:56:16 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
Oct 27 04:56:16 localhost NetworkManager: <information> Device eth1 activation scheduled...
Oct 27 04:56:16 localhost NetworkManager: <information> Activation (eth1) started...
Oct 27 04:56:16 localhost NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Oct 27 04:56:16 localhost NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Oct 27 04:56:16 localhost NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Oct 27 04:56:16 localhost NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Oct 27 04:56:16 localhost NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Oct 27 04:56:16 localhost NetworkManager: <information> Activation (eth1/wireless): access point 'NETGEAR' is unencrypted, no key needed.
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: sending command 'INTERFACE_ADD eth1 wext /var/run/wpa_supplicant '
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: response was 'OK'
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: sending command 'AP_SCAN 2'
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: response was 'OK'
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: sending command 'ADD_NETWORK'
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: response was '0'
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 ssid 4e455447454152'
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: response was 'OK'
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 scan_ssid 1'
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: response was 'OK'
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: response was 'OK'
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: sending command 'ENABLE_NETWORK 0'
Oct 27 04:56:16 localhost NetworkManager: <information> SUP: response was 'OK'
Oct 27 04:56:16 localhost NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Oct 27 04:56:36 localhost NetworkManager: <information> Activation (eth1/wireless): association took too long (>20s), failing activation.
Oct 27 04:56:36 localhost NetworkManager: <information> Activation (eth1) failure scheduled...
Oct 27 04:56:36 localhost NetworkManager: <information> Activation (eth1) failed for access point (NETGEAR)
Oct 27 04:56:36 localhost NetworkManager: <information> Activation (eth1) failed.
Oct 27 04:56:36 localhost NetworkManager: <information> Deactivating device eth1.
Oct 27 04:56:36 localhost NetworkManager: <information> wpa_supplicant(2151): Global control interface '/var/run/wpa_supplicant-global'
Oct 27 04:56:36 localhost NetworkManager: <information> wpa_supplicant(2151): RX global ctrl_iface - hexdump_ascii(len=49):
Oct 27 04:56:36 localhost NetworkManager: <information> wpa_supplicant(2151): 49 4e 54 45 52 46 41 43 45 5f 41 44 44 20 65 74 INTERFACE_ADD et
Oct 27 04:56:36 localhost NetworkManager: <information> wpa_supplicant(2151): 68 31 09 09 77 65 78 74 09 2f 76 61 72 2f 72 75 h1__wext_/var/ru
Oct 27 04:56:36 localhost NetworkManager: <information> wpa_supplicant(2151): 6e 2f 77 70 61 5f 73 75 70 70 6c 69 63 61 6e 74 n/wpa_supplicant
Oct 27 04:56:36 localhost NetworkManager: <information> wpa_supplicant(2151): 09 _
Oct 27 04:56:36 localhost NetworkManager: <information> wpa_supplicant(2151): CTRL_IFACE GLOBAL INTERFACE_ADD 'eth1 wext /var/run/wpa_supplicant '
Oct 27 04:56:36 localhost NetworkManager: <information> wpa_supplicant(2151): Initializing interface 'eth1' conf 'N/A' driver 'wext' ctrl_interface '/var/run/wpa_supplicant'
Oct 27 04:56:36 localhost NetworkManager: <information> wpa_supplicant(2151): Initializing interface (2) 'eth1'
Oct 27 04:56:36 localhost NetworkManager: <information> wpa_supplicant(2151): EAPOL: SUPP_PAE entering state DISCONNECTED
Oct 27 04:56:36 localhost NetworkManager: <information> wpa_supplicant(2151): EAPOL: KEY_RX entering state NO_KEY_RECEIVE
Oct 27 04:56:36 localhost NetworkManager: <information> wpa_supplicant(-1): EAPOL: SUPP_BE entering state INITIALIZE
Oct 27 04:56:37 localhost NetworkManager: <information> wpa_supplicant(-1): EAP: EAP entering state DISABLED
Oct 27 04:56:37 localhost NetworkManager: <information> wpa_supplicant(-1): EAPOL: External notification - portEnabled=0
Oct 27 04:56:37 localhost NetworkManager: <information> wpa_supplicant(-1): EAPOL: External notification - portValid=0
Oct 27 04:56:37 localhost NetworkManager: <information> wpa_supplicant(-1): SIOCGIWRANGE: WE(compiled)=20 WE(source)=18 enc_capa=0xf
Oct 27 04:56:37 localhost NetworkManager: <information> wpa_supplicant(-1): capabilities: key_mgmt 0xf enc 0xf
Oct 27 04:56:37 localhost NetworkManager: <information> wpa_supplicant(-1): Own MAC address: 00:16:6f:b0:4f:2a
Oct 27 04:56:37 localhost NetworkManager: <information> wpa_supplicant(-1): wpa_driver_wext_set_wpa
Oct 27 04:56:47 localhost kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Lastly, the output of an iwconfig eth1:
Code:
eth1 radio off ESSID:"NETGEAR"
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power=off 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
Thanks in advance to anyone who can help. I'll stop at nothing to avoid installing Windows instead of Fedora... 
|
27th October 2006, 06:50 PM
|
|
Registered User
|
|
Join Date: Oct 2006
Posts: 20
|
|
OK so I decided to upgrade to latest driver for the ipw2200 via yum it installed
ipw2200 1.2.0-45.fc6.i386
ieee80211-kmdl-2.6.18-1.2798.fc6.i686
ipw2200-kmdl-2.6.18-1.2798.fc6.i686
and now i get the following error when I try to activate the device
Device eth1 does not seem to be present, delaying initialization.
what gives??
again any help is appriciated
Quote:
|
Originally Posted by FatMutha
I'm having problems too.. I have the ipw2200, it worked find in FC5, now with FC6 it doesn't.. I installed the latest firmware through yum 3.0-9 and followed the steps that mmattax posted as well what was posted by snoze at http://forums.fedoraforum.org/showth...hlight=ipw2200. When I did what snoze said it worked my ipw2200 showed up under wireless and was active, when after I rebooted it no longer activates the device, I tried both steps again no luck, even through network manager it doesn't work. I get the following error
Error for wireless request "Set Bit Rate" (8B20) :
SET failed on device eth1 ; Invalid argument.
Determining IP information for eth1... failed; no link present. Check cable?
Any idea why? Please help |
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
 Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Current GMT-time: 22:02 (Saturday, 18-05-2013)
|
|
 |
 |
 |
 |
|
|
