X

Troubleshooting Mac OS X 10.2.5: Logitech drivers; PowerBook G4 battery indication; coreservicesd using 99% of CPU; more

Troubleshooting Mac OS X 10.2.5: Logitech drivers; PowerBook G4 battery indication; coreservicesd using 99% of CPU; more

CNET staff
3 min read

Logitech driver issues; response There seems to be a conflict between Mac OS X 10.2.5 and Logitech's version 1.1 driver for their mice and keyboards. The mice appear to work correctly, but plugging in an Elite keyboard causes all menu bar issues including disappearing icons and problematic drop-down menus.

Logitech's technical support department offered the following response to the issue:

"Apologize [sic] for the issue you are receiving. The OS X 10.2.5 is not yet supported by our Logitech Control Center at this time. OS X 10.2.5 is so new that we have not yet been updated. We will be updating the software in the very near future. Please check back periodically with our web site at: http://www.logitech.com. Sorry for the inconvenience."

PowerBook G4 Titanium battery indication A large number PowerBook G4 Titanium users are experiencing a lack of warning when the battery goes down to critically low levels after updating to Mac OS X 10.2.5. John Griffin writes:

"In previous system updates there were always two warnings, one when it got down to a level where one could still finish up whatever one was working on and another warning that the PowerBook was about to do a forced shut down (within 'x' number of seconds).

"Now there is no warning. When the Powerbook gets to a zero level and all LEDs on the battery are flashing, it will suddenly go into a forced sleep mode. What is worse is that it seems to be impossible to wake from this sleep once the Powerbook is plugged in. One is forced to hold down the power button and do a cold startup - losing all the work that was in progress."

coreservicesd using 99% of CPU We have received sporadic reports of the coreserviced process suddenly hogging processor time thereby dramatically slowing down the system. The problem has occurred for some users after updating to Mac OS X 10.2.5, and for others it has been a recurring problem with all releases of Mac OS X 10.2.x.

MacFixIt reader Michael Bishop writes:

"This happens to me now upon login. The has been a persistent problem with my PowerBook (bronze) and Mac OS X (10.2.x, including 10.2.5). After I have used it for a while, the configuration changes in some way and then I start to see this problem. Killing coreservicesd allows me to continue using my computer, but now certain things are absent such as drag and drop."

The apparent solution for this skyrocketing CPU usage is to delete all items in the /Library/Preferences/ and /Library/Cache/ folders. You will have to restore any previously marked settings, but the problem should disappear.

SMB access problems after update Ric McGredy describes some problems accessing SMB networked volumes after updating to Mac OS X 10.2.5:

"The only SMB volumes I can get to on my network after doing the Mac OS X 10.2.5 install are running Samba on Linux. The SNAPserver we have won't connect over SMB, and neither will any of the XP peers on my LAN. This definitely worked before Mac OS X 10.2.5.

If you are having problems with SMB networking or have other feedback, please drop us a line at late-breakers@macfixit.com.

Resources

  • http://www.logitech.com
  • late-breakers@macfixit.com
  • More from Late-Breakers