Welcome to the MacNN Forums.

Zappppit · Jun 7, 2002, 05:49 AM

Hi,

MacOS X 10.1.5 INTRODUCED a NEW (and big) BUG in the kernel in the support of KeyLargo controllers used in a tons of Macs (Powerbook Pismos and the first G4s and MANY others).

The kernel is unable to re-inizialize KeyLargo after Sleep, to be more precise below a Log output from system.log from a Pismo 500 running 10.1.5 (and affected from 'no network after sleep bug):

Jun 7 10:44:46 localhost mach_init[2]: added notification for sub-bootstrap
Jun 7 10:48:55 localhost mach_kernel: AppleNMI mask NMI
Jun 7 10:59:56 localhost mach_kernel: UniNEnet: 0 0 UniNEnet:

utToSleep - disabled cell clock!!!
Jun 7 10:59:56 localhost mach_kernel: KeyLargo:

owerMediaBay(FALSE) 0x00
Jun 7 10:59:56 localhost mach_kernel: System Sleep
Jun 7 10:59:56 localhost mach_kernel: System Wake
Jun 7 10:59:56 localhost mach_kernel: Wake event 0001
Jun 7 10:59:56 localhost mach_kernel: AppleNMI unmask NMI
Jun 7 10:59:56 localhost mach_kernel: KeyLargo:

owerMediaBay(TRUE) 0x02
Jun 7 10:59:56 localhost mach_kernel: ADB present:8c
Jun 7 10:59:56 localhost mach_kernel: IOKernelDebugger: Unable to re-enable controller
Jun 7 10:59:56 localhost configd[124]: executing /System/Library/SystemConfiguration/Kicker.bundle/Resources/restart-AppleTalk
Jun 7 10:59:57 localhost configd[124]: executing /System/Library/SystemConfiguration/Kicker.bundle/Resources/restart-NetInfo
Jun 7 10:59:57 localhost configd[124]: executing /System/Library/SystemConfiguration/Kicker.bundle/Resources/set-hostname
Jun 7 10:59:57 localhost configd[124]: executing /System/Library/SystemConfiguration/Kicker.bundle/Resources/restart-lookupd
Jun 7 10:59:57 localhost lookupd[211]: Caught SIGHUP - reset
Jun 7 10:59:57 localhost configd[124]: executing /System/Library/SystemConfiguration/Kicker.bundle/Resources/restart-automount
Jun 7 11:00:34 localhost kextd[41]: loading module: com.apple.driver.AppleUSBComposite.

The line "Jun 7 10:59:56 localhost mach_kernel: IOKernelDebugger: Unable to re-enable controller" is the problem and this was not there using 10.1.4.

Also, using "sudo ifconfig en0 inet up" (the force to enable again the en0) command give often input/output errors before work.

The problems sems are all caused by a bug in the Kernel for KeyLargo support, and in my opinion 10.1.5 can cause also a lot of problems (see kernel panic and general stability iusses), and the networks problems after wakeup are only a consequence of this bug.

Marc

[ 06-07-2002, 05:52 AM: Message edited by: Zappppit ]

macrophyllum · Jun 7, 2002, 11:32 AM

So is there any hack to get the no networking after sleep fixed? Or do we have to wait for another update? Or even better, is there any easy way to downgrade back to 10.1.4?

bemayo · Jun 7, 2002, 11:55 AM

I have had this problem with my DP533 for as long as I remember. Since I hadn't heard anybody else complaining about it, I had assumed it had to do with my cable provider. Any other DP users with this issue before?

AppleCello · Jun 7, 2002, 11:56 AM

I dont want to downgrade to 10.1.4! I like the new eject symbol that appears then fades when I open or close my CD drive

Kristoff · Jun 7, 2002, 12:25 PM

Hmmm..I don't seem to have that problem on my Pismo 500.

But, I do know that in 10.1.4, I used to get the same IP all the time from my DHCP server.
In 10.1.5, it does a first come first serve.
I don't know if that's because in 10.1.4 it never cancelled it's lease, thereby sort-of waiting for the DHCP server to time them out.

It's almost as if when you put a machine to sleep in 10.1.5, it cancels it's lease just prior to sleep. Therefore the DHCP server gives that IP to whatever the next guy to come along.

For example:
in 10.1.4
QS would always get 192.168.1.100
Cube would always get 192.168.1.101
Linux would always get 192.168.1.102
Base Station would always get 192.168.1.103
PowerBook would always get 192.168.1.104

Which was nice because I put /machines entries in NetInfo for name resolution.
But, in 10.1.15, they get whatever is the lowest available.
So, I switched to static IPs.

jguidroz · Jun 7, 2002, 01:43 PM

Interesting, but my Pismo 500 does not lose a network connection after sleep. Of course I am using static ip addresses.

Elly · Jun 7, 2002, 02:41 PM

In 10.1.5, with a Cable connection with attbi, I do NOT loose my network connection after deep sleep, and I am keeping my DHCP lease, with the same IP since their network migration in Dec.

G4 450 AGP
MacSense MIH-130 XRouter Pro

MS · Jun 7, 2002, 03:00 PM

This has happened to me ever since I stepped into the world of X, and Comcast switched over to DHCP instead of a static IP. I never put my machine to sleep anymore due to this reason. I would have to reboot to connect to the internet again.

MS

Yoda's Erotic Piggyback · Jun 7, 2002, 04:50 PM

This problem is new for me since 10.1.5. I hope Apple comes out with a fix ASAP as I can't downgrade.

AKcrab · Jun 7, 2002, 06:10 PM

A supposed fix for the lost connection on wake:
Go to energy saver prefs, set sleep to never, restart.
Go back to energy saver prefs, reset your sleep setting however you like.

I plan on trying when I get home.

awaspaas · Jun 7, 2002, 08:02 PM

<blockquote>quote:<hr />Originally posted by AKcrab:
A supposed fix for the lost connection on wake:
Go to energy saver prefs, set sleep to never, restart.
Go back to energy saver prefs, reset your sleep setting however you like.

I plan on trying when I get home.<hr /></blockquote>... but what if it was already on sleep never?

Norm1985 · Jun 7, 2002, 08:02 PM

Yeah, the problem was introduced for me on my Power Mac G4 450DP with 10.1.5.

I haven't really worked on my PowerBook 550 Combo since the update though, so I don't know about that.

Back up 15 and punt · Jun 7, 2002, 09:52 PM

I run a Power Mac G4 450 DP and this has never been an issue. I am currently using attbi.com as my ISP. I'm wondering what the differences are:

Norm1985 · Jun 7, 2002, 11:23 PM

I also have attibi.com has my ISP.

applenut1 · Jun 7, 2002, 11:30 PM

never had the problem. then I did a clean OS X install and updated to 10.1.4 a few months ago and had that problem for a while. if you leave the computer alone after waking up it'll work but you have to wait and not try to use the connection.

then I got a new hard drive did another clean install to 10.1.4 and it works fine like it used to. 10.1.5 works fine as well

AKcrab · Jun 8, 2002, 12:12 AM

<blockquote>quote:<hr />Originally posted by awaspaas:
 <blockquote>quote:<hr />Originally posted by AKcrab:
A supposed fix for the lost connection on wake:
Go to energy saver prefs, set sleep to never, restart.
Go back to energy saver prefs, reset your sleep setting however you like.

I plan on trying when I get home.<hr /></blockquote>... but what if it was already on sleep never?

<hr /></blockquote>Yep. Didn't work for me. Don't know what's next.

awaspaas · Jun 8, 2002, 12:26 AM

hey, I'm with attbi.com too... anybody else?

mrchin · Jun 8, 2002, 12:59 AM

comcast cable here. Doesn't work after sleep for me on 867.

HouseSold · Jun 8, 2002, 01:04 AM

Same behavior from sleep in Virtual PC 5.03 if sleeping while plugged into the network, except a dimmed screen and only the cursor visible when trying to wake.

Only way out (or in) was to quit and wait 30 seconds (would reset sometimes) or force quit back to OSX desktop then restart windows in Virtual PC upon startup (automatic in VPC 5.03 after force quit or quit without saving image)

bummer

Ideas?

Powerbook G4 DVI 800

Back up 15 and punt · Jun 8, 2002, 01:52 AM

The only sleep issue I've been experiencing is that I occasionally have my machine freeze upon waking up. This has happened to me twice today and I'm sure what is causing it. The only recourse I have when this occurs is to reboot.

V0ID · Jun 8, 2002, 02:56 AM

Happens to me on a pismo 400. The set sleep to never, restart, then set sleep to your preference didn't work for me either. What did work was to change my IP address (i'm not using DHCP) then click "Apply Now". I've only tried this once.

When my network does go, typing "netstat -r" in the terminal shows that all my routing information has disappeared.

hmr · Jun 8, 2002, 08:37 AM

I have a Pismo 400 and I'm also affected by this bug. If it will not be fixed soon, I'll have to "downgrade" to 10.1.4 (pain, because I bought the Mac OS 10 CD and received the 10.1 update...)

I have an ADSL connection, and this works for me to get the network back on after sleep:

1. Open System Preferences.
2. Choose Network, and from the pop-up menu: Active Network Ports.
3. Untick whatever Port Connection you're using.
4. Tick something you're not using [AirPort in my case].
5. Press Apply Now.
6. Untick what you ticked in step 4.
7. Tick the Port Connection you'd like to use.
8. Press Apply Now.

This seems to work for me most of the time.

[ 06-08-2002, 08:39 AM: Message edited by: hmr ]

g. olson · Jun 8, 2002, 11:50 AM

Just a note: Quicksilver 733 G4: no problem with DHCP cable connection after sleep, iBook 600mhz: also no problem with 10.1.5

theolein · Jun 8, 2002, 01:13 PM

I have this bug intermittently i.e. not after every sleep.
Config:Lombard G3 333MHz 10.1.5, Cable modem.
I have already sent in a bug report to apple.
One thing you could try is open the terminal and type in the following:
sudo lookupd -flushcache
or
sudo kill -1 <lookupd's PID> to cause it to hang up

Looking in the logs I see the dns-query timeout messages, many of them. I guess the problem has to do with a memory leak somewhere, but not being familiar with the sleep mechanism, I don't really know.

SupahCoolX · Jun 9, 2002, 03:29 AM

I noticed a similar problem lately, and realized just now that it started when I -upgraded- my iBook 600 to 10.1.5 (CableVision/Optimum Online, DHCP). The fix for me is to just unplug/replug the ethernet cable when I wake the iBook up. Not terribly difficult, but an unnecessary annoyance nonetheless.

Eug · Jun 9, 2002, 08:49 AM

I don't seem to have this problem on my iBook 600. OTOH, I don't often use Ethernet - mainly wireless for me.

By the way, I was told to find the Ethernet ID in the Terminal I should just type "lmhostid". It does not work however.

theolein · Jun 9, 2002, 11:26 AM

I just noticed that /usr/sbin/lookupd was indeed modified by the update to 10.1.5. I have a sneaking suspicion that the problem indeed lies here. In /System/Library/SystemConfiguration/there is a bundle called Kicker.bundle. Inside this bundle there is a programme called Kicker and inside it's Resources directory there is an executable restart_lookupd. You could perhaps try running this and see if it does anything good.

bil207 · Jun 9, 2002, 12:51 PM

I have the problem with losing the network connection and settings when I wake my G4 533 DP from sleep. I first noticed this on my primary hard drive and also on a second hard drive that was brand new and formatted (zeroed all data). I installed OS 10.1 from the cd and then applied all the OS X updates to get to 10.1.5. This installation had no 3rd party software and still lost the Network settings and connections when it woke from sleep requiring a reboot to get the connection back.

I have disconnected all USB devices,removed the added ram, removed the second hard drive, reformatted the new drive a second time and reinstalled OS 10.1. and updated to 10.1.5 again and the problem still persists.

awaspaas · Jun 9, 2002, 01:27 PM

<blockquote>quote:<hr />Originally posted by theolein:
When NASA first started sending up astronauts, they quickly discovered that ballpoint pens would not work in zero gravity. To combat the problem, NASA scientists spent a decade and $12 Billion to develop a pen that writes in zero gravity, upside down, underwater, on almost any surface including glass and at temperatures ranging from below freezing to 300C. The Russians used a pencil.
<hr /></blockquote>Sorry its OT, but here's how the space pen was *really* developed:

In the 1950's there were dozens of ballpoint models, and nearly every one took a different cartridge. In 1953 Fisher invented the "Universal Refill" which could be used in most pens. It was a good seller, since stationery store owners could reduce their stock of assorted refills.

Not content, Fisher continued to work on making a better refill. After much experimentation he perfected a refill using thixotropic ink-semisolid until the shearing action of the rolling ball liquefied it-that would flow only when needed. The cartridge was pressurized with nitrogen so that it didn't rely on gravity to make it work. It was dependable in freezing cold and desert heat. It could also write underwater and upside down. The trick was to have the ink flow when you wanted it to, and not to flow the rest of the time, a problem Fisher solved. Fisher's development couldn't have come at a more opportune time. The space race was on, and the astronauts involved in the Mercury and Gemini missions had been using pencils to take notes in space since standard ball points did not work in zero gravity. The Fisher cartridge did work in the weightlessness of outer space and the astronauts, beginning with the October, 1968 Apollo 7 mission began using the Fisher AG-7 Space Pen and cartridge developed in 1966.

sinebubble · Jun 9, 2002, 02:40 PM

I have a Pismo 500 and I'm experiencing the same loss of networking when it wakes up. However, about 1/3 of the time that I reboot, the networking does not initialize. The system.log doesn't say much other than failing to note that the interface is up and then various network related tools start to timeout or fail to initialize from there.

I am using DHCP as well and this started with 10.1.5.

theolein · Jun 9, 2002, 02:45 PM

<blockquote>quote:<hr />Originally posted by awaspaas:
Sorry its OT, but here's how the space pen was *really* developed:

In the 1950's there were dozens of ballpoint models, and nearly every one took a different cartridge. In 1953 Fisher invented the "Universal Refill" which could be used in most pens. It was a good seller, since stationery store owners could reduce their stock of assorted refills.

Not content, Fisher continued to work on making a better refill. After much experimentation he perfected a refill using thixotropic ink-semisolid until the shearing action of the rolling ball liquefied it-that would flow only when needed. The cartridge was pressurized with nitrogen so that it didn't rely on gravity to make it work. It was dependable in freezing cold and desert heat. It could also write underwater and upside down. The trick was to have the ink flow when you wanted it to, and not to flow the rest of the time, a problem Fisher solved. Fisher's development couldn't have come at a more opportune time. The space race was on, and the astronauts involved in the Mercury and Gemini missions had been using pencils to take notes in space since standard ball points did not work in zero gravity. The Fisher cartridge did work in the weightlessness of outer space and the astronauts, beginning with the October, 1968 Apollo 7 mission began using the Fisher AG-7 Space Pen and cartridge developed in 1966.<hr /></blockquote>That's a good story. My sig is stolen, to be honest, from someone at /. I mostly didn't want it to be a an anti-NASA or anything kind of sig. I just kind of liked the idea that sometimes enormous amounts of resources can be wasted in basically reinventing the wheel. I could basically have posted something to the tune of not seeing the wood for the trees or something like that.

theolein · Jun 9, 2002, 02:48 PM

Would some of you experiencing this problem of no net after sleep perhaps try restarting the lookupd as I mentioned above. I would be interested to see if it helps.

