Jump to content

Chameleon 2.4svn Official PKG Installer

ErmaC

By ErmaC,
in Chameleon

 Share
4,261 posts in this topic

Recommended Posts

davidm71
davidm71
Posted
Posted

Hi,

 

I upgraded from 2.1 2064 to 2.2 2187 and got a KP immediately. Stalled out on an error message : 'Sata device checksum not found' or something like that. I reinstalled the older version and it works again and was able to install from 10.82 to 10.83 without problem. So if it aint broke I wont fix it but it has me wondering what could have gone wrong?

 

Thanks.

 

Notes: I had just cloned an existing partition to another drive from case sensitive to not-sensitive format. Maybe chameleon is tripping on that? Though it finds the SSDTs without problems.

 

My org.chameleon.Boot.plist:

 

 

<key>GenerateCStates</key>

<string>Yes</string>

<key>GeneratePStates</key>

<string>Yes</string>

<key>Kernel</key>

<string>mach_kernel</string>

<key>Timeout</key>

<string>3</string>

<key>device-properties</key>

<string> ......................</string>

 

 

My smbios.plist:

 

 

<key>SMbiosvendor</key>

<string>Apple Inc.</string>

<key>SMbiosversion</key>

<string>IM121.88Z.0047.B0A.1104221555</string>

<key>SMboardproduct</key>

<string>Mac-942B59F58194171B</string>

<key>SMfamily</key>

<string>iMac</string>

<key>SMmanufacter</key>

<string>Apple Inc.</string>

<key>SMmanufacturer</key>

<string>Apple Inc.</string>

<key>SMmemspeed</key>

<string>1600</string>

<key>SMmemtype</key>

<string>24</string>

<key>SMproductname</key>

<string>iMac12,2</string>

<key>SMserial</key>

<string>C02FL2D5DHJP</string>

Link to comment
Share on other sites
Rampage Dev
Rampage Dev
Posted
Posted

Not working for me with build: 2190

 

Complied the binaries from the projects page installed and still displaying as 2189. Tried the complied binaries here as well and same thing. This is on a fusion drive install.

 

The following is the terminal commands I am using after changing the directory to the compiled bootloader folder:

 

fdisk -f boot0 -u -y /dev/disk0

fdisk -f boot0 -u -y /dev/disk1

dd if=boot1h of=/dev/disk0s3

dd if=boot1h of=/dev/disk1s3

Ideas?

Link to comment
Share on other sites
Gringo Vermelho
Gringo Vermelho
Posted
Posted

You forgot an r in rdisk?

 

I just pulled 2191 from svn, compiled and installed it. I use boot0md even though I never boot Windows with Chameleon, it's not even installed on the Windows drive. That's just how I roll.

 

./fdisk440 -f boot0md -u -y /dev/rdisk1
dd if=boot1h of=/dev/rdisk1s1
cp boot /Volumes/EFI

 

boot GUI shows r2191.

Link to comment
Share on other sites
Rampage Dev
Rampage Dev
Posted
Posted

You forgot an r in rdisk?

 

I just pulled 2191 from svn, compiled and installed it. I use boot0md even though I never boot Windows with Chameleon, it's not even installed on the Windows drive. That's just how I roll.

 

./fdisk440 -f boot0md -u -y /dev/rdisk1
dd if=boot1h of=/dev/rdisk1s1
cp boot /Volumes/EFI

 

boot GUI shows r2191.

 

It helps if you copy Boot.... Dam fusion drive makes me for get things.

  • Like 1
Link to comment
Share on other sites
Deridjian
Deridjian
Posted
Posted

Is it rather safe to upgrade from 2.1 r2069 to this release?

And can I just use the .pkg installer or do I have to compile manually and install via Terminal to be on the safe side?

Never change a running system, I always get headaches doing so...

 

Thank you for any experiences!

Link to comment
Share on other sites
Rampage Dev
Rampage Dev
Posted
Posted

Is it rather safe to upgrade from 2.1 r2069 to this release?

And can I just use the .pkg installer or do I have to compile manually and install via Terminal to be on the safe side?

Never change a running system, I always get headaches doing so...

 

Thank you for any experiences!

 

manually is what I

recommend.

Link to comment
Share on other sites
DarwinX
DarwinX
Posted
Posted

Is it rather safe to upgrade from 2.1 r2069 to this release?

And can I just use the .pkg installer or do I have to compile manually and install via Terminal to be on the safe side?

Never change a running system, I always get headaches doing so...

 

Thank you for any experiences!

 

Chameleon Wizard - Utility for Chameleon by Janek202

 

Chameleon WizardV4.2.1.app.zip

Link to comment
Share on other sites
LAbyOne
LAbyOne
Posted
Posted

@ Ermac

 

just installed this new release and its hanging on just after resolving all devices when you should being able to choose your startup partition it hangs on slash

 

tested on 2 machines same results (different hardware) 1st on i7 and 2nd quad all running 10.8.4 latest

