firewire nightmare with snow leopard

SO I got a used macbook from ebay and upgraded that to snow leopard 10.6.4. All good. Then I used migration assistant to take my stuff off my old laptop running 10,5.8...and that actually worked.
Now My new laptop has zero firewire, and my old one will not boot. Just turns it self completely off about 5 seconds after the spinning grey wheel appears.
I want fire wire in the new one, and want to keep the old one.
What a mess. Seems like i just stepped back into windows 99.
So far i have done the command/option/p/r thing
I have repaired permissions a couple of times,
What a gross feeling...yuk

thanks if you can point me in better direction:)

macbook 2ghz, Mac OS X (10.6.4)

Posted on Sep 8, 2010 12:58 AM

Reply
23 replies

Sep 8, 2010 12:30 PM in response to Douglas Meeuwsen

OK, so i wiped the old mac, and it works and the firewire works too. That's good cuz i was thinking that hooking up the two with a firewire cable blew out both firewire cicuits or something.

So no on the snow leopard mac, the profiler just says under firewire:

FireWire Bus:

Maximum Speed: Up to 400 Mb/sec

does that mean that i at least have a firewire bus? Power does come out of the firewire port because it will light up an unpowered firewire drive. Just nothing gets recognized.
I have the day off, so I have reparied permissions 5 times, removed the battery, done the pra thing a few times, pretty everything people say to do.....nothing

Gotta be be somebody out there that has gotten this to work.....I have noticed that there are about a thousand posts to various forums regarding this

Sep 9, 2010 10:32 AM in response to Douglas Meeuwsen

so i have figured out that the firewire is mainly just super flaky. About every forty times you plug a drive in, it will recognize it. You can use it for a short time, and then it freezes the finder for a while. ejecting takes minutes after the firewire bus flakes out. At least it isn't burnt:)

hopefully there might be a patch in the future. I am going to try my MOTU audio interfaces anyway today to see if they might work....

Sep 9, 2010 12:35 PM in response to Hazem Malek

yeah, no go with the smf
I have been researching this for a couple days, and have read hundreds of posts from people with the same problem. Looks like a built in problem. I'm trying to find the extensions from 10.5.8 which sounds like it could work, but i can seem to get them from anywhere. Must be some rule about posting that stuff to the forums here.

thanks though

DOug M

Sep 9, 2010 2:53 PM in response to Douglas Meeuwsen

It sounds like the firewire port on the used Mac is defective. (As someone said, this could be why it was sold.) If so, there is no patch or other software fix for this: although different extensions might cause it to react differently, none are capable of repairing physical damage to the circuitry or making it reliable.

Regarding obtaining OS extensions, there is a reason they are not available individually: they are meant to be installed as part of an integrated package that among other things performs various checks & updates internal references in other OS files to make sure all the pieces are compatible with each other & will work as expected with the other parts of the OS.

If you have a legally obtained copy of the installer, you can usually use Pacifist to replace a damaged extension file with an undamaged copy of the same file without problems, but using it to substitute & mix different versions of OS extensions is not advisable, at least if your goal is a reliable system.

Sep 9, 2010 3:17 PM in response to Steve M.

The items in /System/Library/Extensions, known as kernel extensions, with the file type of "kext."

There are a bunch of them, many with a hierarchical dependency on others for their functionality. For example, there is a whole family of several dozen "IO" (input/output) extensions, including five that support various Firewire features. None of the five are stand-alone, each depending on other IO kexts for low level support, arbitration, & so on.

That's why mixing kexts from different OS versions rarely works reliably. It's a little like using parts from one year of a car in another year's engine.

Sep 9, 2010 7:47 PM in response to Steve M.

nah my firewire port is fine, tihs is a known software issue with snow leopard.
SO anyway, i now am pretty sure that the kExt utility has fixed things for using my firewire audio interfaces, and my main firewire drives as well. I do have one drive by "acomdata" that is still very flaky, but my iomegas are fine, and my MOTU 896 is working great with logic studio 9.
WHEW! I did not really care about the drives, but I really need that firewire to run my recording rig.
Check out the other threads, the really long 15 page thread about this, and you can find a link to kExt utility around page 13 of the thread

Crossing my fingers:)

doug M

Sep 10, 2010 3:32 AM in response to Douglas Meeuwsen

I have no idea what "known software issue with snow leopard" you are talking about or what long topic discusses it. If you have permissions problems, Disk Utility's Repair Permissions step should solve them. Kext utility is primarily a developer's tool for non-Apple extensions -- anything it fixes that Disk Utility can't isn't a part of Snow Leopard & the responsibility to fix it is the developer's, not Apple.

Sep 10, 2010 5:12 AM in response to Douglas Meeuwsen

Douglas Meeuwsen wrote:
nah my firewire port is fine, tihs is a known software issue with snow leopard.


Interesting. Which particular 'known software issue with snow leopard' is this? I have several Macs running SL, all of them with FireWire ports, none of them with anything like the problems you have. Could you supply a RADAR report number for this 'known issue'? Could you go into a little detail about it? How do you reliably reproduce it? Which versions of the OS have it? Which hardware does it affect?

Sep 10, 2010 11:29 AM in response to R C-R

well, the "known problem" is the one i described, which thousands of people are having, and there is even a petition to get apple to move on it.... if you want to know more, just google it i guess.

Basically the kext extensions are messed up when you "upgrade" to snow, and you can fix that by messing around with kext, complicated mess. For me, the kext utility repaired things. or so I hope:)

still, it is a big problem, that started with 10.6 and still going with 10.6.4

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

firewire nightmare with snow leopard

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.