It could possibly also be a problem with ifconfig I think, since this affects the routing and someone noted that the routing info was gone after sleep. ifconfig has also, like lookupd been changed or modified since 10.1.5

Mac Zealot · Jun 9, 2002, 05:09 PM

Aw so that's a bug? I've had this problem with my computer as long as I can remember.

If I disconnect, and try to reconnect, it won't work until I turn off the machine and turn it back on. Funny but this still happens even after they replaced the logic board in my machine.

theolein · Jun 9, 2002, 06:46 PM

The next time the bug turns up I think that rebooting into single user mode (cmd-s on start)and doing a "/sbin/fsck -y" might fix the problem. I now think that the 10.1.5 install mucks up something in the file system as it changes quite a few Unix tools and changes the mail permissions etc.

AKcrab · Jun 9, 2002, 07:48 PM

<blockquote>quote:<hr />Originally posted by theolein:
The next time the bug turns up I think that rebooting into single user mode (cmd-s on start)and doing a "/sbin/fsck -y" might fix the problem. I now think that the 10.1.5 install mucks up something in the file system as it changes quite a few Unix tools and changes the mail permissions etc.<hr /></blockquote>I tried fsck -y. Didn't do anything for me. (no errors found)

theolein · Jun 9, 2002, 08:02 PM

<blockquote>quote:<hr />Originally posted by AKcrab:
I tried fsck -y. Didn't do anything for me. (no errors found)<hr /></blockquote>Do you still have the no network after sleep problem? If so, did you try restarting lookupd?

AKcrab · Jun 9, 2002, 08:13 PM

<blockquote>quote:<hr />Originally posted by theolein:
 <blockquote>quote:<hr />Originally posted by AKcrab:
I tried fsck -y. Didn't do anything for me. (no errors found)<hr /></blockquote>Do you still have the no network after sleep problem? If so, did you try restarting lookupd?<hr /></blockquote>My 'no network' issue is not nearly as drastic as others. It always reconnects all by itself within about 15 seconds or so, but the fact remains it didn't used to disconnect. People have suggested that this is the way it's always been, but that's just not true. If I was logged in to various services with fire and the system went to sleep, I could come back and would still be connected. This is no longer true. So, I really have no need to restart lookupd, as that doesn't seem to be my issue. Is this perhaps two different issues?

awaspaas · Jun 9, 2002, 11:01 PM

restarting lookupd didnt help.... i even tried doing a sudo shutdown now and relogging in - it seems nothing short of a restart will re-enable my internet <img border="0" title="" alt="[Frown]" src="frown.gif" />

OldManMac · Jun 9, 2002, 11:21 PM

I'm using 10.1.5 on a Time Warner Road Runner cable connection, and I've not experienced this issue.

theolein · Jun 9, 2002, 11:38 PM

<blockquote>quote:<hr />Originally posted by awaspaas:
restarting lookupd didnt help.... i even tried doing a sudo shutdown now and relogging in - it seems nothing short of a restart will re-enable my internet

<hr /></blockquote>Have you looked whether inetd is running?

Calli46 · Jun 9, 2002, 11:45 PM

!0.1.5 did introduce this bug on my system (G4 500DP). Like others, I log on the internet with DHCP on a cable modem. Never got this problem before updating to 10.1.5.

Now, will we have to buy 10.2 to get (possibly) rid of the bug or will Apple issue a 10.1.5.something ?

sinebubble · Jun 10, 2002, 12:41 AM

