1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Sat, 13 Dec 2003 02:24 am, you wrote: |
5 |
> > > I plan to boot everything from the CompactFlash card (128MB). I also |
6 |
> > > installed 256MB RAM. I will use an I/O and a multiport RS232 card. |
7 |
> > > |
8 |
> > > |
9 |
> > > I already tried some installations(basically started with slackware, |
10 |
> > > but also tried others) but always failed. It boots ok into DOS but |
11 |
> > > fails booting with LiLo(it returned LI 04 - which shall be "sector not |
12 |
> > > found"). It runs ok if I boot from a rescue floppy and the chroot to |
13 |
> > > CF's /. |
14 |
> > |
15 |
> > Be very careful with your lilo options. Make sure the specify what the |
16 |
> > boot device is at bootup (not /dev/sda1 when its attached to you card |
17 |
> > read/ writer). I remeber I did something with the bios=0x84(?) options in |
18 |
> > lilo to make it work (I had a harddrive and a compact flash to that may |
19 |
> > of been related). I'll email my former collegue to attempt to obtain the |
20 |
> > lilo configuration. I do remember facing a similar problem. lba related |
21 |
> > maybe but I can't remember exactly. |
22 |
> |
23 |
> OK, I actually made it to install lilo on /dev/sda1 (while on desktop |
24 |
> machine). in lilo.conf everything was /dev/hda1 as will be on the |
25 |
> industrial box. lilo was called with -b boot-dev witch overides the |
26 |
> current settings. If lilo started, then this should be ok? |
27 |
> |
28 |
|
29 |
The lilo conf from when I used it |
30 |
|
31 |
boot="/dev/hdc" |
32 |
map=/boot/map |
33 |
install=/boot/boot.b |
34 |
prompt |
35 |
timeout="50 |
36 |
compact |
37 |
disk=/dev/hdc bios=0x80 |
38 |
serial=1,9600b8 |
39 |
append="console=tty0 console=ttyS1,9600n8" |
40 |
default="linuxr" |
41 |
password="pass" |
42 |
restricted |
43 |
image="/boot/bzImage" |
44 |
label=linuxr |
45 |
root=dev/hdc1 |
46 |
|
47 |
The lilo -b may tell it where to write the image but the config file tells it |
48 |
how what is layed out where when it is installed. |
49 |
|
50 |
The bios=0x80 fixed the problem with the LI 04 for me. I was using a compact |
51 |
flash and a harddrive and booting off the compact flash. |
52 |
|
53 |
> > > Now, I have a Gentoo 1.4 running working machine (freshly installed |
54 |
snip |
55 |
> I think RAM shouldn't be a problem. I wouldn't like to write too much on |
56 |
> the CF or is the number of writes nowadays unlimited? |
57 |
|
58 |
Good move. Comment out bits of the bootup process that write to disk and when |
59 |
you think your complete - change the fstab to mount readonly and see what you |
60 |
missed. |
61 |
|
62 |
> > > I would mount the CF for writing settings and some |
63 |
> > > info. |
64 |
> > > At the end I would like to have the major work done on the PC/desktop |
65 |
> > > and only finalize/debug on the PC/104 box. |
66 |
> > > Don't need fancy things, just working environment. It won't have a |
67 |
> > > standard display/keyboard on runtime, anyway. |
68 |
> > |
69 |
> > Look at the serial conole options for the kernel and lilo if you havent' |
70 |
> > already. |
71 |
|
72 |
there is the config for it above. |
73 |
|
74 |
> > > How would "crossdev-0.2", "base-layout lite", "uclibc buildroot/ |
75 |
> > > toolchain", ... help in this process? How to get them? |
76 |
> > |
77 |
> > crossdev = emerge crossdev |
78 |
> |
79 |
> This is then the only one. |
80 |
> Are out there others, I only mentioned the ones mentioned on the list |
81 |
> last days? |
82 |
|
83 |
I the others are work in progress. |
84 |
|
85 |
> Doesn't want to emerge. It says it is masked. (sorry, new to gentoo) |
86 |
> I read somewhere about masked. |
87 |
> Where can I read more on that 'masked' stuff? And how to get it down? |
88 |
|
89 |
env ACCEPT_KEYWORDS="~x86" emerge ..... |
90 |
|
91 |
> > uclibc buildroot = still being worked on although there is an exampe in |
92 |
> > bug 29312 (http://bugs.gentoo.org/show_bug.cgi?id=29312) |
93 |
> > base-layout lite = still in design phases. |
94 |
> > |
95 |
> > If your arch is the same on both machines. Compile binary packages with |
96 |
> > the correct optimisations and to a binary install onto the compact flash. |
97 |
> > Use the "env ROOT=(CF mount point)" to install them. Always do a pretend |
98 |
> > first as I have seen some occasion pecularities where it doesn;t want ot |
99 |
> > install to $ROOT (ref http://bugs.gentoo.org/show_bug.cgi?id=34887) |
100 |
> > |
101 |
> > To save disk space do a bind mount (or symlink) on the CF /usr/share/doc |
102 |
> > some other documentation directories (/usr/share/info /usr/share/man) to |
103 |
> > local disk space. |
104 |
> |
105 |
> info and man pages are not required. |
106 |
|
107 |
Yep - this places these files in a different directory so they aren't copied. |
108 |
|
109 |
> The user won't notice this is a computer - this a weighing machine with |
110 |
> some I/O. It shall be an industrial controller, then decided for linux |
111 |
> due to big number of serial ports, printing and later HTTP or FTP access |
112 |
> for displaying/downloading statistics and maybe(probably, just for the |
113 |
> fun of doing it) some web management. |
114 |
> Display is a 2x16 LCD just for current status, changing params and |
115 |
> major warnings. |
116 |
> |
117 |
|
118 |
sounds good |
119 |
|
120 |
- -- |
121 |
|
122 |
Daniel Black |
123 |
- -- |
124 |
Proudly a Gentoo Linux User. |
125 |
GnuPG/PGP signed and encrypted email preferred |
126 |
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x32A64DC8 |
127 |
-----BEGIN PGP SIGNATURE----- |
128 |
Version: GnuPG v1.2.3 (GNU/Linux) |
129 |
|
130 |
iD8DBQE//hkcTDSbtjKmTcgRAiYjAJ92bud6ySqxeMNzJKfNJ2qNfwwgqACfcLxY |
131 |
7wC0nKzypbBeVsawSzepl8g= |
132 |
=mfDr |
133 |
-----END PGP SIGNATURE----- |
134 |
|
135 |
|
136 |
-- |
137 |
gentoo-embedded@g.o mailing list |