Sorry, but that has nothing to do with your Firewire ports. You have some corrupted files involved in the login that's causing your delay, I suspect. Try creating a new user account. Disable automatic login, then restart the computer. At the login screen select this new account instead of your usual account. If there's no delay, then you indeed have problems with one or more files associated with your normal account's login.
Thanks for the reply. I have done all that. I believe I have a defective Firewire circuit. I have done every test imaginable. This is what my System Profiler reads after boot: Warning: Unable to list FireWire devices. <--- in red. Once in a great while the machine will boot normal and after boot if I check the System Profiler it reads that my Firewire 400 is working properly. I really believe that I have defective hardware, although I will say it seems to be more prominent since the Leopard upgrade, I just assumed it is getting much worse.
Message was edited by: Davidaz
I don't know if I am getting to the login screen. This happens before I even get a mouse cursor. I get the spinning wheel on the white screen then the spin stops and the screen goes all blue (no cursor) then after about 4-5 minutes I get the blue screen with a mouse cursor then seconds later my desktop. What is the software checking at that time?
The blue screen means you've gotten past any hardware checks which occur when the gray screen is visible. If you have nothing connected to the Firewire ports then get to the blue screen you are at the point where the OS is starting the initialization process and loading the GUI. As I said your problem is elsewhere. What you might consider doing is the following:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.
Well Kappy, I wish you were right because I would love to get to the bottom of this. I did as you said in your first post and created another "test" account and turned off auto-login and restarted. The results were the same. I get the white/gray Apple screen with the spinning pinwheel, then it goes to a solid blue screen (no cursor), then 4-5 minutes later I get a flash of the blue screen and the mouse cursor appears then seconds later I get the screen to choose a login account.
If what you are saying is correct then I am puzzled as to when the machine does (rarely) boot normally I am getting the Firewire OK in the System Profiler check?
I feel that the system is "hanging" on the firewire check, which you say happens at the Apple/spinning pinwheel screen, and I think the screen goes to timeout and since it's not ready for the blue screen with mouse cursor I just get a blank blue screen. Is there a way to run a "log" of the startup process?
I do know how to perform an Archive and Install but I cannot boot from a 10.5 system disk because I do not have one. I have a older Disk Warrior CD that will boot but I am afraid to do that because the boot system on it is Tiger. I have heard that if you boot from an older system than is on the drive it writes something to the drive in the process and that it will not boot back into the newer system anymore.
Message was edited by: Davidaz
If you cannot do an Archive and Install since you do not have the installer disc, then there's really little you can do. If you have a Leopard compatible version of Disk Warrior (4.1) then you can use it to repair the directory structure, but that will not fix a corrupt file problem which is more likely the problem you are having. If it's a cache related problem then you might fix it by removing all system and user caches then rebooting. You can use a tool such as TinkerTool System, Onyx, Cocktail, etc. to clear all system, user, and font caches. Restart immediately. You could also try the following instead:
You will need to type some Unix commands. If you are not comfortable with this, I don't know of anything other than a re-install. But if you are careful, you should be OK. I recommend you print this out in a largish mono-spaced font so you don't miss any spaces (or add extra ones). Note that case is important.
Be careful. Some of these commands are dangerous, since you are going to be root.
Start up in Single-User mode by restarting the computer. After the chime press and hold down the COMMAND-S keys until you see white text on a black background. When this has finished you will see a prompt ending in '#', although there may be other messages. Enter the following commands after the prompt:
Press RETURN. Wait a few seconds for 8-10 lines of output. If the last line says repairs were carried out, repeat this command until you get a message 'The volume <yourdiskname> appears to be OK'. Then continue with:
/sbin/mount -uw /
rm -r *
rm -r *
Press RETURN after each command.
This should now take you to a proper login screen after the normal boot sequence. You should then Repair Permissions by using Disk Utility (in your /Applications/Utilities folder).
well, I hate to say it, but I think Davidaz is right: it is a hardware, specifically FireWire problem. I have the exact same issueand I know for a fact my FireWire is dead. further more, I know the day my FireWire died and the day my computer started to hang for 7 min at startup was one in the same. you see, I made the mistake of trying to plug a powered up harddrive into a powered up mbp. this wouldn't have been a problem except I accidentally had the FireWire 800 plug upside down. I didn't cram it in, just tried it. when it didn't work, I flipped it over, but it was too late. my firewire and mbp would never be he same.
anyways, all that to say, I have the exact same problem. the grey (or white as some have called it) screen davidaz is talking about is before the blue almost to login screen. it has nothing to do with permissions, it is a hardware issue.
that being said, I do t know how to fix it except for replaci g the blown out FireWire chip. I'd lime to disable it completely, but I don't know unix and have no idea where to begin (well after I get to the command prompt). I know there are ways of disabling onboard components in BIOS but I'm not sure about EFI. Does anyone know? it would be much appreciated. thanks!
Okay, I had the same problem and finally found an answer. It totally worked and my mac is waking, sleeping, and starting up way better again. And, for some reason, the battery life seems to be more stable. Not sure why, but I'm not complaining. Here's the solution:
(Harddrive) > System > Library > Extensions
Find everything that looks like IOFireWire*.kext
for me, it was the following files:
Take these files and copy them somewhere else. I put them in:
(Harddrive) > System-disabled > Library > Extensions
Just so I'd remember where they originally went. Notice that when you grab them and drag them from the Extensions folder to a new folder, OSX automatically does a copy command rather than a move command, so you will have to manually delete these from the System > Library > Extensions folder after you "move" them to a new folder. (I'm assuming a little trick so we, the users, don't screw ourselves )
Double check these files are no longer in (Harddrive) > System > Library > Extensions . If they're gone, then restart your computer. It should work great.
This totally worked for me and, like I said, makes my computer feel like new (kind of) again. Or at least an expensive MacBook.