1 |
Okay, now Lilo loads the first stage and returns the error-code 99. The |
2 |
man-page contains a paragraph containing the error codes: |
3 |
99 invalid second stage index sector |
4 |
and a detailed description: |
5 |
"... Errors 99 and 9A usually mean the map file (-m or map=) is not |
6 |
readable, likely because LILO was not re-run after some system change, |
7 |
or there is a geometry mis-match between what LILO used (lilo -v3 to |
8 |
display) and what is actually being used by the BIOS (one of the lilo |
9 |
diagnostic disks, available in the source distribution, may be needed to |
10 |
diagnose this problem). ..." |
11 |
|
12 |
But how can I get the right device-map needed for my embedded system? I |
13 |
tried to create a CF card with the diagnostic disks data (writing on CF |
14 |
instead of wirting to /dev/sd0) but the system doesn't even boot with |
15 |
this CF-Card. |
16 |
|
17 |
Lutz |
18 |
|
19 |
Ned Ludd wrote: |
20 |
> I always used lilo for this task. I found grub to be way to problematic |
21 |
> and BIG. On x86 I'd chroot into the CF and run lilo. It can be tricky |
22 |
> and a tad confusing at times till you make that mental map of where the |
23 |
> devices live. Note be careful or you could end up killing the wrong |
24 |
> boot sector or device. |
25 |
> |
26 |
> My CF was my /dev/sdb but CF is IDE so I needed a conf like this. |
27 |
> http://dev.gentoo.org/~solar/embedded/local/local/customize/etc/lilo.conf |
28 |
> |
29 |
> The kernel got installed to sdb1->hda1 and sdb2->hda2 was used as the |
30 |
> ROOT file system. |
31 |
> |
32 |
> I also used these two scripts to speed up the task. |
33 |
> |
34 |
> (Format the CF) |
35 |
> http://dev.gentoo.org/~solar/embedded/fdisk_cf_flash |
36 |
> |
37 |
> (Copy the FS to flash and run the bootloader) |
38 |
> http://dev.gentoo.org/~solar/embedded/flash_cf_disk |
39 |
> |
40 |
> .. good luck. |
41 |
> |
42 |
> |
43 |
> |
44 |
> On Tue, 2006-03-28 at 11:37 +0200, Lutz Schönemann wrote: |
45 |
> |
46 |
>>Hi, |
47 |
>>I'm trying to get Linux running on a x86 embedded-system (Panel PC |
48 |
>>"Atlas"). The os should be loaded from a CF-Card (CF-Card reader is |
49 |
>>onboard and bootable). My current problem with it is that I don't know |
50 |
>>how to get a bootloader installed on a CF-Card. |
51 |
>>I have a Gentoo-Box (Toshiba Laptop) compiled for i386. The CF-Card is |
52 |
>>connected via USB. When ever I install a bootloader on the CF-Card a |
53 |
>>Dell laptop is able to boot from it but the embedded system doesn't do |
54 |
>>it. It seems to be the problem that the two BIOS differ to much from |
55 |
>>each other. |
56 |
>>How can I install a bootloader that works on other hardware (with |
57 |
>>different BIOS)? |
58 |
>> |
59 |
>>Someone told me to build a very small kernel and put that into the |
60 |
>>master boot record (must be smaller than 446 bytes). How can I do this? |
61 |
>>I have deactivated nearly all features, compiled everything as module |
62 |
>>that could be build as module but the kernel size is 627k !?! |
63 |
>> |
64 |
>>For more information on the hardware: |
65 |
>>http://www.kws-computer.de/ppcatlas.html |
66 |
>> |
67 |
>>there is a link to the data sheet (Datenblatt) |
68 |
>> |
69 |
>>Thanks for help |
70 |
>> |
71 |
>>-- |
72 |
>>Lutz Schönemann |
73 |
>> |
74 |
>>Addr: Fraunhofer Institut für Sichere Informations Technologie SIT |
75 |
>> Rheinstrasse 75, 64295 Darmstadt, Germany |
76 |
>>WWW: http://www.sit.fraunhofer.de |
77 |
>> |
78 |
>>Zertifizierungen in der FhG: http://pki.fraunhofer.de |
79 |
|
80 |
|
81 |
-- |
82 |
Lutz Schönemann |
83 |
|
84 |
Addr: Fraunhofer Institut für Sichere Informations Technologie SIT |
85 |
Rheinstrasse 75, 64295 Darmstadt, Germany |
86 |
WWW: http://www.sit.fraunhofer.de |
87 |
|
88 |
Zertifizierungen in der FhG: http://pki.fraunhofer.de |
89 |
-- |
90 |
gentoo-embedded@g.o mailing list |