Vintage issue bootloader

[Edhawk]

This is the kext installed:

Where exactly are these kexts installed? Which other kexts have you included in this location?

Assumption from this screenshot is that you are not using AppleALC.kext for your ALC889 audio codec.

Are you using WhateverGreen.kext in your /Library/Extensions folder?
Or are you just relying on ATI=True in your config.plist?

 

[Edhawk]

I have a Legacy Clover EFI prepared for your system, but can't finish it without knowing where the kexts are installed and which kexts you are using within El Capitan. As any kexts I add to the new Clover_r5119 EFI could clash with the kexts already in your system, i.e. /System/Library/Extensions or /Library/Extensions folders.

Legacy Clover EFI folder,
This is lacking a patched DSDT.aml & the final edits to config.plist.

The DSDT Database doesn't have a patched DSDT.aml for the GA-P55 UD4 motherboard with Bios F15. The latest Bios for GA-P55 UD4 motherboard is F10.



There is a patched DSDT.aml for GA-P55A UD4 with Bios F15 in the TMx86 DSDT Database, is this your motherboard?



Are you using the wrong patched DSDT.aml for you system?
Are you using the wrong Bios for your motherboard?

 

[Edhawk]

This is a screenshot of the partially completed Clover Legacy EFI.

Legacy CLOVER EFI folder viewed in Finder.

IF you notice the 'boot' file at the top of the Tree, this is what makes the Legacy Clover EFI work on old Bios systems. Without this 'boot' file the system won't boot in to Clover.

 

[moriarty]

It's a P55A-UD4 F15.
Sorry, my mistake. When I put the build does not exist this model, I think...

 

[Edhawk]

OK, that's fine as long as we have the correct patched DSDT.aml for your system.

 

[Edhawk]

Can you do the following:

Boot in to El Capitan.

1. Launch the Terminal app (found within your Applications > Utilites folder)
2. Type (or copy and paste) the following command:

kextstat | grep -v com.apple

1. Press Enter
2. Within moments Terminal will list all 3rd party kernel extensions (Note: you may need to stretch the Terminal window so it's easier to see and read).

Copy and paste the list of 3rd party kexts to a TextEdit document, save it and post a zipped copy here. So I can see which 3rd Party Kexts are present in your setup.

 

[moriarty]

El Capitan photo tree

Upload entire El Capitan/EFI, by the way... (and the DSDT patched for the system, of course).

Got two EFI... (Clover/EFI y El Capitan/EFI/EFI) I think it is weird... comparing your EFI... but the system works...

 

[moriarty]

3rd Party Kexts from terminal:

Last login: Mon Nov 27 20:33:27 on console
RiffRicos-Mac-Pro:~ riffrico$ kextstat | grep -v com.apple
Index Refs Address Size Wired Name (Version) UUID <Linked Against>
14 0 0xffffff7f80f78000 0x2000 0x2000 org.tgwbd.driver.NullCPUPowerManagement (1.0.0d2) 93D39664-55FB-9220-39AD-A436B33DB160 <7 4 3>
19 3 0xffffff7f81941000 0x19000 0x19000 org.netkas.driver.FakeSMC (1328) 1368FF02-1329-346F-98D6-599CE439340E <11 7 5 4 3 1>
24 0 0xffffff7f8199b000 0x5000 0x5000 org.hwsensors.driver.CPUSensors (1328) 2227862F-9B94-341B-9274-15783442BEEE <19 7 5 4 3>
42 0 0xffffff7f81975000 0x15000 0x15000 org.hwsensors.driver.GPUSensors (1328) B854C5C5-ACFE-3AC1-ACC1-A0BB28AE524C <19 12 11 7 5 4 3>
48 0 0xffffff7f8195e000 0x14000 0x14000 org.hwsensors.driver.LPCSensors (1328) 5FA24C87-70C6-3288-B222-5296B3FEE543 <19 12 11 7 5 4 3>
51 0 0xffffff7f80f13000 0x34000 0x34000 com.lnx2mac.driver.RealtekRTL81xx (0.0.90) 176B89CC-A2D7-1DC6-5F16-DC877BC80189 <50 12 5 4 3 1>
120 0 0xffffff7f80a21000 0x37000 0x37000 com.paragon-software.filesystems.extfs (30.3.11) FB7BD498-B52E-3B42-AFD6-

E17D4F15266E <7 5 4 1>
RiffRicos-Mac-Pro:~ riffrico$

 

[Edhawk]

Thank you.

That tells me you don't need FakeSMC.kext or as I was going to add VirtualSMC.kext in your /EFI/CLOVER/Kexts/Other folder, as it and the associated Sensor kexts are already in your macOS setup.

Same goes for the RealtekRTL81xx Ethernet kext and NullCPUPowerManagement.kext.

Adding a newer version of these kexts could have caused the system to kernel panic.

The 'Paragon-Software extfs' entry for the Linux ext file system is nothing to worry about, as it won't affect the way your system boots.

Which SMBIOS are you using, MacPro3,1, 4,1, 5,1 or 6,1?

 

[Edhawk]

OK, so you are using MacPro3,1 SMBIOS.