Sicelo writes: >Hi >> Sep 3 18:11:00 valiant iio-sensor-prox[4546]: Not a switch >> [/sys/devices/0020:\ >> 1022:0001.0003/HID-SENSOR-200076.1.auto/iio:device1/../capabilities/sw] >> Sep 3 18:11:00 valiant iio-sensor-prox[4546]: Invalid bitmask entry for >> /sys/d\ >> evices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0f/LNXVIDEO:00/input/input14/e\ >> vent4 >> Sep 3 18:11:00 valiant systemd[1]: iio-sensor-proxy.service: Deactivated >> succe\ >> ssfully.
>This message is actually not indicating a fault and should be ignored. My actual issue is that iio-sensor-proxy is failing to run when I try to start it using systemctl. My notes on the missing path in the initial bug report were just my preliminary efforts to track down why. >> This has worked in the past, I don't know which version (nor which >> kernel version!) suffered the regression. > >What was working exactly? E.g. which sensor(s) if any? Or just that >iio-sensor-proxy ran without the notification above? I was using the acceleration sensor to auto-rotate my screen; the important difference is that iio-sensor-proxy ran. I had no reason to check the logs, so I don't know whether it had the notification. >I might be able to give you some hints. > >BR, >Sicelo A. Mhlongo Any hints would be appreciated! -- Joe Pfeiffer 1440 Tierra del Sol Dr Las Cruces, NM 88007-5548 575.496.3501 (C)
