Announcement

Collapse
No announcement yet.

Wifi won't connect after upgrade hardy --> intrepid

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Wifi won't connect after upgrade hardy --> intrepid

    When I installed the automatic patches this evening, I got an innocent-looking question whether I wanted to upgrade. I answered yes. What a mistake! The wifi that was working flawlessly under 8.04 is now inoperative. I already spent many hours trying to fix it or finding an answer. It seems to be a problem that many users have. But none of the tips seems to work out for me. Wonder why they released it, knowing it had these problems.....

    ok now some info on the problem. I have an Intel 3945ABG chipset. knetworkmanager shows no available networks. However when I open a shell and issue the command: iwlist wlan0 scan, I can see my network. That's odd.

    I can manually create a new entry and provide the essid and encryption details (WPA2 psk) in knetworkmanager, but it still doesn't connect. I have the system log entries at the end of the post if it interests anyone. I have tried disabling encryption altogether, still doesn't connect...

    I read a post about installing wicd. I followed the instructions and added a software source in Adept for apt.wicd.net, but I can not find the package wicd. So I couldn't try that either. I tried kwlan, no result. Tried switching to another channel (11 -> 9), still nothing. Now I have run out of options.

    I don't like the general look & feel of 8.10 that much, so I'll have no regrets downgrading to 8.04, and perhaps try again later when all the bugs in 8.10 have been ironed out. But you never know, let's give this a try. If anyone has a tip for making this wifi working again under 8.10, I'll be much obliged.

    =================================================
    the log entries:

    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0) starting connection 'DV201AM'
    2008-11-23 21:34:01 qlt297 NetworkManager <info> (wlan0): device state change: 3 -> 4
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    2008-11-23 21:34:01 qlt297 NetworkManager <info> (wlan0): device state change: 4 -> 5
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0/wireless): access point 'DV201AM' has security, but secrets are required.
    2008-11-23 21:34:01 qlt297 NetworkManager <info> (wlan0): device state change: 5 -> 6
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    2008-11-23 21:34:01 qlt297 NetworkManager <info> (wlan0): device state change: 6 -> 4
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    2008-11-23 21:34:01 qlt297 NetworkManager <info> (wlan0): device state change: 4 -> 5
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0/wireless): connection 'DV201AM' has security, and secrets exist. No new secrets needed.
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Config: added 'ssid' value 'DV201AM'
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Config: added 'scan_ssid' value '1'
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Config: added 'key_mgmt' value 'WPA-PSK'
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Config: added 'psk' value '<omitted>'
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Config: added 'proto' value 'WPA RSN'
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Config: added 'pairwise' value 'TKIP CCMP'
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Config: added 'group' value 'TKIP CCMP'
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    2008-11-23 21:34:01 qlt297 NetworkManager <info> Config: set interface ap_scan to 1
    2008-11-23 21:34:01 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 0 -> 2
    2008-11-23 21:34:02 qlt297 kernel [ 2609.327371] wlan0: authenticate with AP 00:1a:92:67:d4:e3
    2008-11-23 21:34:02 qlt297 kernel [ 2609.329472] wlan0: authenticated
    2008-11-23 21:34:02 qlt297 kernel [ 2609.329481] wlan0: associate with AP 00:1a:92:67:d4:e3
    2008-11-23 21:34:02 qlt297 kernel [ 2609.331894] wlan0: RX AssocResp from 00:1a:92:67:d4:e3 (capab=0x411 status=0 aid=1)
    2008-11-23 21:34:02 qlt297 kernel [ 2609.331903] wlan0: associated
    2008-11-23 21:34:02 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 2 -> 3
    2008-11-23 21:34:02 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 3 -> 0
    2008-11-23 21:34:02 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 0 -> 4
    2008-11-23 21:34:02 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 4 -> 5
    2008-11-23 21:34:06 qlt297 kernel [ 2613.323231] wlan0: deauthenticated
    2008-11-23 21:34:06 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 5 -> 0
    2008-11-23 21:34:07 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 0 -> 2
    2008-11-23 21:34:07 qlt297 kernel [ 2614.320109] wlan0: authenticate with AP 00:1a:92:67:d4:e3
    2008-11-23 21:34:07 qlt297 kernel [ 2614.322034] wlan0: authenticated
    2008-11-23 21:34:07 qlt297 kernel [ 2614.322048] wlan0: associate with AP 00:1a:92:67:d4:e3
    2008-11-23 21:34:07 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 2 -> 4
    2008-11-23 21:34:07 qlt297 kernel [ 2614.324494] wlan0: RX ReassocResp from 00:1a:92:67:d4:e3 (capab=0x411 status=0 aid=1)
    2008-11-23 21:34:07 qlt297 kernel [ 2614.324501] wlan0: associated
    2008-11-23 21:34:07 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 4 -> 5
    2008-11-23 21:34:11 qlt297 kernel [ 2618.313571] wlan0: deauthenticated
    2008-11-23 21:34:11 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 5 -> 0
    2008-11-23 21:34:12 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 0 -> 2
    2008-11-23 21:34:12 qlt297 kernel [ 2619.312093] wlan0: authenticate with AP 00:1a:92:67:d4:e3
    2008-11-23 21:34:12 qlt297 kernel [ 2619.314028] wlan0: authenticated
    2008-11-23 21:34:12 qlt297 kernel [ 2619.314042] wlan0: associate with AP 00:1a:92:67:d4:e3
    2008-11-23 21:34:12 qlt297 kernel [ 2619.316418] wlan0: RX ReassocResp from 00:1a:92:67:d4:e3 (capab=0x411 status=0 aid=1)
    2008-11-23 21:34:12 qlt297 kernel [ 2619.316433] wlan0: associated
    2008-11-23 21:34:12 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 2 -> 4
    2008-11-23 21:34:12 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 4 -> 5
    2008-11-23 21:34:16 qlt297 kernel [ 2623.302963] wlan0: deauthenticated
    2008-11-23 21:34:16 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 5 -> 0
    2008-11-23 21:34:17 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 0 -> 2
    2008-11-23 21:34:17 qlt297 kernel [ 2624.300182] wlan0: authenticate with AP 00:1a:92:67:d4:e3
    2008-11-23 21:34:17 qlt297 kernel [ 2624.302038] wlan0: authenticated
    2008-11-23 21:34:17 qlt297 kernel [ 2624.302051] wlan0: associate with AP 00:1a:92:67:d4:e3
    2008-11-23 21:34:17 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 2 -> 4
    2008-11-23 21:34:17 qlt297 kernel [ 2624.304519] wlan0: RX ReassocResp from 00:1a:92:67:d4:e3 (capab=0x411 status=0 aid=1)
    2008-11-23 21:34:17 qlt297 kernel [ 2624.304526] wlan0: associated
    2008-11-23 21:34:17 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 4 -> 5
    2008-11-23 21:34:17 qlt297 NetworkManager <info> wlan0: link timed out.
    2008-11-23 21:34:21 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 5 -> 0
    2008-11-23 21:34:21 qlt297 kernel [ 2628.293151] wlan0: deauthenticated
    2008-11-23 21:34:22 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 0 -> 2
    2008-11-23 21:34:22 qlt297 kernel [ 2629.292107] wlan0: authenticate with AP 00:1a:92:67:d4:e3
    2008-11-23 21:34:22 qlt297 kernel [ 2629.294089] wlan0: authenticated
    2008-11-23 21:34:22 qlt297 kernel [ 2629.294098] wlan0: associate with AP 00:1a:92:67:d4:e3
    2008-11-23 21:34:22 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 2 -> 4
    2008-11-23 21:34:22 qlt297 kernel [ 2629.296511] wlan0: RX ReassocResp from 00:1a:92:67:d4:e3 (capab=0x411 status=0 aid=1)
    2008-11-23 21:34:22 qlt297 kernel [ 2629.296518] wlan0: associated
    2008-11-23 21:34:22 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 4 -> 5
    2008-11-23 21:34:26 qlt297 NetworkManager <info> Activation (wlan0/wireless): association took too long.
    2008-11-23 21:34:26 qlt297 NetworkManager <info> (wlan0): device state change: 5 -> 6
    2008-11-23 21:34:26 qlt297 NetworkManager <info> Activation (wlan0/wireless): asking for new secrets
    2008-11-23 21:34:26 qlt297 kernel [ 2633.237478] wlan0: disassociating by local choice (reason=3)
    2008-11-23 21:34:26 qlt297 NetworkManager <info> (wlan0): supplicant connection state change: 5 -> 0
    2008-11-23 21:34:26 qlt297 NetworkManager <WARN> get_secrets_cb(): Couldn't get connection secrets: Requested setting is empty.
    2008-11-23 21:34:26 qlt297 NetworkManager <info> (wlan0): device state change: 6 -> 9
    2008-11-23 21:34:26 qlt297 NetworkManager <info> Activation (wlan0) failed for access point (DV201AM)
    2008-11-23 21:34:26 qlt297 NetworkManager <info> Marking connection 'DV201AM' invalid.
    2008-11-23 21:34:26 qlt297 NetworkManager <info> Activation (wlan0) failed.
    2008-11-23 21:34:26 qlt297 NetworkManager <info> (wlan0): device state change: 9 -> 3
    2008-11-23 21:34:26 qlt297 NetworkManager <info> (wlan0): deactivating device (reason: 0).
    Tags: None
    • Top
    • Bottom
    #2
    Re: Wifi won't connect after upgrade hardy --&gt; intrepid

    I had this problem with my wife's toshiba laptop. It is not intel chipset but the symptoms are the same. This link helped me fix her's.

    http://unsharptech.com/2008/10/31/at...intrepid-ibex/

    David
    • Top
    • Bottom

    Comment

      #3
      Re: Wifi won't connect after upgrade hardy --&gt; intrepid

      Thanks David, I read the page, and it seems to apply to the Atheros chipset only. I'll try that as a last resort.
      • Top
      • Bottom

      Comment

        #4
        Re: Wifi won't connect after upgrade hardy --&gt; intrepid

        Well i was in the same boat for a while. I am not so sure what I did to fix the issue but I am working now. I have installed may of the tip I have read and none of them worked. How I did get it working was this, run the live cd (you should connect with the live cd) get connected to the internet then install.

        Once installed the wifi was working but only at 1/2 the strength. This is the best I could get for some time. If I reconnected to my wifi after a full boot I would get 90% and that was normal under 8.4, and XP. But what I do now is use my keyboard fn key to turn off the wifi and then back on and I am good.

        I am not so sure it is a kernel issue as under Ubuntu 8.10 it works fine, I think it is some thing in KDE that is not working.

        If I were you I would do a clean install with the wifi connected first.

        Noel Vh
        ++Noel Vh++<br />Desktop support Lv II, III<br />Large Pharma company<br />New Jersey USA
        • Top
        • Bottom

        Comment

          #5
          Re: Wifi won't connect after upgrade hardy --&gt; intrepid

          Originally posted by Anne8946
          Thanks David, I read the page, and it seems to apply to the Atheros chipset only. I'll try that as a last resort.
          Cool. I just mentioned this as her symptoms were almost identical. It would see my network. If I gave a manual ip wicd would report attached to "my lan" with 0db. As soon as I installed the mentioned backport .deb things worked.

          D 8)
          • Top
          • Bottom

          Comment

            #6
            Re: Wifi won't connect after upgrade hardy --&gt; intrepid

            Noel,

            Thanks for the tip. I just finished downloading & burning the 8.10 cd, you guess: wifi works without a hitch!

            This got me baffled though, because what is different on the cd? It's both 8.10, same stuff you would think.

            How to proceed now? Can I somehow copy the settings of the live cd to my installed version on the hd? What can I compare to see what the issue is?
            • Top
            • Bottom

            Comment

              #7
              Re: Wifi won't connect after upgrade hardy --&gt; intrepid

              I am just as confused as you. In doing some reading it looks like there are some backports on the CD than can be used, but I have not tried that. Currently I am OK with how my wifi works, and I spent soooo much time on it I have given in to the fact I have to reconnect my wifi once the OS has booted. It only takes a few sec more to do so.

              What I did see in mandriva was the wifi would connect before KDE loaded, this I would like to see happen in KB. This way all of my Smb4k mounts would mount on startup.

              So dose any one if this is possible, I mean to have the wifi connect before the x server starts??

              Noel Vh
              ++Noel Vh++<br />Desktop support Lv II, III<br />Large Pharma company<br />New Jersey USA
              • Top
              • Bottom

              Comment

                #8
                Re: Wifi won't connect after upgrade hardy --&gt; intrepid

                Last update. Wifi is working now. Scary thing is I don't know what got it working. When I chose new connection yesterday, it suddenly showed a list of networks in range, and after that I only had to enter my WPA key and it worked.

                The only thing I can think of was de-installing knetworkconf, since that wasn't being used on the live cd too.

                Thanks for the help.
                • Top
                • Bottom

                Comment

                Previous template Next
                Working...
                X