Re: slow (s-l-o-w) install - where is mem= ?


----- Original Message -----
From: "Frank Cox" <theatre@xxxxxxxxxxx>
To: "For users of Fedora" <fedora-list@xxxxxxxxxx>
Cc: "Ric Moore" <wayward4now@xxxxxxxxx>
Sent: Saturday, February 16, 2008 7:41 PM
Subject: Re: slow (s-l-o-w) install


On Sat, 16 Feb 2008 21:36:42 -0500
Ric Moore <wayward4now@xxxxxxxxx> wrote:

If you have 2G of memory, would using mem=2G be of any advantage?

I have 4G of memory. It works when I specify "mem=2G". It also works
when I
specify "mem=4024M" but I don't get a whole 4024mb.

Booting without "mem=" causes it to run amazingly slowly.

--
MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list


--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: Call memory reference - NASM - x86
    ... The CALL FAR mem forms execute a far call by loading the destination ... address out of memory. ... offset, and 16 bits of segment. ... Unless you specify otherwise, it is an offset from DS, just like any other memory reference; SS if the base register is ESP, BP, or EBP. ...
    (alt.lang.asm)
  • Call memory reference - NASM - x86
    ... I'd like to do a call to a location in memory specified by a location ... The CALL FAR mem forms execute a far call by loading the destination ... offset, and 16 bits of segment. ... should I specify the call as?: ...
    (alt.lang.asm)
  • Re: slow (s-l-o-w) install
    ... Ric Moore wrote: ... I have 4G of memory. ... It works when I specify "mem=2G". ... Booting without "mem=" causes it to run amazingly slowly. ...
    (Fedora)
  • Re: Programming in standard c
    ... read into memory*. ... If you can actually specify the mode, in many cases the size will be ... It's at least two distinct sizes already. ... such accesses with mandatory file locking. ...
    (comp.lang.c)
  • Re: ManagementEventWatcher.start=OutOfMemoryException
    ... the target system really didn't have enough memory to service the request... ... I have to specify different user/pass for each machine to ... >>>> ManagementEventWatcher watcher; ...
    (microsoft.public.win32.programmer.wmi)