gpu_mem doesn't work for me

[riaqn]

Three hours ago I updated the firmware to the latest revision.Actually the "gpu_mem"worked for me before the update.And after the update I rewrite the config.txt:
#echo gpu_mem=16 > /boot/config.txt
I 've tried many value but none of them works.
#cat /proc/meminfo
MemTotal: 448776 kB
MemFree: 405120 kB
It seems that the GPU takes 64MB of memory,as default. I wonder it's a bug or just me?
Sorry for my poor English.

[Shikky]

Same here, I registered so I could create a thread, but then I saw yours.

I can't get neither the gpu_mem nor the gpu_mem_512 to work. The other settings in config.txt work fine (overscan, sdtv_mode, etc). Seems like bootcode.bin doesn't correctly do it's job somehow.

As far as I know, I'm at the latest firmware version (the one from 5 days back). 3.6.11+ kernel.

Generally I would say pick an older version, but bootcode.bin is already a month old, so it should not be a 'new' bug or something (unless its in start.elf).

[DirkS]

Did you check that the text is actually added to config.txt?

You can check it with

Code: Select all

cat /boot/confg.txt

BTW: you will need root privileges to change this file. Also, using a single '>' you will overwrite any other contents of config.txt.

Gr.
Dirk

[Shikky]

A short update from my part:

Tried older firmware (March 4th) using rpi-update, didn't make a difference. Back to the new firmware now, still no change in GPU memory. Although I don't think it's that relevant, I'm using Raspbian, bootstrapped it myself. The RPi has a samsung chip.

I'm baffled. I must be doing something very wrong, but I'm not seeing it. Any help is very much appreciated.

[FTrevorGowen]

Have you tried using raspi-config to do this task?
Whilst that tool normally just runs on the very first boot of a fresh raspbian image it can be rerun later via:
sudo raspi-config

and select the "memory_split" option.
Trev.

[Shikky]

Have you tried using raspi-config to do this task?
Whilst that tool normally just runs on the very first boot of a fresh raspbian image it can be rerun later via:
sudo raspi-config

and select the "memory_split" option.
Trev.

Thanks for your reply. That's how I first got the config.txt. I just tested it again by removing my config.txt and resetting the memory split setting with that script, but /proc/meminfo still shows 448MB of regular memory.

Just for completeness:

Code: Select all

# /opt/vc/bin/vcgencmd version
Mar 19 2013 00:06:03
Copyright (c) 2012 Broadcom
version 377915 (release)

# uname -a
Linux media-pi 3.6.11+ #397 PREEMPT Mon Mar 18 22:17:49 GMT 2013 armv6l GNU/Linux

# cat /boot/config.txt
overscan_left=5
gpu_mem=128

MD5 sums of files in /boot: http://pastebin.com/yxfK4Vxa

[riaqn]

Did you check that the text is actually added to config.txt?

You can check it with

Code: Select all

cat /boot/confg.txt

BTW: you will need root privileges to change this file. Also, using a single '>' you will overwrite any other contents of config.txt.

Gr.
Dirk

Thanks for comments.All options in config.txt is commented out except the gpu_mem.Because I use the rpi as a server, so graphic is no use to me.I 'm root, and it's safe to overwrite the config.txt.

[riaqn]

Have you tried using raspi-config to do this task?
Whilst that tool normally just runs on the very first boot of a fresh raspbian image it can be rerun later via:
sudo raspi-config

and select the "memory_split" option.
Trev.

Actually I'm using archlinux for arm.So there is no script like that.

[riaqn]

Same here, I registered so I could create a thread, but then I saw yours.

I can't get neither the gpu_mem nor the gpu_mem_512 to work. The other settings in config.txt work fine (overscan, sdtv_mode, etc). Seems like bootcode.bin doesn't correctly do it's job somehow.

As far as I know, I'm at the latest firmware version (the one from 5 days back). 3.6.11+ kernel.

Generally I would say pick an older version, but bootcode.bin is already a month old, so it should not be a 'new' bug or something (unless its in start.elf).

Well, I've rewrite the img using windows image writer, update the firmware using "pacman -Syu" instead of "rpi-update".Now everything goes fine with me.I guess the problem is the rpi-update script.
BTW, if I don't need the graphics,how small the gpu_mem can be set to use the memory as little as possible to max the memory used by ARM?
Sorry for my poor English.

[Shikky]

Well, I've rewrite the img using windows image writer, update the firmware using "pacman -Syu" instead of "rpi-update".Now everything goes fine with me.I guess the problem is the rpi-update script.
BTW, if I don't need the graphics,how small the gpu_mem can be set to use the memory as little as possible to max the memory used by ARM?
Sorry for my poor English.

I think 16MB for the GPU is the minimum according to the documentation. That already requires a cut down version of the firmware code, so smaller than that is not possible I guess.

Edit: Well, apparently the problem is indeed with rpi-update. Installation through apt-get worked wonders. That's a nasty bug they have there.

[pluggy]

rpi-update is for cutting edge updates, it's experimental, it breaks stuff. If you want a quiet life, don't use it.