Jump to content
661 posts in this topic

Recommended Posts

Hi Andy and BlackCH,

 

I've been bumping into this kernel panic a while now, it's appears almost once every two days, out of nowhere.

 

IMG_1854.JPG

 

I've tried to get help from the VooDoo thread, and one of the member recommend me to replace the seatbelt.kext. Did that and the problem persist. I'm really confused and don't know what else to do. Should I upgrade to 9.6.0 using AnV kernel? If so, how? I selected VooDoo 9.5.0 1.0 during installation and it should be stable (according to lots of people who reported).

 

system.kext.png

seatbelt.kext.png

mach_kernel.png

AnV XNU V1.3 is Darwin XNU 9.6.0...

You need seatbelt.kext and System.kext for 9.6.0...

Get them both from the installer package on this forum (AnV XNU V1.3, get both .sitx files, extract with StuffIt, use Pacifist to extract System.kext and seatbelt.kext, put them in the right place with the right permissions...).

That should solve the problem...

 

Err, the problem persists even with AnV kernel... What is wrong with this?

IMG_1874.JPG

See other 2 replies...

Err, the problem persists even with AnV kernel... What is wrong with this?

 

popophobia,

 

Someone else beat me to the punch about seatbelt kext. If that works for you then ignore the below and congrats.

 

I am not a kernel expert but I had a similar issue which turned out to be my Networking kext. If you look at each line that starts with "debugger: " you can see that it refers to your GFX kext. What versions of OS X have you had working on your setup? The reason I ask is you could acquire the NVDAResman.kext, IODRVSupport.kext, IOPCIFamily.kext, and IOGraphicsFamily.kext from a previous working version and put it in your extensions folder using Kext Helper.

 

Best of luck!

popophobia,

 

Someone else beat me to the punch about seatbelt kext. If that works for you then ignore the below and congrats.

 

I am not a kernel expert but I had a similar issue which turned out to be my Networking kext. If you look at each line that starts with "debugger: " you can see that it refers to your GFX kext. What versions of OS X have you had working on your setup? The reason I ask is you could acquire the NVDAResman.kext, IODRVSupport.kext, IOPCIFamily.kext, and IOGraphicsFamily.kext from a previous working version and put it in your extensions folder using Kext Helper.

 

Best of luck!

 

I installed the package from Andy (9.6.0) so seatbelt and system kext should not be a problem.

 

In my previous install, I used natit I think, not as simple as EFI string as in this XxX installer. I'm not sure if it's replaceable. Should I try to apply a patch (nvidia patch) instead of using the EFI string method because it's pretty obvious that the graphic card is causing the problem here.

I installed the package from Andy (9.6.0) so seatbelt and system kext should not be a problem.

 

In my previous install, I used natit I think, not as simple as EFI string as in this XxX installer. I'm not sure if it's replaceable. Should I try to apply a patch (nvidia patch) instead of using the EFI string method because it's pretty obvious that the graphic card is causing the problem here.

Me I prefer EFI strings but if you wish you can remove them from:

/Library/Preferences/SystemConfiguration/com.apple.Boot.plist

Then just install injector like natit/nvinject/nvkush.

You can try if this works better for you but AFAIK EFI strings work better...

I would say: test it and report back...

excuse me man.. i don't want to quote all the post.. but

 

what is the correct order to apply those ppf? i didn't have unterstood.

 

you wrote from bottom to top

 

iso first edition (it's obvoiusly)

 

then: dvdplayer fix

then: crashfinder fix

 

then PPF1 min fix

 

then you wrote about PPF3 fix..

 

but i didn't see any ppf2 link ..

and where is the link of ppf3?

 

thanks in advance.. your iso for me is very important!!

excuse me man.. i don't want to quote all the post.. but

what is the correct order to apply those ppf? i didn't have unterstood.

you wrote from bottom to top

iso first edition (it's obvoiusly)

then: dvdplayer fix

then: crashfinder fix

then PPF1 min fix

then you wrote about PPF3 fix..

but i didn't see any ppf2 link ..

and where is the link of ppf3?

thanks in advance.. your iso for me is very important!!

 

If you have the REV1 you can update only up to PPF1. After that you need a new ISO.

Just download the new version (it has every patch integrated): 'XxX_x86_10.5.6_Install_Disc_Universal_Final.v2' from "the green demon" (Make sure you get the 'FINAL.V2' version), the old ISO is kind of crappy; besides, any future PPF will be done over this new ISO. I will change the first post 'cos is confusing.

Well I downloaded the v2 final, MD5 matched, I burnt with Nero @ 4x, and did data verification. Just did a default install, gets to 2 minutes remaining and then get an error saying that it couldn't verify the package "Java" and asks to reboot.

 

Have burnt it twice now, any ideas?

Well I downloaded the v2 final, MD5 matched, I burnt with Nero @ 4x, and did data verification. Just did a default install, gets to 2 minutes remaining and then get an error saying that it couldn't verify the package "Java" and asks to reboot.

 

Have burnt it twice now, any ideas?

 

It is a problem on your side; AFAIK theres nothing wrong with the ISO (I've tested several times). The DVD is not reading properly, most likely because the ATA/SATA in not fully working with this release. Or maybe your DVD drive is faulty... IDK....

The DVD is not reading properly, most likely because the ATA/SATA in not fully working with this release. Or maybe your DVD drive is faulty.

 

Is there a fix or patch I can apply for the ATA/SATA? It is strange that it can get all the way through the install, down to the last two minutes and then fail.

 

I tried burning on another PC to no avail either, also chose to install the AppleAHCI e.t.c for the SATA, still no luck. *shrug*

Hey BlackCH,

 

XxX_x86_10.5.6_Install_Disc_Universal_Final.v2 Mkext doesnt work for me but Extensions.mkext_mcp67_c.zip

worked for me i was able to install leopard successfully. Have u made any changes to the newer mkext final v2 regarding MCP67 support its not working any longer, Can u just post the newer mkext with MCP67 support for XxX_x86_10.5.6_Install_Disc_Universal_Final.v2. what are the changes that exists between rev 1 mkext and rev 2 mkext or can i use Extensions.mkext_mcp67_c.zip with XxX_x86_10.5.6_Install_Disc_Universal_Final.v2dvd. plz reply

 

I have attached the thumbnail check it out for the error, i think its saying unsupported kext 0x055010de

 

regards,

macky

 

Looks promising. Try this out:

http://www.megaupload.com/?d=8RMN33UL

 

 

 

1- Is been there for long time already:

http://forum.osx86scene.com/viewtopic.php?f=16&t=1661

Nowadays install the bootloader is much more easier. Enough with adding chameleon installer to the install packages....

or you have the automated Instahackintosh:

http://forum.insanelymac.com/index.php?showtopic=136138

 

2- No way. Im convinced google can provide this and more. I encourage self-help and research.

 

3-The Install.log file contains all the information. /var/log/Install.log (I think)

post-197843-1236674276_thumb.jpg

Hey BlackCH,

 

does FX5200,128 mb graphic card fully supported in this release ?

 

thx :wallbash:

 

i guess FX 5200 is not supported with any 10.5.6 release........i tried this card with many 10.5.2 releases but wont worked....but it worked very nicely with all resolutions on kalyway 10.5.2.......i'm also downloading this release to check that FX 5200 128 MB and FX 5500 256 MB are working or not with this release.........

 

BTW guud luck.........if anyone have a fix for these cards than please post here..........

 

thanx...........

CPU ID

 

Last release v1; My atom was recognized as a 1.6ghz Intel core solo.

 

This release V2, with what I believe to be same selection of customization based on my notes; the cpu is unknown and causing some apps to think its a powerpc

 

Advice?

 

Thanks everyone.

CPU ID

 

Last release v1; My atom was recognized as a 1.6ghz Intel core solo.

 

This release V2, with what I believe to be same selection of customization based on my notes; the cpu is unknown and causing some apps to think its a powerpc

 

Advice?

 

Thanks everyone.

 

Kernel related? Or maybe wrong SMBios?

×
×
  • Create New...