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

asapreta
asapreta
Posted
Posted
For me, went on smoothly and seems best optimized to date.

 

I had the same feeling and it fixed some issues I has having with ANY msn clients I tried.

Link to comment
Share on other sites
Rene204
Rene204
Posted
Posted
is there any way to get it to update to 459 without having one previous installed? it always hanged on me on 444 and i have 430 working extremely well.

using p35-d3sl, q9300 and 9800gt

 

you should have a look to www.netkas.org, too...

Link to comment
Share on other sites
bcc9
bcc9
Posted
Posted
Anyway. Looking at the mach_kernel of Lion I see this:

Where WESTMERE, NEHALEM, and SANDYBRIDGE all jump to the same spot reading the MSR that caused you problems.

That's exactly what I noted in my first FLEX_RATIO post. Patching that code was how I found that this MSR mishandling was the root cause of my mach_kernel failing to boot.
And since Apple is Intels biggest client, and since Apple has Intel engineers working for them... I'd say that it is safe to assume that MSR 0x194 is part of what should work. Not to mention that more MSR's are missing from the docs/white papers, and that Asus engineers cite NDA restrictions when people do ask for info about them.
I'd say no, it's definitely *not* safe to assume undocumented fields are guaranteed to be set the way apple's code happens to be testing them, when using non-apple hardware. Relying upon undocumented hardware behavior is not good practice. If intel has registers whose semantics are only shared under NDA with a few vendors (and not the linux folks for example), then there isn't really anything concrete to complain to the bios vendors about.

 

I do however think that having the osx bootloader clear bit 16 of that MSR when bits 8 thru 15 come up 0 is a very reasonable fix. Works for me . If anyone else needs a chameleon boot file with this fix let me know.

 

I have found a few FLEX_RATIO references in intel's documents but nothing that details the semantics.

Link to comment
Share on other sites
Time2Retire
Time2Retire
Posted
Posted
I'd say no, it's definitely *not* safe to assume undocumented fields are guaranteed to be set the way apple's code happens to be testing them, when using non-apple hardware. Relying upon undocumented hardware behavior is not good practice. If intel has registers whose semantics are only shared under NDA with a few vendors (and not the linux folks for example), then there isn't really anything concrete to complain to the bios vendors about.

Nothing is absolutely safe, but it isn't limited to Apple alone since Asus UEFI initializes this MSR with the correct values. And you can't do anything wrong when you port the values from one to the other MSR. At least that's what I've read in the datasheet.

 

Anyway. Most of the interesting MSR's are only slowly being added in non-NDA covered Intel documentation. I mean not much was given away in the beginning of the Sandy Bridge CPU launch. Same for JakeTown CPU's This sucks for us, but that is how things seem to work at Intel..

 

I do however think that having the osx bootloader clear bit 16 of that MSR when bits 8 thru 15 come up 0 is a very reasonable fix. Works for me . If anyone else needs a chameleon boot file with this fix let me know.

Oh sure. It is great that you located the problem and found a work around for your boot problem, but have you ruled out all other possible readouts from this specific MSR? I don't think so.

 

I have found a few FLEX_RATIO references in intel's documents but nothing that details the semantics.

Search for: "CLOCK_FLEX_MAX" instead and find this (for example):

 

"The processor’s maximum non-turbo core frequency is configured during power-on reset by using values stored internally during manufacturing. The stored value sets the highest core multiplier at which the particular processor can operate. If lower max non- turbo speeds are desired, the appropriate ratio can be configured using the CLOCK_FLEX_MAX MSR."

Not much of a give away, but that is what I can do for now ;)

Link to comment
Share on other sites
oSxFr33k
oSxFr33k
Posted
Posted
The final will in general have the same requirements for chameleon. Offical (RC5 based) will not work - but until the release i think there will be at least some beta chamelon (one step further the very early chameleon lion bird now)

Also for NVIDIA: working will work, non working not - i dont think they will add officeal fermi support for example.

 

 

Thanks for the reply and sorry for the late response. If the Nvidia cards I have are all working in Snow Leopard mostly because of Chameleon will they also work in Lion thats the question.

Link to comment
Share on other sites
bcc9
bcc9
Posted
Posted
Oh sure. It is great that you located the problem and found a work around for your boot problem, but have you ruled out all other possible readouts from this specific MSR? I don't think so.
I identified a thorny interop problem between OSX and certain gigabyte h67 motherboard(s).

I found two different fixes, and detailed them here. They are the only working solutions for the h67ma-ud2h at this point.

I don't know why you keep posting inflammatory responses, but you are not helping here in any way, in fact you're just costing me extra time clarifying things to you.

 

I see you have a history of bad attitude posts earlier in this thread so I'm not taking it personally. But I wish you'd at least show some respect or maybe get your posts moderated by a mature adult.

Link to comment
Share on other sites
Time2Retire
Time2Retire
Posted
Posted
I identified a thorny interop problem between OSX and certain gigabyte h67 motherboard(s).

I found two different fixes, and detailed them here. They are the only working solutions for the h67ma-ud2h at this point.

