Jump to content
xpamamadeus

Ozmosis

6,132 posts in this topic

Recommended Posts

How can you link the OEM Splashscreen to the GUI and use it as background? I've never seen that and the Gigabyte Splashscreen doesn't get displayed either. So I don't get what you're saying or I'm just missunderstanding you...

The GUID I was talking about is for the pointer image which can be found in the Theme file. That's also why you can't find the ID in the UEFI.

 

Forget what I said, because i was wondering to put my Profil Logo that i use as splashscreen in my ROM and put it it in the Theme/Icons/ folder, and pointing that Theme.plist to use it with black color background! Problem here is that it need to change the placement of the drives icons and all icons size, after that and finally will have a screengui with to much icons, this is why Hermit developer stuffs maybe decided to leave that damn background gui.

 

I just want to know how to compile it, because I have PNG missing when i'm trying to do it, I can try to change the icons size to have smaller icons and after that the Logo can be fitted discretly, and this is only what i need.

 

Excuse me if I wasn't clear!  

Edited by ammoune78

Share this post


Link to post
Share on other sites
Advertisement

@ammoune78 We are not talking about the BIOS splashscreen image, we are trying to figure out if there's a way to set an image as background for the OzmosisGUI. If you look at the image that david posted above, the idea is to replace the blue background behind the displayed boot options. That has nothing to do with the OEM Logo in the UEFI but with image data within the OzmosisHorizontalTheme ;)

 

Btw: Does this theme actually exist? http://www.insanelymac.com/forum/index.php?app=forums&module=forums&section=findpost&pid=2193678

Or is it just a mockup? I would love to know what options you can find behind the toolbar buttons :D

 

Good thing will be to contact BlackFrog maybe?

Share this post


Link to post
Share on other sites

HS DP6  install Success on QUO SysDef iMac 13,2 after changing Defaults.plist

		<key>BiosDate</key>
		<string>08/08/2017</string>
		<key>BiosVersion</key>
		<string>IM131.88Z.010F.B00.1708080805</string>

Share this post


Link to post
Share on other sites

You need to understand that theme is strict relation with Ozmosis Interface implementation, so all you can do is to use existing features that are implemented already, or wait for future implementations/releases.

Share this post


Link to post
Share on other sites

Wa

 

You need to understand that theme is strict relation with Ozmosis Interface implementation, so all you can do is to use existing features that are implemented already, or wait for future implementations/releases.

 

Thats good to know and appreciate the information you have provided. Was just hoping to discover an undocumented feature or two to spice up the interface. Though one cool thing I have discovered is that the Theme.Plist references FFS GUIDs under the 'Command' key for certain functions that do not exist for everyone. So was wondering if perhaps I could replace one of the GUIDS with the 'QFlash'  bios module or some other efi program?

 

As far as getting a custom background image patience will be a virtue here I guess..

 

Thank you.

Share this post


Link to post
Share on other sites

...So was wondering if perhaps I could replace one of the GUIDS with the 'QFlash'  bios module or some other efi program?

I think a better answer you will get after you try and share the result with everyone.

Share this post


Link to post
Share on other sites

How can you link the OEM Splashscreen to the GUI and use it as background? I've never seen that and the Gigabyte Splashscreen doesn't get displayed either. So I don't get what you're saying or I'm just missunderstanding you...

The GUID I was talking about is for the pointer image which can be found in the Theme file. That's also why you can't find the ID in the UEFI.

 

My answer for you is a question! Why from the OzmosisGUI and when you double click on BIOS Chip icon it takes you to UEFI Settings after a reboot, or double click on HermitShell for example it takes you to it? How can it be possible, now you'll not misunderstand me!  :wink_anim:  ^_^

Share this post


Link to post
Share on other sites

That is possible because of the OzmosisUI Implemetation in Ozmosis itself. Both services have fixed file GUIDs which are set in the theme.plist under "Command". Ozmosis reads this value and starts the EFI Application with the GUID set in the propertylist.

An OEM splashscreen isn't an EFI Application, though...

Share this post


Link to post
Share on other sites

