coreboot September 2003

coreboot@coreboot.org

68 participants
171 discussions

Re: Opteron ECC Syndrome Issues
by ebiederman＠lnxi.com 19 Sep '03

19 Sep '03

Stefan Reinauer <stepan(a)suse.de> writes: > Eric, > > with the latest CVS I am seeing memory errors on all addresses of the > second dimm module in our solo systems. This does not happen on the > HDAMA. Memory size is correctly detected though. Any good starting point > for debugging this? The first dimm module works perfectly fine. Is this ECC SDRAM? If so the current code in the public CVS tree is incorrect. To get the check bits correct the memory needs to be explicitly written to. There are also a couple of B3 stepping errata that can cause bugs like that. And I believe there is an errata that says something about the first dimm slot needing to be populated for the Athlon64. So I would start by ensuring the know errata are fixed. And testing to see what the problems follows if you swap the DIMMS. I need to push the bug fixes from my internal tree back to the public tree. This is a please bug me until I get it done request. I will see what I can do later today. Eric

1 0

Announcing FILO
by SONE Takeshi 19 Sep '03

19 Sep '03

Hi, I wrote a bootloader, available here: http://te.to/~ts1/filo/ and here the README: This is FILO, a bootloader which loads boot images from local filesystem, without help from legacy BIOS services. Expected usage is to be burned into the BIOS ROM together with LinuxBIOS. FEATURES - Console on VGA + keyboard, serial port, or both - Line editing with ^H, ^W and ^U keys to type arbitrary filename to boot - Improved IDE driver derived from Etherboot 5.1 - Support for filesystems: ext2, fat, jfs, minix, reiserfs, and xfs - Full support for the ELF Boot Proposal (where is it btw, Eric?) - Auxiliary tool to compute checksum of ELF boot images - Full 32-bit code, no BIOS calls REQUIREMENT Only i386 PC architecture is currently supported. Recent version of GNU toolchain is required to build. I have tested with Debian/woody (gcc 2.95.4, binutils 2.12.90.0.1, make 3.79.1) and Debian/sid (gcc 3.3.2, binutils 2.14.90.0.5, make 3.80). INSTALL First invokation of make creates the default Config file. $ make Edit this file as you like. It's fairly straightforward (I hope). $ vi Config Then running make again will build filo.elf, the ELF boot image of FILO. $ make Use filo.elf as your payload of LinuxBIOS, or a boot image for Etherboot. USING At "boot:" prompt, type the name of your boot image in the form: devicename:filename (eg. hda1:/boot/kernel.elf). FILO supports only IDE hard disk (or compatible) for now. The devicename for IDE disk is same as in Linux (eg. hda1 means the first partition of master device on primary controller). FILO can boot any bootable ELF images, which include Linux converted by mkelfImage, Etherboot .elf and .zelf, Memtest86, FILO itself, etc. If AUTOBOOT_FILE is set in Config, FILO tries to boot this file first, and falls back to boot: prompt if it fails. If AUTOBOOT_DELAY is also set, FILO waits specified time in seconds for a key hit before booting AUTOBOOT_FILE. Otherwise it tries to boot AUTOBOOT_FILE immediately unless a key stroke is waiting. BUG REPORTING If you have trouble, set DEBUG_ALL in Config and send its console output to me at <ts1(a)tsn.or.jp>. ACKNOWLEDGEMENT I have taken pieces of code and learned concepts from various standalone programs including GNU GRUB, Etherboot, polled IDE patch by Adam Agnew, Memtest86, LinuxBIOS, and Linux. I must say thanks to all the developers of these wonderful software, especially to Eric Biederman for his great development work in this area. LICENSE Copyright (C) 2003 by SONE Takeshi <ts1(a)tsn.or.jp> and others. This program is licensed under the terms of GNU General Public License. See the COPYING file for details. -- Takeshi

4 4

EPIA Up
by Nathanael Noblet 18 Sep '03

18 Sep '03

