Author Topic: Firmware (Read 4378 times)

Buck · « **on:** October 07, 2006, 07:29:56 PM »

Can anybody tell me the key combo for re-set the Firmware on my e-Mac?
Thanks, Buck

kbeartx · « **Reply #1 on:** October 07, 2006, 08:11:23 PM »

Buck -

I'm not sure what you want, or think you want to do.

Firmware is data that is stored in an EPROM chip, and it's something you might upgrade, but not reset...

Are you thinking of zapping the PRAM? That is Command-Option-P-R held immediately after the startup chime, until the chime has sounded five times in all.

gunug · « **Reply #2 on:** October 08, 2006, 02:18:14 PM »

To get into the Open Firmware on that machine you hold down Command-Option-O-F (for open firmware) when it's booting up and you should go into a sort of text mode which ends in a prompt with "OK." When you get that you should type the following:

reset-nvram <enter>

another "OK"

reset-all

and the thing should reboot! If you're having problems getting it to boot off a particular drive (should you have more than one volume) you can reboot while holding down the option key by itself and you will be given a choice of bootable volumes that the open firmware finds!

Buck · « **Reply #3 on:** October 09, 2006, 07:39:52 PM »

QUOTE(gunug @ Oct 8 2006, 03:18 PM) <{POST_SNAPBACK}>

To get into the Open Firmware on that machine you hold down Command-Option-O-F (for open firmware) when it's booting up and you should go into a sort of text mode which ends in a prompt with "OK." When you get that you should type the following:

reset-nvram <enter>

another "OK"

reset-all

and the thing should reboot! If you're having problems getting it to boot off a particular drive (should you have more than one volume) you can reboot while holding down the option key by itself and you will be given a choice of bootable volumes that the open firmware finds!

I wasn't sure of the key strokes. You conffermed that I was doing it correctly.
So here's. the problem.
When resetting the firmware. I get a (word unknown) when I type (reset-nvram).
Ever hear of this happening? Thanks, Buck

gunug · « **Reply #4 on:** October 09, 2006, 10:05:54 PM »

I can try it on an eMAC tomorrow if you would like me to do so. I would say that Open Firmware could be messed up and you could "update" the firmware if it is messed up! It could also be that you didn't type it correctly (it should be "reset-nvram" with no spaces between)!

Buck · « **Reply #5 on:** October 10, 2006, 02:23:04 AM »

QUOTE(gunug @ Oct 9 2006, 11:05 PM) <{POST_SNAPBACK}>

I can try it on an eMAC tomorrow if you would like me to do so. I would say that Open Firmware could be messed up and you could "update" the firmware if it is messed up! It could also be that you didn't type it correctly (it should be "reset-nvram" with no spaces between)!

I do have it typed correctly.
I have had to reset my firmware in the past.
Things went fine then. Buck

gunug · « **Reply #6 on:** October 10, 2006, 09:56:58 AM »

Buck - For what it's worth I just went into Open Firmware on an eMAC and everything worked just like it did on a Powermac or iMAC or whatever else I've ever worked with. It also looks like there are no updated Open Firmware for eMAC's on the website. The reset is actually the "reset-all" command so maybe it doesn't matter. Why are you trying to do the reset; what problem are you trying to solve?

QUOTE

Try resetting the computer by typing "reset-all" at the Open Firmware prompt. If this does not seem to make a difference, the fault maybe hardware related. Typically, a defective processor card causes these types of symptoms.

I just read something on the Apple Service Source website about someone who had been experimenting with a Linux on their computer and got a similar message in the Open Firmware to what you're getting. They mentioned "resetting the PRAM" as a possible cure: Command-Option-P-R.

Xairbusdriver · « **Reply #7 on:** October 10, 2006, 10:36:00 AM »

QUOTE

I do have it typed correctly.

How many times have I said that only to discovered ( or worse, have it pointed out! ) that I actually only thought I had typed it correctly.

Since you are basically in the Terminal, you have to be absolutely, positively, 100% correct. You will never win an argument with the Terminal by claiming you have done something correctly and "it" is broken.

As a tip for showing input in Terminal ( and just about any other program ), I'd suggest setting the font to one that shows lower case "L" differently than the number "1". It is also great to have one that makes the letter "O" and the number "0" easily recognizable. Of the choices available here, I tend to use Courier ( because I can remember and spell it in FastReply!

).

Thus, the suggested commands to enter when in Open Firmware are:
reset-nvram <enter>

[response on screen] "OK"

reset-all

Buck · « **Reply #8 on:** October 10, 2006, 12:24:24 PM »

QUOTE(gunug @ Oct 10 2006, 10:56 AM) <{POST_SNAPBACK}>

Buck - For what it's worth I just went into Open Firmware on an eMAC and everything worked just like it did on a Powermac or iMAC or whatever else I've ever worked with. It also looks like there are no updated Open Firmware for eMAC's on the website. The reset is actually the "reset-all" command so maybe it doesn't matter. Why are you trying to do the reset; what problem are you trying to solve?
I just read something on the Apple Service Source website about someone who had been experimenting with a Linux on their computer and got a similar message in the Open Firmware to what you're getting. They mentioned "resetting the PRAM" as a possible cure: Command-Option-P-R.

Thanks for the help. I no longer had a problem.
Problem solved. I hope.
Ya'll have great day. Buck

Xairbusdriver · « **Reply #9 on:** October 10, 2006, 05:40:29 PM »

Buck, we're all glad you solved the problem, but we depend on people to share their success by telling how the problem was solved, especially, if none of the suggestions offered were resposible. Please let us know how you solved the problem.

Buck · « **Reply #10 on:** October 16, 2006, 05:06:54 PM »

All I did was to copy-paste Gunug's sample: reset-nvram.
And it worked. Even though I typed the very same over and again. Go figure.
Goes to show one never knows how a problem will get solved if at all.
Have a great day, Buck

Xairbusdriver · « **Reply #11 on:** October 16, 2006, 09:09:22 PM »

OK! Another "Save" for gunug! And thanks for clearing up the mystery!

BTW, how far from Loafer's Glory ( home of <weldiger> ) is Kings Mountain?

Buck · « **Reply #12 on:** October 21, 2006, 05:42:21 AM »

QUOTE(airbusdriver @ Oct 16 2006, 10:09 PM) <{POST_SNAPBACK}>

OK! Another "Save" for gunug! And thanks for clearing up the mystery!

BTW, how far from Loafer's Glory ( home of <weldiger> ) is Kings Mountain?

About 115 mi, North West of K.M.

Xairbusdriver · « **Reply #13 on:** October 21, 2006, 09:31:18 AM »

OK!

BTW, did you know that there is a "TS" Frappr Map? Unfortunately, it appears that Flash is now required, the map can no longer show as much of the world as previously, the page must be much wider to keep from scrolling horizontally and it is now tightly linked to a bunch of "My..." junque. It's still Beta and free, so what should I expect. I must apologize for not visiting it more, I discovered that at some point 'our' map became visible to the public list of maps, that might explain some of the SPAM the board/members got with TS spoofed addresses. My bad!

sokukodo · « **Reply #14 on:** October 23, 2006, 09:52:17 AM »

But, how does one know when the firmware should be re-set? Or zapping the pram, for that matter. I do these things once in a blue moon, but only because I think I should; I mean, it's never hurt to run the checks.

Richard

News:

Author Topic: Firmware (Read 4378 times)