I don't know why you keep posting inflammatory responses, but you are not helping here in any way, in fact you're just costing me extra time clarifying things to you.

 

I see you have a history of bad attitude posts earlier in this thread so I'm not taking it personally. But I wish you'd at least show some respect or maybe get your posts moderated by a mature adult.

What inflammatory responses? What bad attitude or lack of respect are you talking about? That's nonsense man. You simply cannot accept that a 15 year old girl is smarter than you, because hell yes did you forgot something. And now I should be moderated, because you can't handle it? Pfffft.

Link to comment
Share on other sites
digital_dreamer
digital_dreamer
Posted
Posted

Anyone know what's up with the Memory display for System Information on the latest release (11A459e), or is this some silly goof on my part?

I've used smbios.plist injected info and, then, Cham RC5 r800 with the info removed from smbios.plist.

 

RAM_11A459e.png

 

Bootloader messages show that it's being recognized (semi-accurately) as the following:

Slot: 0 Type 24 2048MB (DDR3 SDRAM) 1333MHz Vendor=Corsair
	 PartNo=CM3X2G1600C9 SerialNo=00000000
  Slot: 2 Type 24 2048MB (DDR3 SDRAM) 1333MHz Vendor=Corsair
	 PartNo=CM3X2G1600C9 SerialNo=00000000
  Slot: 4 Type 24 2048MB (DDR3 SDRAM) 1333MHz Vendor=Corsair
	 PartNo=CM3X2G1600C9 SerialNo=00000000

 

and:

MemoryDevice:
   deviceLocator: A0
   bankLocator: Bank0/1
   memoryType: DDR3
   memorySpeed: 1600MHz
   manufacturer: Corsair
   serialNumber: 00000000
   assetTag: 
   partNumber: 

  Type: 17, Length: 27, Handle: 0x19

etc.

 

Is Apple expecting us to populate the other fields, now, before showing anything?

 

MAJ

Link to comment
Share on other sites
miliuco
miliuco
Posted
Posted
Anyone know what's up with the Memory display for System Information on the latest release (11A459e), or is this some silly goof on my part?

 

Same issue here in a system installed following your hackinstaller guide, with Chameleon r796.

Link to comment
Share on other sites
Rene204
Rene204
Posted
Posted
Any ALC888 kexts for DP2 or DP3?

 

Using here the GA-P55-USB3 (rev.1), seems that is an ALC888,

solution for me is using the [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] HDA Rollback (HDA-kext from 10..6.2) this works here without any Problems...

(in combination with ALC8xxHDA.kext, HDAEnabler888.kext, both from [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url]-Installer too.)

 

Try out..

Link to comment
Share on other sites
Goron
Goron
Posted
Posted
Using here the GA-P55-USB3 (rev.1), seems that is an ALC888,

solution for me is using the [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] HDA Rollback (HDA-kext from 10..6.2) this works here without any Problems...

(in combination with ALC8xxHDA.kext, HDAEnabler888.kext, both from [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url]-Installer too.)

 

Try out..

 

Has anyone managed to get sound output on AD1988B? It shows up systemprofiler, but no device is found within system preferences ... using SL dsdt and AD2000B.kext ...

 

Currently i´m running DP3 (11A459e), but it didn´t work in any predecessor either :P

Link to comment
Share on other sites
Aivarz
Aivarz
Posted
Posted

For AD1988B.

With this in DSDT:

            Device (HDEF)
           {
               Name (_ADR, 0x001B0000)
               Method (_DSM, 4, NotSerialized)
               {
                   Store (Package (0x08)
                       {
                           "subsystem-id", 
                           Buffer (0x04)
                           {
                               0xA0, 0x00, 0x00, 0x00
                           }, 
                           "subsystem-vendor-id", 
                           Buffer (0x04)
                           {
                               0x6B, 0x10, 0x00, 0x00
                           }, 
                           "layout-id", 
                           Buffer (0x04)
                           {
                               0x0C, 0x00, 0x00, 0x00
                           }, 
                           "PinConfigurations", 
                           Buffer (Zero) {}
                       }, Local0)
                   DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                   Return (Local0)
               }
           }

Link to comment
Share on other sites
DarwinX
DarwinX
Posted
Posted
What inflammatory responses? What bad attitude or lack of respect are you talking about? That's nonsense man. You simply cannot accept that a 15 year old girl is smarter than you, because hell yes did you forgot something. And now I should be moderated, because you can't handle it? Pfffft.

 

You are indeed quite ingenious when it comes to coding, perhaps better than most on this forum, which is very impressive especially considering your very young age. Certainly, your contribution is significant and appreciated; what's questionable is the manner in which it's delivered. While your demeanor is quite expected of a 15 year old, it is unprofessional and dismissive of other corroborators. Having said that, I disagree with the remark that you are to be moderated as this is not a dictatorship or a blog. Such extremes are better reserved for profanity, spam or personal verbal attacks on other members of the board.

 

Please remember that we are all here in the pursuit of the mutual cause. :)

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