On Wed, 2007-05-09 at 22:45 -0700, roger wrote:
Ram4 Testing DRAM : 00000000-0009ffff DRAM fill: 00000000-0009ffff 000a0000 DRAM filled DRAM verify: 00000000-0009ffff 000a0000 DRAM range verified. Done. Testing DRAM : 00100000-007c0000 DRAM fill: 00100000-007c0000 007c0000 DRAM filled DRAM verify: 00100000-007c0000 007c0000 DRAM range verified. Done. Copying LinuxBIOS to RAM. Jumping to LinuxBIOS. LinuxBIOS-2.0.0.0Fallback Wed May 9 15:55:10 PDT 2007 booting...
I should be seeing next roughly "end 35a51f17, start 1" and PCI enumerating. More stuff to look over at this point as the Config.lb isn't entirely filled with PCI bus data.)
As mentioned already, there's probably a DRAM error someplace causing the hang on "booting..."
Think I should also state, I'm getting a 0xE7 postcode either during DRAM Verify or DRAM Test. Other then this, I get the usual 0x80 before and 0x80 at "Jumping to LinuxBIOS..."
Are there any debugging methods I can try during DRAM verify/tests?
I see something pertaining to prink_debug but it's not being provided by console.c in auto.c, requires another include or something.
I'll go back to the tyan/s1846 profile and see if I get the same results.
-- Roger http://www.eskimo.com/~roger/index.html Key fingerprint = 8977 A252 2623 F567 70CD 1261 640F C963 1005 1D61
Thu May 10 20:16:58 PDT 2007