https://bugzilla.kernel.org/show_bug.cgi?id=218578 Hans de Goede (jwrdegoede@xxxxxxxxxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jwrdegoede@xxxxxxxxxxxxxxxx | |g --- Comment #4 from Hans de Goede (jwrdegoede@xxxxxxxxxxxxxxxxx) --- Kirk, Jonathan Cc-ed me on this bug since I've done a lot of work on accelerometers on x86 tablets. I notice you use the word "reboot(ed)" a lot in your last comment. What happens if you power off the tablet and then power it back on again and then directly start the livecd (presumably this is what you did during your first test?). This way the device is fully reset / in a clean hwstate when starting the livecd. Or reboot from a working Windows environment into the livecd ? (maybe Windows does something extra and rebooting keeps that state, combined with the livecd because you have had the accelerometer work there before) As for figuring out which DSDT node is actually the one used on your tablet. Lets first focus on 1 single tablet (of your choosing) and ignore the other tablet for now. On the chosen tablet can you do: ls -l /sys/bus/i2c/devices/ This should show a device for your accelerometer. E.g. "i2c-MXC6655:00" (but maybe something else) please run: cat /sys/bus/i2c/devices/i2c-MXC6655:00/firmware_node/path replacing "i2c-MXC6655:00" with the actual accelerometer i2c-device and then let us know the output. Also please run: sudo acpidump -o acpidump.txt sudo dmesg > dmesg.txt And attach both generated .txt files here. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
