coreboot September 2004

coreboot@coreboot.org

41 participants
123 discussions

RE: Intel E7520 support
by YhLu 26 Sep '04

26 Sep '04

Stefan/Ron, How about add acpi that only is related to pci to the LinuxBIOS? Otherwise how make the PCI-E device get interrupt assigned? Regards YH -----Original Message----- From: YhLu Sent: Thursday, September 23, 2004 6:54 PM To: 'ebiederman(a)lnxi.com' Subject: RE: Intel E7520 support Eric, How to set let the PCI-E device know the interrupt assign it? Under Normal BIOS, the device can get interrupt via ACPI, and there is no entry in mptable for it. So when using LinuxBIOS, How to do ? Regards YH

4 3

Re: amdk8_scan_chains() questions
by maillists＠petrolhead.com 26 Sep '04

26 Sep '04

> Stefan Reinauer <stepan(a)openbios.org> writes: > > > * Liu Tao <liutao(a)safe-mail.net> [040922 04:57]: > > > I googled some results of amdk8 linuxbios, and seems after > > > dev_enumerate() AMD8111 is not at bus0. So does it mean > when we are > > > running from the BIOS ROM the IO HUB must be at bus0, and when we > > > are running in RAM the bus number doesn't matter? > > Yes. So long as linux can find it. We just put it at > bus 0 as convenience so we can find it easily. > > Putting the hypertransport chains on their own bus is clearer > reflection of reality than putting extra devices on bus 0. It's even simpler than that. Before the HT and IO routing is initialized the BIOS ROM access happens because of an HT feature called the compatibility bit. This bit is set for all accesses that are not covered by any routing table io/memory/mem-mapped-io etc. Requests with the compatibility bit set are routed down the link with the IO hub on it and generally, 8131 can route to the PCI bus, these end up in the southbridge/iohub which in the case of ROM BIOS address routes to the ROM. Once the HT and routing is initialized BIOS ROM addresses would be routed to by the routing tables to the BIOS rom, this may be on Bus 0 or Bus 1 or any other number, as long as the routing tables are appropriately setup. Chris

1 0

Epia M freebios2 still broken?
by Trellix78＠aol.com 24 Sep '04

24 Sep '04

I finally made the jump and compiled a freebios2 image for the Epia M but it's not booting at all. I used the default Config.lb, except that I changed the serial speed to 115200 and the payload to etherboot. Now, I get nothing on the serial port and the system locks up hard. Booting with the stock BIOS doesn't even bring it to life unless I clear CMOS, remove the power and let it sit for a little bit. Anybody know what I can try besides banging my head against the wall? Thanks. David

2 1

where is it?
by Bryan E. Chafy 24 Sep '04

24 Sep '04

The linuxbios website says to get the source tree from: cvs -d:pserver:anonymous@cvs.freebios.sourceforge.net:/cvsroot/freebios login But it always times out (tried from varios locations). When I go to the "CVS Repository" link, it says to get it from: cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/freebios login ... That worked, but what I get appears to be a very old version. There's no freebios2 directory and nothing updated from this year. On this page I see a freebios2 directory: http://cvs.sourceforge.net/viewcvs.py/freebios/#dirlist What is the correct way to get the latest source tree?

3 3

RE: freebios2 compilation error (romcc)
by YhLu 23 Sep '04

23 Sep '04

