Jump to content

Mac OS X Lion (Developer Preview) Released

harrydeo

By harrydeo,
in New Releases and Updates

 Share
1,521 posts in this topic

Recommended Posts

Andy Vandijck
Andy Vandijck
Posted
Posted
Hey Andy, do you have any estimate for the atom kernel? I've already uploaded the files DP2 Kernel :D

Ok, downloading original DP2 kernel right now...

I'll upload the Atom / new Celeron kernel when I'm done with it... :angry:

Link to comment
Share on other sites
Time2Retire
Time2Retire
Posted
Posted
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

Nope. This IMCH you mention here is Apple's PDRC and the _CRS method of this method takes care of a bunch of address allocations which are vital to a good boot. Just change it and you are toast. The fact that you have this (PBUS) OperationRegion/Field combo in your DSDT is a good thing. The thing is that I don't see certain things in Asus DSDT's that make a good boot possible.

 

Here's another example; I only found out recently that this Name (HPTC, 0xFED1F404) in my DSDT is read by AppleHPET.kext (be my guest and check it with otool). And yes that's the 'High Precision Timer' aka HPET kext. One that must be good or your hack won't ever boot. Oh yes. People can boot Snow Leopard without it, but this change was made only recently so... fix it.

 

So what was changed here to stop the DF?

It's not an easy fix, or I would have mentioned it already. I'm not a teaser.

 

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?

In this case the name doesn't really matter, because it is just a matter of giving the OS (read: AppleACPIFamily.kext) what it needs, but you need to have certain things in your DSDT or it will Double Fault KP. And not having the HPTC is just one of them. In short; We're not talking about an easy one stop all solution. This need time, but we'll get there eventually. Patience is however a requirement, and nobody likes to be made a fool when they really know stuff so... :)

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted
but you need to have certain things in your DSDT or it will Double Fault KP.

Hi DHP

 

I understand what you're saying, though it doesn't help explain why I can (sometimes) boot 10.7 on my system using Netkas' modded RC3 or Andy's modded AnVal RC5 without experiencing a double fault when using my existing DSDT. I mean, if I could never boot with those loaders then it would make sense.

Link to comment
Share on other sites
atlee
atlee
Posted
Posted
Hi DHP

 

I understand what you're saying, though it doesn't help explain why I can (sometimes) boot 10.7 on my system using Netkas' modded RC3 or Andy's modded AnVal RC5 without experiencing a double fault when using my existing DSDT. I mean, if I could never boot with those loaders then it would make sense.

 

I plus 100 on this too. I can boot but randomly. DHP would already have explained it if she found the solution, If she posts her solution then i can change it to match my methods.

 

Also HPET is fixed in my DSDT and shouldn't have any problems with SL or Lion.

 

I looked into this kernel panic and what it happens, like i stated before the IMCH is referred to the northbridge of the CPU, so this northbridge controls the RAM and also the GFX controller. normally a 0x00000008 kernel trap is causes by hardware id that kernel does not like, kexts which are incompatible, faulty hardware.

 

Like i said before i doubt it's only IMCH related or even HPET like you mention above. the wrong instructions is being sent to a certain point and being rejected and causing a CPU panic.

 

To Isolate the problem it isn't our ram, so it leaves Chameloen code if it is built correctly for Lion or not or the kext's we are using for SL inside of Lion. But kext's might not be an issue because [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] can boot Lion fine every single time and i know why because it's EFI based and uses original apples boot file and spoofs a lot of things like smbios etc.

 

My guess is it's the Chamelon code.

 

The IMCH is referring to in it's full name Integrated Memory Control Hub, which is a graphics and memory controller.

 

My Southbridge and Northbridge match Apple's hardware so i'm not too sure why you are looking at the Northbridge.

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted

DHP is working towards getting her new Asus system booting Lion, so my guess is these things she's finding out are based on Asus hardware as she posted earlier. She has proved in the past to be resourceful and I don't doubt her abilities so let's give her time and see what she comes up with.

 

I'm no ACPI expert and only know what I have read in the past and from my occasional experiments etc. But looking at my iMac 11,3's DSDT, Name (HPTC, 0xFED1F404) is there as it is in DHP's DSDT. So I guess this is maybe a common addition in newer boards using newer CPU's, as it's not in my hack's DSDT or a Macpro3,1's DSDT which is what mine's roughly based on. But it's not mandatory to boot 10.7.

 

XPC and [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] have proved that Chameleon's ideology / coding needs changing if it's to be a reliable bootloader for Lion.

Link to comment
Share on other sites
atlee
atlee
Posted
Posted
DHP is working towards getting her new Asus system booting Lion, so my guess is these things she's finding out are based on Asus hardware as she posted earlier. She has proved in the past to be resourceful and I don't doubt her abilities so let's give her time and see what she comes up with.

 

I'm no ACPI expert and only know what I have read in the past and from my occasional experiments etc. But looking at my iMac 11,3's DSDT, Name (HPTC, 0xFED1F404) is there as it is in DHP's DSDT. So I guess this is maybe a common addition in newer boards using newer CPU's, as it's not in my hack's DSDT or a Macpro3,1's DSDT which is what mine's roughly based on.

 

XPC and [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] have proved that Chameleon's ideology / coding needs changing if it's to be a reliable bootloader for Lion.

 

I'm also no expert, i'm a web designer in my field but i get the drift with a lot of this stuff. I also find Name (HPTC, 0xFED1F404) inside my DSDT. DHP does sound like she is getting to something but i'm not sure why the link to the NB controller. anyway i'm willing to listen and learn. I would like to learn more about where she is targeting in her DSDT, patches that are being tested and why those targets have been chosen if she is happy to make them available to everyone so others can change it to match their platform and try the same tricks.

Link to comment
Share on other sites
elitee
elitee
Posted
Posted
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)

 

I managed to get it to boot with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url], but I have to delete the cache everytime. [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] also appears to be not reading my DSDT, this is with 1.5a, is your DSDT working?

Link to comment
Share on other sites
atlee
atlee
Posted
Posted
I managed to get it to boot with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url], but I have to delete the cache everytime. [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] also appears to be not reading my DSDT, this is with 1.5a, is your DSDT working?

 

DSDT function does not work for me also, the smbios doesn't spoof anything either. I guess a bootloader is needed to fix all these issues but it will take time.

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted

XPC loads a modified DSDT, allows SMBIOS overrides and EFI device property injection. It patches the FADT for restart and I think can now even load kexts from an /Extra/Extensions.mkext. All that and other tricks... It's my default bootloader for Lion for now.

Link to comment
Share on other sites
mitch_de
mitch_de
Posted
Posted

XPC UEFI-Bootloader 0.82.33 | Build 05.04.2011 http://www.mediafire.com/?7zz5auzknab66nz

Hint: In the settings.plist of all XPC are some settings you may delete (like DeviceProperties key injection, i believe thats an GPU - may confuse your system if you have other gpu type and / or have already gpu stuff in your dsdt.aml!) or edit for your system!

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted
Hint: In the settings.plist of all XPC are some settings you may delete (like DeviceProperties key injection, i believe thats an GPU - may confuse your system if you have other gpu type and / or have already gpu stuff in your dsdt.aml!) or edit for your system!

Good point mitch. However, I had no problems using GFX in my DSDT and keeping the default DeviceProperties in XPC's settings.plist, But I recently removed my GFX info from my Lion DSDT and now have it as a hex string in XPC's settings.plist/DeviceProperties. It works just great.

Link to comment
Share on other sites
Time2Retire
Time2Retire
Posted
Posted

I'll soon post something in the DSDT section of this forum that will explain what HPET change is required, but more importantly why – with a line by line description of the old/factory and new/replacement code. This way everybody can have a look at it, and verify what I write (wrote here). And it won 't stop with HPET.

 

Thing is that I have a lot of reading and gathering of information to do before this can happen (to rule out errors) but since I am also a professional field hockey player with five trainings sessions, two matches each week, and additional trainings sessions to give myself... next to following my college classes, this simply takes time. Not to mention that I can boot Lion on two Mac's so this is not exactly a top priority for me.

 

Here's one more clue: Look at AppleACPIPlatformExpert (version info) and wonder what changed. It's all there wide in the open, but you have to know where and what to look for it.

Link to comment
Share on other sites
geticus
geticus
Posted
Posted
XPC UEFI-Bootloader 0.82.33 | Build 05.04.2011 http://www.mediafire.com/?7zz5auzknab66nz

Hint: In the settings.plist of all XPC are some settings you may delete (like DeviceProperties key injection, i believe thats an GPU - may confuse your system if you have other gpu type and / or have already gpu stuff in your dsdt.aml!) or edit for your system!

 

Black screen here (with or without deleting DeviceProperties key injection) and reboot on sandy bridge MSI board.

Link to comment
Share on other sites
fredouille
fredouille
Posted
Posted
Good point mitch. However, I had no problems using GFX in my DSDT and keeping the default DeviceProperties in XPC's settings.plist, But I recently removed my GFX info from my Lion DSDT and now have it as a hex string in XPC's settings.plist/DeviceProperties. It works just great.

 

hello

can you post your setting plist so as i can compare because i can't make my gfx works please

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted

@DHP - thanks for the info posted earlier.

Am I getting warm if I look in to the ACPI Statistics?

 

@fredouille - Sure, here you go.

 

Note: I have zero'd the BiosVersion, SerialNumbers and PlatformUUID fields that I am using.

Also for anyone looking at using it, the ProcessorType, ProcessorBusSpeed and ScreenMode are set for my system so they will probably need changing for your own system.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
 <dict>

   <key>SmbiosTables</key>
   <dict>

     <key>Table</key>
     <dict>
       <key>Type</key>
       <integer>0</integer>
       <key>BiosVersion</key>
       <string>MP31.88Z.0000.000.0000000000</string>
       <key>BiosVendor</key>
       <string>Apple Inc.</string>
     </dict>

     <key>Table</key>
     <dict>
       <key>Type</key>
       <integer>1</integer>
       <key>Manufacturer</key>
       <string>Apple Inc.</string>
       <key>ProductName</key>
       <string>MacPro3,1</string>
       <key>Family</key>
       <string>Mac</string>
       <key>SerialNumber</key>
       <string>000000000000</string>
       <key>SKUNumber</key>
       <string>SKUNumber</string>
       <key>Version</key>
       <string>0.0</string>
     </dict>

     <key>Table</key>
     <dict>
       <key>Type</key>
       <integer>2</integer>
       <key>Manufacturer</key>
       <string>Apple Inc.</string>
       <key>ProductName</key>
       <string>Mac-F4208DC8</string>
       <key>AssetTag</key>
       <string>MacPro</string>
       <key>SerialNumber</key>
       <string>000000000000</string>
       <key>LocationInChassis</key>
       <string>None</string>
       <key>Version</key>
       <string>0.0</string>
       <key>BoardType</key>
       <integer>10</integer>
     </dict>

     <key>Table</key>
     <dict>
       <key>Type</key>
       <integer>3</integer>
       <key>Manufacturer</key>
       <string>Apple Inc.</string>
       <key>AssetTag</key>
       <string>MacBla</string>
       <key>SerialNumber</key>
       <string>123456789</string>
       <key>Version</key>
       <string>0.0</string>
       <key>ChassisType</key>
       <integer>3</integer>
     </dict>

     <key>Table</key>
     <dict>
       <key>Type</key>
       <integer>131</integer>
       <key>ProcessorType</key>
       <integer>301</integer>
     </dict>

     <key>Table</key>
     <dict>
       <key>Type</key>
       <integer>132</integer>
       <key>ProcessorBusSpeed</key>
       <integer>1064</integer>
     </dict>

    </dict>

  <key>FacpFix</key>
   <dict>
     <key>PMProfile</key>
     <string>0x01</string>
     <key>Flags</key>
     <string>0x400</string>
     <key>SpaceID</key>
     <string>0x01</string>
     <key>BitWidth</key>
     <string>0x08</string>
     <key>BitOffset</key>
     <string>0x00</string>
     <key>AccessWidth</key>
     <string>0x01</string>
     <key>Address</key>
     <string>0x0CF9</string>
     <key>Value</key>
     <string>0x06</string>
   </dict>

   <key>SSDTHandling</key>
   <dict>
     <key>RemoveSSDT</key>
     <integer>1</integer>
     <key>CreateCST2</key>
     <integer>1</integer>
     <key>CreateCST3</key>
     <integer>1</integer>
     <key>CreateCST4</key>
     <integer>1</integer>  	
  </dict>

   <key>OSXKernelSettings</key>
   <dict>
     <key>KernelName</key>
     <string>mach_kernel</string>
     <key>KernelFlags</key>
     <string>-v</string>
   </dict>

   <key>PlatformUUID</key>
   <dict>
     <key>Part1</key>
     <string>0x00000000</string>
     <key>Part2</key>
     <string>0x0000</string>
     <key>Part3</key>
     <string>0x0000</string>
     <key>Part4.1</key>
     <string>0x00</string>
     <key>Part4.2</key>
     <string>0x00</string>
     <key>Part4.3</key>
     <string>0x00</string>
     <key>Part4.4</key>
     <string>0x00</string>
     <key>Part4.5</key>
     <string>0x00</string>
     <key>Part4.6</key>
     <string>0x00</string>
     <key>Part4.7</key>
     <string>0x00</string>
     <key>Part4.8</key>
     <string>0x00</string>
   </dict>

   <key>ScreenMode</key>
   <integer>361</integer>

   <key>DeviceProperties</key>
   <string>6d0200000100000001000000610200000d00000002010c00d041030a010000000101060000010101060000007fff04002e000000400030002c004100410050004c002c0062006f006f0074002d0064006900730070006c00610079000000080000000100000020000000400030002c0063006f006d00700061007400690062006c00650000000f0000004e5644412c4e564d61630022000000400030002c006400650076006900630065005f00740079007000650000000c000000646973706c61790014000000400030002c006e0061006d0065000000130000004e5644412c446973706c61792d410020000000400031002c0063006f006d00700061007400690062006c00650000000f0000004e5644412c4e564d61630022000000400031002c006400650076006900630065005f00740079007000650000000c000000646973706c61790014000000400031002c006e0061006d0065000000130000004e5644412c446973706c61792d42001c0000006400650076006900630065005f0074007900700065000000100000004e5644412c506172656e7400220000004100410050004c002c0073006c006f0074002d006e0061006d00650000000a000000536c6f742d31100000004e00560043004100500000001800000004000000000003001c0000000000000a00000000220000005600520041004d002c0074006f00740061006c00730069007a00650000000800000000000020100000006d006f00640065006c000000140000004765466f7263652038383030204754001e00000072006f006d002d007200650076006900730069006f006e0000001300000036322e39322e32332e30302e303000</string>

   <key>DefaultBoot</key>
   <string>Acpi(PNP0A08,0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(4,GPT,3BAD5333-F6EA-4E7B-B8EF-59D2B962FAEB,0xE269EB0,0x94C2950)</string>

 </dict>
</plist>

Link to comment
Share on other sites
fredouille
fredouille
Posted
Posted
@DHP - thanks for the info posted earlier.

Am I getting warm if I look in to the ACPI Statistics?

 

@fredouille - Sure, here you go.

 

Note: I have zero'd the BiosVersion, SerialNumbers and PlatformUUID fields that I am using.

Also for anyone looking at using it, the ProcessorType, ProcessorBusSpeed and ScreenMode are set for my system so they will probably need changing for your own system.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
 <dict>

   <key>SmbiosTables</key>
   <dict>

     <key>Table</key>
     <dict>
       <key>Type</key>
       <integer>0</integer>
       <key>BiosVersion</key>
       <string>MP31.88Z.0000.000.0000000000</string>
       <key>BiosVendor</key>
       <string>Apple Inc.</string>
     </dict>

     <key>Table</key>
     <dict>
       <key>Type</key>
       <integer>1</integer>
       <key>Manufacturer</key>
       <string>Apple Inc.</string>
       <key>ProductName</key>
       <string>MacPro3,1</string>
       <key>Family</key>
       <string>Mac</string>
       <key>SerialNumber</key>
       <string>000000000000</string>
       <key>SKUNumber</key>
       <string>SKUNumber</string>
       <key>Version</key>
       <string>0.0</string>
     </dict>

     <key>Table</key>
     <dict>
       <key>Type</key>
       <integer>2</integer>
       <key>Manufacturer</key>
       <string>Apple Inc.</string>
       <key>ProductName</key>
       <string>Mac-F4208DC8</string>
       <key>AssetTag</key>
       <string>MacPro</string>
       <key>SerialNumber</key>
       <string>000000000000</string>
       <key>LocationInChassis</key>
       <string>None</string>
       <key>Version</key>
       <string>0.0</string>
       <key>BoardType</key>
       <integer>10</integer>
     </dict>

     <key>Table</key>
     <dict>
       <key>Type</key>
       <integer>3</integer>
       <key>Manufacturer</key>
       <string>Apple Inc.</string>
       <key>AssetTag</key>
       <string>MacBla</string>
       <key>SerialNumber</key>
       <string>123456789</string>
       <key>Version</key>
       <string>0.0</string>
       <key>ChassisType</key>
       <integer>3</integer>
     </dict>

     <key>Table</key>
     <dict>
       <key>Type</key>
       <integer>131</integer>
       <key>ProcessorType</key>
       <integer>301</integer>
     </dict>

     <key>Table</key>
     <dict>
       <key>Type</key>
       <integer>132</integer>
       <key>ProcessorBusSpeed</key>
       <integer>1064</integer>
     </dict>

    </dict>

  <key>FacpFix</key>
   <dict>
     <key>PMProfile</key>
     <string>0x01</string>
     <key>Flags</key>
     <string>0x400</string>
     <key>SpaceID</key>
     <string>0x01</string>
     <key>BitWidth</key>
     <string>0x08</string>
     <key>BitOffset</key>
     <string>0x00</string>
     <key>AccessWidth</key>
     <string>0x01</string>
     <key>Address</key>
     <string>0x0CF9</string>
     <key>Value</key>
     <string>0x06</string>
   </dict>

   <key>SSDTHandling</key>
   <dict>
     <key>RemoveSSDT</key>
     <integer>1</integer>
     <key>CreateCST2</key>
     <integer>1</integer>
     <key>CreateCST3</key>
     <integer>1</integer>
     <key>CreateCST4</key>
     <integer>1</integer>  	
  </dict>

   <key>OSXKernelSettings</key>
   <dict>
     <key>KernelName</key>
     <string>mach_kernel</string>
     <key>KernelFlags</key>
     <string>-v</string>
   </dict>

   <key>PlatformUUID</key>
   <dict>
     <key>Part1</key>
     <string>0x00000000</string>
     <key>Part2</key>
     <string>0x0000</string>
     <key>Part3</key>
     <string>0x0000</string>
     <key>Part4.1</key>
     <string>0x00</string>
     <key>Part4.2</key>
     <string>0x00</string>
     <key>Part4.3</key>
     <string>0x00</string>
     <key>Part4.4</key>
     <string>0x00</string>
     <key>Part4.5</key>
     <string>0x00</string>
     <key>Part4.6</key>
     <string>0x00</string>
     <key>Part4.7</key>
     <string>0x00</string>
     <key>Part4.8</key>
     <string>0x00</string>
   </dict>

   <key>ScreenMode</key>
   <integer>361</integer>

   <key>DeviceProperties</key>
   <string>6d0200000100000001000000610200000d00000002010c00d041030a010000000101060000010101060000007fff04002e000000400030002c004100410050004c002c0062006f006f0074002d0064006900730070006c00610079000000080000000100000020000000400030002c0063006f006d00700061007400690062006c00650000000f0000004e5644412c4e564d61630022000000400030002c006400650076006900630065005f00740079007000650000000c000000646973706c61790014000000400030002c006e0061006d0065000000130000004e5644412c446973706c61792d410020000000400031002c0063006f006d00700061007400690062006c00650000000f0000004e5644412c4e564d61630022000000400031002c006400650076006900630065005f00740079007000650000000c000000646973706c61790014000000400031002c006e0061006d0065000000130000004e5644412c446973706c61792d42001c0000006400650076006900630065005f0074007900700065000000100000004e5644412c506172656e7400220000004100410050004c002c0073006c006f0074002d006e0061006d00650000000a000000536c6f742d31100000004e00560043004100500000001800000004000000000003001c0000000000000a00000000220000005600520041004d002c0074006f00740061006c00730069007a00650000000800000000000020100000006d006f00640065006c000000140000004765466f7263652038383030204754001e00000072006f006d002d007200650076006900730069006f006e0000001300000036322e39322e32332e30302e303000</string>

   <key>DefaultBoot</key>
   <string>Acpi(PNP0A08,0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(4,GPT,3BAD5333-F6EA-4E7B-B8EF-59D2B962FAEB,0xE269EB0,0x94C2950)</string>

 </dict>
</plist>

 

thank you

EDIT : it doesn't work for me (8800GTX) I obtained hex with EFI Studio (save as hex ) and add it in deviceproperty

in the setting plist !

I tried also almost all injectors (NVInject, NVEnabler 32 & 64, Natit)

add it in DSDT , add dev_id in NVDANV50Hak.kext with no luck :)

Worth is all those method works great with leo & Snowleo !

Link to comment
Share on other sites
fredouille
fredouille
Posted
Posted
I took the device properties directly from ioreg from within SL with my machine booted from Chameleon and using GraphicsEnabler.

 

thanks for the info ( i noticed that hex is different from the one of EFIStudio)

I've followed your method but still no luck ( well it's properly recognized but believe QE/CI don't work because VLC, DVD player crash !)

post-93689-1302283524_thumb.png

Link to comment
Share on other sites
YoMuS
YoMuS
Posted
Posted

Hi!

 

Why do I get this screen right before the desktop appears? (In 11a419 only)

 

post-12287-1302285296_thumb.jpg

 

It happens using either Natit, NVEnabler, ATY_init, dsdt injection, efi string...

 

My graphics card is a gtx260 which is working perfectly under SL and Lion DP1. Anybody has a clue?

 

Thanks

Link to comment
Share on other sites
blackosx
blackosx
Posted
Posted
well it's properly recognized but believe QE/CI don't work because VLC, DVD player crash !

That looks like it's recognised correctly. I'm guessing CI is working because you have managed to take a screenshot. Do you see the water ripples when dragging widgets on to the dashboard (make sure 'Show Dashboard as a space' is unchecked in System Prefs/Exposé & Spaces).

 

I don't know why DVD player and VLC aren't working for you as both are working fine here.

Link to comment
Share on other sites
kocoman
kocoman
Posted
Posted

There seems to be a 450 post limit on "Printed version" of threads in the invision boards.

So its hard to search the posts.

 

I tried both [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] (1.5a) and XPC (82.33) on MSI p6n2 mb, but only gets "BStart rt" then blank screen.

 

---

here is my result.. if anyone understands it

 

MD5 (DuetToHdd) = bcddeed0b013f82635767808cc35e0fc

-----

 

xpc modded hdd (or no parameter in DuettoHDD) - gets Bstart rt! then black screen (LCD inverter lamp still at full, press all keys, no response)

 

MD5 (Efildr20) = c00d5077ed32bec945de53fe6f5f0c7d

 

xpc modded USB - gets Berr rt! - stuck there

MD5 (Efildr20) = abeb48da7a1e6cf16b1d98f73b45faf9

 

 

xpc original

MD5 (Efildr20) = f360a2278ddef04e785218ae3b3d114e

 

 

-------

 

[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] 1.5a mooded AND original!!

MD5 (Efildr20) = 8164f6e3b6b4cf972546edd50a2d9c5c

 

 

[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] patch with HDD (no parameter) - Bstart, then black screen with LCD inverter still at full

MD5 (Efildr20) = 2123f531c42a636b19b476c3c55e1e4c

 

(arrgh, textedit autocorrects [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] into boot) [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] patch with usb - Berr rt!

MD5 (Efildr20) = 1acc97b2c5d60a9f16965fc1afd01fe7

 

---

 

It seems that Duet bootloader only with with MBR, while SL and Lion needs GUID to install. It seems to be going backwards with MBR..

 

anyway might need another MB.

 

Is there a wiki of working MBs for Lion? it seems all info is scattered all over the place..

Link to comment
Share on other sites
atlee
atlee
Posted
Posted
XPC loads a modified DSDT, allows SMBIOS overrides and EFI device property injection. It patches the FADT for restart and I think can now even load kexts from an /Extra/Extensions.mkext. All that and other tricks... It's my default bootloader for Lion for now.

 

I'm pretty sure i had USB issues with all XPC flavours just stuck on waiting for root, could not initialize the USB's at the start, will give it another try can't hurt :)

 

yeah XPC never has work just tryed it and all USB ports don't boot just sits there waiting for boot device, wonder what the diff between XPC and [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] with taking control of USB ports?

 

Is there a USB trick like Chamelon built into this would be awsome to see how well XPC makes Lion boot and recognise stuff when it reaches desktop.

Link to comment
Share on other sites
tdtran1025
tdtran1025
Posted
Posted
There seems to be a 450 post limit on "Printed version" of threads in the invision boards.

So its hard to search the posts.

 

I tried both [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] (1.5a) and XPC (82.33) on MSI p6n2 mb, but only gets "BStart rt" then blank screen.

 

---

here is my result.. if anyone understands it

 

MD5 (DuetToHdd) = bcddeed0b013f82635767808cc35e0fc

-----

 

xpc modded hdd (or no parameter in DuettoHDD) - gets Bstart rt! then black screen (LCD inverter lamp still at full, press all keys, no response)

 

MD5 (Efildr20) = c00d5077ed32bec945de53fe6f5f0c7d

 

xpc modded USB - gets Berr rt! - stuck there

MD5 (Efildr20) = abeb48da7a1e6cf16b1d98f73b45faf9

 

 

xpc original

MD5 (Efildr20) = f360a2278ddef04e785218ae3b3d114e

 

 

-------

 

[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] 1.5a mooded AND original!!

MD5 (Efildr20) = 8164f6e3b6b4cf972546edd50a2d9c5c

 

 

[url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] patch with HDD (no parameter) - Bstart, then black screen with LCD inverter still at full

MD5 (Efildr20) = 2123f531c42a636b19b476c3c55e1e4c

 

(arrgh, textedit autocorrects [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] into boot) [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] patch with usb - Berr rt!

MD5 (Efildr20) = 1acc97b2c5d60a9f16965fc1afd01fe7

 

---

 

It seems that Duet bootloader only with with MBR, while SL and Lion needs GUID to install. It seems to be going backwards with MBR..

 

anyway might need another MB.

 

Is there a wiki of working MBs for Lion? it seems all info is scattered all over the place..

 

Not done properly. Try XPC .0.82.33, It has OS X formatter, making it the job a lot less cumbersome.

loader: http://www.mediafire.com/?7zz5auzknab66nz

USB stick setup: attached file

XPC_Boot_Prepare_Tool.zip

Link to comment
Share on other sites
kocoman
kocoman
Posted
Posted
Not done properly. Try XPC .0.82.33, It has OS X formatter, making it the job a lot less cumbersome.

loader: http://www.mediafire.com/?7zz5auzknab66nz

USB stick setup: attached file

 

I did try 0.82.33 before, I got the link from the irc room at moofspeak uefi-channel, same goes for [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url]..

 

I could not find a "OS X formatter" in the XPC package, the one linked by you is "Made by caine for applelife.ru users. http://caine.in"

 

The md5 stuff came from the DuetToHDD app

 

I tried the one "Made by caine for applelife.ru users. http://caine.in" (also attached by your post), and it only says "MBR start" then same blank screen.

 

I disabled serial port.. but still same..

 

I tried Netkas RC3 patched, but got double panic with "can't preform kext scan" (on the Base Install Image)

 

using C2D E6400

 

I wish there was some debug version with more output ?

 

thanks

 

EDIT: I am looking at this file,

 

http://www.projectosx.com/forum/index.php?...ost&p=13091

 

It boots in text to say "ABCE

 

"welcome to efi world"

 

we'll see what I can do with that

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