Starts in Open Firmware. No OS

Short story,
When I turn on the Pismo, I get open firmware. I beleive the Hard Drive was formatted, and maybe partitioned eternally through a PC program called Macdrive. I have the software Restore Disc, and the software Install Disc. Neither will boot. I have reset the Pram, and Nvram through open firmware. All i get is a blinking '?' on Boot. How can i install the OS 9 back on this Mac?
Long Story,
I was given two G3 Pismo's and told to wipe them clean, and donate them. They would not powerup, as they had been sitting a long time. I took the hard drives out, and cleaned them (deleted files that seemed private) with a PC program called Macdrive. I then learned to Unplug the Pram Battery and this would powerup the Mac, and then boot to OS 9.1. I can't remember, but I may have used Macdrive to Reformat and/or Repartition the Hard drive.
I then became hooked on Mac, and decided to keep one of them. Now when I power it up, I end up getting open firmware, and I cannot boot into OS 9.1 I'm not familiar with Mac Commands, so how can I boot from the Software CD?
Holding down C while powerup does not work.

slow horse,
Until the issue of why you are booting into OF is solved, installing a fresh OS on the HD will not help; the boot into OF occurs long before any software loads. A normal cold start will produce the startup chime, then the raster (gray screen), then either a flashing '?' (no bootable volume found) or it starts to load the OS. I don't know why you are getting into OF. If the powerbook worked normally before you removed the HD, remove it again (and leave it out), then see if you can start to a normal startup chime and get to the flashing '?'. If you can, then see if it will boot a CD. If this is a successful test, then something may be wrong with the HD and/or HD ribbon cable.
However, assuming you solve the OF issue, this article discusses the differences between the Restore CD and the System Install CD. You should be able to boot to either barring any hardware problem.
http://docs.info.apple.com/article.html?artnum=31204
If you cannot boot to the CDs, you can connect the Pismo to your iBook via FireWire Target Disk Mode:
http://docs.info.apple.com/article.html?artnum=58583
You of course can also remove the HD, place it in an external FireWire or USB HD case and install software from the iBook.
If you have access to a FireWire CDRW or DVD burner, you can in most cases boot to a CD or DVD when connecting to the Pismo's FireWire port. Use the option key startup in this case.
If you connect to an iBook, you will not be able to use your Powerbook G3 Software CDs; the installer on the Powerbook CD sees an iBook, not a Pismo. If connected via FireWire Target Disk Mode, the Pismo is seen as just another external HD, nothing else. Depending on which version iBook you have, you can follow one of two procedures, and both will work regardless of how you connect the Pismo's HD to the iBook.
1. If the Pismo's HD mounts on the iBook's desktop, use 9.x's Drive Setup to initialize the HD; this will also automatically update the HD driver. If using 10.x's Disk Utility to initialize the HD, make sure you check the option 'Install MacOS 9 HD Driver'; if you do not, your Pismo will not boot to 9.x. When initializing with 10.x, be SURE to select the topmost name in the list in the left column; this is the HD's model number...do not select the HD's user-given name.
2. If the iBook has 9.1 > 9.2.2 installed, you should be able to drag-copy the System Folder from the iBook to the Pismo's HD. Be sure the System Folder is "blessed" after dragging it over to the HD: Open the System Folder icon, double-click the System file (suitcase), then close all windows.
3. You can also use the iBook's System CDs to install software on the Pismo's HD. Depending on what version software came with the iBook:
http://docs.info.apple.com/article.html?artnum=42929
If the above instructions are not the correct version, please let me know exactly what OS came with the iBook.

Similar Messages

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?

G3PB now starts with Open Firmware page.

G3 PB running Os X 10.2.8 and now have Open Firmware page when starting. It has just begun doing this. I didn't think much of it at first but now each time I start I have the Open Firmware page asking me to type in "mac-boot" to start. It seems to go through the normal start after this but I am wondering what happened and how to avoid getting the Open Firmware start page?

firstfrost,
Your computer should not boot into Open Firmware without a prompt. Corrupted PRAM can cause this issue; reset and test.
http://docs.info.apple.com/article.html?artnum=2238

IMac G3 won't boot - starts in Open Firmware

Hi there, I tried to install Debian PPC Linux on my iMac G3, it didn't install properly and now the machine only boots to Open Firmware. I would like to re-install Mac OS 9, I have the system software disc. Please could someone advise on how best to do? Thank you!!

