I'm almost done with this Proliant!!! I've got slack running, but free -m
only shows 900 or so mb ram, I've got 2gig in the box. In my .config, I've
got

# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
CONFIG_HIGHIO=y

Any ideas?

Somedude wrote:
> I'm almost done with this Proliant!!! I've got slack running, but free -m
> only shows 900 or so mb ram, I've got 2gig in the box. In my .config, I've
> got
>
> # CONFIG_NOHIGHMEM is not set
> CONFIG_HIGHMEM4G=y
> # CONFIG_HIGHMEM64G is not set
> CONFIG_HIGHMEM=y
> CONFIG_HIGHIO=y

root@oslo:~# cat /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 1058414592 701579264 356835328 0 123088896 327155712
Swap: 1027760128 0 1027760128
MemTotal: 1033608 kB
MemFree: 348472 kB
MemShared: 0 kB
Buffers: 120204 kB
Cached: 319488 kB
SwapCached: 0 kB
Active: 283992 kB
Inactive: 219760 kB
HighTotal: 131048 kB
HighFree: 2044 kB
LowTotal: 902560 kB
LowFree: 346428 kB
SwapTotal: 1003672 kB
SwapFree: 1003672 kB

Snip of my .config (2.4.27):
# Processor type and features
#
CONFIG_MPENTIUM4=y
CONFIG_HIGHMEM4G=y
CONFIG_HIGHMEM=y
CONFIG_MTRR=y
CONFIG_SMP=y

Are you sure you edited lilo.conf correctly (after copying the new image
to /boot) and ran lilo after compiling your new kernel? You may still
load the old kernel!

"Trygve Selmer" <trselmer@start.no> wrote in message
news:4179A543.3040601@start.no...
> Somedude wrote:
> > I'm almost done with this Proliant!!! I've got slack running, but
free -m
> > only shows 900 or so mb ram, I've got 2gig in the box. In my .config,
I've
> > got
> >
> > # CONFIG_NOHIGHMEM is not set
> > CONFIG_HIGHMEM4G=y
> > # CONFIG_HIGHMEM64G is not set
> > CONFIG_HIGHMEM=y
> > CONFIG_HIGHIO=y
>
> root@oslo:~# cat /proc/meminfo
> total: used: free: shared: buffers: cached:
> Mem: 1058414592 701579264 356835328 0 123088896 327155712
> Swap: 1027760128 0 1027760128
> MemTotal: 1033608 kB
> MemFree: 348472 kB
> MemShared: 0 kB
> Buffers: 120204 kB
> Cached: 319488 kB
> SwapCached: 0 kB
> Active: 283992 kB
> Inactive: 219760 kB
> HighTotal: 131048 kB
> HighFree: 2044 kB
> LowTotal: 902560 kB
> LowFree: 346428 kB
> SwapTotal: 1003672 kB
> SwapFree: 1003672 kB
>
> Snip of my .config (2.4.27):
> # Processor type and features
> #
> CONFIG_MPENTIUM4=y
> CONFIG_HIGHMEM4G=y
> CONFIG_HIGHMEM=y
> CONFIG_MTRR=y
> CONFIG_SMP=y
>
> Are you sure you edited lilo.conf correctly (after copying the new image
> to /boot) and ran lilo after compiling your new kernel? You may still
> load the old kernel!
>
What do I need to edit in lilo.conf?

SomeDude wrote:
> "Trygve Selmer" <trselmer@start.no> wrote in message
> news:4179A543.3040601@start.no...
>
>>Somedude wrote:
>>
>>>I'm almost done with this Proliant!!! I've got slack running, but
>>>free -m only shows 900 or so mb ram, I've got 2gig in the box.
>>
>>Are you sure you edited lilo.conf correctly (after copying the new image
>>to /boot) and ran lilo after compiling your new kernel? You may still
>>load the old kernel!
>
> What do I need to edit in lilo.conf?

Just be sure your lilo.conf points to your newly installed kernel, then
run the command lilo.

Hi
I'm Daryoush and a new member.

Try following in the lilo.conf

append="MEM=2048M"



Somedude wrote:
> I'm almost done with this Proliant!!! I've got slack running, but
free -m
> only shows 900 or so mb ram, I've got 2gig in the box. In my
..config, I've
> got
>
> # CONFIG_NOHIGHMEM is not set
> CONFIG_HIGHMEM4G=y
> # CONFIG_HIGHMEM64G is not set
> CONFIG_HIGHMEM=y
> CONFIG_HIGHIO=y
>
> Any ideas?

daryoush.ashtari@gmail.com wrote:

> Hi
> I'm Daryoush and a new member.

Of what I wonder.

The more usual practice is to write your answer to a given issue,
*underneath* the trimmed, quoted material.
--
Two Ravens
"...hit the squirrel..."

"Two Ravens" <two-ravens@opera$mail.com> wrote in message
news:417a673f$0$1397$cc9e4d1f@news-text.dial.pipex.com...
> daryoush.ashtari@gmail.com wrote:
>
> > Hi
> > I'm Daryoush and a new member.
>
> Of what I wonder.
>
> The more usual practice is to write your answer to a given issue,
> *underneath* the trimmed, quoted material.
> --
> Two Ravens
> "...hit the squirrel..."

Hey all, thanks for the tips. I figured it out. I was examining the
..config file, and the options WERE correct. What I didn't mention earlier
was when I'd try to reboot with the recompiled kerel, I'd get an "unable to
mount root" so I figured I screwed some of the stuff up. Turns out, I
recompiled and just turned everything in the filesystems that I didn't know
(or didn't FOR SURE need) on, or compiled in...and all is good.

I'm not sure however if the .config in the /usr/src/linux directory is the
same as the running kernel I'm using right after the install...?? That was
what was throwing me off..

Thanks for all your help, this group is awesome...

SomeDude wrote:

> I'm not sure however if the .config in the /usr/src/linux directory is the
> same as the running kernel I'm using right after the install...??**That
> was what was throwing me off..

The .config file that you used to compile the running kernel is the one that
matches the running kernel. If you *just now* compiled the kernel in that
directory, and *just now* installed it, and didn't move anything .config
files around after that, then yes, that file will represent the
configuration of your new kernel.

But the kernel doesn't know anything about the configuration file that was
used to create it, so it's up to you to keep a copy of the configuration
around for each kernel if you want to refer to it. A common practice is to
copy the configuration for your running kernel to /boot/config for this
purpose.

Jeffrey