Jump to content

z68 UD7 B3 Firewire Power Conservation and GUID Invalid Help Needed

Firewire z68 z68 UD7-B3 GUID Invalid Firewire Power Conservation DSDT

  • Please log in to reply
4 replies to this topic

#1
bivanov

bivanov

    InsanelyMac Protégé

  • Members
  • Pip
  • 4 posts
  • Gender:Not Telling

I have been trying to work out the following issue. My firewire works well enough when I boot up 10.8.5. However once it wakes from sleep I receive "Firewire GUID is invalid".

 

In researching the issue I also noticed that on startup the console will show the "Firewire runtime power conservation disabled" entry. This leads me to believe that there is some kind of power management issue in the firewire controller.

 

I have found several encouraging threads regarding possible fixes:

 

Changing IRQ settings in the DSDT 

http://www.insanelym...ict-using-dsdt/

 

Firewire power conservation hack

http://www.projectos...x.php/t956.html

 

http://www.insanelym...atcher/page-118

 

 

The solution I have been pursuing is to incorporate the DSDT edit for the firewire power conservation hack. I have made progress however am struggling to successfully compile the DSDT. I have received the "device SB.PCI0.PCIB.FRWR" object does not exist error. I believe it to have something to do with the FRWR _ADR.

 

I am struggling to identify the the FRWR address (_ADR I assume) and how to successfully point the DSDT edit towards the right board controllers/components. I am unsure which section of the DSDT I must add the Device thread to. The majority of the hack code is provided by the DSDT editor, however there are parts I am unsure about.

I have been through so many broken threads where the subject is either dropped or loosely documented for those that need that extra bit of help understanding.

 

My primary uses for this machine are pro audio, graphics, and video. Hence my need for firewire. The system runs great otherwise and I really feel that this part of smoothing out the final 5% of the system.

 

I have listed below hardware and software details.

 

Hardware Specification:

  • ​Gigabyte z68x UD7-B3
  • The board has a built in T.I. TSB43AB23 Firewire controller
  • BIOS F10
  • i7 3770K
  • EVGA GTX 760 2gb
  • 16gb 1600MHz RAM
  • Focusrite Saffire Pro Audio Interface
  • OS X 10.8.5

 

Console Entries:

  • FireWire runtime power conservation disabled. (3)
  • FireWire GUID ffffffffffffffff is invalid!

Software:

  • DSDTSE
  • IORegistry Explorer


#2
maleorderbride

maleorderbride

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 275 posts
  • Gender:Male

Why not purchase a PCI or PCI-e FW800 card and sidestep the problem?  Just disable the onboard.



#3
bivanov

bivanov

    InsanelyMac Protégé

  • Members
  • Pip
  • 4 posts
  • Gender:Not Telling

I have read about people having the same issue with dedicated cards. This TI chipset is compatible, I think the DSDT just needs to be made to work with it. If I don't put the computer to sleep it all works just fine.

I would much rather learn to fix this and walk away with the experience and an even better machine. A lot of threads went the "just buy a new card" approach and that doesn't really fix anything.



#4
bivanov

bivanov

    InsanelyMac Protégé

  • Members
  • Pip
  • 4 posts
  • Gender:Not Telling

Update. I did pick up the Syba card. At worst I have a spare firewire card, best case it works.

 

http://www.sybausa.c...1&currentPage=0

 

 

Here is what I have learned so far:

 

  • Turning the display off blips the card so you have to re-synchronize it . 
  • Waking from sleep will result in a freeze within seconds of using any audio.
  • Firewire runtime power conservation still flags in the console
  • Firewire GUID invalid no longer occurs, instead the computer freezes after wake

I think the new issues are tied to the PCIe controller. I did install the card on the PCIe slot (x8_2) that doesn't share bandwidth with the PCIe x16_1

 

My board has PCIe x16_1, x16_2, x8_1, x8_2

 

I am going to try doing another round of IRQ hunting to see if that is the culprit.

 

 

As for the firewire runtime power conservation error, I am hoping to get some help with the DSDT edit.

 

I have compiled a DSDT with the Firewire Power Conservation Hack, however it is not solving the issue. I do not know how to embed

 

This is what I have done so far. I am fishing around for the right _ADR from IORegistryExplorer.

 

I have removed PCIB fro, the (\_SB.PCI0.FRWR, Zero) line because this board does not have a PCIB device.

 

I have been trying to add the FRWR Device inside the PCI0 Device, but am not sure how to correctly do that.

 Method (_L1A, 0, NotSerialized)
        {
            Notify (\_SB.PCI0.FRWR, Zero)
            Notify (\_SB.PWRB, 0x02)
        }
    }


Device (FRWR)
            {
                Name (_ADR, 0xF4000000)
                Name (_GPE, 0x0B)
                Method (_DSM, 4, NotSerialized)
                {
                    Store (Package (0x02)
                        {
                            "fwhub", 
                            Buffer (0x04)
                            {
                                0x00, 0x00, 0x00, 0x00
                            }
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }
            }

For now I am using the built in firewire because it is more stable. 

 

If anyone can let me know what other information I can provide.

 

Cheers



#5
aphex6b

aphex6b

    InsanelyMac Protégé

  • Members
  • PipPip
  • 82 posts
  • Gender:Male

il share my experiences with firewire on Osx86. My older system had onboard TI chip, this was X58-UD5 Gigabyte board, i ran a RME card of the 1394 output, i used chameleon as boot loader, only issues i ever had was indeed the "Firewire runtime energy conservation is disabled" @ boot time, then thanks to the OSXSe tools i managed to successfully add the Firewire HUB device and fixed that. Started to mess with Clover and found out it also had ability to patch that same thing on the fly. Now on my current UEFI system with VIA chipset, that same clover patch did not work anymore, i still had the " energy conservation is disabled" but didn't really bother me since it worked great in general, however after wake from sleep, i got kernel spamming all over console with the GUID 0000 is disabled errors. I searched a bit and read that this had to do with a Gigabyte bug? Kinda gave up, perhaps as last thing i wanted to give a try loading apple efi driver via clover, this was only about 2 months ago, now what i do not know how i managed to get the kernel log spam to stop, but the GUID errors are no longer there, also when running ifconfig -vv fw0 it gets a correct mac address etc, so i like to know how i made it get a correct GUID all of a sudden. I believe there was also some security related mac os firewire thing with Lion if i remember correct, that's why some reference it as firewire-security mode? 







Also tagged with one or more of these keywords: Firewire, z68, z68 UD7-B3, GUID Invalid, Firewire Power Conservation, DSDT


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy