Reinstall on MDD boots into Terminal

I recently bought another MDD G4, the same model as the one I've owned for years . The previous owner didn't have the set of discs that came with it, and had installed Tiger on one of two internal HDs. However, I have a set that came with my computer.
As I would like to use the dual-boot capability to include OS 9, for which I have a lot of favorite programs, games, etc. I cloned the boot drive to the second drive using SuperDuper, and then used my install disc from my set to install OS 10.2.1.
On start up, I got a user log-in screen, and on logging in, I found myself in Terminal (Welcome to Darwin) which I know little about. How do I exit this (is there a command procedure?) to get to the more familiar interface? Also, I then want to install OS 9. I'm not sure if the discs in the set will do this, but I also have an OS 9.O disc and a 9.2.2 upgrade disc. And I have an OS X updater disc to 10.2.8. From there, I assume I can install my Panther disc.
But again, having OS 9.2.2 capability is what's important. And of course, how to get out of Terminal. It's all very interesting, something about Bash, and Shells, but for another day, thank you.
Keith

Yes, you really have to come here to get help on "old" models. I went to my local Apple store with a question about a G3 and the kid (I say the term advisedly) had almost no idea to what I was referring. I suspect my G3 was new when he was 10 years old.
I really don't know how specific the discs are. Maybe somebody else can answer that one. I don't think they go down to serial number but there may be some sub-versions in the models that you can't really detect easily. I have two cars the same year and model, but when I work on them I notice small differences such as the screws that hold on a part on one are not the same as the screws on the other. Maybe something like that except in the hardware or software.
Yes, OS9 had to be updated 9.0.4 _> 9.1 >9.2.1 -> 9.2.2 In OSX major versions (e.g., 10.1, 10.2, etc.) are basically new installs of operating system and you can jump. For example, if you have a computer running Panther that is capable of running Leopard you don't need to install Tiger, but you do have to pay for each new major version. Within a version you can (and should) use the "combo" (ugh, I always say "combination") updaters. So if you have a fresh install of Tiger and want to update it to 10.4.11 you can do it in one step with the combo updater.
You know, when I was doing more OS9 back in my G3 days I don't recall having to boot from a CD to do a fresh install of OS9. Now maybe I had some special version (this was at a large place with a site license and nobody had CDs), but I am wondering if you can get your lame version of 9.2.2 on your new computer you could maybe run your installer to get 9.0 onto the MDD. Do not boot to the new version immediately (which will not boot your computer anyway), but run all the updaters to take it to 9.2.2, then try booting from it. I'm not positive it will work but it's worth a try. If it gives you a good version of 9.2.2 you can then trash the old copy.
The drivers issue is a whole separate thing, but I've already gone through that.

Similar Messages

IMac G5 booting into Terminal Window

At start up the fans come on and I get the opening white Apple screen then everything goes black. I am not sure but it would appear that my IMac G5 is booting into Terminal. I get a whole load of Unix code then it changes to a plain blue screen with the mouse able to drive the cursor but nothing else.
Can anyone suggest how to get out of Terminal into a normal GUI Mac screen.
I cannot boot from the original CD/DVD nor can I start up in safe mode.
Alan

With no responses I worked at it myself. Having zapped the PRAM many times it suddenly cleared

G4 MDD boots into the boot menu

I have a Power Mac G4 MDD (with the firewire 800 port) that is booting into the boot menu most of the time when I press the power button. From there I can select the HD and the boot procedes normally. I thought it was a HD problem and replaced it, but the boot menu still appears, as if I am holding the option key . I also tried changing the amount of memory and clearing the PRAM with the keyboard. What could be causing this? TIA

Maybe too obvious, but, did you reset the startup disk control panel? check or replace the battery?
If you reset nvram in any way you have to go back and set startup disk again. I prefer using Open Firmware rather than zap method.
Instead of replacing the drive, backup with superduper, run disk warrior, erase and restore to clean up a drive. Then run Tiger Cache Cleaner which can now do some maintenance and repairs from Single User Mode, very nice alternative to Applejack, which has also been 'tool of the trade.'
Try booting from a FW800 drive and do some of those repairs.

PowerMac G4 MDD booting into DARWIN/BSD screen.

Hi,
I've been sitting here for the past three days trying to figure out how to fix this problem. My computer keeps booting into the darwin/bsd screen and will not boot into the operating system. Apparently the kernel has a problem. I have tried everything including the "/sbin/fsck -yf" thing. None of it seems to work at all. It just brings me back to this "darwin/bsd screen.
I just found my installation dvd and put it in. Then I held the OPTION+D keys which brought me to the boot drive screen. This screen shows the Main HD symbol and the Mac OS X INSTALL CD icons. But, I am unable to switch over to the Install disc icon to run it. My mouse just doesn't respond at all on this screen, but somehow the keyboard does.
Can someone tell me whats going on???

Resetting your Mac's PRAM and NVRAM
http://docs.info.apple.com/article.html?artnum=2238
http://docs.info.apple.com/article.html?artnum=42642
Tried resetting the PMU?
http://docs.info.apple.com/article.html?artnum=14449
Might try applesetupdone...
This was Posted by: JoseAranda at September 9, 2006 3:48 AM
"OK, restart your computer, hold down Command-s and type in the following:
/sbin/fsck -fy Enter
Repeat until no errors.
/sbin/mount -uaw Enter
rm /var/db/.applesetupdone Enter
1. The rm command is the remove command which deletes the file.
2. Robert: I'd rename the file via: mv /var/db/.applesetupdone /var/db/.applesetupdone.old
reboot Enter
Once you've done that the computer reboots and it's like the first time you used the machine. Your old accounts are all safe. From there you just change all other account passwords in the account preferences!!
end of posted by: JoseAranda"

IMac boots into Terminal

Grandkids have my G4 iMac with OS X 10.4.11 installed and has only 256 MB of memory.
While a granddaughter was reading a Facebook listing the screen went black. Now when powered up the monitor remains black and is actually in the Terminal mode. Typing cal brings up April's calendar.
I re-booted inserted the Tiger CD and held down the C key. After booting up on the CD and getting to the install screen I tried several things. First, I chose the Start Up Drive and selected the OS X 10.4.11 drive---this resulted in the black screen in the Terminal Mode again. After re-booting on the CD again I selected the Disk Utility and repaired permissions---same result-the black screen in Terminal. Another CD re-boot and attempted Disk Verify on Disk Utility---resulted in disk error---same result when Disk Repair selected.
Basic questions: 1) Would re-installing Tiger be the best approach to resolve the issue? 2) Is there another procedure I am missing which also solves the problem? 3) Would exiting the Terminal mode resolve the problem?
Royal

The file's authoring info, album info, etc, may be lost, unless you can rescue the entire Music folder. If that info is in the actual physical file name, it is not lost. The music is still there regardless, unless something really bad happened to the hard drive.
It won't mess up the iPod, just make sure the machine that syncs to the iPod has the entire desired library. You can always transfer music between computers, and between computer and iPod, but not from iPod to computer.
Of course this is all subject to the license restrictions of the music itself.
Message was edited by: a brody

Imac booting into terminal window

Ever since updating to Mountain Lion my imac boots up showing the boot up script, sometimes it stops and I have to type exit or boot to get it going...I've spoken to Apple 'support' 6 times now and including a re-install they have talked me through a miriad of processes...none of them have worked.

Have you done this?
Install or Reinstall Lion/Mountain Lion from Scratch
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Erase the hard drive:
1. Select Disk Utility from the main menu and click on the Continue button.
2. After DU loads select your startup volume (usually Macintosh HD) from the left side list. Click on
the Erase tab in the DU main window.
3. Set the format type to Mac OS Extended (Journaled.) Optionally, click on the Security button and set the Zero
Data option to one-pass. Click on the Erase button and wait until the process has completed.
4. Quit DU and return to the main menu.
Reinstall Lion: Select Reinstall Lion/Mountain Lion and click on the Install button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

I reinstalled osx 10.8.2 from recovery disk, now verify disk says my hard drive is there but wont boot into it regardless which partition i select to boot into , everytime it boots me into the recovery, i need help!

Mb pro running like garbage with 10.8.2 tried a reinstall of osx from recovery utility now the utility says my hard drive is ok but wont boot into it keeps booting me back into recovery tried restart option to select disk tried using the select startup disk from recovery, gives a message asking if i really want to boot to it and in that message is the only rime it shows a question mark on the drive dont know what to do cant find similar issue

Your rushing and not making much sense.
Your machine was running like garbage, so you tried to reinstall 10.8---did you do this or not?
Disk Utility says your drive is ok, that's good.
But when you boot it keeps booting Recovery HD, so perhaps the firmware has made a mistake, it can forget.
You held the option key down to boot into Startup Manager, why didn't you select OS X for the boot volume?
When you get into OS X you change the Startup Disk in System Preferences, that should take care of the Flashing Question mark issue.
attemtping to ireinstall osx from recovery partition bar is full on install screen, but im now at -6hours remaining
So now your reinstalling OS X like you set out to do before, it does take some time as it has to download from Apple's servers.
If your Internet connection is slow and/or Wifi is slow then it will take awhile.
So you should have the Flashing Question Mark and Reinstall Only OS X covered.
You should be able to boot the machine, but your performance issues may be something else and still remain.
Why is my computer slow?
Step by Step to fix your Mac
https://discussions.apple.com/community/notebooks/macbook_pro?view=documents#/?p er_page=50

Dual boot 10 & 8.1 Had to reinstall 8.1 now can't boot into 10

I dual boot win 8.1 and win 10...............I had to reinstall 8.1 and now even though I've added the entry for Win 10 in the boot menu it fails to load with a driver signature verification failure on the windows loader file. I have found out how to disable
driver signature verification but I have to reboot from INSIDE windows to do it. I can boot into win 8.1 just not win 10
Mark Carroll

I got it at Get IntoPC but if you have fast ring enabled on build 10041 it installs 10049 through windows update
Mark Carroll
Microsoft is the ONLLY source for Win 10 TP ISO.
If MS has not released it, then what you get is an illegal copy and probably not working .
I know how one can get 10049 installed via Windows Update. That has nothing to do with your case. You were using a 10049 ISO which has yet to be released by Microsoft.

Cannot boot into Recovery Mode but need to reinstall OS X, any suggestions?

My Mac boot is stuck at the Apple logo with a progress bar, and even when booting Recovery Mode (Command+R) it is stuck. Hence I don't think I can use Internet Recovery to reinstall OS X. Do you guys have any suggestions as to what to do? Thanks!

FYI:
I have tried booting into Single User Mode, using fsck to repair permissions, but to no avail. However in the Single User Mode I did notice something unusual. When trying to reboot using the command 'exit', a long list of errors came out.
Most were Library/Extensions/... .kext is not authentic; omitting from prelinked kernel.
Some errors were ...: No such file or directory
And afterwards the errors were stuck there and no reboot occurred. I also couldn't type anything.

[Solved] Can't boot into Arch after deleting some partitons

About 6 months ago I installed Arch on a machine that used to run Ubuntu. Had some trouble at the time getting to boot into Arch but somehow managed. Now eventually decided to delete the old Ubuntu partitons to free up some space using gparted. Arch partition number changed from sda12 to sda6.
On rebooting after deleting ubuntu partitions with gparted, I got an ubuntu splash screen and a whole lot of ubuntu boot options. Somehow these were all contained in my Arch's /boot/grub/menu.lst. Arch is all on one partition and no separate boot partition (which I had with Ubuntu - maybe I haven't deleted that and this is the problem?). Will need to check that out.
I can chroot into Arch and did the following -
grub> find /boot/grub/stage1
(hd0,5)
grub> root (hd0,5)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,5)/boot/grub/stage2 /boot/grub/menu.lst"... succeed
ed
Done.
grub>
The Arch /boot/grub/menu.lst had a whole lot of ubuntu stuff in it but I edited to the following -
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
# examples
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)
title Arch uuid
#root (hd0,5)
uuid d15cf4f9-18ca-4ec5-95bc-db0f6f264736
kernel /boot/vmlinuz26 root=/dev/sda6 ro vga=775
intrd /boot/kernel26.img
title Arch hd
root (hd0,5)
kernel /boot/vmlinuz26 root=/dev/sda6
intrd /boot/kernel26.img
I have a bootinfo script which gives the following (from the chroot environment) -
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
=> No boot loader is installed in the MBR of /dev/sdb
sda1: _________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sda2: _________________________________________________________________________
File system: Extended Partition
Boot sector type: -
Boot sector info:
sda5: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: /dev/sda5 already mounted or sda5 busy
sda6: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: /dev/sda5 already mounted or sda5 busy
mount: /dev/sda6 already mounted or sda6 busy
sda7: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:
sda3: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.04.1 LTS
Boot files/dirs: /etc/fstab
sda4: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs: /grub/menu.lst /grub/grub.cfg /grub/core.img
sdb1: _________________________________________________________________________
File system: xfs
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:
=========================== Drive/Partition Info: =============================
Drive: sda ___________________ _____________________________________________________
Disk /dev/sda: 750.2 GB, 750155292160 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start End Size Id System
/dev/sda1 417,690 6,554,519 6,136,830 82 Linux swap / Solaris
/dev/sda2 25,414,954 1,465,144,064 1,439,729,111 5 Extended
/dev/sda5 25,414,956 1,360,287,809 1,334,872,854 83 Linux
/dev/sda6 1,360,287,873 1,423,198,349 62,910,477 83 Linux
/dev/sda7 1,423,198,413 1,465,144,064 41,945,652 83 Linux
/dev/sda3 6,554,520 25,414,829 18,860,310 83 Linux
/dev/sda4 * 63 417,689 417,627 83 Linux
Drive: sdb ___________________ _____________________________________________________
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
Partition Boot Start End Size Id System
/dev/sdb1 2,048 1,953,523,711 1,953,521,664 83 Linux
blkid -c /dev/null: ____________________________________________________________
Device UUID TYPE LABEL
/dev/loop0 squashfs
/dev/sda1 2a95d85a-45fe-4584-88dd-0ee20e651ec5 swap
/dev/sda2: PTTYPE="dos" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x5" PART_ENTRY_NUMBER="2"
/dev/sda3 32495e1a-227c-4d23-9f63-b1319def0dd9 ext3
/dev/sda4 d6dc69b0-967d-4886-b62d-8c0d6be06b41 ext3
/dev/sda5 37971286-b8d3-4a1b-9f94-4008288fed6d ext3 data
/dev/sda6 d15cf4f9-18ca-4ec5-95bc-db0f6f264736 ext3 30GB-02
/dev/sda7 eb736131-b558-4404-9b83-7f1e6d9e76ae ext3 var
/dev/sda: PTTYPE="dos"
/dev/sdb1 0e83045d-a0bd-4d36-b61d-bdb905130dc2 xfs 1TB-04
/dev/sdb: PTTYPE="dos"
============================ "mount | grep ^/dev output: ===========================
Device Mount_Point Type Options
/dev/sda12 / ext3 (rw,commit=0)
=============================== sda3/etc/fstab: ===============================
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1 = swap
/dev/sda1 none swap sw 0 0
# /dev/sda3 = root
#UUID=32495e1a-227c-4d23-9f63-b1319def0dd9
/dev/sda3 / ext3 relatime,errors=remount-ro 0 1
# /dev/sda4 = boot
# UUID=d6dc69b0-967d-4886-b62d-8c0d6be06b41
/dev/sda4 /boot ext3 relatime 0 2
# /dev/sda5 = home
# UUID=670eee83-0a3e-429c-863f-b9ecced9f97e
/dev/sda5 /home ext3 relatime 0 2
#/dev/sda6
#UUID=37971286-b8d3-4a1b-9f94-4008288fed6d
/dev/sda6 /home/ben/Data ext3 defaults,relatime 0 0
# /dev/sda7
# UUID=fdb14ca4-d71d-489f-a00e-6e608770674c
/dev/sda7 /var ext3 relatime 0 2
# /dev/sda8
/dev/sda8 /opt ext3 relatime 0 2
# /dev/sda10 - Arch
/dev/sda10 /mnt/arch ext3 relatime 0 2
# Not sure what this is doing here
# Have commented it out - May be the reason why xbmc and mythtv were crashing on dvd insert and play
# /dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
# /dev/sde1
# uuid appears to be 644406B3570C1846 -> ../../sde1
#/dev/sde1 /home/ben/Data/TVRecordings-1TB01 xfs defaults,relatime 0 0
#1TB-01
UUID=76f3823a-81dc-45c9-a0b7-2bc6c3beb2f8 /media/1TB-01 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 1TB-02
UUID=59cbf7a1-7008-40d0-96ed-c6f231823d4f /media/1TB-02 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 1TB-03
UUID=0e936800-3c53-4b87-abc8-19be0ffca7f9 /media/1TB-03 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 750GB-02 ext3 Partition
# UUID giving problems, trying with dev
# UUID=c23b9c9a-66fc-4256-9211-73156c1ac64a /media/750GB-02_ext3 ext3 defaults,relatime 0 0
/dev/sde2 /media/750GB-02_ext3 ext3 defaults,relatime 0 0
============================= sda4/grub/menu.lst: =============================
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
# examples
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false
## ## End Default Options ##
title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-26-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-26-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-24-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-24-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-23-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-23-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-22-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-22-generic
title Ubuntu 10.04.1 LTS, memtest86+
root (hd0,3)
kernel /memtest86+.bin
quiet
### END DEBIAN AUTOMAGIC KERNELS LIST
============================= sda4/grub/grub.cfg: =============================
# DO NOT EDIT THIS FILE
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
function recordfail {
set recordfail=1
if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set 32495e1a-227c-4d23-9f63-b1319def0dd9
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-26-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-26-generic
menuentry 'Ubuntu, with Linux 2.6.32-26-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-26-generic ...'
linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-26-generic
menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-24-generic
menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-24-generic ...'
linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-24-generic
menuentry 'Ubuntu, with Linux 2.6.32-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-23-generic
menuentry 'Ubuntu, with Linux 2.6.32-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-23-generic ...'
linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-23-generic
menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-22-generic
menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-22-generic ...'
linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-22-generic
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux16 /memtest86+.bin
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux16 /memtest86+.bin console=ttyS0,115200n8
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Arch Linux (on /dev/sda10)" {
insmod ext2
set root='(hd0,10)'
search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
linux /boot/vmlinuz26 root=/dev/sda10 ro
initrd /boot/kernel26.img
menuentry "Arch Linux Fallback (on /dev/sda10)" {
insmod ext2
set root='(hd0,10)'
search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
linux /boot/vmlinuz26 root=/dev/sda10 ro
initrd /boot/kernel26-fallback.img
#### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
# From Arch grub menu.lst
# (0) Arch Linux
#title Arch Linux [/boot/vmlinuz26]
#root (hd0,0)
#kernel /vmlinuz26 root=/dev/sda3 ro
#initrd /kernel26.img
#Note: With a separate boot partition, omit /boot from the path, (i.e. type set prefix=(hdX,Y)/grub and insmod
(hdX,Y)/grub/linux.mod).
#This introduces the "linux" and "initrd" commands, which should be familiar (see #Configuration).
#An example, booting Arch Linux:
#set root=(hd0,5)
#linux /boot/vmlinuz26 root=/dev/sda5
#initrd /boot/kernel26.img
#boot
###menuentry "Arch1" {
###insmod ext2
###set root='(hd0,10)'
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
###search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UU
ID
###linux /boot/vmlinuz-26 root=635d7d02-3f5b-4af6-9c74-16b2af8cc7fd ro quiet splash # ARCH'S ROOT UUID
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
###menuentry "Arch2" {
###insmod ext2
###set root='(hd0,4)' #= TRYING UBUNTU'S BOOT
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
###menuentry "Arch3" {
###insmod ext2
###set root='(hd0,10)' #= TRYING UBUNTU'S BOOT IN HD FORMAT
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
### END /etc/grub.d/40_custom ###
=================== sda4: Location of files loaded by Grub: ===================
.0GB: grub/core.img
.0GB: grub/grub.cfg
.0GB: grub/menu.lst
.0GB: grub/stage2
.0GB: initrd.img-2.6.32-22-generic
.0GB: initrd.img-2.6.32-23-generic
.1GB: initrd.img-2.6.32-24-generic
.1GB: initrd.img-2.6.32-26-generic
.0GB: vmlinuz26
.0GB: vmlinuz-2.6.32-22-generic
.0GB: vmlinuz-2.6.32-23-generic
.1GB: vmlinuz-2.6.32-24-generic
.0GB: vmlinuz-2.6.32-26-generic
=============================== StdErr Messages: ===============================
No volume groups found
mdadm: No arrays found in config file or automatically
[/quote]
Output of fdisk -l from chroot is -
[quote]Disk /dev/sda: 750.2 GB, 750155292160 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000b084
Device Boot Start End Blocks Id System
/dev/sda1 417690 6554519 3068415 82 Linux swap / Solaris
/dev/sda2 25414954 1465144064 719864555+ 5 Extended
/dev/sda3 6554520 25414829 9430155 83 Linux
/dev/sda4 * 63 417689 208813+ 83 Linux
/dev/sda5 25414956 1360287809 667436427 83 Linux
/dev/sda6 1360287873 1423198349 31455238+ 83 Linux
/dev/sda7 1423198413 1465144064 20972826 83 Linux
Partition table entries are not in disk order
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00025bd3
Device Boot Start End Blocks Id System
/dev/sdb1 2048 1953523711 976760832 83 Linux
I need to post this now and come back from a different machine to note the error messages I am now getting on boot. ...
Note that when I boot and press esc to get the menu I get the menu.lst I created (in the second quote) above in /dev/sda6, ie the one with the Arch hd and uuid entries - so grub is looking there and finding that menu.lst, but something goes wrong after that.
OK. Have now booted the machine and after pressing esc and selecting the uuid entry (the same thing happens with the hd entry) I get a whole lot of stuff, but what seems relevant is (typing it out) -
List of all partitions:
No filesystem could mount root, tried:
Kernel panic - not syncing: VS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper Not tainted 2.6.39-Arch #1
If anyone can help I'd really appreciate it. This is my MythTV machine so the WAF is about to take a big dive!
If I could just install grub to the MBR as if this was a new installation of Arch that would be great.
I am really lost as to what is going on, which I'm sure is evident.
Thanks a lot
belbo
Last edited by belbo (2011-08-12 13:31:23)

Hi. Unfortunately that didn't help.
So next, based on this post https://wiki.archlinux.org/index.php/Ke … el_version I chrooted into Arch and (a) rolled back and (b) reinstalled my kernel but that didn't help either. I suspected it wouldn't because the kernel was working fine before I deleted the partitions in question.
[2011-08-08 23:32] ==> Image generation successful
[2011-08-08 23:32] upgraded kernel26 (2.6.39.3-1 -> 2.6.39.3-1)
I then did a pacman -Suy and the linux package has now replaced kernel26. ( See this wiki entry http://www.archlinux.org/news/changes-t … filenames/). I didn't change anything in menu.lst owing to this and it seems there is no need to. Unfortunately this hasn't helped either - still getting the kernel panic.
Pacman.log relating to the new kernel package below -
[2011-08-09 00:22] Running 'pacman -Suy'
[2011-08-09 00:22] synchronizing package lists
[2011-08-09 00:23] starting full system upgrade
[2011-08-09 00:23] Running 'pacman -Suy'
[2011-08-09 00:23] synchronizing package lists
[2011-08-09 00:23] starting full system upgrade
[2011-08-09 00:26] removed python-mygpoclient (1.5-1)
[2011-08-09 00:26] removed kernel26 (2.6.39.3-1)
[2011-08-09 00:26] warning: /boot/grub/menu.lst installed as /boot/grub/menu.lst.pacnew
[2011-08-09 00:26] upgraded grub (0.97-17 -> 0.97-19)
[2011-08-09 00:26] upgraded icu (4.8-1 -> 4.8.1-1)
[2011-08-09 00:26] upgraded linux-firmware (20110512-2 -> 20110727-1)
[2011-08-09 00:26] >>> Updating module dependencies. Please wait ...
[2011-08-09 00:26] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2011-08-09 00:26] ==> Building image from preset: 'default'
[2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2011-08-09 00:26] ==> Starting build: 3.0-ARCH
[2011-08-09 00:26] -> Parsing hook: [base]
[2011-08-09 00:26] -> Parsing hook: [udev]
[2011-08-09 00:26] -> Parsing hook: [autodetect]
[2011-08-09 00:26] -> Parsing hook: [pata]
[2011-08-09 00:26] -> Parsing hook: [scsi]
[2011-08-09 00:26] -> Parsing hook: [sata]
[2011-08-09 00:26] -> Parsing hook: [filesystems]
[2011-08-09 00:26] -> Parsing hook: [usbinput]
[2011-08-09 00:26] ==> Generating module dependencies
[2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2011-08-09 00:26] 7079 blocks
[2011-08-09 00:26] ==> Image generation successful
[2011-08-09 00:26] ==> Building image from preset: 'fallback'
[2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2011-08-09 00:26] ==> Starting build: 3.0-ARCH
[2011-08-09 00:26] -> Parsing hook: [base]
[2011-08-09 00:26] -> Parsing hook: [udev]
[2011-08-09 00:26] -> Parsing hook: [pata]
[2011-08-09 00:26] -> Parsing hook: [scsi]
[2011-08-09 00:26] -> Parsing hook: [sata]
[2011-08-09 00:26] -> Parsing hook: [filesystems]
[2011-08-09 00:26] -> Parsing hook: [usbinput]
[2011-08-09 00:26] ==> Generating module dependencies
[2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2011-08-09 00:26] 23360 blocks
[2011-08-09 00:26] ==> Image generation successful
[2011-08-09 00:26] installed linux (3.0.1-1)
I don't think I've mentioned that my old menu.lst seems to have disappeared and so must have been on one of the partitions that were deleted. I did have 2 Arch installations when I was setting things up months ago and that menu.lst may have been on the other partition but pointing to this partiton's kernel for booting. Presumably that's possible since this partiton is definitely the one I have been using for the last several months (confirmed by log and other files updated in the last few days etc). Even so, I suppose that probably wouldn't be relevant to this issue, since grub is finding the menu.lst on this partition when it boots so it is looking in the intended place now.
It seems I'm at a bit of a dead end. It seems these kernel panics are usually because there is something wrong with the kernel - which there wasn't with mine (and presumably the kernel in the new linux package is fine) or there is a typo in menu.lst (I can't see one and nobody has pointed one out yet) or menu.lst is pointing to the wrong partition (mine is pointing to the same partition and /boot directory that is found by grub - which is where my boot image is located - so it seems to be correct). I have nevertheless tried editing the menu.lst entry when booting to boot from different partitions but so far that hasn't worked either.
If anybody has other ideas I'd really appreciate it.
If not, some suggestions on re-installing would also be appreciated. I have a recent tar archive of the partition, but presumably reinstalling that wouldn't be of much use since it would just put back what is currently there. I guess that I need to format the partition, create a separate boot partition, do a fresh install of Arch into the formatted partition (and with boot in the new boot partition). And then restore my tar backup (excluding the boot directory) into the formatted partition?
Any assistance greatly appreciated.
Thanks
belbo
Last edited by belbo (2011-08-08 23:17:49)

G5 will not boot into OSX - stays at a command-line prompt

My G5 will not boot into OS X. I would appreciate and and all advice. Thanks.
What happened:
I had the G5 running one morning, with the Isight camera on, plugged into the front-console firewire port. I was running EvoCam software.
At about 2 hours into running, the cam stopped broadcasting – I got home to check it out three hours later, and the screen was black, and the fan was louder than I had ever, ever heard it on this box.
I did a hard shut-down with the powerbutton on the Cinema Display monitor.
At reboot, I see a grey screen for approx 5 seconds, with a dark grey apple logo, and then the screen goes to black, with a command-line prompt.
It’s been like that ever since.
I ran the Apple Hardware test, from the internal CD drive, and it shows no errors.
I cannot boot from an OSX installer DVD. It won’t recognize it. It goes straight to the black screen and Command line prompt.
I have re-seated the RAM, as well as the Airport Card. The only other card – which I have not re-seated, it the video card.
I am able to use the machine in Target Mode, so I can extract data from the drives, which is great. Oddly enough, I’m able to use the front-console firewire port to connect to my other Mac in Target mode – with no problems. Also – in Target mode, the fan never goes above the usual quiet self.
I would appreciate any advice one can provide. Thanks!
The machine:
Mac G5 dual 2.0 – First Generation (purchased December 2003)
It’s on it’s 3rd Motherboard – and now it’s fully out of Applecare warrantee.
OSX 10.4.9
4GB Ram
2 internal drives: 160GB + 300GB
Airport Extreme
20” Cinema Display (first generation)
Mac G5 dual 2.0 – First Generation Mac OS X (10.4.9)

Well, Apple Support does have articles on:
Isolating Issues in Mac OS X
http://docs.info.apple.com/article.html?artnum=25392
won't boot or login
http://docs.info.apple.com/article.html?artnum=106464#symp1
And if those don't work, call.
With G4 there is/was
"Fix for a Mac that won't power up
Mirrored Doors G4. When you pressed the power button, the button would light up, but the computer would not turn on. The fans on the power supply wouldn't turn on.
FIX: unplug the machine, pull the clock battery, hit the power button to discharge. Then plug it in without the clock battery. The machine should boot perfectly. Shut down, reinstall the clock battery, and now the system is fully functional. Macosxhints
http://docs.info.apple.com/article.html?artnum=300552
Reseat video? try another video card?
My Step #1 is to always boot into Open Firmware (and do reset-nvram, reset-all, if you can't do that, you are sunk).
Oh, and What do you see in verbose mode on startup?
Mac Pro 2GHz 4GB 10K Raptor 23" Cinema Mac OS X (10.4.9) WD RE RAID Aaxeon FW800 PCIe MDD-G4 APC RS1500 Vista

Can only boot into Windows 7. Can't even boot from Snow Leopard DVD.

I have no idea what prompted this. I don't recall installing any OS updates recently, other than some Windows Live apps in Windows 7.
I have an early 2009 Mac Mini with Snow Leopard, and have Windows 7 64-bit installed in a Boot Camp partition. When I installed Windows 7, I couldn't get the Boot Camp utility to install within Windows (I guess because it's 64-bit) so to switch back and forth between OSes, I just shut down the Mac and restart it with the Option key pressed, and select Mac OS X when I want to return to Mac. This has worked for about a month and a half now (ever since I got Windows 7). Suddenly I have problems.
I first had problems booting into Windows or Mac. I got to the grey screen with the Apple logo, with that spinning "progress" thing going for a while, then it would freeze up and get stuck on the grey screen with the Apple logo. I zapped the PRAM. No help. Then, after disconnecting all external drives (I have several) and extra USB devices, I was able to boot from the DVD install disk and reinstall Snow Leopard on my internal drive. Joy, or so I thought. Then I booted into Windows 7, and after some weirdness getting it to start, it did successfully start and ran just peachy.
Then I turned off the Mac and held down the option key (as usual) to return to Mac OS. But now all that happens is that I get a grey screen for a few seconds, then the Mac boots back into Windows 7, which seems to work fine. (I'm in Windows 7 right now.) I turned on one my external drives (Snow Leopard installed, connected via Firewire 800) in hopes that the Mac would boot into that, but same thing. Ignored and back to Windows 7.
Then I thought I'd boot from the install DVD again by putting it in the drive and holding down the C key as I restart, but the same thing--a grey screen for a few seconds, and then booting right into Windows 7. I can't seem to escape Windows 7! It's a bit disturbing when it won't even recognize the install DVD.
I tried to call Apple Care since I'm within my 90 day support window, but of course they are closed. I'm figuring that I'm going to have to take this into an Apple Store, but thought I'd see if anyone has any ideas. Any advice will be appreciated. Thanks.

According to Apple, Win 7 64bit is supported with Bootcamp 3.0. If bootcamp 3.0 is available; I could not find it anywhere on Apple's website. It appears the most recent version is 2.2. The only place I could find 3.0 is not on Apples website and it's a questionable source so I won't post it here.
It may just be a matter of time before Apple makes it available. I'm not suggesting you wait, however if the install disk can't be used, I'm not too sure where u could go from there. Calling Applecare might work.
If you do a simple google search using the terms 'download bootcamp drivers windows 7' u will see what I was referring too.
Here's what I found from Apple (It doesn't specifically mention 64bit however just win7): http://support.apple.com/kb/HT3920
This is not from Apple, but specifically addresses whether they support win7 64bit: http://www.macnn.com/articles/09/08/31/boot.camp.win.7.64.support/
Here is more info about bootcamp 3.0 and win7: http://www.apple.com/support/bootcamp/

Michael C stopped my MacBook booting into Darwin/BSD, but it is now sloooow

I am testing a MacBook 2.16 GHz for possible use at work. Upgraded to 3GB RAM and Hitachi 200GB HD. Performance was great after a week, but one day I got a dark screen at bootup with the Darwin/BSD-login-password message that a lot of people seem to get. I followed Michael Conniff's advice (http://discussions.apple.com/thread.jspa?messageID=4550428) and got the system to boot into the GUI properly. But ever since then performance has been very slow: e.g. selecting the Date and Time takes 5 seconds to launch and clicking on the AirPort icon takes the same amount of time to produce the drop-down menu. It's like the MacBook is running in slow-motion. The exception is the Dock: it pops up quickly and the Apps scroll by quickly. Launching the Apps is another matter, though.
NO OTHER APPS INSTALLED. Really. No MS programs or even freeware. Just iLife '08. All the current updates have been installed. Zapped the PRAM, ran Disk Utility to check the disk and verify permissions--even booted into single-user mode and ran fsck (disk was okay). Tonight I reinstalled the OS in a clean install, installed all the updates, and afterwards the MacBook is just as slow. What is going on? If it's this slow, I guess I won't be using Parallels anytime soon to replace my Dell!

Well, this has been frustrating. The original hard disk also will occasionally boot into Darwin and menu selection is still very sluggish. The local Apple Store won't touch an Apple recertified MacBook--even one that was just delivered a couple of days ago from the Apple Store Online. I then spent several hours on the phone, mostly on hold, but sometimes transferred in a closed loop from Customer Support to Tech Support and back to Customer Support. Sadly, the case number I was given by a rep (the third one I spoke to) isn't showing up as valid either. At this point I just want to return the MacBook (which I think I still can), but I can't reach anyone to arrange for this!

I have a new l7 macbook pro running snow leopard. When I try to boot into windows7 32bit, I get either a blue, black, or flickering screen. Then I have to physically shut down and try again. At that point it will load correctly. Any help?

I have a new l7 Macbook Pro running snow leopard. When I tried to to install windows 7 32 bit on bootcamp, I kept getting a flicking black and blue screen when it tried to install. (Tried several times). I finally downloaded the bootcamp windows support to a flash. I inserted that and finally got it installed. Now when I try to boot into windows I get either a solid black (sometimes blue) or flickering screen and windows will not start up. If I then physically shut down the mac and restart, it will finally boot into windows where it tells me that windows was shut down unexpectently and once I click start windows normally, it will boot up. That will generally let me boot into windows for the remaining of the day. The next day, the same thing happens again. I have tried reinstalling several times, and the same thing keeps happening. It is not my windows disk because it installs flawlessly on the mid 2008 macbook pro. Anyone know how to fix this?

I own HDM 2011. But they have products that aren't listed or hard to find too.
Recommending Pro version for one user's needs:
http://www.wilderssecurity.com/showthread.php?t=297756
Pro vs HDM 2011 feature comparison
http://www.paragon-software.com/home/hdm-personal/comparison.html
Forum topics:
http://www.wilderssecurity.com/showthread.php?t=297756
http://www.wilderssecurity.com/showthread.php?t=303155

A late 2007 Mac Pro (2,1) no longer boots into 64-bit Snow Leopard

In Snow Leopard 10.6.7, my late 2007 Mac Pro (2,1/3.0 GHz/Dual Quad-Core Intel Xeon) no longer seems to be booting into 64-bit mode. I've tried holding down the 6 and 4 keys during startup and even used a Terminal sudo command to force the machine to always boot into 64-bit mode. No matter what I try, an About This Mac>More Info>Software check only reports the following:
     64-bit Kernel and Extensions: No
Before I upgraded from Leopard 10.5 to Snow Leopard 10.6, I carefully researched this, and this Mac Pro model specifically was listed by Apple as being capable of 64-bit booting — meaning that it would utilize at least some extra memory. At the time, under OS 10.5 and early versions of 10.6, when I used this Terminal command...
     ioreg -l -p IODeviceTree | grep firmware-abi
...my Mac Pro 2,1 returned this response:
     "firmware-abi" = <"EFI64">
As a result of my tests and research, I upgraded the installed SDRAM from 4MB to the theoretical maximum Apple indicated this model could support (16MB) so that Adobe Photoshop 12 (CS 5) would fully utilize extra installed memory under Snow Leopard. While using the first versions of 10.6 Snow Leopard, the machine worked fine in 64-bit mode. Now, in the wake of the 10.6.6 or the 10.6.7 update (I didn't notice which), I find that this model no longer even reports itself as being 64-bit capable, though it once did.
Now, the aforementioned Terminal query returns this response:
      "firmware-abi" = <"EFI32">
Also, the Library>Preferences folder does even not contain a file called "com.apple.boot.plist," which some owners have reported editing to force 64-bit booting.
The thing is, I spent a fair amount of money upgrading this machine to the maximum amount of SDRAM supported. I purchased it because it was advertised as being 64-bit capable and I upgraded it because Apple originally reported it as being a 64-bit model. Now, I'm not sure if the extra memory I added is being fully utilized, though Photoshop does report seeing 15547MB of available memory.
Have any other owners of these second-generation Intel Mac Pro's encountered this? Does anyone know what's going on? Am I doing something wrong when checking for the 64-bit installation or architecture? Is Snow Leopard 10.6.7 mis-reporting the architecture for this model? Or did Apple silently withdraw 64-bit support for this machine in a recent OS update?

Hatter: Thanks for the feedback and links. Well, as described in one of the threads you linked to, the document below reinforces your assertion that only Mac Pro's 3,1 or later (early 2008) support 64-bit booting in Snow Leopard:
http://support.apple.com/kb/HT3770
However, if you asked me in court, I would swear on a stack of Bibles that sometime in the past, I read an Apple document indicating that the Mac Pro 2,1 supported 64-bit booting and I really thought I recalled booting this particular machine into 64-bit mode under early versions of Snow Leopard.
I guess I'm mistaken. Certainly, this issue can be confusing. When I read them out loud to myself, even perfectly-written, accurate explanations on the subject can sound like a circular, non-sensical George Bush rationalization being delivered by comic Will Ferrell. I must not be correctly recalling the details of booting into 64-bit mode with this machine. And I guess that since Photoshop has its own memory management scheme, and I only have 16 gigabytes of SDRAM installed anyway, it doesn't matter that much. Furthermore, in one of your links, Jason Snell of Macworld writes:
"...If you’re running a Mac powered by an Intel Core 2 Duo processor or an Intel Xeon processor, your Mac is 64-bit capable. And Snow Leopard runs 64-bit-capable applications in 64-bit mode regardless of whether it’s booting into a 64-bit or 32-bit kernel. In fact, the only big advantage of booting into a 64-bit kernel would be the ability to use more than 32 gigabytes of RAM..."

Reinstall on MDD boots into Terminal

Similar Messages

Maybe you are looking for