Un-needed Extensions and Verbose Mode Errors |
December, 24, 2002 9:18 PM |
tippingj |
Greetings to all. I will admit that I despise the GUI for MOSX's bootup. I'm the sort of person that *has* to see the "gears" work underneath the OS when booting- it's just a nastey habbit, and I like to see what goes on. Almost every day, I boot my Mac (XPF 2.2.4), and then, see the errors about the Kernal Extensions and run over to the computer thinking that something is gonna detonate and take out my neighborhood. Saying that. Can I delete the un-needed Kernal Extensions (the ones causing the errors about dependencies, and loading, etc, wrong version, etc)- and if so, how can I tell which ones are for 10.1 (running 10.1.5 now) and those for 10.0? Basically, which ones can I delete so the Verbose/Console mode doesn't give me the pages worth of errors about incorrect versions? |
. |
RE: Un-needed Extensions and Verbose Mode Errors |
December, 26, 2002 7:46 PM |
joevt |
. |
What kind of computer do you have? What extensions are giving you errors? To get a list of extensions that XPostFacto installs, use the "Install Extensions" menu item in XPostFacto and select a volume that does not have a folder called "System". XPostFacto will create a System folder with its extensions. Move that folder for future reference. The stuff you see in verbose mode is also dumped to the file /private/ var/log/system.log. I use BBEdit to look at and edit that file. Every time you startup, a line containing "syslogd: restart" is dumped to the log. Use that to find the beginning of the info from the time you started up. The next line is usually "standard timeslicing quantum is 10000 us" although sometimes early verbose stuff does not get dumped to the log. I use 10.2 so you might see different stuff than I do. Look for the kernel extension errors in the log file. I have a habbit of looking in the log file to make sure PowerLogix Cache Control didn't screw up. Hopefully, Ryan will have a better cache config. Use the kextstat command in the Terminal to get a list of installed extensions, along with their versions and dependencies. Kernel extensions are stored in /System/Library/Extensions/. Drivers have names like com.apple.whatever. Kexts are folders in the Extensions folder that have names like Whatever.kext. I use CodeWarrior to search for the driver name in all the ".plist" files in the Extensions folder to find the kext. The plist files also have version info, dependencies lists, and matching info. In the Terminal, go to the Extensions directory. You can try using "sudo kextload -nt Whatever.kext" to test the kext without loading it. The command will tell you about dependency problems. I use XPostFacto 2.2.4 with OS X 10.2. I usually remove PatchedSCSIType05.kext and PatchedIOSCSICDDrive.kext because they do not load at all. I also remove AppleCurio.kext even though it does load because I don't use the external SCSI bus and it contains a plugin for OSX 4K78 that does not load. To remove an extension use "sudo rm -R whatever.kext". You also might consider deleting Extensions.mkext and Extensions.kextcache in "/System/Library/" using "sudo rm filename" although it is not usually necessary. |
. |
RE: Un-needed Extensions and Verbose Mode Errors |
December, 25, 2002 9:53 AM |
mitch707 |
. |
Boy! Unlike you, I interpret all that bootup/startup stuff as, "Go get a cup of coffee, I'll take care of everything and call you when it's ready". In my cyber life, unlike real life, the destination outweights the trip. Unchecked compulsions (nasty habits) are counterproductive. Good Luck. |
|
|