Closed janbrummer closed 5 years ago
Disabling the driver should do it.
Yeah, right but then i loose disk protection. Not a good deal.
You still have a spinning disk in this machine? As far as I'm concerned, if the hp_accel
driver creates an accelerometer device, then it needs to be consumable by user-space, otherwise it could all be handled internally.
I thought that the main problem with the HP devices were the orientation of the accelerometer.
Try setting ID_INPUT_ACCELEROMETER=0
in a udev rule? See:
https://github.com/systemd/systemd/blob/master/hwdb/60-sensor.hwdb
for details on how
Thanks for your quick response Bastien! I've fixed it by adding another quirk for my system and created a pull request for systemd: https://github.com/systemd/systemd/pull/13453
Therefore this one is obsolete. Thanks.
On a HP EliteBook 850 G3 the hard driver accelerator sensor
lis3lv02d
is accidently used as an input source for iio-sensor-proxy. This causes lots of problems taking this notebook to a meeting in an active state. Screen orientation changes quickly and it looks akwards in a meeting room rotating the whole system to get back to a correct state. Input device is created byhp_accel
module:Glue between LIS3LV02Dx and HP ACPI BIOS and support for disk protection LED.
How can we prevent it from getting used?
The necessary information for the sensor: