coreboot May 2003

coreboot@coreboot.org

70 participants
143 discussions

ASUS TX97LE mainboard seems support too.
by bendany 16 May '03

16 May '03

ASUS TX97LE , the northbridge is 82439TX, southbridge is 82371AB, and I try it with the linuxbios build by mainboard digitallogic/smartcore-p5, test it. and succeeded loading the etherboot payload. need more test.

5 9

Items that should be in the FAQ or README
by roger 16 May '03

16 May '03

recommended/required hardware should be listed in the FAQ or README (or did I pass-over it?) 1) Diskonchip model(s) number for ordering (Diskonchip Millenium 8MB MD2810-D08? --> www.m-sys.com) 2) Zif socket model/ordering numbers (so far, i'm looking at a 32-6554-11 32-pin zif dip .6 spacing (gold over nickel plating) <-- is this a good one? pulled from linuxbios mail list archives) Roger http://www.eskimo.com/~roger/index.html

1 0

Tyan Tiger 1832DL Motherboard (SMP P3 -- 440BX)
by roger 16 May '03

16 May '03

Tyan Tiger 1832DL Motherboard (SMP P3 -- 440BX) -- Chip Info -- (looks like a 2MB eeprom?) Main bios chip markings: Winbond W29C020-90 92900292073701V Other Sticker #1: 8x32 116A (or 118A) Other Sticker #2: AMIBIOS 686 1985-95 American Megatrends B254065 -- Roger http://www.eskimo.com/~roger/index.html

1 0

debugger
by Frank 15 May '03

15 May '03

Can anyone recommend a debugger for bringing up LinuxBios on an x86 system... __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com

4 11

etherboot
by Serafino Sorrenti 15 May '03

15 May '03

Hello, now i download etherboot 5.1.8, i need more information to use this! tnx Serafino

4 9

Re:debugger
by jarcher 15 May '03

15 May '03

That may work. Longer term I'm more worried about debugging payloads. As they will probably change more often than the prebios stuff. Jordan At 01:55 PM 5/15/2003 -0400, steven james wrote: >On Thu, 15 May 2003, jarcher wrote: > > > PS: Has anyone done a USB interface low level debugger? Early BIOS or at > > least just prior to payload decompress. > >I've looked into it, but it's a bit complex to have up at that point (at >least with the regular UHCI and OHCI). At the least, it will require RAM >and a portion of PCI to be up and running. At that point, might as well >just put it in the C code after PCI init. > >G'day, >sjames > > >-- >-------------------------steven james, director of research, linux labs >... ........ ..... .... 230 peachtree st nw ste 2701 >the original linux labs atlanta.ga.us 30303 > -since 1995 http://www.linuxlabs.com > office 404.577.7747 fax 404.577.7743 >-----------------------------------------------------------------------

1 0

Intel L440GX+
by Jonathan B. Horen 15 May '03

15 May '03

Shalom! While reading the LinuxBIOS website FAQ, I looked for instructions for building the romimage for the Intel L440GX+ motherboard -- they're missing; I also tried the link for Intel's "System Update Package" -- it's a dead link. So, can anyone send me build instructions for my motherboard and a pointer to the SUP? TIA! (33-node Beowulf cluster, wanting to move to LinuxBIOS/BeoBOOT/BProc) -- JONATHAN B. HOREN UNIX SYSTEMS ADMINISTRATOR E: horen(a)mail.iucc.ac.il Inter-University Computation Center T: +972-(0)3-640-5203 Tel-Aviv University F: +972-(0)3-640-9118 Ramat-Aviv 69978 Israel

2 1

EPIA VGA patch
by SONE Takeshi 15 May '03

15 May '03

Hello, I started with a fresh checkout of CVS tree (since my current working tree is a mess) and made a minimum modification to boot ADLO with VGA BIOS to enable video on a EPIA. With attached patches, my EPIA 5000 boots into GRUB (then Linux) with VGA console. lb-epia.patch This applies to LinuxBIOS itself. Enables shadow RAM, adds vgainit.inc (it is harmless unless HAVE_FRAMEBUFFER is enabled), and a minimum fix to raminit.inc. Ron, please apply this one. adlo-epia.patch This is for ADLO. Since it includes changes specific to EPIA, it should not (entirely) go into CVS. Note that this includes serial debug patch by hcyun, and EPIA doesn't work without it. Perhaps a timing problem? pirq-EPIA.bin This should be put at util/ADLO/pirq. It was taken from LinuxBIOS, not Award BIOS (I think it makes sense). Of cource, VGA BIOS is also required and it must be taken from your box. As I said this is minimum modification, it does not boot very fast, and it may fail to detect IDE at cold boot. For these issues, I have already posted fixes to the list. RAM is fixed at 64MB, as current CVS is. If you change this, you have to hack raminit.inc, as well as CMOS value in the ADLO/loader.s. I'm working on automatic detection of RAM. Have fun. -- Takeshi

4 6

RE: TUSL2-C almost work.....
by Yap Ee Huey 15 May '03

15 May '03

Hi, I thought zkernel_start could be the reason, but not : --------------------------------------------------------------------------- Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.2 203:init_bytes() - zkernel_start:0xfffc0000 zkernel_mask:0x0000007f Searching for 16 byte tags 64:rom_read_bytes() - overflowed source buffer. max_block = 3 init_bytes found 0 tags Found ELF candiate at offset 0 Loading Etherboot version: 5.1.8 Dropping non PT_LOAD segment New segment addr 0x20000 size 0x12e0f offset 0xb0 filesize 0x3f5d (cleaned up) New segment addr 0x20000 size 0x12e0f offset 0xb0 filesize 0x3f5d Loading Segment: addr: 0x000000000ff7ec68 memsz: 0x0000000000012e0f filesz: 0x0000000000003f5d Clearing Segment: addr: 0x000000000ff82bc5 memsz: 0x000000000000eeb2 Jumping to boot code at 0x20000 (Restarted) LinuxBIOS-1.0.0 Tue May 13 11:51:30 EDT 2003 starting... Ram1 Ram2 ................. --------------------------------------------------------------------------- Still looping............ My kernel was built by : mkelfImage --command-line="root=/dev/hda5 console=ttyS0,19200" --kernel vmlinux -o vmlinux..elf But the ELF image cannot be tagged. (invalid linux kernel) Also, the tagged bzImage cannot be made ELF. (Not an linux kernel at line 73) Could it be a problem ? I should have a tagged ELF according to the Documentation. Thanks a lot. regards, eehuey >From: hcyun(a)etri.re.kr >To: yapeehuey(a)hotmail.com, rminnich(a)lanl.gov >CC: linuxbios(a)clustermatic.org >Subject: RE: TUSL2-C almost work..... >Date: Thu, 15 May 2003 15:28:14 +0900 > > > > Welcome to elfboot, the open sourced starter. > > January 2002, Eric Biederman. > > Version 1.2 > > 203:init_bytes() - zkernel_start:0xfff00000 > > zkernel_mask:0x0000ffff > > Searching for 16 byte tags > > 64:rom_read_bytes() - overflowed source buffer. max_block = 15 > > init_bytes found 0 tags > > Found ELF candiate at offset 0 > > Loading Etherboot version: 5.1.8 > > Dropping non PT_LOAD segment > > New segment addr 0x20000 size 0xeee0 offset 0xb0 filesize 0x617c > > (cleaned up) New segment addr 0x20000 size 0xeee0 offset 0xb0 > > filesize > > 0x617c > > Loading Segment: addr: 0x000000000ff7ece8 memsz: > > 0x000000000000eee0 filesz: > > 0x000000000000617c > > Clearing Segment: addr: 0x000000000ff84e64 memsz: 0x0000000000008d64 > > Jumping to boot code at 0x20000 > > -------------------------------------------------------------- > > ---------------------------------------------- > > > > Then it restarts. > >It seems like you should specify ZKERNEL_START correctly. If you have 256KB >flash part, ZKERNEL_START should be 0xfffc0000. > >Heechul. > _________________________________________________________________ Download the latest MSN Messenger http://messenger.msn.com.my

2 1

RE: TUSL2-C almost work.....
by hcyun＠etri.re.kr 15 May '03

15 May '03

> Welcome to elfboot, the open sourced starter. > January 2002, Eric Biederman. > Version 1.2 > 203:init_bytes() - zkernel_start:0xfff00000 > zkernel_mask:0x0000ffff > Searching for 16 byte tags > 64:rom_read_bytes() - overflowed source buffer. max_block = 15 > init_bytes found 0 tags > Found ELF candiate at offset 0 > Loading Etherboot version: 5.1.8 > Dropping non PT_LOAD segment > New segment addr 0x20000 size 0xeee0 offset 0xb0 filesize 0x617c > (cleaned up) New segment addr 0x20000 size 0xeee0 offset 0xb0 > filesize > 0x617c > Loading Segment: addr: 0x000000000ff7ece8 memsz: > 0x000000000000eee0 filesz: > 0x000000000000617c > Clearing Segment: addr: 0x000000000ff84e64 memsz: 0x0000000000008d64 > Jumping to boot code at 0x20000 > -------------------------------------------------------------- > ---------------------------------------------- > > Then it restarts. It seems like you should specify ZKERNEL_START correctly. If you have 256KB flash part, ZKERNEL_START should be 0xfffc0000. Heechul.

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
15
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 May 2003