Bug 9588 - Smart Battery not recognized by sbs module
Summary: Smart Battery not recognized by sbs module
Status: CLOSED DUPLICATE of bug 9137
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Battery (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: acpi_power-battery
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-17 13:21 UTC by Bill Gribble
Modified: 2008-01-12 16:10 UTC (History)
0 users

See Also:
Kernel Version: 2.6.24-rc5
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Bill Gribble 2007-12-17 13:21:41 UTC
Distribution: debian unstable
Hardware Environment: Raon Digital Everun (AMD Geode UMPC)
Software Environment: 
Problem Description: Smart Battery not recognized by driver, even though i2c tools show it to be there 

Sensors-detect detects a Smart Battery, and i2cdetect shows why: 

# i2cdetect -y 0 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- 0b -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         

I believe that the device at 0x0b is a smart battery because (1) the 
manufacturer told me the device had a smart battery on SMBus, (2) I can dump
its contents and watch values within the register change in ways that make it really look like a battery.  In particular, the stuff at 0x0c-0c0f looks
like battery voltage or charge level (not sure of the scale)... it goes 
up when AC plugged in, down when discharging the battery.  0x2f looks like
it represents the AC adapter state somehow; it takes different values when
the AC is plugged in or not.

# i2cdump -y 0 0x0b
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 e6 0a 01 00 ff ff 01 fd 5b 04 04 02 62 44 18    .???...??[???bD?
10: 40 ff ff 58 00 38 a7 1b fc 5c 31 fb 08 XX XX XX    @..X.8???\1??XXX
20: 0b 07 04 0d XX XX XX XX XX XX XX XX XX XX XX b0    ????XXXXXXXXXXX?
30: XX XX XX XX XX XX XX XX XX XX XX XX 00 1d 22 1d    XXXXXXXXXXXX.?"?
40: XX XX XX XX XX de XX XX XX XX XX XX XX XX XX XX    XXXXX?XXXXXXXXXX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
80: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
90: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX

However, I can load the sbs and sbshc drivers and nothing happens (no battery information in /sys/ or /proc/ ACPI trees, only an AC adapter which claims to be always on, which is what my DSDT tells ACPI to say... see http://bugzilla.kernel.org/show_bug.cgi?id=9137)

Any help appreciated!
Comment 1 Fu Michael 2007-12-26 00:35:49 UTC

*** This bug has been marked as a duplicate of bug 9137 ***

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