Jump to content

apianti

Developers
  • Content Count

    1,274
  • Joined

  • Last visited

  • Days Won

    29

apianti last won the day on May 3

apianti had the most liked content!

4 Followers

About apianti

  • Rank
    I have dementia!

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. apianti

    Clover General discussion

    No, actually neither is capable of creating EFI entries in the way you think. They both can create one entry, the one pointed to by {bootmgr} (previously bcdedit could only modify the entry but it seems that it creates it now as well if needed). The firmware entries are added by bootmgfw.efi to the BCD that is passed into the system for usage (through the registry) and to prevent not having a default loader has some setting to replace BOOTX64.efi (while apparently not properly enumerating the rest of the firmware entries). I'm going to turn off my notifications now. Because I am serious, I am not enjoying doing this anymore.
  2. apianti

    Clover General discussion

    No, I'm just generally irritated by the fact that I research things, say what is going on, people say some nonsense, I provide documentation/evidence, no one reads it, and then says the same things without any evidence to the contrary of what I said. For instance, I am in windows 10, plugged in an ubuntu installer and ran these commands, at no point did I restart: Magically.... I have a firmware application for the usb! BOOTX64.efi does not get overwritten. However, if I clean the USB and perform the same command. BOOTX64.efi is written, back to original output of bcdedit with no firmware applications, if I then overwrite BOOTX64.efi and then run the same command again, BOOTX64.efi is overwritten. EDIT: And that is called the prestige. Good night! EDIT2: I forgot to say don't do this as you can destroy your whole installation.
  3. apianti

    Clover General discussion

    What build version? My point is that bcdboot is what initializes the BCD, according to the documentation bcdboot can only set windows boot manager and bcdedit can only read entries from the BCD. Did you ADD an entry and then it appeared in that list? Because changing the order is simply matching the order of variables. Since literally NONE of my five computers display any of these entries, they had to have been created by bcdboot when creating the BCD. I always install windows first, but even my surface pro and stick pc do not show these entries and windows was preinstalled, is the same version, and both have other OSes as well. Sigh... I literally just described to you a situation where windows can be booted from a different location BY DESIGN. Why would windows detect itself as a firmware application? That leads me to believe that it is indeed just copying firmware variables when bcdboot creates the BCD. Does your other windows install still exist? Does it say that the other one is there as a firmware application? Also, I'm literally just done. I cannot stand this community anymore. I'm done. Have a great time guys but I'm just done, I don't care at all anymore. Goodbye.
  4. apianti

    Clover General discussion

    No, I'm not doing anything non standard, I know how it works. The reason it is not overwriting \EFI\BOOT\BOOTX64.efi is because of the firmware application entries present in the BCD, bcdedit only reads from the BCD for entries. So those entries were either created by you, some other application, or you already had them set when you initially installed windows and bcdboot when initializing a new BCD adds them. I am on the lastest version of windows 10 through the developer preview channel. And this is the output of my bcdedit: Notice no firmware application entries at all? Even though I have windows, clover, and four linux distros all set to boot from my firmware menu, plus the additional ones that show up when a USB is inserted. You say the entries change, but how do you know that they are changing? Are you adding new entries and those entries are then appearing in that output? Why would it be showing boot entries with no application path? You have two USB disks connected when you booted? Neither of which is bootable yet it shows an entry for? EDIT: And I just told you that it is booting from \EFI\BOOT\BOOTX64.efi because I cleared my nvram, I'm not moving the bootmgfw.efi and trying to use it somewhere else. But that's entirely possible to do by changing the BCD, which is allowed by the bcdboot command. EDIT2: To clarify, it does startup repair if the {bootmgr} path is different from the path it is booted, not specifically \EFI\Microsoft\Boot\bootmgfw.efi, that's just the default location.
  5. apianti

    Clover General discussion

    This is a different issue altogether. I'm assuming you have it set to timeout and automatically boot macOS? Please look at your preboot.log when this happens and see if the selected entry to boot is found because I imagine that it is deciding that the windows entry is somehow what is supposed to be used, probably because it didn't find anything and your windows entry is the first? EDIT: Wait your edit makes me believe that the installer is actually returning a failure code and your firmware is moving on to the next boot entry, it just appears to be a restart.
  6. apianti

    Clover General discussion

    Yeah, where on earth would I gather information pertaining to bcdedit... Maybe the microsoft resources? https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/bcdedit-command-line-options I think you are confusing bcdedit with bcdboot, which is also not capable of adding any EFI boot entries except for windows boot manager, which is exactly what happens during an update. And I don't mean like a random security fix, I mean the actual build updates. https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/bcdboot-command-line-options-techref-di EDIT: Also, what you're describing is a non-compliant implementation of (U)EFI, which is not what I was saying, I was saying that if windows detects that it has been booted from any place other than \EFI\Microsoft\Boot\bootmgfw.efi, it performs startup repair. EDIT2: And you should be using \EFI\CLOVER\CLOVERX64.efi, the \EFI\BOOT\BOOTX64.efi is provided for the exact reason that windows overwrites it, so that it is the default on the disk when there is no entry for the actual clover location.
  7. apianti

    Clover General discussion

    That's weird because I have installed clover as \EFI\BOOT\BOOTX64.efi and then created a boot entry to \EFI\CLOVER\CLOVERX64.efi. Guess what? Windows updated and now my \EFI\BOOT\BOOTX64.efi is a copy of \EFI\Microsoft\Boot\bootmgfw.efi. It absolutely does this, clear your nvram after a windows update and windows will boot, say something happened to your startup, do a bunch of random nonsense, make you restart and will have set itself as the default pointing to \EFI\Microsoft\Boot\bootmgfw.efi. If masking was the issue then you would have to use the alternate method of launching clover in the first place, unless you already know before hand and install to the disk, boot from a USB, use the EFI shell to set the boot entry. I'm pretty sure you wouldn't be asking a question about why it was happening if you were aware of this. And are you really telling me how to use bcfg or bcdedit? Windows BCD only contains entries pertaining to windows boot manager and does nothing with EFI entries. It is not capable of editing EFI boot entries, however, it can chain load, though it doesn't always work. I just updated my windows like a week ago and my clover like a week before that, here is proof that it does overwrite \EFI\BOOT\BOOTX64.efi:
  8. apianti

    Clover General discussion

    Yes, windows will decide that it needs to set itself as the default for some unknown reason and it appears to be completely random. Also, windows update will cause \EFI\BOOT\BOOTX64.efi to be overwritten often.
  9. apianti

    Clover General discussion

    I have a wireless usb 3.0 keyboard and have no problem in the shell. Try using one of the other shell variations. It may be a limitation of your firmware or the keyboard as well since the simple text input protocol doesn't have shift/alt/control/etc key support so it relies on the driver. If the driver doesn't properly check whether the shift key is pressed to alter the character that is retrieved from the keyboard then it will just use the character represented by the key scan code. The keyboard may also be to blame by having a different scan code for keys, especially if it is not an ANSI english keyboard. EDIT: You can also try using either the ps2 keyboard driver from edk2, or the usb keyboard driver from clover or unmodified from edk2. Though if you are legacy booting you already have the clover modified one.
  10. apianti

    Intermittent panic on wakeup, desperate for help

    Looks like maybe you have a bad kernel patch? I am unsure that is weird nothing should be changing the kernel's allocation map entries....
  11. apianti

    Clover v3

    I am unsure, I was doing well for a while but then I had some seizures over a few days before my birthday and I feel like my brain got fried, maybe you have noticed I keep mixing words up and having to fix them in edits later. Thanks for asking though. I'm currently trying to finish this semester finals which includes a project, and I have another class and three research papers to complete for publication over the summer, not to mention the worst schedule for fall I could imagine (two of my days are 8am to 10pm), so I guess I don't know really at all. I think I have had a meaningful contribution to this community, I don't know how much more I can contribute at this point. I think my time may be better spent on more generalized research because I comfortably think those guys are all capable of continuing to advance the work being done in this community. This is only a small subset of very specialized research. I'm also further limited in what I can do because I'm in the US, so I can't help to reverse anything and write code for what was reversed, I have to do one or the other because of the law. Which should explain my behavior of trying to get other people to help me when I talk about making changes to some parts. Also, I deliberately made some decisions that I knew would force others to do stuff... And probably made them upset with me in different ways... I will probably still be around for advise and stuff but at this point I think it might be time to pass the torch... IDK..
  12. apianti

    OpenCore Discussion

    Yeah, not even close to a rebranding of clover. Clover is monolithic, and a bunch of old projects (~2011) stitched together and made to work in UEFI. There should be a huge difference in performance in everything. Also, did you notice the part where I said because it is modular the GUI would not be a requirement? Some people want their machine to behave exactly like a mac would which means the ability for a GUI boot selector. EDIT: Also maybe some people just have an easier time with GUIs, it would make sense because why bother having a GUI and not just go back to DOS or UNIX?
  13. apianti

    OpenCore Discussion

    Use the OpenCore ACPI patcher, all the patches are in those files I pointed you to, you really should figure it out on your own. Read the documentation and look at the sample configuration, there is no need to drop and reinsert tables that are already present, unless you have a really terrible firmware that directly maps the tables from the ROM. I very much doubt this is the case unless you have one of the early (Hybrid)(U)EFI firmwares and you would have definitely probably bricked it by now anyway, lol. Yes, I know the way I wrote that looks weird but there are multiple different kinds of firmware that suck from when the transition was happening.
  14. apianti

    OpenCore Discussion

    Look at the fixes built into clover for those patches and perform those same patches... Specifically they should be in https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/rEFIt_UEFI/Platform/AcpiPatcher.c and https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/rEFIt_UEFI/Platform/FixBiosDsdt.c.
  15. apianti

    OpenCore Discussion

    The beauty is that it's modular, so a GUI would not be a requirement, but could easily be an additional driver (or application), as would any feature set beyond the basic features. There is a way to modify clover's nvram emulation to work only as a driver without the GUI doing the loading of the variables. However, there is an issue in some firmwares where the emulation must be disabled for certain actions and why it does not behave like this already. EDIT: Wrote the same thing twice, lol. Also might be better idea to convert the newer version of MdeModulePkg/Universal/Variable/RuntimeDxe to perform this loading of a plist instead since it's now a much more robust driver than what is in clover. EDIT2: There is also possibility now to write a windows mechanism to save nvram information that was not available before, and linux could have always done this, unsure why no one has done that... I think that windows may require a signed driver to do this though.
×