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

Similar Messages

  • Yet another "won't boot from a certain disk" issue

    My Sawtooth G4 just got a new second drive, which seems to work fine. At first it wouldn't boot OS 9 (there are multiple partitions on it) but after some messing with the OS 9 install disk and changing the Startup Disk in the control panel I got that sorted out. The real problem is with OS X. I'm running 10.3.9 on my primary HD and I wanted another OS X system on the new HD so I CCC'd my first disk to the new HD's first partition (which worked fine on the old drive's second partition, now erased) but the Mac won't boot from it. It showed up under the boot options menu (hold option down) but simply wouldn't boot from it no matter what. Finally, I erased the partition and installed OS 10.3 then upgraded it to 10.3.9 (still won't boot from it) but the problem continues. I get the spinning wheel followed by the circle with the bar through it.
    It looks to me like there are tons of possible causes for this after reading through several similar threads here. Could somebody tell me what the most logical approach is to fixing this? Or maybe there's some stupid obvious thing I forgot?
    Thanks!

    Haven't you ever had a system crash or something that messed up your startup disk or some portion of the OS? And what if your prefs or anything custom has been affected? If you only have one startup drive and it gets hosed you are really in a world of hurt, as then it's up to recovery methods to salvage things. And if you don't have unlimited time to sort all this out? It seems obvious why I would want two startup disks - I've used this system for fifteen years and it just works, thats all. Under OS 9 everything was a lot simpler - you just copied the files to another disk and if they were there, you got a boot disk; everything is a lot more complex in X and I don't really understand it even now.
    Then there's the issue of why the other startup disk, while recognized as such, won't boot. That's a puzzle to me. I can't imagine how the Carbon Copy Cloned disk wouldn't work for this - that's what I did before and it worked fine.
    The new drive is a SATA drive with an OWC card, but since the partitions with OS9 boots work fine I don't know what to think. (I have to have OS 9 because I still use Vision for my sequencing and audio recording, and because 9 crashes more often than X I always have at least two boot disks of my main system - just in case.)
    Thanks.

  • HP Pavillion DV9705ea (DV9000 series) CD/DVD not showing - Cannot boot from CD/DVD - BIOS issues!

    All,
    I'm having some issues here with a HP Pavillion DV9705ea machine (DV9700). I'm looking at this for a client. It had Vista home and it dropped the DVD - Wasn't in Device manager either. I checked the drivers and the Microsoft 'Fix It' man, which my client had used (Automated Troubleshooting Services) had put some random, unrelated driver in there. I removed the driver and restored the original, but to no avail.
    After much playing within the OS, I managed to convince my client that a rebuild was a good idea - Both to fix this, and a great opportunity for a refresh. I managed to coax them into a Windows 7 upgrade, cool - Or so I thought.
    I backed-up all of the data, popped the disk in and attempted to boot. Nothing. The machine is unaware of the DVD. Odd. I managed to ruin the Vista build on the HDD - This was partly because I was sure it was about to be wiped and partly because I wasn't exactly careful when moving data within it and powering it down incorrectly due to freezing! Academic, Vista is gone.
    I attempted to boot the recovery manager, using F11 - This worked. However, it throws a zig-zag'ed, stripy screen at around 70%. Have tried this several times.
    I booted from a USB HDD and ran a version of VistaPE to update the BIOS from 'F2; to 'F32'. Although this was a success, the DVD is still not recognised. I have used an independantly powered Lenovo USB CD/DVD Burner to boot from and have had no joy.
    I took a second HDD, popped it into a different shell and built XP on it. I then put this in the Pavilion and booted - Got the message "Operating System Not Found". I have used my USB HDD again and booted a partition manager, I can see the HDD from here, no problems. I can also see them from VistaPE.
    Going forwards - I am going to remove the DVD drive from the machine and attempt to boot from my external drive. I'm in abit of a corner at the moment as all roads arrive at the same destination - Fail.
    I'm thinking 3rd party driver required? Any thoughts surrounding this would be helpful!
    If anyone can shed any light on the issue, fantastic - If not, well, then it'll be an RMA for my client as this machine is out of warranty as of Feb 2009.
    Cheers, Mike.

    Hello,
    Its just to let you know that HP laptop are the worst in the world they have a Graphics chip error in almost every model especially in DV6000 and otherDV. Then, DVD/CD does not detect at all and its all motherboard hardware error. As, i do repairing myself I tried to resold all the joints for the connector for the DVD/CD it worked but as i took off DVD and replug it its as good as dead its motherboard failure.
    Now, about cameras DV9000 have a very big issue for failure of builtin cameras i think these both problems have some common reason as both Builtin camera and DVD connector on same side of the MOBO.
    Please help People save money and time. Stop them to buy HP. A sincere request.
    Regards

  • PowerMac G5 not showing boot manager or open firmware

    I recently got a PowerMac G5 Dual 2.5 GHz (7,3) from a friend of mine, and I would like to dual-boot it between Tiger (or Leopard) and Debian PPC. However, every time I try to bring up the boot menu (hold ALT/option at boot before chime) there is simply a black screen. Same happens when I try to boot to Open Firmware (hold CMD-ALT-O-F); just a blank screen. When I try to boot from the Debian CD, it's almost as though it is ignored, as I am put straight to OS X, but I can boot from the Panther/Tiger DVDs. I have tried resetting the PRAM, the SMU via the button on the board, and I left it unplugged overnight, to no avail. Can anyone help?

    It's acting like there is a firmware password in some respects.  It should be asking for your firmware password when a firmware password was configured but it doesn't seem to be.  I've never used a firmware password, so I have no direct experince with it.
    1) Might try the hardware reset.   I'd try this first. You will have to search around to find where the hardware reset button is on your machine.  BDAQUA help? 
    2) Might try the procedure to delete firmware password.  I'd try it.  Don't think it can hurt!
    Maybe your are getting the firmware password?  Do you see this image?
    http://support.apple.com/kb/HT1352
    http://reviews.cnet.com/8301-13727_7-57521667-263/use-the-calculator-to-reveal-a -macs-firmware-password/
    Remove one memory stick.  Then do as BD suggests.
    BDAqua reminds me:
    Then, the PRAM must be reset 3 times. (Command + Option + p + r).
    http://www.securemac.com/openfirmwarepasswordprotection.php
    You machine does boot to one partition always.  Could install a linux boot manager in that partition.  Yaboot on a ppc
    The mac startup manager is installed in firmware cannot touch it.  Linux boot manager is install on hd.

  • 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

  • HUGE powermac open firmware issue.

    Well, basically I have a sawtooth G4.
    I was trying to install Tiger via any method possible, since the DVD drive doesn't seem to work.
    So using another mac, I tried to install it via target disk mode.
    Well, the G4 wouldn't boot into target disk, so I booted into open firmware.
    I typed in "target-mode"... and it said "ok". It basically did nothing.
    I got frustrated and typed "reset-nvram", booted back up in open firmware, and the entire "target-mode" command is GONE. Nothing. It can't find it.
    Any idea on what to do would be highly appreciated.

    Hi there, put the Install Disc in the other Mac, boot the other Mac into Target Mode, boot the Sawtooth G4 with the Option/alt key held down, does the Install Disc show as a boot choice?
    If so select it & Install.

  • "My Page" login problem, open directory issue I think

    I'm able to log into the My Page web portal for a local server account user, but not any of the user's in the Open Directory (LDAP) node. Anyone know what might be causing that? Thanks in advance.

    Is there a specific group that gets access to the web portal tools (wiki, blog, etc) that the users in the network node need to be in?

  • Booting From USB-- opening Recovery mode?

    So, I copied my Moutain Lion CD to a USB Drive (on another computer) because there's no hard drive on Air's and I bought ML forever ago at an Apple store and didn't have it associated with my Apple ID. But, when I try to reboot from my USB Drive on my Air (pressing Option after startup) it appears on the list of drives (although Mac HD doesn't...?) and when I click it, it goes to OS X Utilties. From there is Disk Utilties (Mac HD is in there...!) and Reinstall ML (from Apple ID though). I don't know how I keep getting to this recovery page, when I just want to reboot to my USB drive.     

    Mt Lion never came on a CD/DVD. You can't get Mt Lion without buying it from the Mac App Store unless it came Preinstalled on your Mac when it was built, New.
    If it is not associated with your Apple ID then it is associated with someone else's Apple ID, that is unless as stated above it came Pre-Installed on your Mac when it was new, Manufactured.
    If you have a Mid 2012 Air model there is a Recall on the SSD installed in them.

  • Booting from external, need to stop bad internal drive from trying to mount

    I have an Intel iMac with a bad internal drive. It won't mount, but makes several clicks every few seconds trying to access the drive. Eventually I will take it in for repair, but I don't want to be without it for several days and it is working fine with the external drive.
    It's not a huge problem, but the clicking gets annoying. Does anyone have suggestions on how I can disable the drive or prevent the computer from trying to access it? I don't want to physically disable it unless it is a simple procedure. I'm hoping there is a software solution via OS X or Terminal commands.
    I should say that I found some instructions to prevent a drive from mounting, but it requires the drive's UUID which I can't get unless it mounts. Also, I don't know if this will stop the clicking. Anyway, here are the instructions. Perhaps there is a way to do something similar without knowing the UUID or by knowing the UUID of the working drives? I appreciate any help.
    1. Open Disk Utility
    2. Select the bad drive, then click the Info button
    3. Copy the Universal Unique Identifier (UUID) code
    4. Open a Terminal window and type: sudo pico /etc/fstab
    5. Enter your password
    6. Enter the line below (using your own UUID):
    UUID=CDB15826-88A3-36AC-8009-3E71355F0B18 none hfs rw,noauto
    (taken from http://www.macseven.com/files/20070719how_to_prevent_a_drive_volume_frommounting.html)

    I don't know if it can be done using software solution (I think not). It's possible to remove the drive physically but it is rather tricky. see this thread for instructions
    http://discussions.apple.com/thread.jspa?threadID=630315

  • 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

  • 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.

  • 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.

  • 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

  • Can't boot from DVD using C key

    I desperately need to use DiskWarrior on my startup disk. I have used it on my secondary internal hard disk with no problems. A couple of years ago my Apple keyboard went up on me and I needed a replacement immediately (I worked from home), so I ran out to OfficeDepot and bought a Microsoft keyboard that had software with it to make it run with a Mac. It has done fine for me. However, when trying to boot from DiskWarrior, I hold the C key down and it doesn't boot from the DVD, it just boots from my internal startup disk. I was able to install Mac OS X 10.4 with the DVD and this keyboard, however. DiskWarrior tech support dudes tell me it is the fault of the Microsoft keyboard. I'm not so sure (since I installed 10.4 with this keyboard). I don't want to buy an Apple keyboard "just in case." But perhaps this is a known issue by somebody "out there." Any help would be appreciated (before my startup disk explodes altogether). Thanks!

    I have 3 Microsoft keyboards, going back to my G4 MDD. Usually plugged into an Apple Display, but on some occassions I've had to plug it directly into front USB port (or rear, front is accessible).
    The one thing that I would do, is not just "zap PRAM" from cold boot, but boot into the Open Firmware screen and RESET-NVRAM, and see if that helps. Force the device ID list to be rebuilt, and does a more complete job than zapping can.
    There have been a lot of major problems with Apple USB hub type support. I too was troubleshooting an issue and got the "run around."
    The only time I've seen where someone could not boot from a DVD/CD was when the hard drive in the system directory was severely corrupt - OS X looks to find any and all bootable devices even when you boot from CD or another drive. And a damaged journaling file is even harder to fix usually.
    Outside of the G4 PCI model (1999, early '00) a G4 can boot from Firewire, any problem I'd guess was a defective FW port; some FW cases themselves.
    I never really use DW CD. Always always clone your system; create an Emergency boot drive to work from - and used only in emergency so you know it works and isn't just a backup. And, of course, a backup of your working system.
    USB cables can flake out. Even new. The USB extension cable Apple includes being one such that has been known to be the culprit. So doubt and verify any cables and devices.
    One G5 owner has a LaCie drive not even connected, but the FW cable was, hanging out the back, and would cause:
    slow boot sometimes; kernel panic other times; pull the cable, life is back to normal again. FW cables and devices (not sure if LaCie has the market cornered or not) that "wipe out" FW ports, cause shorts, should be avoided (maybe banned).
    I've used an MS keyboard for about 4 yrs on my G4, still running 10.4.11. Ever since my Apple split ergonomic keyboard died, and I've got 4 Apple Pro keyboards sitting around (I can palm a basketball but don't like typing on small keyboards). Currently use MS 3000 and 4000 keyboards.
    There are lots of reports of Leopard where the system is not responding, but the mouse able to move, but no interaction - can't launch anything or even bring up the Force Quit dialogue. The system being totally non-responsive, and people force shutdown, with high potential of leaving the directory in disrepair.
    Mac OS 10.2.5 was suppose to fix and solve USB hub problem. That updated lasted less than two weeks. USB issues have been around, as have Firewire problems. Even Windows Vista can loose track of and get confused by unplugging/replugging devices multiple times that it looses the device ID.

  • EMac wont fully boot from HD and wont allow boot from CD/DVD

    I got a eMac the other day knowing something was wrong with it but figured it was probably a Open Firmware issue. I cant get the thing to boot all the way from the HD, it will give the loading screen with the blue bar going accorss then go to a solid blue screen and sit. If I try to boot with option it will ask for a password and has a lock on the boot screen. I tried to reset the PRAM with Option Command P & R and it still just boots to the main HD but stalls like without pressing anything. Im just trying to start from scratch with this computer(No passwords and a fresh install of OSX).

    OK, I got the Open Firmware off of it, so it boots from the CD now. Problem is that now it wont install OSX. I have TIger and Panther and have tried both. With Tiger it will boot fine and lets me start the install process and then about 15% into the intall it quits with errors and cant install. With Panther it just wont boot from the CD at all it gives me a circle with line diaganal line through it. Maybe the battery is bad ill check that tonight. Other than that I cant think of what else it could be other than bad ram maybe. Ill change that too and rule that out as well.

Maybe you are looking for

  • Custom field added in Module pool is not reflecting in SRM Shopping cart

    Hi all, I have to add a custom field for Plant in the Ship-To address subscreen(BBPSC01) in Shooping cart in SRM. I have added the field in the program "saplbbp_sc_ui_its" in screen 310. But I think need to write the HTML code/Java script in HTML tem

  • Help with ipsecurity policy

    im working on a windows server 2012 standard machine and am trying to create an ip security policy rule, on windows server 2008 i could block ip address from the internal lan on a machine running rras and dhcp dns, but now if i assign a new ip securi

  • Plot line in the middle of a time series

    Hi I am trying to plot the limits for a graph. These limits are specified for 10, 20 and 30 ms (In particular I want to plot the limits for neck calibration tests for H3 dummy calibration). For this I need to draw a line from 10 ms to 30 ms. How do I

  • ArsTechnica on Daniel_K Driv

    http://arstechnica.com/news.ars/post/2008033-creative-irate-after-modder-spruces-up-vista-x-fi-drivers.html But the real issue isn't the money. Read between the lines, and O'Shaughnessy is proclaiming that his company has the sacred right to enable a

  • Thunderbolt no display after firmware update (Windows only)

    hi folks it appears my thunderbolt 27" is 50% dead... after doing the firmware update (i think it was 1.2), my thunderbolt is now dead in Windows. it works perfectly in Mac OS X, and is detected correctly and 'all. as soon as I boot with it into Wind