On Fri, May 07, 2010 at 05:57:35AM -0400, Arne Georg Gleditsch wrote:
Joe Korty joe.korty@ccur.com writes:
As a first time coreboot user, I thought that I should first try it out on a supported board. That way I would learn the ropes a bit before even thinking about doing something more challenging.
Naturally I am having troubles. I suspect that as a newbie I am probably doing something stupid. But then I've heard that mb manufacturers like to change things around without notice, so maybe I'm doing things right and what was once a supported mb, no longer is.
The hardware: SuperMicro H8DME-2. Four 1Gbyte DDR2-667/533/400 Registered ECC SDRAM sticks from Crucial. Two Quad-Core AMD 2378 2.4 GHz Processors. Onboard video. One SATA disk. One PATA DVD-ROM reader. NULL modem serial cable from COM1 to COM1 on another PC.
The details: When booting coreboot, nothing happens for about 45 seconds. Then the fans speed up to high and some messages start appearing on the serial line. These messages print rather slowly (maybe 1 second/message). They are:
coreboot-4.0-r5521M Wed May 5 10:53:42 EDT 2010 starting... *sysinfo range: [000cf000,000cf730] bsp_apicid=00 Enabling routing table for node 00 done. Enabling SMP settings (0,1) link=00This looks like the bootup code for gen f Opterons. It doesn't look like the h8dme has a fam10 variant yet, which is what you need for the 2378 CPUs.
Thanks Arne! I'll have to figure out how to proceed from here.
On a side note, it _looks_ like the slowdown might be due to the udelay unification. Still bisecting.
Joe
The hardware: SuperMicro H8DME-2. Four 1Gbyte DDR2-667/533/400 Registered ECC SDRAM sticks from
Crucial.
Two Quad-Core AMD 2378 2.4 GHz Processors. Onboard video. One SATA disk. One PATA DVD-ROM reader. NULL modem serial cable from COM1 to COM1 on another PC.
The details: When booting coreboot, nothing happens for about 45 seconds. Then the fans speed up to high and some messages start appearing on the serial line. These messages print rather slowly (maybe 1 second/message). They are:
coreboot-4.0-r5521M Wed May 5 10:53:42 EDT 2010 starting... *sysinfo range: [000cf000,000cf730] bsp_apicid=00 Enabling routing table for node 00 done. Enabling SMP settings (0,1) link=00This looks like the bootup code for gen f Opterons. It doesn't look like the h8dme has a fam10 variant yet, which is what you need for the 2378 CPUs.
Thanks Arne! I'll have to figure out how to proceed from here.
On a side note, it _looks_ like the slowdown might be due to the udelay unification. Still bisecting.
I'm surprised you found a revision that works, since it has never supported fam10. I think it would be more fruitful for you to look at one of the boards that has both fam10 and k8 support, and try to put together an h8dme_fam10 port.
Thanks, Myles
On Fri, May 07, 2010 at 07:30:08AM -0600, Myles Watson wrote:
This looks like the bootup code for gen f Opterons. It doesn't look like the h8dme has a fam10 variant yet, which is what you need for the 2378 CPUs.
Thanks Arne! I'll have to figure out how to proceed from here.
On a side note, it _looks_ like the slowdown might be due to the udelay unification. Still bisecting.
I'm surprised you found a revision that works, since it has never supported fam10. I think it would be more fruitful for you to look at one of the boards that has both fam10 and k8 support, and try to put together an h8dme_fam10 port.
For the record, I've been trying to get that going for a while, but have not had much success - very early hangs in the fam10 code on this board. Cf. the problems Knut is having, I think...
Thanks, Ward.
On Fri, May 07, 2010 at 07:30:08AM -0600, Myles Watson wrote:
This looks like the bootup code for gen f Opterons. It doesn't look like the h8dme has a fam10 variant yet, which is what you need for
the
2378 CPUs.
Thanks Arne! I'll have to figure out how to proceed from here.
On a side note, it _looks_ like the slowdown might be due to the
udelay
unification. Still bisecting.
I'm surprised you found a revision that works, since it has never
supported
fam10. I think it would be more fruitful for you to look at one of the boards that has both fam10 and k8 support, and try to put together an h8dme_fam10 port.
For the record, I've been trying to get that going for a while, but have not had much success - very early hangs in the fam10 code on this board. Cf. the problems Knut is having, I think...
Sorry I forgot that. The Supermicro names all blend together for me. Have you tried adding the extra bits to the masks in resourcemap.c?
Thanks, Myles
On Fri, May 07, 2010 at 09:37:54AM -0400, Ward Vandewege wrote:
On Fri, May 07, 2010 at 07:30:08AM -0600, Myles Watson wrote:
This looks like the bootup code for gen f Opterons. It doesn't look like the h8dme has a fam10 variant yet, which is what you need for the 2378 CPUs.
I'm surprised you found a revision that works, since it has never supported fam10. I think it would be more fruitful for you to look at one of the boards that has both fam10 and k8 support, and try to put together an h8dme_fam10 port.
For the record, I've been trying to get that going for a while, but have not had much success - very early hangs in the fam10 code on this board. Cf. the problems Knut is having, I think...
What AMD Processor model numbers have you folks been using on the SuperMicro H8DME-2 mainboards? I'd like to buy a pair of known-working CPUs.
I currently have a pair of AMD model #2378 Processors, which are of the fam10 line, with a pair of model #2222 CPUs, which are of the K8 line.
Thoughts? Regards, Joe
On Fri, May 07, 2010 at 01:59:12PM -0400, Joe Korty wrote:
What AMD Processor model numbers have you folks been using on the SuperMicro H8DME-2 mainboards? I'd like to buy a pair of known-working CPUs.
I currently have a pair of AMD model #2378 Processors, which are of the fam10 line, with a pair of model #2222 CPUs, which are of the K8 line.
The port for that board was done on a pair of 2216 HE CPUs.
You may be hard pressed to find those for sale these days...
Thanks, Ward.
-
Joe Korty -
Myles Watson -
Ward Vandewege