Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
ErmaC

Chameleon v2.1 (Main Trunk)

603 posts in this topic

Recommended Posts

Topic to discuss improvements, proposals, and tests on Chameleon v2.x

 

 

 

 

 

 

 

old entries.

-----

CHAMELON 2 RC5 diff patch files

-----

^Andy^

(760) source: http://www.mediafire.com/?b8ion36rp3e0s4z

---

.pkg ^Andy^ Chameleon_2.0_RC5_rAndy_Lion.zip

(755) source: http://www.mediafire.com/?y3roclftu494xwb

---

.pkg result of diff V6 Chameleon_2.0_RC5_r755_Lion.pkg.zipwork in progress:

-----

May 4 2011 - Kabyl branch: Binaries Kabyl_LionV1.zip

May 7 2011 - Kabyl branch: binaries Kabyl_LionV3.zip

I apply at the Kabyl revision 748 the recent Lion "patch"

(thx to Kabyl for his help in code correction and adaptation)

You can find the diff file at voodooprojects > HERE


  • Include the Chameleon Lion Patch code by cparm (ported by oldnapalm)
  • Include the Haiku - OpenBSD - FreeBSD as we see in diff V6 of the main trunk
  • Into V3 I rework the code with Lion code from Trunk 760
    - As the other diff version the credits go the original author.

-----

 

with official trunk 760 the above "patch" are "obsolete"

 

Here the temporal BootHelp.txt info

 

here the diff file for patch the "virgin" Chameleon 2 RC5 trunk 75x

into

Chameleon 2 RC5 trunk 75x for Lion and lower...

    LION patch credits:
  • All the credits go to the Chameleon team
  • Andy Vandijck
  • cparm
  • netkas
  • DutchHockeyPro
  • And all involved in the development in any way.
     
    - Removed -x32 and arch=i386 option, use i386 instead -
     
    V.1 (for Trunk752)

  • Credits to oldnapalm to share the patched C2RC5 source ported from old Chameleon-2.0-RC3-r658(patched source)
    I hope no forgot any credits...
    Things added:
  • "cosmetics" compiling (like meklort branch) credits to meklort
  • Some ID correction in pci.h and other things credits to Andy and valv (AnVAL Branch)
  • More Nasm correction by KillerJK
    Also in nvidia.c will be applied some fix coming from different branch
  • (nvidia.c) NVPM (copied from Slice nvidia.c code) credits to Slice
  • (nvidia.c) "display-cfg" property injecting by Jingu
  • (nvidia.c) An additional device properties has to be injected to get HDMI back: @1,connector-type by Jingu or yehia2amer

     
    V.2 (for Trunk752)
    Things added:
  • Correct one warning thx mitch_de
    bootstruct.c: In function ‘initKernBootStruct’:
    bootstruct.c:54: warning: assignment from incompatible pointer type

     
    V.3 (for Trunk753)
    Things added:
  • Correct last warning
    ati.c: In function ‘setup_ati_devprop’:
    ati.c:662: warning: pointer targets in passing argument 3 of ‘devprop_add_value’ differ in signednes
    from (AnVAL branch)
  • Add Icon and detection for Haiku OS credits to scorpius link
  • Add Icon and detection for FreeBSD and OpenBSD from (AnVAL branch)
  • Add credits into CREDITS file

     
    V.4 (for Trunk753)
    Binaries: C2RC5r755_diffV4.zip
    Things added:
  • Add oldnapalm's suggest "fix" for FAT16, FAT32 and BEFS into gui.c
  • Add more credits into CREDITS file

     
    V.5 (for Trunk753)
    Binaries: C2RC5r755_diffV5.zip
    Things added:
  • Applyoldnapalm's suggest "fix" into gui.c

     
    V.6.1 (for Trunk753)C2RC5753xlionV6.1.diff.zip
    Binaries:
    Things:
  • boot at 32&64 bit and kext from E/E
  • v6.1 Add asm code by DutchHockeyPro and comment the equivalent in boot.c

     
    V.7 (for Trunk753)C2RC5753xlionV7.diff.zip
    Binaries: C2RC5r755_diffV7.zip
    Things:
  • Correct pci.c/.h

