General TC > General TC Talk
[Solved] not seeing all my Memory on 14.x x86
aus9:
Hi Rich
Just been back on TC64 and the key thing to me is
on TC64 dmesg | grep Memory has 6006032/6215008k available
now here is TC32 and my dmesg
--- Code: ---dmesg | grep Memory
Memory: 952388K/985184K available (6664K kernel code, 866K rwdata, 1832K rodata, 732K init, 400K bss, 32796K reserved, 0K cma-reserved, 87196K highmem)
tc@box:~$
--- End code ---
PS I just tried a different web browser and no difference detected so its not a TCE it must be something else
Incidently I have an AMD APU which means my graphics comes from the CPU. In the bios I give it 2G of RAM so I will never see 8G in total
hope that helps
Vaguiner:
--- Quote from: aus9 on August 03, 2023, 08:40:34 PM ---I give it 2G of RAM
--- End quote ---
Hello. I once went through a similar situation. I assume these 2GB are used from the 4GB available to the system, not the remaining 4GB unallocated.
Rich:
Hi aus9
I figured it out.
The following are the ranges of usable addresses for system RAM from dmesg.
I added the spaces to break up the addresses into groups of 4 digits.
--- Code: ---BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000 0000 0000 0000-0x0000 0000 0009 d3ff] usable
BIOS-e820: [mem 0x0000 0000 0010 0000-0x0000 0000 09d8 1fff] usable
BIOS-e820: [mem 0x0000 0000 0a00 0000-0x0000 0000 0a1f ffff] usable
BIOS-e820: [mem 0x0000 0000 0a20 b000-0x0000 0000 0aff ffff] usable
BIOS-e820: [mem 0x0000 0000 0b02 0000-0x0000 0000 3b32 3fff] usable
BIOS-e820: [mem 0x0000 0000 3ddf f000-0x0000 0000 3eff ffff] usable
BIOS-e820: [mem 0x0000 0001 0000 0000-0x0000 0002 3f33 ffff] usable
--- End code ---
The first 6 address ranges add up to approximately 962 Mbytes.
The last address range is approximately 6069 Mbytes (~6 Gbytes).
With 32 bits the highest address you can access is FFFF FFFF.
That last block of RAM uses addresses 1 0000 0000 through 2 3F33 FFFF
and is out of reach for a 32 bit address.
Rich:
Hi aus9
I noticed one other thing:
--- Code: ---Kernel command line: BOOT_IMAGE=/grub/vmlinuz tce=sda4 home=sda4 waitusb=5 nozswap
Unknown kernel command line parameters "nozswap BOOT_IMAGE=/grub/vmlinuz tce=sda4 home=sda4 waitusb=5", will be passed to user space.
--- End code ---
The BOOT_IMAGE=/grub/vmlinuz is probably incorrect. Your boot loader
is passing it to the kernel.
jazzbiker:
--- Quote from: aus9 on August 03, 2023, 07:47:39 PM ---Does that affect any TCE submission?
--- End quote ---
I suppose not. You use 32-bit extensions from x86 repo and any extension buit in Core64 mode will be 32-bit extension. In theory.
In practice I've submitted extensions a few and I did them for both x86 and x86_64 archs on the same machine. I've seen no reclamations concerning 32-bit versions. Probably because nobody use them :-) But I'm using them day by day.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version