Jump to content
xpamamadeus

Ozmosis

6,132 posts in this topic

Recommended Posts

I almost have put together an executable  program that on the Windows command line would split all the the png files in Theme.bin but Cecekpawon did such a nice job I'm not sure I'm going to continue writing it although his requires php to be installed. Not sure if after the plist file the order of badges matters but I wish I could have experimented with that more if not for the fact I went away for the weekend. Will let you know if there are any issues when I work on it later. If you could point me to a working Black Oz Theme that would be great. I'll do more later..

 

Thanks

 

 

I don't know how to extract Ozmosis Theme files nor to pack it, as i wanted to change also the PNG's, for changing the look: Pure as Apple, Black, White or Gray with a New Oz LOGO! But if it can help you here's the OzmosisBlackTheme extracted from QUO_Oz-1479.ROM.

 

OzmosisBlackTheme.zip

Share this post


Link to post
Share on other sites
Advertisement

Are you currently working on Windows executable + batch script (and maybe QT for OSX)? That would be great david, please continue! Yes Windows doesnt come with PHP for sure, and my script just a demo trying to know how theme.bin was assembled, and parsed by Oz.

 

I have tried manually add new Badge Sierra (supposed with valid ID), and still get ignored by Oz.

Badge: (w_128 x h_128) "MountainLion" 3039(09)_3030(00) - (id_137 frame_0)
Badge: (w_128 x h_128) "Mavericks" 3131(11)_3030(00) - (id_139 frame_0)
Badge: (w_128 x h_128) "Yosimite" 3133(13)_3030(00) - (id_141 frame_0)
Badge: (w_128 x h_128) "ElCap" 3135(15)_3030(00) - (id_143 frame_0)
Badge: (w_128 x h_128) "Sierra" 3137(17)_3030(00) - (id_145 frame_0)  <======= 
Badge: (w_128 x h_128) "Windows7" 3330(30)_3030(00) - (id_158 frame_0)
Badge: (w_128 x h_128) "Windows8" 3331(31)_3030(00) - (id_159 frame_0)
Badge: (w_128 x h_128) "Windows10" 3332(32)_3030(00) - (id_160 frame_0)

If your upcoming tool is to create another theme with existing valid ID it may work (have not tried my self).

 

Valid struct may looks like this:

- theme.plist
- [null terminator]
- pngs (Font)
- pngs (Pointer)
- pngs (Bus)
- pngs (Button)
- pngs (Device)
- pngs (Badge)
- pngs (Selector)
- pngs (Special)

* Update the script to get ID, as prefix dumped filename to reassemble.

Share this post


Link to post
Share on other sites

How did you figure out that Oz definitely ignores it? Did you also run bdmesg? Normally it should say:

Installed Badge Image 128 x 128 Id 145 Frame 00 "Sierra" (23)
Have you tried to replace the PNG with a new Image or to add a new Badge for a new OS? As far as I know there is a more or less current version of the HorizontalTheme that includes a badge for Sierra but also old versions where the latest badge is only for El Capitan.

 

Could you also attach the PNG that you were trying to add, please? :)

Share this post


Link to post
Share on other sites

Can't do testing right now either but this one should still be working:

Your theme doesnt have badge at all?

 

 

