coreboot September 2003

coreboot@coreboot.org

68 participants
171 discussions

DoC on Eipa
by Michael Fenner 17 Sep '03

17 Sep '03

Hallo, does anybody have experience with DOC's on an Epia-M board? I read in a previous message ( http://www.mail-archive.com/linuxbios@clustermatic.org/msg03307.html ) that the DOC Millennium 8MB Module MD2802-D08 might work. Can anybody confirm this? They also say I need a ZIF socket, which makes sense, and an DIP-32 256K X8 120NS Atmel Flash Memory. I don't really understand what I would need that for. Can anybody help? Also I read that the EPIA-M still has problems with some DDR-Rams. Does anybody have a list which Rams are supported? thanks, Michael

5 20

funny idea
by Niki Waibel 17 Sep '03

17 Sep '03

hi, i just had a funny idea... what about haveing bios savior + DoC in a mb _and_ connecting the bios savior switch to an address pin... that way it should be possible to have enough room in the bios savior rom for doing everything. then the DoC could be activated... i think that booting should start with the internal bios savior chip (with linuxbios). and then, at some stage (all init of mem and copying of bios savior rom done) the switch is "activated" (by a read of some address or sthg). then a copy of the DoC is done ... what do you think? niki

3 2

solo + SST49LF080A
by Ralf Große Börger 17 Sep '03

17 Sep '03

Hi, I am seeing strange effects, if I am using LinuxBIOS in a SST49LF080A on a solo system. The same LinuxBIOS image(256KB) works flawless with a SST49LF040 or the preinstalled Winbond chip, but it gets stuck somewhere in setup_resource_map with the SST49LF080A. On the other hand, the preinstalled Pheonix BIOS boots from a SST49LF080A without a problem. A quick look into the datasheets of both SST chips revealed a slight difference: The SST49LF080A decodes the bottom 128 KB memory access address (0x000FFFFF to 0x000E0000) only, whereas the SST49LF040 decodes the complete 512KB memory area (0x000FFFFF to 0x0007FFFF). Does this pose any problems for LinuxBIOS? Or has anyone else made experiences with the SST49LF080A? There has been a thread about sporadic problems, but I can reproduce this behaviour with several SST49LF080A and I'm quite sure the chip is flashed correctly. Best regards Ralf

2 1

Help! with Linuxbios + EPIA 5000 + Etherboot
by Hubert Denkmair 17 Sep '03

17 Sep '03

