| 4:35 am on Apr 12, 2003 (gmt 0)|
Edit /etc/lilo.conf (as root) and add the line (as the first line) :
Obviously, 128 would not be correct in your case, so change that and reboot. Have a rescue disk handy as this can go wrong. If so, your machine won't boot, hence the need for a rescue disk.
Lower the value in that case and reboot again.
| 6:42 am on Apr 12, 2003 (gmt 0)|
No need for that - yet. When the machine is loading, at the LILO prompt write Linux (or the kernel you want to load) and mem=xxxM; it would look
LILO: Linux mem=128M
or something like that; and if it doesn't load just run the usual LILO, nothing was changed. When you're sure modify lilo.conf.
| 1:45 pm on Apr 12, 2003 (gmt 0)|
i did the append in the lilo.conf.anaconda since there was not just a lilo.conf in the etc folder. the machine did load, but I'm not sure if the program is utilizing the other sticks. I am using a grub loader and could not get the linux mem command to work from the command prompt. maybe i didnt do this process right, if I didn't let me know please. Thank you for your responses.
| 10:05 am on Apr 15, 2003 (gmt 0)|
Since you aren't using Lilo (you are using Grub) thats why you don't have /etc/lilo.conf. I would guess lilo.conf.anaconda is only used in installation. (anaconda is the red hat installer)
Have you checked the bios is finding the memory..? It should show it when it boots up. Also, have you checked to see if you need any drivers for your motherboard?
| 12:32 pm on Apr 15, 2003 (gmt 0)|
it scans all three sticks of 128M and then proceeds to checking drives. Then it loads os.