Update: just spoke to Brian (not on LJ) who thought that possibly it could be a CPU or memory thing, on the grounds that possibly up till that point, it would be running on BIOS only but then would need to load a default driver to read from the CD-ROM and thus need to invoke main memory. Which sounded plausible, though we weren't sure if that theoretical sequence is actually true :-)
don't know what you all think about that reasoning or if someone can confirm the hypothetical facts behind it... but I think I will try each of the memory sticks by itself next (which I'd been thinking anyway was an un-tried possible move) and swop them around from slot to slot a bit.
bit reluctant to unseat the CPU & heatsink but I suppose that would be next if no-one else has better ideas...
If you see anything on screen, then the CPU is alive - you can see how healthy in the BIOS. As far as the memory goes, you might want to go into the BIOS and have it run a full POST but it either way it will report how much memory it can find. If it's pretty much what you put into the machine (it could be a little less, if the motherboard reserves some for the on-board display), then that's OK as well.
The interesting thing is, the only way for the system to know what make of drive it is, is to ask it - and so data-wise it's OK. If the name was a little corrupted, then it would be a guaranteed cable not-plugged-in properly. Since it looks OK though, the drive is fine, and the problem is almost certainly elsewhere.
If you see anything on screen, then the CPU is alive
Well it is then :-)
you can see how healthy in the BIOS.
not sure what you mean by that.
re memory If it's pretty much what you put into the machine (it could be a little less, if the motherboard reserves some for the on-board display), then that's OK as well.
yes, realised after my last post that in fact the "1984MB OK" already reported probably indicated the memory wasn't the problem (which is 2 gig less some amount for something or other, think it was indeed the display)
The interesting thing is, the only way for the system to know what make of drive it is, is to ask it - and so data-wise it's OK. If the name was a little corrupted, then it would be a guaranteed cable not-plugged-in properly. Yeah, that's what I thought. Actually I wasn't sure if it was an all-or-nothing deal, because maybe it could get the name and still not be fully working. But I don't think it can be the cable itself, at any rate, because of the swopping in or out of cables and alternate drives. If
( ... )
That it gets into the BIOS is a good sign, as in it could be worse :)
These are parentheses: (), those brackets [] are normal.
The difference in memory size is how much you've allocated for the built-in graphics: 2048-1984 = 64M (this is changeable in the BIOS).
Tried connecting (with CPU, fan and RAM installed) just:
the CPU fan connector (or it'll go 'eek, I'm getting too hot' quickly) the 24 pin power connector (or it won't work) the 4 pin power connector (ditto) the chassis speaker connector (so you can hear any beeps) the floppy drive (if you get this one the wrong way around it will appear to be permanently 'on') with that boot floppy the keyboard the display
.. and powering on? Get into the BIOS setup and press F9 (restore default settings) and reboot. It should boot from the floppy (or at least attempt to do so!) and if it doesn't, there is something odd
( ... )
This says that your CPU is only supported by version P1.60 of the BIOS and it looks like you've currently got P1.30:
"AMIBIOS(C)2005 American Megatrends, Inc. ALiveNF6G-DVI BIOS P1.30 CPU : AMD Athlon(tm) 64 X2 DualCore Processor 3600+ Speed : 1.90GHz Count : 2"
.. so even though it's getting the basics (speed and name) right, it may not be setting the various registers correctly for a Brisbane rather than a Windsor core.
So.. return the board with an 'Oi, you knew I wanted it to work with that processor' or find someone with a CPU it will support, and borrow it to update the BIOS.
The joys of getting a new, better, processor variant :/
I got the board from Tekheads - I picked them for their good customer service, and I think there's a good chance they will flash the BIOS for me (for little or no money) even though I didn't actually check with them beforehand (already knew the board supported the CPU, didn't realise BIOS might be an issue) & was getting the CPU elsewhere so they couldn't have known from that. Will ask them, at any rate.
Comments 6
don't know what you all think about that reasoning or if someone can confirm the hypothetical facts behind it... but I think I will try each of the memory sticks by itself next (which I'd been thinking anyway was an un-tried possible move) and swop them around from slot to slot a bit.
bit reluctant to unseat the CPU & heatsink but I suppose that would be next if no-one else has better ideas...
Reply
The interesting thing is, the only way for the system to know what make of drive it is, is to ask it - and so data-wise it's OK. If the name was a little corrupted, then it would be a guaranteed cable not-plugged-in properly. Since it looks OK though, the drive is fine, and the problem is almost certainly elsewhere.
Reply
Well it is then :-)
you can see how healthy in the BIOS.
not sure what you mean by that.
re memory
If it's pretty much what you put into the machine (it could be a little less, if the motherboard reserves some for the on-board display), then that's OK as well.
yes, realised after my last post that in fact the "1984MB OK" already reported probably indicated the memory wasn't the problem (which is 2 gig less some amount for something or other, think it was indeed the display)
The interesting thing is, the only way for the system to know what make of drive it is, is to ask it - and so data-wise it's OK. If the name was a little corrupted, then it would be a guaranteed cable not-plugged-in properly. Yeah, that's what I thought. Actually I wasn't sure if it was an all-or-nothing deal, because maybe it could get the name and still not be fully working. But I don't think it can be the cable itself, at any rate, because of the swopping in or out of cables and alternate drives. If ( ... )
Reply
These are parentheses: (), those brackets [] are normal.
The difference in memory size is how much you've allocated for the built-in graphics: 2048-1984 = 64M (this is changeable in the BIOS).
Tried connecting (with CPU, fan and RAM installed) just:
the CPU fan connector (or it'll go 'eek, I'm getting too hot' quickly)
the 24 pin power connector (or it won't work)
the 4 pin power connector (ditto)
the chassis speaker connector (so you can hear any beeps)
the floppy drive (if you get this one the wrong way around it will appear to be permanently 'on') with that boot floppy
the keyboard
the display
.. and powering on? Get into the BIOS setup and press F9 (restore default settings) and reboot. It should boot from the floppy (or at least attempt to do so!) and if it doesn't, there is something odd ( ... )
Reply
This says that your CPU is only supported by version P1.60 of the BIOS and it looks like you've currently got P1.30:
"AMIBIOS(C)2005 American Megatrends, Inc.
ALiveNF6G-DVI BIOS P1.30
CPU : AMD Athlon(tm) 64 X2 DualCore Processor 3600+
Speed : 1.90GHz Count : 2"
.. so even though it's getting the basics (speed and name) right, it may not be setting the various registers correctly for a Brisbane rather than a Windsor core.
So.. return the board with an 'Oi, you knew I wanted it to work with that processor' or find someone with a CPU it will support, and borrow it to update the BIOS.
The joys of getting a new, better, processor variant :/
Reply
I got the board from Tekheads - I picked them for their good customer service, and I think there's a good chance they will flash the BIOS for me (for little or no money) even though I didn't actually check with them beforehand (already knew the board supported the CPU, didn't realise BIOS might be an issue) & was getting the CPU elsewhere so they couldn't have known from that. Will ask them, at any rate.
Thank you for this skilful bit of detective work!
Live & learn eh :-)
Reply
Leave a comment