Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > Fedora 17/18 > Servers & Networking
FedoraForum Search

Forgot Password? Join Us!

Servers & Networking Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 23rd May 2008, 05:44 PM
unix.95054 Offline
Registered User
 
Join Date: May 2008
Posts: 5
Fedora 8 - iwl4965 - Intel Wireless WiFi Link 4965AGN related problem

Dear Fedora gurus,

I am facing problem in configuring the wifi on my laptop. I installed Fedora 8 [(Linux version 2.6.23.1-42.fc8 (kojibuilder@xenbuilder2.fedora.redhat.com)] on my Acer Aspire 5920 Laptop. I am finding it bit tricky to setup my wifi correctly.

Looks like I am able to connect to wifi temporarily and the wireless router assigns IP address also, but immediately after that, it gets disconnected. Here are the messages from /var/log/messages file:

I am main concerned why it is loosing IP address after getting it.

I am kind of stuck with this in mind and need some help. Please guide what I can do to configure wifi.

-------------------------------------------
May 22 23:53:32 user-PC dhclient: Trying recorded lease 192.168.1.101
May 22 23:53:32 user-PC avahi-daemon[2655]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.101.
May 22 23:53:32 user-PC avahi-daemon[2655]: New relevant interface wlan0.IPv4 for mDNS.
May 22 23:53:32 user-PC avahi-daemon[2655]: Registering new address record for 192.168.1.101 on wlan0.IPv4.
May 22 23:53:35 user-PC avahi-daemon[2655]: Withdrawing address record for 192.168.1.101 on wlan0.
May 22 23:53:35 user-PC avahi-daemon[2655]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.101.
May 22 23:53:35 user-PC avahi-daemon[2655]: Interface wlan0.IPv4 no longer relevant for mDNS.
May 22 23:54:13 user-PC kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 22 23:54:13 user-PC dhclient: wmaster0: unknown hardware address type 801
May 22 23:54:13 user-PC dhclient: wmaster0: unknown hardware address type 801
May 22 23:54:13 user-PC dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
May 22 23:54:17 user-PC dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
May 22 23:54:26 user-PC dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
May 22 23:54:34 user-PC dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
May 22 23:54:53 user-PC dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
May 22 23:55:07 user-PC dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
May 22 23:55:22 user-PC dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
May 22 23:55:27 user-PC dhclient: No DHCPOFFERS received.
-------------------------------------------


May 22 23:35:28 user-PC gnome-keyring-daemon[3055]: adding removable location: volume_uuid_3632_6630 at /media/disk-1
May 22 23:35:28 user-PC hald: mounted /dev/sdb1 on behalf of uid 0
May 22 23:39:56 user-PC NetworkManager: <info> User request for activation of wlan0.
May 22 23:39:56 user-PC NetworkManager: <info> There is a pending activation, won't change.
May 22 23:39:56 user-PC NetworkManager: <info> Activating device wlan0
May 22 23:39:56 user-PC NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May 22 23:39:56 user-PC NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May 22 23:39:56 user-PC NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May 22 23:39:56 user-PC NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May 22 23:39:56 user-PC NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May 22 23:39:56 user-PC NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto linksys' requires no security. No secrets needed.
May 22 23:39:56 user-PC NetworkManager: <info> Config: added 'ssid' value 'linksys'
May 22 23:39:56 user-PC NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
May 22 23:39:56 user-PC NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May 22 23:39:56 user-PC NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2
May 22 23:40:21 user-PC NetworkManager: <info> Activation (wlan0/wireless): association took too long, failing activation.
May 22 23:40:21 user-PC NetworkManager: <info> Activation (wlan0) failed for access point (linksys)
May 22 23:40:21 user-PC NetworkManager: <info> Marking connection 'Auto linksys' invalid.
May 22 23:40:21 user-PC NetworkManager: <info> Activation (wlan0) failed.
May 22 23:40:21 user-PC NetworkManager: <info> Deactivating device wlan0.
May 22 23:40:21 user-PC NetworkManager: <WARN> remove_network_cb(): Couldn't remove network from supplicant interface: The requested network does not exist..
May 22 23:40:21 user-PC NetworkManager: <info> SWITCH: no current connection, found better connection 'Auto linksys (wlan0)'.
May 22 23:40:21 user-PC NetworkManager: <info> Activating device wlan0
May 22 23:40:21 user-PC NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
May 22 23:40:21 user-PC NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 0
May 22 23:40:21 user-PC NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
May 22 23:40:21 user-PC NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
May 22 23:40:21 user-PC NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
May 22 23:40:21 user-PC NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
May 22 23:40:21 user-PC NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto linksys' requires no security. No secrets needed.
May 22 23:40:21 user-PC NetworkManager: <info> Config: added 'ssid' value 'linksys'
May 22 23:40:21 user-PC NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
May 22 23:40:21 user-PC NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May 22 23:40:21 user-PC NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2
May 22 23:40:46 user-PC NetworkManager: <info> Activation (wlan0/wireless): association took too long, failing activation.
May 22 23:40:46 user-PC NetworkManager: <info> Activation (wlan0) failed for access point (linksys)
May 22 23:40:46 user-PC NetworkManager: <info> Marking connection 'Auto linksys' invalid.
May 22 23:40:46 user-PC NetworkManager: <info> Activation (wlan0) failed.
May 22 23:40:46 user-PC NetworkManager: <info> Deactivating device wlan0.
May 22 23:40:46 user-PC NetworkManager: <WARN> remove_network_cb(): Couldn't remove network from supplicant interface: The requested network does not exist..
May 22 23:42:44 user-PC kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May 22 23:42:45 user-PC dhclient: receive_packet failed on wlan0: Network is down
May 22 23:42:45 user-PC NetworkManager: <info> (eth0) supplicant interface is now in state 3 (from 2).
May 22 23:42:45 user-PC NetworkManager: <info> (wlan0) supplicant manager is now in state 0 (from 1).
May 22 23:42:45 user-PC NetworkManager: <info> (wlan0) supplicant interface is now in state 3 (from 2).
May 22 23:42:51 user-PC NetworkManager: <info> Trying to start the supplicant...
May 22 23:42:51 user-PC NetworkManager: <info> (wlan0) supplicant manager is now in state 1 (from 0).
May 22 23:42:51 user-PC kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 22 23:42:51 user-PC NetworkManager: <info> (wlan0) supplicant interface is now in state 2 (from 1).
Reply With Quote
  #2  
Old 24th May 2008, 09:25 PM
unix.95054 Offline
Registered User
 
Join Date: May 2008
Posts: 5
Thumbs up RESOLVED -> Upgraded to Fedora 9 solved problem :-)

