10.5.1 update issue and workaround

[satan_himself]

I've run into an issue while updating my 10.5 installation to 10.5.1 and thought I might share a workaround in case anybody else runs into the same problem.

 

I'm running Leopard on an Asus A6JC laptop (Core 2 Duo) using pc_efi and unmodified kernel. 10.5 installed without issues.

However, after installing the 10.5.1 update and rebooting, the system would freeze after displaying "Jettisoning Kernel Linker" in verbose mode. (I have a hunch that some post install script tried to execute an encrypted binary and dsmos.kext wasn't loaded yet. I haven't verified this in any way though.)

 

Anyway, the solution is to boot into single user mode and replace the kernel with a patched ToH kernel, just for the first boot after the uptade. After the system boots successfully, I was able to restore the unmodified kernel and am running it now.

 

In other words:

put kernel_toh into your root directory

apply the 10.5.1 update

after reboot, press f8, and boot the system with the -s argument

now type:

 

mount -uw /
mv mach_kernel mach_kernel.plain
mv mach_toh mach_kernel
chmod 644 mach_kernel
chown root:wheel mach_kernel
reboot

 

The system should reboot normally. Now you can restore the unmodified binary, i.e. type in the terminal:

sudo mv mach_kernel.plain mach_kernel
sudo chown root:wheel mach_kernel

 

and do a permission repair using Disk Utility just in case.

[steLee]

yeah!

 

Earlier last week i called it my dirty updater on the IRC channell with a secret name lol (ok the netkas forum).

 

There are no ill side effects and on a Quad Core setup this 10.5.1 update blazes along quite kinkly fast seriously worth the update

 

Take note repairing permissions after the update will take AT LEAST 20 minutes...

[josh256]

"Take note repairing permissions after the update will take AT LEAST 20 minutes..."

 

That's not normal (I've updated a handful of mobo/chipsets to 10.5.1). You may want to check your console for [ongoing] errors..

[acdbox]

I think I've found the right people to help me in my hour (Hours!) of need.

 

Installed TOH RC2 10.5, and everything worked fine.

I then updated to 10.5.1 and everything started to look hairy, very hairy.

Basically as soon as leopard starts to load it reboots. Common problem from what I undertsand.

 

I havent copied any kernels into my root directory prior to installing the update, as I have only just read this post.

 

Now keeping in mind im a newbie please tell me someone has the power and knowledge to help me????

[more or less]

I've run into an issue while updating my 10.5 installation to 10.5.1 and thought I might share a workaround in case anybody else runs into the same problem.

 

I'm running Leopard on an Asus A6JC laptop (Core 2 Duo) using pc_efi and unmodified kernel. 10.5 installed without issues.

However, after installing the 10.5.1 update and rebooting, the system would freeze after displaying "Jettisoning Kernel Linker" in verbose mode. (I have a hunch that some post install script tried to execute an encrypted binary and dsmos.kext wasn't loaded yet. I haven't verified this in any way though.)

 

Anyway, the solution is to boot into single user mode and replace the kernel with a patched ToH kernel, just for the first boot after the uptade. After the system boots successfully, I was able to restore the unmodified kernel and am running it now.

 

In other words:

put kernel_toh into your root directory

apply the 10.5.1 update

after reboot, press f8, and boot the system with the -s argument

now type:

 

mount -uw /
mv mach_kernel mach_kernel.plain
mv mach_toh mach_kernel
chmod 644 mach_kernel
chown root:wheel mach_kernel
reboot

 

The system should reboot normally. Now you can restore the unmodified binary, i.e. type in the terminal:

sudo mv mach_kernel.plain mach_kernel
sudo chown root:wheel mach_kernel

 

and do a permission repair using Disk Utility just in case.

 

That's a great tip and a good idea.

 

When I had this problem on a previous install what I did was put the ToH vanilla kernel in the BrazilMacPPF and ran it after I updated.