General TC > General TC Talk

[Solved] not seeing all my Memory on 14.x x86

<< < (5/7) > >>

Rich:
Hi aus9
Seems this has come up before:
https://forum.tinycorelinux.net/index.php/topic,19415.msg120213.html#msg120213

He fixed it in reply #46:

--- Quote from: coreplayer2 on January 14, 2016, 04:48:14 PM --- ... Increased vmalloc to 256MB ...
--- End quote ---

jazzbiker:
Hi Rich,

In the thread You've mentioned vmalloc was hiding not solving. The solution was using Core64 mode on the box with a lot of RAM and lot of GPU RAM. Did I understand right?

@aus9: Are You observing this error in Core64 mode?

Rich:
Hi jazzbiker
From  https://mjmwired.net/kernel/Documentation/kernel-parameters.txt :

--- Code: ---vmalloc=nn[KMG] [KNL,BOOT] Forces the vmalloc area to have an exact
size of <nn>. This can be used to increase the
minimum size (128MB on x86). It can also be used to
decrease the size and leave more room for directly
mapped kernel RAM.
--- End code ---
The way I read it you are setting aside a larger (in this case) contiguous
address space aside for handling memory allocations.


--- Quote from: jazzbiker on August 28, 2023, 01:51:05 AM --- ... The solution was using Core64 mode on the box with a lot of RAM and lot of GPU RAM. Did I understand right? ...
--- End quote ---
Yes, either Core64 or Corepure64. The issue appears to be available address space, not
available RAM. If you look at my reply #7 you'll see where I showed most of the RAM
was mapped out of reach above the 4 Gbyte address range.

aus9:
Hi jazzbiker

--- Quote --- The solution was using Core64 mode on the box with a lot of RAM and lot of GPU RAM. Did I understand right?
@aus9: Are You observing this error in Core64 mode?
--- End quote ---

hmm  thats no help for dumbos like me  ;D

How do I know what is a lot of GPU RAM. If you notice I reduced the motherboard RAM reserved for my APU to give my system more RAM and allegedly more free RAM

I have never seen this in TC64 but I am trying to stay kind of pure Tinycore x86 while compiling.
And personal taste....I do not want to run a 64 bit kernel with 32 bit apps in case my brain gets confused.

If there is a smarter way let me know.

Incidently slightly off topic.....I saw a recent post at
https://www.phoronix.com/

so I am thinking maybe I can build something related to "containers" like snap appimage flatpak etc
not good for compiling against but quite good for those wanting a quick up-to-date software
-negative is built against /usr and no stripping and a fair amount of duplication.

Hi Rich
Altho I mentioned your post 7 and thought that was the explanation to my compile issue.....I can only report what I see.
And what I am now seeing......is that my new setup is allowing me to load quite large make dependencies and still not crash

Rich:
Hi aus9

--- Quote from: aus9 on August 28, 2023, 05:18:42 AM --- ... hmm  thats no help for dumbos like me  ;D ...
--- End quote ---
Let me try explaining it another way:
1. For x86, your CPU can address 4 Gbytes of stuff. It's a 4 lb sack.
2. You have 8 Gbytes of RAM. Lets call that 8 lb of shit.
3. Your peripherals (video, sound, network, disk, etc.) want another
   3 Gbytes of space. That's an additional 3 lb of crap.
 
That takes care of the groundwork.

You can't fit 11 lb of shit and crap into a 4 lb sack.

It's first come first served, therefore:
If your 4 lb sack (x86 CPU) contains 3 lb of crap (peripherals), it can only hold 1 lb of shit (RAM).

Result:
The other 7 lb of shit (RAM) remain unused.

Note: For a metric explanation, replace each occurrence of  lb  with  kg.

Navigation

[0] Message Index

[#] Next page

[*] Previous page