That is possible because of the OzmosisUI Implemetation in Ozmosis itself. Both services have fixed file GUIDs which are set in the theme.plist under "Command". Ozmosis reads this value and starts the EFI Application with the GUID set in the propertylist.

An OEM splashscreen isn't an EFI Application, though...

Not only that but in Ozmosis.ffs I have found the Hermitshell Guid referenced in code so its hardwired to load the shell. Unfortunately in my system i either have to do a cmos reset or delete HermitShell from the boot menu using bcfg so it is reinstated or else the reference is lost after a reboot. I dont know if references in theme.plist will make a difference in my case but going to try probably by Sunday. Stay tuned.

Share this post


Link to post
Share on other sites

Some things are referenced in ozmosis.efi. This way the command "Firmware" also works although its obviously not a File GUID... I don't think that these values in the Plist are only there to look good, they should serve a purpose unless it's not implemented (yet).

Do you use a shell where the File GUID matches the one in the Theme.plist?

Share this post


Link to post
Share on other sites

Some things are referenced in ozmosis.efi. This way the command "Firmware" also works although its obviously not a File GUID... I don't think that these values in the Plist are only there to look good, they should serve a purpose unless it's not implemented (yet).

Do you use a shell where the File GUID matches the one in the Theme.plist?

No I was forced to use bcfg boot add as I couldn't get the built in shell working. It would work only once then after reboot not work anymore. Ill try to alter theme.plist guids and see what can happen.

Share this post


Link to post
Share on other sites

No I was forced to use bcfg boot add as I couldn't get the built in shell working. It would work only once then after reboot not work anymore. Ill try to alter theme.plist guids and see what can happen.

what does not work after restart? Theme?

Share this post


Link to post
Share on other sites

@Crusher,

 

No not the theme. What doesn't work is the 'Builtin Shell' or Hermitshell from either the F12 boot menu or from the Oz GUI. Only works once. After reboot not work again when trying to load it from Firmware Volume. So I have to create a bcfg boot add to hermitshell off of my efi folder.

Share this post


Link to post
Share on other sites

@Crusher,

 

No not the theme. What doesn't work is the 'Builtin Shell' or Hermitshell from either the F12 boot menu or from the Oz GUI. Only works once. After reboot not work again when trying to load it from Firmware Volume. So I have to create a bcfg boot add to hermitshell off of my efi folder.

Try to add and hermitshell via bcfg like a boot.

Share this post


Link to post
Share on other sites

You could also put the file into EFI/Boot folder. Afterwards name it BOOTX64.efi if you don't mind. This way it will automatically get added...

Which shell do you use, could you attach it?

Share this post


Link to post
Share on other sites

 

HS DP6  install Success on QUO SysDef iMac 13,2 after changing Defaults.plist

		<key>BiosDate</key>
		<string>08/08/2017</string>
		<key>BiosVersion</key>
		<string>IM131.88Z.010F.B00.1708080805</string>

 

High Sierra DP7 from DP6 .. nothing to do, just works.

Share this post


Link to post
Share on other sites

High Sierra DP7 from DP6 .. nothing to do, just works.

		<key>FirmwareFeatures</key>
		<integer>3909612855</integer>
		<key>FirmwareFeaturesMask</key>
		<integer>4280287039</integer>

:) HI  .I also use QUO SysDef iMac 13,2 

 

What's your FirmwareFeatures & FirmwareFeaturesMask?     I set  3909612855 & 4280287039 not work with High Sierra DP7 .....

Share this post


Link to post
Share on other sites
		<key>FirmwareFeatures</key>
		<integer>3909612855</integer>
		<key>FirmwareFeaturesMask</key>
		<integer>4280287039</integer>

:) HI  .I also use QUO SysDef iMac 13,2 

 

What's your FirmwareFeatures & FirmwareFeaturesMask?     I set  3909612855 & 4280287039 not work with High Sierra DP7 .....

 

 

For 13,2.

post-971914-0-23015700-1503496967_thumb.png

Share this post


Link to post
Share on other sites
		<key>FirmwareFeatures</key>
		<integer>3909612855</integer>
		<key>FirmwareFeaturesMask</key>
		<integer>4280287039</integer>

:) HI  .I also use QUO SysDef iMac 13,2 

 

What's your FirmwareFeatures & FirmwareFeaturesMask?     I set  3909612855 & 4280287039 not work with High Sierra DP7 .....

 

<key>FirmwareFeatures</key>
<integer>0xE907F537</integer>
<key>FirmwareFeaturesMask</key>
<integer>0xFFFFFFFF</integer>

Share this post


Link to post
Share on other sites

Ok, a fresh question from an old time user. I have a Fusion Disk with Sierra on it booting from Ozmosis (a very old version that allowed for Fusion drives I believe it was 894M) it has served me very well thus far, however with High Sierra I can only get a KP, and it is so fast that It doesn't give me an option to view the error before it scrolls past with a full screen of debug followed by mach restart 3 times.

 

This is on a separate single SATA drive I use for Beta testing on my hack vs beta testing on my MacBook Pro (where I installed the OS on the disk like I did Sierra). All protections are disabled in firmware so it should see the FakeSMC.ffs like Sierra does, and load it.  Any help would be greatly appreciated.

 

HBP

:: Edited ::

After Screencapturing the monitor with my iPhone, the KP is on com.apple.driver.AppleACPIPlatform(6.1)

 

it does pick up FakeSMC but for some reason, the ACPI for Sierra doesn't work for High Sierra?  any thoughts?

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.

  • Similar Content

    • By ciriousjoker
      TLDR:
      I'm trying to boot MacOS on a Chromebook without UEFI. I'm stuck at getting the bootloader (Chameleon/Clover) to work.  
      My setup / context:
      I have an Acer Chromebook Spin 13.
      Available ports:
      2 x USB-C 1 x USB-A 3.0 MicroSD Slot No USB A 2.0 (I've read that Clover has problems with USB 3.0) Firmware:
      There's no UEFI firmware available and by default, it doesn't even allow booting anything other than ChromeOS. Thanks to MrChromebox (big shoutouts!), I flashed a custom legacy bios that allows me to boot anything linux related. This bios is flashed into the RW_LEGACY section of the existing bootloader (coreboot afaik) and doesn't have any configuration options. If I have to change a setting, I could try compiling his bios payload myself with the specific setting enabled.  
      What I've tried so far:
      Chameleon attempts:
      Only selected setting was "Install chameleon on the chosen path", rest was unselected.
       
      1 - Install chameleon first without restoring the basesystem:
      Output:
      > boot0: GPT
      > boot0: done
      (hangs; pressing power button once shuts down
      Chameleon installation log is attached as "Chameleon_Installer_Log_BEFORE".
       
      2 - Install Chameleon after restoring the base system:
      Output:
      > boot0: GPT
      > boot0: GPT
      > boot0: doneboot1: /boot       <- Exactly like that, no line break in between
      (hangs; pressing power button once shuts down)
       
      I haven't been able to reproduce #2 after wiping the drive and doing the same thing again. Subsequent attempts have resulted in either #1 of either Chameleon or Clover.
      Chameleon installation log is attached as "Chameleon_Installer_Log_AFTER".
       
      Clover attempts:
      I tried multiple settings and configurations, but all of them boiled down to either one of these.
       
      1 - Doesn't do anything, just hangs at "Booting from usb..."
      2 - Boots into the blue/grey mode as shown in the attached images.
      According to MrChromebox, this could be an old Tianocore DUET It doesn't detect anything (cpu frequency, ram, partitions or disks)  
      I've read pretty much every article, github readme and other types of documentation for coreboot, tianocore, clover, chameleon and MrChromebox' rw_legacy payloads and right now, I'm totally clueless as to what to try next...
       
      A few questions that came up:
      Why does chameleon hang? What is it looking for, /boot was clearly written to the disk by the Chameleon installer? What exactly is the blue/grey image? According to MrChromebox, it could be Tianocore DUET Where does it come from? Clover? The mainboard itself? Why does the blue/grey thing not detect my processor frequency or any partitions/drives? Can I use some sort of DUET bootloader to chainload Clover?  
      If you guys could answer any of them or if you have any other guesses or information as to what's happening, I'd be really happy!
      Chameleon_Installer_Log_BEFORE.txt
      Chameleon_Installer_Log_AFTER.txt





    • By Slice
      Since rev 4844 Vector Themes are supported and there are ready-to-use Clovy by Clovy, cesium by Slice and BGM_SVG by Blackosx.
      You may see it's structure to create own theme
      -------------------------------------------------------------------------------------------------------------------------------------------------------
       
       
      Now I want to add vector graphics support in Clover. See rev 4560 and later.
      It is not working yet but designers may begin to create Vector Themes.
      It supposed to consist of SVG elements and has design size. It will be rendered to any screen size scaled from design size.
       
      What application in macOS can create SVG graphics?
      Inkscape is not working in macOS 10.11+. Pity.
      LibreOffice Draw works with SVG but buggy.
      Boxy SVG cost 10$ but looks good enough. It creates the best in simplicity files and have more then enough features.
      Illustrator is good but expensive.
       
      How to improve SVG file?
      Clover has restricted support for SVG. It is your job to make compatible file and as small as possible to speedup rendering.
      Some helps:
      Help:Inkscape – From invalid to valid SVG Inkscape files
      From invalid to valid SVG Adobe Illustrator files
      From invalid to valid SVG files of other editors: BKchem, ChemDraw and CorelDRAW
      Help:Illustrator – Assistance with creating and saving SVG images in Adobe Illustrator that will pass W3C validation
      User:Quibik/Cleaning up SVG files manually
      Later I will write own instructions specific to Clover abilities.
       
      How to create SVG fonts?
      You can google to find ready-to-use SVG fonts.  I found some problems with too beaty fonts: slow rendering and overflow crash. Be careful.
      You can get ttf or otf fonts and convert them into svg by using online WEB services. Not a problem to google.
      But then I want to find a way to simplify the font to reduce a size and speedup rendering.
      You can create own font by FontForge It is opensource and available for Windows, Mac and GNU+Linux. It creates otf font which you can convert to svg font.
       
      Pictures from Badruzeus
      https://www.insanelymac.com/forum/applications/core/interface/file/attachment.php?id=301597
    • By thomaspetersen
      Hi All
       
      I'm trying to start a Hackintosh High Sierra 10.13.5 installation:
      - MSI B350 PC Mate
      - Ryzen 5 - 2600
      - Radeon Pro 580 GPU
      - 4 x 8GB DDR4
      (Have a working clover bootloader for HS 10.13.3 - but for some reason, I can't use that setup with the 10.13.5) 
       
      Have tried different bootloader setup, with different outcomes...
      ATM. I get this error/hang - "Unknown CPU: family = 0x17, model = 0x8, Stepping = 0x2"
      Have search google, and can see that the threads ppl. are getting this, is when they look at "About this mac", I haven't yet installed the OSX.
       
      So can someone help...

      I'm running the newest Kexts: AppleALC, FakeSMC, Lilu, RealtekRTL8111, USBInjectAll and WhateverGreen.
      In Bootloader setup, i'm running: -v, -s, -f, -no_compat_check, busratio=34, PCIRootUID=1, npci=0x2000, dart=0 and nv_disable=1
      In SMBIOS i'm using the iMac18,2 and in RT i'm using BooterConfig: 0x28 and CsrActiveConfig: 0x67
      In installed drivers i'm using: AptioMemoryFix, EmuVariableUefi-64, OsxAptioFixDrv-64 (Have tried Fix2 as well)
       
      But i'm, keep getting the Unknown CPU hang/error, can someone help...
      Or do someone have a setup with the same CPU and GPU, that can show me his/her setup for Bootloader/Kexts...
    • By apianti
      Just so you all know I actually have done something. I have pushed the source to both my github and to sourceforge, please commit to the experimental branch and I will merge it into the stable branch once it is safe. Also, nothing meaningful happens yet so don't get too excited. Only the Visual studio build works right now. I haven't set up the Xcode or Makefile builds yet, I'm trying to do them now.
       
      https://github.com/apianti/Clover
      https://sourceforge.net/p/cloverefiboot/Clover
       
      IA32/X64/ARM/ARM64 testing ISO (6/7/2018): Clover-3.0-experimental.iso
×