Re: standard large memory question

2000-07-12 Thread brian moore
On Wed, Jul 12, 2000 at 07:02:25PM +0100, Jeff Green wrote: > It did automatically detect until the last couple of kernels (progress?) > what you want is append="mem=160M" somewhere in lilo.conf Actually, the BIOS makers started changing the API again. Reverting to an older BIOS will make it work

Re: standard large memory question

2000-07-12 Thread Richard E. Hawkins
> > So I've used > > mem=160 > > Am I missing something obvious? > Yes. The units i.e. mem=160M ahh. That did it. gee, if it won't run in 160 bytes of ram, the port to the 8051 is doomed :) thanks

Re: standard large memory question

2000-07-12 Thread Jeff Green
It did automatically detect until the last couple of kernels (progress?) what you want is append="mem=160M" somewhere in lilo.conf Jeff "Richard E. Hawkins" wrote: > > Ack. I've seen the answer to this dozens of times, but can't find it > in the archives. > > I *thought* that large memory was

Re: standard large memory question

2000-07-12 Thread Debian User
On Wed, 12 Jul 2000, Richard E. Hawkins wrote: > > Ack. I've seen the answer to this dozens of times, but can't find it > in the archives. > > I *thought* that large memory was now automatically detected, but my > system on a nice fresh frozen is still only finding 64M (out of 160M) > > So

standard large memory question

2000-07-12 Thread Richard E. Hawkins
Ack. I've seen the answer to this dozens of times, but can't find it in the archives. I *thought* that large memory was now automatically detected, but my system on a nice fresh frozen is still only finding 64M (out of 160M) So I've used mem=160 at lilo, but the kernel panics trying to cre