Keep getting the grey "need to restart" screen!

Hi all,
I have my lovely 12" PowerBook G4, 1.5GHz, which I love and don't want to depart with! For a while I was running 10.4 OS on it, and recently decided to upgrade to 10.5. Just today I had installed a brand spanking new copy of 10.5 and after restarting and logging into my admin account, all of the sudden I got the grey, "your computer needs to be restarted" screen. I did it, and logged in again and the same thing happened. Then I restarted again and logged in as a GUEST, and everything was working fine!

Thinking I might need to do some updates, I've selected Software Update, and sure enough there were somethings that needed to be updated, so I did that, restarted, logged in to the admin account, and things worked for about 5 min, then grey screen again! I restarted again and logged in as guest again and did the software update and there were now some additional things to update, which I did, restarted, logged in as admin, and the grey screen appeared right away. SO onnceee again I restarted logged in a guest and did the software update, and this time there were no new updates! With all the updates I am now up to 10.5.8 for the OS.

Meanwhile, I noticed that my wifi stopped working! I see the network and I connect to it just fine, but no internet! Other computers in the house work on the same wifi network, but the only way I can get internet now is through the ethernet cord.... what's happening?! Do you think it has something to do with firmware? I went on the apple website, and checked for updates, and the last firmware updates they released for my PowerBook was back in 05, and I recall updating all that before. Could it be that my lil computer just can't take all this new pressure from a more demanding OS? If so why does it work flawlessly under Guest login? Help please.

Thanks!
-One Muddled Guy

Just a thought,

Have you tried disabling your password and username at the startup and seeing if you can boot directly into your admin account?

If that does not work, I would make a new account and test it out.

I don't know if this would be relevant to the situation at hand, but how much RAM does your G4 have? OS X 10.5 needs considerably more memory than 10.4, but that wouldn't explain why Guest account works ...

You did a clean install, archive & install or an upgrade install?

Sounds like an upgrade install if the guest account is working. First thing would be to open up Console and read through the logs to see if you can find the offending application.

jhonrox said:

I don't know if this would be relevant to the situation at hand, but how much RAM does your G4 have? OS X 10.5 needs considerably more memory than 10.4, but that wouldn't explain why Guest account works ...

Click to expand...

Hi jhonrox, I've ugraded my ram to 1.25gb a little while back, which i think is enough for 10.5. Thanks though

bobtomay said:

You did a clean install, archive & install or an upgrade install?

Sounds like an upgrade install if the guest account is working. First thing would be to open up Console and read through the logs to see if you can find the offending application.

Click to expand...

Hi bobtomay, this was an upgrade from a 10.4 version. How would I go about opening up the console logs? I have yet to do that Also would it matter which account I do this from? I am in guest now.

Thanks!

Since your guest account is working, log into that. Console is in your Applications / Utilities folder.

Sounds like some 3rd party app that's not compatible causing the system to crash. The logs should give you a hint of what it is.

This is where an external bootable backup helps. With it, you could boot to the external and be able to browse the internal to delete the offending files. It may be tough to do that from the guest account.

bobtomay said:

Since your guest account is working, log into that. Console is in your Applications / Utilities folder.

Sounds like some 3rd party app that's not compatible causing the system to crash. The logs should give you a hint of what it is.

This is where an external bootable backup helps. With it, you could boot to the external and be able to browse the internal to delete the offending files. It may be tough to do that from the guest account.

Click to expand...

I found the logs! I dont understand a thing they talk about, but I took alexsd123's advice and removed the password from my admin account, and created a new admin account into which I was able to login without a problem. I've attached the log report from the console... if anyone can give me some points on what the problem might be, I would greatly appreciate it.

View attachment Console Report.txt

This is actually a more accurate console log as it corresponds directly to when I tried logging into my admin account right when the gray screen appeared. If anyone notices anything out of the ordinary, please let me know so that I could at least know what to address. Thanks!

9/17/09 10:18:58 PM com.apple.launchctl.System[2] fsck_hfs: Volume is journaled. No checking performed.
9/17/09 10:18:58 PM com.apple.launchctl.System[2] fsck_hfs: Use the -f option to force checking.
9/17/09 10:19:05 PM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
9/17/09 10:19:06 PM com.apple.launchd[1] (com.apple.RemoteDesktop.PrivilegeProxy) Unknown key for boolean: EnableTransactions
9/17/09 10:19:06 PM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
9/17/09 10:19:06 PM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
9/17/09 10:19:06 PM com.apple.launchd[1] (org.x.privileged_startx) Unknown key for boolean: EnableTransactions
9/17/09 10:19:39 PM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[70]) Exited: Terminated
9/17/09 10:19:39 PM com.apple.launchctl.Aqua[76] launchctl: Couldn't stat("/etc/mach_init_per_user.d"): No such file or directory
9/17/09 10:19:39 PM com.apple.launchd[73] (com.apple.AirPortBaseStationAgent) Unknown key for boolean: EnableTransactions
9/17/09 10:19:39 PM com.apple.launchd[73] (org.x.startx) Unknown key for boolean: EnableTransactions
9/17/09 10:19:41 PM com.apple.launchd[73] (com.apple.ReportPanic[81]) Exited with exit code: 1
9/17/09 10:19:56 PM Dock[88] [QL ERROR] Generator database update takes too long... we will use what we currently have
9/17/09 10:19:56 PM Dock[88] [QL ERROR] Generator database update takes too long... we will use what we currently have
9/17/09 10:20:43 PM org.ntp.ntpd[30] Error : nodename nor servname provided, or not known
9/17/09 10:20:44 PM com.apple.SystemStarter[33] Starting Cisco Systems VPN Driver
9/17/09 10:20:44 PM com.apple.SystemStarter[33] /Library/Application Support/Apple Qmaster/qmasterconfig: line 19: unexpected EOF while looking for matching `"'
9/17/09 10:20:44 PM com.apple.SystemStarter[33] /Library/Application Support/Apple Qmaster/qmasterconfig: line 20: syntax error: unexpected end of file
9/17/09 10:20:44 PM com.apple.SystemStarter[33] Starting Qmaster services
9/17/09 10:20:44 PM com.apple.SystemStarter[33] kextload: extension /System/Library/Extensions/CiscoVPN.kext is already loaded
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
9/17/09 10:20:46 PM com.apple.SystemStarter[33] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
9/17/09 10:20:46 PM com.apple.SystemStarter[33] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

I think I may have figured it out,

Go to the Macintosh HD through finder, then click on Library. There should be a folder in there named StartupItems. Open it, find the NUTD folder and delete it.

alexsd123 said:

I think I may have figured it out,

Go to the Macintosh HD through finder, then click on Library. There should be a folder in there named StartupItems. Open it, find the NUTD folder and delete it.

Click to expand...

hey, thanks for the suggestion but I went to the StartUpItems folder and couldn't find the NUTD folder there. Since I can't get into the needed admin account, I wonder if this could be why? I've tried doing this from a guest account and from another admin account I created in the meantime and nothing.