roger wrote:
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?
Not really. A few things to check: is your CAS latency being set the same on the northbridge as it's being set by MRS? Is the MA Map type correct? Is DRAM refresh being enabled correctly? Is NBXCFG correct (ie correctly set for ecc/parity, etc)? ECC should probably not be enabled for now even if your ram supports it, I think ECC requires some special init that isn't being done (yet). What happens if you don't perform the ram test? Boot up the factory BIOS, with the timings set manually to their largest values (or whatever values linuxbios is using), if your BIOS allows it, and compare the output lspci -nxxx -s 0:0.0 to dump_pci_device(0), and see if anything shows up. Once again, good luck ;)
-Corey