Mac OS X on x86 Hardware 2008–2024 Technical Archive
InfiniteMac OSx86 › OSx86 Core & 10.X › AppleVIAATA, JMicron and AppleNForceATA over 4gb RAM bug sol…
28,985 reads · 2008-11-05 – 2010-01-18
Dossier 10.X Core AHCI / SATA

AppleVIAATA, JMicron and AppleNForceATA over 4gb RAM bug solved

I know this issue has affected many members here, i'm glad to report it seems to have been solved at last. Obviously post any driver feedback in the original thread. Basically, the problem is when you have more than 3 gb of ram (some says…

Primary Author
@Voyn1x Published 2008-11-05
Collection
OSx86 Core & 10.X
Archival Footprint
28,985 historical reads · 4 curated field notes (from 7 dispatches) · 2008-11-05 – 2010-01-18
Credited Voices (5)
@Creatorp (2)@lanceomni (2)@Voyn1x@LawlessPPC@bhast2

I know this issue has affected many members here, i'm glad to report it seems to have been solved at last. Obviously post any driver feedback in the original thread.

@slashhack on InsanelyMacBasically, the problem is when you have more than 3 gb of ram (some says 2.5 gb) and AppleVIAATA driver (I think JMicron IDE driver also has this problem). In my case, I've got 2 IDE HDD and when I upgraded to 4 gb of ram, my desktop started to freeze, or give kernel panics. After some hours of googling and looking for the driver to…


Source ↗

Synthesized Community Field Notes

4 technical responses curated from 7 original dispatches

Field Note #1 @Creatorp 2010-01-18

Um...which exactly do i donwload from the google site?

Field Note #2 @lanceomni 2010-01-18

Try the one linked in my signature. Please backup you existing extensions prior to installing

Field Note #3 @Creatorp 2010-01-18

i know but then it tells me to download from google code source and i have the options of

patch.diff (darwin-ata.googl ecode.com/files/patch.diff) ALPS GlidePoint voodoo patch (code.goo gle.com/p/darwin-ata/downloads/detail?name=patch.diff&can=2&q=) Jul 09 (code.goo gle.com/p/darwin-ata/downloads/detail?name=patch.diff&can=2&q=) 6.7 KB (code.goo gle.com/p/darwin-ata/downloads/detail?name=patch.diff&can=2&q=) 161 (code.goo…
Field Note #4 @lanceomni 2010-01-18

Im sorry I forgot I had linked to the thread and not to an actual file. Here is a direct link:
darwin-ata.googl ecode.com/files/AppleNForceATA.kext.zip

You can use an application like KextHelper and you can also manually install as described below.

Manually install a kext
Manually Installing a Kext
You can manually install drivers (kexts) by following the instructions below. Be sure to do your research and make sure that what you are installing will work. It is highly recommended that you do steps 2, 3 & 4 to backup your extensions folder. This will make it possible to recover from a non booting system

Place the kext you wish to install on your desktop (The following commands rely on it being on the desktop).

1. Give yourself root privileges so that you can modify files.

sudo -s

2. Make a backup copy of your kexts. First we will make a directory called "backup" in our root directory to store them. Open Terminal and type:

mkdir /backup

3. Change directories to /System/Library This will shorten some of the commands we have to type in.

cd /System/Library

4. Copy your kexts to the new "backup" folder.

cp -r Extensions/ /backup/

5. Copy the kext from your desktop to the extensions folder (Replace MYKEXT.kext with the name of the kext you want to install.

cp ~/Desktop/MYKEXT.kext Extensions/MYKEXT.kext

Repeat step 5. for each additional kext.

6. Set the proper permissions for the extensions folder.

chmod -R 755 Extensions/

7. Set the proper ownership for the extensions folder.

chown -R root:wheel Extensions/

8. Touch the extensions folder

touch Extensions/

9. Remove the extensions cache to force OSX to rebuild it with our new kext.

rm -rf Extensions.mkext

10. Repair permissions to your drive.

diskutil repairpermissions /

11. Reboot using the boot-flags -v -f
-v Verbose Mode displays useful information during the boot process.
-f Forces OSX to load kexts from the extensions folder instead of the cache file. We did delete the cache file so this is just a precaution.

Corroborated & Participated: @LawlessPPC @bhast2
Sources & Contributor Provenance (5 credited usernames · Thread #1552)
UsernameDossier ContributionDispatchesActive Window
@CreatorpContributor22010-01-18
@lanceomniContributor22010-01-18
@Voyn1xPrimary Author12008-11-05
@LawlessPPCContributor12008-11-05
@bhast2Contributor12008-11-11