I put my system to sleep, woke it up and found (no surprise), networking was down. I HUPed lookupd, inetd (don't see what that would accomplish), but no love. I also brought the interface down and then back up. Got an input/output error and no networking. I couldn't even manually configure my networking.

This sucks.

Jun 9 21:26:45 cytosine sudo: brian : TTY=ttyp1 ; PWD=/private/var/log ; USE
R=root ; COMMAND=/sbin/ifconfig en0 up
Jun 9 21:27:23 cytosine configd[121]: DHCP en0: RELEASE transmit failed
Jun 9 21:27:34 cytosine configd[121]: DHCP en0: INIT-REBOT transmit failed

AKcrab · Jun 10, 2002, 04:11 PM

<a href="http://forums.macosxhints.com/showthread.php?s=&threadid=3332" target="_blank">Link</a>
<blockquote>quote:<hr />A potential fix has been posted over at Apple Discussions. It is to replace the AppleGMACEthernet.kext with a copy from pre 10.1.5.
<hr /></blockquote>Anyone wanna try?

theolein · Jun 10, 2002, 05:05 PM

<blockquote>quote:<hr />Originally posted by AKcrab:
<a href="http://forums.macosxhints.com/showthread.php?s=&threadid=3332" target="_blank">Link</a>
<blockquote>quote:<hr />A potential fix has been posted over at Apple Discussions. It is to replace the AppleGMACEthernet.kext with a copy from pre 10.1.5.
<hr /></blockquote>Anyone wanna try?<hr /></blockquote>I don't know if that is such a good idea. 10.1.5 didn't change that extension as far as I know.

dscottbuch · Jun 10, 2002, 10:50 PM

I have this same problem on a pismo 500 with 640MB. It doesn't affect my airport connection I use at home but only the enet connection. Not every time I sleep but it does seem to happen everytime after using the airport connection inbetween.

I found the following on macintouch

Before I go on with my message, MacFixit had this work-around, which I'll try when I get home tonight:

Finally, for those who prefer to work in Terminal, Matthew Stoops offers this work-around (we have not confirmed its success):

1. Type <ifconfig -a> and locate interface that pertains to Ethernet. Notice that en0 (Ethernet) status is inactive and does not have an IP address. 2. Type <sudo ifconfig en0 inet up>. 3. Again type <ifconfig -a> and look at interface entry. The Ethernet port should again be active and will have an IP address associated with it.

I posted the following to the Apple KB Discussion thread:

I'll add my name to the list of people who lose their connection upon sleep.

I'll be trying this tomorrow when I get back to my enet connection.

---Update---

The problem was present when I tried to hook up to my work network. ifconfig showed the interface to be 'UP' but inactive. taking the interface 'DOWN' and then 'UP' did nothing. It again took TWO reboots to fix. The first reboot was a hard reboot.

These seem to be the pertinent system.log files from the first 'Wake'

Jun 11 07:46:45 localhost kextd[41]: loading module: com.apple.driver.AppleUSBKeyboard.
Jun 11 07:46:46 localhost mach_kernel: USBF: 36590.331 AppleUSBKeyboard[0x25a0c00]::start USB Generic Keyboard @ 3 (0x21100
00)
Jun 11 07:46:46 localhost kextd[41]: loading module: com.apple.driver.AppleUSBMouse.
Jun 11 07:46:47 localhost mach_kernel: USBF: 36590.821 AppleUSBMouse[0x357e800]::start - USB Generic Mouse @ 4 (0x2120000)
Jun 11 07:47:52 localhost slpd: FAIL: Could not join multicast group: Can't assign requested address
Jun 11 07:47:52 localhost slpd: ERR: SLPDALocator: set_multicast_sender_interf: SLP_NETWORK_INIT_FAILED
Jun 11 07:47:52 localhost slpd: ERR: get_converge_result: multicast sendto: Bad file descriptor
Jun 11 07:50:11 localhost sudo: scott : TTY=ttyp1 ; PWD=/Users/scott ; USER=root ; COMMAND=/sbin/ifconfig en0 inet up
Jun 11 07:50:31 localhost last message repeated 2 times
Jun 11 07:51:07 localhost sudo: scott : TTY=ttyp1 ; PWD=/Users/scott ; USER=root ; COMMAND=/sbin/ifconfig en0 inet down
Jun 11 07:51:26 localhost SLP-UA: FAIL: Could not join multicast group: Can't assign requested address
Jun 11 07:51:26 localhost SLP-UA: ERR: SLPDALocator: set_multicast_sender_interf: SLP_NETWORK_INIT_FAILED
Jun 11 07:51:26 localhost SLP-UA: ERR: get_converge_result: multicast sendto: Bad file descriptor
Jun 11 07:51:27 localhost sudo: scott : TTY=ttyp1 ; PWD=/Users/scott ; USER=root ; COMMAND=/sbin/ifconfig en0 inet up
Jun 11 07:52:45 localhost ntpd[237]: sendto(17.254.0.31): No route to host
Jun 11 07:53:02 localhost /Volumes/Apps/Net Monitor/Net Monitor.app/Contents/MacOS/Net Monitor: Net Monitor Quits
Jun 11 07:53:03 localhost loginwindow[334]: kCGErrorIllegalArgument : CGSUnregisterWindowWithSystemStatusBar: Invalid window
Jun 11 07:53:04 localhost configd[141]: executing /System/Library/SystemConfiguration/Kicker.bundle/Resources/restart-automount
Jun 11 07:53:04 localhost mach_kernel: syncing disks...
Jun 11 07:53:04 localhost syslogd: exiting on signal 15
Jun 11 08:03:10 localhost syslogd: restart

----------

Scott

[ 06-11-2002, 11:26 AM: Message edited by: dscottbuch ]

cla214 · Jun 11, 2002, 11:53 AM

My problem isn't the total loss of networking as described above, but rather a problem of temporary loss of connectivity every so often.

It's not a big deal, as it usually comes back if I close and relaunch IE (or whatever internet app I'm using), but it is certainly a bug that came with the upgrade to .1.5

