October 19, 2016 at 08:15 #10931
I use free command in my Cubox-i4x4 and this is result:
You are authenticated root@geexbox /root$ free total used free shared buffers cached Mem: 1793524 647496 1146028 0 11992 137400 -/+ buffers/cache: 498104 1295420 Swap: 0 0 0
If I got it right system see only 1.8Gb ram instead 4.0Gb..
It is possible to see all 4.0 Gb of ram?October 20, 2016 at 07:11 #10938
You reported that before, but unfortunately I don’t have a 4×4 to test. I know that the memory size detection in u-boot is somewhat flaky. Jon N. changed something a while ago but I heard bad things (i.e. some non-booting units) about this change. So I did not include it. However, I’m also not 100% sure if our kernel config has something to do with this. There is one parameter that looks suspicious… Maybe next week I can build a kernel with that param changed, so that we can rule that out.October 28, 2016 at 07:59 #10944
Some thing like this ?
Basically, the parameter that sets the total available physical memory is "mem=MEMORY_LIMIT". And this is a kernel boot parameter. You need to add, say "mem=1G" for maximum of 1GB available physical memory to the kernel boot parameter. For more info on how to add kernel boot parameters look at https://wiki.ubuntu.com/Kernel/KernelBootParametersOctober 28, 2016 at 09:25 #10945
No, I was thinking about a kernel compile-time configuration. BTW, can you attach a micro USB cable to the console port of your box, open a terminal and abort the boot process by pressing a key during the 3 second countdown. This should get you to an u-boot prompt. Then type:
and post the output here.October 30, 2016 at 21:32 #10958
Could you explain better? I’m a eternal newbye… ^_^
1) attach a micro USB cable to the console port of your box, (I can do it)
2) open a terminal (how I can open a terminal using USB? I know command like ‘telnet
‘ for get a terminal…)
3) abort the boot process by pressing a key during the 3 second countdown. (…)
4) Then type: bdinfo (…)
Thank youOctober 30, 2016 at 21:56 #10959
Ok, man if I did it right, this is what you asked for:
CuBox-i U-Boot > bdinfo arch_number = 0x000012D5 boot_params = 0x10000100 DRAM bank = 0x00000000 -> start = 0x10000000 -> size = 0xF0000000 eth0name = FEC ethaddr = d0:63:b4:00:84:1f current eth = FEC ip_addr = <NULL> baudrate = 115200 bps TLB addr = 0xFFFF0000 relocaddr = 0xFFF70000 reloc off = 0xEF770000 irq_sp = 0xFF76FF38 sp start = 0xFF76FF28 FB base = 0x00000000 CuBox-i U-Boot >
may be?October 30, 2016 at 21:57 #10960
This was a double of previous post. Sorry.
October 30, 2016 at 22:26 #10962
- This reply was modified 1 year, 4 months ago by skelos.
-> size = 0xF0000000
it seems quite good : 4GB
But Rudi is better than me for thisOctober 30, 2016 at 23:01 #10963
please , could you let me know why 0xF0000000 is equal to 4Gb? F is not equal to 16? If you know… if not I wait Rudi.October 30, 2016 at 23:54 #10965
Of course 0xF0000000 is not exactly 4GB. However, iMX6 is a 32bit machine and some address space is required for the SoC’s control registers. Therefore the area above 0xF0000000 is not reported as valid memory. It’s actually present, but cannot be used.
But anyway, the output tells us that u-boot is detecting the memory size correctly. Now the question is why the kernel would not report it. I suspect CONFIG_VMSPLIT_2G…October 31, 2016 at 21:33 #10968
Please let me know if I can do ohter tests for you.December 1, 2016 at 14:24 #11288
Rudi, do you have any news?December 3, 2016 at 13:40 #11292
I’m away for the next two and a half weeks. Maybe Tom can build a new kernel package with CONFIG_VMSPLIT_3G set (and CONFIG_VMSPLIT_2G unset). But be aware that it might not boot at all or fail on 1920×1080 videos…December 4, 2016 at 09:50 #11296
Building it with CONFIG_VMSPLIT_3G set to “y”December 4, 2016 at 10:03 #11297
You can test this kernel : http://download.geexbox.org/cuboxi/linux_imx_3.14-1.0.x-mx6-sr%2b5~27e61f6-5_armv7.opk
You must be logged in to reply to this topic.