Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #51997 > unrolled thread

Mavericks/WiFi problem

Back to article view | Back to comp.sys.mac.system

Contents

  Mavericks/WiFi problem Ted Lee <tmplee@mr.net> - 2013-11-07 12:17 -0600
    Re: Mavericks/WiFi problem Ted Lee <tmplee@mr.net> - 2013-11-07 13:26 -0600
      Re: Mavericks/WiFi problem Jolly Roger <jollyroger@pobox.com> - 2013-11-07 19:36 +0000
        Re: Mavericks/WiFi problem Ted Lee <tmplee@mr.net> - 2013-11-07 13:41 -0600
        Re: Mavericks/WiFi problem Ted Lee <tmplee@mr.net> - 2013-11-07 15:03 -0600
          Re: Mavericks/WiFi problem Jolly Roger <jollyroger@pobox.com> - 2013-11-09 04:12 +0000
            Re: Mavericks/WiFi problem Ted Lee <tmplee@mr.net> - 2013-11-08 22:38 -0600
              Re: Mavericks/WiFi problem Jolly Roger <jollyroger@pobox.com> - 2013-11-10 01:49 +0000
                Re: Mavericks/WiFi problem Ted Lee <tmplee@mr.net> - 2013-11-09 21:04 -0600
      Re: Mavericks/WiFi problem Barry Margolin <barmar@alum.mit.edu> - 2013-11-07 14:37 -0500
    Re: Mavericks/WiFi problem jmm7175@gmail.com - 2013-11-21 19:52 -0800

#51997 — Mavericks/WiFi problem

My 13" MacBookPro retina wifi has developed a problem since I upgraded 
to Mavericks.  Previously when it woke up from sleep it would find my 
network(s) immediately.  Now, it has trouble finding my networks, and 
even if it does find one of them it may not show the others for awhile. 
  (I have a wifi-g on one router and two wifi-n's (low band and high 
band) on another.  I've noticed that it sometimes stops the periodic 
"looking for networks" scan.  If I turn wifi off and on that sometimes 
fixes it.  It also seems to fix it (sometimes) by restarting.  One time 
I tried trashing the airport prefs and that seemed to fix it (for 
awhile) but it may just have been the restart afterwards.  As soon as I 
can figure out how to revert to my previous system (Mountain Lion, which 
should be in the Time Machine backups) without losing the work I've done 
since, I'll check to see if it really is the software upgrade or a 
hardware problem.

Anyone else seen a similar problem?  (I've some some threads that talk 
about wifi problems after Mavericks, but they don't sound the same.)

Ted

[toc] | [next] | [standalone]

#52004

On 11/7/13, 12:17 PM, Ted Lee wrote:
> As soon as I can figure out how to revert to my previous system
> (Mountain Lion, which should be in the Time Machine backups) without
> losing the work I've done since, I'll check to see if it really is the
> software upgrade or a hardware problem.

OK, read up some on restoring a system from backup and it looks both 
messy enough and risky enough I'm not going to bother.  It definitely 
looks like there's no easy way to say "restore only the OS; keep the 
data as is."  I'll live with it the way it is (it works well once 
connected, even if I may have to click a few times to get it connected) 
and wait to see if it improves after the next release.

I suppose I could restore mountain lion to a spare partition on one of 
my external drives and boot from that just to see how things work, but 
even that sounds problematical.

Ted

[toc] | [prev] | [next] | [standalone]

#52007

On 2013-11-07, Ted Lee <tmplee@mr.net> wrote:
> On 11/7/13, 12:17 PM, Ted Lee wrote:
>> As soon as I can figure out how to revert to my previous system
>> (Mountain Lion, which should be in the Time Machine backups) without
>> losing the work I've done since, I'll check to see if it really is the
>> software upgrade or a hardware problem.
>
> OK, read up some on restoring a system from backup and it looks both 
> messy enough and risky enough I'm not going to bother.  It definitely 
> looks like there's no easy way to say "restore only the OS; keep the 
> data as is."  I'll live with it the way it is (it works well once 
> connected, even if I may have to click a few times to get it connected) 
> and wait to see if it improves after the next release.
>
> I suppose I could restore mountain lion to a spare partition on one of 
> my external drives and boot from that just to see how things work, but 
> even that sounds problematical.

