Most, likely, this is caused by bq27x00_battery.ko module loaded during boot - it loads first, then open path for bme. Ho ever, after stopping bme, starting it again result in reboot (to protect device from possible harm, by 2 thing accessing same i2c bus simultaneously. In KP's up to 47, there was a "path" that allowed them to co-exist together, but it was considered possibly harmful for the device. Real risk is disputable, and it depends how things are "protected" - in best case, during such risky situation bq27x00_battery just got "confused", in worst case, it may result in random, dangerous things related to hardware. So, with no doubts, disabling this "path" is improvement (trust me, I was very skeptic about removing it, and dig deep to get info why it's necessary). First of all, you should check '/etc/modprobe.d/blacklist' - it should contain: Code: blacklist bq27x00_battery If this is present, You should check '/etc/modules'. It's possible, that it contains bq27x00_battery entry there - mysteriously, it happened to me, while upgrading to kp49. Modules from this list, are loaded during boot regardless of blacklist entry (thanks to Pali for that info), so you should *remove* it from here. After that, reboot, and Your issue should be fixed. /Estel
blacklist bq27x00_battery