-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Model B+ wont boot with invalid total_mem value. #782
Comments
Can you test this: https://drive.google.com/uc?id=0B-6zmEDJwxZES1lhRmJhUWZkcmc&export=download The Pi SoC has a 30-bit address space (top 2 bits are used for caching aliases). However recent updates try to put GPU memory that the ARM doesn't need to access in the top page. We have provided a way for vcdbg to get GPU debug info from top page using DMA. As this is still undergoing testing you must enable it manually with total_mem=1024. As Pi0/Pi1 only used half the pages of the MMU anyway, they never had a missing 16M or sdram, so setting total_mem=512 will provide no benefit. |
Yes, That took care of the issue. And thanks for explanation. If I am using this on a headless box, will the extra memory be usable to the normal kernel? |
Yes, you will have 16M of extra usable memory. However you are free to set gpu_mem=64 and you will get 16M extra on the arm side. |
Yes, I was only seeing 4MB extra. Thanks. |
kernel: AudioInjector Octo sound card, updates See: raspberrypi/linux#1921 kernel: Audioinjector Octo : add extra sample rates, fix rst and use bcm270x regs See: raspberrypi/linux#1930 kernel: Driver support for Google voiceHAT soundcard See: raspberrypi/linux#1923 kernel: Add support for Allo Boss DAC add-on board for Raspberry Pi See: raspberrypi/linux#1924 kernel: Add support for Allo Piano DAC 2.1 plus add-on board for Raspberry Pi See: raspberrypi/linux#1925 kernel: BCM270X_DT: Allow multiple instances of w1-gpio overlays kernel: leds-gpio: Remove stray assignment to brightness_set firmware: bootcode: Don't let total_mem exceed sdram size See: #782 firmware: bootcode: Store boot partition number in PM_SPARE firmware: dtoverlay: Change node address when reg is set See: https://www.raspberrypi.org/forums/viewtopic.php?f=107&t=178721
kernel: AudioInjector Octo sound card, updates See: raspberrypi/linux#1921 kernel: Audioinjector Octo : add extra sample rates, fix rst and use bcm270x regs See: raspberrypi/linux#1930 kernel: Driver support for Google voiceHAT soundcard See: raspberrypi/linux#1923 kernel: Add support for Allo Boss DAC add-on board for Raspberry Pi See: raspberrypi/linux#1924 kernel: Add support for Allo Piano DAC 2.1 plus add-on board for Raspberry Pi See: raspberrypi/linux#1925 kernel: BCM270X_DT: Allow multiple instances of w1-gpio overlays kernel: leds-gpio: Remove stray assignment to brightness_set firmware: bootcode: Don't let total_mem exceed sdram size See: raspberrypi/firmware#782 firmware: bootcode: Store boot partition number in PM_SPARE firmware: dtoverlay: Change node address when reg is set See: https://www.raspberrypi.org/forums/viewtopic.php?f=107&t=178721
Fix should be in rpi-update firmware now. Okay to close? |
Did a quick test with the version from github. Everything seems fine. |
…ry from option total_mem=1024 from 4MB to 16MB of extra memory on pi2 and pi3 - Ref raspberrypi/firmware#782
With firmware pulled today (March 25th commit), it appears as issue #717 has cropped back up
A model B+ fails to boot with this setting
[PI1]
total_mem=513
This works, but how to distinguish between 256M and 512M models.
[PI1]
total_mem=512
Does a pi with less than 1024 memory benefit from this setting, or is total_mem=1024 providing extra memory for only rpi2B and rpi3B
The text was updated successfully, but these errors were encountered: