Mac OS X 10.4.2 (#7): Loss of Ethernet connectivity; FireWire drives unmounting -- power adapters to blame?; more

Loss of Ethernet connectivity We previously reported on losses of AirPort-based network connectivity after applying either the Mac OS X 10.4.2 or AirPort 4.2 update (or both).

MacFixIt reader Karl Kaufmann writes:

"I have upgraded one of my Macs to 10.4.2, and subsequently lost the ability to communicate via Ethernet. Ironically, I had just downloaded this update via Ethernet by using System Update. [...] I know the network is operational--I'm using it with this Mac (running 10.3.9) with no issues..."

As of yet, the only viable workaround for this issue appears to be a reversion to Mac OS X 10.4.1. Creating new network locations, deleting specific .plist files, and other traditional workarounds have proved unsuccessful for most readers so far.

If you are having a similar issue, please let us know.

FireWire drives spontaneously unmounting -- power adapters to blame? Over the past few days we've been covering an issue where FireWire drives unmount spontaneously under Mac OS X 10.4.2.

FireWire-based RAID configurations seem to be the most susceptible to this issue.

In some cases, it appears that a faulty power adapter can be to blame.

MacFixIt reader Junebug Clark reports that replacing his current LaCie power adapter with a new unit caused the spontaneous unmounts to cease on his Mac OS X 10.4.2 system.

Junebug writes:

"I have two LaCie 400GB drives and two LaCie 500GB drives running as two separate RAIDs. Also I have a LaCie DVD external drive.

"For two months I have been trouble shooting one RAID going off-line. Besides unmounting from the desktop, the key indicator was that the power light on one of the drives would be flashing while the other drive would still have a steady power on light. To shorten my trials and tribulations report the answer was to call Lacie and order a new Power Supply. About $24 and 48 hours later... Problem fixed."

More Mail.app problems We continue to cover issues with the version of Mail.app (2.0.2) included with Mac OS X 10.4.2.

A number of users report dramatically slower operation from the application, accompanied by an increased toll on system resources.

Jonathan Fisher writes:

"Since upgrading to 10.4.2, the entire Mail.app has become a resource hog. IMAP, Exchange, POP makes no difference. CPU usage is pegged at about 68.9%"

Meanwhile, MacFixIt reader Faisal reports yet another IMAP issue with the new release -- this time with non-standard ports:

"I've run into a problem with mail.app under 10.4.2 which is 100% repeatable:

"We have an IMAP server running on non-standard ports (it's a test server, the production server is on 143 and 993). if i point Mail.app at the server on the non-standard port it doesn't connect. By running tcpflow i've been able to verify that it doesn't even try to open the connection.

"Every other mail client i've tried (thunderbird, entourage) works fine, so I'll live with those for a while, but we'd rather use (and be able to support) Mail.app."

Similar issue? Please let us know.

Previous coverage:

• Mac OS X 10.4.2 (#6): Sleep Issues -- Check for software-related causes; FireWire Drives spontaneously unmounting
• Mac OS X 10.4.2 (#5): Sleep issues may be USB device, network-related -- solutions; iCal search broken -- solution; more
• Mac OS X 10.4.2 (#4): More AirPort connectivity fixes; Menu items disappear -- may not be Spotlight-related in some cases; more
• Mac OS X 10.4.2 (#3): More on delayed startup -- try disabling network connections; AirPort connectivity fixes; more
• Mac OS X 10.4.2 (#2): Common Workarounds; AirPort/Wireless connectivity lost; Widget, TCP/IP security updates; more
• Apple releases Mac OS X 10.4.2, Mac OS X 10.4.2 Server [Download Links, Release Notes]

Resources