Is this a tray or slot loading iMac?
I'll assume slot.
I forget what booting into open firmware signifies. :-(
It does seem like a reset situation.
Sometimes if volumes don't appear in Startup Manager (what you get when you hold down the Option key at startup), you need to reset the Mac's PRAM, NVRAM, and Open Firmware. Shut down the Mac, then power it up, and before the screen lights up, quickly hold down the Command, Option, P, and R keys, until the Mac has chimed twice more after the powerup chime. Then, before the screen lights up, hold down Command-Option-O-F until the Open Firmware screen appears. Then enter these lines, pressing Return after each one:
reset-nvram
set-defaults
reset-all
"The reset-all command should restart your Mac. If so, you have successfully reset the Open Firmware settings."
http://support.apple.com/kb/TS1812?viewlocale=en_US
How to eject a cd from the internal cd drive:
eject cd
List of devices:
devalias
List of variables:
printenv
( nvram is the equivalent Mac OS X terminal command. )
Resetting your Mac's PRAM and NVRAM
http://support.apple.com/kb/HT1379
reset the PMU
http://mrjcd.com/junk/PMU.jpg
for slot loaders.
Try holding down the option key then power on. This brings up the startup manager. Click on your cd. Click on right arrow key.
I have ubuntu 6 .6 lts running on my iMac G3 600. there are some video setting to change.
Robert

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

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.

Only Starts Up in Open Firmware

I have a G4 400 MHz running Tiger 10.4.3 and lately it's been booting up to the Open Firmware screen. I can type mac-boot and it'll boot up to OS X. I'm not holding any keys during startup and yet is just boots to Open Firmware. What does this mean and how can I stop it?

See http://docs.info.apple.com/article.html?artnum=42642 for details.

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.

IBook G4 - Black screen in open firmware

Hi, i have a strange problem with my iBook G4.
When switched on it chimes and starts loading but the screen is completely black (not no backlight but completely black). In otherwords it does not show the grey screen or apple logo.
Once the OS boots the blue screen comes up and everything works perfectly.
So the problem is that anything before the actual OS loads is black. That means the grey screen with apple logo, open firmware and the drive selection screen (if you boot holding ALT/OPT) are all black.
I have tried resetting the PMU, Pram and blindly (with black screen) in open firmware did reset-nram and reset-all but nothing changed.
It is a late 2004 iBook G4 1.2Ghz with 512MB ram, 30GB HD and OSX Leopard 10.5.8.

This is a strange one, isn't it?
I'd count my lucky stars that it will boot into the OS, and I'd be saving up for a new MacBook Pro (or used MacBook).
I'm going to kick this one around with some of the gang in the Lounge and see if any of them have any ideas about what may be causing this.
Good luck with it.

How do I install an open firmware password on my 10.6.8 OSX Macbook?

I tried to download the lastes version of open firmware, but it is incompatible with the version of my computer. Don't tell me to use a disk I got with my computer, that would be for a Macbook Pro, not a Macbook, which is what I have. Please tell me if you can find a link to a firmware password program for Mac OSX 10.6.8, or if you have another way of installing a firmware password. Thanks.

You have other problems on your computer, then, or not reading carefully. Note this:
"For Mac OS X v10.5.x, start from the Leopard Install DVD and choose Firmware Password Utility from the Utilities menu, then skip to step 5."
For Snow Leopard if the above does not work, then look for the Firmware Password utility on your Snow Leopard DVD.
Oh, and please don't click on the Helpful or Solved buttons for your own posts.

Strange boot bug; open firmware not working

Hi!
I have a powerbook Alu 15", 1.5Ghz. It runs OS X 10.4.2 with the latest security update. My problem started last Saturday.
The problem is that my pb will not restart nor boot on its own. The computer makes its usual chime, the hard-disk starts to spin for a few second, and then stops suddenly before anything is displayed on the screen (the display does not even light-up). If I press the option key after or before the chime, and keep it pressed, or the shift key, or the c key, or the t key, or the command-option-p-r key combination, or even the command-option-o-f key combination, the behavior is exactly the same: the disk starts to spin for a few second after the chime, and suddenly halts. The computer appears to shutdown on its own before the boot can even start.
Here is the strange part: the computer boots normally if I press the command key (this key on its own is not suppose to do anything). It also works if I press the command-s or command-v key combination. No other key combination seem to work.
Except for this strange boot behavior, the computer works flawlessly. I did not have any kernel panic for at least a year, the computer did not crash recently, everything works fine except for one small detail on which I will come back at the end.
I've tried to fix the problem by the following actions:
1) Clean install of Tiger with a new partitioning of the disk; I even zeroed the entire disk. This did not change anything so the problem is probably not OS related.
2) Reset of the PMU with the four finger salute: shift-control-option-power combination. No effect except that I lost the date/time information. Hence the reset worked.
3) Tried to reset the PRAM, but the command-option-p-r key combination does not seem to work.
4) Tried to load the open firmware with command-option-o-f, but this does not work either.
5) Memory seems ok. I have 1x256M of Apple RAM + 1x1G of RAM bought from OWC. I've had the OWC RAM for about a year without any problem. Anyway, I removed the 1G module and tried to boot on the 256M Apple module alone. Exact same behavior. Then I removed the Apple module and put back the 1G module. Exact same boot behavior. So the problem is not with my RAM, unless both modules have simultaneously developed a malfunction.
6) Tried to run the Apple hardware tests. However, for my machine, these tests come on the install DVD, in a special hidden volume. To boot on this special volume, one needs to boot with the option key depressed, and to select the boot volume from the open firmware interface. But this does not work on my machine, the computer seems to shut down before this interface can be activated!
So this problem is very strange. I can live with having to press the command key for booting my machine, but I would sure like to know what is going on here. Is the problem hardware related? Perhaps, but as I said, the machine works flawlessly except for the strange boot behavior.
Is the problem related to firmware? I think that this is the most probable option. What do you think? Maybe, the firmware got slightly corrupted? Maybe a bit got flipped in the flash memory? Is this possible? I guess so. But, what can I do? Should I contact my friendly local repairman?! I have to admit that this option scares me a little bit for such a strange problem. I would need an Apple engineer with boot related experience/expertise!
Now, here is a little bit of further information. I don't know if its related, but it is also very strange. I work with a dual screen configuration. Usually, I connect my screen and then I wake up the computer. Last week, I noticed that if I connect my second screen live, the system detects it automatically. I guess this is new to Tiger? Anyway, the strange behavior is that the computer then asks me if I want to sleep, restart or shutdown my pb, as if I had pressed the power button. But I did not press this button when I connected the dvi connector >:-o
Many thank

Hi Scott!
Almost every time the PowerBook woke after sleep, I got the 'Are you sure you want to shut down your computer now...' message.
I get this message upon wake only rarely, but every time I plug or unplug a display live.
The strange behaviour was tolerable, so I've lived with it for several months. But then when checking out the PowerBook discussions, I read about the failing lower RAM slot problems, and just out of interest, checked out my System Profiler....
Ok, so the good news is that my pb may continue to work for several months
My lower RAM slot appears to be ok for now.
Interestingly, I'm sure that the start-up problems began when I started using my PowerBook with a 23" Apple Cinema Display (a pink hued one, but that's another on-going saga) - and you too have mentioned that you use an external display, so I wonder if that's part of the cause of our start-up problems.
Yes, I've noticed the 'Are you sure you want to shut down your computer now...' message just a few days before noticing the strange boot problem (not sure if the machine booted in between). I use ViewSonic displays (one at home and one at the office), and several different projectors in different class rooms. From what I read, it is plausible that there is a link between this problem and the dvi port. Could it be that the boot sequence of mb is affected by a hardware problem on the dvi port? But not when a press the command key?!
Anyway, my machine is no longer under warranty, so I intend to live with the problem for as long as possible...
But I've been doing more regular backups since then.
Best wishes to you and your (almost) new machine!
Marc.

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 17" Boots into Open Firmware; Won't boot from HD or Disk

This PBG417 (1GHz/512MB/60GB) has an complex recent history directly related to this problem. It was thought to have a dead logic board, and was given to me for a very insignificant amount of money. I discovered today (at an Authorized Apple Repair center) it merely had a ribbon cable disconnected from the logic board which kept it from powering on, which, when rge cable was reconnected it did on the spot, fully booting (imagine my satisfaction). However, upon getting home, it booted into Open Firmware instead, and offedrs a choice of typing mac-boot or shut-down. Mac-boot takes it to the grey screen where the question mark/Finder guy blink and nothing happens. I put a grey PowerBook G4 17" system disk in, but not the one that shipped with it, hoping it would do. When I try to boot from disk, it goes to Open Firmware, I enter mac-boot, it goes to happy Finder with no question folder, but stays there with the optical drive occasionally making movememts and sounds. If you enter any command besides shut down or mac-boot, iot says unknown word; the command prompt itself is 0> .
I'm not sure the hard drive is seated correctly. When I got the computer, the drive was removed; I put it in an enclosure and installed Tiger on it and put it back in, but apart from connecting the ribbon cable, it just sat in its bay not fixed down. However, it booted correctly the first time it was successfully started.
Finally, the previous owner removed all 23 bottom case screws when he took out the drive and lost them; the Apple repair tech mustered up about 9 and put them in the crucial locations but it's still not screwed down everywhere, although the one time it booted correctly, it had no screws in it.
It seems the computer doesn't read the hard drive or the disk, but the hard drive mau be installed wrong and the disk, while for a 17" was not the one that shipped with this PowerBook 17". The computer is missing many case screws, bnutg booted properly only when there were none it place. I also tried resetting the PMU but am not sure I did reset it because the Apple article isn't clear about which models have which processes. I tied Target Disk Mode but it woujldn't mount/boot.
How can I get the disk out and how to make it boot to the desktop?

You can try to reset NVRAM here is KBase from apple site:
http://docs.info.apple.com/article.html?artnum=42642
and after that reset PRAM in your unit, here is the kbase:
http://docs.info.apple.com/article.html?artnum=2238
If needed you can also tried to reset PMU, here is the kbase:
http://docs.info.apple.com/article.html?artnum=14449
Make sure you choose the correct step for your unit.
If after all the steps your unit still booting up to open firmware then there is possibility that you have corrupt NVRAM which could not be fixed by doing reset except replacing logic board.
Good luck. Hope this help
Flippo

Open Firmware displayed on Desktop

Hi all,
I was wondering has anyone come across a problem where open firmware is displayed on the desktop. It happened when the computer was being shutting down. The computer all of a sudden displayed the open firmware screen over the desktop, the prompt was displayed but it wasn't possible to type anything in. The computer is a 1.8Ghz G5, 10.3.9. All the fans started running and the mac was left over night. The fans were still running the nextday and it was shutdown. I had a look in the System Profiler and the only thing that I could see that was relevant was this error
localhost loginwindow[179]: sendQuitEventToApp (iCalAlarmScheduler): AESendWithMach returned error -1712
Nov 6 13:41:30 localhost kernel: AFPSleepWakeHandler: waking up
Nov 6 13:41:30 localhost mDNSResponder[138]: mDNSResponder Waking at 8751262
Nov 6 17:33:40 localhost loginwindow[179]: sendQuitEventToApp (iCalAlarmScheduler): AESendWithMach returned error -1712
Nov 6 17:33:41 localhost loginwindow[179]: halting
Nov 6 17:33:42 localhost shutdown: halt by machine_3:
Nov 6 17:33:44 localhost syslogd: exiting on signal 15
Nov 7 09:47:37 localhost syslogd: restart
Does anyone know what this error means?
Fiachra.

Fiachra:
I think it was possible to run "repair disk" while booted from the hd a couple of osx versions back.
You cannot repair the volume from which you are booted. That is why you need to boot from the install disk, or another volume, e.g. while booted from a Firewire external boot volume, or from another mac while in Firewire Target Disk Mode. You can do a certain amount of Disk Repair by Starting up in the Safe Mode.
I have read verious oppinions about which way was best to run "repair permissions" so I tough the jury was out on that one.
While you can Repair Disk Permissions while booted from the install disk doing it from the Utilities Folder on the boot disk is preferable because it examines and repairs the latest permissions on the boot volume. At least that is the rationale I have seen, which seems to make sense to me.
On the other topic, I use Tech Tool Pro regularly and I try to do it at a time when I am not using the computer for anything else so I don't have to worry about how long it is taking. Many users prefer for Disk Warrior for directory repairs, although I find TTP to be as efficient, and it does the other things as well.
Good luck.
cornelius.

Starts in Open Firmware. No OS

Similar Messages

Maybe you are looking for