[SOLVED] Slackware on the Raspberry Pi is a Memory Hog?!?
Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I installed Slackware 14.1 on my Raspberry Pi (512 meg RAM) using these instructions. To my surprise the memory footprint of it booting into the CLI is approximately 360 megs (determined using "free"). Even my x86 install on my laptop uses less memory (also a 32 bit 14.1 install). Raspbian and Arch on the same Pi use < 100 megs for a CLI boot. I think of Slackware as a lean, mean computing machine, which is why this surprised me.
So why is it this much of a memory hog? Inefficient distribution of RAM to the Framebuffer/GPU? Daemons starting at boot? If that is the case why is my x86 utilizing less memory?
On a side note, is the kernel for Slackware compiled for a hard or soft float?
I love Slackware immensely and will continue to use it on the Raspberry Pi, I am just curious.
Seems it will run on the PI but is not optimized for it. I tried a minimal install and had all kinds of problems until I started over with a full install. I got mine running fine but started stressing it and eventually it went in the weeds for a few hours and I killed power when I got home and that corrupted the drive so I need to install again.
I installed Slackware 14.1 on my Raspberry Pi (512 meg RAM) using these instructions. To my surprise the memory footprint of it booting into the CLI is approximately 360 megs (determined using "free"). Even my x86 install on my laptop uses less memory (also a 32 bit 14.1 install). Raspbian and Arch on the same Pi use < 100 megs for a CLI boot. I think of Slackware as a lean, mean computing machine, which is why this surprised me.
So why is it this much of a memory hog? Inefficient distribution of RAM to the Framebuffer/GPU? Daemons starting at boot? If that is the case why is my x86 utilizing less memory?
On a side note, is the kernel for Slackware compiled for a hard or soft float?
I love Slackware immensely and will continue to use it on the Raspberry Pi, I am just curious.
Something is wrong with your setup...
Because I use SlackwareARM 14.1 (also) in a 10" WonderMedia 8650 (ARMv5TE) netbook, sporting just 256MB RAM. Still, my setup having a full install (excluding KDE, KDEI) and it run nice and responsive under X.org, using XFCE4 as DE.
So, I can't claim that Slackware-ARM is a Memory Hog.
Last edited by Darth Vader; 02-10-2014 at 10:20 AM.
Have you checked with top or htop which process is using that much memory? Also, what exactly does free report?
Not yet but I will. The RAM is shared between the GPU and CPU. I wonder if a good chunk is being reserved for the GPU. There are ways to adjust that with the other distros. I am mostly using Slack from the command line and don't need fancy graphics.
Right after boot my Pi has 120Mb used most of which is cache and buffers ... the real usage is less then 20Mb. If I then start X with fluxbox window manager real usage rises to 25Mb.
Unfortunately I'm editing from my AC100 and cut and paste does not work from xterm ... otherwise I'd post the output of free to show the mem usage of my Pi.
I'm just guessing: you have enabled tmpfs in fstab that by default will use 50% of the available ram.
I'm just guessing: you have enabled tmpfs in fstab that by default will use 50% of the available ram.
No, it will not. The 50% default is the limit how much it can use. tmpfs will only use as much RAM as it needs to store the data, if you only have a 1MB file on a tmpfs it will only use 1MB.
That's true but depending on what you do with the tmpfs it can happen that it gets used to something close to the default maximum allowed.
I've seen that happen on my printserver running on a seagate dockstar from readoly filesystem where all the stuff that needs to be written ends up in tmpfs. But it was just a guess with out having the output of free or /proc/meminfo ... ina nay case there is something odd with that system: my Pi is not on right now but I've handy my hedless salvaged tablet with a very similar setup to my Pi (practically the same packages installed and same amount of ram) and here is what it has to say about memory usage
There seems to be confusion about what free reports. The memory actually used by the system for applications can be found in the second row, in your case about 24MB. Have a look here: http://www.linuxatemyram.com/
There seems to be confusion about what free reports. The memory actually used by the system for applications can be found in the second row, in your case about 24MB. Have a look here: http://www.linuxatemyram.com/
Thanks. That makes for interesting reading. Interestingly the man page for free does not make that explicit.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.