coreboot

coreboot@coreboot.org

10 participants
39710 discussions

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

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot