51 replies to this topic

[kitmac]

BJMoose, on Sep 9 2009, 08:07 AM, said:

Have you tried putting your kexts into the EXTRAS/EXTENSIONS folder or are they just in the EXTRAS folder itself?  I've always put mine in E/E.

Yes, EXTRA/EXTENSIONS

[BlackCH]

kitmac, on Sep 9 2009, 11:51 AM, said:

ok thanx....
Y would my kexts in my EXTRAS folders not load though.....????
Is it neccessary to make the two folders  /10.5  /10.6 inside extra  ???

yes, they will be loaded from /Extra/Extensions.mkext or /Extra/Extensions/ . If you have problems loading your kexts, get Kext Utiltiy.app and run it. This will rebiuild the kext caches.
You dont need to make two folders. The /Extra/Extensions/ for 10.5 can be located in the 10.5 partition too.

[chrischmo]

Hi!

Thank you for this great piece of Software! I would never have thought that installing OS X on PC hardware would be that easy. Must have been a whole lot of work to get it this far.

Since it's my first posting, kudos to this forum, too! Very active, very helpful, already learned a lot.

Now to my questions:
I installed Snow Leopard via USB-Stick from the retail DVD following this guide  on lifehacker using RC2. I'm still using this stick to boot the system. Now I'd like to upgrade to RC3.

Would backing up and restoring RC2 be as trivial as packing and in case of disaster unpacking the "boot" file and the "Extra" Folder?

Can I then go ahead and install RC3 the usual way to get a working bootloader for the system already installed?

Sorry if I have overlooked any thread/guide already covering this, I searched but couldn't find anything. Also, should anybody know resources giving a good overview of Chameleon, please feel free to tell me!

Regards and thanks in advance,

Chris

[andrewq2]

I'm confused about the new E/E folder can i make a 10.5 and a 10.6 folder for separate kexts? when i tried that i could not load snow (lucky leopard doesn't require any so i could fix it).

[tbar]

Almost all of the questions being asked here are answered in the RC3 topic on the website chameleon.osx86.hu.
I'll give a brief rundown of my experience so far. I was already using Chameleon RC2 so all I had to do was replace the boot file with the one provided in the RC3 package. As was mentioned in an earlier post there is an installer available if you are starting from scratch or if you're a command line user that option is available by default. Many of the problems encountered for me were related to a now known bug for users booting from a USB stick. The Boot.plist file on the USB stick is not being read so you are forced to enter those commands from the Chameleon boot prompt. My current boot string is:

-v arch=i386 "Graphics Mode"="1400X1050X32"

This boots in verbose (-v) 32bit kernel (arch=i386) vesa graphics mode 1400X1050X32 which I use because my video card (ATI HD 3870) is not supported at this time and will otherwise default to 1024X768. If you're loading Boot.plist from the hard disks /Extra folder instead of a USB stick then these commands can be automated in the kernel flags string of that file (com.apple.Boot.plist).

Take a look at their site for more detailed answers.

[mitch_de]

Sure, site is an good way - but most of the questions there would be needless, if ther would be an really useful manual for such things like:
Ch on an HD with different OS X Systems (10.5 / 10.6), active boot = 10.5
USB Boot issues / solution: type in the kernel_flag bootscreem -v arch=i386

Also some questions their arent answered like new VBIOS Yes/No.

Would be fine if one of the CH team takes some time to make such an manual  with main error examples&fixxes of that (more than an readme) - over the time , i am 110% sure, that saves much time for the ch team dont must look+answer at least 60% questions on their forum/site.

[tbar]

mitch_de, on Sep 9 2009, 10:44 PM, said:

Would be fine if one of the CH team takes some time to make such an manual  with main error examples&fixxes of that (more than an readme) - over the time , i am 110% sure, that saves much time for the ch team dont must look+answer at least 60% questions on their forum/site.

I totally agree, releasing updates with new features that are poorly documented causes much confusion and too many unnecessary questions that should have at least a few examples to start with. The answer usually given is if you don't understand it don't use it. Nobody forcing us to update. I guess that's the price you pay living on the bleeding edge of the technology. Sometimes it's fun , sometimes disaster .

[mitch_de]

YEP.
I got now USB Booting (CH R3) to my HD partitions  working with your hint , typing the kernel flags in (because on USB boot.plist isnt used=bug)
Problem:
DVDs in my AHCI DVD (AHCI, ICH9 native, Pioneer 217F) arent shown, even if i press F5 (resan)m or F10.
Only all Win/Mac Volumes shown (also all AHCI ICH9 native).
Anyone else have this problem (DVD´s not shown as boot device) and at least an workaround ?

[boreas]

If I use RC3 installer, firmware abi displayed as a "EFI32"
if I type in Terminal

        "ioreg -l -p IODeviceTree | grep firmware-abi"
it returns me  
        "| |   "firmware-abi" = <"EFI32">"

In System Profiler I have          " 64-bit Kernel and Extensions:   Yes "

But, if I use PC EFI 10.1, firmware abi displayed as a "EFI64".

Do you have EFI64 with Chameleon RC3?

Thank's!

[iamhappy]

HALELUJA

everything failed multiple installation-attempts, but it seems the bootloader was the problem

installed it on my "not working snow leo test usb drive". now it works.

THANk you !

[zoltankr]

kitmac, on Sep 9 2009, 01:14 PM, said:

Yes, EXTRA/EXTENSIONS

I'm new to chameleon 2.
The "Extra/Extensions" folder is created by chameleon 2? Is possible to put the kexts to /extensions folder (without kexthelper?).

I would be grateful for any answer! Thank you!

[KariNeko]

zoliky, on Sep 13 2009, 09:01 PM, said:

I'm new to chameleon 2.
The "Extra/Extensions" folder is created by chameleon 2? Is possible to put the kexts to /extensions folder (without kexthelper?).

I would be grateful for any answer! Thank you!

Yes, and you will need to set manually the file permissions ( 755, root:wheel ). And then create the mkext manually.