On Fri, Jan 07, 2000 at 12:09:43PM -0800, William Heindl wrote:
>
> I am running slink on an IBM 560Z with 128Meg of RAM. Only 64Meg are
> being seen (as evidenced from doing "dmesg"). Now, I have seen in
> various HOWTOs that this is expected, and the solution is to build the
> kernel with "new
On Fri, Jan 07, 2000 at 12:09:43PM -0800, William Heindl wrote:
>
> I am running slink on an IBM 560Z with 128Meg of RAM. Only 64Meg are
> being seen (as evidenced from doing "dmesg"). Now, I have seen in
> various HOWTOs that this is expected, and the solution is to build the
> kernel with "new
On Sat, 08 Jan 2000, William Heindl wrote:
>I am running slink on an IBM 560Z with 128Meg of RAM. Only 64Meg are
>being seen (as evidenced from doing "dmesg"). Now, I have seen in
>various HOWTOs that this is expected, and the solution is to build the
>kernel with "newmem" set. However, I'm puzz
On Sat, 08 Jan 2000, William Heindl wrote:
>I am running slink on an IBM 560Z with 128Meg of RAM. Only 64Meg are
>being seen (as evidenced from doing "dmesg"). Now, I have seen in
>various HOWTOs that this is expected, and the solution is to build the
>kernel with "newmem" set. However, I'm puzz
Just put line
append="mem=128M" in your /etc/lilo.conf and run lilo again.
2.2.x can't see all ram in my laptop, either.
Chanop
On Fri, Jan 07, 2000 at 12:09:43PM -0800, William Heindl wrote:
>
> I am running slink on an IBM 560Z with 128Meg of RAM. Only 64Meg are
> being seen (as evidenced f
Just put line
append="mem=128M" in your /etc/lilo.conf and run lilo again.
2.2.x can't see all ram in my laptop, either.
Chanop
On Fri, Jan 07, 2000 at 12:09:43PM -0800, William Heindl wrote:
>
> I am running slink on an IBM 560Z with 128Meg of RAM. Only 64Meg are
> being seen (as evidenced f
You can easily go to a 2.2. kernel without changing the distribution.
download the source from ftp.kernel.org or a mirror, it compiles easily.
Check make-kpkg if you want to make a debian package from the kernel.
The 2.2 kernel may or may not see the memory, again, try the mem=64m on
the kenrel
You can easily go to a 2.2. kernel without changing the distribution.
download the source from ftp.kernel.org or a mirror, it compiles easily.
Check make-kpkg if you want to make a debian package from the kernel.
The 2.2 kernel may or may not see the memory, again, try the mem=64m on
the kenrel
>
> Will stepping up to potato (I assume that's what you mean by a 2.2
> based kernel) necessarily fix the memory problem? Also,
> how big a headache am I in for in compiling the kernel and pcmcia
> services? I'm a bit of a novice at this Linux system administration
> stuff, although I've been a
>
> Will stepping up to potato (I assume that's what you mean by a 2.2
> based kernel) necessarily fix the memory problem? Also,
> how big a headache am I in for in compiling the kernel and pcmcia
> services? I'm a bit of a novice at this Linux system administration
> stuff, although I've been a
Hi,
Yes, the BIOS does pick up the memory. This machine dual boots NT,
and NT has no problem seeing all 128Meg. However, in Linux, at boot
time I just get:
Memory: sized by int13 088h
Console: 16 point font, 400 scans
Console: colour VGA+ 80x25, 1 virtual console (max 63)
pcibios_init : BIOS
Hi,
Yes, the BIOS does pick up the memory. This machine dual boots NT,
and NT has no problem seeing all 128Meg. However, in Linux, at boot
time I just get:
Memory: sized by int13 088h
Console: 16 point font, 400 scans
Console: colour VGA+ 80x25, 1 virtual console (max 63)
pcibios_init : BIOS
If you have not yet, now is a good time to move up to a 2.2 based kernel.
Beyond that, does your bios see the mem? Do you see it at boot time?
If you have not yet, now is a good time to move up to a 2.2 based kernel.
Beyond that, does your bios see the mem? Do you see it at boot time?
This isn't so much a laptop problem as a "some machines" problem. add
mem=XXm to the kernel in startup. If using lilo this can be done with the
append line, but I suggest you test it using manual entry first
On Fri, 7 Jan 2000, William Heindl wrote:
>
> I am running slink on an IBM 560Z with 1
This isn't so much a laptop problem as a "some machines" problem. add
mem=XXm to the kernel in startup. If using lilo this can be done with the
append line, but I suggest you test it using manual entry first
On Fri, 7 Jan 2000, William Heindl wrote:
>
> I am running slink on an IBM 560Z with 1
I am running slink on an IBM 560Z with 128Meg of RAM. Only 64Meg are
being seen (as evidenced from doing "dmesg"). Now, I have seen in
various HOWTOs that this is expected, and the solution is to build the
kernel with "newmem" set. However, I'm puzzled. Two guys at my
office built their system
I am running slink on an IBM 560Z with 128Meg of RAM. Only 64Meg are
being seen (as evidenced from doing "dmesg"). Now, I have seen in
various HOWTOs that this is expected, and the solution is to build the
kernel with "newmem" set. However, I'm puzzled. Two guys at my
office built their system
18 matches
Mail list logo
