Jump to content

Update 10.6.2 Hazard to 10.6.8


picodepaperis01
 Share

16 posts in this topic

Recommended Posts

A bit of time ago I made my first Hackintosh, a Fujitsu Siemems Lifebook S7710 running OS X Snow Leopard 10.6.2 Hazard, and everything worked perfectly. I tried to install iLife '11, but I noticed it requested at least OS X 10.6.8 . So I downloaded the combo update from the Apple site and I installed it. Then I ran M.u.l.t.i.b.e.a.s.t and I choosed E.a.s.y.b.e.a.s.t, the drivers for the audio and for the Network. Finished this I rebooted and a kernel panic occurred. This is the report

post-1575084-14390281579799_thumb.jpg

Anyone can say me how to fix? I didn't have anything important, if necessary I could also do a fresh install.

Thanks in advance

 

P.s. Sorry for my english, I know it's not so good

 

 

I forgot: my pc has an Intel950GMA mobo with integrated graphics and Intel Dual Core processor

Link to comment
Share on other sites

A bit of time ago I made my first Hackintosh, a Fujitsu Siemems Lifebook S7710 running OS X Snow Leopard 10.6.2 Hazard, and everything worked perfectly. I tried to install iLife '11, but I noticed it requested at least OS X 10.6.8 . So I downloaded the combo update from the Apple site and I installed it. Then I ran M.u.l.t.i.b.e.a.s.t and I choosed E.a.s.y.b.e.a.s.t, the drivers for the audio and for the Network. Finished this I rebooted and a kernel panic occurred. This is the report

attachicon.gif20150808_084953.jpg

Anyone can say me how to fix? I didn't have anything important, if necessary I could also do a fresh install.

Thanks in advance

P.s. Sorry for my english, I know it's not so good

I forgot: my pc has an Intel950GMA mobo with integrated graphics and Intel Dual Core processor

kernel in backtrace with: sk.triax.kext.sleepEnabler.kext ...

 

What should that tell us? This driver is the cause of your problem. remove the driver (or use another sleepenabler.kext version)

 then repair disk permissions, renew the cache ... then reboots the system.

Have everything else as you install the system or which tools you used, I would like to distance ourselves.

Link to comment
Share on other sites

kernel in backtrace with: sk.triax.kext.sleepEnabler.kext ...

 

What should that tell us? This driver is the cause of your problem. remove the driver (or use another sleepenabler.kext version)

then repair disk permissions, renew the cache ... then reboots the system.

Have everything else as you install the system or which tools you used, I would like to distance ourselves.

hello

 

sleepenabler must be the one for the os x version u go use ..

 

anyaway like say before .. delete that kext .. will do nothing

 

good hack

I made as you both sayed, I replaced sleepenabler.kext with the one for 10.6.8 downloaded from hackintoshosx but at the reboot it stucks on this screen

post-1575084-14390618848036_thumb.jpg

Other solutions? I don't know anymore what to do?

Link to comment
Share on other sites

I'll try... Let's hope well

hello

 

have u try to see the image u post from here ?

 

i see nothing .. only thing i see .. is stuck at ur firewire port .. try to disable it from bios

 

good hack

I made as you sayed... It stucks on the same screen without the lines about the firewire
Link to comment
Share on other sites

you must be carefull when using sleepenabler. it should match the kernel else KP.

Yes, you are absolutely right. But now I don't think the sleepenabler to be the problem, now I want to understand why after the replacement it stucks

The strange thing about the grub is that if after the OS X installation I rebooted from the charmeleon I had to delete appletymcdriver.kext before to be able to boot normally, but if I immediatly after the OS X installation I installed ubuntu 15.04 and I booted OS X through the ubuntu grub I didn't have any problem, althoug appletymcdriver.kext was still in the system/library/extensions

Link to comment
Share on other sites

was this just an upgrade to 10.6.8? tried npci=0x2000 ?


10.6.8 changed a lot specially ACPI. i think error you're having is the "stuck on PCI configuration". This happened a lot on some system since 10.6.8. the rest of of the message are only the buffer from the kexts that are bieng used. This is where npci or dsdt patch or using acpiplatform & iopcifamily from 10.6.7 comes into place.

Link to comment
Share on other sites

was this just an upgrade to 10.6.8? tried npci=0x2000 ?

 

10.6.8 changed a lot specially ACPI. i think error you're having is the "stuck on PCI configuration". This happened a lot on some system since 10.6.8. the rest of of the message are only the buffer from the kexts that are bieng used. This is where npci or dsdt patch or using acpiplatform & iopcifamily from 10.6.7 comes into place.

My pc is in dual boot with ubuntu 15.04. There is the ubuntu grub as bootloader... Can you say me how to add flags in it please?
Link to comment
Share on other sites

as already wrote "artur-pt", you should disable in BIOS, the Firewire! and it is better to create a custom DSDT, it is soo long ago with Snow Leopard, who old brain cells forgotten much.
which vers. of FakeSMC.kext you use and where you have placed the FakeSMC.kext  /E/Extensions or /S/L/Extensions ? it bothers me this statement in your image: FakeSMC is a dubicate; .....

fakesmc.kext.zip

Edited by spakk
Link to comment
Share on other sites

 

 

as already wrote "artur-pt", you should disable in BIOS, the Firewire! and it is better to create a custom DSDT, it is soo long ago with Snow Leopard, who old brain cells forgotten much.

which vers. of FakeSMC.kext you use and where you have placed the FakeSMC.kext /E/Extensions or /S/L/Extensions ? it bothers me this statement in your image: FakeSMC is a dubicate; .....

I have already tried to disable the firewire but it stucks on the same screen without the lines about the firewire.

About the fakesmc.kext I don't know much... I have never modified or moved it. However I think it's in s/l/extensions

Link to comment
Share on other sites

was this just an upgrade to 10.6.8? tried npci=0x2000 ?

 

10.6.8 changed a lot specially ACPI. i think error you're having is the "stuck on PCI configuration". This happened a lot on some system since 10.6.8. the rest of of the message are only the buffer from the kexts that are bieng used. This is where npci or dsdt patch or using acpiplatform & iopcifamily from 10.6.7 comes into place.

I tried, but it stucks on this screen

post-1575084-14391889319226_thumb.jpg

Link to comment
Share on other sites

 Share

×
×
  • Create New...