Re: [coreboot] ASUS KFN4D16 - K8 FAM10

[thomas ward]

Thanks Myles!

Your reply is very helpfull to me (especailly the part about using v2 - I was unsure which of v2 or v3 was appropriate) and very clear. I will follow the "destructions" (probably not till August becasue busy in June and holiday most of July) and once I have blown up the board will post the results to this list.

regards,

Tom.

--- On Wed, 17/6/09, Myles Watson  wrote:
> From: Myles Watson 
> Subject: Re: [coreboot] ASUS KFN4D16 - K8 FAM10
> To: "Thomas Ward" 
> Cc: "[e-mail]" 
> Date: Wednesday, 17 June, 2009, 5:13 PM
>
> On Tue, Jun 16, 2009 at 3:36 AM,
> Thomas Ward 
> wrote:
>
> Hello,
>
> I realise your list is very technical and this is probably
> a daft set of question so please forgive me if it is
> cluttering up your list but I couldn't find a more
> appropriate place to ask,..
>
> ... so here goes.
>
> My questions are about running coreboot on an ASUS KFN4-D16
> with an NVIDIA CK804 chipset and a SST SST49LF080A (BIOS?)
> chip  33-4C-NHE 0631138-B
>
> I have 2 cpus one is a 65nm dual core opteron 2210, the
> second CPU is a quad core 45nm "Shanghai" opteron
> 2376 - this CPU isn't supported by the ASUS BIOS.
>
> My aim is to get the board to boot with the quad core CPU,
> I would be happy if it boots with support for all the RAM
> and at least one of the ethernet ports, I can live without
> PCI, SATA, USB etc.They should all work.
>
> My plan is to use a BIOS saviour and buy a second
> SST49LF080A chip  and then
> flash  coreboot for K8 (?) with flashrom to verify that
>
> coreboot works on this board
> flash  coreboot for fam10 (?) with flashrom
>
> does this sound like a good plan?Yes.
>
> I have a couple of other questions
>
> E. what sort of BIOS chip / bios saviour kit should I use
> with this board?RD1
>
> output from flashrom, superiotool and lspci appended
> below,
>
> many thanks for any help and good luck with your project,
>
> Tom Ward
>
> root@shed:/home/tom/coreboot/flashrom# ./flashrom
>
> flashrom v0.9.0-r555
>
> No coreboot table found.
>
> Found chipset "NVIDIA CK804", enabling flash
> write... OK.
>
> Calibrating delay loop... OK.
>
> Found chip "SST SST49LF080A" (1024 KB) at
> physical address 0xfff00000.Hopefully this
> chip is socketed.
>
> superiotool r3695
>
> Found Winbond W83627THF/THG (id=0x82, rev=0x84) at
> 0x2eThis SuperIO is supported.
>
> 00:00.0 Memory controller: nVidia Corporation CK804 Memory
> Controller (rev a4)
>
> This board is very similar to the
> tyan/s2892.
>
> If I were you, my first step would be to get the BIOS
> savior (or just use the pushpin method)
>
> http://www.coreboot.org/Developer_Manual
>
> Once you can recover from a bad flash,
>
> check out the latest coreboot-v2
> mkdir src/mainboard/asus/kfn4-d16
> svn cp src/mainboard/tyan/s2892/*
> src/mainboard/asus/kfn4-d16/
> mkdir targets/asus/kfn4-d16
>
> svn cp targets/tyan/s2892/Config.lb targets/asus/kfn4-d16/
>
> edit src/mainboard/asus/kfn4-d16/Config.lb
>
> Enable devices that are in your lspci, disable any that
> don't show up.  Don't worry about cards that you
> plug in, they'll be found automatically.
>
> Change the SuperIO from chip superio/winbond/w83627hf to
> superio/winbond/w83627thf and change any settings there that
> you need to.
> Change socket_940 to socket_F
>
> (When you're ready to switch to fam10)
> Change amdk8 to amdfam10 everywhere (may need some other
> small fixups)
>
> edit targets/asus/kfn4-d16/Config.lb
> Change s2892 to kfn4-d16
> make sure ROM_SIZE matches the chip you're using.
>
> cd targets
>
> ./buildtarget asus/kfn4-d16
>
> make a payload (Maybe seabios)
> cp your_payload targets/asus/kfn4-d16/kfn4-d16/payload.elf
>
> make -C asus/kfn4-d16/kfn4-d16
>
> Last step is to send your patches to the list with a
> Signed-off-by: <your-email> line.
>
> Thanks,
> Myles
>
> -----Inline Attachment Follows-----

ASUS KFN4D16 - K8 FAM10

[Myles Watson]

> Your reply is very helpfull to me (especailly the part about using v2 - I
> was unsure which of v2 or v3 was appropriate) and very clear.

Great.
> I will
> follow the "destructions"

:)
> (probably not till August becasue busy in June
> and holiday most of July) and once I have blown up the board will post the
> results to this list.

I'm looking forward to it.

Thanks,
Myles

ASUS KFN4D16 - K8 FAM10

[Thomas Ward]

1.
I can report that flashrom  v0.9.0-r670 works with KFN4-D16
I flashed an ASUS ROM (3.02) and halted the computer and rebooted, computer booted up as normal.

Should I formally inform someone so that the documentation can be updated to reflect the fact that flashwom works with this board?

2.
I am struggling to configure coreboot for this board based on Myles Watson's recommendation of using the tyans2892 as a template.
2.1
in acpi_tables.c resourcemap.c mptable.c dsdt.dsl there are references to AMD8131, this board does not have an AMD8131, should I remove these references?

2.2 in Options.lb
default CONFIG_MAINBOARD_PART_NUMBER="s2892"
default CONFIG_MAINBOARD_VENDOR="Tyan"
default CONFIG_MAINBOARD_PCI_SUBSYSTEM_VENDOR_ID=0x10f1
default CONFIG_MAINBOARD_PCI_SUBSYSTEM_DEVICE_ID=0x2892
Do I need to edit?

2.3
in dsdt.dsl there are references to onboard ATI RAGE, this board has an ES1000
and to an INTELL NIC, this board has broadcom

2.4

in Config.lb
2.4.1 there are references to 8 DIMMS, this board has 16	
should I add 8 more from 58 to 65?
  chip drivers/generic/generic #dimm 1-1-1
    device i2c 57 on end
  end
2.4.2
the SMBUS has ADT7463A  and WINBOND  monitors, do I need to edit this to reflect the KFN4-DE16?, How do I find out what the KFN4-D16 has
2.4.3
Do I just remove the references to AMD8131? Do I replace with anything?
2.4.4
Do I need to add info about the PCI-E to PCI bridge and the ATI ES1000 VGA?
02:00.0 PCI bridge: Intel Corporation 6702PXH PCI Express-to-PCI Bridge A (rev 09)
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 21)
05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 21)
06:05.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)

thanks again for your help

Tom Ward

thomas ward wrote:
> Thanks Myles!
>
> Your reply is very helpfull to me (especailly the part about using v2 - I was unsure which of v2 or v3 was appropriate) and very clear. I will follow the "destructions" (probably not till August becasue busy in June and holiday most of July) and once I have blown up the board will post the results to this list.
>
> regards,
>
> Tom.
>
> --- On Wed, 17/6/09, Myles Watson  wrote:
> > From: Myles Watson 
> > Subject: Re: [coreboot] ASUS KFN4D16 - K8 FAM10
> > To: "Thomas Ward" 
> > Cc: "[e-mail]" 
> > Date: Wednesday, 17 June, 2009, 5:13 PM
> >
> > On Tue, Jun 16, 2009 at 3:36 AM,
> > Thomas Ward 
> > wrote:
> >
> > Hello,
> >
> > I realise your list is very technical and this is probably
> > a daft set of question so please forgive me if it is
> > cluttering up your list but I couldn't find a more
> > appropriate place to ask,..
> >
> > ... so here goes.
> >
> > My questions are about running coreboot on an ASUS KFN4-D16
> > with an NVIDIA CK804 chipset and a SST SST49LF080A (BIOS?)
> > chip  33-4C-NHE 0631138-B
> >
> > I have 2 cpus one is a 65nm dual core opteron 2210, the
> > second CPU is a quad core 45nm "Shanghai" opteron
> > 2376 - this CPU isn't supported by the ASUS BIOS.
> >
> > My aim is to get the board to boot with the quad core CPU,
> > I would be happy if it boots with support for all the RAM
> > and at least one of the ethernet ports, I can live without
> > PCI, SATA, USB etc.They should all work.
> >
> > My plan is to use a BIOS saviour and buy a second
> > SST49LF080A chip  and then
> > flash  coreboot for K8 (?) with flashrom to verify that
> >
> > coreboot works on this board
> > flash  coreboot for fam10 (?) with flashrom
> >
> > does this sound like a good plan?Yes.
> >
> > I have a couple of other questions
> >
> > E. what sort of BIOS chip / bios saviour kit should I use
> > with this board?RD1
> >
> > output from flashrom, superiotool and lspci appended
> > below,
> >
> > many thanks for any help and good luck with your project,
> >
> > Tom Ward
> >
> > root@shed:/home/tom/coreboot/flashrom# ./flashrom
> >
> > flashrom v0.9.0-r555
> >
> > No coreboot table found.
> >
> > Found chipset "NVIDIA CK804", enabling flash
> > write... OK.
> >
> > Calibrating delay loop... OK.
> >
> > Found chip "SST SST49LF080A" (1024 KB) at
> > physical address 0xfff00000.Hopefully this
> > chip is socketed.
> >
> > superiotool r3695
> >
> > Found Winbond W83627THF/THG (id=0x82, rev=0x84) at
> > 0x2eThis SuperIO is supported.
> >
> > 00:00.0 Memory controller: nVidia Corporation CK804 Memory
> > Controller (rev a4)
> >
> > This board is very similar to the
> > tyan/s2892.
> >
> > If I were you, my first step would be to get the BIOS
> > savior (or just use the pushpin method)
> >
> > http://www.coreboot.org/Developer_Manual
> >
> > Once you can recover from a bad flash,
> >
> > check out the latest coreboot-v2
> > mkdir src/mainboard/asus/kfn4-d16
> > svn cp src/mainboard/tyan/s2892/*
> > src/mainboard/asus/kfn4-d16/
> > mkdir targets/asus/kfn4-d16
> >
> > svn cp targets/tyan/s2892/Config.lb targets/asus/kfn4-d16/
> >
> > edit src/mainboard/asus/kfn4-d16/Config.lb
> >
> > Enable devices that are in your lspci, disable any that
> > don't show up.  Don't worry about cards that you
> > plug in, they'll be found automatically.
> >
> > Change the SuperIO from chip superio/winbond/w83627hf to
> > superio/winbond/w83627thf and change any settings there that
> > you need to.
> > Change socket_940 to socket_F
> >
> > (When you're ready to switch to fam10)
> > Change amdk8 to amdfam10 everywhere (may need some other
> > small fixups)
> >
> > edit targets/asus/kfn4-d16/Config.lb
> > Change s2892 to kfn4-d16
> > make sure ROM_SIZE matches the chip you're using.
> >
> > cd targets
> >
> > ./buildtarget asus/kfn4-d16
> >
> > make a payload (Maybe seabios)
> > cp your_payload targets/asus/kfn4-d16/kfn4-d16/payload.elf
> >
> > make -C asus/kfn4-d16/kfn4-d16
> >
> > Last step is to send your patches to the list with a
> > Signed-off-by: <your-email> line.
> >
> > Thanks,
> > Myles
> >
> > -----Inline Attachment Follows-----