Frequently Asked Questions
The FMC bus does not load the driver because of: EEPROM has no FRU information?
You got this error when the FMC bus is not able to read the mezzanine identifier from the mezzanine eeprom. The main cause of this error is an invalid eeprom content (typically an empty eeprom). You can read the eeprom content with the following commands:
cd /sys/bus/fmc/devices/<device-name>-<device-id>
hexdump eeprom
You can dump the eeprom content to a file with the following commands:
cd /sys/bus/fmc/devices/<device-name>-<device-id>
cat eeprom > /path/to/a/file
The eeprom content validity depends on the FMC mezzanine type so we cannot tell you here if your eeprom is correct or not (for sure, your eeprom is not correct if you find a long serie of 0x00 or 0xFF at offset 0x00 of the eeprom). The IPMI description is at offset 0x0; to understand the eeprom content please read the FRU definition.
If you are able to generate your own eeprom (or just fix a wrong eeprom) you can flash it by doing:
cd /sys/bus/fmc/devices/<device-name>-<device-id>
cat /path/to/your/eeprom/file > eeprom