Board:asus/kfsn4-dre: Difference between revisions

From coreboot
Jump to navigation Jump to search
No edit summary
No edit summary
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
The KFSN4-DRE is a relatively modern AMD Family 10h motherboard. It is well supported and stable under Coreboot, with all CPUs, RAM, and peripherals functioning normally.
[[File:Kfsn4-dre-mainboard-raptor-devsys.png|400px|thumb|right|ASUS KFSN4-DRE PCB 1.04G at Raptor Engineering.]]


[https://www.raptorengineeringinc.com Raptor Engineering] hosts an automated test system which checks this board for proper functionality every six hours.  Successful test results are recorded to the board status repository, while failed tests are reported to the coreboot mailing list.
== General Information ==


Automated tests for patchsets on Gerrit are available by adding the "Raptor Engineering Automated Test Stand <noreply@raptorengineeringinc.com>" user as a reviewer.
The KFSN4-DRE is a relatively modern AMD K8 / Family 10h motherboard. It is well supported and stable under Coreboot with Family 10h processors, with all CPUs, RAM, and peripherals functioning normally.  K8 processors currently require specific RAM configurations to work correctly.


{| class="wikitable"
This board is automatically tested by Raptor Engineering's test stand.  For more details please visit [[AutoTest/RaptorEngineering]].
|+Test stand details
|-
|CPU
|2x Opteron 8347 (Fam10h @ 1.9GHz / 4 cores ea.)
|-
|RAM
|2GB DDR2-667 on Node 0 channel 0
|2GB DDR2-667 on Node 0 channel 1
|2GB DDR2-667 on Node 1 channel 0
|2GB DDR2-667 on Node 1 channel 1
|-
|OS
|Debian Jessie 64-bit, kernel 3.16.0
|-
|Add-on cards
|None
|}


{| class="wikitable"
== Installation Notes ==
|+crossgcc
* coreboot can be flashed internally when migrating from the proprietary BIOS. Flashrom can safely reprogram the ROM under Linux.
|-
* When migrating from the proprietary BIOS, after flashing coreboot the CMOS memory should be cleared. Failing to clear the CMOS could result in odd hangs during the boot process.
|Package
|Version
|-
|ACPICA
|20150204
|-
|binutils
|2.25
|-
|gcc
|4.9.2
|-
|gmp
|6.0.0a
|-
|libelf
|0.8.13
|-
|mpc
|1.0.3
|-
|mpfr
|3.1.2
|}


Serial output will remain enabled pending acceptance of the Fam10h early CBMEM patches currently under review.
== Known Issues ==
It has recently come to my attention that booting from USB mass storage devices is not possible.  Both SeaBIOS and GRUB fail to see any attached flash drives, even though the USB keyboard functions normally.  Also, grub is unable to properly initialize the USB keyboard (very slow typing rate, several seconds per character), but SeaBIOS functions normally.  Additional debugging is needed by an interested party to resolve these issues. [[User:Tpearson|Tpearson]] ([[User talk:Tpearson|talk]])
 
[[Category:Tutorials]]

Latest revision as of 17:01, 11 October 2016

ASUS KFSN4-DRE PCB 1.04G at Raptor Engineering.

General Information

The KFSN4-DRE is a relatively modern AMD K8 / Family 10h motherboard. It is well supported and stable under Coreboot with Family 10h processors, with all CPUs, RAM, and peripherals functioning normally. K8 processors currently require specific RAM configurations to work correctly.

This board is automatically tested by Raptor Engineering's test stand. For more details please visit AutoTest/RaptorEngineering.

Installation Notes

  • coreboot can be flashed internally when migrating from the proprietary BIOS. Flashrom can safely reprogram the ROM under Linux.
  • When migrating from the proprietary BIOS, after flashing coreboot the CMOS memory should be cleared. Failing to clear the CMOS could result in odd hangs during the boot process.

Known Issues

It has recently come to my attention that booting from USB mass storage devices is not possible. Both SeaBIOS and GRUB fail to see any attached flash drives, even though the USB keyboard functions normally. Also, grub is unable to properly initialize the USB keyboard (very slow typing rate, several seconds per character), but SeaBIOS functions normally. Additional debugging is needed by an interested party to resolve these issues. Tpearson (talk)