9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: chuckf@arcor.de
To: 9fans@cse.psu.edu
Cc: kruhft@gmail.com
Subject: [9fans] install  "out of physical memory"
Date: Sun, 17 Sep 2006 16:06:38 +0200	[thread overview]
Message-ID: <6104977.1158501998226.JavaMail.ngmail@webmail12> (raw)

Hallo,
 I read this in the archives regarding the Compaq. I"m having the same
problem with physical memory. I don"t quite understand how you overcame it.

Can you explain in more detail? Do i copy another program to the floppy..like
"9pccd.gz" Does it contain a different swap routine?  Do I need a utility program?
I tried "swapon" and named a linuxswap portion... didn't help.


........from archives 2005 July......
The major installation problem was that the system was constantly 
running out of physical memory during the distmount phase. After a 
bunch of hunting and exploration, it looked like the kernel was only 
reporting about 3k free pages of free physical memory, with about 16k 
pages of swap (approx numbers). 

I managed to get the plan9 partion 'preped' with a swap, so after 
copying the swap utility from the plan9 boot image (9pccd.gz) to a 
shared ext2 partition i was able to use it from the plan9 install image 
(9pcflop.gz) and fire up the swap file so I could sucessfully perform 
the install. 

Everything went smoothly with the install after that and I'm now 
booting plan9 from the harddrive using grub. :) 

After this experience, I have a feeling that either there's a bug in my 
comp's mainboard which causes problems with the physical memory 
calculation or (since I don't know much about the kernel yet) it has a 
hardcoded max somewhere that is limiting my available memory. Any 
comments on this problem or suggestions on how to fix it? 

And finally, I would suggest to the iso maintainers that they put the 
swap utility in the 9pcflop.gz image and some instructions in the 
installation/installer to enable the swap file when it's created so 
others don't have this kind of problem.


             reply	other threads:[~2006-09-17 14:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-17 14:06 chuckf [this message]
2006-09-17 18:31 ` erik quanstrom
2006-09-17 19:13   ` Chuck Foreman
2006-09-17 19:22     ` Russ Cox
     [not found]       ` <ee9e417a0609171222v1163c0d5k49987948781fc714@mail.gmail.co m>
2006-09-17 20:05         ` Chuck Foreman
2006-09-17 20:33           ` Russ Cox
2006-09-17 20:40             ` John Floren
2006-09-17 21:01               ` geoff
2006-09-17 21:03                 ` John Floren
2006-09-17 21:23                   ` geoff
2006-09-17 21:10                 ` Bruce Ellis
2006-09-17 21:18                   ` erik quanstrom
2006-09-17 21:20                     ` Bruce Ellis
2006-09-17 23:32                       ` erik quanstrom
2006-09-18  1:20                         ` geoff
     [not found]             ` <ee9e417a0609171333t228a677eh39d1db121c39ab21@mail.gmail.co m>
2006-09-17 22:35               ` Chuck Foreman
2006-09-18  3:34                 ` Burton Samograd
     [not found]                   ` <7155ede00609172034w1d7ee768paff34c7577d6178a@mail.gmail.co m>
2006-09-18 18:28                     ` Chuck Foreman
2006-09-17 19:23 Chuck Foreman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6104977.1158501998226.JavaMail.ngmail@webmail12 \
    --to=chuckf@arcor.de \
    --cc=9fans@cse.psu.edu \
    --cc=kruhft@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).