Jump to content
ErmaC

Clover problems report & features request

946 posts in this topic

Recommended Posts

15 hours ago, vladichimescu said:

@Slice I tried looking for a way in clover config.plist to disable a custom SSDT placed in ACPI/patched but I couldn't get one to work.

fact: I created SSDT-DDGPU.aml to disable nvidia dgpu in my laptop (using config.plist to boot 'normal') but I also created a config.dgpu.plist which should drop the loading of SSDT-DDGPU.aml and enable nvidia drivers, yet the only way of ignoring the custom SSDT is by clover GUI, by hand, on each boot, in GUI > drop tables section.

 

is there a flag where the name of the custom/patched SSDT to be ignored/dropped can be set?

regards

Such this?

Снимок экрана 2019-02-15 в 9.13.19.png

Share this post


Link to post
Share on other sites
Advertisement

Hi 

 

What is the right edk2 svn version !

The fourth last commits mentioned 4 different versions. I don't understand.

 

Thanks

Share this post


Link to post
Share on other sites

Hello,I want to ask how to set default installation language ,I use this before

<key>Language</key>

<string>zh_CN:0</string>

But now I found it can not work,install language is english。

Thanks!

Share this post


Link to post
Share on other sites

This seems not "Clover Problem", but my fault.

So, I just "DISKPART > CLEAN" my whole HDD via Windows PE, #OFC after made backups: except.. my ESP -_-

I then recreated new GPT scheme with DiskUtility, got new ESP, restoring OS'es partitions etc.

Bootup to macOS via USB Pendrive then install "Clover for UEFI only" onto ESP.

Now, I'm having this issue on UEFI Shell when navigating to ESP (FSX):

cd [DIR] is not a directory

(no issue with Legacy EFI Shell, though)

I've followed dmazar guides as well:

newfs_msdos -v EFI -F 32 /dev/rdisk0s1
or
sudo newfs_msdos -F 32 -b 1024 -v EFI /dev/rdisk0s1

// also manually:

dd if=/dev/disk${1}s1 count=1 bs=512 of=/tmp/origbs
cp boot1f32 /tmp/newbs
dd if=/tmp/origbs of=/tmp/newbs skip=3 seek=3 bs=1 count=87 conv=notrunc
dd of=/dev/disk${1}s1 count=1 bs=512 if=/tmp/newbs

I've also remade "EFI" (/dev/sda1) with gParted under LinuxLive as well, set as: boot, esp.. install Clover using dd commands, writing EF00 as Type code with GPT Fdisk, but weird is.. still get this issue. So, I'm unable booting UEFI mode #atm. I've placed "FAT-64.efi" on ..\drivers64UEFI too.

 

Is there any missing steps? Thanks.

 

IMG_20190221_235314.png

Edited by Badruzeus

Share this post


Link to post
Share on other sites

I think that you did not create that EFI partition correctly as that is not the GUID that an ESP should get but just a basic data partition. There is an issue with ESPs because of FAT being absolutely terrible to determine which version is being used and lots of drivers make assumptions that are not always correct instead of detecting. I think your best bet is to allow an OS installer to create the EFI partition, I personally usually use gparted in linux because it has never failed to work for me on any computer if I just erase and reinitialize the disk to gpt but I also know that windows, macOS, and (all variants I know of) linux allows this in the installer.

Share this post


Link to post
Share on other sites
16 minutes ago, apianti said:

I think that you did not create that EFI partition correctly as that is not the GUID that an ESP should get but just a basic data partition. There is an issue with ESPs because of FAT being absolutely terrible to determine which version is being used and lots of drivers make assumptions that are not always correct instead of detecting. I think your best bet is to allow an OS installer to create the EFI partition, I personally usually use gparted in linux because it has never failed to work for me on any computer if I just erase and reinitialize the disk to gpt but I also know that windows, macOS, and (all variants I know of) linux allows this in the installer.

 

Ah OK, let me try again from scratch with gParted and not using any Partition Label neither named as "EFI". Thanks.

