Koozali.org: home of the SME Server

RAM

WXP

RAM
« on: September 29, 2001, 08:57:00 PM »
Hey,

I'm installing a server here with 1,5Gb of RAM.
Is it possible to make E-Smith reconize this huge size ?

Because phpSysInfo only tell me 895,59MB

Dan Brown

Re: RAM
« Reply #1 on: September 29, 2001, 09:31:17 PM »
You need to edit lilo.conf, and add the following line under "image=/boot/vmlinuz-2.2.19-7.0.8:

    append="mem=1536M"

There seems to be an "e-smith way" to do this (based on the template file /etc/e-smith/templates/etc/lilo.conf/9170up-append), but I don't know what that would be--I expect there's a configuration database entry that can be made somehow.

Once that change is made, however you do it, run /sbin/lilo and reboot.

steve macgregor

Re: RAM
« Reply #2 on: September 29, 2001, 09:35:33 PM »
If I might ask a very simple question, how would I find out how much RAM e-smith is recognizing?

Thanks,

Steve

Dan Brown

Re: RAM
« Reply #3 on: September 29, 2001, 09:37:01 PM »
The "free" command should do what you need.  It reports sizes in KB.

steve macgregor

Re: RAM
« Reply #4 on: September 29, 2001, 09:47:11 PM »
Dan,

How do I find lilo.conf?

thanks,

steve

Dan Brown

Re: RAM
« Reply #5 on: September 29, 2001, 10:10:04 PM »
/etc/lilo.conf

steve macgregor

Re: RAM
« Reply #6 on: September 29, 2001, 10:40:25 PM »
Thank you for your help Dan. It worked like a charm! (I think... :) )

steve

WXP

Re: RAM
« Reply #7 on: September 30, 2001, 12:20:15 AM »
Dan thanx for your answer !!

Is it ok like this :

[root@sgtserver lilo.conf]# cat /etc/lilo.conf
#------------------------------------------------------------
# DO NOT MODIFY THIS FILE! It is updated automatically by the
# e-smith server and gateway software. Instead, modify the source
# template in the /etc/e-smith/templates directory. For more
# information, see http://www.e-smith.org.
#
# copyright (C) 1999, 2000 e-smith, inc.
#------------------------------------------------------------

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/e-smith.pcx
linear
default=esmith

image=/boot/vmlinuz-2.2.19-7.0.8smp
        label=esmith
        read-only
        root=/dev/hda6




append ="mem=1536M"

image=/boot/vmlinuz-2.2.19-7.0.8
        label=esmith-up
        read-only
        root=/dev/hda6





#------------------------------------------------------------
# TEMPLATE END
#------------------------------------------------------------

WXP

Re: RAM
« Reply #8 on: September 30, 2001, 12:26:20 AM »
First of all, is the kernel compiled with the option > 1 Gb RAM ?!

If not I'm killing you all ;-)))

steve macgregor

Re: RAM
« Reply #9 on: September 30, 2001, 01:42:31 AM »
Ummm, Dan, I think I have a problem... I ran /sbin/lilo and it did it's thing, and then I rebooted and now it says:

Kernel panic: Attempted to kill the idle task!
In swapper task - not syncing

What now? Is there a way to get in and change it back?

Humbly,


Steve

Dan Brown

Re: RAM
« Reply #10 on: September 30, 2001, 01:51:30 AM »
If that's all you changed in lilo.conf, it shouldn't have caused this.  However, this is why God created the boot floppy (you _did_ make one when you installed, right?)  If you boot from that, you should be fine.  If you didn't make one, I'm not sure what's your best way of getting one.  It isn't the same as the installation boot floppy.

steve macgregor

Re: RAM
« Reply #11 on: September 30, 2001, 02:06:06 AM »
I do have a boot floppy! No, I correct that, I have a re-install floppy... but I do have another HD from the same system that I was trying to upgrade to that I just plugged in. any chance I could make a boot floopy from there or should/ could I use an image from the image part of the install CD?

I hate this feeling...

steve

Dan Brown

Re: RAM
« Reply #12 on: September 30, 2001, 02:16:48 AM »
Well, if you unplug the old hard drive, plug in the other one, install e-smith on the new drive, and make the boot floppy, that should work.  AFAIK, none of the images on the CD are suitable.

steve macgregor

Re: RAM
« Reply #13 on: September 30, 2001, 02:19:33 AM »
:) I found that out, and am currently transferring the install image. thank god for a back up drive!

I PROMISE I will ALWAYS make a boot floppy from this day on! (and not overwrite it!)

We will see how it goes.

Thanks again,


Steve

steve macgregor

Re: RAM
« Reply #14 on: September 30, 2001, 02:22:14 AM »
You don't suppose it was because I put the wrong number in there? Honestly, I did it sort of hastily, and it would seem likely that I would do some fool thing like that.

Steve

steve macgregor

Re: RAM
« Reply #15 on: September 30, 2001, 02:33:39 AM »
Thanks for your help Dan. The boot disk worked, and I edited lilo.conf and removed what I had added, rebooted without the floppy and all is well. Runs like a charm!

Steve

Rangi Biddle

Re: RAM
« Reply #16 on: September 30, 2001, 07:57:44 AM »
Just as another quick solution with that change that you made to your lilo.conf file did you just type lilo or did you type lilo -v as adding the -v parameter would verify that everything is working and write the boot sector.

I dunno if that helps any but anyway good luck!!

Chris

Re: RAM & Sysinfo
« Reply #17 on: October 16, 2001, 04:34:36 AM »
Hi there,

Sorry this has nothing to do with your ram problem, but reading though the thred it seems you have that well in hand.

What i would like to know is if there is a RPM for the phpsysinfo 'package'.
Going though the forums lately i have found the tar package with all the files that i need but i carnt figure out what to do with them.

As i understand it the RPM's put everything where it needs to be and updates anything that needs it. correct?

So if that is true where do you find the info in the tar 'package' to know where to put everything?

Any help would be great.

Chris

WXP

Re: RAM & Sysinfo
« Reply #18 on: October 16, 2001, 08:04:02 AM »
Hi,

Untar the phpsysinfo files in a fresh ibays with php and cgi activated..
and that's it !

See ya