OS X compatible motherboard -> QUO

valiant · January 15, 2020

On 1/13/2020 at 6:56 AM, IronManJFF said:

You may be running out of PCI Lanes, if you are not using FireWire and/or Thunderbolt, disable them in firmware and see if it helps with Slot 4.

I will try this, but I am a little reluctant. Plugging things in and out of slot 4 is very tight and usually means removing the video card, which makes me nervous every time that I might break something.

valiant · January 15, 2020

Lilu & WhateverGreen?

Did I read that Lily and WhateverGreen were rolled into XMAX-E ROM? I can't find the change notes (SO MANY tabs open in so many places...).

If they were, do I put appropriate kexts into the /Efi/Oz/ partition, or the /boot/EFI/Extras/ folder, or the /boot/Library/Extras/folder?

If they were not rolled in, can they be used in parallel to the UEFI ROM changes?

I am still trying to refine my system and wonder if that's the best way to do it?

Thanks.

IronManJFF · January 15, 2020

Lilu is not been baked into the firmware..

You should put it into the EFI partition in the /Efi/Oz/Darwin/Extensions/Common folder

Delete that /boot/EFI clover (or whatever it is ) {censored}

valiant · January 18, 2020

On 1/15/2020 at 3:32 PM, IronManJFF said:

Lilu is not been baked into the firmware..

You should put it into the EFI partition in the /Efi/Oz/Darwin/Extensions/Common folder

Thanks!

On 1/15/2020 at 3:32 PM, IronManJFF said:

Delete that /boot/EFI clover (or whatever it is ) {censored}

I don't actually have EFI folder - I've just been reading so many articles about getting wifi to work I'm getting more confused than anything...

valiant · January 18, 2020

HDMI sound?

So... I have a "pure" SSD that boots Mojave. It's my reference if you will. But once I got it going I used it to install Mojave over Yosemite on my working fusion volume. I used the bcfg boot addp technique to make it bootable.

However, here's a weird thing. The SSD version has working sound over HDMI. The fusion volume does not. How do I troubleshoot that?

Thanks.

ntsmkfob · January 18, 2020

2 hours ago, valiant said:

Thanks!

I don't actually have EFI folder - I've just been reading so many articles about getting wifi to work I'm getting more confused than anything...

EFI is a separate partition that has to be mounted to open. Use a tool like Hackintool or EFI Agent to see which disks have an EFI and mount them to make changes.

valiant · January 20, 2020

On 1/18/2020 at 4:36 AM, ntsmkfob said:

EFI is a separate partition that has to be mounted to open. Use a tool like Hackintool or EFI Agent to see which disks have an EFI and mount them to make changes.

Thanks for that! I didn't know about EFI Agent. That's a pretty cool tool!

So the MojaveSSD had

/Efi/KernextPatcher.plist
/Efi/KernextPatcherLog.txt
and
/Efi/Oz/defaults.plist

