# Zkunlockifs segfaults preventing Debian (Raspbian) 12 to boot

**URL:** <https://community.zymbit.com/t/zkunlockifs-segfaults-preventing-debian-raspbian-12-to-boot/1635>\
**Category:** ZYMKEY4\
**Created:** [March 12, 2024, 1:40am UTC](https://community.zymbit.com/t/zkunlockifs-segfaults-preventing-debian-raspbian-12-to-boot/1635 "2024-03-12T01:40:42Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Bob\_of\_Zymbit](https://avatars.discourse-cdn.com/v4/letter/b/82dd89/32.png) [@Bob\_of\_Zymbit](https://community.zymbit.com/u/Bob_of_Zymbit)\
**Post date:** [March 14, 2024, 5:06pm UTC](https://community.zymbit.com/t/zkunlockifs-segfaults-preventing-debian-raspbian-12-to-boot/1635/10 "2024-03-14T17:06:40Z")

</div>

@afunix I think that rule might have covered legacy OSs. I don’t think it is used in bookworm. You are correct in that the names don’t match in bookworm.

My guess is the move to 6.6.20 is still the culprit. Debian/RaspberryPi changed the way GPIO numbering is handled. Another customer ran into this issue. Can you try this?

[https://community.zymbit.com/t/zymkey-doesnt-bind-properly/1633/11?u=bob\_of\_zymbit](https://community.zymbit.com/t/zymkey-doesnt-bind-properly/1633/11)

---

_[View the full topic](https://community.zymbit.com/t/zkunlockifs-segfaults-preventing-debian-raspbian-12-to-boot/1635)._