I think if I were in this position, I  would try going into System
Preferences > Network, clicking the Location menu, and creating a new
location with settings that mimic the location you are currently using.
Then switch to that location and restart to see if things get better.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#52009

On 11/7/13, 1:36 PM, Jolly Roger wrote:
> I think if I were in this position, I  would try going into System
> Preferences > Network, clicking the Location menu, and creating a new
> location with settings that mimic the location you are currently using.
> Then switch to that location and restart to see if things get better.

I tried that (just duplicated Automatic and tried the duplicate.)
I thought it helped, but then the behavior reverted to misbehaving.
I suppose if there were some kind of errors in the "Automatic" location 
they would just have been duplicated, so it's worth just trying a brand 
new location.  As I recall there aren't any interesting settings that 
I'm using (like a static IP or routing info or such.)

Ted

[toc] | [prev] | [next] | [standalone]

#52025

On 11/7/13, 1:36 PM, Jolly Roger wrote:
> I think if I were in this position, I  would try going into System
> Preferences > Network, clicking the Location menu, and creating a new
> location with settings that mimic the location you are currently using.
> Then switch to that location and restart to see if things get better.
That actually does seem to have sort of fixed it (making a new location, 
not duplicating the existing one.)
I've tried the sleep/wake cycle several times now and it has immediately 
come up connected to the network I want.
On the other hand, it is *not* looking for networks, so the only network 
it's showing is the one I was on.  Turning wifi off and on doesn't get 
it going looking for networks.  On the other other hand, while I was 
typing this apparently it did find the other networks -- I suppose its 
cycle for looking for networks is now a lot longer once it got connected 
to one, or something like that.  Yup, restarted and now it has resumed 
the behavior of looking for networks once every 10 seconds or so -- it 
definitely was not looking at all that frequently before the restart.  
It'll be interesting to see if the "right" behavior continues (I hadn't 
done a restart  after doing the location switch.)

Ted

[toc] | [prev] | [next] | [standalone]

#52079

On 2013-11-07, Ted Lee <tmplee@mr.net> wrote:
> On 11/7/13, 1:36 PM, Jolly Roger wrote:
>> I think if I were in this position, I  would try going into System
>> Preferences > Network, clicking the Location menu, and creating a new
>> location with settings that mimic the location you are currently using.
>> Then switch to that location and restart to see if things get better.
> That actually does seem to have sort of fixed it (making a new location, 
> not duplicating the existing one.)
> I've tried the sleep/wake cycle several times now and it has immediately 
> come up connected to the network I want.
> On the other hand, it is *not* looking for networks, so the only network 
> it's showing is the one I was on.  Turning wifi off and on doesn't get 
> it going looking for networks.  On the other other hand, while I was 
> typing this apparently it did find the other networks -- I suppose its 
> cycle for looking for networks is now a lot longer once it got connected 
> to one, or something like that.  Yup, restarted and now it has resumed 
> the behavior of looking for networks once every 10 seconds or so -- it 
> definitely was not looking at all that frequently before the restart.  
> It'll be interesting to see if the "right" behavior continues (I hadn't 
> done a restart  after doing the location switch.)

Let us know!

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#52082

On 11/8/13, 10:12 PM, Jolly Roger wrote:
> On 2013-11-07, Ted Lee <tmplee@mr.net> wrote:
>> On 11/7/13, 1:36 PM, Jolly Roger wrote:
>>> I think if I were in this position, I  would try going into System
>>> Preferences > Network, clicking the Location menu, and creating a new
>>> location with settings that mimic the location you are currently using.
>>> Then switch to that location and restart to see if things get better.
>> That actually does seem to have sort of fixed it (making a new location,
>> not duplicating the existing one.)
>> I've tried the sleep/wake cycle several times now and it has immediately
>> come up connected to the network I want.
>> On the other hand, it is *not* looking for networks, so the only network
>> it's showing is the one I was on.  Turning wifi off and on doesn't get
>> it going looking for networks.  On the other other hand, while I was
>> typing this apparently it did find the other networks -- I suppose its
>> cycle for looking for networks is now a lot longer once it got connected
>> to one, or something like that.  Yup, restarted and now it has resumed
>> the behavior of looking for networks once every 10 seconds or so -- it
>> definitely was not looking at all that frequently before the restart.
>> It'll be interesting to see if the "right" behavior continues (I hadn't
>> done a restart  after doing the location switch.)
>
> Let us know!
>

No change from the above.  It does seem fairly consistently now to find 
my preferred network right away after a sleep/wake cycle.  At first it 
will show  "looking for network" every 10 seconds or so if I pull down 
the wifi menulet.  After a while (minutes?) it will stop doing that.  It 
will then still immediately find my preferred network after a sleep, but 
it won't resume the "looking for a network".  Turning wifi off/on 
doesn't start it looking, but a restart does.  Basically now I'm a happy 
but puzzled camper.

Ted

[toc] | [prev] | [next] | [standalone]

#52091

On 2013-11-09, Ted Lee <tmplee@mr.net> wrote:
> On 11/8/13, 10:12 PM, Jolly Roger wrote:
>> On 2013-11-07, Ted Lee <tmplee@mr.net> wrote:
>>> On 11/7/13, 1:36 PM, Jolly Roger wrote:
>>>> I think if I were in this position, I  would try going into System
>>>> Preferences > Network, clicking the Location menu, and creating a new
>>>> location with settings that mimic the location you are currently using.
>>>> Then switch to that location and restart to see if things get better.
>>> That actually does seem to have sort of fixed it (making a new location,
>>> not duplicating the existing one.)
>>> I've tried the sleep/wake cycle several times now and it has immediately
>>> come up connected to the network I want.
>>> On the other hand, it is *not* looking for networks, so the only network
>>> it's showing is the one I was on.  Turning wifi off and on doesn't get
>>> it going looking for networks.  On the other other hand, while I was
>>> typing this apparently it did find the other networks -- I suppose its
>>> cycle for looking for networks is now a lot longer once it got connected
>>> to one, or something like that.  Yup, restarted and now it has resumed
>>> the behavior of looking for networks once every 10 seconds or so -- it
>>> definitely was not looking at all that frequently before the restart.
>>> It'll be interesting to see if the "right" behavior continues (I hadn't
>>> done a restart  after doing the location switch.)
>>
>> Let us know!
>>
>
> No change from the above.  It does seem fairly consistently now to find 
> my preferred network right away after a sleep/wake cycle.  At first it 
> will show  "looking for network" every 10 seconds or so if I pull down 
> the wifi menulet.  After a while (minutes?) it will stop doing that.  It 
> will then still immediately find my preferred network after a sleep, but 
> it won't resume the "looking for a network".  Turning wifi off/on 
> doesn't start it looking, but a restart does.  Basically now I'm a happy 
> but puzzled camper.

Glad you got at least part of the issue resolved. I would try resetting
the SMC to see if that gets you closer to expected behavior:

<http://support.apple.com/kb/HT3964>

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#52094

On 11/9/13, 7:49 PM, Jolly Roger wrote:
> Glad you got at least part of the issue resolved. I would try resetting
> the SMC to see if that gets you closer to expected behavior:
>
> <http://support.apple.com/kb/HT3964>
>

It doesn't look like my symptoms are at all related to the SMC.  It's 
something to do with the airport software, I think.  I hesitate to do 
something as drastic as resetting the SMC when everything it seems to 
have anything to do with is fine.

But thanks for the suggestion.

Ted

[toc] | [prev] | [next] | [standalone]

#52008

In article <l5gph8$cna$1@dont-email.me>, Ted Lee <tmplee@mr.net> wrote:

> On 11/7/13, 12:17 PM, Ted Lee wrote:
> > As soon as I can figure out how to revert to my previous system
> > (Mountain Lion, which should be in the Time Machine backups) without
> > losing the work I've done since, I'll check to see if it really is the
> > software upgrade or a hardware problem.
> 
> OK, read up some on restoring a system from backup and it looks both 
> messy enough and risky enough I'm not going to bother.  It definitely 
> looks like there's no easy way to say "restore only the OS; keep the 
> data as is."

That tends to be difficult, because when you revert the OS, you also 
often have to downgrade to the older versions of Apple applications. But 
they may have written data in new formats that the old versions don't 
understand.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

[toc] | [prev] | [next] | [standalone]

#52503

I just worked with an apple support rep yesterday to try and isolate the problem.  He had me do a safe boot (hold down shift while starting up) and in safe boot the problem did not happen.  When we went back to normal boot, the problem returned.  After some further investigation, we narrowed it down to Google Drive.  As soon as I uninstalled it, my wifi went back to normal.  This may have been just me, but I thought I would share just in case.  

Jason

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.mac.system

csiph-web