rev 1.0 - http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?Produ... rev 1.1 -http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?Produ... rev 2.0 - http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?Produ...
All these references says that GA-M57SLI-S4 "Supports AMD Phenom X4/ Phenom X3 processors*" but
http://www.coreboot.org/Supported_Motherboards only list "AMD Sempron™ / Athlon™ 64 / FX / X2" under "CPU" for "GA-M57SLI-S4".
Why is that so?
Will you add AMD Phenom X3, AMD Phenom X4 as suggested?
David Englund wrote:
All these references says that GA-M57SLI-S4 "Supports AMD Phenom X4/ Phenom X3 processors*" but
http://www.coreboot.org/Supported_Motherboards only list "AMD Sempron??? / Athlon??? 64 / FX / X2" under "CPU" for "???GA-M57SLI-S4".
Why is that so?
K8/Fam10 CPU support is not unified in coreboot v2, and because the m57sli target in coreboot was created before Fam10 was available, coreboot on m57sli only supports K8.
Will you add AMD Phenom X3, AMD Phenom X4 as suggested?
The code to support Fam10 CPUs is already in coreboot, but no target for the m57sli uses it. It is certainly possible to create a new m57sli target for Fam10 CPUs however.
Since the board is now EOL I don't think we will do it, but any efforts are welcome.
For v3 I hope we can unify K8 and Fam10, which would mean that a v3 port for the m57sli will indeed support all CPUs that are compatible, but such a port is still some time in the future. v3, although 2 years old, is still a baby.
//Peter
On Wed, Sep 10, 2008 at 11:14 AM, Peter Stuge peter@stuge.se wrote:
David Englund wrote:
All these references says that GA-M57SLI-S4 "Supports AMD Phenom X4/ Phenom X3 processors*" but
http://www.coreboot.org/Supported_Motherboards only list "AMD Sempron??? / Athlon??? 64 / FX / X2" under "CPU" for "???GA-M57SLI-S4".
Why is that so?
K8/Fam10 CPU support is not unified in coreboot v2, and because the m57sli target in coreboot was created before Fam10 was available, coreboot on m57sli only supports K8.
On the subject of CPU support (in v2, at least) is there something to be careful about, when using opteron 165 (dual core opteron without registered ECC ram support)
I'm asking that because I have such a CPU and I have really strange bug when booting linux kernel, and I have been told that it could be RAM-related... And I'm actually unable to pinpoint the problem myself.
Vincent Legoll wrote:
is there something to be careful about, when using opteron 165 (dual core opteron without registered ECC ram support)
Not that I know of, but maybe someone else knows.
I'm asking that because I have such a CPU and I have really strange bug when booting linux kernel, and I have been told that it could be RAM-related... And I'm actually unable to pinpoint the problem myself.
Let memtest86 run for a few days.
//Peter
On Wed, Sep 10, 2008 at 7:04 PM, Peter Stuge peter@stuge.se wrote:
Vincent Legoll wrote:
is there something to be careful about, when using opteron 165 (dual core opteron without registered ECC ram support)
Not that I know of, but maybe someone else knows.
Has anyone run coreboot on opteron 1X5 series ?
I'm asking that because I have such a CPU and I have really strange bug when booting linux kernel, and I have been told that it could be RAM-related... And I'm actually unable to pinpoint the problem myself.
Let memtest86 run for a few days
A few days will be a pain to do, the box is noisy and in my only room, and would need another box running alongside to serve as serial console. UGGH
I've ran it for 2 hours and it had found nothing, OK I know that to be sure one has to let it run for a few days, but the ram problem I'd be expecting is not of the bad HW kind, more of the badly initialized HW, maybe MTRR or something like that...
The box ran linux just fine for a long time being a networked distcc compile node, so CPU & ram should be fine (this kind of setup often exhibits any ram problems, maybe even more than memtest under certain circumstances)
I'm still not having problem with it booted through legacy BIOS. Are you suggesting coreboot is so aggressive on ram that it would exhibit such behaviours ?
I think the likelyhood that I messed something setting up coreboot is probably higher than faulty HW...
Hi,
Has anyone run coreboot on opteron 1X5 series ?
I used 144 and now using 175. Works fine.
Rudolf
On Wed, Sep 10, 2008 at 10:44 PM, Rudolf Marek r.marek@assembler.cz wrote:
Has anyone run coreboot on opteron 1X5 series ?
I used 144 and now using 175. Works fine.
Thanks for the info.
Which motherboard ? What RAM (size, dual-channel, type, etc...)
Could you send me a kernel boot log ? eventually with "debug apic=debug loglevel=9" parameters a coreboot log.
Again, thanks
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello here it is:
Decoding EEPROM: /sys/bus/i2c/drivers/eeprom/0-0050 Guessing DIMM is in bank 1
- ---=== SPD EEPROM Information ===--- EEPROM Checksum of bytes 0-62 OK (0x98) # of bytes written to SDRAM EEPROM 128 Total number of bytes in EEPROM 256 Fundamental Memory type DDR SDRAM SPD Revision 0.0
- ---=== Memory Characteristics ===--- Maximum module speed 400MHz (PC3200) Size 512 MB tCL-tRCD-tRP-tRAS 2.5-3-3-8 Supported CAS Latencies 2.5, 2 Supported CS Latencies 0 Supported WE Latencies 1 Minimum Cycle Time (CAS 2.5) 5 ns Maximum Access Time (CAS 2.5) 0.6 ns Minimum Cycle Time (CAS 2) 6 ns Maximum Access Time (CAS 2) 0.7 ns
- ---=== Manufacturing Information ===--- Manufacturer Kingston Manufacturing Location Code 0x04 Part Number K Manufacturing Date 2005-W23 Assembly Serial Number 0x6C3E7B6C
Decoding EEPROM: /sys/bus/i2c/drivers/eeprom/0-0051 Guessing DIMM is in bank 2
- ---=== SPD EEPROM Information ===--- EEPROM Checksum of bytes 0-62 OK (0x98) # of bytes written to SDRAM EEPROM 128 Total number of bytes in EEPROM 256 Fundamental Memory type DDR SDRAM SPD Revision 0.0
- ---=== Memory Characteristics ===--- Maximum module speed 400MHz (PC3200) Size 512 MB tCL-tRCD-tRP-tRAS 2.5-3-3-8 Supported CAS Latencies 2.5, 2 Supported CS Latencies 0 Supported WE Latencies 1 Minimum Cycle Time (CAS 2.5) 5 ns Maximum Access Time (CAS 2.5) 0.6 ns Minimum Cycle Time (CAS 2) 6 ns Maximum Access Time (CAS 2) 0.7 ns
- ---=== Manufacturing Information ===--- Manufacturer Kingston Manufacturing Location Code 0x04 Part Number K Manufacturing Date 2005-W23 Assembly Serial Number 0x6C3EA76C
Number of SDRAM DIMMs detected and decoded: 2
Rudolf
-
David Englund -
Peter Stuge -
Rudolf Marek -
Vincent Legoll