Hello all,
Previously I posted regarding having problems getting my Dual G4 450 system to boot OSX while it booted OS9 just fine. I spent more time doing researching and found that when watching the install disc (worked previously) is booting in verbose mode, it will hang with the message "Still waiting on boot device" and it will display that over and over again.
However as I was researching this, I took notice of what was listed immediately before the boot device error. It started off as: From path: "/pci@f2000000/pci-bridge@d/mac-io@7/ata-3@200000/disk@0:9,\mach_kernel",
which as I later learned is the location of the boot device (cd or hdd) being booted from. More importantly the disk@0:9 in my case is the disk and partition that the boot program is looking for.
In my case I do NOT have 9 partitions so after more reading I went into the NVRAM/Open Firmware settings to change this. I changed the boot-device setting via the setenv boot-device command to reflect a disk@0:0 setting but that did not help. I even reset the entire nvram and pram settings to factory defaults. That did not help at all. The boot program on the CD CONTINUED to reference the disk@0:9 location even after I made the changes in the firmware.
How can I go about solving this? OS9 works fine, as does the different PPC flavors of linux.
Previously I posted regarding having problems getting my Dual G4 450 system to boot OSX while it booted OS9 just fine. I spent more time doing researching and found that when watching the install disc (worked previously) is booting in verbose mode, it will hang with the message "Still waiting on boot device" and it will display that over and over again.
However as I was researching this, I took notice of what was listed immediately before the boot device error. It started off as: From path: "/pci@f2000000/pci-bridge@d/mac-io@7/ata-3@200000/disk@0:9,\mach_kernel",
which as I later learned is the location of the boot device (cd or hdd) being booted from. More importantly the disk@0:9 in my case is the disk and partition that the boot program is looking for.
In my case I do NOT have 9 partitions so after more reading I went into the NVRAM/Open Firmware settings to change this. I changed the boot-device setting via the setenv boot-device command to reflect a disk@0:0 setting but that did not help. I even reset the entire nvram and pram settings to factory defaults. That did not help at all. The boot program on the CD CONTINUED to reference the disk@0:9 location even after I made the changes in the firmware.
How can I go about solving this? OS9 works fine, as does the different PPC flavors of linux.