Hi there. i normally like to stand up to my problems and face them head on, but eventualy you have to admit when you have been beaten, and my HacFirewire just beat me REALLY badly. I have spent the past three days trying to get the firewire to work, I have installed every kext, followed every guide, and so far nada. so over to you, can anyone help?

I am running a Shuttle SG31G2 which has built in Firewire (front and back). There is no hardware issue with the firewire itself as it works perfectly under Windows 7 where it shows up as TEXAS instruments 1394 OHCI compliant host controller.

Under Mac OS however, when I look at FireWire in System Profiler, I see this "Unable to list FireWire devices."
When I check the logs I see "FireWire GUID ffffffffffffffff is invalid!"

I don't know if this is significant, but in System Profiler, two FireWire related extensions are listed, IOFireWireFamily & IOFireWireIP.

However in the actual folder there are more IOFireWireAVC, IOFireWireSBP2 & IOFireWireSerialBusProtocolTransport (there is also AppleFWaudio in there somewhere.) None of those items show up in System Profiler.
I tried "sudo kextload -t /System/Library/Extensions/IOFireWireAVC.kext" but it did nothing.

I am really afraid of this one. Last night in my attempts to fix this problem I found a thread which suggested using USB fix to correct the problem. I installed it and my system refused to boot, I had to wipe the drive and start again.

I built this system for video editing, so Firewire is an important part, but solving this is just way beyond my skill level. So does anyone have any suggestions?

Thanks in advance.

Hi there.

Still having no luck with the firewire, but I have discovered something.
Whenever I try to load IOFirewireAVC via terminal, it goes okay, however it throws up an error about AppleFWaudio.

For example after I kextloaded IOFireWireSerialBusProtocolTransport.kext. This appeared.

kextload: /System/Library/Extensions/AppleFWAudio.kext is not a directory
kextload: extension /System/Library/Extensions/IOFireWireSerialBusProtocolTransport.kext appears to be loadable
kextload: /System/Library/Extensions/IOFireWireSerialBusProtocolTransport.kext loaded successfully

So it seems as if the other kexts are working okay, but FWaudio is holding them all back.
For some reason in System Profiler, fw-audio shows up, but is grayed out (the others are not listed).

So any idea why fw audio is causing these problems? Anyone?

Anyone anyone?

I've been doing more snooping around on my Mac, I noticed something. In System Profiler the Mac address of the firewire is ff:ff:ff:ff:ff:ff:ff:ff. I could be totally wrong, but I believe this is an error. Could it be that my Hackintosh does not know where the firewire port really is and needs to be shown?

I could be totally wrong, this is just a theory, but would it be possible to boot into Windows, find the Mac address of the firewire port and then go into Mac OS and edit the Mac address. To point OS X in the right direction?

Also, the IPv4 address is blank, is this an error or is it just because the firewire is not connected to the net?

Please?

i am having audio issues with my Apogee Ensemble since
updating to 10.5.8 from 10.5.2. it is a firewire device.
maybe something similar is happening?

have you made any progress?

Progress, not a bit.

However you might have helped. Some people have had Firewire problems after upgrading. To fix it they install the Firewire Kexts from their earlier installation.

I tried installing the FW kexts from 10.4.9 but that didn't do anything for me. Maybe I have a different problem.

But that doesn't mean reverting to earlier kexts won't help you. Try this thread for a guide http://www.insanelymac.com/forum/ind...owtopic=133426

Let me know if that helps...and ya know, if anyone can help me...

Okay, I have a very simple idea which requires almost no effort. So can someone please respond.

Could someone with working Firewire and Windows installed on their computer help me out. Could you go into Windows and copy all the information about your Firewire in Device Manager (ya know, the numbers and settings etc.)

Then in Mac OS can you write down the information about Firewire in System Profiler?

If I have this information, then I can compare it to my own setup and hopefully see where mine is going wrong.

Please?

you must have pci card firewire chipset : texas intrument ( about usd 8-21)
and install iatkos 10.5.5 or 10.5.7
recomend moterboard gigabyte

Hi there, thanks for the reply.

It must be a PCI card, damn, I'm using on board fire wire. Is there anyway around this or is installing a card my only option?
The price of the fw card doesn't bother me because I have one sitting right here from my last computer (it's a little dusty, but still working) the only thing I am slightly worried about is overextending my computers power supply.

Out of curiosity, why does it have to be iatkos? Wouldn't a retail copy of OS X do the same?

---

Asus P5QL-Pro
Core2Quad Q8200 RAM: Kingston 6GB DDR2 667
nVidia 9400 GT Dual Monitors at 1440x900
OS X 10.7.2
M-Audio Delta 66 with Omni I/O
LAN: Realtek8102EL (works)

Hi there.

I tried deleting AppleHPET.kext, but it didn't fix the problem.
Although I'm sure I will need to later. Although I googled it, a lot of people claimed they needed to drop hpet to get firewire working, It wouldn't suprise me if two things are wrong, the GUID FFFFFFFF error and the hpet.kext. So once I solve the first, I have the solution for the second standing by. Thanks.