barish Posted February 7, 2019 Posted February 7, 2019 I did the following upgrades this morning libcurl3:armhf (7.52.1-5+deb9u8, 7.52.1-5+deb9u9), libgd3:armhf (2.2.4-2+deb9u3, 2.2.4-2+deb9u4), armbian-config:armhf (5.72, 5.74), linux-headers-next-sunxi:armhf (5.70, 5.73), linux-image-next-sunxi:armhf (5.70, 5.73), curl:armhf (7.52.1-5+deb9u8, 7.52.1-5+deb9u9), libcurl3-gnutls:armhf (7.52.1-5+deb9u8, 7.52.1-5+deb9u9), linux-dtb-next-sunxi:armhf (5.70, 5.73), base-files:armhf (9.9+deb9u6, 9.9+deb9u7) and found my I2C bus not working anymore. I did a scan on the 4 buses (Olinuxino Micro A20) and found a device on i2c-1 instead of i2c-0, changed my settings and all worked again, so I guess one of the updates must have changed the labeling of the busses? Is this by accident or on purpuse?
Igor Posted February 7, 2019 Posted February 7, 2019 2 minutes ago, barish said: Is this by accident or on purpuse? Most likely settings were changed upstream since I don't recall seeing anyone around Armbian fiddling around this. 1
martinayotte Posted February 7, 2019 Posted February 7, 2019 13 minutes ago, barish said: found a device on i2c-1 instead of i2c-0 If you do a "i2cdetect -l", you will probably see that i2c-0 is dedicated to "sun4i_hdmi_i2c adapter", which maybe wasn't present before ... 2
barish Posted February 8, 2019 Author Posted February 8, 2019 19 hours ago, martinayotte said: If you do a "i2cdetect -l", you will probably see that i2c-0 is dedicated to "sun4i_hdmi_i2c adapter", which maybe wasn't present before ... This is indeed the case. Thanks for this information, the change must have crept in lately. If I had the energy I could find out which of the i2c adapters on the Olinuxino were labeled as "hdmi", but right now, since I don't need to know, I won't...
Recommended Posts