Jump to content

Mac OS X Lion (Developer Preview) Released


harrydeo
 Share

1,521 posts in this topic

Recommended Posts

It was a little more complicated than that. OSInstall.mpkg contains several checks that must be overcome before it allowed installation to take place. The two most important were: a. you must be installing to a certain set of Apple computers, and b. you must install to a GUID partition scheme.

 

To install to MBR, you needed to have a modified installer package. To install to a non-Apple machine, there were two workarounds: a. a modified installer package, OR b. your bootloader needed to inject the right information so that the installer thought you had a suitable Apple computer. The second boot file that Netkas produced had a hard-wired injection to get around that requirement. Certain versions of [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and XPC could inject the correct information. So, if you used one of those, you had no problems and did not need to modify or replace the OSInstall.mpkg file.

 

A lot of people think it is a no-brainer to use Chameleon RC3 and the second Netkas boot file. But a lot of people are still stymied with constant double KP's when using that combination. I never got a single boot using them.

 

In my case, the issue is different - despite my single Apple-OS HD being all-GPT (GUI Partition Table), it's split between Snow and Lion; a condition that no HD-based bootloader permits (not even AnVal's new loader) - hence my sticking with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url].

Link to comment
Share on other sites

It was a little more complicated than that. OSInstall.mpkg contains several checks that must be overcome before it allowed installation to take place. The two most important were: a. you must be installing to a certain set of Apple computers, and b. you must install to a GUID partition scheme.

 

To install to MBR, you needed to have a modified installer package. To install to a non-Apple machine, there were two workarounds: a. a modified installer package, OR b. your bootloader needed to inject the right information so that the installer thought you had a suitable Apple computer. The second boot file that Netkas produced had a hard-wired injection to get around that requirement. Certain versions of [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and XPC could inject the correct information. So, if you used one of those, you had no problems and did not need to modify or replace the OSInstall.mpkg file.

 

A lot of people think it is a no-brainer to use Chameleon RC3 and the second Netkas boot file. But a lot of people are still stymied with constant double KP's when using that combination. I never got a single boot using them.

 

Yes, and yes, totally agreed. I lucked out the first time since I had so many HDs laying around, hence no need for MBR. But a few days ago, I got my hands on a 16g USB stick. So I was itchy to put BaseSystem.dmg on the stick, aloong with either [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] ot XPC. Here is what discover:

- XPC injects proper cheats to fool the installer ([url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] does not), but the fact that BaseSystem resides on the MBR USB stick, install halts immediately after the welcome screen.

- Now that I have the rigged OSInstall.mpkg, the install went through fine; and I purposedly install DP2 on a hybrid MBR HD. But after that, both [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and XPC balk at MBR with multiple OSes. So it looks like I may have to go the Netkas way.

I will report my progress later.

Link to comment
Share on other sites

Regarding your boot loader

 

great job first boot loader i have used that has booted my system, now instead of booting my system with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] i can boot with full processor speed, DSDT, smbios etc just awesome thank you man. does this branch of RC5 allow the ATIFb string or ATIConfig string? is it from Kabyl's branch?

 

this is great news for me, only thing that was disappointing was using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] :)

Link to comment
Share on other sites

Anyone here willing to take a bet what makes Lion boot or fail? I tell you this: It's the freaking Device (PCI0) in your DSDT!!!!!!!!

 

This is why so many of you with a Gigabyte board can boot Lion and we Asus board users cannot.

Link to comment
Share on other sites

great job first boot loader i have used that has booted my system, now instead of booting my system with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] i can boot with full processor speed, DSDT, smbios etc just awesome thank you man. does this branch of RC5 allow the ATIFb string or ATIConfig string? is it from Kabyl's branch?

 

this is great news for me, only thing that was disappointing was using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] :)

It's from valv's branch and I'm not sure it supports the ATIFb string or ATIConfig string.

It supports everything latest AnVAL supports...

 

Anyone here willing to take a bet what makes Lion boot or fail? I tell you this: It's the freaking Device (PCI0) in your DSDT!!!!!!!!

 

This is why so many of you with a Gigabyte board can boot Lion and we Asus board users cannot.

What precisely is the issue with PCI0?

My PCI root is also defined in DSDT as PCI0 and it does boot...

Link to comment
Share on other sites

The secret with my GA-EP45-UD3R and Cartri bios for DP2 was to follow the usual guides for DP1 and remove PlatformSupport list in CoreServices, put fakesmc.kext in Extensions, delete Cache folder, put dsdt.aml in S/L/Extra folder, set correct permissions on fakesmc, AND DELETE AppleTyMCEDriver in Extensions. The lack of network support was solved using the Lnx2Mac’s Realtek RTL81xx driver.

 

Anyone here willing to take a bet what makes Lion boot or fail? I tell you this: It's the freaking Device (PCI0) in your DSDT!!!!!!!!

 

This is why so many of you with a Gigabyte board can boot Lion and we Asus board users cannot.

Link to comment
Share on other sites

What precisely is the issue with PCI0?

My PCI root is also defined in DSDT as PCI0 and it does boot...

Let's start by adding a signature :)

 

 

The secret with my GA-EP45-UD3R and Cartri bios for DP2 was to follow the usual guides for DP1 and remove PlatformSupport list in CoreServices, put fakesmc.kext in Extensions, delete Cache folder, put dsdt.aml in S/L/Extra folder, set correct permissions on fakesmc, AND DELETE AppleTyMCEDriver in Extensions. The lack of network support was solved using the Lnx2Mac’s Realtek RTL81xx driver.

That was the easy part. Now use that HDD and connect it to an Asus board. I did. I have 20 different boards here (in a class room) and only GB boards boot. What a coincidence. And now change PCI0.MCHC in your DSDT/BIOS and it is POOF !

 

 

You're not talking about double fault - or?

Yes I do. I had to setup PCI0.MCHC in a certain way. Won't help other people though since this is board specific.

Link to comment
Share on other sites

someone did in AMD?

 

It´s not possible at the moment because there is no kernel for it and it will take time at least to the final version until apple will release the sourcecode.

 

So there is no chance to install it on an amd system.

Link to comment
Share on other sites

Let's start by adding a signature ;)

 

Don't be like that! PCI0 is inside mac's IOREG so this cannot be the cause of a CPU specific panic. PCI0 is used in all mac's ioreg which connects EHCx, Ethernet etc

 

So no PIC0 is not the case.

 

Your referring to a label within the PCI0 class.

 

MCHC is also board specific so this is not the case for everyone. and this is not what is causing the DF.

DSDT in or out of Extra folder has no effect, my DSDT under the PCI0 section has no reference to specific labels only from an ASUS board.

 

In a MacBook X3100 the Intel northbridge, the path inside the IOREG is registered against the chipset bridge.

("acpi-path" = "IOACPIPlane:/_SB/PCI0/MCHC@0") the Intel GMA X3100 works off this bridge.

 

so how could you be saying this has something to do with the DF?

 

What causes a kernel trap 0x00000008 ?

That's the Double Panic- the kernel panics while panicing. FUNNY THAT :P

It can be caused by corrupt driver code(I think the code could be referring to Chameleon), but is more likely to be bad ram (or bad CPU, motherboard- anything that causes a bad instruction to get to the cpu).

 

Could it be fakesmc? could it be NullCPU kext, well every DP1 and DP2 install everyone has used fakesmc, so eliminating wither fakesmc or chameleon code would be a good start.

 

Another could be certain hardware id's not responding well with the kernel.

Can't be bad memory, so it is hardware id related, fakesmc related or chameleon related.

Link to comment
Share on other sites

hi, dp2 install without problems on a X58A-UD3R GT240 to restart after about 10 times stayed at "PCI configuration Begin" try to boot with-x the same problem, try using the installer and the same problem. my gfx is configured in the DSDT. dsdt it works perfectly in Snow as in DP1.

