Jump to content
8 posts in this topic

Recommended Posts

well i have been using iatkos for a couple of days everything seemed perfect till i actually needed to start doing some work with cs4. opened up a couple of files and it crashed. read about appleviaata.kext fixes because over 3 gigs isnt supported by 32 bit or something because applieviaata was made for 32bit so i tried slashhack's fixes posted here http://forum.insanelymac.com/index.php?sho...1&start=100 and im not sure if im not doing it right or im not choosing the right files (i chose AppleVIAATA.kext-v0.2.zip

and JMicronATA.kext.zip)

but it didnt fix nething. so i opened up my activity monitor and opened those programs and files again and it seems to crash aroudn 2.5 ish gigs of ram. not sure what to do but ne way here is my setup.

 

iatkos 5i 10.5.5 upgraded throguh apple to 10.5.6.

abit ip35-e

core 2 duo e6750

nvidia 7300gt 512mb

2 SATA hard drives internel 3 ATA hard drives EXTERNAL(through USB CASES)

1 IDE DVD drive

this motherboard does use jmicron (cant disable through bios)

6 gigs of ram 2x2gig and 2x1gig sticks.

 

 

thx for thehelp ahead of time.

 

EDIT:

 

i just thought of something i think it may not be workign with slashacks appleviaata kexts because im running iatkos 5i which secures its own kexts in a folder so you can do apple update without it messing up your system. how do i modify those kexts so it runs off of the new AppleVIAATA.kext file? thx

Listen, if you don't need IDE and want to have full use of your ram, just delete this file JMicronATA.kext and add this line to terminal in single mode, and it will be fix!

rm /System/Library/Extensions.mkext

 

well i did that. loaded cs4 stuff till it used 2.4-2.5 gb's of ram and it crashed again. ne one else?

well i did that. loaded cs4 stuff till it used 2.4-2.5 gb's of ram and it crashed again. ne one else?

 

if slashack's fix isnt working then you can use the bootflag maxmem.

maxmem=2048 will cap your memory usage at 2GB you can play around with it till you get the sweet spot. You may want to verify that you do not have any conflicting kexts as this fix usually works.

if slashack's fix isnt working then you can use the bootflag maxmem.

maxmem=2048 will cap your memory usage at 2GB you can play around with it till you get the sweet spot. You may want to verify that you do not have any conflicting kexts as this fix usually works.

 

its hard to tell which kexts i need because there are 288 of them. some of them i can see that i probably dont need but most of them idk. nething i should be looking for in particular? thx

 

if slashack's fix isnt working then you can use the bootflag maxmem.

maxmem=2048 will cap your memory usage at 2GB you can play around with it till you get the sweet spot. You may want to verify that you do not have any conflicting kexts as this fix usually works.

 

also im not sure why it would panic immediately when i run Rember. it did it instantly, no need to access my IDE which is my dvd burner, no disk inside.

The 32bit kext address issue causes a complete freeze. As in you see the screen freeze, mouse & sound. If you are getting kernel panics it may be something else. Generally this happens around 3.5gb used but I have also had it freeze close to 3gb on one machine that had 3 PCI cards installed. I pulled all of the cards and the freezing moved back up to 3.5gb.

 

Do you see the kernel panic msg? You can check Console, make sure to check all of the logs.

The 32bit kext address issue causes a complete freeze. As in you see the screen freeze, mouse & sound. If you are getting kernel panics it may be something else. Generally this happens around 3.5gb used but I have also had it freeze close to 3gb on one machine that had 3 PCI cards installed. I pulled all of the cards and the freezing moved back up to 3.5gb.

 

Do you see the kernel panic msg? You can check Console, make sure to check all of the logs.

 

yes it is a kernel panic. the msg scrolls down and says " power off hold wutever button blah blah" and now for some reason im having issues booting into vista but that is an entirely differnet subject. however YES it is a kernel panic.

×
×
  • Create New...