![]() |
![]() ![]() Did I break my computer trying to install Linux? It can't boot now. |
Some people have accidentally written data onto the portion of their harddisk that contains the disk driver code used by the Mac OS. If this happens, and the partition map still indicates there is a valid driver present, then the computer may well lock-up whenever it tries to read from that drive in the boot sequence. The solution is to re- install the driver. That may be easier said than done because it may seem impossible to boot the machine. If you can talk to open firmware to request a floppy boot, then the "help*.coff utility" available at ftp://ftp.linuxppc.org/users/harry/ will allow you to use pdisk to delete the driver partition. You should then be able to boot. If you can't get to open firmware, then another approach is to unplug the power connector from the dead drive, boot the computer (e.g. from CD), then with the computer still running, plug the power connector back into the drive, then run drive setup or whatever driver/formatting utility you like to install a new driver. harry eaton haceaton@aplcomm.jhuapl.edu [wj@duke.edu - fixed location of the help utility to Harry's LinuxPPC directory] It could also be as simple as corrupted PRAM - try zapping it during bootup by holding down the [command]-[option]-p-r key combination while the computer boots (during and after the startup chord - let it reset twice, at least). wj@acpub.duke.edu Some people have noted that command-option-P-R may not work if you have extra devices connected to your ADB bus. If it doesn't work, disconnect any such devices and try again. Paul.Mackerras@cs.anu.edu.auhaceaton@aplcomm.jhuapl.edu, wj@acpub.duke.edu, Paul.Mackerras@cs.anu.edu.au, wj@duke.edu | |
If your MacOS Partition is HFS+, grab an OS installer CD that is pre-OS 8.1.
Boot from that. You should get the drive with the "Where_have_all_my_files_gone?" file and that's it. This /should/ correct the problem temprorarily enough to allow you to start up off of that drive and repair the driver.
johan@newsmagic.com, b.judd@xtra.co.nz | |
In my case, the install left me with the Question Mark screen but no boot function from the ata disk on my G3 233 standard box.
The easy workarounds were the Sys8 Install Disk (then use HD Setup from the utility folder to mount the ATA volumes and copy the files off) or any SCSI disk seems to work also (both Syquest units booted -- they had system files on them -- from the Question Mark screen). In either event, you'll probably have to reformat the ATA disk and reload all your software. No other fix I tried (including blanking out and rebuilding the driver partitions) worked. If someone comes up with a more elegant fix, please supersede this.Dave North north@znet.com | |
I got the infamous question mark after install as well (and I get it sometimes after rebooting from LinuxPPC 1999). I popped in my Norton Utilities CD to boot and tried to run Disk Doctor on the drive -- however, the drive could not be found at all. I thought I was completely hosed. I gave up and decided to try again later. When I booted my machine (PowerMac 7500, upgraded to 604/120) the next time, it worked fine -- no question mark. Now, whenever the problem occurs, I boot from either my Norton CD or my System 8.5 CD, then reboot again, and everything seems to work fine after that.
craig@gillikin.cncfamily.com | |
On my 7600/132, an external HD formated to use with LinuxPPC was guilty.
I had to switch it off, reboot MacOS, switch it on then re-format it with
another formatter. Then, eveything was fine to continue LinuxPPCR5 installation!
lol@hugo.ch | |
There is a firmware update for Macs with 1.2GB hard drive firmware revisions of
1.37 or less. The firmware bug causes the question mark to appear even under normal.
conditions. The 1.2GB Firmware update patch is available at www.support.apple.com.
tillman@azstarnet.com | |
[Append to This Answer] |
Previous: |
![]() |
Next: |
![]() |
|