Bug 798158 - lis3lv02d: unknown sensor type 0x33
Summary: lis3lv02d: unknown sensor type 0x33
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.2
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Dean Nelson
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks: 1269638
TreeView+ depends on / blocked
 
Reported: 2012-02-28 07:49 UTC by Alexander Lindqvist
Modified: 2015-10-08 11:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-08 11:59:22 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Alexander Lindqvist 2012-02-28 07:49:03 UTC
Description of problem:
The accelerometer in this HP Laptop Pavilion dm1-4110eo (and others) is not supported.

Version-Release number of selected component (if applicable):
2.6.32-220.4.1.el6.x86_64 #1 SMP

How reproducible:
Boot computer

Steps to Reproduce:
1. Boot computer
2. View message log or boot messages.
3.
  
Actual results:


Expected results:


Additional info:
From boot:
Feb 27 22:46:59 alex kernel: lis3lv02d: laptop model unknown, using default axes configuration
Feb 27 22:46:59 alex kernel: lis3lv02d: unknown sensor type 0x33
Feb 27 22:46:59 alex kernel: lis3lv02d: probe of HPQ0004:00 failed with error -22
Feb 27 22:46:59 alex kernel: lis3lv02d driver loaded

Comment 2 RHEL Program Management 2012-05-03 05:37:53 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 4 Andy Gospodarek 2013-04-25 20:39:51 UTC
Alexander, if someone was able to give you a test-kernel would you be able to give it a try for us?

Comment 5 Alexander Lindqvist 2013-04-30 06:14:36 UTC
Sadly I don't have that laptop anymore so I can't help with this.


Note You need to log in before you can comment on or make changes to this bug.