thecodecowboy Posted August 6, 2008 Share Posted August 6, 2008 Hi, I have a Texas Instruments firewire card which I can't get working on my Hackintosh. I'm looking for a developer / hacker to get this working and will pay you if you succeed. Please PM me if interested. codecowboy. Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/ Share on other sites More sharing options...
macwanabe Posted August 6, 2008 Share Posted August 6, 2008 What's not working with your card. Or is it not even detected ? Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/#findComment-846915 Share on other sites More sharing options...
verdant Posted August 6, 2008 Share Posted August 6, 2008 Hi, I have a Texas Instruments firewire card which I can't get working on my Hackintosh. I'm looking for a developer / hacker to get this working and will pay you if you succeed. Please PM me if interested. codecowboy. Your kernel version and system.kext version should be the same........even for Firewire not just USB.......see this thread for Mysticus C*'s USB Mount Fix v1.3....... Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/#findComment-846939 Share on other sites More sharing options...
thecodecowboy Posted August 6, 2008 Author Share Posted August 6, 2008 It is not even detected, though it is listed if I do lspci. 04:01.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 01) (prog-if 10 [OHCI]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+ INTx- Latency: 64 (500ns min, 1000ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 17 Region 0: Memory at eebff800 (32-bit, non-prefetchable) Region 1: Memory at eebf8000 (32-bit, non-prefetchable) Capabilities: [44] <chain broken> The kernel version and system.kext are the same. dmesg shows: FireWire (OHCI): start - unable to get device memory FireWire (OHCI): start - unable to get device memory Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/#findComment-846984 Share on other sites More sharing options...
verdant Posted August 6, 2008 Share Posted August 6, 2008 It is not even detected, though it is listed if I do lspci. 04:01.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 01) (prog-if 10 [OHCI]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+ INTx- Latency: 64 (500ns min, 1000ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 17 Region 0: Memory at eebff800 (32-bit, non-prefetchable) Region 1: Memory at eebf8000 (32-bit, non-prefetchable) Capabilities: [44] <chain broken> The kernel version and system.kext are the same. dmesg shows: FireWire (OHCI): start - unable to get device memory FireWire (OHCI): start - unable to get device memory Does OS X recognise and work with the onboard EE 1394a interface?.......could the two be conflicting because your Firewire card is (I guess?) a Firewire 800 having the Texas Instruments TSB82AA2 64-bit PCI host controller.......does disabling onboard Firewire in BIOS make a difference? Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/#findComment-847039 Share on other sites More sharing options...
thecodecowboy Posted August 6, 2008 Author Share Posted August 6, 2008 Hi - thanks for the reply. I bought the card because the onboard ports were also not recognised. The card is this one: http://www.maplin.co.uk/Module.aspx?Module...=14&doy=5m8 It has a 1394a port too and it says osx is supported. I get the same behaviour whether the bios option for the Agere (onboard) chip is enabled or not. I also reset the CMOS on the motherboard just in case, have tried new BIOS version etc. Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/#findComment-847192 Share on other sites More sharing options...
verdant Posted August 6, 2008 Share Posted August 6, 2008 Hi - thanks for the reply. I bought the card because the onboard ports were also not recognised. The card is this one: http://www.maplin.co.uk/Module.aspx?Module...=14&doy=5m8 It has a 1394a port too and it says osx is supported. I get the same behaviour whether the bios option for the Agere (onboard) chip is enabled or not. I also reset the CMOS on the motherboard just in case, have tried new BIOS version etc. This is a strange one because others in the forum apparently have the same 1394b chipset based Firewire card running OK.....see here.......does the card work with Windows XP OK? Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/#findComment-847312 Share on other sites More sharing options...
thecodecowboy Posted August 6, 2008 Author Share Posted August 6, 2008 I dont know. I dont have a windows install to test and I dont fancy installing it just to see if the firewire card works to be honest. Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/#findComment-847432 Share on other sites More sharing options...
verdant Posted August 6, 2008 Share Posted August 6, 2008 I dont know. I dont have a windows install to test and I dont fancy installing it just to see if the firewire card works to be honest. See if it works on Linux partition assuming Linux driver available for that chipset...... Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/#findComment-847713 Share on other sites More sharing options...
thecodecowboy Posted August 7, 2008 Author Share Posted August 7, 2008 hi, it appears in device manager in ubuntu. dmesg shows: [ 37.293906] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 37.345798] ohci1394: fw-host0: Runaway loop while stopping context: ... [ 37.397717] ohci1394: fw-host0: Runaway loop while stopping context: ... [ 37.449610] ohci1394: fw-host0: Runaway loop while stopping context: ... [ 37.501515] ohci1394: fw-host0: Runaway loop while stopping context: ... [ 37.501520] ohci1394: fw-host0: OHCI-1394 165.165 (PCI): IRQ=[17] MMIO=[eebff800-eebfffff] Max Packet=[65536] IR/IT contexts=[32/32] [ 37.600619] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 37.699727] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 37.798836] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 37.897945] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 37.997049] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.096150] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.195258] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.294382] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.393485] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.492611] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.591731] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.690848] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.789965] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.889076] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.988191] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.087306] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.186410] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.285534] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.384658] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.483773] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.582890] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.682006] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.781112] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.880232] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.979347] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 40.078468] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 40.177587] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 40.276698] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 40.375817] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 40.474934] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 40.474954] ohci1394: fw-host0: Serial EEPROM has suspicious values, attempting to set max_packet_size to 512 bytes [ 41.571133] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] do you think these are similar / related errors? I have no other way of testing the card as the firewire device I want to use is an m-audio firewire 410 and there's no linux driver. i'm beginning to suspect that the motherboard might be faulty but have no real way of knowing. Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/#findComment-848688 Share on other sites More sharing options...
verdant Posted August 8, 2008 Share Posted August 8, 2008 hi, it appears in device manager in ubuntu. dmesg shows: [ 37.293906] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 37.345798] ohci1394: fw-host0: Runaway loop while stopping context: ... [ 37.397717] ohci1394: fw-host0: Runaway loop while stopping context: ... [ 37.449610] ohci1394: fw-host0: Runaway loop while stopping context: ... [ 37.501515] ohci1394: fw-host0: Runaway loop while stopping context: ... [ 37.501520] ohci1394: fw-host0: OHCI-1394 165.165 (PCI): IRQ=[17] MMIO=[eebff800-eebfffff] Max Packet=[65536] IR/IT contexts=[32/32] [ 37.600619] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 37.699727] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 37.798836] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 37.897945] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 37.997049] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.096150] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.195258] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.294382] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.393485] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.492611] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.591731] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.690848] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.789965] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.889076] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 38.988191] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.087306] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.186410] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.285534] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.384658] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.483773] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.582890] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.682006] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.781112] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.880232] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 39.979347] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 40.078468] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 40.177587] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 40.276698] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 40.375817] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 40.474934] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] [ 40.474954] ohci1394: fw-host0: Serial EEPROM has suspicious values, attempting to set max_packet_size to 512 bytes [ 41.571133] ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100] do you think these are similar / related errors? I have no other way of testing the card as the firewire device I want to use is an m-audio firewire 410 and there's no linux driver. i'm beginning to suspect that the motherboard might be faulty but have no real way of knowing. Not sure about that......as others have reported the same "...EEPROM has suspicious values, attempting to set max_packet_size to 512 bytes" error under Ubuntu for example......so on this basis it is difficult to say if the card is faulty or the MOBO or that the problem lies elsewhere......this may be a stupid question but have you installed the latest M-Audio Firewire 410 driver.....there different versions for each OS 10.5.x update..... Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/#findComment-849062 Share on other sites More sharing options...
thecodecowboy Posted August 8, 2008 Author Share Posted August 8, 2008 yes - i have installed the one for 10.5.4. Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/#findComment-849064 Share on other sites More sharing options...
verdant Posted August 8, 2008 Share Posted August 8, 2008 yes - i have installed the one for 10.5.4. In this case all I can suggest is if you can do so, is to try the Firewire card in different PCI slots.......it may be some form of device memory conflict........sorry I cannot be of more help...... Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/#findComment-849148 Share on other sites More sharing options...
manmal Posted January 20, 2010 Share Posted January 20, 2010 hi, what about if firewire is integrated in a laptop and cannot be disabled ? what should i do ? thanks! mal Link to comment https://www.insanelymac.com/forum/topic/119577-bounty-offered-get-firewire-working-on-my-hackintosh/#findComment-1390781 Share on other sites More sharing options...
Recommended Posts