Change to -O -----Original Message----- From: Jeff Stevens [mailto:jsteve17@yahoo.com] Sent: Thursday, September 23, 2004 11:27 AM To: linuxbios(a)clustermatic.org Subject: Re: freebios2 compilation error (romcc) I also found if I remove the -O2 option from romcc it compiles fine, but then auto.inc is way to big. Thanks, Jeff --- Jeff Stevens <jsteve17(a)yahoo.com> wrote: > I have downloaded the latest version of LinuxBIOS > for > AMD64 (freebios2), and am having problems compiling > it. It is erroring out when it runs romcc. Here is > a > screen dump of the error: > > --> > > ./romcc -mcpu=k8 -O2 ./auto.E > auto.inc > auto.c:118.49: coherent_ht.c:291.41: > coherent_ht.c:410.23: coherent_ht.c:645.27: > auto.c:221.47: > Load address out of bounds > make[1]: *** [auto.inc] Error 1 > > <-- > > I tried commenting out those lines, and if I just > comment out line 645 of coherent_ht.c (result = > setup_smp();) it compiles fine. What do I need to > do > to get this to compile correctly. > > Thanks, > Jeff Stevens > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > _______________________________________________ > Linuxbios mailing list > Linuxbios(a)clustermatic.org > http://www.clustermatic.org/mailman/listinfo/linuxbios > _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

freebios2 compilation error (romcc)
by Jeff Stevens 23 Sep '04

23 Sep '04

I have downloaded the latest version of LinuxBIOS for AMD64 (freebios2), and am having problems compiling it. It is erroring out when it runs romcc. Here is a screen dump of the error: --> ./romcc -mcpu=k8 -O2 ./auto.E > auto.inc auto.c:118.49: coherent_ht.c:291.41: coherent_ht.c:410.23: coherent_ht.c:645.27: auto.c:221.47: Load address out of bounds make[1]: *** [auto.inc] Error 1 <-- I tried commenting out those lines, and if I just comment out line 645 of coherent_ht.c (result = setup_smp();) it compiles fine. What do I need to do to get this to compile correctly. Thanks, Jeff Stevens __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 1

i845GV ddr init
by zhu shi song 22 Sep '04

22 Sep '04

(1) The bios from original MB have to handle registers 40~4F, but I check them in i845GV datasheet, they are all intel reserved. Where can I find information about such intel reserved registers? (2) what earlymtrr doing for? Is it related to ddr sdram init? tks zhu __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail

3 2

PXE support
by Sagiv Yefet 22 Sep '04

22 Sep '04

Does anyone know if linuxbios support in PXE ? Sagiv

3 2

FW: Boot problem
by Sagiv Yefet 22 Sep '04

22 Sep '04

I used : mkelfImage-2.5 The command: ./objdir/sbin/mkelfImage -t bzImage-i386 --kernel=/home/sagivy/vmlinuz \ --command-line="console=ttyS0,115200 root=/dev/hda3" \ --initrd=/home/sagivy/initrd --output=/home/sagivy/vmlinuz.elf I had problem in building mkelfImage: linux-i386/head.S: Assembler messages: linux-i386/head.S:458: Error: junk at end of line, first unrecognized character is `U' So in file convert.h I change from: #define CONVERT_MAGIC 0XA5A5A5A5UL To: #define CONVERT_MAGIC 0XA5A5A5A5 and then it was built. Sagiv -----Original Message----- From: David Hendricks [mailto:cro_marmot@comcast.net] Sent: Tuesday, September 21, 2004 6:16 PM To: linuxbios(a)clustermatic.org Subject: Re: Boot problem As I recall, that's a message Etherboot tends to spew when there's something seriously wrong with the elf image. How did you create the elf? Which version of mkelfImage (If that's what you used)? On Tue, 21 Sep 2004 10:21:23 +0200 "Sagiv Yefet" <sagivy(a)3vium.com> wrote: > I prepared a kernel elf file. > The station is up and it loads the elf file. > Then nothing happens. > Just print something: > Firmware: bios is Linuxbios > > What can be the problem? > > Sagiv > > _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

2 1

amdk8_scan_chains() questions
by Liu Tao 22 Sep '04

22 Sep '04

Hello, In AMD's <<BIOS and Kernel developer's Guide>> 3.3.16 LDTi Bus Number Registers section it says that if the link contains the HT IO hub the secondary bus number must be programmed to 0. But amdk8_scan_chains() is called with max=0, so it won't write the secondary register of any link to 0? Or some other code handles this case? Regards, Liu Tao

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot September 2004