There are two issues here - the first error sh: /sys/bus/i2c/drivers/eeprom/unbind: No such file or directory seems to be caused by a missing kernel module, probably one of the CONFIG_EEPROM_* modules but im not sure which one.

Unfortunately, adding these modules in doesnt seem to fix the main issue, which is the failure to read the eeprom system info. Here is what we know:

This info (EEPROM) can be read in ONIE with the onie-syseeprom command, although this doesnt tell us too much as this functionality is patched into busybox by onie
The problem could be related to the different kernel configs on the two images but it is hard to compare as they are significantly different versions of the kernel and very different configs.
It was noted that onlps is able to access and print all of the information other than the system eeprom info suggesting that it is only access to this eeprom that is missing
the hardware setup of this machine (how this eeprom is actually connected) seems to be very hard to get and is making it difficult to figure out how the system should be configured
the issue could be in the platform code which is inherited from onl/onlp
ths system startup makes a number writes to i2c in order to setup a mux - but, again, without documentation it is very unclear how the thing should be setup

This is just a brain dump after half a day of debugging - hopefully @CommitThis can add anything i have missed above or any other observations about the issue..

Uh oh!

APS Networks 100G ONLP has issues to be resolved. #16

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions