* [gentoo-amd64] System Memory
@ 2009-12-01 20:54 sean
2009-12-01 22:05 ` Chris Faulkner
2009-12-01 23:46 ` [gentoo-amd64] " Duncan
0 siblings, 2 replies; 17+ messages in thread
From: sean @ 2009-12-01 20:54 UTC (permalink / raw
To: gentoo-amd64
If I am reading this correctly my system here is not seeing all 8GB of
memory, though the system bios does.
cat /proc/meminfo
MemTotal: 5581372 kB
MemFree: 4051424 kB
Buffers: 240436 kB
Cached: 645496 kB
SwapCached: 0 kB
Any reason where to check why all the memory?
Thanks
Sean
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [gentoo-amd64] System Memory
2009-12-01 20:54 [gentoo-amd64] System Memory sean
@ 2009-12-01 22:05 ` Chris Faulkner
2009-12-02 1:26 ` sean
2009-12-01 23:46 ` [gentoo-amd64] " Duncan
1 sibling, 1 reply; 17+ messages in thread
From: Chris Faulkner @ 2009-12-01 22:05 UTC (permalink / raw
To: gentoo-amd64
Do you have 2 or more video cards?
On Tue, Dec 1, 2009 at 2:54 PM, sean <tech.junk@myfairpoint.net> wrote:
> If I am reading this correctly my system here is not seeing all 8GB of
> memory, though the system bios does.
>
> cat /proc/meminfo
>
> MemTotal: 5581372 kB
>
> MemFree: 4051424 kB
>
> Buffers: 240436 kB
>
> Cached: 645496 kB
>
> SwapCached: 0 kB
>
>
>
> Any reason where to check why all the memory?
>
> Thanks
> Sean
>
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* [gentoo-amd64] Re: System Memory
2009-12-01 20:54 [gentoo-amd64] System Memory sean
2009-12-01 22:05 ` Chris Faulkner
@ 2009-12-01 23:46 ` Duncan
2009-12-02 2:14 ` sean
1 sibling, 1 reply; 17+ messages in thread
From: Duncan @ 2009-12-01 23:46 UTC (permalink / raw
To: gentoo-amd64
sean posted on Tue, 01 Dec 2009 15:54:36 -0500 as excerpted:
> If I am reading this correctly my system here is not seeing all 8GB of
> memory, though the system bios does.
>
> cat /proc/meminfo
>
> MemTotal: 5581372 kB
>
> MemFree: 4051424 kB
>
> Buffers: 240436 kB
>
> Cached: 645496 kB
>
> SwapCached: 0 kB
>
>
>
> Any reason where to check why all the memory?
No time to detail ATM, but at least some of it may have to do with the
legacy 32-bit PCI device I/O area at the top of 32-bit memory -- that is,
at the top of the 4 gig address space. That takes a chunk of memory
address space, typically a half gig tho it may be a gig or so (but you
seem to have even more missing than that??) for device io use. If your
bios and the kernel aren't setup properly to leave a hole in the physical
memory address space there, the real memory addresses behind the io
addresses will be masked and that memory not available.
Some BIOSs actually count more memory than one has when this hole is
active, counting "thru" the hole, but displacing the real physical memory
up above 4 gig, so 8 gig may appear as 9 or 10 gig. Others do that, but
then subtract the memory hole, so the total returns to normal. Others
may simply skip that area when detecting memory and not show it at all,
so the memory count appears normal, even tho the hole is there.
But if you don't have that hole configured properly, you WILL lose access
to the real memory behind it.
Gotta run...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [gentoo-amd64] System Memory
2009-12-01 22:05 ` Chris Faulkner
@ 2009-12-02 1:26 ` sean
0 siblings, 0 replies; 17+ messages in thread
From: sean @ 2009-12-02 1:26 UTC (permalink / raw
To: gentoo-amd64
Chris Faulkner wrote:
> Do you have 2 or more video cards?
>
only one video card
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [gentoo-amd64] Re: System Memory
2009-12-01 23:46 ` [gentoo-amd64] " Duncan
@ 2009-12-02 2:14 ` sean
2009-12-02 7:06 ` Duncan
2009-12-02 13:57 ` Nikos Chantziaras
0 siblings, 2 replies; 17+ messages in thread
From: sean @ 2009-12-02 2:14 UTC (permalink / raw
To: gentoo-amd64
Duncan wrote:
>
> But if you don't have that hole configured properly, you WILL lose access
> to the real memory behind it.
>
I forgot to setup for the hole in BIOS.
It looks much better now.
MemTotal: 7649744 kB
MemFree: 6832176 kB
Buffers: 22108 kB
Cached: 299636 kB
SwapCached: 0 kB
Thanks Duncan.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [gentoo-amd64] Re: System Memory
2009-12-02 2:14 ` sean
@ 2009-12-02 7:06 ` Duncan
2009-12-02 8:32 ` Barry Schwartz
2009-12-02 13:57 ` Nikos Chantziaras
1 sibling, 1 reply; 17+ messages in thread
From: Duncan @ 2009-12-02 7:06 UTC (permalink / raw
To: gentoo-amd64
sean posted on Tue, 01 Dec 2009 21:14:28 -0500 as excerpted:
> Duncan wrote:
>>
>> But if you don't have that hole configured properly, you WILL lose
>> access to the real memory behind it.
>>
>>
> I forgot to setup for the hole in BIOS. It looks much better now.
>
> MemTotal: 7649744 kB
> MemFree: 6832176 kB
> Buffers: 22108 kB
> Cached: 299636 kB
> SwapCached: 0 kB
>
> Thanks Duncan.
Indeed. *MUCH* better! =:^)
And I'm glad you got it without me having to do the whole detailed
explanation, too. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [gentoo-amd64] Re: System Memory
2009-12-02 7:06 ` Duncan
@ 2009-12-02 8:32 ` Barry Schwartz
0 siblings, 0 replies; 17+ messages in thread
From: Barry Schwartz @ 2009-12-02 8:32 UTC (permalink / raw
To: gentoo-amd64
Duncan <1i5t5.duncan@cox.net> writes:
> And I'm glad you got it without me having to do the whole detailed
> explanation, too. =:^)
You care about these things so the rest of us don't have to. :)
^ permalink raw reply [flat|nested] 17+ messages in thread
* [gentoo-amd64] Re: System Memory
2009-12-02 2:14 ` sean
2009-12-02 7:06 ` Duncan
@ 2009-12-02 13:57 ` Nikos Chantziaras
2009-12-02 16:28 ` sean
1 sibling, 1 reply; 17+ messages in thread
From: Nikos Chantziaras @ 2009-12-02 13:57 UTC (permalink / raw
To: gentoo-amd64
On 12/02/2009 04:14 AM, sean wrote:
> Duncan wrote:
>>
>> But if you don't have that hole configured properly, you WILL lose access
>> to the real memory behind it.
>>
>
> I forgot to setup for the hole in BIOS.
> It looks much better now.
>
> MemTotal: 7649744 kB
> MemFree: 6832176 kB
> Buffers: 22108 kB
> Cached: 299636 kB
> SwapCached: 0 kB
You're still missing half a GB though. Is this a 32-bit kernel?
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [gentoo-amd64] Re: System Memory
2009-12-02 13:57 ` Nikos Chantziaras
@ 2009-12-02 16:28 ` sean
2009-12-02 18:25 ` Nikos Chantziaras
0 siblings, 1 reply; 17+ messages in thread
From: sean @ 2009-12-02 16:28 UTC (permalink / raw
To: gentoo-amd64
Nikos Chantziaras wrote:
>>
>> MemTotal: 7649744 kB
>> MemFree: 6832176 kB
>> Buffers: 22108 kB
>> Cached: 299636 kB
>> SwapCached: 0 kB
>
> You're still missing half a GB though. Is this a 32-bit kernel?
>
No.
2.6.30-gentoo-r5 #10 SMP Wed Nov 25 16:42:59 EST 2009 x86_64 AMD
Opteron(tm) Processor 246 AuthenticAMD GNU/Linux
^ permalink raw reply [flat|nested] 17+ messages in thread
* [gentoo-amd64] Re: System Memory
2009-12-02 16:28 ` sean
@ 2009-12-02 18:25 ` Nikos Chantziaras
2009-12-03 0:13 ` sean
0 siblings, 1 reply; 17+ messages in thread
From: Nikos Chantziaras @ 2009-12-02 18:25 UTC (permalink / raw
To: gentoo-amd64
On 12/02/2009 06:28 PM, sean wrote:
> Nikos Chantziaras wrote:
>
>>>
>>> MemTotal: 7649744 kB
>>> MemFree: 6832176 kB
>>> Buffers: 22108 kB
>>> Cached: 299636 kB
>>> SwapCached: 0 kB
>>
>> You're still missing half a GB though. Is this a 32-bit kernel?
>>
>
> No.
> 2.6.30-gentoo-r5 #10 SMP Wed Nov 25 16:42:59 EST 2009 x86_64 AMD
> Opteron(tm) Processor 246 AuthenticAMD GNU/Linux
If this isn't due to a graphics card using system RAM instead of GPU RAM
(integrated cards do this), then you might want to look whether a BIOS
update is available which might fix this.
Unless of course you don't mind the missing 0.5GB :)
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [gentoo-amd64] Re: System Memory
2009-12-02 18:25 ` Nikos Chantziaras
@ 2009-12-03 0:13 ` sean
2009-12-03 3:39 ` Duncan
0 siblings, 1 reply; 17+ messages in thread
From: sean @ 2009-12-03 0:13 UTC (permalink / raw
To: gentoo-amd64
Nikos Chantziaras wrote:
>
> If this isn't due to a graphics card using system RAM instead of GPU RAM
> (integrated cards do this), then you might want to look whether a BIOS
> update is available which might fix this.
>
> Unless of course you don't mind the missing 0.5GB :)
>
My video card is not integrated, and I know there are BIOS updates for
my system, I have just not managed to update it.
Thanks, I have been meaning to look into it.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [gentoo-amd64] Re: System Memory
2009-12-03 0:13 ` sean
@ 2009-12-03 3:39 ` Duncan
2009-12-03 9:21 ` Raffaele BELARDI
0 siblings, 1 reply; 17+ messages in thread
From: Duncan @ 2009-12-03 3:39 UTC (permalink / raw
To: gentoo-amd64
sean posted on Wed, 02 Dec 2009 19:13:17 -0500 as excerpted:
> My video card is not integrated, and I know there are BIOS updates for
> my system, I have just not managed to update it.
Just be careful... I managed to fry my BIOS while updating it (due to a
memory stick going bad, thus writing garbage to the flash), a couple
months ago. Had I known the recovery procedure when it happened, I might
have been able to recover it, but due to lack of knowledge, I screwed
that up too.
I ended up on my netbook, ordering a newly flashed BIOS chip for my main
machine over the net from California.... Suffice it to say that I now
know WAYYY more than I ever wanted to know, about recovering from a bad
BIOS flash.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [gentoo-amd64] Re: System Memory
2009-12-03 3:39 ` Duncan
@ 2009-12-03 9:21 ` Raffaele BELARDI
2009-12-03 21:03 ` sean
2009-12-03 22:17 ` Duncan
0 siblings, 2 replies; 17+ messages in thread
From: Raffaele BELARDI @ 2009-12-03 9:21 UTC (permalink / raw
To: gentoo-amd64
Duncan wrote:
> sean posted on Wed, 02 Dec 2009 19:13:17 -0500 as excerpted:
>
>> My video card is not integrated, and I know there are BIOS updates for
>> my system, I have just not managed to update it.
>
> Just be careful... I managed to fry my BIOS while updating it (due to a
> memory stick going bad, thus writing garbage to the flash), a couple
> months ago. Had I known the recovery procedure when it happened, I might
> have been able to recover it, but due to lack of knowledge, I screwed
> that up too.
>
> I ended up on my netbook, ordering a newly flashed BIOS chip for my main
> machine over the net from California.... Suffice it to say that I now
> know WAYYY more than I ever wanted to know, about recovering from a bad
> BIOS flash.
>
Same here, I had to order a new flash chip when it happened to me. The
recovery procedure you mention is specific to your motherboard model?
raffaele
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [gentoo-amd64] Re: System Memory
2009-12-03 9:21 ` Raffaele BELARDI
@ 2009-12-03 21:03 ` sean
2009-12-03 22:17 ` Duncan
1 sibling, 0 replies; 17+ messages in thread
From: sean @ 2009-12-03 21:03 UTC (permalink / raw
To: gentoo-amd64
Raffaele BELARDI wrote:
>> Just be careful... I managed to fry my BIOS while updating it (due to a
>> memory stick going bad, thus writing garbage to the flash), a couple
>> months ago. Had I known the recovery procedure when it happened, I might
>> have been able to recover it, but due to lack of knowledge, I screwed
>> that up too.
>>
>> I ended up on my netbook, ordering a newly flashed BIOS chip for my main
>> machine over the net from California.... Suffice it to say that I now
>> know WAYYY more than I ever wanted to know, about recovering from a bad
>> BIOS flash.
>>
>
> Same here, I had to order a new flash chip when it happened to me. The
> recovery procedure you mention is specific to your motherboard model?
>
> raffaele
>
>
For the reason that both of you mention, in the past I have always
purchased the BIOS chip upgrade for any system I want to make sure will
not be the victim of a meltdown.
Which is why I have not upgraded this system yet again to the latest.
^ permalink raw reply [flat|nested] 17+ messages in thread
* [gentoo-amd64] Re: System Memory
2009-12-03 9:21 ` Raffaele BELARDI
2009-12-03 21:03 ` sean
@ 2009-12-03 22:17 ` Duncan
2009-12-04 8:22 ` Raffaele BELARDI
1 sibling, 1 reply; 17+ messages in thread
From: Duncan @ 2009-12-03 22:17 UTC (permalink / raw
To: gentoo-amd64
Raffaele BELARDI posted on Thu, 03 Dec 2009 10:21:56 +0100 as excerpted:
> Same here, I had to order a new flash chip when it happened to me. The
> recovery procedure you mention is specific to your motherboard model?
No. It's specific to brands of BIOS. Both AMI BIOS (mine) and Award
BIOS have a recovery procedure, tho the other one (IDR the name) and
vendors such as Dell may not.
http://biosman.com/biosrecovery.html
When it first happened, when I'd try to boot it would do a floppy drive
seek, apparently trying to find that AMIBOOT.ROM file as detailed in the
above. But as I didn't know what I was doing, I used the EPROM-clear
pins on the mobo, thinking I had nothing to lose anyway and hoping to
clear the problem, and lost that. By the time I started looking for BIOS
replacement sites (which I had read about before so I knew they existed)
and came across that info, it wasn't doing a floppy seek either, so
ordering a new chip was pretty much my only option.
This board is EOLed, so no more flashes for it, but I'm going to know
what my BIOS is and have a recovery floppy ready the next time I DO do a
flash.
(That's assuming BIOS hasn't been replaced by EFI or something by then, I
think they have their own recovery procedures... FWIW, I just used the
gdisk ebuild available in bugzilla, to build gdisk, and used it to switch
all my disks over to to GPT partitions. I'm ready for > 2TiB disks now,
AND have the extra reliability of checksummed partition tables as well as
no worries about extended partitions, any more. Plus GPT (and gdisk)
allows naming the partitions, which helps quite a bit in managing them.
GPT was designed for EFI, but works quite well with standard BIOS as
well, as long as you follow the rules. Gentoo's grub 0.97-rWHATEVER has
patches that support it, and it's a kernel option, so I was good to go as
soon as I enabled that and rebuilt/reinstalled my kernel, and merged
gdisk using the bugzilla ebuild. =:^)
FWIW, routers and the like, and various firmware based media players,
etc, often have similar recovery procedures. I was familiar with them,
but wasn't aware they had recovery procedures in general computer BIOS as
well.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [gentoo-amd64] Re: System Memory
2009-12-03 22:17 ` Duncan
@ 2009-12-04 8:22 ` Raffaele BELARDI
2009-12-04 16:37 ` Duncan
0 siblings, 1 reply; 17+ messages in thread
From: Raffaele BELARDI @ 2009-12-04 8:22 UTC (permalink / raw
To: gentoo-amd64
Duncan wrote:
> Raffaele BELARDI posted on Thu, 03 Dec 2009 10:21:56 +0100 as excerpted:
>
>> Same here, I had to order a new flash chip when it happened to me. The
>> recovery procedure you mention is specific to your motherboard model?
>
> No. It's specific to brands of BIOS. Both AMI BIOS (mine) and Award
> BIOS have a recovery procedure, tho the other one (IDR the name) and
> vendors such as Dell may not.
>
The other one (mine) is Phoenix. I was about to write that it does not
support recovery, but maybe I'm wrong:
http://www.theeldergeek.com/forum/index.php?showtopic=21209
raf
^ permalink raw reply [flat|nested] 17+ messages in thread
* [gentoo-amd64] Re: System Memory
2009-12-04 8:22 ` Raffaele BELARDI
@ 2009-12-04 16:37 ` Duncan
0 siblings, 0 replies; 17+ messages in thread
From: Duncan @ 2009-12-04 16:37 UTC (permalink / raw
To: gentoo-amd64
Raffaele BELARDI posted on Fri, 04 Dec 2009 09:22:50 +0100 as excerpted:
> Duncan wrote:
>>
>> It's specific to brands of BIOS. Both AMI BIOS (mine) and Award
>> BIOS have a recovery procedure, tho the other one (IDR the name) and
>> vendors such as Dell may not.
>>
> The other one (mine) is Phoenix. I was about to write that it does not
> support recovery, but maybe I'm wrong:
>
> http://www.theeldergeek.com/forum/index.php?showtopic=21209
Thanks. So we know that all three of the big guys have recovery, but
some mfrs turn it off for their BIOS versions, for some reason.
Also, until reading that topic, I didn't know that USB based floppy-
drives would work, but they apparently do at least for PhoenixBIOS. I
still have a "real" floppy connector and drive on my machine.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2009-12-04 18:01 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-01 20:54 [gentoo-amd64] System Memory sean
2009-12-01 22:05 ` Chris Faulkner
2009-12-02 1:26 ` sean
2009-12-01 23:46 ` [gentoo-amd64] " Duncan
2009-12-02 2:14 ` sean
2009-12-02 7:06 ` Duncan
2009-12-02 8:32 ` Barry Schwartz
2009-12-02 13:57 ` Nikos Chantziaras
2009-12-02 16:28 ` sean
2009-12-02 18:25 ` Nikos Chantziaras
2009-12-03 0:13 ` sean
2009-12-03 3:39 ` Duncan
2009-12-03 9:21 ` Raffaele BELARDI
2009-12-03 21:03 ` sean
2009-12-03 22:17 ` Duncan
2009-12-04 8:22 ` Raffaele BELARDI
2009-12-04 16:37 ` Duncan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox