osx 10.3.8

sqook · Post by **sqook** » Thu Feb 10, 2005 4:13 pm

Credo wrote:problem! Help!

upgraded to 10.3.8 on my PB
rebooted
since then it only boots text based environment SH Darwin BSD Login screen...

C

Log in normally, and then run "dmesg" as well as "tail -n 100 /var/log/messages", and paste them back here.

Actually, the dmesg output will be rather long, so you might just want to look for the interesting bits. You can also pm them to me and I'll take a look at them for you.

Credo · Post by **Credo** » Thu Feb 10, 2005 5:57 pm

sqook

thank for your attention

but the problem is i cant log in normaly and therefore i can not copy and paste here. Or can i start Safari outside the grafphic OS X environment?

i can do the dmesg though, is there anything special there of interest?

C

sqook · Post by **sqook** » Thu Feb 10, 2005 6:28 pm

Credo wrote:sqook

thank for your attention

but the problem is i cant log in normaly and therefore i can not copy and paste here. Or can i start Safari outside the grafphic OS X environment?

i can do the dmesg though, is there anything special there of interest?

C

You can log in normally.... it's just not a GUI login.

I've had problems like this before, and the reason you're getting dumped to a console is probably because the loginwindow process can't start for some reason. Mac OS will give you a root recovery console (or in this case, what seems to be a text login) as a key for system recovery, but here, you're in the realm of unix diagnostics now. If you've never used a unix shell before, this will likely be very confusing, but stick with it, as unix is very good at system recoveries. You're right, though; I forgot that you'll be unable to paste anything here and you'll have to do the diagnostics on your own.

"dmesg" (in case you were curious) is a record of all the kernel error/warning messages that have been printed out since the machine booted up. It is normally not that interesting until the end of output, so just look at the last 10 or so lines for any nasty looking messages.

I also forgot that OS X has some different ways of doing log reporting than standard *nix's. Unfortunately, I don't have my mac with me at work today, so I am unable to tell you the specific location of the logfiles, but you can find the directory in which they are stored by running this command:

Code: Select all

find / -iname "*crashreport*" -type d -print

I also don't remember if OS X respects the "-iname" option or not; so if it doesn't work, then try:

Code: Select all

find / -name "*Crash*" -type d -print

You are looking for a directory called "crashreporter" or something very similar to that. Type in "cd blah" (where 'blah' is the name of the directory it gives you), and then type in "ls" to show the files there. Inside of that directory will be logfiles from processes that crash and burn. You can read the files with the "cat" command. The key to properly diagnosing the machine is in finding out (a) where along the boot process it dies, (b) what program is dying, and with what error message, and (c) googling said information and finding a solution.

There are obviously many possible things that could be wrong with your machine, and the place for me hypothesizing about them will longer be in this thread.

If this post doesn't give you a good "hint" as to finding out how to recover your mac, PM me and I'd be happy to help you out from there.

If this seems like too much work for you, you can also just reinstall your machine. Do you have an ipod? If so, I'd advise installing an image of OS X on it, booting your mac from the ipod, and using that to recover your data first by dumping it to either the ipod or network storage (that trick works like a charm, btw).

Credo · Post by **Credo** » Thu Feb 10, 2005 6:56 pm

sqook

you are very kind trying to help me out of this!!! Bless u man!

i will try what you said. My unix language capabilities are shallow to say the least, but i will give it a try and get back here. (might be tomorrow though)

again thanks!

C

noisetonepause · Post by **noisetonepause** » Thu Feb 10, 2005 8:03 pm

Squook -

Is there any way to disable to GUI login? I'm stupid like that...

Had a look at /System/Library/Coreservices/loginwindow.app, but it looks like it also takes care of other things, so I'm wary of just deleting it.

-Paws

sqook · Post by **sqook** » Thu Feb 10, 2005 8:22 pm

noisetonepause wrote:Squook -

Is there any way to disable to GUI login? I'm stupid like that...

Had a look at /System/Library/Coreservices/loginwindow.app, but it looks like it also takes care of other things, so I'm wary of just deleting it.

-Paws

This page should tell you how.

Rather interesting little hack; I had always thought that most of the /etc files were ignored by OSX and regenerated there for legacy purposes.

noisetonepause · Post by **noisetonepause** » Thu Feb 10, 2005 8:30 pm

Now, why didn't I know about this page? Free chairs for you, mate.

(and soz for misspelling your name, I noticed after I posted, than couldn't be arsed to edit it...)

-Paws

noisetonepause · Post by **noisetonepause** » Thu Feb 10, 2005 8:32 pm

Pico? Pico?!

Meh.

I'll give this a go, but if you look at the loginwindow.app bundle, you'll see that it contains the .nibs for the shut down/log out/sleep dialog, as well as the force quit one. Hmm.

-Paws

sqook · Post by **sqook** » Thu Feb 10, 2005 8:59 pm

noisetonepause wrote:Pico? Pico?!

Meh.

I'll give this a go, but if you look at the loginwindow.app bundle, you'll see that it contains the .nibs for the shut down/log out/sleep dialog, as well as the force quit one. Hmm.

-Paws

Haha, I didn't write the guide... I would have at least told you to use vi. ;]

.nib files are just resources for the graphical elements of a carbon application (as you seem to have discovered by now). The problem with removing loginwindow.app is that your OS is going to expect it to be there and try to launch it as part of the default boot. When this fails, it may not necessarily give you a login prompt as a backup.... but then again, I've never really had to tweak my mac like this, so I don't know how OS X would deal with something like that.

But hell, don't take my word for it... I'm really curious to know what happens myself. =) You should try running chmod 000 on that directory and let us know what happens..

noisetonepause · Post by **noisetonepause** » Thu Feb 10, 2005 10:20 pm

sudo mv /Applications/Utilities/Terminal.app /System/Library/CoreFoundation/Finder.app

REAL MEN DON'T NEED MICE

err... sorry about that!

12micsn1 · Post by **12micsn1** » Thu Feb 10, 2005 11:19 pm

people should know they need to repair there permissions before upgrading and after. some programs might not open till permissions are repaired.

applications/ultilities/disk ultility

php · Post by **php** » Fri Feb 11, 2005 5:10 am

tch wrote:Does anyone use Logic Pro7?
Is is good with the 10.3.8 ?
thx

I'm using Logic Pro 7.0.1 with OS 10.3.8 and they get along fine. Not very likely that Apple would update their OS and break their pro apps in the process.

Zky · Post by **Zky** » Fri Feb 11, 2005 5:29 am

ok guys.. so all of u consider this update is safe both for the pb and ableton? working with no prob??

any noticeable improvements?

last time I had to back to 10.3.6 and I do not want to go thru the same shit again..

Hardtoe · Post by **Hardtoe** » Fri Feb 11, 2005 8:14 am

Yo,

BEWARE & CAUTION - If you have the macally ishock driver it can use most of your cpu and fill your startup drive with meaningless crap....I had 9 gigs filled with bad "log" info which it took me 2 hours to unravel and delete. For instructions on a fix see http://discussions.info.apple.com/ under the panther / install / "osx10.3.8=rapidly dissappearing harddrive space" thread. Also I still have the fucking Live 4 / motu 828 audio "glitch" which fucks up my timing when I'm mixing with my partner...

Good Luck

Orion

Zky · Post by **Zky** » Fri Feb 11, 2005 10:54 am

yes..checking the apple site,,seems that people are more confused than pleased with this update...

question is,, it is really worth do to the upgrade for us the audio users??.. because if it's just to improve safari and other stuff like that I don't see why to risk a somewhat stable system..

still more to come I think..we'll see..