the slings and arrows... |
October, 21, 2002 11:01 AM |
asarath |
My Configuration: 8600/200 upgraded with powerlogix g3/400. 352 MB RAM (2x128 MB - in A1 & A2, 1x64 MB - in B1, 2x16 MB - in A3 & B3); 2GB stock drive, 4GB Quantum at scsi 6 (partitioned into 2x 2GB), a 40GB seagate on an ultratek 66 card, stock internal cd and external yamaha cdrw; no-name usb card; owc firewire card; display is the av card that came with the 8600. Stock drive runs 9.0.4. All hard drives set up with Apple Drive Setup. Tried installing 10.0 on one of the quantum partitions with xpf 2.2.2. This is what happened: the installation proceeded smoothly through choosing drive, installation type etc. During the actual installation, this happened after about 100MB was installed: Unresolved kernel trap (cpu 0): 0x300 - Data access DAR= 0x783b7b18 PC=0x000a3224 Latest crash info for cpu 0: Exception state (sv=0x0e904800) PC=0x000A3224; MSR=0x00009030; DAR=0x783b7b18; DSISR=0x40000000; LR=0x0015c6c0; RI=0x0a50bbb0; XCP= 0x0000000c (0x300 - Data access) Backtrace: 0x00251360 0x0015c6c0 0x000a834c 0x000a7d9c 0x000af144 0x00092848 0x0008e9a0 0x3864889e Proceeding back via exception chain Exception state (sv=0x0ea3d800) PC=0x7000B7BC; MSR=0x0000d030; DAR=0x80009168; DSISR=0x40000000; LR=0x7000b4f4; RI=0xbffffc30; XCP= 0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 1.4: Sun Sep 9 15:39:59 PDT 2001; root: xnu/xnu -201.obj~1/ RELEASE_PPC Memory access exception (1,0,0) Waiting for remote debugger connection Options Type continue c reboot r *I pressed continue* panic (cpu 0) = 0x300 - Data access Latest stack backtrace for cpu 0: Backtrace 0x0008122c 0x000815cc 0x00027d38 0x0008b4ec 0x0008aac0 0x0008e82c Proceeding back via exception chain: Exception state (sv=0x0e904800) PC=0x000A3224; MSR=0x00009030; DAR=0x783b7b18; DSISR=0x40000000; LR=0x0015c6c0; RI=0x0a50bbb0; XCP= 0x0000000c (0x300 - Data access) Backtrace: 0x00251360 0x0015c6c0 0x000a834c 0x000a7d9c 0x000af144 0x00092848 0x0008e9a0 0x3864889e Proceeding back via exception chain Exception state (sv=0x0ea3d800) PC=0x7000B7BC; MSR=0x0000d030; DAR=0x80009168; DSISR=0x40000000; LR=0x7000b4f4; RI=0xbffffc30; XCP= 0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 1.4: Sun Sep 9 15:39:59 PDT 2001; root: xnu/xnu -201.obj~1/ RELEASE_PPC Memory access exception (1,0,0) Waiting for remote debugger connection Options Type continue c reboot r *I pressed continue to see where it would go* Continuing panic: We are hanging here.... Tried again, but rebooted at the prompt: rebooted to a broken system folder. Tried yet again with a borrowed 10.1.3 disk (just to see if the problem repeated) but the whole process got hung even before installation, with a 'waiting for root device' message. Turned out to be a problem with the CD itself. I recovered the damaged file (essentials.pax.gz) and copied the whole CD. Then I read the thread about BootX! In any case, it still gives me the waiting for root device message. And as a special favour, someone lent me Jaguar to try. On my internal 12x (or 8x, not sure) CD, the monitor gives me a message "OUT OF RANGE". On the external Yamaha, which is properly terminated, I get to the install stage - choosing drive etc. The installation starts up and then abruptly exits due to "an unexpected error cpu(0)". Returned Jaguar, 10.1.3 and, belatedly tried Gauge Pro. The memory test told me there was a problem at $04000000 and every segment till $04000206 when I gave up pressing the continue button. Obviously one of the RAM chips is defective - but which one? (The next time I ran gauge pro, my machine crashed!) Please help Ashok Sorry if the line breaks get garbled. |
. |
RE: the slings and arrows.(Thanks Ryan) |
October, 31, 2002 3:16 AM |
asarath |
. |
Solved!!! Fortune, they say favours the brave. So for the first time in my life I fiddled with the RAM in my Mac (done it on a PC once, but a PC is not as precious ;-)). Discovered that my problem *is* the 64MB RAM chip. Took it out and I'm doing just fine with OS 10. I think the $04000000 has to do with the physical location of the chip, because when I moved it to slot A3, the problem arose at $0300000... Let's see how stable OS 10 is on my machine...booted back and forth between it and 9.0.4, tried running a few apps like TextEdit, iMovie etc. They seem ok. Slow but then I loaded OS10 primarily to get a MacOS unsupported USB digital camera to download pictures through IOXPERTS' utility. (It was that or use a Windows machine!) Turns out I'll have to wait a while before the camera is supported. Thanks again Ryan for XPF and the forum. Live long and prosper. Ashok |
. |
RE: the slings and arrows... |
October, 21, 2002 11:11 PM |
asarath |
. |
Thanks Ryan. Unfortunately Gauge Pro gives no indication of how to interpret its findings. Though it's funny that the problem starts at the 64 MB mark - that probably means either that my 64MB chip at slot B1 is being read as the first RAM chip or that there's a problem halfway through one of the 128 MB chips. I'll see if the reseller has someon who can diagnose this. Will try Gauge PRo again and see how long the problem continues. I'm not too confident of swapping RAM in and out... (though I'm ok with PCI cards!) Thanks again for xpf. Ashok |
. |
RE: the slings and arrows... |
October, 21, 2002 2:39 PM |
OSXGuru |
. |
All of this is extremely consistent with a RAM problem of some kind, as Gauge Pro says. I'm actually not sure how to tell which chip is the problem--does Gauge Pro give any instructions on that? If I'm interpreting $04000000 correctly, then the problem starts at the 64 MB mark. So I'm guessing that the "first" chip is a 64 MB chip which is OK, and then the "next" one isn't. But I'm not sure how "first" and "next" translate to physical memory slots. |
|
|