Leaderboard

Yeah, of course, anyone who would like to work on the wiki can PM me your sourceforge user name and I will give you permission to edit the wiki.

I will look at adding that soon. Interestingly enough I changed Hackintool to use the pcidebug value in IOReg instead of gfxutil yesterday as I was finding it was more accurate. If you get a chance check out Hackintool 2.3.4 and see if the exported values are correct. It will now generate a table and a json format files. Next I will add Devices/Properties and perhaps even DSDT format.

Public Beta isn't out yet, only Developer Beta. Edit: Now it is LOL

@headkaze I applaud your effort and time spent developing this excellent tool, kudos for implementing some of the user feature requests.

Hi, can this be fixed in an upcoming release? In the PCI section the device is shown correctly: In the "PCIManeger" tool you are correctly informed: Thank you

I can only speak 2 languages fluently. One of which is my native language. :)) I also speak a bit of Spanish, French, Italian, Russian, and currently learning a bit of Japanese, as well. I definitely know the bad words in some of these. :))) But, for these last ones, I can't say I speak well enough to get a translation done. So, in other words, yeah, that would help.

Clover wiki has been migrated back to sourceforge to try to keep it as up to date as possible, and is now live. Please use this wiki as official from now on. https://sourceforge.net/p/cloverefiboot/wiki/Home/ EDIT: You may comment fixes and suggestions to a page, but they are subject to moderation by admin (basically slice and I) unless you are a team member (but ultimately still manually moderated if necessary). EDIT2: Forgot to give a huge shout out to @arsradu for migrating and updating the wiki. Thanks!

this is OPEMU for Lilu Plugin Intel Haswell Pentium / Celeron Series Or older processor expansion instruction set Emulation USAGE: copy Lilu.kext & OpcodeEmulator.kext To /EFI/CLOVER/kexts/Other/ NOTE: if it don't work, please rebuild Lilu and OpcodeEmulator On Your Machine. Lilu Releases: https://github.com/acidanthera/Lilu/releases UPD: 2017/11/17 FIX kernel_trap UPD: 2019/02/11 BMI1/BMI2 Instruction Set Fix UPD: 2019/02/15 Store & Load x86/x64 Register Fix UPD: 2019/02/18 Modrm Addressing、XMM/R64/R32 Register Store & Load Fix UPD: 2019/02/20 BMI1/BMI2 Instruction Set Completed UPD: 2019/02/22 IMM Byte Fix UPD: 2019/03/03 High Sierra Support UPD: 2019/03/07 "lock" & "ud2" instruction return UPD: 2019/04/08 add YMM Register & F16C Instruction Set & VSSEX Instruction Set UPD: 2019/04/25 add AES / VAES Instruction Set、AVX 2.0 Gather Instruction、VSIB Addressing UPD: 2019/05/03 add AVX / AVX2 / FMA Instruction Set UPD: 2019/05/15 VSSE (VEX SSE) 、VSSE2 (VEX SSE2) Instruction Set Completed. UPD: 2019/05/18 VSSE3、VSSSE3、VSSE4.1 VSSE4.2 Instruction Set Completed. UPD: 2019/05/19 add "vpclmulqdq" instruction. & fix BMI andn & bzhi instruction. UPD: 2019/05/20 add "sysenter"、"sysexit" instruction for AMD Machines 32-bit Mode UPD: 2019/05/21 add "vpclmulqdq" VEX.256 Version & Update Lilu to 1.3.5 (Build based on Lilu 1.3.5) UPD: 2019/05/25 YMM Register Store & Load FIX. AVX、AVX 2.0 Opcode Emulator Completed. OpcodeEmulator-20190525.zip

Known bug since beta 2 with AMD dGPU's. Same for me (purple lines before white flash) with RX560 or 580. But like @CMMChris told me, not a big deal...

How to support AMD: Migrate source code content to (opemu.c for AMD) Rebuild xnu

fdisk440 is not needed because you can just use dd, which is already available, so I'm pretty sure that is just a script. You need to preserve the last 72 bytes of the master/partition boot record, the first 440 are for boot code and the last two are the bootable flag, 70 bytes give a description of the format of the disk/partition beyond that boot record sector. fdisk will just modify that information for the master boot record, (i.e. the four primary partitions for the disk). Because actually there is no such thing a FAT12/FAT16/FAT32 anymore it's actually VFAT and the number of total clusters determine the actual type that is used. So you had to reduce from 4096 to 2048 bytes per cluster to get less sectors per cluster giving you more clusters so that it probably became FAT32 like you specified instead of FAT16 like it would expect when being read after it checked the cluster count. FAT filesystems are not case sensitive. Yeah, I wouldn't really worry about the messages if you still have everything working, unless you have a really old machine I very much doubt it has LPC, let alone anything actually connected to it. Far more likely that it is using GPIO (i2c and SMBus) or SPI if it's newer. It's probably a bug in the beta, this frequently happens in the betas, at least the image is there and not just a black screen for the first part like last time.....

https://olarila.com/forum/viewtopic.php?f=62&t=9766

@arsradu: rebooted 6 times in a row (3 times with USB stick and 3 times with EFI on SSD updated) and problem seems solved.

Hi Patrice, I'm currently on Lilu 1.3.5 (official) and AppleALC 1.3.7 (built by me). Aaand...so far so good. If you wanna try them on your computer, you can find them attached to this post. AppleALC1.3.7&Lilu1.3.5.zip Edit: Now I saw that 1.3.7 is officially released. So...I guess it should be fixed with this release. Haven't tried it yet.

hello @vandroiy2012 I have a new codec. (At the request of the user in two variants.) ALC892 - LayoutID 17 (11) for MSI B150M MORTAR (Outputs SwitchMode) ALC892 - LayoutID 18 (12) for MSI B150M MORTAR (Outputs ManualMode) new_Resources.zip can you please added the new codec? many thanks

Yeah, there's stuff all over it that needs finished, fixed, or removed. Anyone who is already at least a member of the project can edit the wiki. I decided against making it open to anyone to reduce the incorrect changes that could amass or prevent someone straight up deleting information. I agree, I know a few languages but not well enough to translate any better or even close to just literally using Google or Yandex translate. I'll stick to English and a mediocre illiterate child's Russian. 1. It depends how you installed it, you may have overwritten the volume label or other information for the volume. 2. You can zero out the last two bytes of a MBR or PBR and that will make it not bootable. You can put 0x55, 0xAA back to make it bootable again. Refer to the PC BIOS boot reference for more information. 3. Fix only applies to macOS. You need to fix your ACPI tables for linux. You're missing that method to support ASPM states I'm guessing. Not sure if it's fixable in the legacy firmware, I don't see why it wouldn't be present in your original tables if your machine supported it, unless it's disabled in the firmware. 4. Also only fixes for macOS. Hmmmm..... Unsure why it would have overlapping regions, that's strange but I really doubt you need LPC. Also, the fact it is attempting to use ACPI and then says to use an ACPI driver instead makes no sense.... This may also be a side effect of legacy?

Grazie di tutto

@apianti In config.plist/ACPI/DSDT/Fixes, bitmask suffix can be remove right? @arsradu you may also check this changes regarding my concern above. Thanks for the new wiki

@apianti @arsradu, thank you guys for moving the wiki, it was a much needed change. Do you have plans to add the translated pages too? I can work on the spanish section and get it up to date.

iMac 19,1

Update feito, na App Store e correu tudo bem... tudo funciona como deve...

Thanks @iCanaro, that's it...

hardware info by videoproc

Hi @Mroverst, At this moment I don’t remember the name of the program but is the same of the @iCanaro, and when I return home I’ll see the name of the program and tell you...

provato ad avviare da USB con il minimo sindacale???

Hi, @headkaze, u can add option save as .txt in PCI List? Thank u!

If the things keep going on that way, soon or later we'll be able to patch our DSDT on it Keep your great job team