How use the .diff file...?

Fireup your terminal

- create a folder navigate into it.

- download the Chameleon2 RC5 source code:

svn co http://forge.voodooprojects.org/svn/chameleon/trunk

- download the diff patch file into the same first folder

patch -p0

- done... :)

 

You will see the patching code process like this...

[size=1]sh-3.2# patch -p0 < C2RC5753xlionV4.diff
patching file trunk/CHANGES
patching file trunk/CREDITS
patching file trunk/Chameleon.xcodeproj/project.pbxproj
patching file trunk/Makefile
patching file trunk/TODO
patching file trunk/artwork/themes/default/device_befs.png
patching file trunk/artwork/themes/default/device_befs_o.png
patching file trunk/artwork/themes/default/device_freebsd.png
patching file trunk/artwork/themes/default/device_freebsd_o.png
patching file trunk/artwork/themes/default/device_openbsd.png
patching file trunk/artwork/themes/default/device_openbsd_o.png
patching file trunk/doc/BootHelp.txt
patching file trunk/i386/MakeInc.dir
patching file trunk/i386/Makefile
patching file trunk/i386/boot0/Makefile
patching file trunk/i386/boot0/chain0.s
patching file trunk/i386/boot1/Makefile
patching file trunk/i386/boot2/Makefile
patching file trunk/i386/boot2/boot.c
patching file trunk/i386/boot2/boot.h
patching file trunk/i386/boot2/drivers.c
patching file trunk/i386/boot2/graphics.c
patching file trunk/i386/boot2/gui.c
patching file trunk/i386/boot2/mboot.c
patching file trunk/i386/boot2/options.c
patching file trunk/i386/boot2/resume.c
patching file trunk/i386/cdboot/Makefile
patching file trunk/i386/doc/README
patching file trunk/i386/libsa/Makefile
patching file trunk/i386/libsa/libsa.h
patching file trunk/i386/libsa/string.c
patching file trunk/i386/libsaio/Makefile
patching file trunk/i386/libsaio/acpi_patcher.c
patching file trunk/i386/libsaio/allocate.c
patching file trunk/i386/libsaio/aml_generator.c
patching file trunk/i386/libsaio/ati.c
patching file trunk/i386/libsaio/befs.c
patching file trunk/i386/libsaio/befs.h
patching file trunk/i386/libsaio/bios.h
patching file trunk/i386/libsaio/biosfn.c
patching file trunk/i386/libsaio/boot.h
patching file trunk/i386/libsaio/bootstruct.c
patching file trunk/i386/libsaio/bootstruct.h
patching file trunk/i386/libsaio/console.c
patching file trunk/i386/libsaio/device_inject.c
patching file trunk/i386/libsaio/disk.c
patching file trunk/i386/libsaio/fake_efi.c
patching file trunk/i386/libsaio/fdisk.h
patching file trunk/i386/libsaio/freebsd.c
patching file trunk/i386/libsaio/freebsd.h
patching file trunk/i386/libsaio/hpet.c
patching file trunk/i386/libsaio/load.c
patching file trunk/i386/libsaio/mem.c
patching file trunk/i386/libsaio/nvidia.c
patching file trunk/i386/libsaio/openbsd.c
patching file trunk/i386/libsaio/openbsd.h
patching file trunk/i386/libsaio/pci.c
patching file trunk/i386/libsaio/pci.h
patching file trunk/i386/libsaio/pci_root.c
patching file trunk/i386/libsaio/pci_setup.c
patching file trunk/i386/libsaio/platform.c
patching file trunk/i386/libsaio/saio_types.h
patching file trunk/i386/libsaio/smbios_patcher.c
patching file trunk/i386/libsaio/spd.c
patching file trunk/i386/libsaio/stringTable.c
patching file trunk/i386/libsaio/sys.c
patching file trunk/i386/libsaio/usb.c
patching file trunk/i386/util/Makefile
sh-3.2#  [/size]

