Pleased experienced on EPIA : Linuxbios runs,but smbus errors, no normal rom starting, payload making difficulties

Thu May 6 07:43:01 CEST 2004

hello to every linuxBios people,

First, I would like I got V2 started on EPIA C3 Ezra with a null 
payload for a start ...and that truely welcome and pleasant. 

I heared a while ago of a half baud rate problem, I 
have no worries on this side. I was trying to to collect
debug serial sent strings via minicom, but i would't advice 
this, it's a mess to configure (in fact for someone like I).
I've just make it with this script that I have joined in there
if it is of any use to somebody :

#!/bin/bash
# Hear !
#
#
( [ "x$1" = "x" ] && echo "Usage $0 log_file" && exit 0)|| $LOG="$1"
ter=`tty`
echo "****************************************************" >>$LOG 
echo " Hear! Boot Log started on `date +%d/%m/%y\|%T` " >> $LOG
echo "  tty in use : $ter  from ttyS0 " >>$LOG
echo "****************************************************" >>$LOG 

  cat -sbA </dev/ttyS0 | tee -a $LOG

It can be lauch that way :
[root at ge] sh hear.sh boot.log
[root at ge] cat boot.log | while read line; do if [ "x$line" != "x$" ];
then echo $line;fi;done

it outputs the bellow log with some non-fatal (?) error
on which, firstly I would like some explanation if you will

****************************************************
 Hear! Boot Log started on 04/05/04|17:27:54 
  tty in use : /dev/pts/0  from ttyS0 
****************************************************
1 jM-^^xM-C$
2 LinuxBIOS-1.1.6.0Fallback Mon May 3 18:39:09 CEST 2004 starting...$

Why the normal rom didn't start first, though I config 2 payloads
normal and fallback. I belived fallback were called in case of
fallback BTW of erroring normal rom ?! 

3 vt8601 init starting$
4 Slot 00 is SDRAM 04000000 bytes $
5 Slot 01 is SDRAM 04000000 bytes $

6 Slot 02smbus_error: 04$
7 Device Error$
8 is empty$
9 Slot 03smbus_error: 04$
10 Device Error$
11 is empty$

What are these error number refers to ? 
It work though, but these errors while init plus the fallback mode
right from the start, show nothing good for the future deployement
I presume ... anyway

12 vt8601 done$
13 POST: 0x39$
14 LinuxBIOS-1.1.6.0Fallback Mon May 3 18:39:09 CEST 2004 booting...$
15 POST: 0x40$
16 Finding PCI configuration type.$
17 POST: 0x5f$
18 Enumerating static devices...$
19 Enumerating buses...$
20 POST: 0x24$
21 POST: 0x25$
22 POST: 0x24$
23 POST: 0x25$
24 POST: 0x55$
25 POST: 0x55$
26 done$
27 POST: 0x66$
28 Allocating resources...done.$
29 POST: 0x88$
30 Enabling resourcess...$
31 done.$
32 Initializing devices...$
33 Devices initialized$
34 POST: 0x89$
35 vt8231_init: enabling compatibility IDE addresses$
36 Ethernet fixup$
37 pci_routing_fixup: dev is 00017fc0$
38 setting southbridge$
39 setting ethernet$
40 setting pci slot$
41 pci_routing_fixup: DONE$
42 POST: 0x70$
43 totalram: 128M$
44 Initializing CPU #0$
45 POST: 0x60$
46 Enabling cache...POST: 0x6a$
47 done.$
48 POST: 0x92$
49 POST: 0x93$
50 Disabling local apic...done.$
51 POST: 0x9b$
52 CPU #0 Initialized$
53 POST: 0x75$
54 POST: 0x9a$
55 Checking IRQ routing tables...$
56 done.$
57 Copying IRQ routing tables to 0xf0000...done.$
58 Verifing copy of IRQ routing tables at 0xf0000...done$
59 POST: 0x96$
60 Welcome to elfboot, the open sourced starter.$
61 January 2002, Eric Biederman.$
62 Version 1.3$
63 POST: 0xf8$
64 Cannot Load ELF Image$
65 POST: 0xff$

	So this is ok I have not linked any payload, but why does it 
	redo it once more :

66 jM-^^xM-C$
67 LinuxBIOS-1.1.6.0Fallback Mon May 3 18:39:09 CEST 2004 starting...$
68 vt8601 init starting$
69 Slot 00 is SDRAM 04000000 bytes $
70 Slot 01 is SDRAM 04000000 bytes $
71 Slot 02smbus_error: 04$
72 Device Error$
73 is empty$
74 Slot 03smbus_error: 04$
75 Device Error$
76 is empty$
77 vt8601 done$
78 POST: 0x39$
79 LinuxBIOS-1.1.6.0Fallback Mon May 3 18:39:09 CEST 2004 booting...$
80 POST: 0x40$
81 Finding PCI configuration type.$
82 POST: 0x5f$
83 Enumerating static devices...$
84 Enumerating buses...$
85 POST: 0x24$
86 POST: 0x25$
87 POST: 0x24$
88 POST: 0x25$
89 POST: 0x55$
90 POST: 0x55$
91 done$
92 POST: 0x66$
93 Allocating resources...done.$
94 POST: 0x88$
95 Enabling resourcess...$
96 done.$
97 Initializing devices...$
98 Devices initialized$
99 POST: 0x89$
100 vt8231_init: enabling compatibility IDE addresses$
101 Ethernet fixup$
102 pci_routing_fixup: dev is 00017fc0$
103 setting southbridge$
104 setting ethernet$
105 setting pci slot$
106 pci_routing_fixup: DONE$
107 POST: 0x70$
108 totalram: 128M$
109 Initializing CPU #0$
110 POST: 0x60$
111 Enabling cache...POST: 0x6a$
112 done.$
113 POST: 0x92$
114 POST: 0x93$
115 Disabling local apic...done.$
116 POST: 0x9b$
117 CPU #0 Initialized$
118 POST: 0x75$
119 POST: 0x9a$
120 Checking IRQ routing tables...$
121 done.$
122 Copying IRQ routing tables to 0xf0000...done.$
123 Verifing copy of IRQ routing tables at 0xf0000...done$
124 POST: 0x96$
125 Welcome to elfboot, the open sourced starter.$
126 January 2002, Eric Biederman.$
127 Version 1.3$
128 POST: 0xf8$
129 Cannot Load ELF Image$
130 POST: 0xff$

Secondly, I intended to make a IDE elfImagepayload to boot a kernel
on a hard disk, I've read that LinuxBios alone could do that quite
well.
So got mkelfImage 1.16 (i know it's quite old
but i can't find a link to a recent one- BTW please a link to a more
recent one would be appreciated). 

I had a error on the build that's seems not to be relevant since 
ending ok ( that's i like to say to myself in these cases ) 

[root at ge] make;echo "Build : $?";
find :./kunzip_src: No such file
...
Build : 0

So I made  : mkelfImage -kernel=/boot/vmlinuz 
vmlinuz is a kenel bzImage.
It made elfImage, that is wierd :

ls says :
-rwxr-xr-x    1 root     root       901816 mai  5 10:08 elfImage

file says:
elfImage: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
statically linkedfile: corrupted section header size.

It's corrupted, could it be the build "warn"-error message ?

I've done a readelf -x on it too :

En-tête ELF:
  Magique:   7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 
  Classe:                            ELF32
  Données:                          complément à 2, système à octets de
poids faible d'abord (little endian)
  Version:                           1 (current)
  OS/ABI:                            UNIX - System V
  Version ABI:                       0
  Type:                              EXEC (fichier exécutable)
  Machine:                           Intel 80386
  Version:                           0x1
  Adresse du point d'entrée:         0x101c0
  Début des en-têtes de programme:   52 (octets dans le fichier)
  Début des en-têtes de section:          0 (octets dans le fichier)
  Fanions:                           0x0
  Taille de cet en-tête:             52 (bytes)
  Taille de l'en-tête du programme:  32 (bytes)
  Nombre d'en-tête du programme:     5
  Taille des en-têtes de section:    0 (bytes)
  Nombre d'en-têtes de section:      0
  Table d'indexes des chaînes d'en-tête de section: 0

Il n'y a pas de section dans ce fichier.

En-têtes de programme:
  Type           Décalage Adr. vir.  Adr.phys.  T.Fich. T.Mém.  Fan
Alignement
  NOTE           0x0000d4 0x00010000 0x00010000 0x001c0 0x001c0 RWE 0
  LOAD           0x0000d4 0x00010000 0x00010000 0x0562c 0x058b8 RWE 0
  LOAD           0x0058b8 0x00091000 0x00091000 0x00000 0x00028 RWE 0
  LOAD           0x0058b8 0x00100000 0x00100000 0xd6a00 0x700000 RWE 0
  LOAD           0x0dc2b8 0x00800000 0x00800000 0x00000 0x00000 RWE 0

Il n'y a pas de segement dynamique dans ce fichier.

Il n'y a pas de relocalisation dans ce fichier.

Il n'y a pas de section unwind dans ce fichier.

Aucune information de version repérée dans ce fichier.