Hi, I finally received a working BIOS Saviour and tried linuxbios the first time last night. I tried to exactly follow the EPIA-Howto but failed because I can't compile etherboot as described there: First of all there's no line "CFLAGS+= -DPCIBIOS" to comment out in the etherboot-5.0.11 "Config" file - I assume it might be a typo in the howto and commented out the line "CFLAGS+= -DPCBIOS", but it won't work. Anyways, I'm not able to compile the etherboot-5.0.[10,11] sources at all. I'm using a fresh upgraded debian "testing" with gcc-3.3.1 Simply doing a --- tar xvjf etherboot-5.0.11.tar.bz2 cd etherboot-5.0.11/src make bin32/via-rhine.elf --- throws tons of warnings and fails to link with messages like --- bin32/via-rhine.o(.text+0x2e8): In function `rhine_probe1': : undefined reference to `currticks' --- As I'm not familiar with C/GCC I have no idea where this may come from (wrong compiler version, wrong libs...?) I tried the etherboot-5.2.1 source package. Opposing to etherboot-5.0 there are no linuxbios options so I suppose they are not needed any more. The etherboot-5.2 package compiles fine (I'm doing a "make bin/via-rhine.elf"). From there on I'm following the EPIA-HOWTO again and the linuxbios build runs smoothly, flashing the romimage also was no problem. When booting, the linuxbios initialization seems to be ok, but after loading etherboot nothing seems to happen any more. The last lines on the serial console are: --- Copying IRQ routing tables to 0xf0000...done. Verifing priq routing tables copy at 0xf0000...succeed Wrote linuxbios table at: 00000500 - 00000698 checksum 345e Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.2 37:init_bytes() - zkernel_start:0xfff00000 zkernel_mask:0x0000ffff Found ELF candiate at offset 0 Loading Etherboot version: 5.2.1 Dropping non PT_LOAD segment New segment addr 0x20000 size 0xf160 offset 0xb0 filesize 0x5bdc (cleaned up) New segment addr 0x20000 size 0xf160 offset 0xb0 filesize 0x5bdc Loading Segment: addr: 0x000000000ff7faa8 memsz: 0x000000000000f160 filesz: 0x0000000000005bdc Clearing Segment: addr: 0x000000000ff85684 memsz: 0x0000000000009584 Jumping to boot code at 0x20000 --- Now, who can help be getting linuxbios/etherboot to work at all, or - better: boot from local IDE? Do I need special config options for etherboot-5.2? I searched the mailinglist but did not find any indication... What's wrong with my etherboot-5.0? Is my debian broken? Thanks for your help, Hubert

3 3

Getting started
by Craig C. Forney 17 Sep '03

17 Sep '03

Hi! I'm a newbie with linuxbios (and linux for that matter). We are in the process of creating a stripped-down (but extremely dense) dual Opteron server. It is basically a pair of Opterons and an 8111 that has a 10/100 NIC, a pair of USB ports, and an IDE interface, along with 4GB of RAM. We'd like to run linuxbios on it. I have an Arima Hdma dual Opteron system I am using for development. I'd like to start by building a linuxbios for the Arima system. I have been able to build and run a 64-bit kernel from the Suse _64 distribution on the Arima system successfully. I have downloaded the latest (as of yesterday) freebios2 tree from sourceforge.net. I went to targets and ran: # buildtarget arima/hdama Then I did the following: # cd arima/hdma/hdma # make It successfully made romcc, but when it tried to run it to make either the failover or normal rom, it gets the following error: reset_test.c:13,111: 0x1e43570 copy Internal compiler error: bad type passed to copy I'm probably missing some steps, or starting in the wrong place. I'd appreciate some advice. I spent some time looking through the archives, but did not find any definitive tutorial for the latest linuxbios creation (although the March 2003 linux-magazine article was useful to gain a perspective). Any help appreciated. I've been reading the mailing list for about a month, and I'm impressed with the progress this group has made. Thanks, Craig ========================================================== Craig C. Forney cforney(a)opus.com Opus Innovations LLC http://www.opus.com ==========================================================

11 24

EPIA-800 and VGA post LinuxBIOS init
by David Hendricks 17 Sep '03

17 Sep '03

I have successfully managed to boot an EPIA-800 board to a usable state using Steve Gehlback's VGA configuration, Etherboot, and a vanilla FreeBIOS tree. VGA comes up reliably every time I boot. However VGA output only appears until Etherboot jumps to my phase 1 beoboot image. What must be done to have VGA output after Etherboot loads my image?

2 1

LinuxBios + EPIA5000 + Win2k Bootloader + HD + VGA
by Sven Lübke 17 Sep '03

17 Sep '03

Hi! I want to install LinuxBIOS on my EPIA5000 in combination with an IDE-Harddisk. The harddisk contains a Win2k bootloader which boots LiLo or Win2k. The VGA port on the EPIA board should be enabled! Is that combination possible/up-to-date at all? Which setup has the fastest boottime? I tried to compile LinuxBIOS with ADLO and Bochs, cause I don't want to use etherboot, but for some reason the computer didn't boot. I read all the FAQs and the "How to" for EPIA mainboards but it's not working anyway! Is ADLO able to boot the Win2k loader? Is someone using the same setup and has a config-file for me? Can someone help me? My goal is to boot Linux as fast as possible and sometimes (if I need it) switch to Win2k. Thank you for your help! Best regards, Sven

2 1

CVS not working, link to daily snapshot broken
by Dave Ashley 16 Sep '03

16 Sep '03

http://www.linuxbios.org/developer/download/index.html cvs [checkout aborted]: recv() from server cvs.freebios.sourceforge.net: EOF cvs [checkout aborted]: recv() from server cvs.freebios.sourceforge.net: Connection reset by peer http://cvs.sourceforge.net/cvstarballs/freebios-cvsroot.tar.gz Object not found! The requested URL was not found on this server. The link on the referring page seems to be wrong or outdated. Please inform the author of that page about the error. If you think this is a server error, please contact the webmaster Error 404

2 1

romcc fixes for AMD64
by Stefan Reinauer 16 Sep '03

16 Sep '03

Hi, with the attached fix romcc is able to compile all of auto.c for the freebios2 amd64 targets. To keep all changes clean and visible, they're encapsulated in ifdefs. Note: This fix alone does not make LinuxBIOS compile on AMD64 completely yet. GCC and ld need the -m32 in some places at least to compile everything. Is there any need in going 64bit for the LinuxBIOS C payload on Opteron? Since the kernel does long mode switching itself this should not be the case, but maybe there are different opinions. Next fail I saw after romcc passed auto.c was the following: /home/stepan/freebios2/src/superio/NSC/pc87360/superio.c:61: warning: `pnp_read_enable' defined but not used /tmp/ccLriZXb.s: Assembler messages: /tmp/ccLriZXb.s:243: Error: Incorrect register `%rdx' used with `l' suffix /tmp/ccLriZXb.s:245: Error: Incorrect register `%rdx' used with `l' suffix make: *** [superio.o] Error 1 Greetings, Stefan -- Architecture Team SuSE Linux AG

3 5

Re: extending "buildrom"
by YhLu 16 Sep '03

16 Sep '03

Optional offset is a good idea. But seem when We build normal or fallback image the offset are fixed at the time. For example: The LsiSCSIFW is 48k. and its final offset in ROM is 0. When building fallback image, I set ROM_SIZE is 512K, and fallback section size if 96K ( 32k+64k) so the offset is 512K-96K.The final offset in ROM should be 512K-96K. When building normal image, I set ROM_SIZE is 512K-48K. and normal section size is 512k-48k-96k, and the offset is 48K. The final offset in ROM should be 48K. So We only need to cat them all together, except We don't want normal you may need the optional offset. Regards YH. -----邮件原件----- 发件人: ron minnich [mailto:rminnich@lanl.gov] 发送时间: 2003年9月16日 7:25 收件人: Stefan Reinauer 抄送: YhLu; LinuxBIOS 主题: Re: extending "buildrom" On Tue, 16 Sep 2003, ron minnich wrote: > On Tue, 16 Sep 2003, Stefan Reinauer wrote: > > > * ron minnich <rminnich(a)lanl.gov> [030915 16:51]: > > > On Mon, 15 Sep 2003, Stefan Reinauer wrote: > > > > > > > buildrom <imagename.rom> > > > > size ROM_SIZE > > > > data ./lsiscsifw 65536 So the one change I'd make is to have an optional offset. data ./lsiscsifs 65536 image normal NORMAL_SIZE 0x20000 etc. This would be so that you could have non-contiguous data areas. ron

1 0

← Newer
1
...
8
9
10
11
12
13
14
...
18
Older →

Jump to page:

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 2003