also [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and XPC probe with the same results. any ideas?

Link to comment
Share on other sites

hi, dp2 install without problems on a X58A-UD3R GT240 to restart after about 10 times stayed at "PCI configuration Begin" try to boot with-x the same problem, try using the installer and the same problem. my gfx is configured in the DSDT. dsdt it works perfectly in Snow as in DP1.

also [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and XPC probe with the same results. any ideas?

 

 

Copy fakesmc.kext to s/l/e and repair permissions....

Link to comment
Share on other sites

Hi!

 

I just installed dp2, but when the login screen is about to load, I get a corrupted/scrambled image. (Using NVEnabler or Natit or ATY_Init)

 

I'm running a gtx260 with no problems under dp1.

 

Which are the kexts related to NVidia cards? Maybe checking the differences between dp1 and dp2 ones, I can get a solution.

 

Thanks

Link to comment
Share on other sites

Hi!

 

I just installed dp2, but when the login screen is about to load, I get a corrupted/scrambled image. (Using NVEnabler or Natit or ATY_Init)

 

I'm running a gtx260 with no problems under dp1.

 

Which are the kexts related to NVidia cards? Maybe checking the differences between dp1 and dp2 ones, I can get a solution.

 

Thanks

 

Remove the kext injectors, enable remote login and then copy injector over again, then VNC in and set a resolution high enough to restore the scrambled screen, not 100% fix but try it please.

Link to comment
Share on other sites

That was the easy part. Now use that HDD and connect it to an Asus board. I did. I have 20 different boards here (in a class room) and only GB boards boot. What a coincidence. And now change PCI0.MCHC in your DSDT/BIOS and it is POOF !

Could you post the modifications you made.

It's good to know what to edit (and why...).

Thanks in advance ;)

Link to comment
Share on other sites

hi, dp2 install without problems on a X58A-UD3R GT240 to restart after about 10 times stayed at "PCI configuration Begin" try to boot with-x the same problem, try using the installer and the same problem. my gfx is configured in the DSDT. dsdt it works perfectly in Snow as in DP1.

also [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and XPC probe with the same results. any ideas?

 

use XPC and copy your EFI String to settings.plist to DeviceProperties ... after 10 Secs [PCI configuration begin] should go away and Lion goes to boot up in full size ...

Link to comment
Share on other sites

Remove the kext injectors, enable remote login and then copy injector over again, then VNC in and set a resolution high enough to restore the scrambled screen, not 100% fix but try it please.

 

When I login remotely, I can only see a white screen. Thanks anyway. :D

Link to comment
Share on other sites

Could you post the modifications you made.

It's good to know what to edit (and why...).

Thanks in advance :)

 

Hi Andy i'm also interested, RevoGirl i was wrong by saying my board does not have IMCH which refers to the northbridge.

Intel Lynnfield IMC

Device (IMCH)
		{
			Name (_ADR, One)
			OperationRegion (PBUS, PCI_Config, Zero, 0xC0)
			Field (PBUS, DWordAcc, NoLock, Preserve)
			{
						Offset (0x40), 
					,   4, 
				PM0H,   2, 
						Offset (0x41), 
				PM1L,   2, 
					,   2, 
				PM1H,   2, 
						Offset (0x42), 
				PM2L,   2, 
					,   2, 
				PM2H,   2, 
						Offset (0x43), 
				PM3L,   2, 
					,   2, 
				PM3H,   2, 
						Offset (0x44), 
				PM4L,   2, 
					,   2, 
				PM4H,   2, 
						Offset (0x45), 
				PM5L,   2, 
					,   2, 
				PM5H,   2, 
						Offset (0x46), 
				PM6L,   2, 
					,   2, 
				PM6H,   2, 
						Offset (0x47), 
						Offset (0x48), 
					,   7, 
				HENA,   1, 
						Offset (0x50), 
				PXEN,   1, 
				PXSZ,   2, 
					,   17, 
				PXBR,   12
			}
		}
	}
}

 

So what was changed here to stop the DF?

Sorry RevoGirl, about the misunderstanding regarding IMCH, had a DSDT extracted from MacOSX which did not pickup the IMCH, had to extract from Windows or Linux.

 

Maybe the wrong instructions are being sent to the northbridge which in return panic the CPU at CPU0 before it even loads any kexts?

 

Also looked at X58 Gigabyte setup and cannot find Method IMCH. Also my old X58 setup and cannot find IMCH.

 

Is IMCH only related to PM55 or HM55 chipset boards?

Link to comment
Share on other sites

Those of you with X58A-UD*, how did you go about getting around the Double KP when installing/running? Which Bootloader are you using?

 

 

I have an X58A-UD7 (rev1, bios F7) that I've been toying with DP1 on. I'm using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] 1.4a and have not experienced a single KP yet. I've stayed with this so far even though it's not as slick as chameleon; the reason being that I've been using Kabyl's bootloader with my ATI 5870 on SL, [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] picks up the 5870 as a generic 5000 series card (no QE/CI though)

Link to comment
Share on other sites

I have an X58A-UD7 (rev1, bios F7) that I've been toying with DP1 on. I'm using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] 1.4a and have not experienced a single KP yet. I've stayed with this so far even though it's not as slick as chameleon; the reason being that I've been using Kabyl's bootloader with my ATI 5870 on SL, [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] picks up the 5870 as a generic 5000 series card (no QI/CE though)

 

stick with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] is better until this DF is resolved with Chamelon, I also can force a framebuffer personality but i cannot get qe/ci. sucks :)

Link to comment
Share on other sites

 Share

×
×
  • Create New...