Jump to content

Chameleon 2.4svn Official PKG Installer


ErmaC
4,261 posts in this topic

Recommended Posts

I did, yes :wacko:

also pciroot and all other tries didn.t work.

I guess its something that hapened between rev 760 and 828. maybe the kabyl ati init or something else...

 

You could also try completely eliminating your /Extra/Extensions directory by moving all of your system extensions to the /System/Library/Extensions directory and adding the UseKernelCache=Yes to your org.chameleon.Boot.plist. While this may not seem related to your issue, this simple modification has helped many in booting their previously "unbootable" Lions as the OS X 10.7 handles its boot up kext caches quite differently than its predecessors.

Link to comment
Share on other sites

You could also try completely eliminating your /Extra/Extensions directory by moving all of your system extensions to the /System/Library/Extensions directory and adding the UseKernelCache=Yes to your org.chameleon.Boot.plist. While this may not seem related to your issue, this simple modification has helped many in booting their previously "unbootable" Lions as the OS X 10.7 handles its boot up kext caches quite differently than its predecessors.

Lion and snowleopard boot very well with only fakesmc if i use chameleon rc5 r760.

The problem lies before even booting lion. chameleon just don't show its start menu at all. as if my graphic card isn't plugged in. (and don't tell osx that it exists too) :wacko:

I can provide all infos requested like the dumped connectors configuration or else to anyone close to chameleon development to reinstate my card native support like it was before. I just don't know who to approach.

 

<Update! Culprit found: its the Resolution module finally!! >

Deleting it allows chameleon to boot effortlessly Lion and have my graphic card works natively

It seems the graphic module refuse my 15" samsung CRT monitor

<Thanks for your help DarwinX :) >

Link to comment
Share on other sites

Package Installer has now been updated for further testing. Now at rev1640 and replaces the previous v1630.

 

The changes include:

- Improved to the way it looks for previous installations and it now looks on the EFI system partition for the stage 2 loader (if relevant for the particular disk you're installing to).

- Added extra wording to the install log to help give a concise report.

- exclusive boot options are now enabled for resolutions and keylayouts. The options will look enabled when the menu is collapsed, but the enabled options are selecting 'None'. This means that running the installer and selecting the default settings will install Chameleon only - nothing else will be installed.

- The installer has had a facelift.

- The English (only) text has undergone some changes.

 

For most users, it's NOT recommended installing Chameleon to more than one partition of the same disk.

However, new users might just do that and then get confused when changes to some files aren't reflected on next boot, or worse still, the system fails to boot. It's for this reason that I would like confident / experienced testers to try out using this installer to install Chameleon to more than one partition on the same disk to see if the scripts help prevent encountering any issues.

Before attempting this though, make sure you have a backup method of booting your system. Either a secondary HDD or bootable USB flash drive that you've verified as working.

 

As before,

To anyone who would like to test this, please do so on a test rig and understand that this is a beta.

If for any unlikely reason that data loss should occur, I will not be held responsible. You test this at your own risk.

 

Source is available from: http://forge.voodooprojects.org/p/chameleo...anches/blackosx

 

I look forward to hearing any feedback.

Thanks

 

 

(removed: 25th October)

 

UPDATE:

20th October 16:40 - Updated now to rev1655

Includes the latest Chameleon binaries which have JrCs posted fix for iCloud/Facetime when using RAID.

Package installer changes since rev1640 are just changes to the credits file and some internal structure changes.

 

 

(removed: 25th October)

 

EDIT:

Lastest test package at post #1043

Link to comment
Share on other sites

Hi,

 

thx for that great job done.

 

I face a small problem with it. Maybe it's a bug or a just a config

issue.

 

My osx86 box is running Chameleon_2.1svn_r1640 from usb boot stick

loading Lion from internal GPT HD.

 

Chameleon starts and shows me correctly 2 OS X installation :

"hd(1,3) Lion" and "hd(1,6) Lion Test". Booting fails sometimes

with "Can't find /mach_kernel". This indicates missing root device.

Booting with "rd=disk0s3" succeeded after second try!!

 

It seems to me that order of disks are messed up.

 

I tried to specify rd by uuid in /Extra/org.chameleon.Boot.plist as

args of Kernel Flags. Neither "rd=<UUID>" nor "rd=uuid --uuid=<UUID>"

works.

 

I spent couple of time searching but without success.

 

So please help.

 

Thx.

Michael

 

My Box :

Lenovo ThinkPad x121e

i3-2357M / 4 GB RAM

internal : 320 GB / GPT / 64 Bit EFI Loading Ubuntu 11.10 via Grub

external : 1 GB USB / MBR / Loading Lion

Link to comment
Share on other sites

Hi,

 

thx for that great job done.

 

I face a small problem with it. Maybe it's a bug or a just a config

issue.

 

My osx86 box is running Chameleon_2.1svn_r1640 from usb boot stick

loading Lion from internal GPT HD.

 

Chameleon starts and shows me correctly 2 OS X installation :

"hd(1,3) Lion" and "hd(1,6) Lion Test". Booting fails sometimes

with "Can't find /mach_kernel". This indicates missing root device.

Booting with "rd=disk0s3" succeeded after second try!!

 

It seems to me that order of disks are messed up.

 

I tried to specify rd by uuid in /Extra/org.chameleon.Boot.plist as

args of Kernel Flags. Neither "rd=<UUID>" nor "rd=uuid --uuid=<UUID>"

works.

 

I spent couple of time searching but without success.

 

So please help.

 

Thx.

Michael

 

My Box :

Lenovo ThinkPad x121e

i3-2357M / 4 GB RAM

internal : 320 GB / GPT / 64 Bit EFI Loading Ubuntu 11.10 via Grub

external : 1 GB USB / MBR / Loading Lion

same for me before.

when chameleon starts it uses (in my case) hd(1,1) but inside osx the partion becames hd(2,1). I did many trial and errors (have 3hdd) till I had the correct boot, hide and rename partition hd(x,x) (I rename the win7 100MB to win7 instead of system reserved since win boot lays there.

as for my bios config I setup winhdd, then chameleon hdd. (Windows bootloader first to keep hybernate).

but you have a laptop with one hdd so I don't know if it remains hd(0,x) or becames hd(1,x) inside osx.

use -v in cham-boot to check what number it uses there and fdisk in osx to see if its the same.

 

1640 installer is still alpha and buggy[should read blackosx release post ;p ] (empty chameleon.boot.plist no copy back extensions and if you install it twice (in my case) it just stops creating the extra folder even though the log says it did (elevation prob?).

try installing first chameleon rc5 r760, copy the extra folder (just in case) and then without reboot reinstall chameleon 2.1 r1640. Its what I did to get back the new cham files (modules...)

 

hope it helps :)

Link to comment
Share on other sites

Chameleon starts and shows me correctly 2 OS X installation :

"hd(1,3) Lion" and "hd(1,6) Lion Test".

Hi MiMe

 

Where are those numbers taken from? as Chameleon will use the device list presented by the BIOS and not OS X. If you stick with those number's then Chameleon will do as you ask. OS X is known to show (sometimes) the drives in a different order to that from BIOS.

 

To see the numbering that Chameleon uses, press the TAB key when at the GUI mode.

 

 

Hi jack kyle

 

Thanks for testing. See reply to MiMe for drive order query. For reference, I have two HDD's and sometimes OS X shows hd(0) as disk0 and hd(1) as disk1, on another boot they could be reversed.

 

1640 installer is still alpha and buggy[should read blackosx release post ;p ] (empty chameleon.boot.plist no copy back extensions and if you install it twice (in my case) it just stops creating the extra folder even though the log says it did (elevation prob?).

try installing first chameleon rc5 r760, copy the extra folder (just in case) and then without reboot reinstall chameleon 2.1 r1640. Its what I did to get back the new cham files (modules...)

I guess it's all down to expectations for the installer. It's designed to create a fresh install, not to upgrade a previous install. Maybe I could look at the merging of an existing /Extra folder if that's wanted by the majority?

 

If you run the installer only selecting 'Standard' or 'EFI' from the Chameleon Bootloader menu, then it will just install the boot loader, leaving any current /Extra folder intact and you should be able to just reboot.

 

If you select to install the Bootloader and another item from the list that lives in the /Extra folder, for example a Module, then the installer will create a new /Extra folder and a blank org.chameleon.Boot.plist for you to build upon. Any existing /Extra folder will be backed up so you can replace items if wanted.

 

If you select boot options/kernel flags from the installer menu then the new org.chameleon.Boot.plist will be populated with those selections.

Link to comment
Share on other sites

Hi jack kyle & blackosx,

 

thanks for your posts.

 

Changing boot order (internal hdd before usb hdd; choosing boot device by

pressing F11) inside BIOS does not help.

 

IMHO problem is from Chameleon because OS X (which is mach_kernel)

can't be started. Which Chameleon routine is starting /mach_kernel?

It seems to me that this function is using another way to distinguish hdd

than function that is getting hdd info from BIOS.

 

If Chameleon can't start /mach_kernel it also won't be able to read

/Extra/org.chameleon.Boot.plist from same partition. This makes sense

to me.

 

Booting from external CDROM (rBoot-LE-1.0.1) works like a charm. Unfortunately

I can't remember whether LION is hd(0,3) or hd(1,3). (I can test it tomorrow.)

Probadly - which makes sense - it will be hd(0,3) and there'll no hdd disorder.

 

Yes I do know that it's a alpha release. My workaround (typing twice rd=disk0s3)

works. I'm more and less fine but WAF could be highly improved ;-)

 

Unfortunately 64 Bit GRUB2 inside EFI can't boot MBR. Thus I do need USB

stick.

 

Thanks a lot again.

MiMe

Link to comment
Share on other sites

Changing boot order (internal hdd before usb hdd; choosing boot device by

pressing F11) inside BIOS does not help.

Hi MiMe

 

From a quick Google search I read there have been a few suggested solutions to your problem posted:

 

- One being to swap the ports the HDD's are plugged in to?

- Another to add the following key/string to org.chameleon.Boot.plist (numbers depend on your system)

Default Partition
<string>hd(0,3)</string>

- or add the device to the kernel flags as you are already doing.

<key>Kernel Flags</key>
<string>rd=diskXsX</string>

- There's also skip_partno patch which may or may not help you. I don't know as I've never used it.

 

IMHO problem is from Chameleon because OS X (which is mach_kernel)

can't be started. Which Chameleon routine is starting /mach_kernel?

It seems to me that this function is using another way to distinguish hdd

than function that is getting hdd info from BIOS.

You can find the code at http://forge.voodooprojects.org/p/chameleo...tree/HEAD/trunk

I don't know exactly where to point you without reading through the code myself but maybe look in /i386/boot2/ for either boot.c or mboot.c

 

Another suggestion could be to install Chameleon HDD then use it to chain load GRUB. but GRUB will need to be installed to the partition and not MBR.

 

Yes I do know that it's a alpha release.

The release I have in this thread for testing is only for the package installer code. The Chameleon code itself is far from an alpha release and is in continuous development. You can always post your issues here.

Link to comment
Share on other sites

Chameleon installer log - Tue Oct 25 00:44:00 EDT 2011
Installer version: 2.1svn 1655
======================================================
/dev/disk0
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:     FDisk_partition_scheme                        *120.0 GB   disk0
  1:               Windows_NTFS Windows 7 Pro           120.0 GB   disk0s1
/dev/disk1
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *60.0 GB    disk1
  1:                        EFI                         209.7 MB   disk1s1
  2:                  Apple_HFS Lion                    59.7 GB    disk1s2
/dev/disk2
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *1.0 TB     disk2
  1:       Microsoft Basic Data Storage                 1.0 TB     disk2s1
/dev/disk3
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *1.0 TB     disk3
  1:         Microsoft Reserved                         134.2 MB   disk3s1
  2:       Microsoft Basic Data Media                   1.0 TB     disk3s2
/dev/disk4
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:     FDisk_partition_scheme                        *300.1 GB   disk4
  1:               Windows_NTFS Data Drive              300.1 GB   disk4s1
/dev/disk5
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:     FDisk_partition_scheme                        *500.1 GB   disk5
  1:                  Apple_HFS Backup                  500.1 GB   disk5s1
/dev/disk6
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *8.2 GB     disk6
  1:                        EFI                         209.7 MB   disk6s1
  2:                  Apple_HFS myHack OS X Install ... 7.8 GB     disk6s2
======================================================
Running Standard postinstall script
Target volume = / on /dev/disk1s2
Target disk already has existing Chameleon stage 0 loader - boot0
======================================================
Stage 0 loader not written to /dev/disk1.
Written boot1h to /dev/rdisk1s2.
Written boot to / on /dev/disk1s2.
======================================================
About to check your disk for previous installations
which involves checking the EFI system partition if
appropriate for this disk.
Mounting /dev/disk1s1 as /Volumes/EFI
======================================================
Checking for previous chameleon installations on disk1
************************** TAKE NOTE *****************************
**** There is an existing Chameleon installation on /dev/rdisk1s1
**** and that installation will still be the default loader as it's
**** on an earlier partition. If you want this new installation on
**** / to be default then you will need to remove the
**** boot file from /dev/rdisk1s1 and re-run this installer.
**************************************************************
======================================================
Disk: /dev/rdisk1	geometry: 7297/255/63 [117231408 sectors]
Signature: 0xAA55
        Starting       Ending
#: id  cyl  hd sec -  cyl  hd sec [     start -       size]
------------------------------------------------------------------------
1: EE 1023 254  63 - 1023 254  63 [         1 -  117231407] <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 / partition active.
======================================================
Standard script complete
Installer version: 2.1svn 1655
Running Post postinstall script
Target volume = 
Installed module:Resolution.dylib
Added boot option: Graphics Mode=1920x1080x32
Writing folder: /Extra
Volume named 'EFI' is mounted...
Unmounting /dev/disk1s1
Cleanup: ,2
======================================================
Post script complete

 

Ok, losing my mind here. Why is the installer not creating the /Extra folder?! I have selected the resolution module, standard install, and selected a resolution option. Thanks in advance!

Link to comment
Share on other sites

Hi smsaim

 

Thanks for posting the log file.

I think I see what the problem is and am looking at a fix now....

I'll post a revised package when I think I've solved it.

 

UPDATE:

Please can you test this revised version.

The /Extra folder should now be correctly copied to the target destination when installing to / .

 

 

EDIT:

Removed 25th October - 21:59. Replace by version in post #1049

Link to comment
Share on other sites

Hi smsaim

 

Thanks for posting the log file.

I think I see what the problem is and am looking at a fix now....

I'll post a revised package when I think I've solved it.

 

UPDATE:

Please can you test this revised version.

The /Extra folder should now be correctly copied to the target destination when installing to / .

Thanks blackosx! That did it! It created the Extra folder just fine. I guess you fixed targeting the 'target volume'?!

 

Could give me some info on Resolution.dylb? I'm trying to get my GTX 470 to make Chameleon boot at 1920x1080. The highest res in my video cards VESA is 1280x1024 and that's the most I can get. I thought the options I selected here would give the high res boot but it didn't. Here's the new log. Will tinker around a bit more.

 

Chameleon installer log - Tue Oct 25 07:40:43 EDT 2011
Installer version: 2.1svn 1658
======================================================
/dev/disk0
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:     FDisk_partition_scheme                        *120.0 GB   disk0
  1:               Windows_NTFS Windows 7 Pro           120.0 GB   disk0s1
/dev/disk1
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *1.0 TB     disk1
  1:         Microsoft Reserved                         134.2 MB   disk1s1
  2:       Microsoft Basic Data Media                   1.0 TB     disk1s2
/dev/disk2
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *60.0 GB    disk2
  1:                        EFI                         209.7 MB   disk2s1
  2:                  Apple_HFS Lion                    59.7 GB    disk2s2
/dev/disk3
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *1.0 TB     disk3
  1:       Microsoft Basic Data Storage                 1.0 TB     disk3s1
/dev/disk4
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:     FDisk_partition_scheme                        *300.1 GB   disk4
  1:               Windows_NTFS Data Drive              300.1 GB   disk4s1
======================================================
Running Standard postinstall script
Target volume = /Volumes/Lion on /dev/disk2s2
Target disk already has existing Chameleon stage 0 loader - boot0
======================================================
Stage 0 loader not written to /dev/disk2.
Written boot1h to /dev/rdisk2s2.
Written boot to /Volumes/Lion on /dev/disk2s2.
======================================================
About to check your disk for previous installations
which involves checking the EFI system partition if
appropriate for this disk.
Mounting /dev/disk2s1 as /Volumes/EFI
======================================================
Checking for previous chameleon installations on disk2
======================================================
Disk: /dev/rdisk2	geometry: 7297/255/63 [117231408 sectors]
Signature: 0xAA55
        Starting       Ending
#: id  cyl  hd sec -  cyl  hd sec [     start -       size]
------------------------------------------------------------------------
1: EE 1023 254  63 - 1023 254  63 [         1 -  117231407] <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/Lion partition active.
======================================================
Standard script complete
======================================================
Running Post postinstall script
Target volume = /Volumes/Lion
Installed module:Resolution.dylib
Added boot option: Graphics Mode=1920x1080x32
Added boot option: GraphicsEnabler=Yes
Writing folder: /Volumes/Lion/Extra
Volume named 'EFI' is mounted...
Unmounting /dev/disk2s1
Cleanup: ,2
======================================================
Post script complete

Link to comment
Share on other sites

Running 1655 (previously 1496) it completely messed up my Hackintosh, i.e. it renamed /Extra to /Extra_OLD... and looked as though it tried to install to an EFI partition (which I've never used or created):

 

/dev/disk0
  #:					   TYPE NAME					SIZE	   IDENTIFIER
  0:	 FDisk_partition_scheme						*1.0 TB	 disk0
  1:			   Windows_NTFS						 73.4 GB	disk0s1
  2:				  Apple_HFS ATVHD				   926.8 GB   disk0s2
/dev/disk1
  #:					   TYPE NAME					SIZE	   IDENTIFIER
  0:	  GUID_partition_scheme						*1.0 TB	 disk1
  1:						EFI						 209.7 MB   disk1s1
  2:				  Apple_HFS MacOSX				  999.9 GB   disk1s2

Installer version: 2.1svn 1655
Running Post postinstall script
Target volume = 
Installed Theme:Default
Found existing /Extra folder. Renaming it /Extra-OLD-22-12-40
Writing folder: /Extra
Volume named 'EFI' is mounted...
Unmounting /dev/disk1s1

 

 

Haven't had this issue before on a Chameleon installer and don't know much about Chameleon but I thought I'd post this as possibly it hasn't been seen before. I renamed /Extra_OLD to /Extra and all is fine. Why would it mess with this folder anyway?

Link to comment
Share on other sites

please look for my last issue .. the ati.c has an error in HD6490M for the family chipset

CHIP_FAMILY_RV730 for 6490M and 6470M was changed to

CHIP_FAMILY_CAICOS in revision 1657.

Link to comment
Share on other sites

@squatter

 

The package installer here was put together with the aim of installing Chameleon, and not upgrading a previous installation. Though that will change with the next revision.

 

There are notices here about making sure you have a backup method of booting your system. Either a secondary HDD or bootable USB flash drive that you've verified as working, before using this installer. This should be a default operation for any hackintosh user to safeguard against any issue of a failed boot.

 

But let's look at your issues.

it renamed /Extra to /Extra_OLD...

This is by design. If you select any option in the installer which would create an item destined for the /Extra folder then the installer will create an /Extra folder. That means then any option in the installer which is not the Chameleon Bootloder section.

 

On completion, that /Extra folder will be written to the root of the target partition, after of course checking for an existing one and backing that up if found.

 

I see you chose to install a Theme so that's why that happened.

 

and looked as though it tried to install to an EFI partition (which I've never used or created)

The installer will only attempt to install to the EFI system partition if you select the 'EFI' option in the menu. At no other time is anything written to the EFI system partition, and at no time is the EFI system partition formatted. You may have not created it, but OS X's Disk Utility did when you partitioned your disk with a GPT.

 

But what the installer does is this: If either the Standard or EFI install option is selected then during the install process, the scripts will check all the other partitions on the disk, including the EFI system partition (if it exists) for a previous Chameleon installation (check smsaim's log for an example). This is to try to help users identify what they have previously installed and if there could be any possible repercussions with installing to another location.

 

At the end of the process, the installer will unmount any volumes mounted with the name 'EFI' to clean up. It won't delete anything, just unmount.

 

Haven't had this issue before on a Chameleon installer and don't know much about Chameleon but I thought I'd post this as possibly it hasn't been seen before.

Hope this helps answer your questions.

ps. Was that installer log you posted the complete log?

 

Thanks blackosx! That did it! It created the Extra folder just fine. I guess you fixed targeting the 'target volume'?!

Thanks for the confirmation smsaim.

Most of my internal tests have been installing to different disks and not to my currently booted volume so I'd missed the issue of installing to /. The log you posted highlighted that.

 

Could give me some info on Resolution.dylb? I'm trying to get my GTX 470 to make Chameleon boot at 1920x1080. The highest res in my video cards VESA is 1280x1024 and that's the most I can get. I thought the options I selected here would give the high res boot but it didn't. Here's the new log. Will tinker around a bit more.

Sorry. I don't know much about the Resolution Module. I suggest you check voodoo projects forum for more info. But as I understand it, you will only see the highest VESA res as supported by your card, which you have already found.

 

please look for my last issue .. the ati.c has an error in HD6490M for the family chipset

CHIP_FAMILY_RV730 for 6490M and 6470M was changed to

CHIP_FAMILY_CAICOS in revision 1657.

Hi ugokind

 

I see the commit. I'll update my branch with the latest trunk changes for the next revision I post. Thanks

Link to comment
Share on other sites

Thanks blackosx for the comprehensive reply. I did select some options then de-select them (but don't remember selecting the EFI option) and added the default theme to overwrite mine. I had a backup of everything so was OK, and I'm booting fine now with the new Chameleon. Here's the full log attached if it helps.

chamlog.txt

Link to comment
Share on other sites

Package Installer has now been updated for further testing. Now at rev1662 and replaces all previously posted versions.

 

It builds upon the rev1658 which smsaim tested earlier. The changes include:

- merged latest trunk revisions (up to r1657).

- There's now an upgrade option which will merge any newly selected options with an existing /Extra folder.

- Any occurrence of /Extra/com.apple.Boot.plist will be renamed /Extra/org.chameleon.Boot.plist.

 

For the upgrade option, please note:

If you choose a boot option which is already present in your com.apple.Boot.plist then it will NOT be merged.

For example: If you already have

<key>Graphics Mode</key>
<string>1680x1050x32</string>

and choose a resolution of 1920x1080x32 from the installer menu then this will NOT be updated.

Please check the org.chameleon.Boot.plist after running the upgrade option to make sure everything is as you want it.

 

As before,

Before attempting this though, make sure you have a backup method of booting your system. Either a secondary HDD or bootable USB flash drive that you've verified as working.

To anyone who would like to test this, please do so on a test rig and understand that this is a beta.

If for any unlikely reason that data loss should occur, I will not be held responsible. You test this at your own risk.

 

Source is available from: http://forge.voodooprojects.org/p/chameleo...anches/blackosx

 

I look forward to hearing any feedback.

Thanks

 

UPDATE:

rev1662 removed as installer has now been added to Chameleon's trunk.

Link to comment
Share on other sites

Latest trunk using Chameleon Wizard and 10.7.2 update desktop freezes. Went away with latest Chimera 1.5.4 r1394.

 

Azimutz added my card many revisions ago back around r1115

 

Asus G74SX Nvidia GTX 560M

 

Vendor: NVIDIA (0x10de)

Device ID: 0x1251

 

Max Resolution and currently running resolution with the Chimera loader 1920x1080x32

 

Can someone have a look into this to see why the Chimera tree is not freezing with this card and yet the Chameleon r1657 trunk is?

 

Thanks

Link to comment
Share on other sites

@blackosx: still nothing. i did the changes with kernel flags. still 64 bit.

guess the problem is : i never had an extra folder on my harddrive (root).

 

i copied it manually from the distribution. no matter what i try i have no idea what bootlist from where is used... this is really driving me nuts ;)

Link to comment
Share on other sites

@blackosx: still nothing. i did the changes with kernel flags. still 64 bit.

guess the problem is : i never had an extra folder on my harddrive (root).

@sonicfire - You've still got your problem? I thought you'd have sorted it by now?

 

Get yourself a USB flash drive, erase it using Disk Utility - use either FAT32 or Mac OS Extended (journaled). Then run the latest version of the installer here, and point it to your newly erased USB device. Select New installation / Standard bootloader install, and select the options you need for your /Extra folder, including the arch=i386 option.

 

When it's finished, add your DSDT.aml, SMBIOS.plist, Extensions and any other file your system needs to boot to the /Extra folder on your USB flash drive. When you're happy you have everything in the /Extra folder you need, reboot your system, selecting to boot the USB from the BIOS. You should be booted in to Chameleon's GUI where you can proceed to select and boot your OS X installation.

 

Check to see if that boots the kernel in 32-bit mode. If it does, then we can look at sorting your system.

 

Can someone have a look into this to see why the Chimera tree is not freezing with this card and yet the Chameleon r1657 trunk is?

Hi oSxFr33k

 

Your best chance of finding a solution is to post an issue to the forge

 

I like the installer facelift =).

Hey EnzoFX :unsure:

Thanks. I couldn't resist.. lol

Link to comment
Share on other sites

Hi guys ! I just translated the Ressources/en.lproj folders from the latest blackosx and ErmaC branches to French.

But, how do I upload them ? I already changed their name to fr.lproj. Just zip 'em and upload it here as attachement ?

Link to comment
Share on other sites

From the thousand or so downloads of the different versions I've posted here, there has been little feedback. This I can only assume is because users just haven't bothered as the installer has just worked as expected, and there have been no issue with any problems.

 

I want to progress and apply the package installer code in to the main Chameleon trunk, but before I do, I know how dangerous it can be to assume, so I am asking a final call to anyone to feedback any issues of negative results with the last installer I've posted.

 

Thanks

 

Just zip 'em and upload it here as attachement ?

Hi Tenval

 

Thanks. Yes - upload them here and I'll add to the code.

 

Though please note, I might revise some of the text before a final release in which case that could involve revising all the translations somehow?

Link to comment
Share on other sites

Though please note, I might revise some of the text before a final release in which case that could involve revising all the translations somehow?

 

Hi !

 

 

That's no problem, but the best would be that you tell us what you did/did not modify on the final version localization files (especially the .strings file, kinda tough one).

 

Meanwhile, here are the French files.

blackosx_r1658_fr.zip

ErmaC_r1663_fr.zip

Link to comment
Share on other sites

×
×
  • Create New...