Hello, I just wanted to say thanks to everyone that has worked on linuxBIOS. my EPIA board is fully functioning... um no wait, without VGABIOS.. but thats the next step. Its been keeping me at the console for a little too long, but I had a board that I tried porting over and realize the amount of work to get these things working like this. Either way it works and I'm liking it. the Filo bootloader is great, simplifies the load process significantly. I stayed up WAY too late playing with this thing. It felt almost like Christmas... So anyway thanks. -- Nathanael Noblet Gnat Solutions 4604 Monterey Ave NW Calgary, AB T3B 5K4 T/F 403.288.5360 C 403.809.5368 http://www.gnat.ca/

1 0

Re: Any story to boot from Hard Disk
by YhLu 18 Sep '03

18 Sep '03

It's interesting, so it support to file system, while Etherboot only scan first 32 sectors to find the elf. Eric, When using Etherboot 5.2 with LinuxBIOS, does it still support boot from floppy disk? My boss said that if I can flash BIOS only with Floppy under LinuxBIOS, then We could ship some MBs with LinuxBIOS. YH. -----邮件原件----- 发件人: SONE Takeshi [mailto:ts1@cma.co.jp] 发送时间: 2003年9月18日 6:59 收件人: gimyung han 抄送: Linuxbios(a)clustermatic.org 主题: Re: Any story to boot from Hard Disk On Thu, Sep 18, 2003 at 11:19:57AM +0000, gimyung han wrote: > Is anyone tried to boot LinuxBIOS from Hard Disk not using etherboot? > > I heard that etherboot can also boot ide devices........... > > But I don't know how to do it......... > > Thanks for any help Check out this: http://te.to/~ts1/filo/ _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

Any story to boot from Hard Disk
by gimyung han 18 Sep '03

18 Sep '03

Is anyone tried to boot LinuxBIOS from Hard Disk not using etherboot? I heard that etherboot can also boot ide devices........... But I don't know how to do it......... Thanks for any help _________________________________________________________________ 증권 정보 가장 빠르고 편하게 보실 수 있습니다. MSN 증권/투자 http://www.msn.co.kr/stock/

3 2

EPIA Information...
by Nathanael Noblet 18 Sep '03

18 Sep '03

Hello I have received shipment of my epia flash. Although my flash came with an SST chip. www.badflash.com sent me a Windbond chip. I was a little worried, but after using flash_rom to extract the original bios. I proceeded to flash this new chip. It all worked. I rebooted and everything is as it should be. It is unfortunate that I had to pay $10 to find this out, since I have 10 of those chips here for another project. The chip sent is W29C020CP90B. So as to let others know, you can use those in replacement of the original BIOS chip on the EPIA-800. I would suspect that the EPIA-500 and such would also work, but well can't guarantee it. Now on to flashing linuxBIOS to these chips... How exciting... I wonder though if it is prudent to do this at 1am...;) oh well. -- Nathanael Noblet Gnat Solutions 4604 Monterey Ave NW Calgary, AB T3B 5K4 T/F 403.288.5360 C 403.809.5368 http://www.gnat.ca/

2 1

[announce] OpenBIOS Forth Kernel V1.0 released
by Stefan Reinauer 18 Sep '03

18 Sep '03

