public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Iliev <danny@ilievnet.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] [OT] AGPART [SOLVED]
Date: Sat, 5 May 2007 10:58:13 +0300	[thread overview]
Message-ID: <20070505075815.DE6FA92266@mail.ilievnet.com> (raw)
In-Reply-To: <20070504170035.8E51699466@mail.ilievnet.com>

Thanks, guys!

I knew it was IOMMU, as stated in the help section I quoted in the
first message. I had seen "IOMMU=y" in my .config, but I couldn't find
it anywhere in "menuconfig" in order to disable it. So, Jeffrey
Gardner's response helped me "fix" it. I've always been disabling that
"Small Systems" section because of it's name "CONFIG_EMBEDDED" and
because of the statement "change this stuff only if you know what ya
doin'". So, IOMMU was hidden and auto-enabled.

Duncan, thanks for your most detailed answer. Now I know an additional
thing that should be done when compiling a kernel for systems with >3.5G
RAM. Unfortunately I've got no such "problem" ;-) and I'm happy with
my 1G of RAM. It gets rarely used at 100%. Actually only in situations
like compilation of updated packages + web surfing in the same time.
Beryl and Firefox are my biggest resident memory hogs.

Have a nice weekend, people! :)


-- 
Best regards,
Daniel

-- 
gentoo-amd64@gentoo.org mailing list



  parent reply	other threads:[~2007-05-05  8:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04 17:00 [gentoo-amd64] [OT] AGPART Daniel Iliev
2007-05-04 17:36 ` Jeffrey Gardner
2007-05-04 18:21   ` Wil Reichert
2007-05-04 18:47     ` Jeffrey Gardner
2007-05-05  1:58   ` [gentoo-amd64] " Duncan
2007-05-05  7:58 ` Daniel Iliev [this message]
2007-05-05  9:15   ` [gentoo-amd64] Re: [OT] AGPART [SOLVED] Duncan
2007-05-05  9:49     ` Peter Humphrey
2007-05-05 13:56     ` Boyd Stephen Smith Jr.
2007-05-06 14:36       ` [gentoo-amd64] Memory usage Was: " Duncan
2007-05-06  8:34     ` [gentoo-amd64] Re: [OT] AGPART [SOLVED] DRIFT: RAM USAGE Daniel Iliev
2007-05-06 13:36       ` Duncan

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=20070505075815.DE6FA92266@mail.ilievnet.com \
    --to=danny@ilievnet.com \
    --cc=gentoo-amd64@lists.gentoo.org \
    /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