On Fri, 19 Nov 1999, Michael H. Warfield wrote:
> and he should try 2.2.13 as well (2.2.5 sucks anyways).
Truelly right!!! It sucks alot
"La gente que usa VB, solo Ve lo Basico"
-
Martín Marqués email: [EMAI
On Fri, Nov 19, 1999 at 10:59:10AM -0300, Martin A. Marques wrote:
> On Fri, 19 Nov 1999, Charles Galpin wrote:
> > Jesus
> > As others have said, the kernel version you are running should recognize
> > your ram without any lilo lines. I suggest trying two things.
> Wrong!!! Until kernel 2.2.12
On Fri, 19 Nov 1999, Charles Galpin wrote:
> Jesus
>
> As others have said, the kernel version you are running should recognize
> your ram without any lilo lines. I suggest trying two things.
Wrong!!! Until kernel 2.2.12 I had no support for my SiS Moderboard with
a SiS video card which uses me
Jesus
As others have said, the kernel version you are running should recognize
your ram without any lilo lines. I suggest trying two things.
1. Check your bios options. Although this problem doesn't sound like the
exact same thing, others have reported problems with bios memory hole
settings.
2
Ill throw in my 2c worth one more time
and may be this may help or maybe not
My line which DOES work is
append = "mem=128m"
with spaces and small m's just as above
Try it and let me know
Phil
On Fri, 19 Nov 1999, Jesus Peco wrote:
> Hello again;
>
>I've
label=linux
> root=/dev/hda5
> read-only
> append="mem=128M"
> other=/dev/hda1
> label=dos
> table=/dev/hda
>
> I've tested:
> append = "mem=128M"
> append="mem=128m"
> append = &qu
Hello again;
I've tried everything you said but without success.
Here is the lilo.conf again.
boot=/dev/hda5
map=/boot/map
install=/boot/boot.b
prompt
linear
timeout=50
image=/boot/vmlinuz-2.2.5-15
label=linux
root=/dev/hda5
read-only
append=&quo
:-)
Hey thanks BUT
something has gone amiss here
I am not the origianl poster , in fact my line as posted works fine, my RAN is
detected, all of it
I was only pointing out the spaces
as in append="mem=128m"
or append = "mem=128m"
I have the second line with the spaces w
Is it the spaces that are messing up?
This is my line
append = "mem=128m"
Phil
"Martin A. Marques" wrote:
> On Thu, 18 Nov 1999, Gerald Henriksen wrote:
> > append="mem=128M" must be the first line in your lilo.conf file, then run
> > /s
On Thu, 18 Nov 1999, Gerald Henriksen wrote:
> append="mem=128M" must be the first line in your lilo.conf file, then run
> /sbin/lilo and then reboot.
Not necesarrily..
I'll show you mine:
image=/boot/vmlinuz-2.2.13
label=new-13
append="mem=12
On Thu, Nov 18, 1999 at 11:19:27AM -0500, Gerald Henriksen wrote:
> append="mem=128M" must be the first line in your lilo.conf file, then run
> /sbin/lilo and then reboot.
Not true. It does not have to be the first line of lilo.conf and
can be on an image by image
On Thu, 18 Nov 1999, Jesus Peco wrote:
> I have a Pentium II celeron and RedHat6.0 with
> 128M RAM. I have just recompiled the kernel 2.2.5-15
> for a pentium II processor.
...
>
> Is there a way to make linux see I have 128M?
> Do I have a hardware problem?
append="mem=128M" must be the first line in your lilo.conf file, then run
/sbin/lilo and then reboot.
On Thu, 18 Nov 1999, Jesus Peco wrote:
> I have a Pentium II celeron and RedHat6.0 with
> 128M RAM. I have just recompiled the kernel 2.2.5-15
> for a pentium II proces
On Thu, 18 Nov 1999, Jesus Peco wrote:
> I have a Pentium II celeron and RedHat6.0 with
> 128M RAM. I have just recompiled the kernel 2.2.5-15
> for a pentium II processor.
What machine do U have??? Does it have a SIS moderboard with everything
onboard??? In that case you will have to
I have a Pentium II celeron and RedHat6.0 with
128M RAM. I have just recompiled the kernel 2.2.5-15
for a pentium II processor.
I have changed the lilo.conf like this:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/vmlinuz131099
label=linux
15 matches
Mail list logo
