Hi, the bmcsensors port for kernel 2.6 by Yani Ioannou (available on sourceforge, http://bmcsensors-26.sourceforge.net/) looks quite functional now. As also noted by Yani, one thing is really ugly right now: at compile time, bmcsesnors has no idea how many sensors a board provides; this seems to range from ~20 Sesnors for simple boards up to > 60 for a dell 1750. The sysfs interface requires a seperate callback function for read, min, max, label, write min and write max; currently the driver assumes 100 sensors max and just declares callback functions for all of them; while this works ist neither nice code nor especially efficient since most of those functions generaly aren't required. Anyone got an idea how to better handle an unknown number of sensors in the driver? Thanks, Martin