Supermicro X8dtt-f-sg007

nippy

New Member
Jan 29, 2014
5
0
1
good day!
buy motherboard Supermicro X8dtt-f-sg007 (rev.1.02)
bios old 2009 , not working 56**
bios X8dtt-f (BAD)
Please help.
 
Last edited:

MikeC

Member
Apr 27, 2013
59
11
8
UK
Older BIOS may not support 56**, but will support L5520 and you can then update BIOS to latest version and then use 56**
 

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,056
1,600
113
CA
Correct, the older BIOS of some SM boards won't support the XEON 56xx series but do support XEON 55xx series.
You need a 55xx series chip to update BIOS to support 56xx, this is on the SuperMicro page for motherboars that require this if you need to make sure your board CAN support 56xx even after a BIOS update.
 

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,056
1,600
113
CA
Update bios with a 5500 chip to support 5600? The page didn't say to do this, but other SM pages that support 5500/5600 say you need to update the motherboard to support 5600 chips, some I've not needed to and others I've had.
 

nippy

New Member
Jan 29, 2014
5
0
1
Hello
I have many CPU 55** (e5506, l5520 , x5550 , x5570 , w5580)
problem in that, after flash bios (2013 R 2.1c ) card not respond, (afudos /P /B /N /K /R /C /L2)

card only works with bios (09.23.2009)



I added a microcodes from bios (2013 R 2.1c) card to work, but 56 ** CPU does not support (
Firmware R 2.1c motheboard (x8dtt-f-SG007) not work.




THANKS!!!
 
Last edited:

James2020

New Member
Oct 14, 2015
5
0
1
23
Hello
I have many CPU 55** (e5506, l5520 , x5550 , x5570 , w5580)
problem in that, after flash bios (2013 R 2.1c ) card not respond, (afudos /P /B /N /K /R /C /L2)

card only works with bios (09.23.2009)



I added a microcodes from bios (2013 R 2.1c) card to work, but 56 ** CPU does not support (
Firmware R 2.1c motheboard (x8dtt-f-SG007) not work.




THANKS!!!
Was there any update to this Nippy? I have just bought the same boards and am experiencing problems such as no visual output to monitor. My cpus are 5650 Xeon.
 

tjsgifan

New Member
Nov 20, 2015
21
17
3
46
Hi All, I work for a Supermicro reseller and have had a load of these boards in and have established the early version's with version 1.x BIOS should not be flashed using the image on Supermicro's website at all, it render's them unusable. Only if your running BIOS 2.x should you use that file. We've been given a different procedure to use to update earlier boards and it gives full support for X5600 series CPU's.

I'm waiting to test a board in the next couple of days before I post the procedure as I don't want to be held responsible for a duff procedure, but I will let you know ASAP.
 

FMA1394

Active Member
Jan 11, 2013
624
186
43
Is there a way to unbrick boards that got flashed the wrong way without resorting to using something like a chip clamp?
 

tjsgifan

New Member
Nov 20, 2015
21
17
3
46
I'm told by Supermicro that this is not possible, you need to get the board's RMA'd, but for most, these boards are 4-5 years old already and there is little to no chance of warranty support.
 

tjsgifan

New Member
Nov 20, 2015
21
17
3
46
Hi All,

Confirmed working solution :

Edit your AMI.BAT file to include the following options at the end of the command : /mer /opr /fdt

So it becomes :

AFUDOS.EXE %1 /P /B /N /K /R /C /L2 /mer /opr /fdt
 
  • Like
Reactions: James2020

James2020

New Member
Oct 14, 2015
5
0
1
23
Hi Tjsgifan,

Maybe you can help me, I bought a couple of these boards which I am struggling to get ed and working, as of now without going through huge details the blue light at the back of the board for the BMC lights up flashing but I was at first was not getting any monitor out put and now I can't even get power to the cpu fan-



My build is hack where I haven't got the original chassis so for example - I haven't got the all the switches (JF1 Header) filled up- only the on and off and reset. I mention this because it terms of exhausting what could be left to get the systems to turn on so I can upgrade the bios, I'm thinking it might have to do with the JF1 header not having all the pins switches connected as they would be in the official chassis.
 

Rektor87

New Member
Jan 11, 2016
7
0
1
33
Hi All,

Confirmed working solution :

Edit your AMI.BAT file to include the following options at the end of the command : /mer /opr /fdt

So it becomes :

AFUDOS.EXE %1 /P /B /N /K /R /C /L2 /mer /opr /fdt
Hello,
Tell me where to get the bios to X56xx? on the site Supermicro bios X8DTT4.422, but the BIOS does not have keys: /mer /opr /fdt
Please help.
 

tjsgifan

New Member
Nov 20, 2015
21
17
3
46
Hello,
Tell me where to get the bios to X56xx? on the site Supermicro bios X8DTT4.422, but the BIOS does not have keys: /mer /opr /fdt
Please help.
You need to edit the AMI.BAT file as per the instructions and add the keys /mer /opr /fdt to the end of the line.

So :

AFUDOS.EXE %1 /P /B /N /K /R /C /L2

becomes

AFUDOS.EXE %1 /P /B /N /K /R /C /L2 /mer /opr /fdt

Save the AMI.bat file and then run the command as instructed in the download.
 

Rektor87

New Member
Jan 11, 2016
7
0
1
33
You need to edit the AMI.BAT file as per the instructions and add the keys /mer /opr /fdt to the end of the line.

So :

AFUDOS.EXE %1 /P /B /N /K /R /C /L2

becomes

AFUDOS.EXE %1 /P /B /N /K /R /C /L2 /mer /opr /fdt

Save the AMI.bat file and then run the command as instructed in the download.
I did all what you say, add the keys /mer /opr /fdt to the end of the line in ami.bat. But when ami.bat run, there show error. (without this key ami.bat run good). I use x8dtt4.422 bios. Do you use this bios with /mer /opr /fdt keys?
 
Last edited:

tjsgifan

New Member
Nov 20, 2015
21
17
3
46
OK so what is the error? it is case sensitive and you should be typing :

AMI.BAT X8DTT4.422

at the DOS prompt. What media are you booting from?
 

Rektor87

New Member
Jan 11, 2016
7
0
1
33
OK so what is the error? it is case sensitive and you should be typing :

AMI.BAT X8DTT4.422

at the DOS prompt. What media are you booting from?
Booting from usb flash (which dos formated) and with default keys it run.
Ok, i try write capital letter, may be it problem.
Write later, thank you :)