Print

[monkey]

The update has been released.  Anyobody have the courage to try it?
Post the results.

[LonelyTV]

The update has been released.  Anyobody have the courage to try it?
Post the results.

We have to wait for iDeneb to release a 10.5.7 update patch for their distro. Unless you've installed the retail version of Os X using the Boot-132 method then you could update using Apple's Software Update. 

[rcfa]

I have 10.5.7 running on my EeePC 1000HE.
Things actually work better with 10.5.7, no more need for the cpus=1 option, the OS now recognizes a single CPU with hyperthreading, CHUD's CPU preference pane shows the CPU as "Intel Ultra Mobile Processor" and allows selective enabling/disabling of hyperthreading.

Only the new GMA950 related plugin and bundles need to be rescued over from 10.5.6, because the new ones don't properly jive with the hacked GMA950 and AppleIntelIntegratedFramebuffer kexts that are needed for the video resolution to be properly recognized.

Otherwise, 10.5.7 requires the same additional kexts and same kext overrides as 10.5.6.

An I'm not running iDeneb or something like this, but an almost vanilla install with Chameleon 2.0RC1 on an HFS+ formatted EFI partition on a GUID formatted drive.
Dual booting into WinXP also works. What didn't work was transferring the original WinXP with WinClone. So I had to install WinXP from scratch for reasons that are beyond me.

[monkey]

Did you have to patch your dsdt to be able to remove the cpus=1 flag?

[evilscientist]

I have 10.5.7 running on my EeePC 1000HE.
Things actually work better with 10.5.7, no more need for the cpus=1 option, the OS now recognizes a single CPU with hyperthreading, CHUD's CPU preference pane shows the CPU as "Intel Ultra Mobile Processor" and allows selective enabling/disabling of hyperthreading.

Only the new GMA950 related plugin and bundles need to be rescued over from 10.5.6, because the new ones don't properly jive with the hacked GMA950 and AppleIntelIntegratedFramebuffer kexts that are needed for the video resolution to be properly recognized.

Otherwise, 10.5.7 requires the same additional kexts and same kext overrides as 10.5.6.

An I'm not running iDeneb or something like this, but an almost vanilla install with Chameleon 2.0RC1 on an HFS+ formatted EFI partition on a GUID formatted drive.
Dual booting into WinXP also works. What didn't work was transferring the original WinXP with WinClone. So I had to install WinXP from scratch for reasons that are beyond me.

Whoa, whoa, whoa. You've done an almost *vanilla* install? *PLEASE* share the steps for this!!!!!!

[Troklo]

I have 10.5.7 running on my EeePC 1000HE.
Things actually work better with 10.5.7, no more need for the cpus=1 option, the OS now recognizes a single CPU with hyperthreading, CHUD's CPU preference pane shows the CPU as "Intel Ultra Mobile Processor" and allows selective enabling/disabling of hyperthreading.

Only the new GMA950 related plugin and bundles need to be rescued over from 10.5.6, because the new ones don't properly jive with the hacked GMA950 and AppleIntelIntegratedFramebuffer kexts that are needed for the video resolution to be properly recognized.

Otherwise, 10.5.7 requires the same additional kexts and same kext overrides as 10.5.6.

An I'm not running iDeneb or something like this, but an almost vanilla install with Chameleon 2.0RC1 on an HFS+ formatted EFI partition on a GUID formatted drive.
Dual booting into WinXP also works. What didn't work was transferring the original WinXP with WinClone. So I had to install WinXP from scratch for reasons that are beyond me.

Dang dude really?!?!?!?!

Please share the steps on how you did this!

[scn]

Just thought I'd chime in that running the standard Apple update to 10.5.7 (downloaded package, that is) on an iDeneb 1.4 installation worked fine. I have some graphic issues and I think I lost sound, but both should be reparable with proper kexts.

Edit: sound is fine, but I'm not sure about video. I dumped the GMA950 kext and then OS X booted normally (was having major graphical corruption prior). I left the natit.kext and AppleIntegratedFrameBuffer installed and it appears fine.

Note: this is all being done on a Samsung N120.

[LonelyTV]

Just thought I'd chime in that running the standard Apple update to 10.5.7 (downloaded package, that is) on an iDeneb 1.4 installation worked fine. I have some graphic issues and I think I lost sound, but both should be reparable with proper kexts.

Edit: sound is fine, but I'm not sure about video. I dumped the GMA950 kext and then OS X booted normally (was having major graphical corruption prior). I left the natit.kext and AppleIntegratedFrameBuffer installed and it appears fine.

Note: this is all being done on a Samsung N120.

Try installing the 10.5.6 GMA950 Kext and you should be fine. It appears the 10.5.7 GMA950 breaks the graphics on non-apple computers.

[rcfa]

Just thought I'd chime in that running the standard Apple update to 10.5.7 (downloaded package, that is) on an iDeneb 1.4 installation worked fine. I have some graphic issues and I think I lost sound, but both should be reparable with proper kexts.

Edit: sound is fine, but I'm not sure about video. I dumped the GMA950 kext and then OS X booted normally (was having major graphical corruption prior). I left the natit.kext and AppleIntegratedFrameBuffer installed and it appears fine.

Note: this is all being done on a Samsung N120.

Try installing the 10.5.6 GMA950 Kext and you should be fine. It appears the 10.5.7 GMA950 breaks the graphics on non-apple computers.

Are you talking about the actual .kext? I never was able to use the 10.5.6 ones as they are. However, if you are talking about the related .bundle and .plugin files from 10.5.6 in the /System/Library/Extensions folder, and whatever hacked .kexts you used to use with 10.5.6, then you're spot on (i.e. matching my findings).

As for people who want (some) more information about the vanilla install, please check out my (incomplete) response the thread titled "OS X Retail Installation" here: http://smallcomputing.net/forums/index.php/topic,17.0.html

I'll track that topic over there, best I can...

[rcfa]

Did you have to patch your dsdt to be able to remove the cpus=1 flag?

The whole dsdt stuff right now to me is black magic. I wish someone would write up something that makes this understandable. I used once some tool that produced some sort of .aml file which I stuck somewhere in my EFI partition, but it didn't seem to make any difference that I could tell.

The cpus=1 issue just seemed to have gone away with 10.5.7. I think Apple is at least working internally on something that uses Atom CPUs, be that for real product development, or just proof of concept work, or for a new AppleTV, because CHUD's Processor reference pane now also reports the Atom as "Intel Ultra Mobile CPU", and it recognizes that it's a single-core CPU with hyperthreading, and that is AFAIK also new since 10.5.7.

[scn]

Are you talking about the actual .kext? I never was able to use the 10.5.6 ones as they are. However, if you are talking about the related .bundle and .plugin files from 10.5.6 in the /System/Library/Extensions folder, and whatever hacked .kexts you used to use with 10.5.6, then you're spot on (i.e. matching my findings).

As for people who want (some) more information about the vanilla install, please check out my (incomplete) response the thread titled "OS X Retail Installation" here: http://smallcomputing.net/forums/index.php/topic,17.0.html

I'll track that topic over there, best I can...

I'm referring specifically to the .kext file (the AppleIntelGMA950.kext folder (I'm going on memory, so if it's not named exactly that, it's close) that it's in the extensions directory, to be more explicit). I'm not sure if the one I used on the Samsung was from 10.5.5 or 10.5.6 or what the actual differences are, but it definitely corrupted the video when I installed it after the 10.5.7 update. However, with the natit.kext and the appleintegratedframebuffer.kext, my video appears fine and is running at the native resolution. Performance may actually suffer, but in appearance, it looks fine.

As noted, everything else that worked prior to the 10.5.7 update appears to still work.

Also, thanks for the vanilla guide. I think a few of us have been looking for a vanilla option.

[rcfa]

Are you talking about the actual .kext? I never was able to use the 10.5.6 ones as they are. However, if you are talking about the related .bundle and .plugin files from 10.5.6 in the /System/Library/Extensions folder, and whatever hacked .kexts you used to use with 10.5.6, then you're spot on (i.e. matching my findings).

As for people who want (some) more information about the vanilla install, please check out my (incomplete) response the thread titled "OS X Retail Installation" here: http://smallcomputing.net/forums/index.php/topic,17.0.html

I'll track that topic over there, best I can...

I'm referring specifically to the .kext file (the AppleIntelGMA950.kext folder (I'm going on memory, so if it's not named exactly that, it's close) that it's in the extensions directory, to be more explicit). I'm not sure if the one I used on the Samsung was from 10.5.5 or 10.5.6 or what the actual differences are, but it definitely corrupted the video when I installed it after the 10.5.7 update. However, with the natit.kext and the appleintegratedframebuffer.kext, my video appears fine and is running at the native resolution. Performance may actually suffer, but in appearance, it looks fine.

As noted, everything else that worked prior to the 10.5.7 update appears to still work.

Also, thanks for the vanilla guide. I think a few of us have been looking for a vanilla option.

Use whatever AppleIntelGMA950.kext worked with 10.5.6. Then in addition, you have to REPLACE anything in /System/Library/Extensions that has 950 in its name with the corresponding files in the 10.5.6 version of the OS. I think it's two .bundle file bundles, and one .plugin file bundle. I also used the 10.5.6 version of the AppleIntelIntegratedFramebuffer.kext, but maybe the 10.5.7 would work, too.

In any case, if you use just the 10.5.7 version of the AppleIntelIntegradedFramebuffer.kext you will not be able to use anything that requires QuartzExtreme or hardware supported OpenGL.

With the changes I outlined above, you're back to 10.5.6 video performance.

Ronald

[rcfa]

Did you have to patch your dsdt to be able to remove the cpus=1 flag?

The whole dsdt stuff right now to me is black magic. I wish someone would write up something that makes this understandable. I used once some tool that produced some sort of .aml file which I stuck somewhere in my EFI partition, but it didn't seem to make any difference that I could tell.

The cpus=1 issue just seemed to have gone away with 10.5.7. I think Apple is at least working internally on something that uses Atom CPUs, be that for real product development, or just proof of concept work, or for a new AppleTV, because CHUD's Processor reference pane now also reports the Atom as "Intel Ultra Mobile CPU", and it recognizes that it's a single-core CPU with hyperthreading, and that is AFAIK also new since 10.5.7.

OK, to avoid trouble for others: I was inadvertently giving false information here.
It turns out that while playing around with the DSDTPatcher.app I must have once accidentally have hit the "apply to ..." option, so it did install the dsdt.aml onto my root partition without me noticing it.

So yes, you DO need a dsdt.aml in order to get rid of the cpus=1 thing. At least with the 0802 firmware.