Jump to content

fluid | fixed

fbifido

fbifido

Member Since 25 Sep 2008
Offline Last Active Yesterday, 04:23 PM
-----

My 2cent on PC to MAC?

24 April 2013 - 06:20 PM

Hi,

I have ask this question for many years, and the answer is always the same, "it can't be done!".
everyone is moving away from distro type mac installer, so let me ask the question another way.

where do i start?

tools:
-cpuz
-http://www.osx86.net/
-systeminfo
-autopatcher
-autoedid
-autoamdtool
-autoapb
-Clover bootloader
-and many many more.

Now you have a pc, and wants to put mac os x on it, and you want a trouble free convert, first everyone will say to get this and that hardware, which is the best way, but if you can't what then.

you will then need a windows tool call system info: [attachment=112879:SystemInfoWin.zip]

http://img248.images...steminfowin.png
(i don't know how to embed picture)

web link
http://www.insanelym...and-kexts-info/

This software will tell you the Vendor ID and Device ID of all the need part of your system.
this info is for the advance hackey, but its good to know anyway.

Quote

to el coniglio:

1) Can you get this software to show the motherboad id?
2) Can the Ven ID and Dev ID be use to show what kext is needed in windows.


With the info from above you can then use google to start looking up what kext to use for each dev ID.

It would have been great if the BIG kext to VID/DID database was open to the public to use, so that someone with some programming skill could use systeminfo and that database and www.osx86.net to locate and download all needed kext for your system.

Next come the DSDT, there is a patch pack for mother boards and laptop on the net, don't remember where? search for dsdtpatcher. but if the program systeminfo could display the motherboard ID, then we could build a database with that info, and put all the relative patch in it, so that it would be easy for the average joy/Jane to convert to mac.

dsdt patcher should also use the data from systeminfo to do auto-repair / auto-patching.

Now you have completed half of what is needed, the above data is were most people goes wrong.
now you can use cpu-z to see what processor you have in your system, so that you can select the right smbios or create your own, their are tools for this, one is Chameleon Wizard.

i am loss, where are we now:
- we have all the kexts we need.
- we have our dsdt
- we have our smbios, or know which one to select when need to.

with all the above you think you will have a great install, but what fail most install is the video card?
i don't have a easy fix for that problem, other than to buy a tested or recommended video card.

some suggestion:

with all the above info, can some, use this data to create a program that install the kexts, modify kexts if needed, install the dsdt, modify it for the data provided by system info as to make sure the hardware works, install smbios with modify info re your cpu info.

ACPI-patching, done-the-easy-way ?

07 June 2012 - 02:11 PM

https://github.com/R...ne-the-easy-way

Quote

   c/p

ACPI patching, done the easy way

Introduction

RevoBoot is different in many ways and we did not want to make an exception for ACPI table patching. The way we do this is not only new and completely different to what you have seen so far, but the way we do it will make it a lot more easier for people to get started.

Getting rid of DSDT.aml

The first thing we did was to look for ways to get rid of the need to extract the ACPI tables, to obtain the DSDT. Many of these extracted tables are floating around the Internet. Patch here. Patch there. All different. All bound to one specific motherboard and BIOS version. Causing trouble. No more.

SSDT hacking

Yes. We still need to patch the ACPI tables, but we do it differently. The easy way. The way it was supposed to be from day one. Enter tiny SSDT.

Tiny SSDT

Tiny SSDT is just a tiny file – hence the name. Smaller than anything (DSDT) you have seen. Making it a lot easier to understand. Eliminating the need to extract the DSDT and strip it to pieces. A painful time wasting process. Prone to errors. Done over and over again. For every new BIOS update. No more with RevoBoot.

Examples

We've made a couple of examples for you. A basic tiny SSDT with the things that need to be patched, and a couple more advanced ones with device removals and some devices that gets renamed. Resulting in something similar to what you get when you go mad and strip your DSDT. Have a look here:

https://github.com/R...SUS-P8P67-M-PRO
https://github.com/R...SUS-P8Z68-V-PRO
https://github.com/R...l-blown-example

Portability

The way we do it now adds portability i.e. you can use most of the example SSDT's with any motherboard and BIOS version. These are not just made for one specific board and/or BIOS version. Yes. Most of it will work with any bootloader, but you may have to make tiny changes. Making it much easier to control and understand so get going the new way!

- Note well that when you use board/BIOS specific device names that it will become less portable!

Static Tiny SSDT

You can convert your copy of tiny SSDT and include it in RevoBoot, when you are done and everything works for you, just like you would do for any other ACPI table.

What does this mean for DSDT's?

Nothing really. You can still use a static or dynamically loaded DSDT with RevoBoot. This is just another way of patching the ACPI tables, but one that we believe is easier for people to understand. Also. You can use our tiny SSDT as a starter and go mad when you want to remove/rename devices. The examples are both there for you to look at and learn from so go have fun with them.

Notes

This part of the source code of RevoBoot is currently only in a stage 1 phase and thus our implementation will most likely change and get more advanced in the near future. We just had to get something going so that you can get used to doing it the new way.

Drawbacks

The only thing that we are aware of, currently, is that using a tiny SSDT instead of a stripped down DSDT makes you use a bit more memory due to factory DSDT's being larger than stripped copies of it.

Last edited by RevoGirl, 11 months ago

Is it possible to only edit the SSDT and still have a stable system?

Thanks.

Clover v2 r480 EFI bootloader pkg + Win_USBTools

07 June 2012 - 02:01 PM

http://www.osx86.net...&id=2571&page=4

Quote

r480 UnOfficial announced revision from svn, may come with some bugs still need to be fixed. (you may still get some errors or bugs.)


Install to MBR+GPT on Mac: use Clover_v2_r480_pkg+boot1h2.zip
Install to GPT EFI on Mac: use EFI_Tools_Clover_v2_r480_EN.zip
Install to USB Fat32 on Win: use Win_USBTools-Fat32_Clover_v2_r480.zip

Rev 480. Support to install InstallESD.dmg to GPT.( 10.7.x + 10.8.x )


How to install InstallESD.dmg to GPT. since r480.

First, you need to Restore InstallESD.dmg to disk by using Disk Utility.
Then, follow the stage 1 and stage 2 to install 10.7.x or 10.8.x to GPT, and auto-create the Recovery HD used for iCloud.

Stage 1

1.Remove kernelcache in InstallESD.dmg/Library/Preferences/SystemConfiguration/com.apple.Boot.plist.
<key>Kernel Cache</key> remove this line.
<string>xxxxxxxxxxxxx</string> remove this line.
2.Copy BaseSystem.dmg/System/Library/Extensions to partition of InstallESD.dmg and add other kexts (FakeSMC.kext).
3.Clover select to "Boot Mac OS X with extra kexts (skips cache)", and follow the installation with restart first time.

Stage 2

1.Remove kernelcache in target partition's /OS X Install Data/com.apple.Boot.plist.
<key>Kernel Cache</key> remove this line.
<string>xxxxxxxxxxxxx</string> remove this line.
( 10.7.x is /Mac OS X Install Data/com.apple.Boot.plist )
2.Copy InstallESD.dmg/System/Library/CoreServices and /mach_kernel to target partition's / .
3.Copy BaseSystem.dmg/System/Library/Extensions to target partition's / and add other kexts (FakeSMC.kext).
4.Boot to "OS X Install" with "Boot Mac OS X with extra kexts (skips cache)" and finish the installation.
(10.7.x is "Mac OS X Install")

------------------------------------------------------------------------------------------------------------------------------

Install Clover by using boot1h2 or boot1f32alt, after test done with 2 seconds.
Default boot to boot Clover EFI 64bit,
Press key 1 to boot1 for Chameleon
Press key 3 to boot3 for Clover EFI 32bit,
Press key 6 to boot6 for Clover EFI 64bit,


Clover EFI bootloader come from Slice @ ProjectOSX.
package by crazybirdy.

PKG will install for MBR as below.
 /boot
 /EFI/ (folder)
 /etc/rc.local
 /etc/rc.shutdown.local
and you may need to modify the setup files, refer to /EFI/config-sample.plist.
 /EFI/config.plist
 /EFI/BOOT/refit.config

Put Extra kexts to /System/Library/Extensions and rebuild kernelcache.
Suggest to install Clover EFI to a SD card or flash drive with MBR HFS+, it works fine.
Only test on 64bits CPU, both 32bits and 64bits work fine with arch=i386 and arch=x86_64.

Can someone help me understand the text in red above, like a DIY step-by-step help.

Thanks

© 2013 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   Web hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy