PTP/G3 circle-slash installing 10.2 - nvram error? |
October, 19, 2002 2:42 AM |
jeglin |
Specs: PowerTower Pro with PowerLogix G3/500. Apple CDROM ATI Radeon 7000, top slot. Atto ExpressPCIUL2D, 3rd slot. IBM Ultrastar 18Gig, partitioned into 5+13 Throttle set to 24. 465Meg of *non*-interleaved RAM What happens: Run XPF, select 5Gig part. on IBM drive. XPF copies files to 5Gig. XPF reboots automatically. Very brief flash of traditional happy Mac face (small one in center of screen) XPF reboots automatically 2nd time. Comes back with grey OSX Apple, looks like it will work. Circle-slash appears, no further action. Obviously I have tons of variables here, but one sticks out. When I try selecting Extra Diagnostics under Debug, I get a dialog box that says 'could not complete your request because there was an error writing to nvram.' Also, in the XPF log the last lines I see are: Restarting ... Boot-device: pci1/ATTO,ExpressPCIProUL2D/@6:6 Boot-file: -i Boot-command: 0 bootr -v debug=0x20 rd=*scsi-int/@3:9 input-device: kbd output-device: pci1/ATY,RV100Parent/ATY,RV100ad_A NVRAM size limits exceeded Questions: 1. What is the circle-slash most likely to be indicating? I suspect this is different than the 'broken folder' than can appear... 2. What does this nvram issue have to do with it, anything? Is it a cause or an effect? Stefan Jeglinski |
. |
PTP/G3 circle-slash installing 10.2 - nvram error? |
October, 21, 2002 10:43 AM |
OSXGuru |
. |
The 'error writing to nvram' message is unrelated to the primary problem. The issue is that there is only so much room in NVRAM for the settings that XPostFacto needs to make. In your case, you have an unusually long boot-device string, and a long output-device string as well. So adding the "debug" setting to the boot-command pushes you over the NVRAM size limit. The circle-slash means the same thing as the broken folder--it is just a new graphic with the new BootX. Basically, BootX draws the circle-slash to indicate an error condition. If you hold down command-v as the computer is restarting, BootX should operate in verbose mode and print an error message to the screen instead. Assuming that you get that error message, let me know what it is and I may be able to figure out what is wrong. In future versions, I should probably set things up so that BootX always writes the error message along with the circle-slash. |
|
|