izzysanime Posted July 12, 2008 Share Posted July 12, 2008 HI, Firewire is not working for me. Everything else is including USB is working. My specs are : AsRock motherboard 1333 eSata2 INtel core2 duo 3.0Ghz Thanks, Josh Link to comment Share on other sites More sharing options...
IvanPistoff Posted July 25, 2008 Share Posted July 25, 2008 I'm having the same problem. Firewire shows up in the profiler but when I plug in my camera it doesn't work. Dell Latitude D820 I beleive it is 02 Micro firewire chip Link to comment Share on other sites More sharing options...
izzysanime Posted July 28, 2008 Author Share Posted July 28, 2008 Anyone? I thought I read that there are firewire patches to make it work. Link to comment Share on other sites More sharing options...
LexaCh Posted July 29, 2008 Share Posted July 29, 2008 I have the same problem.... Disaster! Link to comment Share on other sites More sharing options...
verdant Posted July 30, 2008 Share Posted July 30, 2008 I have the same problem.... Disaster! Have you checked to see if your system.kext and kernel versions match? Link to comment Share on other sites More sharing options...
izzysanime Posted July 30, 2008 Author Share Posted July 30, 2008 Have you checked to see if your system.kext and kernel versions match? I did, it was for another issue, but they do match for me. Link to comment Share on other sites More sharing options...
RaDmAnZ Posted July 31, 2008 Share Posted July 31, 2008 yes i have HAD the same problem. Firewire card is detected, but no devices work off the card! this is due to the 1394 chipset used. i had some cheap VIA 1394 chipset at first. i thought it was the installation of osx giving issues. but i then tryed a T.I firewire card, and everything worked perfect. so i think it is the chipset that is giving your issues. if anything, i would recommend you purchasing texas instruments firewire cards only for hackintosh's, nothing else.. for TI was the inventor of 1394 and apple have been using their 1394 hardware since 1994. The exact problem i had with the via card, was that devices were seen to be plugged in, but device ID's were reported as 0x0000000, and sometimes, some other HEX address (i cannot remember exactly). All cards used were PCI.. PCMCIA should be no different. if the new ti 1394 card does not fix your problem, there is something wrong with your kernal installation. good luck! Link to comment Share on other sites More sharing options...
izzysanime Posted July 31, 2008 Author Share Posted July 31, 2008 yes i have HAD the same problem. Firewire card is detected, but no devices work off the card! this is due to the 1394 chipset used. i had some cheap VIA 1394 chipset at first. i thought it was the installation of osx giving issues. but i then tryed a T.I firewire card, and everything worked perfect. so i think it is the chipset that is giving your issues. if anything, i would recommend you purchasing texas instruments firewire cards only for hackintosh's, nothing else.. for TI was the inventor of 1394 and apple have been using their 1394 hardware since 1994. The exact problem i had with the via card, was that devices were seen to be plugged in, but device ID's were reported as 0x0000000, and sometimes, some other HEX address (i cannot remember exactly). All cards used were PCI.. PCMCIA should be no different. if the new ti 1394 card does not fix your problem, there is something wrong with your kernal installation. good luck! Unfortunately, I do not have $75 for a TI card. Link to comment Share on other sites More sharing options...
wuzzle Posted August 21, 2008 Share Posted August 21, 2008 Unfortunately, I do not have $75 for a TI card. So don't pay that. $29.95 ... 3-Port FireWire/1394a Professional PCI Host Adapter Link to comment Share on other sites More sharing options...
mrbash Posted August 28, 2008 Share Posted August 28, 2008 I have the exact same problem. I have a SB Audigy card that has FW built in. It was working with the Leo4All release, but with JaS it's detecting but I cannot connect any devices to it. Any help with kexts would be greatly appreciated. Link to comment Share on other sites More sharing options...
mrbash Posted August 30, 2008 Share Posted August 30, 2008 I have been able to resolve this problem by replacing the IOFireWireFamily.kext. I used the one from Leo4All V2. Hopefully the attached file can help some of you guys also. Link to comment Share on other sites More sharing options...
Demonik Posted September 4, 2008 Share Posted September 4, 2008 where are teh attached kexts? Link to comment Share on other sites More sharing options...
mrbash Posted September 5, 2008 Share Posted September 5, 2008 where are teh attached kexts? I had a problem with my Yukon2 drivers. They messed up uploads. Here is what I used from 10.5.2. Note that I experienced some instability so keep backups. Archive.zip Link to comment Share on other sites More sharing options...
Demonik Posted September 6, 2008 Share Posted September 6, 2008 I had a problem with my Yukon2 drivers. They messed up uploads. Here is what I used from 10.5.2. Note that I experienced some instability so keep backups. Thanks mrbash i dont mind instability as long as it works on somelevel i <3 backups. Link to comment Share on other sites More sharing options...
mrbash Posted September 27, 2008 Share Posted September 27, 2008 I want to follow up with some information here. I don't think the stability was related to the firewire. Also, I don't think I needed the kexts from Leo4All. I found that the problem with FireWire for me was that IOFireWireSerialBusProtocolTransport.kext was unloaded. WHen I manually did a kextload of that kext my FireWire devices came to life. I hope the above is helpful to someone. Link to comment Share on other sites More sharing options...
aliasa_anderson Posted October 26, 2008 Share Posted October 26, 2008 I want to follow up with some information here. I don't think the stability was related to the firewire. Also, I don't think I needed the kexts from Leo4All. I found that the problem with FireWire for me was that IOFireWireSerialBusProtocolTransport.kext was unloaded. WHen I manually did a kextload of that kext my FireWire devices came to life. I hope the above is helpful to someone. Which firewire chip you have ? Link to comment Share on other sites More sharing options...
jpowersphoto Posted December 9, 2009 Share Posted December 9, 2009 Which firewire chip you have ? I'm a newbie to the osx86 community. My firewire will pop up on start up, but if I plug it in while mac osx (kalyway 10.5.2) is running it won't work. Link to comment Share on other sites More sharing options...
koushiro Posted December 9, 2009 Share Posted December 9, 2009 I'm a newbie to the osx86 community. My firewire will pop up on start up, but if I plug it in while mac osx (kalyway 10.5.2) is running it won't work. Well, What I did was just buy a separate firewire card. It was $10 on newegg and it works great. Link to comment Share on other sites More sharing options...
ZoroLives Posted December 27, 2009 Share Posted December 27, 2009 Well, What I did was just buy a separate firewire card. It was $10 on newegg and it works great. I don't understand. I have a Gigabyte x58-UD4P with the i7. That board has a firewire socket built in already. I am now trying my Focusrite Sapphire DSP (sound interface for recorded sound). IT is Firewire only. I "thought" it worked as it shows defaulting to full security in FW while booting. But until now I Have not actually tested. Up till now I have been running Leopard and am still struggling to upgrade to SNL. No working FW yet though. Does the thread suggest that I need to get a FW card and forget trying to use the built in GA socket? Thanks Link to comment Share on other sites More sharing options...
Recommended Posts