# Issue on Legato for Raspberry Pi 3

**URL:** <https://forum.legato.io/t/issue-on-legato-for-raspberry-pi-3/3353>\
**Category:** Legato Application Framework\
**Created:** [June 20, 2018, 11:19am UTC](https://forum.legato.io/t/issue-on-legato-for-raspberry-pi-3/3353 "2018-06-20T11:19:53Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aleix96](https://avatars.discourse-cdn.com/v4/letter/a/f0a364/32.png) [@Aleix96](https://forum.legato.io/u/Aleix96)\
**Post date:** [June 20, 2018, 11:19am UTC](https://forum.legato.io/t/issue-on-legato-for-raspberry-pi-3/3353/1 "2018-06-20T11:19:53Z")

</div>

Hi, I am trying to run legato on a Raspberry Pi 3, and I have followed this guide [Configure Raspberry Pi - Legato Docs](https://docs.legato.io/latest/raspbianMain.html) . The thing is that when I start legato, everything seems to work fine until I get the warning: Timed out after waiting 5000ms for indication from child. And then the critical error: Supervisor was killed by a signal 14.

I attach the syslog from the raspberry pi for more details.

 ![legato_log2](https://us1.discourse-cdn.com/flex019/uploads/legato1/original/1X/448c58571ee415f27ac296965456d12adf8c47d6.png)

---

<div class="post-metadata">

**Author:** ![Aleix96](https://avatars.discourse-cdn.com/v4/letter/a/f0a364/32.png) [@Aleix96](https://forum.legato.io/u/Aleix96)\
**Post date:** [June 20, 2018, 11:21am UTC](https://forum.legato.io/t/issue-on-legato-for-raspberry-pi-3/3353/2 "2018-06-20T11:21:38Z")

</div>

I attach the previous log part here because I can only upload one image per post.

 ![legato_log1](https://us1.discourse-cdn.com/flex019/uploads/legato1/original/1X/f30b6cf30e5d8a87bc4c5891548b3e030cc95c16.png)

---

<div class="post-metadata">

**Author:** ![CoRfr](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/corfr/32/69_2.png) [@CoRfr](https://forum.legato.io/u/CoRfr)\
**Post date:** [June 20, 2018, 2:57pm UTC](https://forum.legato.io/t/issue-on-legato-for-raspberry-pi-3/3353/3 "2018-06-20T14:57:34Z")

</div>

Can you try to build with SMACK disabled? `SMACK_DISABLED=1 make raspi` I think.

Im thinking that Legato has some SMACK issues with kernels above 4.4 and this could lead to the issue that you’re facing.

---

<div class="post-metadata">

**Author:** ![Aleix96](https://avatars.discourse-cdn.com/v4/letter/a/f0a364/32.png) [@Aleix96](https://forum.legato.io/u/Aleix96)\
**Post date:** [June 20, 2018, 9:52pm UTC](https://forum.legato.io/t/issue-on-legato-for-raspberry-pi-3/3353/4 "2018-06-20T21:52:25Z")

</div>

I tried:

SMACK\_DISABLED=1

make raspi

And again, legato starts, I can check the legato version but then I get the same error. ☹

Do you mean that if I use an older Raspbian version it may work?

Thank you

---

<div class="post-metadata">

**Author:** ![CoRfr](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/corfr/32/69_2.png) [@CoRfr](https://forum.legato.io/u/CoRfr)\
**Post date:** [June 20, 2018, 10:22pm UTC](https://forum.legato.io/t/issue-on-legato-for-raspberry-pi-3/3353/5 "2018-06-20T22:22:15Z")

</div>

So did you see any change between the 2?

Otherwise you need to do `export SMACK_DISABLED=1` before `make wp76xx` if it’s on 2 lines.

---

<div class="post-metadata">

**Author:** ![Aleix96](https://avatars.discourse-cdn.com/v4/letter/a/f0a364/32.png) [@Aleix96](https://forum.legato.io/u/Aleix96)\
**Post date:** [June 21, 2018, 8:07am UTC](https://forum.legato.io/t/issue-on-legato-for-raspberry-pi-3/3353/6 "2018-06-21T08:07:52Z")

</div>

Where should I notice changes?  
I tried both (same line and also using export) and the error persists there. I am thinking of using an older raspbian version and see if it works.

---

<div class="post-metadata">

**Author:** ![CoRfr](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/corfr/32/69_2.png) [@CoRfr](https://forum.legato.io/u/CoRfr)\
**Post date:** [June 21, 2018, 4:23pm UTC](https://forum.legato.io/t/issue-on-legato-for-raspberry-pi-3/3353/7 "2018-06-21T16:23:01Z")

</div>

The timed out part makes me think that there is some IPC issue.  
I was hoping that disabling SMACK would help, but maybe not 😕
