10-08-2009, 04:12 PM
|
Tiger
|
|
Join Date: Jun 2009
Posts: 306
|
|
Kamal,
Kexts are more or less like windows drivers. Even if you get a Kernel Panic, you can remove it manually, but this is a bit more complicated as you need Terminal language..
You failing audio messages are absolutely normal !
The dsdt information is not correct for OSX (normal), so AppleHDA cannot find audio device.
In Snow Leopard, when installing kexts, right after you copy them into E/E or S/L/E you must ALWAYS run Kext Utility, and the Repair Permissions.
Kext Utilities will rebuild the kext cache, so if you modify any kext, add or delete, you must do this. Kext Utility will repair also, but manually repairing permissions will find new permissions to repair - so do it also.
There is a slight difference between E/E and S/L/E... the first is created ONLY for Chameleon 2 bootloader to have its files and do its thing (like boot options, chameleon skins and also system Extension (kexts)) - and this helps you keep the system tidy.
So, if you update with Software Update, some system files can be replaced/modified by Apple in their original place, so if you keep all your "hack" kexts in E/E, they will always work over S/L/E
There are some rare cases where you need one kext to work with another (dependancies) and sometimes you will have to copy them into S/L/E for the kext to work, but that is rare.
Say audio... you should use VoodooHDA, it overrides AppleHDA, and works with most audio cards.
If Apple were to make, imagine, an iTunes update that also contains AppleHDA upgrade, imagine to add 3D effect or something, it doesn't matter because you will be actually using another kext to activate audio.
Some kexts substitute others (like voodoHDA) - others will work on top of vanilla kexts.
(the term "vanilla" is used for "Apple original not modified")
Hope it is clearer now !
Last edited by Gurruwiwi; 10-08-2009 at 04:27 PM.
|