View previous topic :: View next topic |
Author |
Message |
brendlefly62 Tux's lil' helper
Joined: 19 Dec 2009 Posts: 133
|
Posted: Wed Jun 06, 2018 2:48 pm Post subject: Rpi3(32) "VCHI initialization failed" after knl-up |
|
|
I've been successfully running kernel 4.9.77-v+ on Raspberry Pi 3 (32), and I've been using "vcgencmd" without problems.
Now, running the same commands after upgrading to kernel 4.14.44, I'm getting "VCHI initialization failed"
Based on one article, I checked for but know it's not a user/group permission thing - I'm running the command as root user, in the video group
Based on another article, I suspected mismatch between the new kernel, the vc libraries, etc. However, I recompiled media-libs/raspberrypi-userland after the kernel upgrade -- no change
help?
Last edited by brendlefly62 on Thu Jul 05, 2018 2:08 am; edited 1 time in total |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54119 Location: 56N 3W
|
Posted: Wed Jun 06, 2018 6:28 pm Post subject: |
|
|
brendlefly62,
Look in dmesg for the CMA allocation.
It must be on a 256MB boundary. At one time it was at 512MB but that fails and VHCI initialization fails with it.
Code: | dmesg | grep -i cma
[ 0.000000] cma: Reserved 256 MiB at 0x0000000010000000
[ 0.000000] Kernel command line: 8250.nr_uarts=0 cma=256M bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 dwc_otg.lpm_enable=0 console=tty root=/dev/sda1 cma=256M@256M rootfstype=ext4 rootwait |
_________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
brendlefly62 Tux's lil' helper
Joined: 19 Dec 2009 Posts: 133
|
Posted: Thu Jun 07, 2018 4:26 am Post subject: |
|
|
Thanks, Neddy. Just tried that; still getting VCHI initialization failed
I put cma=256M@256M at the end of the line in cmdline.txt, and I get
Code: | dmesg | grep -i cma
[ 0.000000] cma: Reserved 256 MiB at 0x10000000
[ 0.000000] Kernel command line: bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 dma.dmachans=0x7f35 bcm2709.boardrev=0x2a22082 bcm2709.serial=0xf68e19f7 bcm2709.uart_clock=48000000 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 dwc_otg.lpm_enable=0 console=ttyS0,115200 kgdboc=ttyS0,115200 console=tty1 root=/dev/mmcblk0p3 rootfstype=ext4 elevator=deadline rootwait net.ifnames=0 cma=256M@256M
[ 0.000000] Memory: 732148K/1021952K available (11264K kernel code, 1167K rwdata, 3292K rodata, 1024K init, 372K bss, 27660K reserved, 262144K cma-reserved, 235520K highmem)
|
|
|
Back to top |
|
|
brendlefly62 Tux's lil' helper
Joined: 19 Dec 2009 Posts: 133
|
Posted: Thu Jul 05, 2018 2:06 am Post subject: |
|
|
just circling back to close this out -- turned out problem was not just the cma=256M@256M (which was relevant), but also a corrupted kernel configuration -- no idea how it got that way, I simply started over and built a new kernel, added "cma=256M@256M" to the cmdline.txt, and this problem cleared |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|