FontType1: (w_739 x h_15) "OregonMedium" 3030(00)_3132(12) - (id_0 frame_12)
FontType1: (w_962 x h_22) "OregonMedium" 3030(00)_3138(18) - (id_0 frame_18)
FontType1: (w_1277 x h_29) "OregonMedium" 3030(00)_3234(24) - (id_0 frame_24)
FontType1: (w_1803 x h_41) "OregonMedium" 3030(00)_3336(36) - (id_0 frame_36)
Pointer: (w_15 x h_22) "Default" 3030(00)_3030(00) - (id_1 frame_0)
Button: (w_48 x h_48) "Options" 3031(01)_3030(00) - (id_9 frame_0)
Button: (w_48 x h_48) "Info" 3032(02)_3030(00) - (id_10 frame_0)
Button: (w_48 x h_48) "Shell" 3033(03)_3030(00) - (id_11 frame_0)
Button: (w_48 x h_48) "Firmware" 3034(04)_3030(00) - (id_12 frame_0)
Device: (w_128 x h_128) "InternalDisk" 3031(01)_3030(00) - (id_513 frame_0)
Device: (w_128 x h_128) "ExternalDisk" 3032(02)_3030(00) - (id_514 frame_0)
Device: (w_128 x h_128) "OpticalDisk" 3033(03)_3030(00) - (id_515 frame_0)
Device: (w_128 x h_128) "UniversalSerialBus" 3034(04)_3030(00) - (id_516 frame_0)
Device: (w_128 x h_128) "Firewire" 3035(05)_3030(00) - (id_517 frame_0)
Device: (w_128 x h_128) "ThunderBolt" 3036(06)_3030(00) - (id_518 frame_0)
Device: (w_128 x h_128) "Ethernet" 3037(07)_3030(00) - (id_519 frame_0)
Device: (w_128 x h_128) "Firmware" 3038(08)_3030(00) - (id_520 frame_0)
Device: (w_128 x h_128) "RecoveryVolume" 3039(09)_3030(00) - (id_521 frame_0)
Device: (w_128 x h_128) "CoreStorage" 3130(10)_3030(00) - (id_522 frame_0)

 

 

 

How did you figure out that Oz definitely ignores it? Did you also run bdmesg? Normally it should say:

Installed Badge Image 128 x 128 Id 145 Frame 00 "Sierra" (23)
Have you tried to replace the PNG with a new Image or to add a new Badge for a new OS? As far as I know there is a more or less current version of the HorizontalTheme that includes a badge for Sierra but also old versions where the latest badge is only for El Capitan.

 

Could you also attach the PNG that you were trying to add, please? :)

 

 

Because I never get badge for Sierra rendered in GUI? While Oz can read it as 10.12 >>>

I saw similar log (*before get deleted) which contain Sierra badge already (with exact "145" ID).

I just had an older version of theme.bin with no Sierra badge. Attached theme.bin, dummy badge & log :)

Share this post


Link to post
Share on other sites

No i've extracted it "as is" using UEFITool and no raw body or something else, now here's uncompressed one using MMTool

 

OzmosisBlackTheme.zip

Edited by fantomas1
All posts must be clearly written and easy to read.

Share this post


Link to post
Share on other sites

Well my tool will be a Windows executable though it could also run on a mac since I'm using QT. Its almost done just needs the code cleaned up and error checking. All it does it does is spit out the PNG and Plist files. Nothing more. Pretty simple at the moment but I suppose it could do more if I had more time. I also may enable it to be able to open up the firmware image itself without having to extract the them.bin file but I would have to borrow OZMTool for that and expand it if the author not mind. 

 

As far as testing out those themes you guys have posted haven't had the chance. At work now and would be prefer to be playing with code..

 

Thanks.

Share this post


Link to post
Share on other sites

Playing around with the Theme package the King posted and feel like a kid in a candy store.. but was wondering

what pre-requesites are required to compile the files as on my system it completely failed to pack them all...

 

Thanks

Share this post


Link to post
Share on other sites

Playing around with the Theme package the King posted and feel like a kid in a candy store..

Haha same for me :D Thanks a lot!

 

There are some folders that are required for the script to work. If you take a look into compile.sh these are:

 

Type | Folder | Name of file

FONTS=$THEME/Fonts/*

LOGOS=$THEME/Logos/*.png

POINTERS=$THEME/Pointers/*.png

BUTTONS=$THEME/Icons/Button_*.png

DEVICES=$THEME/Icons/Device_*.png

BADGES=$THEME/Icons/Badge_*.png

SELECTORS=$THEME/Icons/Selector_*.png

SPECIAL=$THEME/Icons/Special_*.png

BUS=$THEME/Icons/Bus_*.png

BACKGROUNDS=$THEME/Background/*.png

+ Theme.plist in $THEME Folder.

 

And there we also have a directory for a background image, everything you asked for ;)

 

Also make sure you name the files right:

# extract type, name, id and frame from filename ie Device_01_00_InternalDisk.png
  # type  = Device
  # id    = 01
  # frame = 00
  # name  = InternalDisk
I hope that I didn't missunderstand you :/ :)

Share this post


Link to post
Share on other sites

Hi,

 

I finally was able to load the OzmosisBlackTheme from the EFI parition and I have some interesting findings. The Oz Black Theme seems not to have keyboard support in my case and all my partitions are spaced too far apart to show all at once. The other finding has to do with where Oz was loading the Theme.bin file from. I assumed it was my Sierra partition running off of the first Sata0 cable but it turns out that I also had an Oz EFI partition on my NVME PCI-E drive that hosts Windows 10. This EFI parition is also completely hidden from OSX as its on a NVME drive and I didn't install any NVME drivers on purpose. Needed Hermit Shell for that and  looking into BdMesg Oz log reported finding the GUID of the Windows NVME first so I assumed thats where to copy the Theme.bin and what do you know it worked! It didn't need a four finger reset either!

 

This opens up an interesting possibility... Loading Sierra from the NVME drive. The only problem in the past I had was that  Oz wouldn't create a boot menu with out a Sata drive but maybe thats changed. Anyhow now thats out of the way time to make some custom themed mods!

 

Thanks

Share this post


Link to post
Share on other sites

Haha same for me :D Thanks a lot!

 

There are some folders that are required for the script to work. If you take a look into compile.sh these are:

 

Type | Folder | Name of file

FONTS=$THEME/Fonts/*

LOGOS=$THEME/Logos/*.png

POINTERS=$THEME/Pointers/*.png

BUTTONS=$THEME/Icons/Button_*.png

DEVICES=$THEME/Icons/Device_*.png

BADGES=$THEME/Icons/Badge_*.png

SELECTORS=$THEME/Icons/Selector_*.png

SPECIAL=$THEME/Icons/Special_*.png

BUS=$THEME/Icons/Bus_*.png

BACKGROUNDS=$THEME/Background/*.png

+ Theme.plist in $THEME Folder.

 

And there we also have a directory for a background image, everything you asked for ;)

 

Also make sure you name the files right:

# extract type, name, id and frame from filename ie Device_01_00_InternalDisk.png
  # type  = Device
  # id    = 01
  # frame = 00
  # name  = InternalDisk
I hope that I didn't missunderstand you :/ :)

 

 

 

Just confused about how to name the Background.png file so it can get included in the theme.bin file. I now have The King's script working perfectly and it adds every included png file however skips the Background.png file. Suspect either I've named it wrong or have incorrect header info.

 

Thanks

Share this post


Link to post
Share on other sites

"*" stands for a random name so the background picture could have any name, as long as it has the right suffix and is placed in the folder called "Background".

 

What have you changed to the script to make it work perfectly?

Share this post


Link to post
Share on other sites

"*" stands for a random name so the background picture could have any name, as long as it has the right suffix and is placed in the folder called "Background".

What have you changed to the script to make it work perfectly?

I just found all the required dependencies and put them in a folder called Tools. Then i created a Windows environment variable called %TOOLS% and pointed it to my c:\tools folder and edited the script to look in %Tools% for the files. I named the background png file 'Background_00_00_Default.png' and placed it in the background folder. Also goto rename logo folder to logos as script looks in logos not logo. Then I ran the script and it worked by doing 'compile.bat nameoffolder'. The script even adds the appropriate tEXT header info. Only thing is the background doesnt work or Oz doesnt know what to do with it because bdmesg certainly says it got loaded. Maybe i got the name wrong or the numbers wrong or the plist needs to mention it I dont know. Only The King could possibly know. Cecekpown said its probably not implemented or was going to be in a later release.

 

Besides that I've gotten close to understanding why after my first cmos clearing why Hermitshell doesnt load. Apparently thats the only time i can get into my firmware volume memory mapped shell... After a reboot it no longer works and I'm forced to use bcfg boot add to create a link onto the hard drive. However doing a Bcfg rm for removing the hermitshell FV built-in volume restores functionality until the next reboot. My feeling is that the pointer to the volume gets lost somehow due to bios bug or something. Anyhow I wish I knew how to create my own FFS auto loading shell driver. Even better if you could convert the Clover efi boot file into an autoloading firmware volume driver the skys the limit..

 

Wish i knew how..

 

Thanks.

 

PS: Will post those tools files later if anyone wants them.

Tools.zip

Share this post


Link to post
Share on other sites

I don't if it's the right thing, but as I look into the QUO ROM, the module that contain MoBo Manufacturer Logo was deleted from it but steel present in the non Ozmosis ROM. If I'm not wrong, and if we delete it from the ROM as i did 6 months ago, at the boot screen no Logo appear only Black Screen! But my question is, did the QUO Board show the right Logo and background at the boot screen, because the old background with: QUO your configuration. .... your choice. is no more present in XMASS one?

 

@davidm71: Have a look at the Oz-QUO-AOS.ROM and MX-QUO-AOS.ROM, it can help you maybe to know something!

Edited by ammoune78

Share this post


Link to post
Share on other sites

I don't if it's the right thing, but as I look into the QUO ROM, the module that contain MoBo Manufacturer Logo was deleted from it but steel present in the non Ozmosis ROM. If I'm not wrong, and if we delete it from the ROM as i did 6 months ago, at the boot screen no Logo appear only Black Screen! But my question is, did the QUO Board show the right Logo and background at the boot screen, because the old background with: QUO your configuration. .... your choice. is no more present in XMASS one?

 

 

Since I don't have a Quo system I'm not sure. All I can tell you is that the Theme package The King posted last week has one called 'OzThemeH256' that has the selection icons twice as large as before, and two extra icons on the top toolbar including an 'About' and 'Config' icon besides the 'CMos' and 'EDKII' icons of which they are non functional. I'll post a picture for you guys later if I can. Unfortunately have no idea how to get the background working. Only can set three colors on the background of the top, mid, and bottom thirds of the screen. If there is a way to enable a background image I bet it needs to be set in the plist file...

 

FullSizeRender.jpg?raw=1

Share this post


Link to post
Share on other sites

I think the OzThemeH256 was never been released for public, it's THe KiNG Theme project, we need someone who have QUO board, maybe I'll ask IronManJFF? And if you look at the plist file you only'll see Background:#xxxxx, but no Background PNG instead. That explain, what i was meaning, Background is only color with Ozmosis icon, and this is why cecekpawon maybe asking a year ago for someone to make logo!

 

There's no Background PNG like Clover or Chameleon because as I said it was deleted from the Oz QUO AOS.ROM, this and it's what I think, but I'm still 75% sure.

Share this post


Link to post
Share on other sites

I think the OzThemeH256 was never been released for public,

That is correct but is not my project. H256 was designed for high DPI displays and was supposed to be implemented the same way Apple have, i.e. if high DPI resolution found load high resolution images if not smaller one, this is very helpful to have a nice looking theme on high DPI displays and also  on tablets/touch screen displays(yes  Ozmosis have touch screen support) where on small display size with high DPI small icons are almost impossible to touch...

Interface is the work of main developer not mine, I had an attempt with it but had luck and I was saved by BlackFrog who designed and implemented the current theme.

As far I know background image is not implemented yet, only color.

 

P.S. While om UI(UserInterface) pressing F10 will take screenshot on the root of EFI partition...

Share this post


Link to post
Share on other sites

@davidm71 You should be able to change the height and width of the background sections and also add sections. Have you tried that?

 

I don't know if this helps but the Theme.plist of the theme called "Standard" refers to the pointer picture using a GUID. It looks like this:

<key>Pointer</key>
	<dict>
		<key>ImageFile</key>
		<string>2CF68EED-7DDB-4784-9EDB-C1CF119483AE</string>
	</dict>
Maybe you could try to implement these lines into the Background section of the plist to point to a custom background picture. No idea if that will work though.

Share this post


Link to post
Share on other sites

@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

Share this post


Link to post
Share on other sites

I tried adding:

<key>Id</key>
<string>0</string>
<key>Image</key>
<string>0</string>

to:

<key>Screen</key>
	<dict>
		<key>Background</key>
		<string>#66ff33</string>
		<key>BottomMargin</key>
		<string>0%</string>
		<key>Height</key>
		<string>100%</string>
		<key>LeftMargin</key>
		<string>0%</string>
		<key>RightMargin</key>
		<string>0%</string>
		<key>TopMargin</key>
		<string>0%</string>
		<key>Width</key>
		<string>100%</string>
		<key>X</key>
		<string>0</string>
		<key>Y</key>
		<string>0</string>
	</dict>

Because I noticed the other icons were referenced by id and image number but that didn't work. I can only assume either its not implemented or the developer just didn't get around to adding it in there. Would bet anything that the original source code probably had it but commented it out. I mean why go through the trouble of writing a script that looks in a 'Background' sub-folder and compiles the file taking into account how many characters were in the word 'background' to parse out the id numbers out of the file name and not bother to include that feature?!

 

My only solution at this point is to use another boot loader like 'Refind' which allows custom background images and turn off the Ozmosis GUI. Only thing is I'm not sure if the Mac emulation would carry forward into another bootloader like Refind. In anycase I'll keep on experimenting on my free time. Only wish we knew who developed it so we could ask him ourselves. Maybe 'Blackfrog' could help?

 

Thanks

Share this post


Link to post
Share on other sites

^_^

 

THe KiNG you're exactly right: God gives, but do not put in bags.

Edited by ammoune78

Share this post


Link to post
Share on other sites

You can add icons on that OzmosisGUI, or link the OEM SplashScreen which we can replace with Background image that we are looking to add to the gui by entering it's Guid or put it on ESP or directly in the Theme.bin.

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.

 

 

I tried adding:

<key>Id</key>
<string>0</string>
<key>Image</key>
<string>0</string>
to:
<key>Screen</key>
	<dict>
		<key>Background</key>
		<string>#66ff33</string>
		<key>BottomMargin</key>
		<string>0%</string>
		<key>Height</key>
		<string>100%</string>
		<key>LeftMargin</key>
		<string>0%</string>
		<key>RightMargin</key>
		<string>0%</string>
		<key>TopMargin</key>
		<string>0%</string>
		<key>Width</key>
		<string>100%</string>
		<key>X</key>
		<string>0</string>
		<key>Y</key>
		<string>0</string>
	</dict>
If you look close, you'll see that

<key>Id</key>
<string></string>
<key>Image</key>
<string></string>
is always within a
<dict> </dict>
Also the only places where you can find "Id" and "Image" as the link to a certain picture is within the "Windows" section of the plist.

 

So I would suggest to try to add a background picture by implementing that into the Windows section. To try it out I would delete everything within the "Windows"-Plist-part but keep the "Selector"-section for example. Then change Top- and BottomMargin of that Section (i.e of Selector) so that it fills out the whole display.

Afterwards add

<dict>
	<key>Enable</key>
	<true/>
	<key>Id</key>
	<string></string>
	<key>Image</key>
	<string></string>
</dict>
to

<key>Selector</key>
<dict>
	<key>Background</key>
			<string>#2c364f</string>
instead of the "<string>#2c364f</string>" part. Maybe that'll work or is worth a try.

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
×