Dear LinuxBIOS community, After some months of development I am happy to announce the new OpenBIOS forth kernel "BeginAgain". It is available from the OpenBIOS CVS in the directory "kernel/" or at http://www.openbios.org/bin/kernel-1.0.tar.bz2 Features -------- - indirect-threaded forth engine - openfirmware user interface - small and portable - easily enhancable Platform Notes -------------- Currently targets for X86 PCs and AMD64 exist. The OpenBIOS forth kernel was developed using gcc on Linux systems. Minor changes might be necessary in non-linux/gcc build environments. Design Goals ------------ The design goals of "BeginAgain" were: 1) Portability 2) Maintainability 3) Small Size ---------------------------------------------------------------------- 1) Portability BeginAgain, with minimal changes, will work on new systems. There is support for X86 and AMD64 at the moment. Implementing support for new systems only requires adaptions to the start code and system abstraction. The current code has been developed using gcc 3.x, but no explicit GCCisms are used. Since gcc is the most widely spread compiler, it should be a good base for easily porting OpenBIOS to new platforms. 2) Maintainability The code is split into several parts: _________________________________________ | | | Forth dictionary | |_________________________________________| ^ | forth code ________|_________________________|_________ | | | v native code _____________ ___________________ | | | | | Scheduler | ----> | primitive words | |_____________| |___________________| ^ ^ | | | | _____________ ____________________ | | | | -->| Startup | | system abstraction | |_____________| |____________________| Platform dependent part ----------------------- a) After taking control the "scheduler", in forth context called "inner interpreter, reads the forth dictionary, a list of nested word definitions that are built using primitive words. b) These primitive words are written in C, so they take advantage of the compiler's ability to optimize code. They represent the minimum set of forth words that are needed to define all language constructs, including the Open Firmware system. c) The startup code is probably the most platform sensitive code. It's task is simple - get the scheduler up and running and provide a dictionary to execute. OpenBIOS provides multiple boot targets per platform. For example, on x86 it is possible to run the kernel either from Grub or LinuxBIOS. An additional target (available on all platforms) allows running the code from a Unix shell. d) The system abstraction part ought to be kept as small as possible. The primary words provide an interface for non-memory-mapped IO, and there's a small builtin console due to the fact that OpenBIOS has no device tree and/or drivers at the moment. Once these platform dependent parts are in place, they can be used to create an indirect-threaded dictionary file. This dictionary file contains a platform abstracted version of forth code that currently depends on the endianness and pointer (cell) size of the target platform. To keep the forth dictionary and the native code strictly seperate the unix hosted version of the kernel has a small builtin interpreter able to bootstrap all of the base system including a forth written interpreter, which represents part of the openfirmware user interface. In a second stage the advanced forth written interpreter is used to extend the bootstrap dictionary with additional features. As an example, ANS forth wordlist support is added, which will be used in the device tree code. Currently the OpenBIOS dictionary contains a nearly complete implementation of the Open Firmware user interface. It passes the Hayes ANS Forth test suite that is run when OpenBIOS is built, writing it's output to the file forth.html. Since the machine is abstracted as early and completly as possible, porting OpenBIOS to a new platform requires only minor efforts. 3) Small size The less code that needs to be adopted when porting OpenBIOS to a new platform, the quicker new ports can happen. Therefore the OpenBIOS kernel is really small. Here is a sample: size in | x86 | amd64 bytes | gcc 3.3 | gcc 3.3.1 -----------------+---------+---------------- multiboot kernel | 6724 | 15464 -----------------+---------+---------------- LinuxBIOS kernel | 7016 | 15896 -----------------+---------+---------------- LinuxBIOS kernel | | inc. dictionary | 27048 | 52920 -------------------------------------------- Installation and usage ---------------------- Run "make" to compile all binaries and dictionaries required to run the OpenBIOS kernel $ make Per default all binaries will be placed in the directory obj-{platform}. Then you can execute the kernel from a shell, by giving the command $ make run To boot LinuxBIOS from GRUB, copy openbios.multiboot and openfirmware.dict to /boot, then add a new entry to your menu.lst config file which looks like this: -------------------- 8< -------------------- title openbios kernel (hd0,2)/boot/openbios.multiboot module (hd0,2)/boot/openfirmware.dict -------------------- 8< -------------------- (hd0,2) is the equivalent to the Linux partition /dev/hda3 OpenBIOS can be used as a payload to LinuxBIOS (www.linuxbios.org) or booted in EtherBoot (www.etherboot.org). The simplest way is to use the kernel that includes the full dictionary: openbios.full Bug reports ----------- Any trouble, bugs etc. should be reported to the openbios mailinglist <openbios(a)lists.openbios.org> Further Development ------------------- BeginAgain is pretty much complete now. Expect only bugfixes and optimizations in the future. Interpretation mode versions of most loop constructs should be included although they are not really needed to get more development going. The next steps in writing an Open Firmware implementation is to complete the Device and Client Interfaces. These two parts are needed to set up a device tree, initialize hardware, and boot the operating system. Once there is a device tree and some basic device interface functions it will be possible to run fcode drivers for device initialization in OpenBIOS, using the FCode evaluator that resides in the OpenBIOS CVS directory forth/evaluator/. Regards, Stefan

3 6

damaged DoC MD2808-D08?
by Niki Waibel 18 Sep '03

18 Sep '03

my DoC MD2808-D08 responds fine to the control registers (chipid and ecc toggle bit are ok i.e.). but if it comes to the stage of sending nand commands and reading memory it seems to do nothing. if mem is read from the same IO reg (0x800) then i always get the same value (0x55). also if the nand ID command is sent, 0x800 responses with 0x55. 0x55 is the beginning of 0x55 0xaa 0x10 0xeb which is the beginning of the IPL code (rom extension)... in addition if i read a page. and then read it again. i get some different bytes: === --- xxx.xxd 2003-09-17 12:01:44.615883064 +0200 +++ xxx2.xxd 2003-09-17 12:01:44.629880936 +0200 @@ -1,67 +1,67 @@ 0000000: 55aa 10eb 3c00 0028 4329 4d2d 5379 7374 U...<..(C)M-Syst 0000010: 656d 7331 3939 3800 0000 2100 0004 001c ems1998...!..... 0000020: 5524 506e 5001 0200 0000 1e6d 1a01 1000 U$PnP......m.... -0000030: 0000 0000 8001 9400 0000 0000 8181 8181 ................ +0000030: 0000 0000 8001 9400 0000 0000 8181 98e6 ................ 0000040: 009c 5053 5152 5657 551e 06ba c01f 33c0 ..PSQRVWU.....3. -0000050: 8ec0 33ff 83c2 408e da81 fa00 8181 8181 ..3...@......... +0000050: 8ec0 33ff 83c2 408e da81 fa00 439a 8181 ..3...@.....C... 0000060: f6b9 0002 fcad 0bc0 75e8 e2f9 83ff 0075 ........u......u -0000070: 021e 0747 83ff 3072 8181 8181 8181 98e6 ...G..0r........ +0000070: 021e 0747 83ff 3072 8181 98e6 439a 8181 ...G..0r....C... 0000080: 588e c20e 1f8b ec83 ec04 8cc0 8c46 fec7 X............F.. 0000090: 46fc ab00 0ee8 1300 8b46 fe8e c033 ffb9 F........F...3.. 00000a0: 0060 33c0 fcf3 ab8b e5eb 7455 8bec 8b46 .`3.......tU...F -00000b0: 048e d8bb 0000 c687 439a 0081 8181 8198 ........C....... +00000b0: 048e d8bb 0000 c687 0381 0081 8181 8181 ................ 00000c0: c687 0210 85be 0008 b1ff e85d 00fc 32e4 ...........]..2. -00000d0: b100 e855 002e 8b0e e643 9a81 8181 8181 ...U.....C...... +00000d0: b100 e855 002e 8b0e 8181 8181 8181 8181 ...U............ 00000e0: 7523 c687 0410 0d2e 8b16 1c00 8181 8181 u#.............. -00000f0: 8814 8834 8181 8181 8181 8181 8181 8198 ...4............ +00000f0: 8898 8834 e643 9a81 8181 8198 e643 9a81 ...4.C.......C.. 0000100: 1009 e836 0084 870d 10ac 02e0 aa4e e2cc ...6.........N.. 0000110: 2e3a 2620 0075 065d 0633 c050 cb5d cb07 .:& .u.].3.P.].. 0000120: 1f5d 5f5e 5a59 5b58 9dcb c687 0410 0b88 .]_^ZY[X........ -0000130: 0cc6 871e 1000 c687 0410 09f6 e643 9a81 .............C.. +0000130: 0cc6 871e 1000 c687 0410 09f6 8181 8181 ................ 0000140: f687 2010 80f6 8720 1080 f687 2010 80f6 .. .... .... ... -0000150: 8704 1080 74f9 f687 2010 80f6 8181 8198 ....t... ....... -0000160: c31c 0000 0000 0000 0000 0000 e600 439a ..............C. -0000170: 0000 0000 0000 8181 8181 8181 8181 8181 ................ +0000150: 8704 1080 74f9 f687 2010 80f6 8181 8181 ....t... ....... +0000160: c31c 0000 0000 0000 0000 0000 0000 8181 ................ +0000170: 0000 0000 8181 0000 8181 8181 8181 8198 ................ 0000180: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0000190: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00001a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ -00001b0: 0000 0000 0000 0000 8181 8181 8181 8181 ................ +00001b0: 0000 0000 0000 0000 e643 9a81 8181 8198 .........C...... 00001c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ -00001d0: 0000 0000 0000 0000 8181 98e6 439a 8181 ............C... -00001e0: 0000 0000 0000 0000 0000 0000 8181 98e6 ................ -00001f0: 0000 0000 439a 8181 8181 8181 8181 8181 ....C........... +00001d0: 0000 0000 0000 0000 e643 9a81 8181 8181 .........C...... +00001e0: 0000 0000 0000 0000 0000 0000 8181 8181 ................ +00001f0: 8100 0000 8181 8181 8181 8181 8181 9898 ................ 0000200: 55aa 10eb 3c00 0028 4329 4d2d 5379 7374 U...<..(C)M-Syst 0000210: 656d 7331 3939 3800 0000 2100 0004 001c ems1998...!..... 0000220: 5524 506e 5001 0200 0000 1e6d 1a01 1000 U$PnP......m.... -0000230: 0000 0000 8001 9400 0000 0000 8181 8181 ................ +0000230: 0000 0000 8001 9400 0000 0000 439a 8181 ............C... 0000240: 009c 5053 5152 5657 551e 06ba c01f 33c0 ..PSQRVWU.....3. -0000250: 8ec0 33ff 83c2 408e da81 fa00 8181 8181 ..3...@......... -0000260: f6b9 0002 fcad 0bc0 75e8 e2f9 83ff 8175 ........u......u -0000270: 021e 0747 83ff 3072 8198 e643 9a81 8181 ...G..0r...C.... +0000250: 8ec0 33ff 83c2 408e da81 fa00 8181 98e6 ..3...@......... +0000260: f6b9 0002 fcad 0bc0 75e8 e2f9 83ff 0043 ........u......C +0000270: 021e 0747 83ff 3072 9a81 8181 8181 8181 ...G..0r........ 0000280: 588e c20e 1f8b ec83 ec04 8cc0 8c46 fec7 X............F.. 0000290: 46fc ab00 0ee8 1300 8b46 fe8e c033 ffb9 F........F...3.. 00002a0: 0060 33c0 fcf3 ab8b e5eb 7455 8bec 8b46 .`3.......tU...F -00002b0: 048e d8bb 0000 c687 0381 98e6 439a 8181 ............C... +00002b0: 048e d8bb 0000 c687 8181 8181 8181 8181 ................ 00002c0: c687 0210 85be 0008 b1ff e85d 00fc 32e4 ...........]..2. -00002d0: b100 e855 002e 8b0e 8181 8181 8181 8181 ...U............ -00002e0: 7523 c687 0410 0d2e 8b16 1c00 8181 8181 u#.............. -00002f0: 8814 8881 8181 8181 8198 e643 9a81 8181 ...........C.... +00002d0: b100 e855 002e 8b0e 8181 8181 8198 e643 ...U...........C +00002e0: 7523 c687 0410 0d2e 8b16 1c00 9a81 8181 u#.............. +00002f0: 8814 8834 8198 e643 9a81 8181 8181 8181 ...4...C........ 0000300: 1009 e836 0084 870d 10ac 02e0 aa4e e2cc ...6.........N.. 0000310: 2e3a 2620 0075 065d 0633 c050 cb5d cb07 .:& .u.].3.P.].. 0000320: 1f5d 5f5e 5a59 5b58 9dcb c687 0410 0b88 .]_^ZY[X........ -0000330: 0cc6 871e 1000 c687 0410 09f6 8198 e643 ...............C +0000330: 0cc6 871e 1000 c687 0410 09f6 8181 8181 ................ 0000340: f687 2010 80f6 8720 1080 f687 2010 80f6 .. .... .... ... -0000350: 8704 1080 74f9 f687 2010 80f6 9a81 8181 ....t... ....... -0000360: c31c 0000 0000 0000 0000 0000 8100 0081 ................ -0000370: 0000 0000 8100 8181 8181 8181 8181 8181 ................ +0000350: 8704 1080 74f9 f687 2010 80f6 8181 8181 ....t... ....... +0000360: c31c 0000 0000 0000 0000 0000 0081 8181 ................ +0000370: 0000 0000 0000 0000 8181 98e6 439a 8181 ............C... 0000380: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0000390: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00003a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ -00003b0: 0000 0000 0000 0000 8181 8181 98e6 439a ..............C. +00003b0: 0000 0000 0000 0000 8181 98e6 439a 8181 ............C... 00003c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ -00003d0: 0000 0000 0000 0000 8181 8181 98e6 439a ..............C. +00003d0: 0000 0000 0000 0000 8181 8181 8181 8181 ................ 00003e0: 0000 0000 0000 0000 0000 0000 8181 8181 ................ -00003f0: 0000 8100 8181 8181 8181 8181 8181 8181 ................ +00003f0: 8181 0000 8181 8181 98e6 439a 8181 8181 ..........C..... 0000400: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0000410: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0000420: 0000 0000 0000 0000 0000 0000 0000 0000 ................ === that data was read by === cmd(bios, NAND_CMD_READ0); adr(bios, page); doc_read_nop(bios); /* nop between write/read */ doc_write_cdsncontrol(bios, CDSN_CTRL_CE); doc_read(bios, ReadPipelineInitialization); for(i=0; i<512-1; i++) { doc_read_4nop(bios); doc_read(bios, CDSNSlowIO); doc_read_4nop(bios); buf[offset++] = doc_read(bios, _CDSNIO_BASE+i); doc_read_4nop(bios); } buf[offset++] = doc_read(bios, LastDataRead); doc_write_cdsncontrol(bios, CDSN_CTRL_CE); if(doc_wait(bios, 5000)) { printf("outch...\n"); return(-1); } === if i read without CDSNSlowIO and without doc_read_4nop(bios) then the result is worse and more bits/bytes are different each read. if i read doc_read(bios, _CDSNIO_BASE) (***check the missing ``+ i''***) then i get 0x55 all the time (except for doc_read(bios, LastDataRead)). all this is very strange and i am beginning to think that my DoC (the flash in it) is damaged. any idea? niki w. waibel

2 2

Thinkpad 440BX bios
by Jeffrey Knight 17 Sep '03

17 Sep '03

Hi I noticed on the linuxbios site that there was some suceess with linuxBIOS on an IBM T22 thinkpad. Nice! Was this done using Intel's phlash utilities, or did did it require some disk-on-chip hardware work? If the installation was pretty smooth, I was thinking of trying it on a 385XD thinkpad. Any advice ? Jeff

2 1

Question about PCX support
by David Hendricks 17 Sep '03

17 Sep '03

In the vga_load_pcx.c file, it says: // This routine supports variable width and height but the default // for linuxbios is 640 x 400 pixels. Is that 400 a typo? It seems like it should be 640 x 480.

2 1

← Newer
1
...
7
8
9
10
11
12
13
...
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