# mangOH Red board rev detected based on EEPROM

**URL:** <https://mangoh.discourse.group/t/mangoh-red-board-rev-detected-based-on-eeprom/2022>\
**Category:** mangOH Red\
**Created:** [October 17, 2018, 5:29pm UTC](https://mangoh.discourse.group/t/mangoh-red-board-rev-detected-based-on-eeprom/2022 "2018-10-17T17:29:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dfrey](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/dfrey/32/303_2.png) [@dfrey](https://mangoh.discourse.group/u/dfrey)\
**Post date:** [October 17, 2018, 5:29pm UTC](https://mangoh.discourse.group/t/mangoh-red-board-rev-detected-based-on-eeprom/2022/1 "2018-10-17T17:29:44Z")

</div>

The mangOH Red contains an EEPROM on the I2C bus. At the time the board is manufactured a string is written in there. I have updated the mangoh\_red.ko kernel module to now attempt to read the contents of the EEPROM in order to determine which board is in use rather than relying on a `revision` module parameter. I put in what I _think_ is the correct string, but I’m concerned that some DV5 boards may not be covered by what I specified. If your board fails detection, you should get a message like this:

```auto
EEPROM contents did not match any known board signature: "[EEPROM Contents]"

```

If you see that message, please reply to this forum post and specify exactly the message that was printed.