Okay, this was unexpected. The cmdline=quiet NEEDS to be there for the
capes to load at boot.
I confirmed your findings in that the other two entries made no
difference, but the quiet option apparently is SIGNIFICANT.
Thanks for your help on this one. Don't even want to guess what's up here.
Moving on now,
Ross
On 11/03/2015 10:58 AM, Robert Nelson wrote:
On Tue, Nov 3, 2015 at 12:50 PM, Ross Morrison <[email protected]> wrote:
Here is my updated uEnv.txt. By ordering the entries like yours and adding
the cmdline= entry, the overlays are now loaded at boot time without error.
===============================
root@bbb-green:~# cat /boot/uEnv.txt
uname_r=4.1.12-bone16
uuid=69951811-ca64-49d9-9e55-49c7c727f449
cmdline=coherent_pool=1M quiet init=/lib/systemd/systemd
dtb=am335x-bonegreen.dtb
cape_enable=bone_capemgr.enable_partno=BB-UART2
root@bbb-green:~#
===============================
Would you think ordering is significant or the one of the coherent_pool or
init entries is the fix?
Not sure either, I disabled each individually,
coherent_pool=1M
This is for some wifi module, with it removed, the cape loads fine..
init=/lib/systemd/systemd
This is for debian wheezy (7.x) to load systemd as init, for debian
(8.x) this isn't needed as systemd is init..
with it removed, the cape loads fine..
Regards,
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
