Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
kdawg

Firewire issues

99 posts in this topic

Recommended Posts

Thx for teh reply,

yes, I did that, but there's no change.

My firewire works without any code in DSDT, but I have the power conservation message.

When I add the code I see it in IOREG, but it's not working.

I'll attach my DSDT.dsl

 

DSDT.dsl.zip

 

So I suppose there's no solution for me yet.

Share this post


Link to post
Share on other sites

I appologize for being slow but ... how do I figure out the address of my firewire from lspci? Mine shows -

 

05:06.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) [104c:8024]

 

Any pointer would be appreciated.

 

Regards,

SMF

Share this post


Link to post
Share on other sites

scrax,

 

Thanks, I've got that part. What I'm confused about is in red below.

 

Device (FRWR) // Added device for Texas Instruments TSB43AB22/A IEEE-1394A Controller

{

Name (_ADR, 0x060A0000) // Reported by 'lspci'

 

Regards,

SMF

Share this post


Link to post
Share on other sites
scrax,

 

Thanks, I've got that part. What I'm confused about is in red below.

 

Device (FRWR) // Added device for Texas Instruments TSB43AB22/A IEEE-1394A Controller

{

Name (_ADR, 0x060A0000) // Reported by 'lspci'

 

Regards,

SMF

 

Ditto for me too

 

09:06.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) [104c:8024]

 

from ex58-ud5 ich10r

 

generic code from first post didn't work so I assume the address is not 0x00070000

Share this post


Link to post
Share on other sites
I appologize for being slow but ... how do I figure out the address of my firewire from lspci? Mine shows

 

05:06.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) [104c:8024]

 

Any pointer would be appreciated.

 

Come on guys, it's simple!

 

05:06.0 = 0x05060000

 

09:06.0 = 0x09060000

 

It's always 8-digits!

Share this post


Link to post
Share on other sites

 

 

Come on guys, it's simple!

05:06.0 = 0x05060000

09:06.0 = 0x09060000

It's always 8-digits!



Thanks MacKonsti, this address thing has had me confused for several weeks now I'm embarrassed to say


It half worked with

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

I now get

FireWire (OHCI) TI ID 8024 built-in now active, GUID 00dcaf5700001fd0; max speed s400.

rather than

FireWire (OHCI) TI ID 8024 PCI now active, GUID 00dcaf5700001fd0; max speed s400.

and no error message. :)

My scanner isn't recognised until after sleep, so bit more tinkering to do

cheers
Steve

Share this post


Link to post
Share on other sites
Thanks MacKonsti, this address thing has had me confused for several weeks now I'm embarrassed to say

 

 

It half worked with

 

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

 

I now get

 

FireWire (OHCI) TI ID 8024 built-in now active, GUID 00dcaf5700001fd0; max speed s400.

 

rather than

 

FireWire (OHCI) TI ID 8024 PCI now active, GUID 00dcaf5700001fd0; max speed s400.

 

and no error message. :)

 

My scanner isn't recognised until after sleep, so bit more tinkering to do

 

cheers

Steve

 

I tried using callback in PCIB (_ADR, 0x001E0000) but didn't work for me apart from deleting 4 or 5 lines of code

 

I only use firewire for my nikon scanner so not a big deal if my scanner isn't hot pluggable - maybe the scanner

needs defining? (quite a lot of detail in there)

 

Prior to sleep this is what ioreg looks like

 

Then straight after sleep/wake turns green then black

 

after powering scanner off then red strike through

 

steve

post-383752-1264458501_thumb.png

post-383752-1264458550_thumb.png

post-383752-1264458590_thumb.png

Share this post


Link to post
Share on other sites
Thanks MacKonsti, this address thing has had me confused for several weeks now I'm embarrassed to say. It half worked with

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

I now get

 

FireWire (OHCI) TI ID 8024 built-in now active, GUID 00dcaf5700001fd0; max speed s400.

 

rather than

 

FireWire (OHCI) TI ID 8024 PCI now active, GUID 00dcaf5700001fd0; max speed s400.

 

and no error message. :)

 

My scanner isn't recognised until after sleep, so bit more tinkering to do.

I also have the same message, funny that you brought it up; I thought I'd seen it change but didn't remember :)

 

Guys, don't forget to insert the correct callback code in Name (_GPE, 0xXX). It has to be the (_GPE) call notification of the superset device that you've placed (FRWR) into...

 

In my case, (FRWR) was made as a device inside (HUB0) device, so the callback in the firewire code points to the (_GPE) notification of the (HUB0) device, respectively... Study the (_GPE) code carefully, and if say there's an _L09 for you, then the code is Name (_GPE, 0x09) without the "L". This could solve the boot non-detection issues...

 

Please use my code as posted in the previous page, and make sure you don't add or remove anything before reading carefully through the code...

Share this post


Link to post
Share on other sites
I also have the same message, funny that you brought it up; I thought I'd seen it change but didn't remember :tomato:

 

Guys, don't forget to insert the correct callback code in Name (_GPE, 0xXX). It has to be the (_GPE) call notification of the superset device that you've placed (FRWR) into...

 

In my case, (FRWR) was made as a device inside (HUB0) device, so the callback in the firewire code points to the (_GPE) notification of the (HUB0) device, respectively... Study the (_GPE) code carefully, and if say there's an _L09 for you, then the code is Name (_GPE, 0x09) without the "L". This could solve the boot non-detection issues...

 

Please use my code as posted in the previous page, and make sure you don't add or remove anything before reading carefully through the code...

 

Do you mean like, I've highlighted what I think are the relevant parts in red - didn't work for me

 

         
           Device (PCIB)
           {
               Name (_ADR, 0x001E0000)
               Method (_STA, 0, NotSerialized)
               {
                   Return (0x0F)
               }

               Name (APIC, Package (0x0C)
               {
                   Package (0x04)
                   {
                       0xFFFF, 
                       Zero, 
                       Zero, 
                       0x10
                   }, 

                   Package (0x04)
                   {
                       0xFFFF, 
                       One, 
                       Zero, 
                       0x11
                   }, 

                   Package (0x04)
                   {
                       0xFFFF, 
                       0x02, 
                       Zero, 
                       0x12
                   }, 

                   Package (0x04)
                   {
                       0xFFFF, 
                       0x03, 
                       Zero, 
                       0x13
                   }, 

                   Package (0x04)
                   {
                       0x0001FFFF, 
                       Zero, 
                       Zero, 
                       0x11
                   }, 

                   Package (0x04)
                   {
                       0x0001FFFF, 
                       One, 
                       Zero, 
                       0x12
                   }, 

                   Package (0x04)
                   {
                       0x0001FFFF, 
                       0x02, 
                       Zero, 
                       0x13
                   }, 

                   Package (0x04)
                   {
                       0x0001FFFF, 
                       0x03, 
                       Zero, 
                       0x10
                   }, 

                   Package (0x04)
                   {
                       0x0006FFFF, 
                       Zero, 
                       Zero, 
                       0x12
                   }, 

                   Package (0x04)
                   {
                       0x0006FFFF, 
                       One, 
                       Zero, 
                       0x12
                   }, 

                   Package (0x04)
                   {
                       0x0006FFFF, 
                       0x02, 
                       Zero, 
                       0x12
                   }, 

                   Package (0x04)
                   {
                       0x0006FFFF, 
                       0x03, 
                       Zero, 
                       0x12
                   }
               })
               Method (_PRT, 0, NotSerialized)
               {
                   Return (APIC)
               }

               [color="#FF0000"]Method (_PRW, 0, NotSerialized)
               {
                   Return (Package (0x02)
                   {
                       0x0B, 
                       0x05
                   })
               }[/color]

               Device (FRWR)
               {
                   Name (_ADR, 0x09060000)
                   [color="#FF0000"]Name (_GPE, 0x0B)[/color]
                   Method (_DSM, 4, NotSerialized)
                   {
                       Store (Package (0x06)
                           {
                               "fwhub", 
                               Buffer (0x04)
                               {
                                   0x00, 0x00, 0x00, 0x00
                               }, 

                               "device-id", 
                               Buffer (0x04)
                               {
                                   0x24, 0x80, 0x00, 0x00
                               }, 

                               "name", 
                               Buffer (0x37)
                               {
                                   "Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller"
                               }
                           }, Local0)
                       DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                       Return (Local0)
                   }
               }
           }

calling

       Method (_L0B, 0, NotSerialized)
       {
           Notify (\[color="#FF0000"]_SB.PCI0.PCIB[/color], 0x02)
       }

Share this post


Link to post
Share on other sites
Do you mean like, I've highlighted what I think are the relevant parts in red - didn't work for me

 

         
           Device (PCIB) // changed from HUB0
           {
               Name (_ADR, 0x001E0000)
               Method (_STA, 0, NotSerialized)
               {
                   Return (0x0F)
               }

               Name (APIC, Package (0x0C)
               {
                   Package (0x04)
                   {
                       0xFFFF, 
                       Zero, 
                       Zero, 
                       0x10
                   }, 

                   Package (0x04)
                   {
                       0xFFFF, 
                       One, 
                       Zero, 
                       0x11
                   }, 

                   Package (0x04)
                   {
                       0xFFFF, 
                       0x02, 
                       Zero, 
                       0x12
                   }, 

                   Package (0x04)
                   {
                       0xFFFF, 
                       0x03, 
                       Zero, 
                       0x13
                   }, 

                   Package (0x04)
                   {
                       0x0001FFFF, 
                       Zero, 
                       Zero, 
                       0x11
                   }, 

                   Package (0x04)
                   {
                       0x0001FFFF, 
                       One, 
                       Zero, 
                       0x12
                   }, 

                   Package (0x04)
                   {
                       0x0001FFFF, 
                       0x02, 
                       Zero, 
                       0x13
                   }, 

                   Package (0x04)
                   {
                       0x0001FFFF, 
                       0x03, 
                       Zero, 
                       0x10
                   }, 

                   Package (0x04)
                   {
                       0x0006FFFF, 
                       Zero, 
                       Zero, 
                       0x12
                   }, 

                   Package (0x04)
                   {
                       0x0006FFFF, 
                       One, 
                       Zero, 
                       0x12
                   }, 

                   Package (0x04)
                   {
                       0x0006FFFF, 
                       0x02, 
                       Zero, 
                       0x12
                   }, 

                   Package (0x04)
                   {
                       0x0006FFFF, 
                       0x03, 
                       Zero, 
                       0x12
                   }
               })
               Method (_PRT, 0, NotSerialized)
               {
                   Return (APIC)
               }

               [color="#FF0000"]Method (_PRW, 0, NotSerialized)
               {
                   Return (Package (0x02)
                   {
                       0x0B, 
                       0x05
                   })
               }[/color]

               Device (FRWR)
               {
                   Name (_ADR, 0x09060000)
                   [color="#FF0000"]Name (_GPE, 0x0B)[/color]
                   Method (_DSM, 4, NotSerialized)
                   {
                       Store (Package (0x06)
                           {
                               "fwhub", 
                               Buffer (0x04)
                               {
                                   0x00, 0x00, 0x00, 0x00
                               }, 

                               "device-id", 
                               Buffer (0x04)
                               {
                                   0x24, 0x80, 0x00, 0x00
                               }, 

                               "name", 
                               Buffer (0x37)
                               {
                                   "Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller"
                               }
                           }, Local0)
                       DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                       Return (Local0)
                   }
               }
           }

calling

       Method (_L0B, 0, NotSerialized)
       {
           Notify (\[color="#FF0000"]_SB.PCI0.PCIB[/color], 0x02)
       }

 

not working for me too, the error is gone but i cant plug and mount my mybook FW drive.. if i shutdown and plug it in before ON then it will be detected. :huh: am i doing something wrong? please check the code.

 

lspci --nn is showing this 04:01.0 FireWire (IEEE 1394) so ADR is 0x04010000

 

 


[color="#0000FF"]Scope[/color] (_GPE)
..............
       Method (_L0B, 0, NotSerialized)
       {
        Notify (\_SB.PCI0.PCIB, 0x02)

[color="#0000FF"]Device (PCIB)[/color]
           {
            Name (_ADR, 0x001E0000)
             ..........................................               
            Method (_PRW, 0, NotSerialized)
               {
                   Return (Package (0x02)
                   {
                       0x0B, 
                       0x05
                   })
               }

[color="#0000FF"]Device (FRWR)[/color]
               {
                   Name (_ADR, 0x04010000)
                   Name (_SUN, 0x2) // PCI slot 2
          	    Name (_GPE, 0x0B)
	    Method (_DSM, 4, NotSerialized)
                   {
                       Store (Package (0x06)
                       {
                           "device-id",  Buffer (0x04) {0x23, 0x80, 0x00, 0x00},
                           "fwhub",      Buffer (0x04) {0x00, 0x00, 0x00, 0x00},
                           "name",       "Texas Instruments TSB43AB22 IEEE-1394 Controller"
                       }, Local0)
                       DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                       Return (Local0)
                   }
               }
           }

Share this post


Link to post
Share on other sites
not working for me too, the error is gone but i cant plug and mount my mybook FW drive..

 

And after a sleep and wake? Can you see it?

Share this post


Link to post
Share on other sites
same! i even tried logging out and it wont just mount or even detected in disk utility.

 

On impulse I tried powering on scanner after boot and un-plugging from the mobo, then re-attaching it

That didn't work

 

I'm wondering if this is because the scanner is powered with its own complex internal mechanisms

(unlike a HD)? But then again it used to work before sleep previously without DSDT

 

There is another device in my DSDT called FWHD - is this related to firewire, if so should I keep or delete?

 

       Device (FWHD)
       {
           Name (_HID, EisaId ("INT0800"))
           Method (_CRS, 0, NotSerialized)
           {
               Name (FWH0, ResourceTemplate ()
               {
                   Memory32Fixed (ReadWrite,
                       0xFFB80000,         // Address Base
                       0x00080000,         // Address Length
                       )
               })
               Return (FWH0)
           }
       }

Share this post


Link to post
Share on other sites
There is another device in my DSDT called FWHD - is this related to firewire, if so should I keep or delete?

That's Firmware Hub device (FWH) or (FHWD) and you don't want to touch that, mate... I was tempted too, before I googled it... Guys, I honestly can't think of anything to say to help you solve this, except, like me, do many DSDT code tests and endless reboots...

 

So to recap; on your mobo's the error disappears but your firewire scanner is not detected after you turn it on, correct? Or even firewire HDD? I have Texas Instruments device, perhaps Agere or others don't behave the same, due to Apple's drivers particularities?

Share this post


Link to post
Share on other sites
That's Firmware Hub device (FWH) or (FHWD) and you don't want to touch that, mate... I was tempted too, before I googled it... Guys, I honestly can't think of anything to say to help you solve this, except, like me, do many DSDT code tests and endless reboots...

 

So to recap; on your mobo's the error disappears but your firewire scanner is not detected after you turn it on, correct? Or even firewire HDD? I have Texas Instruments device, perhaps Agere or others don't behave the same, due to Apple's drivers particularities?

 

 

No problem, thanks for your help. I think I see what the problem is even if I'm not sure how to fix it.

 

I tried having the scanner on before I booted, there are no extra messages in the logs but doing this

I can switch the scanner off and on without having to go through a wake sleep cycle.

 

I assume that unless the powered scanner is on at the start then the original configuration conditions are

somehow not set.

 

This is slightly different from the tested scenario tested yesterday. Here the scanner isn't discovered till after

wake but if I switch it off then I have to do another sleep wake cycle

 

All in all I can live with this because I don't use it that often.

 

So it is working, I just need to remember to power the scanner before I boot otherwise it is just a lump of

metal stuck on the end of a firewire cable

 

Edit:

After sleeping and waking in this scenario the scanner is recognised but claims it is not ready or no film.

This kind of implies that scanners are a bit more complex than HD's and need a few extra features set

Share this post


Link to post
Share on other sites

The associated fix does remove the error for me on boot up ... however it appears to break sleep. When I apply the fix and then sleep (via the apple menu) the computer appears to sleep but the fans continue to spin. If I remove the fix and then sleep the computer completely sleeps with fans off, etc.

 

Any ideas/thoughts?

 

Regards,

SMF

Share this post


Link to post
Share on other sites
The associated fix does remove the error for me on boot up ... however it appears to break sleep. When I apply the fix and then sleep (via the apple menu) the computer appears to sleep but the fans continue to spin. If I remove the fix and then sleep the computer completely sleeps with fans off, etc.

 

Any ideas/thoughts?

 

Regards,

SMF

 

Nice...

 

I have the same issue... (OHR or similar fix this but my goal is do this w/o kext)

So i try and later I post my test result.. ( I try use old method in the first post of the page... unfix this fix :wacko: )

 

Fabio

 

EDIT

Notthing... I think the problem is in the SS code not the Firewire

Share this post


Link to post
Share on other sites
Nice...

I have the same issue... (OHR or similar fix this but my goal is do this w/o kext)

So i try and later I post my test result.. ( I try use old method in the first post of the page... unfix this fix :( )

Fabio

 

EDIT - Notthing... I think the problem is in the SS code not the Firewire

Damn, guys, I also faced the same problem last night, and freaked out. I think that after sleeping/waking the PC for many times, when I turned the firewire HDD on it was not recognised, and slept (to do the detection trick) and it would not sleep--fans were running. I could not wake the thing up, had to reset it (front panel) and it rebooted a few times (got stuck at "Waiting for DSMOS") but then noticed (always on verbose boot -v) this message:

 

31/01/2010 1:00:37 a.m.	FireWire (OHCI) TI ID 8023 built-in now active, GUID 00301b000048628f; max speed s100.

Notice the S100 at the end. I eventually had to reset it a couple of times, remove power plug and wait a few seconds, remove all USB devices (external sticks, HDD and scanner) and booting up came to a normal status (including firewire HDDs). That was scary.

 

I use a more-or-less improved DSDT and only EvOreBoot / FakeSMS / UIDplatform kexts. No SleepEnabler, nor OpenHaltRestart (due to Power Management done by the system). Any ideas, anyone? Am I missing a kext, all this time?

 

Oh and iFabio, what do you mean by "SS code" problem?

Share this post


Link to post
Share on other sites

MacKonsti,

 

What I see in my logs is - "1/29/10 11:56:28 PM kernel System sleep prevented by FRWR". If I remove the fix I can sleep. I haven't been able to find something in the ACPI spec that would help me add code to force the FRWR to sleep - perhaps something in the PTS section of the DSDT.

 

Regards,

SMF

Share this post


Link to post
Share on other sites
Oh and iFabio, what do you mean by "SS code" problem?

 

SS= speedstep

But now I can confirm that is not the SS code the trouble... in my case I also tried the DSDT without "SS" and the problem remains the same.

I will focus to implement the sleep method disabling the Firewire device via BIOS.

When I've also got the sleep I'll do the tests again on firewire.

 

Fabio

 

Sorry for my english.

Share this post


Link to post
Share on other sites

Great work on the fixing guys. For me both solutions give the same problem hot plugging my Apogee Duet. For the rest they seem the same (sleep works with both, but i didn't try n times).

Share this post


Link to post
Share on other sites

Just to add that i also cant sleep with the firewire fix, fans stay on. Without the fix sleep is perfect.

 

Ive also only got an ipod with a firewire cable to test and that does not work before or after sleep, nor connected on a reboot.

 

Regards

Share this post


Link to post
Share on other sites
Just to add that i also cant sleep with the firewire fix, fans stay on. Without the fix sleep is perfect.

 

Ive also only got an ipod with a firewire cable to test and that does not work before or after sleep, nor connected on a reboot.

 

Regards

 

For me the mod don't have any effect on sleep, still working good, but hotplug works only on certain device, not on portable HD, for example.

Share this post


Link to post
Share on other sites

Guys I think I may have found a solution here... While studying the DSDT structure of the other devices like USB etc. I found there's an entry for (_PRW) parameter that's missing from the firewire device. Now just because it ain't there doesn't mean it's not needed. So here's my newly modified code that seems to be working, that I urge you to copy/paste/try and come back with results.

 

First of all, we need a new entry at the end of (_GPE) section, just for firewire (new method "_L1A"):

Method (_L1A, 0, NotSerialized)
{
   Notify (\_SB.PCI0.HUB0.FRWR, 0x00)
   Notify (\_SB.PWRB, 0x02)  // Added notification for power button
}

Just make sure your device description is correct e.g. for me the superset device owning firewire is HUB0, for you could be PCIB etc. The value is on purporse 0x00 despite for USBs being 0x02 (well, you can try and experiment and tell us your findings).

 

Now we need to add a new (_PRW) method in firewire device code, but be careful to keep the (_GPE) value we used before (will explain later):

      Device (FRWR)  // Added device for Texas Instruments TSB43AB22/A IEEE-1394A Controller [104c:8023]
      {
            Name (_ADR, 0x060A0000)  // [b]My firewire address reported by 'lspci -n'[/b]
            Name (_GPE, 0x0B)        // [b]Callback to (_GPE) Method (_L0B) for device owning firewire (HUB0)[/b]

            Method (_DSM, 4, NotSerialized)
            {
                  Store (Package (0x06)
                  {
                      "built-in",
                       Buffer (0x01)
                       {
                            Zero
                       },
                       "fwhub",
                       Buffer (0x04)
                       {
                            0x00, 0x00, 0x00, 0x00
                       },
                       "device-id",
                       Buffer (0x04)
                       {
                            0x23, 0x80, 0x00, 0x00  // [b]Board device ID is [8023] reported by 'lspci -n'[/b]
                       }
                  }, Local0)
                  DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                  Return (Local0)
              }
[color="#0000FF"]
              Method (_PRW, 0, NotSerialized)
              {
                   Return (Package (0x02)
                   {
                        0x1A,  // [b]Callback to new (_GPE) Method (_L1A)[/b]
                        0x05
                   })
              }[/color]
       }

For the 'conservation' error to disappear from bootlogs, we need to make sure the Name (_GPE, 0x0B) entry points to the callback of the superset device owning firewire, not firewire itself (_L1A). In my case, for HUB0 device, the callback in my code points to _L0B, search for yours (e.g. PCIB device?) and just put/leave that value. Don't point this one to the new method _L1A.

 

The new (_PRW) method now should take care of any other calls for power management, just for the firewire itself, through our newly added method in (_GPE) section. Please try this, recompile your DSDT, reboot and let me/us know!

 

I really hope this will help. For me, I can report that when I shut down the hackintosh, the firewire drives now shut also... But if someone with better DSDT knowledge thinks this is a screw up, please post now!!! :censored2:

 

P.S. This code addition doesn't affect the system otherwise (e.g. speed-step etc.)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Posts

    • @onejay09  - thanks again for your help and advice.  I tried various combinations of Info.plist mods (Adding a new Machine entry with my Board ID and GFX0, adding GFX0 to the MacBookPro6,1 Machine entry and adding a Vendor/Device entry to the Board ID and MacBookPro6,1 Machine entries. I thought these might make a difference, but after comparing GPU temps and frequencies to those reported in Windows 7, I'm not seeing any difference.  It appears as though AGPM is natively detecting and handling power management of the NVidia Quadro NVS 140m without any Info.plist mods.   Thanks again.
    • My rig is not booting without the "XCPM bootstrap patch" and "xcpm_program_msrs (c) Pike R. Alpha" patch. Already tested that.  Booting without the TSCAdjustReset.kex is working great and booth sleep and wake is working. The new bios 0603 has an updated microcode and that might be the reason  for the fact that everything is working as it should without the kext.
    • Hello folks,   I may be a privileged user since i own a real mac aka a MBPro 15" mid 2012 runing fine HS... So i wanted to try a personal tip: I hooked my Sandisk 100 GB USB SSD to the real Mac and performed a clean install of High Sierra on it. Then i installed the latest CLOVER on this USB disk and copied the Urashimataro previously provided EFI partition. Then i pluggued this USB to my Xiaomi laptop i5 and tried to boot from this USB SSD. INCREDIBLY BUT TRUE: YES it worked fine. ;-)) Of course i also removed the serials to put mine previously blessed on Sierra...   Happy to share this new tip that lets me boot again my Xiaomi laptop on MacOs, and proud for my own personal solution, since i couldn't retrieve here any workable solution and it drove me crazy and nuts...   Enjoy!
    • Venduto altrove potete chiudere
    • I share your folks pain. Every step forward seems to be two steps backwards in other areas. And at the same time it's soooo worth it with features most forum users are not fully aware of ... yet  Anyway, it would be nice if you could fix this:    Your previous content has been restored.   Not only cannot post as I keep seeing it; the 1st time I saw it also 'restored' (read: removed) something that took me 1 hour to put together. It was a post reply with a quote and image attachments in it. Btw using imgur for external images ain't working either.


×