Jump to content

collac432

Members
  • Content count

    11
  • Joined

  • Last visited

About collac432

  • Rank
    InsanelyMac Protégé
  1. Clover General discussion

    @n3ph For my experience with graphics drivers, white screen is due to graphics accelerator (AppleIntelHDx000GLDriver.kext on Intel HD case). Try to removing the corresponding kext for ati. If you can get desktop, you will have to deal with this kext.
  2. Clover General discussion

    Sure. I attach ShellEFILogs by the way SellEFILogs.zip Hi Slice. Yes, both kexts are loaded. Thank you for your help guys.
  3. Clover General discussion

    I know, but I'd like to get iMessages running, besides the fact that this can be the first of others comming needing RT variables. I've used your DumpUefiCalls.efi and boot/runtime services gets variables requested ok. With InjectSystemID=no, SmUUID=EB 9D 2D 31 2D 88 11 D3 9A 16 78 45 C4 06 xx xx: ... ->GetVariable(ROM, gEfiAppleNvramGuid, 0/6, 6, CC167258) = Success 78 45 C4 06 xx xx | xE..xx ->GetVariable(MLB, gEfiAppleNvramGuid, 0/6, 11, CC1671D0) = Success 57 38 30 43 xx xx xx 41 44 48 4A 46 31 32 33 34 | W80CxxxADHJF1234 35 | 5 ... Variables: 00000006 BS+RT+ gEfiAppleNvramGuid:MLB, DataSize = 11 57 38 30 43 xx xx xx 41 44 48 4A 46 31 32 33 34 | W80CxxxADHJF1234 35 | 5 00000006 BS+RT+ gEfiAppleNvramGuid:ROM, DataSize = 6 78 45 C4 06 xx xx | xE..xx 00000006 BS+RT+ gEfiAppleBootGuid:platform-uuid, DataSize = 10 EB 9D 2D 31 2D 88 11 D3 9A 16 78 45 C4 06 xx xx | ..-1-.....xE..xx As you can see, the platform-uuid is set correctly, but my profile system shows me "UUID de hardware: 00000000-0000-1000-8000-7845C406xxxx" (7845C406xxxx is my ethernet mac address). Same with nvram -p: Davids-iMac:~ David$ nvram -p platform-uuid %00%00%00%00%00%00%10%00%80%00xE%c4%06xx fmm-computer-name David%e2%80%99s iMac For some reason, those variables are ignored, may be when userland launched? It makes you any sense?
  4. Clover General discussion

    By the way, in boot.log appears "FSInjection: not requested". As I added RtVariables to config.plist with MLB key, this should be injected by FSInjection?
  5. Clover General discussion

    Yeah! Davids-iMac:~ David$ ioreg -l -p IODeviceTree | grep \"system-id | "system-id" = <44454c4c590010488050b2c04fxxxxxx> No luck... Davids-iMac:~ David$ sudo nvram MyVar=TestValue Password: Davids-iMac:~ David$ nvram -p MyVar TestValue fmm-computer-name David%e2%80%99s iMac Davids-iMac:~ David$ In EFI Shell, MyVar was not there, neither "fmm-computer-name"
  6. Clover General discussion

    I'm totally sure I'm using UEFI boot. In fact, that is the only boot method I've tried and the reason for choosing Clover as boot loader. I think CLover UEFI boot is the most aproach to apple stuff. The bad thing is that my system is a Dell optiplex 390 desktop. This board has given me many problems (ATA, graphics, etc.) but finally, after hard read and read, is running So, I've been doing some researches and that's is what I found: - boot.log shows following messages: (removed messages no import ants) ... 0:101 0:000 Starting rEFIt rev 980 on American Megatrends EFI ... 139 0:000 Clover revision: 980 running on OptiPlex 390 0:139 0:000 ... with board 0M5DCD 0:152 0:012 Using OEM config.plist at path: EFI\config.plist 0:152 0:000 Loading early settings 0:152 0:000 LoadDrivers() start 0:161 0:008 Starting HFSPlus.efi 0:173 0:012 Using load options 'HFSPlus.efi ' 0:173 0:000 - driver needs connecting 0:173 0:000 Starting FSInject-64.efi 0:186 0:012 Using load options 'FSInject-64.efi ' 0:186 0:000 Starting CsmVideoDxe-64.efi 0:198 0:012 Using load options 'CsmVideoDxe-64.efi ' 0:198 0:000 - driver needs connecting 0:198 0:000 Starting OsxAptioFixDrv-64.efi 0:207 0:008 Using load options 'OsxAptioFixDrv-64.efi ' 0:207 0:000 Starting OsxFatBinaryDrv-64.efi 0:219 0:012 Using load options 'OsxFatBinaryDrv-64.efi ' 0:219 0:000 2 drivers needs connecting ... 0:219 0:000 PlatformDriverOverrideProtocol not found. Installing ... Success 0:219 0:000 Edid: size=128 ... 3:380 0:000 FindStartupDiskVolume ... 3:380 0:000 GetEfiBootDeviceFromNvram: 3:383 0:002 efi-boot-device-data: Acpi(PNP0A03,0)/Pci(1F|2)/Ata(Primary,Master)/HD(Part2,Sig83BD7E68-885D-4C37-BE2A-D71A1D63886E) 3:383 0:000 Volume: 'Acpi(PNP0A03,0)/Pci(1F|2)/Ata(Primary,Master)/HD(Part2,Sig83BD7E68-885D-4C37-BE2A-D71A1D63886E)' 3:383 0:000 LoaderPath: '' 3:383 0:000 Guid = 83BD7E68-885D-4C37-BE2A-D71A1D63886E 3:383 0:000 FindStartupDiskVolume searching ... ... Last part, makes me think that "efi-boot-device-data" exists in NVRAM. Then, why "nvram -p" does not show me it? Other message I don't know if I have to care about is "PlatformDriverOverrideProtocol not found. Installing ... Success" and don't know if it is related to next finding. - I've tried to get my system-id to check if the lasts bytes match with my en0 MAC address. As you explains here, I've set InjectSystemID=Yes and no CustomUUID, so my system-id must be located into IODeviceTree:/efi/platform/system-id... but it does not: Davids-iMac:~ David$ ioreg -p IODeviceTree +-o Root +-o / +-o chosen | +-o memory-map +-o efi | +-o kernel-compatibility | +-o runtime-services | +-o configuration-table | | +-o EB9D2D31-2D88-11D3-9A16-xxxxxxxxxxxx | | +-o 8868E871-E4F1-11D3-BC22-xxxxxxxxxxxx | | +-o 49152E77-1ADA-4764-B7A2-xxxxxxxxxxxx | | +-o 4C19049F-4137-4DD3-9C10-xxxxxxxxxxxx | | +-o 7739F24C-93D7-11D4-9A3A-xxxxxxxxxxxx | | +-o 05AD34BA-6F02-4214-952E-xxxxxxxxxxxx | +-o platform +-o cpus (none of the UUID endings match my ethernet mac address and I don't know if my system-id must be one of them) At this point, it seems like something goes wrong with my NVRAM variables/efi injection. What do you think? If you need some more info/logs/tests from me, feel free to ask. Thank you!
  7. Clover General discussion

    Yes, I'm using UEFI boot, and I didn't know this about real NVRAM booting this way (I thought only real Macs having NVRAM ). Thanks for the explanation But It's a bit confusing the fact that nvram.plist is generated by rc.shutdown.local script. This script is just using the "nvram -px" command to save the output in nvram.plist. So when I type the command in Terminal, I have the same output, only "fmm-computer-name". Any idea about other thing I could check?
  8. Clover General discussion

    Ok. I just have those files ( FSInject-64.efi, HFSPlus.efi, OsxFatBinaryDrv-64.efi, OsxAptioFixDrv-64.efi) and MLB key in config.plist (as my serial + 5 digits to make it 17 chars long) but iMessage behavior is exactly the same as before update to rev.980. Having in mind that my nvram.plist only shows "fmm-computer-name" key, may be clover is not injecting any efi variable for some reason? (I think this is done by FSInject-64.efi, right?)
  9. Clover General discussion

    Is EmuVariableUEFI-64.efi not necessary to inject RT variables needed to fix iMessage problem? If I add EmuVariableUEFI-64.efi to /Efi/drivers64UEFI, kernel panic related to "com.apple.driver.EFIRuntime". Without this, iMessage still can't register even MLB key added to config.plist. Any clue?
  10. No FireWire after 10.5.6 update

    Can anyone post 10.5.5 AppleHPET.kext ? Thanks.
×