Fabio

Share this post


Link to post
Share on other sites
...

 

Hey Fabio, great job with the patches. Would you like to add a installer for this version in your thread? It's more complete and I think it will be better for everybody.

 

Thank you

fun.gif

Share this post


Link to post
Share on other sites
Hey Fabio, great job with the patches. Would you like to add a installer for this version in your thread? It's more complete and I think it will be better for everybody.

 

Thank you

fun.gif

 

Maybe I add a link to this... or this pkg file and source...

(I prefer preserve the other treand with official trunk source... maybe some voodoo developer can official add it... o part of it)

 

with the "cosmetics" compiling we can see some warnings.. (no idea how solve it, I'm not a coder...)

1)

bootstruct.c: In function ‘initKernBootStruct’:

bootstruct.c:54: warning: assignment from incompatible pointer type

 

2)

ati.c: In function ‘setup_ati_devprop’:

ati.c:662: warning: pointer targets in passing argument 3 of ‘devprop_add_value’ differ in signedness

 

Fabio

Share this post


Link to post
Share on other sites

Maybe it's better to keep this in a separated thread, but it would be nice if you attach an installer to your post (then we make it the first in this topic) because not everyone has Xcode installed.

Share this post


Link to post
Share on other sites

"1)

bootstruct.c: In function ‘initKernBootStruct’:

bootstruct.c:54: warning: assignment from incompatible pointer type

"

 

Can it be some typo ?

bootArgs = (boot_args *)malloc(sizeof(boot_args));

bootArgsSnow = (boot_args *)malloc(sizeof(boot_args_snow));

bootstruct.c:54: warning: assignment from incompatible pointer type

 

bootArgs = (boot_args *)malloc(sizeof(boot_args));

bootArgsSnow = (boot_args_snow *)malloc(sizeof(boot_args_snow));

no warning

Share this post


Link to post
Share on other sites
"1)

bootstruct.c: In function ‘initKernBootStruct’:

bootstruct.c:54: warning: assignment from incompatible pointer type

"

 

Can it be some typo ?

bootArgs = (boot_args *)malloc(sizeof(boot_args));

bootArgsSnow = (boot_args *)malloc(sizeof(boot_args_snow));

bootstruct.c:54: warning: assignment from incompatible pointer type

 

bootArgs = (boot_args *)malloc(sizeof(boot_args));

bootArgsSnow = (boot_args_snow *)malloc(sizeof(boot_args_snow));

no warning

 

Yep!!

You right! one warnigs is gone :)