Screenshot 9.png

Edited by Badruzeus

Share this post


Link to post
Share on other sites

Your partition is 411647 - 2048 = 409599 sectors, but FAT uses clusters. What is your sector per cluster for the volume when you created it? Because

Microsoft's EFI FAT32 specification states that any FAT file system with less than 4085 clusters is FAT12, else any FAT file system with less than 65525 clusters is FAT16, and otherwise it is FAT32.

If you didn't change the cluster size to be like 2 or 4 (-b 1024 flag should be 2) then you end up with less than 65525 clusters and a driver that properly follows the specification would try using FAT16, seems weird that it would be able to display the root directory but just happens to be a weird bug. The volume contains the same information for directories and causes the root directory to be found at cluster 2 where it almost always is because its the first thing.

Share this post


Link to post
Share on other sites

Problem #SOLVED, thank you.

I formatted selected Partition 1 (/dev/disk0s1) under Windows PE's DISKPART >

format fs=fat32 quick unit=2k

Manually copy-paste EFI contents into it w/o any extra steps; and created Clover entry from BIOS is able booting Clover (UEFI). Strange is diskutil list it's partition type as "Microsoft Basic Data / 0700: NO NAME", so I then change Type code with gdisk as "EF00" and named as "EFI".

 

Just bit curious; Isn't it similar to this command under Mac? Weird it didn't work for me previously.. guessing, I did wrong step (or it' s just Windows applied special attributes to ESP?):

sudo newfs_msdos -F 32 -c 2 -v EFI /dev/rdisk0s1

..and I just realized that gParted's mkfs.fat created FAT32 with 1 cluster size for my ESP.

 

But now, I'm unable booting LEGACY Clover. Previously, this was my Boot Order list:

00. FS0:\EFI\CLOVER\CLOVERX64.efi "Clover EFI Bootloader" (UEFI)

01. Hitachi HTS545050B9A300 SATA-HDD (Legacy - boot0ss, boot1f32)

02. FS0:\EFI\ubuntu\grubx64.efi "Ubuntu 18.04.2" (IDK this was UEFI or Legacy)

...

> When booting Clover UEFI then Function: Exit, it boots Clover Legacy by default. Exit from Clover Legacy, it boots Ubuntu's Grub2 Bootloader. These abilities have gone at the moment. Actually, not a big deal.. but last time I was able to get Clover Startup Sound with Legacy, now only with UEFI.

Edited by Badruzeus

Share this post


Link to post
Share on other sites

There's a gpt partition tool gdisk

It is available on Linux

and for Windows

https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.4/gdisk-binaries/gdisk-windows-1.0.4.zip/download

and version for macOS can be complied from the sources

https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.4/gptfdisk-1.0.4.tar.gz/download

 

It is parallel of fdisk, but for gpt and knows how to do anything you may need to do with gpt.

Edited by Zenith432

Share this post


Link to post
Share on other sites

The cluster size doesn't matter as long as it's 1, 2, or 4, so you end up with more than 65525 clusters. You didn't create an EFI partition, in both gparted and diskpart there is a special way to create an ESP, that you must specify you want an ESP. Google how to make an EFI partition in either. Not sure how newfs_msdos determines whether to make an EFI or basic data volume but probably just the first partition on a GPT or something, or maybe macOS just assumes because of the PMBR that it is an EFI but it actually is not because it did not have the EFI GUID when you showed the device path in the shell.

Share this post


Link to post
Share on other sites
11 minutes ago, apianti said:

The cluster size doesn't matter as long as it's 1, 2, or 4, so you end up with more than 65525 clusters. You didn't create an EFI partition, in both gparted and diskpart there is a special way to create an ESP, that you must specify you want an ESP. Google how to make an EFI partition in either. Not sure how newfs_msdos determines whether to make an EFI or basic data volume but probably just the first partition on a GPT or something, or maybe macOS just assumes because of the PMBR that it is an EFI but it actually is not because it did not have the EFI GUID when you showed the device path in the shell.

OK, that's why with diskpart formatted FAT32 I was unable to rebuild Windows BCD;

cd /d z:\EFI\Microsoft\Boot\
bootrec /RebuildBcd
//System Partition not found

I think bcoz it uses "MS Basic Data" type (0700) instead of "ESP" (EF00), right?

Till I manually changed it's type code with gdisk.

Share this post


Link to post
Share on other sites

Yeah you have to delete the partition and recreate it with efi format, that's the only way to do it in diskpart. You can just reformat it in gparted, but you have to make sure you change the parameters of the cluster size either way so it's less than 8, or increase the size of the partition so that it will be FAT32 no matter what. That might be pretty wasteful though.

Share this post


Link to post
Share on other sites

Sorry for bit #OffTopic;

I got this when tried building latest AudioPkg..

 

 

MacBook-Pro:~ badruzeus$ cd /Users/badruzeus/udk/EXT_PACKAGES/AudioPkg 

MacBook-Pro:AudioPkg badruzeus$ git pull

remote: Enumerating objects: 18, done.

remote: Counting objects: 100% (18/18), done.

remote: Compressing objects: 100% (7/7), done.

remote: Total 10 (delta 6), reused 7 (delta 3), pack-reused 0

Unpacking objects: 100% (10/10), done.

From https://github.com/Goldfish64/AudioPkg

   4b82d5e..dcbf8ff  master     -> origin/master

Updating 4b82d5e..dcbf8ff

Fast-forward

 Application/HdaCodecDump/HdaCodecDump.c | 2 +-

 1 file changed, 1 insertion(+), 1 deletion(-)

MacBook-Pro:AudioPkg badruzeus$ ls

Application Binaries LICENSE README.md macbuild.tool

AudioPkg.dec External Library UDK

AudioPkg.dsc Include Platform debbuild.sh

MacBook-Pro:AudioPkg badruzeus$ ./macbuild.tool

Already up to date.

ln: AudioPkg: File exists

 

 

I've removed ../Binaries, ../UDK/Build.. but still won't build. Thanks.

Edited by Badruzeus

Share this post


Link to post
Share on other sites
7 hours ago, apianti said:

Because of this line and the next, probably. https://github.com/Goldfish64/AudioPkg/blob/master/macbuild.tool#L123. Unsure what that is even supposed to be doing.

OK, thanks. It needs re-cloning "UDK" on build.

 

About my prev. post (related to: `cd [XXX]: is not a Directory` with UEFI Shell), I realized that having this issue after manually copying EFI contents with File Manager (eg. Windows Explorer, from [LocalDisk_NTFS]:\Backups\EFI\ to [FAT32_ESP]:\). No problem if using `cmd > xcopy /s [source] [target]`, is there any special "attributes" for EFI contents? Weird is with Linux thing goes fine with $ sudo mount /dev/sdaX esp && sudo cp -r [efi_backup] esp. Or.., it was just my bad with wrong FAT format.

Edited by Badruzeus

Share this post


Link to post
Share on other sites

How did you mount the EFI partition in windows explorer? As far as I knew you could only mount it with the command line or by using explorer++. I can't mount any EFI partition to be visible in explorer even with admin privileges...?

Share this post


Link to post
Share on other sites
46 minutes ago, apianti said:

How did you mount the EFI partition in windows explorer? As far as I knew you could only mount it with the command line or by using explorer++. I can't mount any EFI partition to be visible in explorer even with admin privileges...?

// cmd as Administrator
DISKPART
> sel Disk X
> sel Partition Y
> assign letter=Z:
> exit
// Task Manager as Administrator, File, Browse.

I'm not sure if that is good; seems like missing ESP's files / folder attributes < if they previously were installed from HFS+; or it's just my mac's root which has permissions issue. Yes, I use Finder addon: XtraFinder (no attributes options changed though).

Share this post


Link to post
Share on other sites
5 hours ago, apianti said:

How did you mount the EFI partition in windows explorer? As far as I knew you could only mount it with the command line or by using explorer++. I can't mount any EFI partition to be visible in explorer even with admin privileges...?

I don't follow you, because if I mount the boot efi partition from a command prompt with "mountvol T: /S" then afterwards I see the efi partition in T: in explorer.  Any other efi partitions than the boot one can be mounted from a command prompt by running "mountvol" to display the available mountpoints and then choosing the right one using the "mountvol T: <VolumeName>" format.  The partition will then be visible in explorer.

Edited by Zenith432

Share this post


Link to post
Share on other sites
23 hours ago, Badruzeus said:

// cmd as Administrator
DISKPART
> sel Disk X
> sel Partition Y
> assign letter=Z:
> exit
// Task Manager as Administrator, File, Browse.

I'm not sure if that is good; seems like missing ESP's files / folder attributes < if they previously were installed from HFS+; or it's just my mac's root which has permissions issue. Yes, I use Finder addon: XtraFinder (no attributes options changed though).

 

18 hours ago, Zenith432 said:

I don't follow you, because if I mount the boot efi partition from a command prompt with "mountvol T: /S" then afterwards I see the efi partition in T: in explorer.  Any other efi partitions than the boot one can be mounted from a command prompt by running "mountvol" to display the available mountpoints and then choosing the right one using the "mountvol T: <VolumeName>" format.  The partition will then be visible in explorer.

 

Yeah, both of these result in assigning a drive letter to the partition but even if I open explorer as admin it says it doesn't have permission for any EFI partition on any disk and won't let me open them. So I can only access it through the command line or explorer++...

Share this post


Link to post
Share on other sites

api if you are booting windows 10 try mounting EFI in safe mode. you hold left shift key while telling windows 10 to restart from the windows button shutdown menu. that has worked for me in the past using the mountvol X: /s command and normal windows explorer

Share this post


Link to post
Share on other sites
--- a/Drivers/AudioDxe/HdaCodec/HdaCodec.c
+++ b/Drivers/AudioDxe/HdaCodec/HdaCodec.c
@@ -240,6 +240,8 @@
             if (EFI_ERROR(Status))
                 return Status;
             HdaWidget->DefaultEapd = (UINT8)Response;
+            HdaWidget->DefaultEapd &? = 0x7;
+            HdaWidget->DefaultEapd |= HDA_EAPD_BTL_ENABLE_EAPD;
             //DEBUG((DEBUG_INFO, "Widget @ 0x%X EAPD: 0x%X\n", HdaWidget->NodeId, HdaWidget->DefaultEapd));
         }

What is this new C operator &? introduced in r4890?

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.

Announcements

  • Similar Content

    • By STLVNUB
      *Put the script into its own folder as it will create other folders*
      What is BTB?
      Script file to clone and help build Clover or Opencore repos
      Script will create link to itself in /usr/local/bin/bob
      Script SHOULD fix up any stray bobs you may have.
      Then you only need to type bob. and a parameter
      "a" for ACID repo, official
      "d" for ACID repo DUET build
      "c" for CLOVER
      "e" to erase UDK Folder
      Easier typing bob than.....usual stuff
      YOU WILL NEED TO cmod+x THE SCRIPT
      Enjoy
       
    • By cvad
      View File Bootdisk Utility
      Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
      Anyone who likes the program, please support its Community Score.
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
    • By ALGhackintosh
      Hi @chris1111 i have a tenda w311ma usb wireless adapter , i wanted to make it work with my catalina hackintosh so i installed the driver from the official site , the Rt2870driver.kext file and your wireless panel utility but i have a problem : The software dosent always connect to the acess points and when it does , and everything seems to be ok (even in network section of the system preferences ) when i go to safari for example it tells me that im not connected . I tried to connect the pc to my phone using hotspot , same problem in the pc it shows connected to network but in the phone the pc doesnt appear in the list of the connected devices . What to do ? Please help me !
       
×