All the other /Efi/* folders were empty

I copied over the KernextPatcher.plist and defaults.plist to matching locations in the /Efi/ folder on the HD portion of the fusion drive. There was already KernextPatcherLog file there for some reason, which I left alone, even though there was no KernextPatcher.plist file yet.

When I went to the SSD portion of the fusion drive, the /Efi/ folder still had a /Quo/ folder in it. I left it alone. There was already a KernextPatcherLog file there too, which I left alone. There was also a defaults.plist. I took a look at it and it had more entries in it than the one from the reference SSD, so I renamed it and copied over the defaults.plist from the SSD.

So all three of the /Efi/ folders now have the same .plist files in the same place.

But when I boot back into the fusion drive, there is no HDMI audio. I found I had soundflower installed from the Yosemite time, so I uninstalled that and rebooted in case that was the problem, but still no HDMI audio.

What can I try next?

Thanks.

Edited January 20, 2020 by valiant
Clarity

IronManJFF · January 21, 2020

You can delete the QUO folder it comes from an earlier version of the firmware.

You don’t need 3 Defaults.plist, that is a recipe for more confusion. Put it in the drive connected to SATA0,0

Now for sound ... in Terminal

kextstat | grep HDA

kextstat | grep ALC

post the results

Edited January 21, 2020 by IronManJFF

valiant · January 21, 2020

8 hours ago, IronManJFF said:

You can delete the QUO folder it comes from an earlier version of the firmware.

Done.

8 hours ago, IronManJFF said:

You don’t need 3 Defaults.plist, that is a recipe for more confusion. Put it in the drive connected to SATA0,0

Even if I'm not booting from the SSD drive connected to SATA0,0?

Eventually I will be booting exclusively from the fusion drive and will remove the SSD to use elsewhere. And in the meantime I boot sometimes from the SSD, sometimes from the fusion. Especially since I'm trying to figure out why HDMI works on SSD but not fusion, so I'm booting back and forth. I thought the defaults.plist needed to be on the /Efi/ of the boot drive, which is why I'm doing it this way. Is it that it just needs to be on whatever is connected to SATA0,0, no matter which volume you're booting from?

And I seem to remember from w-a-y back in the day that a fusion drive needed an /Efi/ folder on both of the physical volumes that made up the logical volume. I could be wrong about that, it was a while ago...

8 hours ago, IronManJFF said:

post the results

This is from the fusion drive, which does not have working HDMI sound:

ConningTower:~ ned$ kextstat | grep HDA
   57    0 0xffffff7f83c7a000 0x4000     0x4000     com.kext.HDAEnabler (1.0.0d1) EE164AC4-5743-278D-92DA-776233CA760F <13 5 3>
   67    0 0xffffff7f83e2c000 0x22000    0x22000    org.fork.driver.VoodooHDA (6.6.6) no UUID <66 13 8 6 5 3>
  121    0 0xffffff7f83d35000 0x73000    0x73000    com.apple.driver.AppleGFXHDA (100.1.414) 5265FEDA-2514-35FE-A458-8F6BA345F2B5 <120 107 66 13 8 7 6 5 3 1>
  124    1 0xffffff7f83053000 0xc000     0xc000     com.apple.iokit.IOHDAFamily (282.54) 039FEBA2-827D-3E0E-93FC-35CF5107EA15 <6 5 3 1>
  125    0 0xffffff7f83062000 0x1d000    0x1d000    com.apple.driver.AppleHDAController (282.54) E00FE0E4-B03D-34C5-8DC9-39C7D8D50B6B <124 107 66 13 8 7 6 5 3 1>
ConningTower:~ ned$

And (null result):

ConningTower:~ ned$ kextstat | grep ALC
ConningTower:~ ned$

Here are the results from the SSD drive, with working HDMI sound:

Conning-Tower:~ admin$ kextstat | grep HDA
   61    0 0xffffff7f826b0000 0x22000    0x22000    org.fork.driver.VoodooHDA (6.6.6) no UUID <60 13 8 6 5 3>
  118    0 0xffffff7f82b72000 0x73000    0x73000    com.apple.driver.AppleGFXHDA (100.1.414) 5265FEDA-2514-35FE-A458-8F6BA345F2B5 <117 106 60 13 8 7 6 5 3 1>
  124    1 0xffffff7f83320000 0xc000     0xc000     com.apple.iokit.IOHDAFamily (282.54) 039FEBA2-827D-3E0E-93FC-35CF5107EA15 <6 5 3 1>
  125    0 0xffffff7f8332c000 0x1c000    0x1c000    com.apple.driver.AppleHDAController (282.54) E00FE0E4-B03D-34C5-8DC9-39C7D8D50B6B <124 106 60 13 8 7 6 5 3 1>
Conning-Tower:~ admin$

And the same null result for ALC as the other drive.

Edited January 21, 2020 by valiant
Additional info

valiant · January 21, 2020

Hmm...

This must be the problem, it's the only difference between the two results:

   57    0 0xffffff7f83c7a000 0x4000     0x4000     com.kext.HDAEnabler (1.0.0d1) EE164AC4-5743-278D-92DA-776233CA760F <13 5 3>

How do I discover where the HDAEnabler kext is being inserted? I checked bootSSD/Library/Extensions/ and bootSSD/System/Library/Extensions/ and it's not in there.

Thanks.

EDIT: Duh. I was looking in bootSSD. When I looked in fusion drive, there was a file called HDAEnabler1.kext in fusion/System/Library/Extensions/

I removed that.

EDIT: Ok, I rebooted to the fusion drive, but still no HDMI sound option:

538606843_ScreenShot2020-01-21at1_40_30PM.jpg.7324f31aecdee06b3b3e05de1710137a.jpg

I seem to recall the necessity to rebuild something when removing files from /System/Library/Extensions/. That may be the problem, but I don't really know how to do that.

Thanks.

Edited January 21, 2020 by valiant
Additional info

IronManJFF · January 21, 2020

4 hours ago, valiant said:

I thought the defaults.plist needed to be on the /Efi/ of the boot drive, which is why I'm doing it this way. Is it that it just needs to be on whatever is connected to SATA0,0, no matter which volume you're booting from?

And I seem to remember from w-a-y back in the day that a fusion drive needed an /Efi/ folder on both of the physical volumes that made up the logical volume. I could be wrong about that, it was a while ago...

Oz will look for Defaults.plist on the drive which is closer the the BIOS which is a weird way of putting it. But if you put it on SATA0,0 then it will find it every time. It does not matter from which drive you load your OS.

When it finds it the first time, it loads and parse it content and then store it in NVRAM... so even if you modify Defaults.plist after that ..IT DOES NOT MATTER until you reset nvram.

And please can you stop all this random shooting ... you are asking for help , we are providing. So do what we ask you , no less , no more (yes I would have told you to remove HDAEnabler which has no business being there anyway) but the way you are going at it does not help us help you.

About /S/L/E

In terminal, you will do

sudo touch /System/Library/Extensions

and then you restart and then shutdown again

After that you will plug the drive that will stay in SATA0,0 into SATA0,0 (Make sure the Defaults.plist that you want is on this drive. BEFORE you plug unplug) and YOU LEAVE IT THERE! There are 6 SATA connectors on this motherboard, so you have 5 connectors for everything else.

VoodooHDA is injected from somewhere and when VoodooHDA gets in AppleHDA gets out, hence no HDMI/DP sound.

In Terminal, you will do ...

nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda

and post the result. That will tell me if VoodooHDA might come from firmware (but i think not)

and

locate Voodoo

That will tell me if it is coming from the filesystem

Also make sure your signature reflects the hardware we have to work with

Edited January 22, 2020 by IronManJFF

valiant · January 22, 2020

18 hours ago, IronManJFF said:
About /S/L/E

In terminal, you will do
sudo touch /System/Library/Extensions
and then you restart and then shutdown again

Thanks for that, I'll save that command.

18 hours ago, IronManJFF said:

After that you will plug the drive that will stay in SATA0,0 into SATA0,0 (Make sure the Defaults.plist that you want is on this drive. BEFORE you plug unplug) and YOU LEAVE IT THERE! There are 6 SATA connectors on this motherboard, so you have 5 connectors for everything else.

OK. I plugged the SSD portion of the fusion drive into SATA0,0 and deleted the /Efi/Oz/defaults.plist from every other drive.

I rebooted twice, then ran the terminal command above.

Then I ran

nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda

and got a weird result:

ConningTower:~ ned$ nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda
-bash: nvram: command not found
ConningTower:~ ned$

Or at least I think that's weird?

Running nvram with no commands did not throw an error.

Running

locate Voodoo

Resulted in:

ConningTower:~ ned$ locate Voodoo
/Applications/Apps/Hardware Apps/[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] - El Capitan Edition/[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url].app/Contents/Resources/VoodooHDA-v2.8.6.pkg
/Applications/Apps/Hardware Apps/[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] - El Capitan Edition/[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url].app/Contents/Resources/VoodooHDA-v2.8.7.pkg
/Applications/Apps/Hardware Apps/[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] - El Capitan Edition/[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url].app/Contents/Resources/VoodooHDA-v2.8.8.pkg
/Applications/Apps/Hardware Apps/[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] - El Capitan Edition/[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url].app/Contents/Resources/VoodooTSCSync-4.pkg
/Applications/Apps/Hardware Apps/[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] - El Capitan Edition/[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url].app/Contents/Resources/VoodooTSCSync-6.pkg
/Applications/Apps/Hardware Apps/[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] - El Capitan Edition/[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url].app/Contents/Resources/VoodooTSCSync-8.pkg
/private/var/db/receipts/com.tonymacx86.[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url].VoodooHDA-13.pkg.bom
/private/var/db/receipts/com.tonymacx86.[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url].VoodooHDA-13.pkg.plist
/private/var/db/receipts/com.tonymacx86.[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url].VoodooHDA-14.pkg.bom
/private/var/db/receipts/com.tonymacx86.[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url].VoodooHDA-14.pkg.plist
/private/var/db/receipts/com.tonymacx86.[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url].VoodooHdaSettingsLoader-1.pkg.bom
/private/var/db/receipts/com.tonymacx86.[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url].VoodooHdaSettingsLoader-1.pkg.plist
ConningTower:~ ned$

It looks like I tried using Unib**** to install El Capitan back in 2013 (I checked the dates). I did not succeed, because the computer was running Yosemite, not El Capitan. I don't know if Voodoo files in those locations inject anything though.

I did not delete anything this time.

What would you recommend next?

Thanks.

PS I updated my sig with current hardware

Edited January 22, 2020 by valiant
Clarity

IronManJFF · January 22, 2020

Weird indeed

try

sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda
or 
/usr/sbin/nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda
or
sudo /usr/sbin/nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda

is ned a regular user or administrator ?

Edited January 22, 2020 by IronManJFF

valiant · January 22, 2020

Ned is admin.

sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda

Result is

508 13:44:06 [fredh:ConningTower~] $ sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda
Password:
nvram: Error getting variable - '1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda': (iokit/common) data was not found
509 13:44:35 [fredh:ConningTower~] $

(fredh is also admin)

Unfortunately

/usr/sbin/nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHd

and

sudo /usr/sbin/nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda

had same result.

I just confirmed this is on the fusion boot drive in case I'd forgotten.

Still weird...

EDIT: rebooted out of the fusion drive and into the SSD and tried the same command:

Conning-Tower:~ admin$ sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda
Password:
nvram: Error getting variable - '1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda': (iokit/common) data was not found
Conning-Tower:~ admin$

Same error...

Edited January 23, 2020 by valiant

IronManJFF · January 23, 2020

nvram: Error getting variable - '1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda': (iokit/common) data was not found

Excellent that means the firmware will try to inject it

Now do this in Terminal to disable injection of VoodooHDA from firmware

sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda=%01

and reboot

Expected result is that in Sound Control Panel all the motherboard audio in and out will disappear (unless they get injected by something else) and your HDMI/DP out should appear...

If you want to revert this change you can issue in Terminal

sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda=%00

Let me know the result.

valiant · January 23, 2020

1 hour ago, IronManJFF said:
do this in Terminal to disable injection of VoodooHDA from firmware
sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableVoodooHda=%01

Argh.

It took me a while to figure this out. It turns out that there is some invisible character inserted between the 0 and the 1 at the end of that command. I couldn't figure out why it wasn't working until I pasted the command into a text editor for closer examination, and the invisible character showed up. Once I deleted it and pasted the repaired command into Terminal it worked.

Sort of.

Yes, the mobo sound options are gone. But the HDMI options did not appear:

1348511263_ScreenShot2020-01-23at12_13_05PM.png.f93aa645aa33f200be6d42faf6d062f7.png

As an experiment I tried the %00 option, and as promised the mobo sound options returned. But still no HDMI audio.

It's pretty obvious that something is left over from the Yosemite days, because the clean install on the SSD has working HDMI (and no video weirdness - I haven't started on that since I think "one thing at a time" but it may be relevant: on the fusion install (Mojave over Yosemite) window tabs are all black, and when I hover over them with my mouse there's a pixellation effect that looks like tearing or stairstepping - this happens in Safari and Terminal, but it's only on "live" display, when I take a screenshot they display normally).

But I don't know how to identify or correct the differences between the clean install and the upgrade install...

What should I try next?

Thanks.

Edited January 23, 2020 by valiant

IronManJFF · January 23, 2020

Have you installed Lilu & WhateverGreen ?

You should put it into the EFI partition in the /Efi/Oz/Darwin/Extensions/Common folder

valiant · January 23, 2020

No, I didn't. I thought it best to minimize the things being changed all at once.

I'll do that now.

(PS I edited my previous post above with new information after I rebooted)

IronManJFF · January 23, 2020

You can check they are properly loaded with

kextstat| grep Lilu
kextstat| grep Green

valiant · January 23, 2020

1 hour ago, IronManJFF said:
You can check they are properly loaded with
kextstat| grep Lilu
kextstat| grep Green

I found a GitHub with lilu 1.4.1 and another one with WhateverGreen 1.3.6. Actually, I found two for each - I went for the simpler one, assuming the larger one is the developer copy. If that's not the case, is there a trusted source for them? (Search seems to be broken on Insanelymac.)

I downloaded them and put the .kext parts of the package into /Efi/Oz/Darwin/Extensions/Common/

I rebooted, and I don't think they are being picked up.

Last login: Thu Jan 23 13:53:14 on ttys000
ConningTower:~ ned$ kextstat | grep Lilu
ConningTower:~ ned$ kextstat | grep Green
ConningTower:~ ned$

I will reboot into the reference SSD and see what happens there.

UPDATE: same result there.

Edited January 23, 2020 by valiant

IronManJFF · January 23, 2020

1 hour ago, valiant said:

I downloaded them and put the .kext parts of the package into /Efi/Oz/Darwin/Extensions/Common/

UPDATE: same result there.

On the drive connected to SATA0,0 ?

The Official Lilu and its plug-ins are at https://github.com/acidanthera/Lilu

Edited January 23, 2020 by IronManJFF

valiant · January 23, 2020

Well hell.

I have a whole new problem.

One of my case fans was failing and I had to remove the Vega 56 to replace it. I took the opportunity to put a PCI extender ribbon into SATA slot 3 before I put the GPU card back in. Now the Quo won’t boot. The lights come on, the fans spin up, then the fans spin down and the lights go off. Then it does it again. And again.

I tried adding the WiFi card to the ribbon, removing the ribbon, removing everything but HDMI, USB keyboard/mouse, unplugging all drives except fusion, unplugging all drives including Blu-ray, reseating all the cables on the mobo, and finally removing the GPU. No difference. The only thing I didn’t do was take the CPU fan off and reseat the CPU since I have no idea where my thermal paste is just now.

This is pretty disheartening. I really don’t even know where to start.

Might you have any suggestions what to do? Perhaps resetting the bios? Or is it time to start googling?

IronManJFF · January 23, 2020

REMOVE THE BATTERY FOR 5 MINUTES

valiant · January 24, 2020

Taking out and reinserting the battery didn’t help. I tested it and it was a little low, so I replaced it with a fresh battery, but that didn’t help either.

valiant · January 24, 2020

I’m trying to invoke the backup firmware as per the wiki. Methods 1 & 2 aren’t working for me. Apparently there’s a method 3, physically shorting out two pins on the motherboard M_BIOS chip. I’m not sure where those two pins are?

EDIT: I found them - labeled CLR_CMOS. Nothing happens while they’re shorted, then the fans spin up when you remove the short.

Still didn’t help though. Won’t boot to UEFI.

Edited January 25, 2020 by valiant
Additional info

OS X compatible motherboard -> QUO

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites