Joe,
I noticed this, this morning. (I fixed it locally to test my CN400
patch, and the fix is in the CN400 patch posted this morning - Ididn't
know if it was just me!)
src/pc80/Config.lb needs an extra 'uses CONFIG_USE_INIT' line in it.
This is a latent bug in this file that's been show up from somewhere
else....
Jon
-----Original Message-----
From: coreboot-bounces@coreboot.org
[mailto:coreboot-bounces@coreboot.org] On Behalf Of
coreboot-request@coreboot.org
Sent: 17 June 2009 17:39
To: coreboot@coreboot.org
Subject: coreboot Digest, Vol 52, Issue 124
*** WARNING ***
This message has originated outside your organisation,
either from an external partner or the Global Internet.
Keep this in mind if you answer this message.
Send coreboot mailing list submissions to
coreboot@coreboot.org
To subscribe or unsubscribe via the World Wide Web, visit
http://www.coreboot.org/mailman/listinfo/coreboot
or, via email, send a message with subject or body 'help' to
coreboot-request@coreboot.org
You can reach the person managing the list at
coreboot-owner@coreboot.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of coreboot digest..."
Today's Topics:
1. Re: build service results for r4359 broken? (Joseph Smith)
2. Re: build service results for r4359 broken? (Ward Vandewege)
3. Re: ASUS KFN4D16 - K8 FAM10 (Myles Watson)
4. [v2] r4360 - in trunk/coreboot-v2/src/mainboard:
a-trend/atc-6220 a-trend/atc-6240 abit/be6-ii_v2_0
advantech/pcm-5820 amd/db800 amd/norwich amd/rumba
artecgroup/dbe61 asi/mb_5blgp asi/mb_5blmp asus/mew-am
asus/mew-vm asus/p2b asus/p2b-d asus/p2b-ds asus/p2b-f
asus/p3b-f
axus/tc320 azza/pt-6ibd bcom/winnet100 bcom/winnetp680
biostar/m6tba compaq/deskpro_en_sff_p600 dell/s1850
digitallogic/adl855pc digitallogic/msm800sev eaglelion/5bcm
gigabyte/ga-6bxc iei/juki-511p iei/nova4899r
iei/pcisa-lx-800-r10
intel/jarrell intel/mtarvon intel/truxton intel/xe7501devkit
jetway/j7f24 lippert/frontrunner lippert/roadrunner-lx
lippert/spacerunner-lx msi/ms6119 msi/ms6147 msi/ms6178
nec/powermate2000 olpc/btest olpc/rev_a pcengines/alix1c
rca/rm4100 supermicro/x6dai_g supermicro/x6dhe_g
supermicro/x6dhe_g2 supermicro/x6dhr_ig supermicro/x6dhr_ig2
televideo/tc7020 thomson/ip1000 tyan/s1846 via/epia
via/epia-cn
via/epia-m via/pc2500e via/vt8454c (svn@coreboot.org)
----------------------------------------------------------------------
Message: 1
Date: Wed, 17 Jun 2009 11:57:39 -0400
From: Joseph Smith joe@settoplinux.org
To: coreboot mailinglist coreboot@coreboot.org
Subject: Re: [coreboot] build service results for r4359 broken?
Message-ID: 9cd2430bda7419af8eff8a6cbb862878@imap.1and1.com
Content-Type: text/plain; charset="UTF-8"
On Wed, 17 Jun 2009 17:44:25 +0200, coreboot information
info@coresystems.de wrote:
Dear coreboot readers!
This is the automatic build system of coreboot.
The developer "mjones" checked in revision 4359 to
the coreboot repository. This caused the following
changes:
Hmm, every board is broken, looks like an issue with CONFIG_USE_INIT ???
--
Thanks,
Joseph Smith
Set-Top-Linux
www.settoplinux.org
------------------------------
Message: 2
Date: Wed, 17 Jun 2009 12:04:21 -0400
From: Ward Vandewege
ward@gnu.org
To: Joseph Smith
joe@settoplinux.org
Cc: coreboot mailinglist
coreboot@coreboot.org
Subject: Re: [coreboot] build service results for r4359 broken?
Message-ID:
20090617160421.GA22466@countzero.vandewege.net
Content-Type: text/plain; charset=us-ascii
On Wed, Jun 17, 2009 at 11:57:39AM -0400, Joseph Smith wrote:
>
>
>
> On Wed, 17 Jun 2009 17:44:25 +0200, coreboot information
>
info@coresystems.de wrote:
> > Dear coreboot readers!
> >
> > This is the automatic build system of coreboot.
> >
> > The developer "mjones" checked in revision 4359 to
> > the coreboot repository. This caused the following
> > changes:
> >
> Hmm, every board is broken, looks like an issue with CONFIG_USE_INIT
???
But it was not because of Marc's commit - its r4357 that did it.
Thanks,
Ward.
--
Ward Vandewege
ward@fsf.org
Free Software Foundation - Senior Systems Administrator
------------------------------
Message: 3
Date: Wed, 17 Jun 2009 10:13:16 -0600
From: Myles Watson
mylesgw@gmail.com
To: Thomas Ward
tomwardathome@yahoo.co.uk
Cc: "coreboot@coreboot.org"
coreboot@coreboot.org
Subject: Re: [coreboot] ASUS KFN4D16 - K8 FAM10
Message-ID:
2831fecf0906170913m2ad22008wb02028d3780034c2@mail.gmail.com
Content-Type: text/plain; charset="iso-8859-1"
On Tue, Jun 16, 2009 at 3:36 AM, Thomas Ward
tomwardathome@yahoo.co.ukwrote:
> 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
>
> 1. flash coreboot for K8 (?) with flashrom to verify that coreboot
works
> on this board
> 2. 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 0x2e
This 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
Harrison, Jon (SELEX GALILEO, UK)