I just see "No FireWire ports were found."
how can I use it?
I used it at leopard 10.5.8
help me.

If we only knew what your machine was...............(sigh)
My new electronic toaster also doesn't recognise that it has FireWires in!

SticMAC

------------------------
^^
thank you~
my PC is
Q9550
EP45-UD3L
G.Skill 8G Ram
9600GT

firewire Card(PCI Card) : Taxas Instruments OHCI Compliant IEEE 1394 Host Controller
Audio Card : ESI QuataFire
Sound Card : Behringer USB-

OS : Snow Leopard 10.6
------------------------

Have you run DSDT Patcher GUI on it?
I found that my PCI Wireless card does not get recognised until I run the patcher and it somehow activates the PCI Slots!
Also My Dell GX280 has an option to enable/disable PCI Slots in the BIOS, maybe you should look at that too!
Then then you can run DPCIManager to see, if your machine actually sees the card and what its DevID is so that you can maybe add that in the kext!?

Goodluck

SticMAC

remove appleHPET.kext

I also have a problem with firewire on my rig ( ga965p-dq6 )

System profiler tells me " unable to list firewire devices " (translation from french so maybe not the exact same sentence in english, the text is red)

Do you think removing appleHPET can help waneto ?

Thanks

give a try!!

sometimes appleHPET.kext share a irq with your other device, and your device do not work.

I ll try it as soon as i back home

Thanks a lot, hope this helps

I really need firewire for my soundcard.

Report ASAP

cool~~~ **
thanks everybody~~~
my firewire audio card is get a life~
hehehe~

Did not work for me.

Weird as it worked perfect on leopard

Any idea ?

I removed appleHPET.kext and got my firewire but I then seemed to get tons of KP and my system has been rock solid for over a week. Any ideas?

Yeahh, this defenitely did not work for me, got a KP on boot up with SL,

Any other suggestions?

Allan

My computer is seeing the firewire card as it shows up when I look with DPCIManager:

104c:8024 Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

is there anyway to patch the dsdt.aml file to get this thing going?

Update: I tried what SticMac suggested and ran the DSDTPatcher but it didn't seem to make a difference after multiple tries and reboots. I then removed the firewire card and put it in a different slot and now it works! Anyone who is still having problems give this low tech method a shot and see if it helps.

cheers

How do you remove a built in card ?

Anyone have any idea about the " firewire peripherals can t be listed " in system profiler ?

When i boot with +v the firewire controler ( TI ) seems to be detected correctly.

I removed appleHPET.kext and got my firewire(PCI) works nice, in Snow leopard 10.6.1

thanks

ga-ep45-ud3lr

Hi,

I have a Gigabyte GA-EX58-UD3R, and recently did a 10.6 installation. My onboard firewire (worked perfectly in 10.5.8 vanilla) suddenly stopped working. I did a vanilla install of 10.6 and upgraded to 10.6.1 now. The weirdest thing however is that my firewire device (soundcard) is actually recognized by the system-profiler, but it's not found by its driver. Same happens to USB devices (soundcards also). In the attachment there is a Screenshot of a recognized firewire device. Does anybody know a solution? Btw - I don't have any other firewire-device, so I can't experiment all too much.

I have the same problem with my gear, a X48-DS5 with a Q9650:



That's about the problems I have during booting. The messages appears, even if there is no FW device connected to the bus. FW works fine in Windows though. The DCPIManager recognizes it as 104c:8024 Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link).

I am booting up with:



and I am using the NETKAS 10_2 booter. For what it's worth.

Help

[quote name='tomazzzi' post='1250924' date='Sep 4 2009, 09:35 PM']I also have a problem with firewire on my rig ( ga965p-dq6 )

System profiler tells me " unable to list firewire devices " (translation from french so maybe not the exact same sentence in english, the text is red)

Do you think removing appleHPET can help waneto ?


Hi All,

I have the same problem as Tomazzi, In system profiler it states "unable to list firewire devices"
I do not have this problem in Leopard on the same machine.

My Snow Leopard install is vanilla 10.6.1 with DSDT.
I have tried deleteing appleHPET.kext, still the same message and no firewire,
I have tried DSDT patcher GUI, no firewire,
I have tried loading the 32 bit kernel and 64 bit, still the same message in system profiler and no firewire.

I have everything working except this. Any ideas? Is there a Jmicron.kext Leopard equivlent for SL to get this working?

Any and all advice greatly appreciated.
Cheers

I have EX58-UD5 with Core I7 Processor and I am using the build-in firewire port in Snow LEO 10.6.1 .....
I always get this error while booting in Snow: "FireWire runtime power conservation disabled. (2)"

I am using an Echo Audiofire 4 connected with the build-in firewire port and Logic 9.....

And now my problem:

I always get some glitches and pops while making music.....

I think this has to do with the error above.

Is there a fix for this?
Or is there a fully working firewire device for our hackintoshes?

Any ideas?

I had the hardest time getting AppleHPET out. You can check with

QUOTE

to see if it's really gone or not. When it was really gone I had kernel panics, so I can't live without it.

I could not delete appleHPET.kext without running into severe problems either.

I don't understand why Firewire Devices are found and properly listed, but when it comes to driver-communication,
they are not reachable, since it worked all perfectly in 10.5.8... I already tried using kexts of 10.5.8 for snow,
but that was no good idea -> Kernel panic mania!

Maybe we need modified firewire and usb kexts, or justput in a firewire PCIe card which is supported? But what
about USB?

Is there a way to modify the DSDT in a way that could help, regarding communication with onboard firewire and
USB?

Do you guys use modded DSDT? As far as I know, it's the only way to fix CMOS resetting, so I guess there
is no workaround.

Hi guys,

I unistalled appleHPET and now I can see the Firewire ports. Before this, the system coud no find any port.
Tested on this system: Asrock 4cores1600-Q6600-2G-retail 10.6/hameleon RC3.

I didn't experience any kernel panics yet, but I'd like to test the machine for this posibility. Could anybody tell me what operations are making your machines to panic, so I can try it here?

Thanks.

R.

I would love to know how you got onboard firewire to work at all on this mobo - I have the same.
Ive tried removing hpket and still get the warning in system properties regarding it.

Im using the DD setup method for SL with PC EFI 10 boot.

HELP!

Ok, this seems to be a bootloader-Problem, at least for me!

I was using Chameleon RC3, and it turned out that my firewire and USB devices only work properly using PC-EFI 10.2! But doing so causes my system to panic after about half a minute, so I can't use PC-EFI either...

Let's hope there's a fix soon .

UPDATE: I now got it working... I put the bootloader on the wrong partiton by accident and so it was using the wrong /Extra directory.

Now it works - not just fw, but also USB! But it only runs using PC-EFI 10.2 AND with the -x32 kernel flag set!
Chameleon RC3 did NOT work with/without the Kernel flag...




(I am pretty sure my next machine will be a REAL MacPro...)

@ zomby:

I don't have the same mobo, but a GA-EX58-UD3R - I suppose they're quite the same regarding onboard firewire.

I can't tell you how I got USB and firewire working on 10.5.8, since I think it was a combination of random kexts that made it work - I did still have issues with USB devices, though.

But if you managed to install 10.6 vanilla, you should make sure to install PC-EFI 10.2 as bootloader AND enable the -x32 flag, that is how it worked for me. No luck with chameleon 2.0 RC3 - although the devices had been showing up in my system profiler! As an owner of an X58 Mobo you could always use digital dreamers X58 mobo patch installer, which is great! (EDIT: I saw you did)

But be careful and make sure to backup your important stuff - I can tell you that this was a quite messy journey, and I don't exactly know if it ever worked again if I had to do it from scratch. There's too many things I still don't get. As soon as I sort it out I could give some more information.

Good luck!

Hi
I am using DD's install patcher but I installed Snow from a USB Stick not from another OSX partition.
I am using this installer method: http://www.infinitemac.com/f57/guide-insta...ck-drive-t3705/

I am using PC EFI 10.2 as Bootloader.

These are Kext's I am using: Sleepenabler.kext, Platformuuid.kext, Openhaltrestart.kext, NullCPUPowermanageement.kext, IOAHCIBlockstorage.kext, fakesmc.kext and a Disabler.kext for the mouse lag with Nvidia cards.......

You don't have to remove hpet.kext for get firewire to work at all.......


If you have any questions do not hesitate to contact me.....

@masterlen:

although I did an install from my former OSX partition, I can see the result now is the same as yours (PC-EFI 10.2, same Kexts and hpet.kext untouched) -you even seem to have similiar memory and the same gfx-card - The EX58-UD3R seems to be pretty much the same board, except for the onboard sound, which I don't use.

Anyway, I'd like to know if you have the -x32 flag set, or did it even work without it? I have no chance getting firewire and USB to run on my board without forcing OSX into 32-bit mode.
As far as I understood real macs also boot in 32bit mode by default as long as they don't have a 64bit efi, so maybe I don't need to worry?

I don't use the -x32 flag....
The System runs in 64Bit without any issues.....

Good stuff - I removed AppleHPET from /S/L/E and it solved my problem ("No FireWire ports were found").

(I did a SL DSDT Install as per http://www.insanelymac.com/forum/index.php...opic=%20180954)

hello,

worked fine also for me.
I removed AppleHPET and now I have FW port and my focusrite pro 26 working.
No KP.
GA-P35-DS4

cheers

I also removed the AppleHpet and my FW ports work now. Apparently fne but:

I have an external FW HD that gets corrupted from time to time.Mainly it gets unmounted during file copy operations.
I repair it with Disk Utility and then it works fine.
Did anybody experienced something similar?

The reason could be that your firewire doesn't work properly!

Search in the logs for this error:"FireWire runtime power conservation disabled. (2)" in your logs.....


Please see my post fro fire firewire issues!

http://www.insanelymac.com/forum/index.php?showtopic=191029

Hi. Having same issuewith fw on p5q and tc konnekt. First i had the red error message in systemprofile, then i installed the updated drivers from tc and now when i turn the audio card on, it's listed in sytem profiler but not detected by the prefs pannels.
Not working for me even removing appleHPET.kext.

Installed from Golden Master "distro" on an ASUS P5Q, nv9400gt working, audio voodoohda working,ethernet working, ram detected as 800 instead 1066.

Any chances?

[edit] i have this in my system log after installing the driver package and turning on the card; suggestions are very appreciated.

Oct 18 02:53:24 iois-Mac-Pro com.apple.kextd[10]: Can't load /System/Library/Extensions/TCNear.kext - no code for running kernel's architecture.
Oct 18 02:53:24 iois-Mac-Pro com.apple.kextd[10]: Failed to load /System/Library/Extensions/TCNear.kext - (libkern/kext) requested architecture/executable not found.
Oct 18 02:53:24 iois-Mac-Pro com.apple.kextd[10]: Load tc.tctechnologies.driver.TCNear failed; removing personalities.
Oct 18 02:53:24 iois-Mac-Pro com.apple.kextd[10]: Can't load /System/Library/Extensions/TCNear.kext - no code for running kernel's architecture.
Oct 18 02:53:24 iois-Mac-Pro com.apple.kextd[10]: Failed to load /System/Library/Extensions/TCNear.kext - (libkern/kext) requested architecture/executable not found.
Oct 18 02:53:24 iois-Mac-Pro com.apple.kextd[10]: Load tc.tctechnologies.driver.TCNear failed; removing personalities.

I thought TC has updated the konnektseries driver forSL.???

nothing about firewire in my systemlog.

Dont know where is my problem

i know that tc till today has no 64bit drivers. do you start in 64bit-mode? try the 32bit kompatibility-mode.

i bet the tc-connect works then.

greets
gnatze

Its done. Thank you ba-ton, i tried wrongly with -x32 flag and it didnt work at all because this flag (-x32) works on PC-EFI 10.x bootloaders. I am using chameleon 2 rc3 and i had to set arch=i386 kernel flag on the boot file and now everything works flawlessly. So if you use PC EFI 10.x then use the -x32 or -x64 kernel flags, if youre using chameleon 2 rc3 then use arch=i386 or arch=x86_64. It seems too that even running 32 bit kernel we can use 64bit apps. The kernel flag that turns this off only letting you execute 32 bit code is -legacy, which is not recommended in this case.

Golden Master distro is very recommendable, updated to 10.6.2 with minor issues and now firewire (which i suposse now always was running) and my TC Konnekt audio card works too perfectly right now.

Thanks for the clue again Ba- ton. After reading your reply i surf tc's support forum for more info and exactly this was the info ive found:

http://forum.tcelectronic.com/viewtopic.php?id=4664

It seems that the daw software and other audio hardware drivers still run at 32 bit from factory design. They havent changed the code yet but seems they are working on.

Now, after a disgusting MBP hardware fatal death, i feel again quite happy with my solid SL Hackintosh.

Thanks to the community. Keep on.

problem is with

IOFirewireSerialBusProtocolTransport.kext

Its a SL problem not a hackintosh problem. I am looking for IOFirewireSerialBusProtocolTransport.kext for leopard.

I've got the exact same problem here. My firewire is not recognised. I'm using a Asus P5-B Deluxe with a onboard PCI-E Firewire port. I removed the applehpet.kext and the firewire works fine now along with me plugged in Saffire Audio Interface but my Ethernet is no longer working! Its a Marvell PCI-E onboard ethernet controller. System Profiler detects it but it does not detect a cable plugged in

Anyone have similar issue or know of a possible fix?

Thanks