I upgraded to Fedora 9 this morning and used "Network manager". I am now able to connect to wifi net
work using "Network manger" service.

I am emphasizing on Network manager because by default it is not enabled. We need to enable it manually once and after that it will work.

I am not sure whether the driver for my wifi card is upgraded (I hope so), but the OS upgrade worked for me :-)

Last edited by unix.95054; 24th May 2008 at 09:30 PM. Reason: spelling mistake not-> now
Reply With Quote
Reply

Tags
4965agn, fedora, intel, iwl4965, link, problem, related, wifi, wireless

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Intel Wireless WiFi Link 4965AGN won't connect N band PompeyBlue Hardware & Laptops 2 18th November 2009 03:22 PM
No Go? Fedora 8 & Intel Wireless WiFi Link 4965AGN & WPA2 Personal alphonsebrown Servers & Networking 2 25th November 2007 04:34 PM
Packard Bell - Wireless WiFi Link 4965AGN broozer Installation and Live Media 1 10th September 2007 05:41 PM
Intel (R) Wireless WiFi Link 4965AGN PatrickTM Servers & Networking 2 30th April 2007 04:42 PM
Pointer: Intel (R) Wireless WiFi Link 4965AGN PatrickTM Installation and Live Media 0 30th April 2007 05:09 AM


Current GMT-time: 14:25 (Tuesday, 21-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat