InfiniteMac OSx86 - 10.5.6 Released!

InfiniteMac OSx86 (http://infinitemac.com/forum.php)

- 10.X (http://infinitemac.com/forumdisplay.php?f=36)

- - 10.5.6 Released! (http://infinitemac.com/showthread.php?t=1743)

i have XFX 7300GS 256MB

Omg i too have the same problem.. and i have kernel panic on VMWareFusion too..

Quote:

Originally Posted by dagger (Post 19853)

Thanks. Here's what I did:

1. Installed PC_EFI v9 Chameleon on my 10.5.5 HDD using UInstaller 1.2
2. Patched DSDT using DSDT Patcher (Selected all options)
3. Installed 10.5.6 update from Apple site, patched with AMD Patcher .31
4. Rebooted to single user, and followed your instructions (removed all graphics kext etc)
5. Installed Apple's Graphics Update to replace removed kexts.
6. Used OSX86Tools to get hex code of my Graphics card (nVidia Geforce 7300GT 256mb)
7. Inserted the hex code manually in com.apple.Boot.plist string
8. Rebooted.
9. Worked fine, but then I get a kernel panic when I check on Graphics/Display on System Profiler:
http://img301.imageshack.us/img301/4...1205mu6.th.jpg

From what I can understand, it has something to do with the com.apple.iokit.IOGraphicsFamily.

I hope that's detailed enough for you to help me out with this one.

Thanks again and hopeto hear a solution soon.

Quote:

Originally Posted by dagger (Post 19948)

Thanks nfoav8or. Now I know I have no idea what I'm doing.

Here's my Boot.plist:

Code:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

        <key>Kernel</key>

        <string>mach_kernel.voodoo</string>

        <key>Kernel Flags</key>

        <string>None</string>

        <key>Timeout</key>

        <string>5</string>

        <key>device-properties</key>

        <string>6c0200000100000001000000600200000d00000002010c00d041030a0100000

00101060000040101060000007fff04000e0000004e00560050004d0000002000000001000

00000000000000000000000000000000000000000000000000220000005600520041004d0

2c0074006f00740061006c00730069007a006500000008000000000000101c0000006400650

076006900630065005f00740079007000650000000f0000004e5644412c506172656e740e00

00006e0061006d00650000000b000000646973706c617922000000400030002c0064006500

76006900630065005f00740079007000650000000b000000646973706c6179220000004000

31002c006400650076006900630065005f00740079007000650000000b000000646973706c6

179100000006d006f00640065006c0000001a0000006e5669646961204765466f7263652037

33303020475420000000400031002c0063006f006d00700061007400690062006c006500000

00e0000004e5644412c4e564d616314000000400030002c006e0061006d0065000000120000

004e5644412c446973706c61792d4114000000400031002c006e0061006d006500000012000

0004e5644412c446973706c61792d4220000000400030002c0063006f006d00700061007400

690062006c00650000000e0000004e5644412c4e564d6163100000004e00560043004100500

000001800000004000000000003000c00000000000007000000001e00000072006f006d002d

007200650076006900730069006f006e0000002e0000006e5669646961204765466f7263652

037333030204754204f70656e474c20456e67696e65205b4546495d</string>

</dict>

</plist>

Hope its an easy fix.

To both you and demigod -

do you still have the problem if you remove the hex code? double-check the hex code to make sure it is correct as well.

also, demigod, is the running kernel named mach_kernel or mach_kernel.voodoo? Fusion doesn't work with a kernel other than one named mach_kernel... check the voodoo documentation for more info on this.

i used the installer which came with voodoo package.in mac drive i have two files "mach_kernel" as link and "mach_kernel.voodoo" too.. i didn't modified it. and the kernel panic with VMWare is some thing to do with the update i guess.there are lots of post regarding this in vmwarefusion forum.

fusion is important for me atleast for now.so i reverted back to 10.5.5 .. :(
Thanks for the help nfoav8or

Quote:

Originally Posted by demigod (Post 20042)

You should rename you're mach_kernel.voodoo back to mach_kernel to get vmware working...
Place the other mach_kernel in a safe location :)

Code:

VMware (OS X) does not run when running on Voodoo kernel. 

VMware requires the running kernel to be named /mach_kernel. This is a known 

bug in VMware. Either install your Voodoo kernel as /mach_kernel (not 

recommended), or remove /mach_kernel and create a symbolink link in its place 

(alias) which points to Voodoo kernel (/mach_kernel.voodoo). If you used the 

automatic installer, this has been done for you. If you installed the kernel manually, 

refer to the Insta$ing the Kernel section for more details.

Hangs on Boot after Hexcode removal

Quote:

Originally Posted by nfoav8or (Post 20041)

To both you and demigod -

do you still have the problem if you remove the hex code? double-check the hex code to make sure it is correct as well.

Double-checked the hex code like you said, and as fas as I can tell, its the same from the EFIStudio installer as well as the UInstaller.

If I remove the hex code from the Boot.plist, my boot hangs at around this point:
http://img267.imageshack.us/img267/3...1576vp3.th.jpg

I don't see any indication of a kernel panic, and I've let it hang for about 2 hours with no change.

For me to boot properly, I had to remove all the graphics kext again and reinstall the Apple Graphics Update and the Hex code using EFIStudio.

Hangs on restart....

Quote:

Originally Posted by biird (Post 19395)

I'm on an AMD w/ Voodoo 9.5 Kernel and I am posting from 10.5.6. I downloaded and installed the Universal OSX86 Installer and selected Install PC_EFI v9. After that, I downloaded and used the DSDT Patcher GUI and selected all the options. After that, I backed up some kexts and data to be safe and then got the 10.5.6 Update from Software Update (not the ASU; I got an error every time I tried).

After restart, it booted! I had to replace AppleSMBIOS.kext with my old kext because About This Mac would force a logout, but that all I needed to do to get 10.5.6 working for me :)

Hi i followed the above example with the Voodoo kernel in place .... using Apple update .. i am than prompted to restart to complete update to 10.5.6 ...then the screen changes to the default empty desktop (the one you get after a fresh install) even through i have changed the desktop image, then it just hangs until i power the thing off manually ... this now happens any time i try to log out and power down...

after forced power down everything boots up fine again...

anyone have any pointers....

bump

Quote:

Originally Posted by dagger (Post 20174)

so you weren't using the updated graphics already? or had you just deleted the files from before?

My card only requires me to use the NVDANV40Hal.kext (from the update) and the hex string. But it doesn't hurt to keep the rest as you should get full support now.

The above shot you posted just shows that the system is hanging on the graphics as it isn't sure which to use.

And, am I reading this right, you got it working now? awesome.

Quote:

Originally Posted by nfoav8or (Post 20204)

Let me clarify my previous post. I've used the Graphics Update from Apple already (as per your advice), that's why I got my graphics card working and solved my original 10.5.6 update problem. But the kernel panic in the System Profiler still happens.

Quote:

Originally Posted by nfoav8or

do you still have the problem if you remove the hex code? double-check the hex code to make sure it is correct as well.

I did what you said, to remove the Hex code only, to see if the problem goes away with the Kernel panic, but my system just hangs like what you saw from my previous post. I had to remove all the updated graphic kexts again in order to boot back to the GUI and reinstall the updated NVDA* again and restore the Hex code to the Boot.plist, but again have the same System Profiler kernel panic whenever I click on Graphics/Display.

http://img301.imageshack.us/img301/4...1205mu6.th.jpg

So problem still not solved.

look in /System/Library/SystemProfiler/ and then compare that to: http://nfoav8or.infinitemac.com/SystemProfiler.png

any differences?

There's an extra file located in my /System/Library/SystemProfiler folder called SPiPlatformReporter.spreporter.

http://img355.imageshack.us/img355/4...ure2sk3.th.png

That's the only difference file-wise.