Rebooting in Open Firmware

I have a MacBook, with 10.5, and I've noticed that these MacBooks can no longer boot up in open apple firmware by holding down COMMAND-OPTION-O-F. I've tried it on two MacBooks and it didn't work on either. Is this a MacBook thing? Or a Leopard thing?

It's a Macbook, or more specifically, a Intel-based Mac, thing. Open Firmware is a PowerPC only thing, so that command is no longer used.

Similar Messages

Beige G3 boot from **** problem; open firmware issues; bad motherboard?

Dear all,
I'm having huge boot/startup problems with my beige G3 that had been happily running OSX 10.3.9, but for purposes of this discussion we can (mostly) revert to OS 9. Originally, the machine was a G3 @300; was upgraded more than a year ago to a ZIF G4 @500.
To make a long story short, it won't boot from any hard drives, will not boot from any OS X CD, and will only occasionally boot from a 9.x startup CD (whether Apple or Norton Utilities). I think it's an open firmware issue, possibly caused by a bad motherboard (rev. 2).
All this started happening after I used techtool pro, but I think that's coincidence (even though I acknowledge that, for cops and computer users, there are no coincidences.) Also, as discussed below, I'm having the same problems with an HD that wasn't even in the computer when all these things began.
Here are some of the things I've done.
--repeatedly reset PRAM, both with key combinations and removing battery. The only time it will boot from a 9.x CD is after resetting PRAM.
--removed all add-on PCI cards.
--removed additional VRAM
--removed all memory cards and tried replacing one at a time.
--disconnected both existing hard drives and replaced with an older OS 9.x hard drive (approx 60 mb) that I'd used before. Also tried different ribbon cables.
--unplugged floppy drive
--disconnected PCI ATA disk controller that I'd been using for running a large (1.8 gb) hard drive.
--regarding open firmware: readenv usually shows totally normal default AND installed settings. Using reset-all works fine -- at least it makes the machine reboot, but doesn't solve the problem. reset-nvram does NOT work -- says it's an "unknown word."
--using startup keys like holding down the option key, or shift key, or X key or cmd-option plus two others I can't remember, has no effect. Again, after I've tried any kind of reboot, the ONLY way to get the C-key at startup to boot the CD is by resetting the pram (key combination). Otherwise, the usual result of these experiments is a dark screen on startup -- nothing at all (and the LCD monitor tells me "no input.")
--regarding OSX: sometimes (and I emphasize sometimes) I can get the machine to start booting from an OSX 10.2 CD, but it won't complete the process. Sometimes I get a "prohibited" (as in no-parking, no-smoking) icon; sometimes it will start booting (grey screen, OS X Apple icon), then crash (horizontal grey and white jagged bars); sometimes it will show the OS 9 start icon (the tiny smiling Mac SE), but not boot at all.
--when I get the mac successfully booted with an OS 9.x CD (again, this works sometimes, but not always), the old hard drive with two partitions does show on the desktop and can be accessed. Using either disk repair or Norton Utilities shows the 9.2 system partition on the hard drive to be fine. But if I go to the startup disk control panel, confidently set the 9.2 partition as my startup disk, then reboot, there's no change. It won't boot and I'm back at square one.
--even when I do get successfully booted with 9.x, the machine will still occasionally crash for no reason -- ie when I'm moving a Window.
--the only thing I haven't done is slowed down the processor. It's a ZIF G4 bought more than a year ago from XLR8 your Mac. I'm running at the default 500 mhz, and it's never given me any trouble.
So I think it's a bad motherboard or ROM. Thoughts?
Thanks.

