Hugo Vanwoerkom wrote:
Aioanei Rares wrote:
On 04/16/2010 02:33 AM, Eduardo M KALINOWSKI wrote:
On 04/15/2010 07:59 PM, Stan Hoeppner wrote:
Aioanei Rares put forth on 4/15/2010 3:16 PM:
No, it means that 2 one-gig modules in same-coloured slots will
theoretically work better. I have one mod
Lisi put forth on 4/17/2010 10:04 AM:
> Would I be correct in taking this to mean that the memory modules appear to
> be incorrectly installed, and that I could improve my memory performance by
> moving one of the modules that dual channel functions? And also, if that
No, they are currently
On Saturday 17 April 2010 05:35:45 Nick Boyce wrote:
> On 17/04/2010 01:03, Stan Hoeppner wrote:
> > Camaleón put forth on 4/16/2010 8:31 AM:
> >> It can be worst, though. There are manufacturers that paint all the RAM
> >> slots in black or using the same color and so forcing us to read the
> >> m
Nick Boyce put forth on 4/16/2010 11:35 PM:
> My current rig - Abit NF7-S V2 mobo (Nforce 2 chipset) and Athlon XP CPU
> - has 3 DIMM slots all the same fetching shade of blue. I initially
> added two 256Mb sticks in slots 1 & 2, and got dual channel operation
> (the BIOS reports it at boot time
On 17/04/2010 01:03, Stan Hoeppner wrote:
> Camaleón put forth on 4/16/2010 8:31 AM:
>
>> It can be worst, though. There are manufacturers that paint all the RAM
>> slots in black or using the same color and so forcing us to read the
>> manual >:-)
>
> The manufacturers have bastardized the col
Camaleón put forth on 4/16/2010 8:31 AM:
> It can be worst, though. There are manufacturers that paint all the RAM
> slots in black or using the same color and so forcing us to read the
> manual >:-)
The manufacturers have bastardized the color coding to the point it's
useless; thus reading the
Aioanei Rares wrote:
On 04/16/2010 02:33 AM, Eduardo M KALINOWSKI wrote:
On 04/15/2010 07:59 PM, Stan Hoeppner wrote:
Aioanei Rares put forth on 4/15/2010 3:16 PM:
No, it means that 2 one-gig modules in same-coloured slots will
theoretically work better. I have one module in a dual-channel mo
On Fri, 16 Apr 2010 16:06:54 +0300, Aioanei Rares wrote:
> On 04/16/2010 04:31 AM, Stan Hoeppner wrote:
(...)
>> Now, go look at the DIMM socket colors and layout pattern on the Intel,
>> Asus, and yes, other Gigabyte boards to see what the proper color
>> coding for dual channel memory sockets
On 04/16/2010 04:31 AM, Stan Hoeppner wrote:
Aioanei Rares put forth on 4/15/2010 7:06 PM:
Are you guys displaced Ubuntu users who landed on debian-user after a
tornado came through Kansas? ;)
I guess you've never seen "The Wizard of Oz".
You made me dig my latest mobo's man
Aioanei Rares put forth on 4/15/2010 7:06 PM:
>> Are you guys displaced Ubuntu users who landed on debian-user after a
>> tornado came through Kansas? ;)
I guess you've never seen "The Wizard of Oz".
> You made me dig my latest mobo's manual :) [Gigabyte GA-M56S-S3], which
> says plainly : "The
On 04/16/2010 01:59 AM, Stan Hoeppner wrote:
Aioanei Rares put forth on 4/15/2010 3:16 PM:
No, it means that 2 one-gig modules in same-coloured slots will
theoretically work better. I have one module in a dual-channel mobo and
it works ok. Most desktop/workstation mobos do.
No, that'
On 04/16/2010 02:33 AM, Eduardo M KALINOWSKI wrote:
On 04/15/2010 07:59 PM, Stan Hoeppner wrote:
Aioanei Rares put forth on 4/15/2010 3:16 PM:
No, it means that 2 one-gig modules in same-coloured slots will
theoretically work better. I have one module in a dual-channel mobo and
it works ok. Mo
On 04/15/2010 07:59 PM, Stan Hoeppner wrote:
Aioanei Rares put forth on 4/15/2010 3:16 PM:
No, it means that 2 one-gig modules in same-coloured slots will
theoretically work better. I have one module in a dual-channel mobo and
it works ok. Most desktop/workstation mobos do.
No, that'
Aioanei Rares put forth on 4/15/2010 3:16 PM:
> No, it means that 2 one-gig modules in same-coloured slots will
> theoretically work better. I have one module in a dual-channel mobo and
> it works ok. Most desktop/workstation mobos do.
No, that's not correct. If the mobo DIMM slots are colored,
Hugo Vanwoerkom put forth on 4/15/2010 3:09 PM:
> Hi,
>
> The Wiki on dual channel memory says:
>
> "The memory modules are installed into matching banks, which are usually
> color coded on the motherboard. These separate channels allow each
> memory module access to the memory controller, increa
On Thu, 15 Apr 2010 15:47:52 -0500, Ron Johnson wrote:
> On 2010-04-15 15:38, Camaleón wrote: [snip]
>>
>> I always try to fill the RAM slots of the board at their maximum
>> capacity (at least 2 GiB.) so upgrading memory will be worth for it.
>>
>>
> That's a bit garbled... Did you forget a w
On 2010-04-15 15:38, Camaleón wrote:
[snip]
I always try to fill the RAM slots of the board at their maximum capacity
(at least 2 GiB.) so upgrading memory will be worth for it.
That's a bit garbled... Did you forget a word somewhere?
--
Dissent is patriotic, remember?
--
To UNSUBSCRIBE
On Thu, 15 Apr 2010 15:09:08 -0500, Hugo Vanwoerkom wrote:
> The Wiki on dual channel memory says:
>
> "The memory modules are installed into matching banks, which are usually
> color coded on the motherboard. These separate channels allow each
> memory module access to the memory controller, inc
On 04/15/2010 11:09 PM, Hugo Vanwoerkom wrote:
Hi,
The Wiki on dual channel memory says:
"The memory modules are installed into matching banks, which are
usually color coded on the motherboard. These separate channels allow
each memory module access to the memory controller, increasing
throu
On Thu, Apr 15, 2010 at 1:09 PM, Hugo Vanwoerkom wrote:
> Does that mean that placing 2 1GB modules, each into a different colored
> slot, is faster than putting 1 2GB module into one slot and leaving the
> other 3 slots empty?
on my server board the machine will not even boot up if memory is no
Hi,
The Wiki on dual channel memory says:
"The memory modules are installed into matching banks, which are usually
color coded on the motherboard. These separate channels allow each
memory module access to the memory controller, increasing throughput
bandwidth."
Does that mean that placing
>
>
>
> Original Message
>From: [EMAIL PROTECTED]
>To: debian-user@lists.debian.org
>Subject: Re: memory question (hardware)
>Date: Sat, 5 Jul 2008 16:27:07 -0400
>
>>Latency, risk of failure, sure... also sheer design complexity
>(since you have
>
On Sat, 5 Jul 2008 16:27:07 -0400
"Jeff Soules" <[EMAIL PROTECTED]> wrote:
Hello Jeff,
> to solve the geometry of fitting more circuitry in the same space),
True, but for memory that's easier than for, say, a CPU. Mainly
because there's a *lot* of repetition in RAM chips. As a result, a
fair b
:04 AM, <[EMAIL PROTECTED]> wrote:
> >>
> >> >
> >> >
> >> >
> >> > Original Message
> >> >From: [EMAIL PROTECTED]
> >> >To: debian-user@lists.debian.org
> >> >Subject: RE: memory question (ha
Any thing else?
>
>
>
> On Fri, Jul 4, 2008 at 11:04 AM, <[EMAIL PROTECTED]> wrote:
>>
>> >
>> >
>> >
>> > Original Message
>> >From: [EMAIL PROTECTED]
>> >To: debian-user@lists.debian.org
>> >S
t; >
> > Original Message
> >From: [EMAIL PROTECTED]
> >To: debian-user@lists.debian.org
> >Subject: RE: memory question (hardware)
> >Date: Thu, 3 Jul 2008 01:08:10 -0400
> >
> >>I am curious...
> >>
> >>
> >>When m
>
>
>
> Original Message
>From: [EMAIL PROTECTED]
>To: debian-user@lists.debian.org
>Subject: RE: memory question (hardware)
>Date: Thu, 3 Jul 2008 01:08:10 -0400
>
>>I am curious...
>>
>>
>>When memory is manufactured why does a stick of
On Wed, 02 Jul 2008 22:14:01 -0700
Paul Johnson <[EMAIL PROTECTED]> wrote:
Hello Paul,
> Smaller die size means higher price. You're squeezing twice as many
> circuits into the same real estate.
As a result, failure rate will be higher too, since greater density
leads to greater risk of error.
On Thu, 2008-07-03 at 01:08 -0400, Mag Gam wrote:
> When memory is manufactured why does a stick of 4GB memory cost 2.5
> times of 2GB memory? Is the manufacturing process that much different
> to justify the cost?
Smaller die size means higher price. You're squeezing twice as many
circuits int
I am curious...
When memory is manufactured why does a stick of 4GB memory cost 2.5 times of
2GB memory? Is the manufacturing process that much different to justify the
cost?
Joe Hart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tyler Smith wrote:
On 2007-02-13, Joe Hart <[EMAIL PROTECTED]> wrote:
Here's my question. Why do the two different versions report different
a different amount of memory? The 32 bit version says I have a total of
886MB, where the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tyler Smith wrote:
> On 2007-02-13, Joe Hart <[EMAIL PROTECTED]> wrote:
>> Here's my question. Why do the two different versions report different
>> a different amount of memory? The 32 bit version says I have a total of
>> 886MB, where the 64-bit ve
On 2007-02-13, Joe Hart <[EMAIL PROTECTED]> wrote:
>
> Here's my question. Why do the two different versions report different
> a different amount of memory? The 32 bit version says I have a total of
> 886MB, where the 64-bit version says there is 1024MB.
>
I came across this recently when I upg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just for kicks I surfed to http://www.goodbye-windows.com and downloaded
the Debian installer for Windows. I already had Etch on this computer,
but went ahead and ran the installer just to see what it would do.
When I had installed Etch the first tim
I'm not very familiar with gtop, but top gives you the data right at
the top of its output (if display of memory information is enabled).
It tells you how much of your memory and swap is in use and how much
is used in buffers and caching.
You can also get all of this information (the Right Way) fr
On Tue, Jul 03, 2001 at 01:13:59PM +0200, Joerg Johannes wrote:
> I've got 512MB of RAM, and I wanted to see how much of it is free. So I
> ran gtop, which showed me that ~84MB are used (mainly X and apache-ssl).
> OK so far, but cat /proc/meminfo tells me that ~480MB are in use, and
> only 32MB fr
Hello List
I've got 512MB of RAM, and I wanted to see how much of it is free. So I
ran gtop, which showed me that ~84MB are used (mainly X and apache-ssl).
OK so far, but cat /proc/meminfo tells me that ~480MB are in use, and
only 32MB free. So, which of both is right, and who is eating that much
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
> > 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
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
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
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
Bill wrote:
>
> Hi all,
> Can anyone tell me if there is a command that lets
> you know how much memory is used and or left available. If
> so what is it??
>
> Regards and thanks in advance
> Bill
>
"free" will do it for you. If you append it with "-m" (free -m) it
will show megabytes
Hi all,
Can anyone tell me if there is a command that lets
you know how much memory is used and or left available. If
so what is it??
Regards and thanks in advance
Bill
[EMAIL PROTECTED]
*
The Mind is like a parachute;
44 matches
Mail list logo
