9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Mehmet Erol Sanliturk <m.e.sanliturk@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [NOOB ALERT] Use amd64 kernel?
Date: Sat, 5 Feb 2022 00:28:19 +0300	[thread overview]
Message-ID: <CAOgwaMvfPJx-stwyOKKi+vowpHkMKFq5CD3VxXgAtapU5Nfe8Q@mail.gmail.com> (raw)
In-Reply-To: <1848A8C9E0287E099824E0C4764A5D8C@eigenstate.org>

[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]

On Sat, Feb 5, 2022 at 12:09 AM <ori@eigenstate.org> wrote:

> Quoth Alexander Shendi <Alexander.Shendi@web.de>:
> > Hi,
> >
> > Should I use the amd64 kernel (9pc64) vs the 386 kernel (9pc) on a
> machine with 2G RAM?
> >
> > TIA
> > --
> > Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
> >
>
> Shouldn't matter. 386 has marginally more hardware
> support, but if your hardware is supported, both
> should work (and if it's not supported on amd64,
> please complain!)
>
>
amd64 or i386 usage with respect to bit size ( 64 bits versus 32 bits )
depends not on memory size but  CPU kind / model .

Please , first check your CPU for supported bit size .


Memory for i386 is important when size of memory is greater than 4
Gigabytes
( as maximum supported memory size )

(

Consider

https://en.wikipedia.org/wiki/Physical_Address_Extension
Physical Address Extension

) .

For amd64 , memory size is not important ,  BUT  placement of memory chips
on your main board is  VERY important ( even for i386 ) .
Please also check memory placement rules of your main board
with respect to your memory chips .


With my best wishes for all ,


Mehmet Erol Sanliturk

[-- Attachment #2: Type: text/html, Size: 4721 bytes --]

  reply	other threads:[~2022-02-05  1:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 19:48 Alexander Shendi
2022-02-04 20:50 ` Amavect
2022-02-04 21:03 ` ori
2022-02-04 21:28   ` Mehmet Erol Sanliturk [this message]
2022-02-04 22:52   ` Alexander Shendi
2022-02-04 21:16 ` sirjofri
2022-02-05 17:41 ` Stanley Lieber
2022-02-05 21:11   ` Alexander Shendi
2022-02-05 23:12     ` Kurt H Maier

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=CAOgwaMvfPJx-stwyOKKi+vowpHkMKFq5CD3VxXgAtapU5Nfe8Q@mail.gmail.com \
    --to=m.e.sanliturk@gmail.com \
    --cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).