The beige Mac is now operating happily again. My original tentative diagnosis remains the same (although still tentative): corrupted PRAM from bad battery, compounded by bad cables that wrote corrupted data to hard drives, and also (possibly) allowing Tech Tool Pro (a utility that I now regard with deep suspicion) to create a "virtual" startup partition.
A few things I've learned along the way that hopefully may be useful:
--remember that the Ex Post Facto utility can be used to help OS X startup, not just installation. This applies to hard drives, emergency CDs, installation CDs, etc. If you can boot into any working hard drive partition (OS 9 or a backup OS 10), then run Ex Post Facto (same program runs on either OS 9 or X -- don't ask me how) and tell it what system you want to start up from. Also, the utility has sometimes told me that the startup extensions on the disc that I wanted to boot up from were bad, and offered to fix them (which works).
--at least on my Mac (beige, v. 2 motherboard), resetting the CUDA button, resetting the PRAM, resetting Open Firmware and "draining" the memory by unplugging the computer and disconnecting the battery for several hours ALL DO DIFFERENT THINGS.
Specifically, if I'm having trouble booting (from a hard drive or a CD), the FIRST thing I do is restart and resetting the PRAM on the fly -- holding down command, option, P and R at startup, and waiting for the chimes (preferably at least 3-4 times).
If I do that and DON'T hear the chimes, that's my cue for my SECOND action -- restarting into open firmware (command, option O and F keys on startup). That should bring up the black text on white background open firmware screen. View other posts or apple support for details, but if you do PRINTENV and see a bunch of weird gibberish after the default/installed lists, you know that it was messed up and you need to clear it through reset nvram and reset all commands. Be aware some of these commands do or do not work depending upon what version of Open Firmware you have.
After I've rebooted with Open Firmware, then on restart I should be able to reset the PRAM on the fly. If that works, then either let the machine run and see what happens, or hold down the C command and see if it will boot from the CD
Usually, if I've fixed everything as above, the machine will boot into whatever version of OS 9 it finds on a hard drive. That's fine with me -- at that point, use Ex Post Facto to reboot into your OS X. (Before I forget: I used the shareware startup CD creator program BootCD to make an emergency boot CD based on OS 10.2.8 (which theoretically will support a beige mac in native fashion) and Disk Warrior, the god of disk repair utilities. Even though the CD should boot just by holding down the C key on startup, it doesn't -- but if I use Ex Post Facto to boot it, no problems (although the process is very slow -- be patient). Then I can fix almost anything using Disk Warrior.)
If none of the above works, then I'll try resetting the CUDA (on my beige minitower, it's a very small black button inconveniently located between a PCI slot and the side of the computer housing). Hold it down for 15 seconds. That should REALLY clear the PRAM. I know this does something different from the previous steps because this is the only action (except the battery disconnect -- next) that clears the date and time from the memory.
If all else fails, I will unplug the computer and disconnect the battery, then push the CUDA button for 15 seconds and let the machine sit overnight.
One final finding -- I thought I'd fixed everything, but both my hard drives suddenly quit working, I discovered that during all this repeated connect/disconnect of things, one of the male pins inside one of the connectors on my Acard ATA PCI card had broken off. Not good. Fortunately, the card had a second connector, which works fine. And I did some extensive shaking of the computer to make sure (I hope) that the broken pin hadn't landed on a circuit board.
All this took more than two weeks, and the advice of this board was much appreciated. Now I'm on to my next adventure -- trying to figure out why a combo Firewire/USB PCI card won't mount an external drive on Firewire, but will on USB. I've tried two cards with same result -- but a Firewire-only card works just fine.)
Regards to all,
Graham

PowerBook G4 boots to Open Firmware without keyboard access

Summary:
Let me provide a little backstory.
According to the [DARPA Visitor Guidelines|http://www.darpa.mil/body/visitor_guidelines.html] wireless network technology is prohibited from DARPA facilities. Laptops with a wireless card are required to be "disabled at the BIOS level".
Before an upcoming visit to DARPA I was told that I would need to make sure my laptop wireless card was disabled. I mentioned that Macs don't have BIOS but I'd look into doing it in Open Firmware. The response from DARPA was that no one has ever successfully brought an Apple laptop into the facility, and that I should procure a PC laptop for my visit. Ah, a challenge!
I booted into Open Firmware (⌘⌥OF), located the wireless card in the device tree, and removed two properties I figured the driver would be searching for: the vendor ID, and the product ID. I exited Open Firmware and continued to boot into Mac OS X v10.5.2.
Sure enough the System Profiler showed that no wireless card was installed. Success! Now I just need to make the device tree modifications persist between reboots.
It seemed the solution was to place the Open Firmware commands I issued to disable the card into nvramrc. So I set nvramrc to contain the same commands, and set use-nvramrc? to be true. I rebooted the machine but the card was still detected.
A bit [more research|http://docs.sun.com/app/docs/doc/805-4436/6j4719c8v?a=view] revealed that the device tree is not created by Open Firmware until after the nvramrc is executed. The solution is to build the device tree in the nvramrc and tell Open Firmware not to rebuild it. The documentation states that this is accomplished with the probe-all, install-console, and banner Forth commands. I added those commands to my nvramrc and rebooted. The contents of nvramrc:
probe-all install-console banner
dev wireless
" device-id" delete-property
" vendor-id" delete-property
The outcome... well technically the laptop has wireless disabled. Almost everything is disabled. The machine now boots directly into Open Firmware with a few ominous bits of output and no response from the keyboard.
no active package
Apple PowerBook5,6 6.4.9.1f1 BootROM built on 01/21/05 at 10:51:16
Copyright 1994-2005 Apple Computer, Inc.
All Rights Reserved.
Welcome to Open Firmware, the system time and date is 05/06/2008 10:00:00
Command security mode
To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.
ok
0 > _
The first sign that something has gone wrong is no active package. The second message just throws another wrench into the works: Command security mode. Yes, the Open Firmware password was enabled. In retrospect this was a bad thing to have set when mucking about in OF. I knew of the RAM change trick (see below) so this was not an issue at the time.
Question:
So the question is: What actions do I need to take to return the laptop to a useable state. That is, booting into Mac OS X.
*Attempted solutions:*
+1. Reset nvram+
The first and most obvious solution is to reset nvram using the snag key combination ⌘⌥PR. Unfortunately do to the firmware password being set, [all snag keys have been disabled|http://support.apple.com/kb/HT1352]. This means no target disk mode (⌘T), boot from CD (⌘C), boot from network (⌘N), etc... In any case an attempt at resetting nvram yields an additional message being appended to the Open Firmware screen:
Release keys to continue!_
+2. Reset nvram after changing amount RAM in system+
Luckily there is a work-around to firmware password protection. Changing the amount of RAM installed in the machine should allow the nvram zap snag to function. I removed one of the two 512MB DIMMS in the laptop and started up while holding down ⌘⌥PR. This results in the same message as above:
Release keys to continue!_
Not so lucky.
+3. Reset the Power Management Unit+
[Resetting the Power Management (PMU)|http://docs.info.apple.com/article.html?artnum=14449] is accomplished by removing the battery and disconnecting the power cord, and then holding down the power button for about 5 seconds. This had no effect besides resetting the system clock to 01/01/1904 00:00:41.
Getting more desperate...
+4. Search logic board for CUDA+
I [opened the machine|http://www.ifixit.com/Guide/Mac/PowerBook-G4-Al-15-Inch-1-5-1-67-BT-2-0 -LR/64] to search for a hidden [CUDA button|http://docs.info.apple.com/article.html?artnum=86760]. As expected, a CUDA button does not exist on this model and the PMU reset is accomplished as noted in attempted solution 3.
+5. Remove internal battery+
Well the laptop is open now, so I tried removing the internal memory backup battery and revisited each of the above solutions. No success.
+6. Remove hard drive+
Again, since the laptop was open, why not remove the hard drive and see what happens. The machine wasn't even making it to the boot-loader hand-off so I didn't expect this to produce any results. No results produced.
Thinking crazy thoughts...
+7. Attempt a firmware update+
Firmware updates have a side effect of resetting the nvram. Also firmware updates are initiated very early in the startup process by holding down the power button until a tone is heard and the power light flashes. My thought was that I would grab a previous firmware update for this laptop and force it to be reapplied. Unfortunately there have been no updates to this model's firmware.
+8. Write my own firmware update script+
While investigating solution #7 I realized that the file BootROMFirmware installed by the firmware updaters for G5s and G4s machines are just Forth programs with a binary payload attached to the end. I learned [Forth|http://en.wikipedia.org/wiki/Forth(programminglanguage)]. The BootROMFirmware files are really cool, since they do everything from drawing the progress bar during the update, uncompressing and check-summing the binary payload, and generally making sure you don't brick your machine. In any case it seem entirely doable to write my own program in Forth and undo the evil I did before. I really only need to flip one bit. I needed the use-nvramrc? variable set to false. So I created this very simple Forth program:
\ debrickifier
setenv use-nvramrc? false
reset-all
The original firmware file had additional attributes set, a creator and file type of fw99. So I set those two attributes on my file as well. I ran strings on the firmware installer program and guessed that it was copying the file to /System/Library/CoreServices. So this is where I placed my Forth file. Reinstalled the drive and rebooted the laptop while holding down the power key to initiate a firmware install. No dice.
Its hard to tell why this is failing. The file may in the wrong place, have the wrong permissions. From what I've reviewed in the original files, the setenv and reset-all words should be available. Maybe the Firmware Update utilities are setting some other magic in nvram before the reboot.
I think I've covered all the different major solutions that I've attempted. Their might be a few more that I've forgotten to mention (like using an external USB keyboard). I still think that getting some Forth to execute via the firmware update mechanism could use some more exploration. My current worst case is that I'll replace the logic board, although I'd hate to do that when I know there are only a few bad bits flipped in a CMOS somewhere.
I'm hoping to snag the attention of the resident hardware/firmware guru that can shed some light upon the firmware update process, but any help or suggestions would be greatly appreciated.
Cheers,
Mark

For your next DARPA visit, another option might be to buy the cheapest possible third-party wireless card — it doesn't even need to work. Insert it into your Powerbook's CardBus slot before visiting DARPA, and turn Airport off in System Prefs. On arrival at DARPA, remove the card from the Powerbook and hand it to the security guard. Retrieve it from the guard as you leave, and turn Airport back on again when you get home or back to your office. Unable to comply with the letter of the dunderheaded regulation because you have no BIOS, you will be complying with the spirit of it instead, and no one will be the wiser.

Can't reset Open Firmware!

I have a 1GHz titanium, and it has the 'sleep of death' problem - blank screen on opening the lid from sleep. (Only happens intermittently.) It has several other 'issues' lately that are driving me nuts, but one at a time. I would like to reset the open firmware, however on this machine, when I hold cmd-option-o-f on restart it does nothing. Literally.
The machine reboots, then sits there with a blank screen. Nothing happening.
If I release the keys, it does not go into a startup, it just sits there - note the fan is making a slight noise, so technically it is not 'off', however I have to hold down the power key and restart that way.
Is there a way around this? Not a software issue, as all this happens (or rather, doesn't happen!) before anything loads.
-frustrated
Powerbook G4 Mac OS X (10.3.9) Titanium 15" Powerbook 1GHz Superdrive

Are you able to do a pram reset? (command-option-p-r). If so, do this 3 times and then attempt to go immediately into an open firmware reset.
About the sleep issue, I had also had that problem. I performed a reset that has cleared that issue (hopefully permanently). My computer is a little different but I believe the procedure is similar. I would consult the knowledge base to see what the procedure is for doing a reset. In my case, I basically held down the reset button (located next to my modem port) without the battery out and the power cord unplugged.
Hope that helps.

How can I reset the open firmware password?

I wanted to installed Mac OS X Lion from scratch on my newly purchased MBP 15,4"
I put the installESD.dmg on a USB pendrive, then I boot on it. I used Disk utility to erase en encrypte my drive, and at the same time I set the Open firmware password.
I launched the installation process, after a while the computer reboot but I got an error:
there was a problem installing mac os x try reinstalling
I google this error and found many people who solved this issue by erasing the PRAM using the shortcut: cmd + opt + P + R. I'm asked to enter the password which I did but it's still keeping asking for the password so I guess its wrong which is weird cause I typed it in few minutes ago, so I might have done twice a typing error or I don't know.
So my question is how can I reset this password to be able to install my OS? (I cannot access to any OS cause the installation process failed).
Thnak you for your help

Yes I did use the disk utility to restore the dmg on my USB drive. The USB drive is perfectly fine, I can boot on it without any problem, well before setting this open firmware password I could do it.
Now the situation is:
No system installed,
Lock with a password
I have the disk to install SL but I cannot boot on the DVD because it is asking me for this password.

IBook intermittently boots then resets or only starts in open firmware

Hi everyone,
I've been using my iBook G4 (aka my baby ) since purchasing in feb 06. Never had an issue with it, treated it better than anything else I've ever had and it give me trouble. until now.
basically after shutting it donw friday evening i tried to start it up yesterday and when it reached log in, I did so and go a black box center screen informing me to restart by holding down the power button. Each log in attempt (sometimes this occured when the 'starting MAC OS X' popup appeared) gave this problem. Eventually I could log in albeit for 2 mins before the 'please restart'.
I checked the Apple hardware test and extended test showed no issues. I then couldn't tried to boot up but was presented with the 'folder/ ? mark' icon. So, using install discs I tried a disk repair as per Apple manual and it did get one illegal case which was then repaired.
Rebooting then presented me with a white screen with the words 'open firmware.....illegal instruction at %SRR0' date and time included. last words were reducing power 'type Mac-boot' to boot; 'shut-down' to shut down.
mac-boot just brings me to the folder icon. What is funny is that if i switch it off for 30 mins or so and try again, i can log in although not for long.
last night a friend accessed my HD using targetted firewire mode and backed up my data so that's all covered. After he did this i booted up to show him the problem and it worked fine. in fact we had several iTunes vids running, my iPhoto library open and it worked fine. Even the CPU load was nothing to cause concern. So I rebooted and......open firmware.
has anyone here had this same issue with an iBook and knows what the root of the issue is? I've seen some reports of Airport drivers etc etc but nothing changed from Saturday to Sunday. no updates, no new software.
Worst thing is that it's only just over 1 year old and is not in warranty. I'm taking it to an authorized apple service place tonight but any input for you guys on here would be me much appreciated.
Thanks,
Phill
p.S Sorry for the long post, just wanted to include all info.
iBook g4 14 inch, 1Bg RAM, 80Gb HD Mac OS X (10.4.8)

hi Phill,
I saw your posting, and I seem to be having a similar problem with my powerbook. Did you ever solve your issues?

Problem free ibook now can only boot 'open firmware,' help please!

I reasently went to play with my ibook, just opening it from stand by mode and it popped on but everything was frozen for some reason. So i ended up forcing it off and rebooting it only to find that it only wants to boot open firmware. I tried reseting the nvram but that didn't do anything either. What should I do?

You could see if it will boot into Safe Mode. This will take quite awhile longer than a normal startup because it does a file check and repair of the hard disk.
If this works you will see your normal desktop. Once completely started up in Safe Mode, try to restart normally, and go to Applications > Utilities > Disk Utility. Click on the top hard drive icon in the left sidebar and note the S.M.A.R.T. status at the bottom right of the pane. What does it say?
Select the named boot volume in the left sidebar, ("Macintosh HD" unless you've renamed it). What is the hard drive capacity and how much space remains available on it? Repair permissions on it.
See if you are able to do a little hard drive maintenance to help things out.

Open Firmware Password Doesn't Work

I've been using O.F.P. v 1.05 on both my computers for over a year. All has been well until recently. Now when I reboot holding down the option key I either get the O.F.P. screen without the password line so I can choose any bootable disk or I get the password line, but when I enter the password nothing happens and I have to reboot normally.
Both computers running 10.4.3 with all latest updates.
What's going on?

Well, I just searched the Apple Support Knowledge Base and found this text here at http://docs.info.apple.com/article.html?artnum=106482. In the section "How to enable the Open Firmware Password" it says right in the first paragraph:
1. For Mac OS X 10.1 to 10.3.9, Download and Install the Open Firmware Password application, which you can get here. For Mac OS X 10.4 or later, you must use the updated version that can be copied from the software installation disc (located at /Applications/Utilities/ on the disc).
The link for version prior to 10.4.x leads to OFP 1.0.2, so 1.0.5 might already be the updated version that ships with Tiger. I can not check right now because I am not at home where my copy of Tiger is; maybe others can check it in the meantime.
If you not already have done so, maybe you could try to update 10.4.x to the latest version (which is 10.4.3) and get all other available patches as well, just to make sure.
Regards
Jim
AiPB 15 1,25 GHz;; iMac 17 1 GHz (flat panel) Mac OS X (10.4.3)
UPDATE: And I doublechecked that I am indeed running version 1.1 (1) of OFP on my installation. I am not aware of having it updated manually, so it must either have been this all along since I installed Tiger or been updated in the procress.
Message was edited by: Jim Knopf

Open Firmware Can't boot my WinXP install disc (although the OS sees it)

So I've been unable to play ANY games on my MacBook Pro under Crossover (games that worked fine under my old 1.8Ghz MacBook Pro) because I get all sorts of weird graphical rendering issues.
So I thought I'd reboot into windows, install the games there, and see if the problems were related to Crossover or not.
So I launch Bootcamp Assistant to install Windows XP. I pop in the Windows XP disc (under MacOSX) and I see the disc and all the installer files, and I click to reboot into the Windows installer.
The laptop reboots and when it comes up I can hear it trying to read the cd. I can hear it switching speedings up and down and moving the read headers. But it never starts the installer, instead it spits out the disc and prompts me to insert a bootable disc.
Problem is I know this disc works. I've used it many times. And back over under MacOSX it reads the disc just fine.
So I know this "new" laptop I got from work was actually refurbished, and I think they messed with it. Specifically I wonder if they mess with the open firmware. Because again, MacOSX (the software) could see and read the disc just fine. But when I'm in the open firmware loader it can't read the disc.
Also, if I hold down Option at boot time, I get the option to select my WindowsXP disc because it sees it, but again, it can't load it...
Is this a 32-bit/64-bit issue? I don't know. All I know is I can't boot my XP CD to install XP....
Is there a way for me to reinstall the open firmware?

I've now tried my buddy's WindowsXP SP2 disc and the first time, it loaded the windows installer (boot and held down Option and selected the disc) but the install failed. On reboot the windows partition will not boot.
So I tried again, and now his disc and responding the same way my disc responds.
I reboot, hold down Option, select the Windows XP disc, and then the screen goes black. I hear it trying different speeds to read the disc, then finally it stops and spits the disc back out and tells me to insert a bootable disc.
So that's two separate WindowsXP install discs. Both are known to work.
So why can this drive see the disk and files just fine under MacOSX -but not- under the EFI bootloader?? And yes I've tried resetting the NVRAM/PRAM.
Message was edited by: general_error

Zap PRAM with Open Firmware Password?

I'm wondering if there is any way to do this...
I have an older MacBook that had some kind of issue recently, that first prevented it from booting at all, and after resetting the SMC it would boot but the screen is black...
I remember from many years ago that there was an issue with the screen staying black that would be fixed by zapping the pram...
Problem is the system has an Open Firmware password. And while I do know what that passowrd is, it's kind of impossible to go in and disble it with a black screen...
In essense, is there any possible way I can zap the PRAM that doesn't involve psychicly guessing what I'm doing???

I'm fully aware of the key combination. The problem is when Open Firmware password is enabled, holding CMD-OPT-P-R has no effect.... The only way I know to be able to use the key combiantion is to disalbe the Open Firmware password first, then reboot and hold hte keys down.
Which is where my problem lies, as I can't zap the PRAM until I disable my Open Firmware password, and I can't go though the steps to disable my Open Firmware password until after I zap the PRAM in order to re-enable my screen...

Safe Mode & Open Firmware Password

I have the Open Firmware Password enabled, which prevents my machine from booting into Safe Mode when I hold the shift key at startup (as expected). As a result, if I want to use Safe Mode, I have to boot up from my install DVD, disable the password and then reboot. Very tiime consuming!
I just read about an Apple Support document about a way to boot into Safe Mode by entering the following terminal command:
sudo nvram boot-args="-x"
Has anyone tried this before? I'm a little hesitant to test it out in case I run into some sort of Open Firmware/Safe Mode conflict.

Try booting while holding the Option key. It should ask for the firmware password, then let you use boot modifier keys.

Start-up problems, black screen or open firmware

My iBook G4 1.33GHz Dual USB, with 1 gb RAM memory has been troublesome lately. It's installed with the latest version of OS 10.4.9
When starting up the ibook, it will sometimes only show a black screen after the boot chime. Repeated force restart sometimes makes it boot up the open firmware (white screen).
Then I see the error message:
"Illegal instructions at: %SRR0:ff85e778 %SRR1:00081000"
When I continue on with "mac-boot", I get the blue screen with a question marked box. So it can't find the startup disk.
This usually only happens when I'm done working for the day and close the lid on my ibook without manually clicking on the sleep mode when I put in in my drawer,. I've seen several times that the screen is still on when I close the lid, so it will continue to burn battery time.
I've managed to get the ibook to boot properly after removing the battery and letting it "cool-down" for 15-20 min. Also, zapping pram, vram sometimes works, but I don't know how much that actually helped. It worked once when I typed in the reset-nvram in the open firmware screen too.
I'd rather not have this happen at all! Any suggestions? Is this the much-talked about RAM memory failure?
Any suggestions would be very appreciated.
Message was edited by: antony chen

HI,
*"I get the blue screen with a question marked box."*
That can mean several things. One, the drive is failing. Two, your iBook can't find a System Folder to boot from. Try booting while holding down the Option key which will prompt the Startup Manager window.
MemTest
Boot from your install disk and check the hard disk for errors.
Insert Installer disk and Restart, holding down the "C" key until grey Apple appears.
Go to Installer menu (Panther and earlier) or Utilities menu (Tiger and later) and launch Disk Utility.
Select your HDD (manufacturer ID) in the left panel.
Select First Aid in the Main panel.
(Check S.M.A.R.T Status of HDD at the bottom of right panel. It should say: Verified)
Click Repair Disk on the bottom right.
If DU reports disk does not need repairs quit DU and restart.
If DU reports errors Repair again and again until DU reports disk is repaired.
When you are finished with DU, from the Menu Bar, select Utilities/Startup Manager.
Select your start up disk and click Restart
While you have the Disk Utility window open, look at the bottom of the window where you see Capacity and Available. Make sure there is always 15% free disk space. Not enough disk space can cause directory corruption.
If you cannot boot from your install disk, try booting in Safe Mode
A flashing question mark appears when you start your Mac
Carolyn

I am having a Startup problem. Someone comes on the screen with Open Firmware to Startup. How can I reset the PRAM myself to solve this problem?

I am having a Startup problem. Someone comes on the screen with Open Firmware to Startup. How can I reset the PRAM myself to solve this problem?

Read these.
http://support.apple.com/kb/HT1431
http://reviews.cnet.com/8301-13727_7-10330118-263.html

Start-up Problem - White Screen Open Firmware

Hi
Just turned my eMAc on and got a new beeping sound, the little light on the front flashed several times and then the screen went completely white with the following message;
Apple PowerMac 6,4 4.8.2f1 BootROM built on 03/11/04 at 09:18:55
Copyroght 1994 - 2004 Apple Computer, Inc.
All Rights Reserved
Welcome to Open Firmware, the system time and date is: 07:26:35 10/20/2006
To continue booting, type "mac-boot" and press return
To shut down, type "shut-down" and press return
ok
0 >
I typed in 'mac-boot' and return and everything starts and 'appears' to work as normal.
I have shut down and restarted twice and the same thing happens. I also noticed that the push button switch seems to be sticking.
My question is - Is this a hardware issue (the start button is faulty) or is it a software (firmware, corrupt file)?
Many thanks for help and advice
Mick

It's possible it's a hardware problem, but first I'd suggest you try resetting Open Firmware:
At the 0 > prompt, type:
reset-nvram
and press Return
At the 0 > prompt, type:
set-defaults
and press Return
At the 0 > prompt, type:
reset-all
and press Return.
With luck, that will clear things and you'll be back to booting normally.
Hope this helps.

Long tone on start up and then goes into open firmware

I stumbled upon the older posts here and thought I'd add a solution.
http://discussions.apple.com/thread.jspa?messageID=6115258
It was about an emac starting up with a long tone and the led flashes a few times and then goes into Open firmware, and when doing "mac-boot" in open firmware, it attempts to start, shows the apple symbol, the screen goes dim and crashes.
It could be a bad power switch. To confirm - you can remove the emac case, be careful not to touch the motitor's picture tube. Find the cable to the power switch; with a small wire just touch together the black and red wires on the power switch cable (or it might be red and green). This will start the emac. If it boots up and runs OK then the power switch was bad. Not sure where to buy a new switch. I soldered and glued my switch together.
<Edited by Moderator>

Or, you'll find both the short pigtail-cabled nVidia graphics driven power switch and the version with a longer cable used with the AIT graphics driven models here* for a good deal less.
Note that the later ATI version can actually be used with either product generation.
*I may receive compensation as a result of parts or services being ordered by users specified at the link shown in this message.

Rebooting in Open Firmware

Similar Messages

Maybe you are looking for