back to 2189 all nice

installer log :

Chameleon installer log - Tue Apr 30 17:27:04 CEST 2013

Installer version: 2.2svn 2191

======================================================

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *250.1 GB disk0

1: EFI 209.7 MB disk0s1

2: Apple_HFS Snow HD 249.7 GB disk0s2

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *1.0 TB disk1

1: Windows_NTFS DeeVeeX III 1.0 TB disk1s1

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *2.0 TB disk2

1: EFI 209.7 MB disk2s1

2: Apple_HFS DeeVeeX II 2.0 TB disk2s2

/dev/disk3

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk3

1: EFI 209.7 MB disk3s1

2: Apple_HFS MultiMedia 999.9 GB disk3s2

/dev/disk4

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk4

1: EFI 209.7 MB disk4s1

2: Apple_HFS Mountain HD 499.8 GB disk4s2

/dev/disk5

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *2.0 TB disk5

1: EFI 209.7 MB disk5s1

2: Apple_HFS DeeVeeX 2.0 TB disk5s2

/dev/disk6

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *16.2 GB disk6

1: DOS_FAT_32 SEIZE GO2 16.2 GB disk6s1

/dev/disk7

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *16.0 GB disk7

1: Windows_FAT_32 CORSAIR 16.0 GB disk7s1

======================================================

Backup Chameleon files

Backup stage2 file /Volumes/Mountain HD/boot to /Volumes/Mountain HD/Chameleon.Backups/2013-04-30-17h27/boot

Backing up /Volumes/Mountain HD/Extra folder to /Volumes/Mountain HD/Chameleon.Backups/2013-04-30-17h27/Extra

======================================================

Clearing options...

======================================================

Running Standard postinstall script

Target volume = /Volumes/Mountain HD on /dev/disk4s2

Target disk already has existing Chameleon stage 0 loader - boot0

======================================================

Stage 0 loader not written to /dev/disk4.

Written boot1h to /dev/rdisk4s2.

Written boot to /Volumes/Mountain HD on /dev/disk4s2.

======================================================

Preparing to check target disk for previous installations.

Going to check the EFI system partition also.

Mounting /dev/disk4s1 as /Volumes/EFI.

Checking disk4.

Nothing found that could cause any problems.

======================================================

Disk: /dev/rdisk4 geometry: 60801/255/63 [976773168 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

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

1: EE 1023 254 63 - 1023 254 63 [ 1 - 976773167] <Unknown ID>

2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

 

Setting /Volumes/Mountain HD partition active.

======================================================

Standard script complete

======================================================

Module KernelPatcher installed

Module FileNVRAM installed

======================================================

Running Post postinstall script

Target volume = /Volumes/Mountain HD

===============================================

Unmount all volumes named EFI

/private/tmp/PKInstallSandbox.5XWDcu/Scripts/org.chameleon.post.H38iqL/UnMountEFIvolumes.sh: line 25: /private/tmp/PKInstallSandbox.5XWDcu/Scripts/org.chameleon.post.H38iqL/InstallLog.sh: No such file or directory

/private/tmp/PKInstallSandbox.5XWDcu/Scripts/org.chameleon.post.H38iqL/UnMountEFIvolumes.sh: line 26: /private/tmp/PKInstallSandbox.5XWDcu/Scripts/org.chameleon.post.H38iqL/InstallLog.sh: No such file or directory

======================================================

Post postinstall script complete

Link to comment
Share on other sites
TheRacerMaster
TheRacerMaster
Posted
Posted

Is there any way to fix iMessage while using a patched kernel? My laptop requires a patched lapic kernel in order to boot using more than one CPU core. Should I just revert to the stock kernel and try setting up iMessage, then replace it with the patched kernel?

Link to comment
Share on other sites
Rampage Dev
Rampage Dev
Posted
Posted

Is there any way to fix iMessage while using a patched kernel? My laptop requires a patched lapic kernel in order to boot using more than one CPU core. Should I just revert to the stock kernel and try setting up iMessage, then replace it with the patched kernel?

 

No. I have been testing with another user with this and still no go.

Link to comment
Share on other sites
theconnactic
theconnactic
Posted
Posted

Is there any way to fix iMessage while using a patched kernel? My laptop requires a patched lapic kernel in order to boot using more than one CPU core. Should I just revert to the stock kernel and try setting up iMessage, then replace it with the patched kernel?

 

Did you try Chameleon built-in kernel patcher module? It will patch your kernel on-the-fly and, since it will patch the vanilla binary, it will support all OS features, like iMessage. I use this tool for my Atom netbook of my sig, and iMessage works pretty well.

 

All the best!

Link to comment
Share on other sites
  • 3 weeks later...
rvxtm
rvxtm
Posted
Posted

iMessage does now work anymore, installed the latest Enoch with the NV module, 10.8.3 , it worked until i did a reinstall yesterday, and since then i can't get it to work anymore. maybe the NV module is not compatible with 10.8.3...

Link to comment
Share on other sites
3square
3square
Posted
Posted

iMessage does now work anymore, installed the latest Enoch with the NV module, 10.8.3 , it worked until i did a reinstall yesterday, and since then i can't get it to work anymore. maybe the NV module is not compatible with 10.8.3...

 

same here. won't work anymore.

Link to comment
Share on other sites
Philip Petev
Philip Petev
Posted
Posted

That's not going to work in this case, because this plist is being recreated on every shutdown or reboot. Instead, do the following:

 

1. Restart your system and use the -s flag on the next boot

2. Use /sbin/mount -uw / to remount the root filesystem as rw

3. Go to /Extra and delete the plist:

cd /Extra

rm nvram(press here the Tab key to get the full name, then press Enter)

4. Type reboot.

Link to comment
Share on other sites
Rampage Dev
Rampage Dev
Posted
Posted

That's not going to work in this case, because this plist is being recreated on every shutdown or reboot. Instead, do the following:

 

1. Restart your system and use the -s flag on the next boot

2. Use /sbin/mount -uw / to remount the root filesystem as rw

3. Go to /Extra and delete the plist:

cd /Extra

rm nvram(press here the Tab key to get the full name, then press Enter)

4. Type reboot.

 

No, it will not regenerate if the module is removed...

Link to comment
Share on other sites
zarac
zarac
Posted
Posted

I am using XFX ATI 6570 (deviceID=6759, dual DVI + miniHDMI, HD-657X-ZNH3) graphics card and I have to hex-edit AMD6000Controller to activate the working framebuffer personality. Without the edit, I can either boot using only one display with activated framebuffer, or using two displays but with no framebuffer personality activated (IOreg shows RadeonFrambuffer and System Report lists the card as Radeon 6xxx Series). With modified Gibba framebuffer my both displays (connected via DVI) are properly detected (AMD Radeon 6570/7570 Series) and IOreg confirms Gibba framebuffer personality is used.

 

Recently I updated Chameleon from v2.1-r2069 to the latest revision (v2.2-r2232 at the time) and noticed that Gibba framebuffer personality (or any other for that matter) does not get activated anymore. After Selecting my boot drive in Chameleon menu, there is no "ATI card POSTed, reading from vbios" console text - it lists my card as "unsupported" and no mention of Gibba. With older Chameleon the console would report my card as "AMD Radeon 6570/7570 Series" along with framebuffer used (Gibba) and default number of displays for that personality (5) - provided I have GraphicsEnabler=Yes and AtiConfig=Gibba in org.chameleon.boot.plist.

 

So I started testing Chameleon revisions one by one in the reversed order (from the newest to the older ones) using Chameleon wizard app to find where things went wrong.

I found that the last working revision for my card is v2.2-r2210, meaning some change between that one and r2215 (which is the next revision in Chameleon wizard app) broke the compatibility.

 

Currently I'm using r2210 and have no issues whatsoever, but I would like to be able to use newer versions and not stay cut off from the new features and fixes.

 

 

Is there anything I can do?

 

EDIT: here is the detailed lspci output for the card:

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Unknown device [1002:6759] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Unknown device [1682:3195]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at <ignored> (64-bit, prefetchable)
Memory at f5000000 (64-bit, non-prefetchable)
I/O ports at a000
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Capabilities: [100] #1002

Link to comment
Share on other sites
ErmaC
ErmaC
Posted
  • Author
Posted

Is there anything I can do?

 

EDIT: here is the detailed lspci output for the card:

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Unknown device [1002:6759] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Unknown device [1682:3195]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at <ignored> (64-bit, prefetchable)
Memory at f5000000 (64-bit, non-prefetchable)
I/O ports at a000
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Capabilities: [100] #1002

 

Pls try this.. just replace the boot binary file.

 

and report back...

 

ErmaC

  • Like 1
Link to comment
Share on other sites
zarac
zarac
Posted
Posted

Pls try this.. just replace the boot binary file.

 

and report back...

 

ErmaC

 

Tried it and no luck. The graphics card is reported correctly in the console, but that is when the machine freezes. It doesn't even start the osx boot sequence.

Tried with different boot switches, same thing. When I tried -f it froze before loading kexs in console.

Link to comment
Share on other sites
ErmaC
ErmaC
Posted
  • Author
Posted

Tried it and no luck. The graphics card is reported correctly in the console, but that is when the machine freezes. It doesn't even start the osx boot sequence.

Tried with different boot switches, same thing. When I tried -f it froze before loading kexs in console.

hmmm..

same as before ...

this is a "rollback" of ati code and match with 2210.

 

 

 

ErmaC

  • Like 1
Link to comment
Share on other sites
zarac
zarac
Posted
Posted

hmmm..

same as before ...

this is a "rollback" of ati code and match with 2210.

 

 

 

ErmaC

 

This one works just dandy!

Gibba gets activated and my card is reported as "AMD Radeon HD 6570".

 

Is this good or bad?

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...