[lugesm]

As I understand the work-around, this creates an operating system at 10.6.2 level, but running with the kernel from 10.6.1.

Unless Apple moved to the new kernel for the SOLE PURPOSE of defeating ATOM installs, there must be some downside to running in this mode (OSX 10.6.2 w/10.6.1 kernel).

Am I missing something?

[shines on]

Originally Posted by michaelrw11

I followed this procedure after I updated to 10.6.2. I removed the HD from the 10v and installed it in an external drive case. I then connected the drive via USB to my MAC MINI running 10.6.1 and copied the mach_kernel over to the mini 10v HD root. Now when I reinstall the mini 10v drive I get "boot:0 done" after the bios loads. I am running A06 bios. any thoughts? Thanks in advance this is a great site with lots of great info.

mrw

Boot from your snow leopard dvd/usb on your mini, open the terminal and copy /mach_kernel to /Volumes/<mini's partition>/mach_kernel

The method you used was meant for a working backup of your mini's partition.

[Akki]

So seems we can copy aside the 6.0.1 kernel, upgrade and then restore. That gets us all the 6.0.2 framework updates but leaves us with a kernel/framework mismatch.

My 6.0.1 is very well behaved so I'll probably pass.

For me the question that remains is will it ever be worth considering upgrade again if it's no longer just faking out EFI and patching a few device drivers?

[Crisu]

I think the workaround just replacing the mach_kernel is only a temporally solution.

I would be better if we could work with a 10.6.2 kernel - this would be a real working 10.6.2 system.
So I think the kernel has to be modified.

Because the kernel of 10.6 is NOT perfect:

Kernel
CVE-ID: CVE-2009-2835
Available for: Mac OS X v10.6 and v10.6.1,
Mac OS X Server v10.6 and v10.6.1
Impact: A local user may cause information disclosure, an unexpected
system shutdown, or arbitrary code execution
Description: Multiple input validation issues exist in Kernel's
handling of task state segments. These may allow a local user to
cause information disclosure, an unexpected system shutdown, or
arbitrary code execution. This update addresses the issues through
improved input validation. Credit to Regis Duchesne of VMware, Inc.
for reporting this issue.

http://support.apple.com/kb/HT3937

So it would be better we can use a modified 10.6.2 kernel.

Otherwise I am thinking about restoring my system to 10.5.8 - this was much more solid than 10.6.x.

[michaelrw11]

Originally Posted by shines on

Boot from your snow leopard dvd/usb on your mini, open the terminal and copy /mach_kernel to /Volumes/<mini's partition>/mach_kernel

The method you used was meant for a working backup of your mini's partition.

Thanks shines on. I gave this a try and still have the same issue. Any other thoughts?

[ninvin21]

I need a Guide for Dummies on how to Fix this!
I've tried the commands Don't know what I'm doing wrong.

Please make a guide for noobs My system is stuck in the restart loop.

Help Please

I would reinstall but I have so much software installed It would take me days to get it back where I am.

[whipstitch]

Originally Posted by MiniEcto1

Originally Posted by whipstitch
Would installing the VoodooPowerMini kext also solve this problem?

Ooh, what's that?Ooh, what's that?

VoodooPowerMini is an alternative kernal that I'm using. It allows OSX to use speedstep so the processor is not running at fullspeed all the time which should extend battery life and make the system run less hot. If you search the OSX forums for speedstep you'll find out more.

I'm guessing that uipdating the kernal with the VoodooPowerMini after updating to 6.2 but before rebooting will allow me to update to 6.2 and avoid the reboot loop problem. Not sure though. I need to back up my system before trying this.

[Akki]

Originally Posted by ninvin21

I need a Guide for Dummies on how to Fix this!
I've tried the commands Don't know what I'm doing wrong.

Please make a guide for noobs My system is stuck in the restart loop.

Help Please

I would reinstall but I have so much software installed It would take me days to get it back where I am.

Why would you try the upgrade knowing it might kill your machine?!

YouTube- Gun Firecracker Prank *LMAO*

YouTube- Gun Firecracker Prank *LMAO*

How did you originally build your Hackintosh? You'll need to get the machine booted from a 10.6.x source to copy over a working kernel.

[shines on]

Originally Posted by michaelrw11

Thanks shines on. I gave this a try and still have the same issue. Any other thoughts?

If the above didn't work, and you performed the actions correctly, you must be having some other problem. What did you use to install osx on the mini originally? A usb drive made with netbook boot maker? If so, boot from the usb drive into the installer again and run netbook installer from the utilities menu. Point it at the mini's partition and make sure 'install bootloader' is checked as well as 'generate system specific dsdt.aml'.

If some other installation media was used, I'd slave the drive on your mac again and try running netbook installer from there pointed at the mini's partition. MAKE SURE 'GENERATE SYSTEM SPECIFIC DSDT.AML' IS UNCHECKED.

If that doesn't work than I'm out of ideas, perhaps someone else can help you.

Originally Posted by whipstitch

VoodooPowerMini is an alternative kernal that I'm using. It allows OSX to use speedstep so the processor is not running at fullspeed all the time which should extend battery life and make the system run less hot. If you search the OSX forums for speedstep you'll find out more.

I'm guessing that uipdating the kernal with the VoodooPowerMini after updating to 6.2 but before rebooting will allow me to update to 6.2 and avoid the reboot loop problem. Not sure though. I need to back up my system before trying this.

Voodoopowermini.kext is not a kernel. It is a kernel extension. It gets loaded by the main system kernel to provide speed stepping on non-mac hardware. Using it will have no effect on 10.6.2 problems.

[preel]

Has anyone confirmed that this was put out w/ the express intention of stopping the support of Atom processors?

Is it possible that some feature was added to the kernal that broke this for us?