I hope everyone is reporting it to Apple.

ahlawi · Jun 12, 2002, 01:47 PM

here is paris, and ther same bug in France, being discussed in French forums. 10.1.5 introduced this bug on my system (G3 Pismo 500). I log on the internet with DHCP on a motorola cable modem and never got this problem before updating to 10.1.5. trouble is rebooting sometimes doesn't solve the problem, I actually had to reboot three times and reset the modem this morning. This is really very very unnerving.
What is the consequence on NEVER putting the computer to sleep? heating? damage for the screen?

Norm1985 · Jun 12, 2002, 06:16 PM

Well, I've created a solution that fixed at least the problems I was having and what many of you are still suffering from now. It replaces the Ethernet driver in your /System/Library/Extensions with an older version that works perfectly after waking from sleep. Enjoy!

<a href="http://homepage.mac.com/norm1985/nnasfp.pkg.sit" target="_blank">Download it here!</a>

AKcrab · Jun 12, 2002, 07:00 PM

<blockquote>quote:<hr />Originally posted by Norm1985:
Well, I've created a solution that fixed at least the problems I was having and what many of you are still suffering from now. It replaces the Ethernet driver in your /System/Library/Extensions with an older version that works perfectly after waking from sleep. Enjoy!

<a href="http://homepage.mac.com/norm1985/nnasfp.pkg.sit" target="_blank">Download it here!</a><hr /></blockquote>I've tried that fix using a 10.1.3 updater download, and Pacifist. It didn't solve my problem. I have seen other reports of it working, but I *still* get a disconnect upon wake. My network *always* comes back within seconds, but the PC light on my cable modem blinks off, and anything like Fire, Adium, etc. are disconnected.
I hope others have more success than I did.
(I also tried the kext from 10.1 install cd.. also a no-go)

eno · Jun 12, 2002, 07:55 PM

I hereby add my name to the list of people suffering this bug since installing 10.1.5.

Equipment:

Pismo 500.
ADSL modem connected via ethernet.

Problem:

No network after sleep.
"Connect" button in "Internet connect" does nothing.

Workaround:
Reboot, switch network locations, turn modem off and on again, unplug and replug ethernet etc until network starts working again.

Emotional response:
****ing annoyed.