0 — Acpi Prp0001
Introduction: The Enigmatic Boot Message If you’ve ever watched the Linux kernel boot with dmesg or journalctl -k , you may have encountered a line that looks something like this:
echo 1 > /sys/bus/acpi/devices/PRP0001:00/unbind 2>/dev/null echo 1 > /sys/bus/acpi/devices/PRP0001:00/bind Watch dmesg for new output. acpi prp0001 0
External (_SB_.I2C0, DeviceObj) Scope (_SB.I2C0) Device (SENS) Name (_HID, "PRP0001") Name (_DSD, Package () ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"), Package () Package () "compatible", "bosch,bme280" , Package () "reg", 0x77 , ) Introduction: The Enigmatic Boot Message If you’ve ever
When you see log lines like:
ls /sys/bus/i2c/devices/
For an I2C device, ensure the I2C controller driver is bound: /dev/null echo 1 >
ls /sys/bus/acpi/devices/PRP0001:00/ -l If the directory doesn’t exist, the ACPI table might be malformed or the device not present.