(I still don't know if is correct...)

 

soon I update the diff file

 

Fabio

 

EDIT: V2 of diff file added...

Share this post


Link to post
Share on other sites
I will do this things...

 

For now I add a "note" in the top of the first #post

Sorry, I mean to add an installer in your post "in this topic", not in the other one. I agree with you, it's better to have them separated for now, until Chameleon devs decide if the Lion patches will be added to the trunk. But it's up to you, do how you think it's better.

 

If you decide to add the installer in this topic, we move your post to the top, it's more informative for those who are arriving now. For now we leave Maldon's installer in the first post.

Share this post


Link to post
Share on other sites

SL boots fine, but lion boots always into 64-bit kernal mode even when kernel flags set to arch=i386. Hope correct this bug soon. Why not use -usecahe flag for lion boot, which should be ignored by SL, that will fasten the boot process in Lion. :D

Share this post


Link to post
Share on other sites
SL boots fine, but lion boots always into 64-bit kernal mode even when kernel flags set to arch=i386. Hope correct this bug soon. Why not use -usecahe flag for lion boot, which should be ignored by SL, that will fasten the boot process in Lion. :D

The -usecache flag with my patches also allows to use the kernelcache of Snow (it'll check the version to boot, if you have a kernelcache generated at the given path, it'll work...)

Share this post


Link to post
Share on other sites
The -usecache flag with my patches also allows to use the kernelcache of Snow (it'll check the version to boot, if you have a kernelcache generated at the given path, it'll work...)

I notice that even with -usecache, it will still load all the kexts in S/L/E as if it were ignoring a boot cache (mkext from S/L/E). At least that's what it appears to be doing.

Is there a way to get it to just load the kernelcache when using -usecache?

 

Also, is it possible for the bootloader to load a mkext from /Extra and kernelcache from /System?

Or, how about a kernelcache from /Extra, plus the one from /System?

 

Just throwing around ideas.

 

MAJ

Share this post


Link to post
Share on other sites
SL boots fine, but lion boots always into 64-bit kernal mode even when kernel flags set to arch=i386. Hope correct this bug soon. Why not use -usecahe flag for lion boot, which should be ignored by SL, that will fasten the boot process in Lion. :D

You could try an other boot , which was made with the correction in the boot_args pasrt (some posts above). Maybe that was the problem (bug) some of the args where (in SL or LION) not used.

Att: boot with diff V2

boot.zip

Share this post


Link to post
Share on other sites

Thanks MaLd0N and thanks to all involved in the project for the great work.

I tried bootlader on my Snow Leopard installation with hardware in signature and I can boot into system, but like happen with other Chameleon (mozodojo or iReset unofficial installer) my system is very very slow and I can't use it.

Maybe the problem depends to an incompatibility with my Sandy Bridge's CPU or I don't know.

With Anval and RevoBoot I can boot successfully without problem.

 

p.s. Sorry for my poor english, hope you understand :D

Share this post


Link to post
Share on other sites
You could try an other boot , which was made with the correction in the boot_args pasrt (some posts above). Maybe that was the problem (bug) some of the args where (in SL or LION) not used.

Att: boot with diff V2

 

Thanks mitch_de. I replaced the boot with the one you provided, but no luck. Still booting with 64-bit kernel.

Share this post


Link to post
Share on other sites

is there any installation file that i can run it on windows? i lost my usb flash boot so i cant open my lion. [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] doesn't work on my notebook because off MBR START and i cant change bios settings ( it is very basic bios)

 

Summary: is there any exe file for " Chameleon v2.0-RC5 r752 " or is there any way for run pkg files on windows?

 

thanks...

Share this post


Link to post
Share on other sites
i've already installed mac os lion on my pc. i've lost my flash boot. i just need bootloader. anyway i gonna install snow leopard for temprory solution.

If you try to read, what I advised for you, you'll find the answer to your question.

Share this post


Link to post
Share on other sites

I'm quite pissed about something. Here's why:

 

Not only did I found out why, but I also fixed the kernelcache and adler generation bugs. Which nobody did before me! And yes, you can find it in this forum (well documented).

 

Next to that I introduced /chosen/boot-uuid with RevoBoot so this one is mine too (also well documented).

 

I also was the first person to solve the __bzero compiler error for Xcode 4 (PM'ed melkort about it).

 

Now have a look at RevoBoot and the efi changes in Chameleon. Noticed something? Yes. There's even more yet I see no credit in my name?!? Why is that?

 

So how long do you guys want to wait for real Sandy Bridge support in your boot loader? Oh yeah. You can have a look at my work and see that what I did so far, isn't anywhere available. Not in any boot loader... and now I should accept people to use my hard labor and as thanks I get no credit for my hard work?

 

Just lame excuses and getting me a big finger won't help anyone. Now take a look at how long the Chameleon branches were in a stalled state.

 

So are you prepared to wait another year?

Share this post


Link to post
Share on other sites

I think the i386 problem was introduced my me porting Andy's patches to Chameleon.

 

In PC_EFI there's only setupEfiTables in fake_efi.c, and in Chameleon there are setupEfiTables32 and setupEfiTables64, maybe I missed something.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×