https://www.thinkwiki.org/w/api.php?action=feedcontributions&feedformat=atom&user=GmetalThinkWiki - User contributions [en]2026-05-09T03:05:21ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=Talk:Tp_smapi&diff=27848Talk:Tp smapi2007-01-22T11:05:08Z<p>Gmetal: </p>
<hr />
<div>== Feedback ==<br />
<br />
Great, great work! Really! This completely rocks. I just stopped my battery from charging at 77% and restarted charging a bit later, no problems whatsoever. BTW, this is on kernel 2.6.14.3.<br />
<br />
--[[User:Spiney|spiney]] 21:25, 5 Dec 2005 (CET)<br />
----<br />
None of the fuctions is working on my T40, kernel 2.6.14-mm2.<br />
<br />
--[[User:Lammic|lammic]], 2005.12.05<br />
<br />
Works for me on a T41 running 2.6.12-10-686 (Ubuntu 5.10).<br />
<br />
--[[User:berndtnm|berndtnm]], 2005.12.06<br />
<br />
Including stop_charge_thresh? That one seems to be missing on the T42p.<br />
<br />
--[[User:Thinker|Thinker]] 00:46, 7 Dec 2005 (CET)<br />
----<br />
<br />
tp_smapi works just fine on an R52 with Ubuntu Breezy stock kernel.<br />
<br />
--[[User:Micampe|Micampe]] 12:52, 7 Dec 2005 (CET)<br />
<br />
----<br />
<br />
''To set the thresholds for starting and stopping battery charging (in percent of current capacity):''<br />
<br />
'''current''' really? That'd be weird, I'd expect it to be percent of '''total''' capacity.<br />
<br />
--[[User:Micampe|Micampe]] 14:39, 7 Dec 2005 (CET)<br />
<br />
"Current full charge capacity", as opposed to "current remaining capacity" or "designed full charge capacity"...<br />
<br />
--[[User:Thinker|Thinker]] 15:05, 7 Dec 2005 (CET)<br />
----<br />
<br />
Battery features don't work with my T41p. I can't check this with windows. Can anybody try these features?<br />
<br />
-- Nils, 7 Dec 2005<br />
----<br />
<br />
Nils, does cdrom_speed work for you on the T41p? Could you provide the details requested in the README (dmesg etc.)?<br />
<br />
--[[User:Thinker|Thinker]] 21:57, 7 Dec 2005 (CET)<br />
----<br />
<br />
CDRom Speed seems to work. (I see no warnings, but I have to do a speed test.) Now, I've send all outputs to the email-address in the readme.<br />
<br />
-- Nils, 8 Dec 2005<br />
----<br />
<br />
All the features except the stop_charge_thresh seem to work here on a t42p. <br />
One note, the start_charge_thresh seems to really be stop_charge_thresh. Ie, If I set that to lower than my current battery %, it will never charge, <br />
and if I set it to 100 the battery charges all the way. <br />
<br />
--[[User:Nirik|Nirik]] 16 Dec 2005<br />
----<br />
<br />
Nirik, "all the features" as of which version? For example, do the force_discharge{1,2} in tp_smapi 0.12 also work for you? See the table in the article page. About start_charge, that's odd. Can you send me a log of what you did, what was the result a what was the dmesg output for each operation?<br />
<br />
--[[User:Thinker|Thinker]] 14:16, 16 Dec 2005 (CET)<br />
----<br />
<br />
System T40p:<br />
<br />
<pre><br />
fairlight:/sys/devices/platform/smapi/BAT0# echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge1<br />
fairlight:/sys/devices/platform/smapi/BAT0# echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge2<br />
fairlight:/sys/devices/platform/smapi/BAT0# dmesg <br />
tp_smapi: req_in: BX=2118 CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=8680 BX=2118 CX=100 DX=b2 DI=0 SI=0 ret=-38<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2118)<br />
tp_smapi: cannot get force_discharge1 of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: req_in: BX=2104 CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=80 BX=2103 CX=100 DX=78 DI=0 SI=0 ret=0<br />
tp_smapi: cannot get force_discharge2 of battery 0: bx=2103<br />
</pre><br />
<br />
So it seems force_discharge1 is not supported at all. But force_discharge2? By the way, i think wiki is a _very_ good idea for collecting information, but not for discussion. I would prefer a maillinglist. We can use sourceforge.<br />
<br />
--[[User|StefanSchmidt]]<br />
<br />
force_discharge2 is indicating a real error condition (bx=2103 which has bit 0x02 on), but I have no idea what the error is or how to fix it. Sorry. If you can trigger this function under Windows and have SoftICE or equivalent, maybe it can be worked out.<br />
<br />
About the Wiki discussion, I'm not sure a mailing list is justified yet, but you can use the linux-thinkpad list or the e-mail address in the README. <br />
<br />
--[[User:Thinker|Thinker]] 21:42, 16 Dec 2005 (CET)<br />
<br />
OK, then i use linux-thinkpad to get more people involved. I'am away the next weeks, but i hope to find some time to hacking on tp_smapi.<br />
<br />
--[[User:StefanSchmidt]]<br />
----<br />
<br />
Someone reported cd_speed works on T42 but on mine, it doesn't: this is 2378DXU<br />
<br />
--[[User:eBug]] 22:55, 17 Dec 2005 (CET)<br />
----<br />
<br />
eBug, how does it fail? If the file doesn't exist, it means you didn't enable PROVIDE_CD_SPEED (see the README). If it does exist, can you provide the dmesg output when you read an write to the file?<br />
<br />
--[[User:Thinker|Thinker]] 11:53, 18 Dec 2005 (CET)<br />
----<br />
<br />
To confirm:<br />
tp_smapi 0.13 works with hdaps module loaded on T41 (2373-8RG). However, force_discharge*, inhibit_charge_minutes, start_charge_thresh, stop_charge_thresh don't seem to be implemented on this model.<br />
<br />
--[[User:LJSBRokken|LJSBrokken]] 21 Dec 2005<br />
----<br />
<br />
tp_smapi version 0.13 with T23 (2647-3QG) (I have dual batteries)...<br />
<br />
None of the functions which make any changes work...<br />
<br />
<pre># cd /sys/devices/platform/smapi && cat BAT*/* > /dev/null<br />
cat: BAT0/force_discharge1: Function not implemented<br />
cat: BAT0/force_discharge2: Input/output error<br />
cat: BAT0/inhibit_charge_minutes: Function not implemented<br />
cat: BAT0/start_charge_thresh: Function not implemented<br />
cat: BAT0/stop_charge_thresh: Function not implemented<br />
cat: BAT1/force_discharge1: Function not implemented<br />
cat: BAT1/force_discharge2: Input/output error<br />
cat: BAT1/inhibit_charge_minutes: Function not implemented<br />
cat: BAT1/start_charge_thresh: Function not implemented<br />
cat: BAT1/stop_charge_thresh: Function not implemented</pre><br />
<br />
However, all the battery status information is available, and functions appear for both BAT0 and BAT1, regardless of when the UltraBay battery was inserted or ejected- this is very useful, it is the only way I can monitor my UltraBay battery unless it was present on boot.<br />
<br />
--[[User:SystemParadox|SystemParadox]] 21:51, 4 Jan 2006 (CET)<br />
----<br />
<br />
SystemParadox, what's the dmesg output produced by "cat BAT0/force_discharge2"?<br />
<br />
--[[User:Thinker|Thinker]] 22:02, 4 Jan 2006 (CET)<br />
----<br />
<br />
After the upgrade to 0.14 (with kernel 2.6.15, using the patch) I can't use inhibit_charge and start/stop_charge_thresh any longer (getting an input/output error), the dmesg debug output when {{cmd|cat|}}-ing those three files:<br />
<br />
<pre><br />
tp_smapi: tp_smapi 0.14 loading...<br />
tp_smapi: successfully loaded (smapi_port=0xb2).<br />
tp_smapi: req_in: BX=2114 CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=ea210080 BX=ec192114 CX=c18d0700 DX=f7cc00b2 DI=f7f50000 SI=c18d0000 ret=-5<br />
tp_smapi: SMAPI error: Unknown error code (func=2114)<br />
tp_smapi: cannot get inhibit charge of battery 0: Unknown error code<br />
tp_smapi: req_in: BX=2116 CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=c03b0080 BX=c18d2116 CX=c0160328 DX=ec7600b2 DI=ec760000 SI=a0810000 ret=-5<br />
tp_smapi: SMAPI error: Unknown error code (func=2116)<br />
tp_smapi: cannot get start thresh of battery 0: Unknown error code<br />
tp_smapi: req_in: BX=211a CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=c03b0080 BX=c18d211a CX=c016032c DX=eb4500b2 DI=eb450000 SI=241e0000 ret=-5<br />
tp_smapi: SMAPI error: Unknown error code (func=211a)<br />
tp_smapi: cannot get stop thresh of battery 0: Unknown error code<br />
</pre><br />
<br />
--[[User:Spiney|spiney]] 08:12, 10 Jan 2006 (CET)<br />
----<br />
<br />
Oops, the transition to 32-bit SMAPI calls was broken. Fixed in 0.15. Thanks for the quick report!<br />
<br />
--[[User:Thinker|Thinker]] 12:10, 10 Jan 2006 (CET)<br />
----<br />
<br />
Yep, 0.15 works again. Quick response, bravo! :)<br />
<br />
--[[User:Spiney|spiney]] 12:23, 10 Jan 2006 (CET)<br />
----<br />
<br />
On a T22, nothing seems to work with 0.16.<br />
<br />
[[http://www.rafb.net/paste/results/fcUUDs49.html|dmesg output]] when doing cat *<br />
<br />
I am using an Ultrabay2000 battery, so it would be really usefull to be able to control that<br />
<br />
--[[User:nusse|nusse]]<br />
----<br />
<br />
Nusse: Not even the extended battery status? That does work on T23. About the control features, I believe they're not available on the T23; did you have any kind of (dis)charge control under WindowS?<br />
<br />
--[[User:Thinker|Thinker]] 20:59, 11 Jan 2006 (CET)<br />
----<br />
<br />
I don't really know what 'extended battery' status means, but here an example:<br />
<pre><br />
$ cat current_* /sys/devices/platform/smapi/BAT1<br />
cat: current_avg: Input/output error<br />
cat: current_now: Input/output error<br />
</pre><br />
This is what happens when i cat any file in this directory and also in ../BAT1 :(<br />
<br />
--[[User:nusse|nusse]] Thu Jan 12 22:07:26 CET 2006<br />
----<br />
<br />
Nusse: Yes, that's what I meant. What's the {{cmdroot|dmesg}} output generated by these commands?<br />
<br />
--[[User:Thinker|Thinker]] 00:27, 13 Jan 2006 (CET)<br />
----<br />
<br />
<br />
Thinker: I attached some link to my first comment but it seems to be down and the link was wrong anyway.<br />
<pre><br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2118)<br />
tp_smapi: cannot get force_discharge of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2114)<br />
tp_smapi: cannot get inhibit charge of battery 0: Function is not supported by SMAPI BIOS<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2116)<br />
tp_smapi: cannot get start thresh of battery 0: Function is not supported by SMAPI BIOS<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=211a)<br />
tp_smapi: cannot get stop thresh of battery 0: Function is not supported by SMAPI BIOS<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
</pre><br />
<br />
--[[User:nusse|nusse]] Fri Jan 13 14:35:57 CET 2006<br />
----<br />
<br />
Nusse: Thanks; but there's not much we can do. Maybe the T22 uses a different interface, or doesn't have that feature.<br />
<br />
--[[User:Thinker|Thinker]] 23:23, 15 January 2006 (CET)<br />
----<br />
<br />
Thinker: Is there anything I can do to check if the interface is different? Changing 0x1610 to some random number?<br />
<br />
Is there a chance to get it by try and error?<br />
<br />
--[[User:nusse|nusse]] Mon Jan 16 19:10:12 CET 2006<br />
----<br />
<br />
0x1610 is the number of an IO port it writes to, so changing it to a random number will pretty much guarantee a system crash...<br />
<br />
The only way I can think of for figuring out the T22 interface is to see what the Windows software does.<br />
<br />
--[[User:Thinker|Thinker]] 19:47, 16 January 2006 (CET)<br />
----<br />
<br />
I have a R40 (2722-B3G), and several things don't work with 0.16 on linux 2.6.15.1:<br />
<br />
<pre><br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2118)<br />
tp_smapi: cannot get force_discharge of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2114)<br />
tp_smapi: cannot get inhibit charge of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2116)<br />
tp_smapi: cannot get start thresh of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=211a)<br />
tp_smapi: cannot get stop thresh of battery 0: Function is not supported by SMAPI BIOS<br />
</pre><br />
<br />
Don't know about Windows, haven't booted it for weeks nor used it for years...<br />
<br />
--[[User:Wonka|Wonka]] 19:00, 19 January 2006 (CET)<br />
----<br />
<br />
Wonka: do the other features (i.e., extended battery status) work on your R40?<br />
<br />
--[[User:Thinker|Thinker]] 20:30, 20 January 2006 (CET)<br />
----<br />
<br />
--[[User:lisch|lisch]] 16:14, 11 April 2006 (CDT)<br />
<br />
On my X32, with two batteries, I get just what I expect. Looks good:<br />
<pre>$ cat BAT?/* > /dev/null<br />
cat: BAT0/force_discharge: Function not implemented<br />
cat: BAT0/inhibit_charge_minutes: Function not implemented<br />
cat: BAT0/start_charge_thresh: Function not implemented<br />
cat: BAT0/stop_charge_thresh: Function not implemented<br />
cat: BAT1/force_discharge: Function not implemented<br />
cat: BAT1/inhibit_charge_minutes: Function not implemented<br />
cat: BAT1/start_charge_thresh: Function not implemented<br />
cat: BAT1/stop_charge_thresh: Function not implemented<br />
$<br />
</pre><br />
==Changing the CD speed when the CD is being accessed will hang your computer==<br />
<br />
I don't have this problem on my T40p. CDROM is mounted and file on CD is opened. Change speed do '''not''' hang my system.<br />
<br />
-- Stefan Schmidt<br />
----<br />
<br />
An open file looks fine if you're not reading/writing at that point. But my T43 does hangs on this:<br />
# dd if=/dev/scd0 of=/dev/null &<br />
# echo 1 > /sys/devices/platform/smapi/cdrom_speed<br />
<br />
--[[User:Thinker|Thinker]] 16:41, 7 Dec 2005 (CET)<br />
----<br />
<br />
OK, sorry. I was to fast. My system hangs on this commands, too. :(<br />
<br />
-- Stefan Schmidt<br />
<br />
Works well. Great.<br />
<br />
T42 2373-8zh. Working :cdrom_speed and start_charge_thresh. Untest : inhibit_charge_minutes.<br />
<br />
-- Haifeng Chen<br />
<br />
cdrom_speed works on my T40.<br />
<br />
-- [[User:Lammic|lammic]], 2005.12.09<br />
<br />
== Kernel Patch? ==<br />
<br />
Hello Thinker,<br />
<br />
would it be possible to provide the SMAPI support as kernel patch as well? Something along the lines of: (0.12 against 2.6.15-rc5)<br />
<br />
''(deleted, see below for how to create a patch file)''<br />
<br />
Deleted the tp_smapi.c file at the end, out of obvious reasons, and I'm not sure about the placement in the ACPI section, OTOH there it would be found easily next to ibm_acpi.<br />
<br />
Providing a patch would help when recompiling the kernel often, I hate recompiling external modules every time (even got me a kernel-upgrade script to do most of it automatically). But of course it's up to you. :)<br />
<br />
--[[User:Spiney|spiney]] 09:52, 16 Dec 2005 (CET)<br />
----<br />
<br />
I'll be glad to add this, but I don't want to go through additional manual steps in the release process (there are already quite a few). Can you add a "make patch" functionality to the Makefile, or something of the sort, to automatically generate a full patch (including tp_smapi.c) against current kernel sources?<br />
<br />
Also, this shouldn't be under drivers/acpi, since it doesn't use ACPI at all (that's why I didn't make it a patch to ibm_acpi). I think the right place is drivers/firmware, like the dell_rbu driver for Dell laptops.<br />
<br />
BTW, the convention for kernel patches is to start them once level higher:<br />
diff -Nurp kernel-2.6.14-vanilla kernel-2.6.14-patched<br />
<br />
--[[User:Thinker|Thinker]] 17:12, 16 Dec 2005 (CET)<br />
----<br />
<br />
Of course it's from the wrong level, as usual I was just lazy/inattentive. And at one point I'll remember who likes what patch format, promise. ;)<br />
<br />
A patch target as in "create a new file holding a correct diff to current kernel source" would be rather difficult, since line numbers might change etc., but applying the patch should be straighforward with a bit of sed. Of course I could just do that, create a patch with the diff command and then apply the new patch file in reverse. ;)<br />
<br />
--[[User:Spiney|spiney]] 18:36, 16 Dec 2005 (CET)<br />
----<br />
<br />
If it does that on a local copy (no changes the original kernel tree) and cleans up after itself, that's fine with me. :-)<br />
<br />
--[[User:Thinker|Thinker]] 18:50, 16 Dec 2005 (CET)<br />
----<br />
<br />
Ok, here's a shell script that creates the patch, feel free to use it under the terms of the GPL. For example call it from your Makefile with the patch target: (I didn't want to put all the script into the Makefile, since the rules about escaping in Makefiles, well, escape me ;)<br />
<br />
<pre><br />
#!/bin/bash<br />
<br />
KDIR=/lib/modules/$(uname -r)/build<br />
FDIR=drivers/firmware<br />
OPWD=$(pwd)<br />
<br />
TMPDIR=$(mktemp -d)<br />
cd $TMPDIR<br />
<br />
mkdir -p a/$FDIR<br />
cp $KDIR/$FDIR/{Kconfig,Makefile} a/$FDIR<br />
cp -r a b<br />
sed -i -e '/endmenu/i\<br />
config IBM_SMAPI\<br />
tristate "IBM ThinkPad SMAPI Support"\<br />
depends on X86\<br />
---help---\<br />
This adds SMAPI support on IBM ThinkPads, mostly used for battery\<br />
charge control. For more information about this driver see\<br />
<http://www.thinkwiki.org/wiki/SMAPI_support_for_Linux> .\<br />
\<br />
If you have an IBM ThinkPad laptop, say Y or M here.\<br />
' b/$FDIR/Kconfig<br />
sed -i -e '$a\<br />
obj-$(CONFIG_IBM_SMAPI) += tp_smapi.o' b/$FDIR/Makefile<br />
cp $OPWD/tp_smapi.c b/$FDIR<br />
diff -Nurp a b > $OPWD/tp_smapi-$(uname -r).patch<br />
rm -r a b<br />
cd $OPWD<br />
</pre><br />
<br />
BTW, [http://qbnz.com/highlighter/ GeSHi]-based syntax-highlighting would be great...<br />
<br />
--[[User:Spiney|spiney]] 19:28, 16 Dec 2005 (CET)<br />
----<br />
<br />
Ah, neat sed foo. How about [http://tpctl.sourceforge.net/tmp/Makefile this] escapade, then? <br />
<br />
What's the sed spell needed to replace the Makefile's<br />
VER := 0.13<br />
with auto-parsing of<br />
#define TP_VERSION "0.13"<br />
from tp_smapi.c?<br />
<br />
--[[User:Thinker|Thinker]] 20:37, 16 Dec 2005 (CET)<br />
----<br />
<br />
Hmm, something like<br />
VERFROMC=$(sed -ne 's/^#define TP_VERSION "\(.*\)"/\1/gp' tp_smapi.c)<br />
sed -i -e "s/^VER := .*$/VER := $VERFROMC/" Makefile<br />
should do (untested, from the top of my head, maybe the temporary variable isn't even necessary?). And neat Makefile wizardry, at one point I'll learn the syntax.<br />
<br />
--[[User:Spiney|spiney]] 20:44, 16 Dec 2005 (CET)<br />
----<br />
<br />
Makefile escaping is horrible, keep avoiding it... Anyway, the updated [http://tpctl.sourceforge.net/tmp/Makefile make patch] seems to do the right thing.<br />
<br />
--[[User:Thinker|Thinker]] 21:36, 16 Dec 2005 (CET)<br />
----<br />
<br />
Small documentation request: just needed to create a patch for the not-yet-installed 2.6.16-rc2, which is no problem with<br />
make KSRC=/path/to/linux-2.6.16-rc2 KVER=2.6.16-rc2 patch<br />
but I guess it would be a good addition to the README file. :)<br />
<br />
--[[User:Spiney|spiney]] 10:48, 8 February 2006 (CET)<br />
----<br />
<br />
Right, added (to next release).<br />
<br />
--[[User:Thinker|Thinker]] 13:40, 8 February 2006 (CET)<br />
----<br />
<br />
==Installation questions==<br />
Amazing! I've loaded this module in my T43 which is running SuSE 10 with the kernel of 2.6.13-15. I have three points to share:<br />
<br />
1. The battery control part seems to work but has a minor problem. I set the stop_charge_threshold to 70, but the battery stops charging at 55%. Don't know why and how to fix it. :P<br />
<br />
2. I don't have the cd speed control function. Here is what I have under /sys/devices/platform/smapi/:<br />
<br />
./ ../ ac_connected BAT0/ BAT1/ bus@ driver@ power/<br />
<br />
3. SuSE 10 doesn't have the necessary C files under .../drivers/hwmon/, I copied them from a 2.6.14.5 kernel source. Maybe it causes the two problems above. :(<br />
<br />
When I have time, I'll install the new kernel to see if the problems are gone and report the result.<br />
<br />
--[[User:68.51.153.96|68.51.153.96]] 04:31, 2 Jan 2006 (CET)<br />
----<br />
<br />
1. It should stop charging at 70, but will only ''start'' charging when remaining capacity has dipped below <tt>start_charge_thresh</tt>.<br />
<br />
2. See the note about PROVIDE_CD_SPEED.<br />
<br />
3. That's should be needed only for patching the HDAPS driver in order to make it compatible with tp_smapi. If your kernel (which version is it?) doens't inlude the HDAPS driver anyway, you don't need to patch....<br />
<br />
--[[User:Thinker|Thinker]] 09:28, 2 Jan 2006 (CET)<br />
----<br />
<br />
Thanks Thinker.<br />
<br />
1. I discharged and recharged the battery again. This time, it stops at 68% percent, which is pretty good.<br />
<br />
2. I missed the NOTE in README, for I just followed this wiki. :P<br />
<br />
3. My kernel version is 2.6.13-15.<br />
<br />
By the way, I just got this T43 whose model number is 266896U. I feel that the noise of the fan is much louder than my previous T21. I think it is so since it has a CPU with bigger power but am wondering if other T43 has the same big noise?<br />
<br />
--[[User:Tyne|Tyne]] 00:14, 3 Jan 2006 (CET)<br />
----<br />
<br />
The note about PROVIDE_CD_SPEED is also in the Wiki...<br />
<br />
About the T43 fan noise: yes, this is a very common (and annoying) problem. See [[Problem_with_fan_noise]] and our [[ACPI fan control script]], and send Lenovo a complaint in hope they'll fix this at the firmware level.<br />
<br />
--[[User:Thinker|Thinker]] 08:48, 3 Jan 2006 (CET)<br />
----<br />
<br />
== Formatting ==<br />
<br />
Wyrfel, that was some heavy editing you did... I agree with most changes (including the saner color choice). I did like those HINT floats, though - they keep the hints from interrupting the flow of text too much, and this particular text needs any help it can get.<br />
<br />
--[[User:Thinker|Thinker]] 17:04, 3 Jan 2006 (CET)<br />
----<br />
Hei Thinker,<br />
<br />
I'll look into it again. I felt that the floating HINTs were tearing the text apart too much. Maybe we could fix it by placing the clear marks somewhere else.<br />
<br />
[[User:Wyrfel|Wyrfel]] 18:46, 3 Jan 2006 (CET)<br />
----<br />
<br />
== Dual battery operation with tp_smapi ==<br />
<br />
It looks like it is working quite fine with tp_smapi-0.13 and 2.6.15 (it may also work with other versions, but those are the ones I have running right now).<br />
<br />
The juicy details:<br />
<br />
{{cmdroot|cd /sys/devices/platform/smapi/}}<br />
{{cmdroot|cat ac_connected}}<br />
<br />
{{cmdresult|0}}<br />
{{cmdroot|cat BAT{0,1}/state}}<br />
{{cmdresult|discharging}}<br />
{{cmdresult|idle}}<br />
<br />
{{cmdroot|echo 1 > BAT1/force_discharge1}}<br />
{{cmdroot|cat BAT{0,1}/state}}<br />
{{cmdresult|idle}}<br />
{{cmdresult|discharging}}<br />
<br />
Checking capacity values shows that the corrent battery is being depleted.<br />
<br />
And remember, before you yank the CD/DVD drive out, issue:<br />
<br />
{{cmdroot|cat eject > /proc/acpi/ibm/bay}}<br />
<br />
----<br />
<br />
Great! Which ThinkPad model is it? Could you also {{cmdroot|cat /sys/devices/platform/smapi/BAT{0,1}/force_discharge2}} and report the dmesg output (after {{cmdroot|make load}} or {{cmdroot|1=modprobe tp_smapi debug=1}})?<br />
<br />
About the eject command, I think it should be possible to do that automatically when the Ultrabay handle is ejected, via <tt>acpid</tt>.<br />
<br />
--[[User:Thinker|Thinker]] 15:45, 10 Jan 2006 (CET)<br />
----<br />
<br />
It's a T43 (2669). cat'ing force_discharge2 gives me an I/O error and I see<br />
<br />
tp_smapi: cannot get force_discharge2 of battery 0: bx=2103<br />
<br />
tp_smapi: cannot get force_discharge2 of battery 1: bx=2103<br />
<br />
I find these errors irrelevant from the user's point of view, though. <br />
<br />
Indeed, it should be possible to automatise the "eject" command. I should also be noted that once a force_discharge1 is set, it will NOT unset automatically, event when the AC is plugged back in. An obvious fix is to fiddle with the appropriate ACPI event to force_discharge1 back to 0 for all batteries once the AC is attached.<br />
<br />
----<br />
<br />
Thanks, this eliminates the last situation I imagined <tt>force_discharge2</tt> might work. The next tp_smapi version will remove <tt>force_discharge2</tt> and rename <tt>force_discharge1</tt> to <tt>force_discharge</tt>.<br />
<br />
If you write those ACPI scripts, it would be great if you put them on the Wiki.<br />
<br />
--[[User:Thinker|Thinker]] 16:31, 10 Jan 2006 (CET)<br />
----<br />
<br />
Well, I still do not preclude the fact that <tt>force_discharge2</tt> may be useful for something else on other models.<br />
<br />
The ACPI scripts (as well as an installation guide) is underway. It may take a while, though.<br />
<br />
----<br />
<br />
See the new article: [[Using an Ultrabay battery]].<br />
<br />
--[[User:Thinker|Thinker]] 17:05, 10 Jan 2006 (CET)<br />
----<br />
<br />
Hei Thinker,<br />
<br />
i just renamed the new page. Will adjust your links later on. Keeping the redirect page until that's done. Please set any new links you create to the new page (the pages of the individual UltraBay batteries should contain a pointer).<br />
<br />
On a sidenote: I would like to split the SMAPI support under Linux page into a tp_smapi driver page, just listing the features, and a "How to use tp_smapi" page. I would also split the thinkpad/tpctl page off that again. Any objections?<br />
<br />
[[User:Wyrfel|Wyrfel]] 20:42, 10 Jan 2006 (CET)<br />
----<br />
<br />
ACK about the page rename (the old one did sound a bit out of line to my ear, but I couldn't spot why...).<br />
<br />
About the splitting tp_smapi vs. thinkpad/tpctl, no objection.<br />
<br />
About splitting tp_smapi: currently most of that section doubles as both a spec and a HOWTO, which I think is a convenient and concise way to describe things (hey, it must be right, the Perl docs do it!). I'm not sure there's much benefit in duplicating that. Perhaps we should wait for a critical mass of additional lore to accumulate?<br />
<br />
--[[User:Thinker|Thinker]] 21:04, 10 Jan 2006 (CET)<br />
----<br />
Ok, i agree on the latter.<br />
<br />
[[User:Wyrfel|Wyrfel]] 00:57, 11 Jan 2006 (CET)<br />
----<br />
<br />
==Article name capitalization== <br />
<br />
Wikimedia autocapitalizes the article name upon submit. How do I concince Wikimedia that I really want a lowercase "t"? The underline is probably too much too ask...<br />
<br />
--[[User:Thinker|Thinker]] 11:03, 11 Jan 2006 (CET)<br />
----<br />
<br />
Impossible, according to [http://en.wikipedia.org/wiki/Wikipedia:Canonicalization Wikipedia:Canonicalization].<br />
<br />
--[[User:Thinker|Thinker]] 12:04, 11 Jan 2006 (CET)<br />
----<br />
<br />
==Status Table==<br />
For at least the T series i think that charge control was not supported prior to the T42, hardware/BIOS side. Perhaps "N/A" flags would be better here?<br />
<br />
I also created <nowiki>{{Isup}}</nowiki> style templates for status, they just include images, like {{Isup}}.<br />
Not emotional about it, just wanted to let you know in case you want to use them.<br />
<br />
Third and last...would it possibly be better to make the table headers more human readable like i.e. "lower charge threshold" or something like that instead of "start_charge_thresh"?<br />
<br />
[[User:Wyrfel|Wyrfel]] 19:21, 11 Jan 2006 (CET)<br />
----<br />
<br />
About "N/A", sure, if we get reliable data about the hardware capabilities. Alas, most negative reports were just "it doesn't work", and in some cases gave contradictory information (SMAPI interface says a function is unsupported but user says it works under Windows).<br />
<br />
About {{Iyes}} and friends, they're very cute, but I think think they're harder to parse visually and would add some clutter to an already dense table.<br />
<br />
The table headers are just the names of the control files - that's important to keep, sine it's the most natural lookup key. Adding friendly description would be great, if we can fit them in (not everyone has an SXGA+ display...). I tried and failed.<br />
<br />
--[[User:Thinker|Thinker]] 20:38, 11 Jan 2006 (CET)<br />
----<br />
<br />
I have a T41p and the windows tools still don't offer me battery management, even though it's quite a while since the T42 came out.<br />
<br />
I'm ok with the rest.<br />
<br />
[[User:Wyrfel|Wyrfel]] 22:35, 11 Jan 2006 (CET)<br />
----<br />
<br />
For the {{X40}}, I can report success using the stop_charge_thresh feature with BIOS v2.03 (1UETC8WW) and Embedded Controller Program v1.60 (1UHTB0WW).<br />
<br />
[[User:Peterco|Peterco]] 12:07, 28 February 2006 (CET)<br />
----<br />
<br />
== Z60t ==<br />
<br />
Tested on Z60t. No errors using cat. Setting thresholds works. Status and capacity queries work. --[[User:Alon|Alon]] 21:44, 4 May 2006 (CEST)<br />
<br />
== Problem setting thresholds with X40 ==<br />
<br />
My X40, kernel 2.6.16 and tp_smapi 0.20. I try to set the thresholds to 40% and 90% using:<br />
<pre><br />
# echo 90 > stop_charge_thresh<br />
# echo 40 > start_charge_thresh<br />
</pre><br />
which should work, and the kernel reports from dmesg:<br />
<pre><br />
tp_smapi: successfully loaded (smapi_port=0xb2).<br />
tp_smapi: battery 0: changed start threshold to 85(+1)<br />
tp_smapi: battery 0: changed stop threshold to 90<br />
tp_smapi: battery 0: changed start threshold to 39(+1)<br />
</pre><br />
but, on confirmation here is what happens:<br />
<pre><br />
# cat stop_charge_thresh<br />
90<br />
# cat start_charge_thresh<br />
91<br />
</pre><br />
Any clues as to why start doesn't keep? Or why its always at 1 above stop_charge_thresh?<br />
<br />
--[[User:Xmm0|Xmm0]] 15:01, 17 May 2006 (CEST)<br />
----<br />
<br />
Is it any different if you first set start_charge_thresh and then stop_charge_thresh? <br />
<br />
Can you please load tp_smapi with module option "debug=1" and report the dmesg output genereated by each command?<br />
<br />
--[[User:Thinker|Thinker]] 16:31, 17 May 2006 (CEST)<br />
----<br />
<br />
== Battery daemon feedback requested ==<br />
<br />
I am writing a battery-management daemon to control charging and discharging BAT0 and BAT1 in accordance with usage patterns that extend Li-Ion and Li-Py battery life.<br />
<br />
By default, the machine fully discharges BAT1 first, and it is said that deep-cycling all the time dramatically shortens their lifetime.<br />
<br />
My Z61t is the test machine, and it is configured with two batteries, the stock 4-cell, and an "Advanced Ultrabay", which about doubles the runtime of the machine.<br />
<br />
Currently there are two "modes" of the daemon:<br />
<br />
Discharging mode.<br />
<pre><br />
* look at the "remaining_percent" values for both batteries<br />
* if one is more than THRESHOLD percent less than the other one, <br />
force discharge from the battery with more capacity left<br />
(the current value for THRESHOLD is 10%)<br />
</pre><br />
I believe the preceeding will prevent either battery from being deep-cycled disproportionately.<br />
<br />
Charging mode. I am less sure what the "right" algorithm is here. The following is a proposal.<br />
<pre><br />
* look at the "remaining_percent" values for both batteries<br />
* if one is more than THRESHOLD percent less than the other one, <br />
force charging to the battery with less capacity left<br />
* honor pre-set values in stop_charge_thresh and start_charge_thresh<br />
</pre><br />
<br />
I would like to get feedback in the form of "better" algorithms or requests for this daemon.<br />
<br />
--[[User:Zak Smith|Zak]] 19:03, 12 September 2006 (CEST)<br />
<br />
It sounds like your algorithm will indeed minimize wear on both batteries. A side benefit is that charging will toggle between the batteries, which may help keep them cooler while charging and thus prolong their life. OTOH, if you plan to occasionally swap the UltraBay battery for other devices, you may want to fully charge the system battery (up to stop_charge_thresh) first.<br />
<br />
--[[User:Thinker|Thinker]] 22:57, 12 September 2006 (CEST)<br />
<br />
<br />
I have noticed that when force_discharge is set and the batteries switch, the gnome battery monitoring applet gets totally confused about remaining runtime. Besides being a nuisance, this could presumably cause premature emergency shutduwn.<br />
<br />
I have also noticed that the reported remaining runtimes vary greatly between acpi, the applet, and /proc/acpi/battery/*/state<br />
<br />
--[[User:Zak Smith|Zak]] 21:46, 14 September 2006 (CEST)<br />
<br />
What do you mean by "acpi" vs. "/proc/acpi/battery/*/state"? <br />
<br />
The most accurate readout is probably {{path|/sys/devices/platform/smapi/BAT0/remaining_running_time}}, but I don't think any applet uses that yet.<br />
<br />
--[[User:Thinker|Thinker]] 12:07, 15 September 2006 (CEST)<br />
<br />
By acpi, I meant the output of the acpi (1) command. I'll get some comparative numbers later and post them here.<br />
<br />
--[[User:Zak Smith|Zak]] 20:37, 15 September 2006 (CEST)<br />
<br />
Odd, my version of {{path|/usr/bin/acpi}} doesn't report remaining time, just percent (which is the same as {{path|/sys/devices/platform/smapi/BAT0/remaining_percent}}).<br />
<br />
--[[User:Thinker|Thinker]] 21:32, 15 September 2006 (CEST)<br />
<br />
I have been running batteryd for a while with good results. I will upload it here shortly.<br />
<br />
I disabled the preferential charging mode, and only control discharging.<br />
<br />
--[[User:Zak Smith|Zak]] 23:15, 14 November 2006 (CET)<br />
<br />
http://demigod.org/~zak/src/batteryd.cc<br />
<br />
--[[User:Zak Smith|Zak]] 20:18, 5 December 2006 (CET)<br />
<br />
== Instructions for X60 with Bios 1.11 under Debian Etch ==<br />
<br />
Could someone please provide step-by-step instructions of how to make this work with Debian? What have I to do after apt-get install kernel-patch-tpsmapi? Thank you!<br />
<br />
--[[User:PeterBursch|PeterBursch]] 21:39, 15 September 2006 (CEST)</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=User_talk:Gmetal&diff=27758User talk:Gmetal2007-01-20T11:23:50Z<p>Gmetal: </p>
<hr />
<div>=Installing Gentoo Linux 2006.1 on a Thinkpad T60=<br />
<br />
This page details my efforts on installing Gentoo Linux on my Lenovo Thinkpad T60 Model No. 2007FVG.<br />
My laptop has the following hardware configuration:<br />
<br />
* Audio: AD1981HD <br />
* 15in TFT (1400 x 1050)<br />
* Mobile Intel 945PM Express <br />
* Bluetooth<br />
* Gigabit Ethernet<br />
* Wireless LAN IEEE 802.11(a/b/g/n)<br />
* DVD-Writer <br />
* Core 2 Duo - T5600 (1.83 GHz)<br />
* 1 GB RAM<br />
* 120 GB SATA-150 HDD<br />
* Trusted Platform Module (TPM 1.2) Security Chip <br />
* Fingerprint reader <br />
* ATI Mobility Radeon X1400 PCIe (x16) 128 MB <br />
<br />
= Preliminary Steps and Gentoo Linux Setup =<br />
<br />
First step was to make space for my Linux partitions. Booted into Knoppix, resized the Windows partition (freeing about 90Gb of space for<br />
Linux) using QTParted. The hidden partition used by IBM/Lenovo for restoring the laptop was left untouched. I then created an extended partition<br />
on the free space and created the logical partitions for Linux. This machine is 64-bits, but I also wanted to be able to have a 32-bit environment. <br />
So I created two root partitions and a separate home partition. Furthermore, I also placed the directory holding the distfiles and portage into two<br />
separate partitions. All in all this is how drive was partitioned:<br />
<br />
* /dev/sda1 Windows NTFS<br />
* /dev/sda2 IBM Rescue partition<br />
* /dev/sda3 Extended partition<br />
* /dev/sda5 Boot partition<br />
* /dev/sda6 Swap artition<br />
* /dev/sda7 Portage partition<br />
* /dev/sda8 Distfiles partition<br />
* /dev/sda9 Gentoo64 root<br />
* /dev/sda10 Gentoo32 root<br />
* /dev/sda11 /home partition<br />
<br />
Once this was finished I proceeded to reboot and use the Gentoo Linux 2006.1 installation cd for the AMD64 architecture (which is what should be used <br />
for a 64-bit installation on a Core 2 Duo). <br />
<br />
=64-bit Gentoo Linux 2006.1 Installation=<br />
<br />
The installation was quite smooth and was done according to the Gentoo Handbook: [http://www.gentoo.org/doc/en/handbook/index.xml]<br />
The only glitch the kernel that I built, which was done with a manual <br />
<br />
{{cmdroot|make menuconfig}}<br />
<br />
and not with Gentoo's genkernel.<br />
Once I restarted the laptop, my kernel booted fine but was unable to mount the root partition. Turns out that it needed the following <br />
.config entries:<br />
* CONFIG_PARTITION_ADVANCED<br />
* CONFIG_MSDOS_PARTITION<br />
Once I added these entries to my .config and rebuilt the kernel, everything went fine and I booted into Linux.<br />
<br />
== Hardware Configuration ==<br />
<br />
The flags used for compiling the 64-bit partition are the following:<br />
<br />
* kde mp3 mpeg xv sdl quicktime nptl gtk gtk2 jpeg tiff nptlonly alsa qt qt3 qt4 dvd cdr dvdr aac ipv6 trutype emul-linux-x86 png X opengl<br />
<br />
The result of <br />
<br />
{{cmdroot|lspci}} <br />
<br />
is the following:<br />
<br />
* 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)<br />
* 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)<br />
* 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
* 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
* 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
* 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
* 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
* 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
* 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
* 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)<br />
* 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller AHCI (rev 02)<br />
* 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
* 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
* 03:00.0 Network controller: Atheros Communications, Inc. Unknown device 0024 (rev 01)<br />
* 15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller<br />
<br />
== Hardware working out of the box ==<br />
<br />
The integrated gigabit ethernet controller works fine with the e1000 driver:<br />
<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
<br />
The USB controllers also work fine with the ehci_hcd and uhci_hcd drivers found in the kernel:<br />
<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
<br />
This version of the laptop has an integrated SATA controller, and its HDD is also SATA. To get it working<br />
you need to use the AHCI driver:<br />
<br />
* CONFIG_SATA_AHCI<br />
<br />
I also added the following Kernel options (not sure if they are needed though):<br />
<br />
* CONFIG_ATA_PIIX<br />
* CONFIG_PATA_MPIIX<br />
<br />
This laptop also includes an integrated Bluetooth adapter. It is reported as a USB device with a Broadcom<br />
Bluetooth chip. More specifically <br />
<br />
{{cmdroot|lsusb -v}}<br />
<br />
is reporting the following:<br />
<br />
* Bus 004 Device 004: ID 0a5c:2110 Broadcom Corp.<br />
* Device Descriptor:<br />
* bLength 18<br />
* bDescriptorType 1<br />
* bcdUSB 2.00<br />
* bDeviceClass 224 Wireless<br />
* bDeviceSubClass 1 Radio Frequency<br />
* bDeviceProtocol 1 Bluetooth<br />
* bMaxPacketSize0 64<br />
* idVendor 0x0a5c Broadcom Corp.<br />
* idProduct 0x2110<br />
* bcdDevice 1.00<br />
* iManufacturer 1 Broadcom Corp<br />
* iProduct 2 BCM2045B<br />
* iSerial 0<br />
* bNumConfigurations 1<br />
<br />
This device appears to be working fine by including Bluetooth support in the kernel, and using the hci_usb<br />
driver. It does not seem that for this device to work the BCM203x driver is required (it is not loaded by the kernel).<br />
To get it to work, I also needed to emerge bluez-libs and bluez-utils. I must also note that it can be turned on and off<br />
by using the laptop's Function key and F4.<br />
<br />
The audio part was a bit tricky to get it to work properly. The integrated audio chipset uses the snd_hda_intel ALSA<br />
driver (export ALSA_CARDS="hda-intel"). However, I had to use version 1.0.14_rc1 to get it to compile. Eventually, <br />
everything was working fine, but I realised that I needed to run alsaconf or restart the alsasound script each time to <br />
get sound working, because the driver wasn't being loaded correctly. Eventually I came across this post <br />
[http://www.ussg.iu.edu/hypermail/linux/kernel/0610.0/1429.html] which solved my problems. After enabling the integrated<br />
modem from the BIOS, my problem went away. <br />
<br />
HDAPS appears to be working fine. Compiled the kernel with:<br />
<br />
* CONFIG_SENSORS_HDAPS=m<br />
<br />
and emerged app-laptop/hdapsd, and it appears that IBM's HDD shock protection mechanism is working fine. You must also run:<br />
{{cmdroot|rc-update add hdapsd default}}<br />
to make the hdapsd daemon start up at boot time. <br />
<br />
== Hardware Partly working == <br />
<br />
<br />
= TODO =<br />
<br />
Finish the remaining sections</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=Talk:Tp_smapi&diff=27751Talk:Tp smapi2007-01-19T15:34:19Z<p>Gmetal: /* Status Table */</p>
<hr />
<div>== Feedback ==<br />
<br />
Great, great work! Really! This completely rocks. I just stopped my battery from charging at 77% and restarted charging a bit later, no problems whatsoever. BTW, this is on kernel 2.6.14.3.<br />
<br />
--[[User:Spiney|spiney]] 21:25, 5 Dec 2005 (CET)<br />
----<br />
None of the fuctions is working on my T40, kernel 2.6.14-mm2.<br />
<br />
--[[User:Lammic|lammic]], 2005.12.05<br />
<br />
Works for me on a T41 running 2.6.12-10-686 (Ubuntu 5.10).<br />
<br />
--[[User:berndtnm|berndtnm]], 2005.12.06<br />
<br />
Including stop_charge_thresh? That one seems to be missing on the T42p.<br />
<br />
--[[User:Thinker|Thinker]] 00:46, 7 Dec 2005 (CET)<br />
----<br />
<br />
tp_smapi works just fine on an R52 with Ubuntu Breezy stock kernel.<br />
<br />
--[[User:Micampe|Micampe]] 12:52, 7 Dec 2005 (CET)<br />
<br />
----<br />
<br />
''To set the thresholds for starting and stopping battery charging (in percent of current capacity):''<br />
<br />
'''current''' really? That'd be weird, I'd expect it to be percent of '''total''' capacity.<br />
<br />
--[[User:Micampe|Micampe]] 14:39, 7 Dec 2005 (CET)<br />
<br />
"Current full charge capacity", as opposed to "current remaining capacity" or "designed full charge capacity"...<br />
<br />
--[[User:Thinker|Thinker]] 15:05, 7 Dec 2005 (CET)<br />
----<br />
<br />
Battery features don't work with my T41p. I can't check this with windows. Can anybody try these features?<br />
<br />
-- Nils, 7 Dec 2005<br />
----<br />
<br />
Nils, does cdrom_speed work for you on the T41p? Could you provide the details requested in the README (dmesg etc.)?<br />
<br />
--[[User:Thinker|Thinker]] 21:57, 7 Dec 2005 (CET)<br />
----<br />
<br />
CDRom Speed seems to work. (I see no warnings, but I have to do a speed test.) Now, I've send all outputs to the email-address in the readme.<br />
<br />
-- Nils, 8 Dec 2005<br />
----<br />
<br />
All the features except the stop_charge_thresh seem to work here on a t42p. <br />
One note, the start_charge_thresh seems to really be stop_charge_thresh. Ie, If I set that to lower than my current battery %, it will never charge, <br />
and if I set it to 100 the battery charges all the way. <br />
<br />
--[[User:Nirik|Nirik]] 16 Dec 2005<br />
----<br />
<br />
Nirik, "all the features" as of which version? For example, do the force_discharge{1,2} in tp_smapi 0.12 also work for you? See the table in the article page. About start_charge, that's odd. Can you send me a log of what you did, what was the result a what was the dmesg output for each operation?<br />
<br />
--[[User:Thinker|Thinker]] 14:16, 16 Dec 2005 (CET)<br />
----<br />
<br />
System T40p:<br />
<br />
<pre><br />
fairlight:/sys/devices/platform/smapi/BAT0# echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge1<br />
fairlight:/sys/devices/platform/smapi/BAT0# echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge2<br />
fairlight:/sys/devices/platform/smapi/BAT0# dmesg <br />
tp_smapi: req_in: BX=2118 CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=8680 BX=2118 CX=100 DX=b2 DI=0 SI=0 ret=-38<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2118)<br />
tp_smapi: cannot get force_discharge1 of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: req_in: BX=2104 CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=80 BX=2103 CX=100 DX=78 DI=0 SI=0 ret=0<br />
tp_smapi: cannot get force_discharge2 of battery 0: bx=2103<br />
</pre><br />
<br />
So it seems force_discharge1 is not supported at all. But force_discharge2? By the way, i think wiki is a _very_ good idea for collecting information, but not for discussion. I would prefer a maillinglist. We can use sourceforge.<br />
<br />
--[[User|StefanSchmidt]]<br />
<br />
force_discharge2 is indicating a real error condition (bx=2103 which has bit 0x02 on), but I have no idea what the error is or how to fix it. Sorry. If you can trigger this function under Windows and have SoftICE or equivalent, maybe it can be worked out.<br />
<br />
About the Wiki discussion, I'm not sure a mailing list is justified yet, but you can use the linux-thinkpad list or the e-mail address in the README. <br />
<br />
--[[User:Thinker|Thinker]] 21:42, 16 Dec 2005 (CET)<br />
<br />
OK, then i use linux-thinkpad to get more people involved. I'am away the next weeks, but i hope to find some time to hacking on tp_smapi.<br />
<br />
--[[User:StefanSchmidt]]<br />
----<br />
<br />
Someone reported cd_speed works on T42 but on mine, it doesn't: this is 2378DXU<br />
<br />
--[[User:eBug]] 22:55, 17 Dec 2005 (CET)<br />
----<br />
<br />
eBug, how does it fail? If the file doesn't exist, it means you didn't enable PROVIDE_CD_SPEED (see the README). If it does exist, can you provide the dmesg output when you read an write to the file?<br />
<br />
--[[User:Thinker|Thinker]] 11:53, 18 Dec 2005 (CET)<br />
----<br />
<br />
To confirm:<br />
tp_smapi 0.13 works with hdaps module loaded on T41 (2373-8RG). However, force_discharge*, inhibit_charge_minutes, start_charge_thresh, stop_charge_thresh don't seem to be implemented on this model.<br />
<br />
--[[User:LJSBRokken|LJSBrokken]] 21 Dec 2005<br />
----<br />
<br />
tp_smapi version 0.13 with T23 (2647-3QG) (I have dual batteries)...<br />
<br />
None of the functions which make any changes work...<br />
<br />
<pre># cd /sys/devices/platform/smapi && cat BAT*/* > /dev/null<br />
cat: BAT0/force_discharge1: Function not implemented<br />
cat: BAT0/force_discharge2: Input/output error<br />
cat: BAT0/inhibit_charge_minutes: Function not implemented<br />
cat: BAT0/start_charge_thresh: Function not implemented<br />
cat: BAT0/stop_charge_thresh: Function not implemented<br />
cat: BAT1/force_discharge1: Function not implemented<br />
cat: BAT1/force_discharge2: Input/output error<br />
cat: BAT1/inhibit_charge_minutes: Function not implemented<br />
cat: BAT1/start_charge_thresh: Function not implemented<br />
cat: BAT1/stop_charge_thresh: Function not implemented</pre><br />
<br />
However, all the battery status information is available, and functions appear for both BAT0 and BAT1, regardless of when the UltraBay battery was inserted or ejected- this is very useful, it is the only way I can monitor my UltraBay battery unless it was present on boot.<br />
<br />
--[[User:SystemParadox|SystemParadox]] 21:51, 4 Jan 2006 (CET)<br />
----<br />
<br />
SystemParadox, what's the dmesg output produced by "cat BAT0/force_discharge2"?<br />
<br />
--[[User:Thinker|Thinker]] 22:02, 4 Jan 2006 (CET)<br />
----<br />
<br />
After the upgrade to 0.14 (with kernel 2.6.15, using the patch) I can't use inhibit_charge and start/stop_charge_thresh any longer (getting an input/output error), the dmesg debug output when {{cmd|cat|}}-ing those three files:<br />
<br />
<pre><br />
tp_smapi: tp_smapi 0.14 loading...<br />
tp_smapi: successfully loaded (smapi_port=0xb2).<br />
tp_smapi: req_in: BX=2114 CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=ea210080 BX=ec192114 CX=c18d0700 DX=f7cc00b2 DI=f7f50000 SI=c18d0000 ret=-5<br />
tp_smapi: SMAPI error: Unknown error code (func=2114)<br />
tp_smapi: cannot get inhibit charge of battery 0: Unknown error code<br />
tp_smapi: req_in: BX=2116 CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=c03b0080 BX=c18d2116 CX=c0160328 DX=ec7600b2 DI=ec760000 SI=a0810000 ret=-5<br />
tp_smapi: SMAPI error: Unknown error code (func=2116)<br />
tp_smapi: cannot get start thresh of battery 0: Unknown error code<br />
tp_smapi: req_in: BX=211a CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=c03b0080 BX=c18d211a CX=c016032c DX=eb4500b2 DI=eb450000 SI=241e0000 ret=-5<br />
tp_smapi: SMAPI error: Unknown error code (func=211a)<br />
tp_smapi: cannot get stop thresh of battery 0: Unknown error code<br />
</pre><br />
<br />
--[[User:Spiney|spiney]] 08:12, 10 Jan 2006 (CET)<br />
----<br />
<br />
Oops, the transition to 32-bit SMAPI calls was broken. Fixed in 0.15. Thanks for the quick report!<br />
<br />
--[[User:Thinker|Thinker]] 12:10, 10 Jan 2006 (CET)<br />
----<br />
<br />
Yep, 0.15 works again. Quick response, bravo! :)<br />
<br />
--[[User:Spiney|spiney]] 12:23, 10 Jan 2006 (CET)<br />
----<br />
<br />
On a T22, nothing seems to work with 0.16.<br />
<br />
[[http://www.rafb.net/paste/results/fcUUDs49.html|dmesg output]] when doing cat *<br />
<br />
I am using an Ultrabay2000 battery, so it would be really usefull to be able to control that<br />
<br />
--[[User:nusse|nusse]]<br />
----<br />
<br />
Nusse: Not even the extended battery status? That does work on T23. About the control features, I believe they're not available on the T23; did you have any kind of (dis)charge control under WindowS?<br />
<br />
--[[User:Thinker|Thinker]] 20:59, 11 Jan 2006 (CET)<br />
----<br />
<br />
I don't really know what 'extended battery' status means, but here an example:<br />
<pre><br />
$ cat current_* /sys/devices/platform/smapi/BAT1<br />
cat: current_avg: Input/output error<br />
cat: current_now: Input/output error<br />
</pre><br />
This is what happens when i cat any file in this directory and also in ../BAT1 :(<br />
<br />
--[[User:nusse|nusse]] Thu Jan 12 22:07:26 CET 2006<br />
----<br />
<br />
Nusse: Yes, that's what I meant. What's the {{cmdroot|dmesg}} output generated by these commands?<br />
<br />
--[[User:Thinker|Thinker]] 00:27, 13 Jan 2006 (CET)<br />
----<br />
<br />
<br />
Thinker: I attached some link to my first comment but it seems to be down and the link was wrong anyway.<br />
<pre><br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2118)<br />
tp_smapi: cannot get force_discharge of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2114)<br />
tp_smapi: cannot get inhibit charge of battery 0: Function is not supported by SMAPI BIOS<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2116)<br />
tp_smapi: cannot get start thresh of battery 0: Function is not supported by SMAPI BIOS<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=211a)<br />
tp_smapi: cannot get stop thresh of battery 0: Function is not supported by SMAPI BIOS<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
</pre><br />
<br />
--[[User:nusse|nusse]] Fri Jan 13 14:35:57 CET 2006<br />
----<br />
<br />
Nusse: Thanks; but there's not much we can do. Maybe the T22 uses a different interface, or doesn't have that feature.<br />
<br />
--[[User:Thinker|Thinker]] 23:23, 15 January 2006 (CET)<br />
----<br />
<br />
Thinker: Is there anything I can do to check if the interface is different? Changing 0x1610 to some random number?<br />
<br />
Is there a chance to get it by try and error?<br />
<br />
--[[User:nusse|nusse]] Mon Jan 16 19:10:12 CET 2006<br />
----<br />
<br />
0x1610 is the number of an IO port it writes to, so changing it to a random number will pretty much guarantee a system crash...<br />
<br />
The only way I can think of for figuring out the T22 interface is to see what the Windows software does.<br />
<br />
--[[User:Thinker|Thinker]] 19:47, 16 January 2006 (CET)<br />
----<br />
<br />
I have a R40 (2722-B3G), and several things don't work with 0.16 on linux 2.6.15.1:<br />
<br />
<pre><br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2118)<br />
tp_smapi: cannot get force_discharge of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2114)<br />
tp_smapi: cannot get inhibit charge of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2116)<br />
tp_smapi: cannot get start thresh of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=211a)<br />
tp_smapi: cannot get stop thresh of battery 0: Function is not supported by SMAPI BIOS<br />
</pre><br />
<br />
Don't know about Windows, haven't booted it for weeks nor used it for years...<br />
<br />
--[[User:Wonka|Wonka]] 19:00, 19 January 2006 (CET)<br />
----<br />
<br />
Wonka: do the other features (i.e., extended battery status) work on your R40?<br />
<br />
--[[User:Thinker|Thinker]] 20:30, 20 January 2006 (CET)<br />
----<br />
<br />
--[[User:lisch|lisch]] 16:14, 11 April 2006 (CDT)<br />
<br />
On my X32, with two batteries, I get just what I expect. Looks good:<br />
<pre>$ cat BAT?/* > /dev/null<br />
cat: BAT0/force_discharge: Function not implemented<br />
cat: BAT0/inhibit_charge_minutes: Function not implemented<br />
cat: BAT0/start_charge_thresh: Function not implemented<br />
cat: BAT0/stop_charge_thresh: Function not implemented<br />
cat: BAT1/force_discharge: Function not implemented<br />
cat: BAT1/inhibit_charge_minutes: Function not implemented<br />
cat: BAT1/start_charge_thresh: Function not implemented<br />
cat: BAT1/stop_charge_thresh: Function not implemented<br />
$<br />
</pre><br />
==Changing the CD speed when the CD is being accessed will hang your computer==<br />
<br />
I don't have this problem on my T40p. CDROM is mounted and file on CD is opened. Change speed do '''not''' hang my system.<br />
<br />
-- Stefan Schmidt<br />
----<br />
<br />
An open file looks fine if you're not reading/writing at that point. But my T43 does hangs on this:<br />
# dd if=/dev/scd0 of=/dev/null &<br />
# echo 1 > /sys/devices/platform/smapi/cdrom_speed<br />
<br />
--[[User:Thinker|Thinker]] 16:41, 7 Dec 2005 (CET)<br />
----<br />
<br />
OK, sorry. I was to fast. My system hangs on this commands, too. :(<br />
<br />
-- Stefan Schmidt<br />
<br />
Works well. Great.<br />
<br />
T42 2373-8zh. Working :cdrom_speed and start_charge_thresh. Untest : inhibit_charge_minutes.<br />
<br />
-- Haifeng Chen<br />
<br />
cdrom_speed works on my T40.<br />
<br />
-- [[User:Lammic|lammic]], 2005.12.09<br />
<br />
== Kernel Patch? ==<br />
<br />
Hello Thinker,<br />
<br />
would it be possible to provide the SMAPI support as kernel patch as well? Something along the lines of: (0.12 against 2.6.15-rc5)<br />
<br />
''(deleted, see below for how to create a patch file)''<br />
<br />
Deleted the tp_smapi.c file at the end, out of obvious reasons, and I'm not sure about the placement in the ACPI section, OTOH there it would be found easily next to ibm_acpi.<br />
<br />
Providing a patch would help when recompiling the kernel often, I hate recompiling external modules every time (even got me a kernel-upgrade script to do most of it automatically). But of course it's up to you. :)<br />
<br />
--[[User:Spiney|spiney]] 09:52, 16 Dec 2005 (CET)<br />
----<br />
<br />
I'll be glad to add this, but I don't want to go through additional manual steps in the release process (there are already quite a few). Can you add a "make patch" functionality to the Makefile, or something of the sort, to automatically generate a full patch (including tp_smapi.c) against current kernel sources?<br />
<br />
Also, this shouldn't be under drivers/acpi, since it doesn't use ACPI at all (that's why I didn't make it a patch to ibm_acpi). I think the right place is drivers/firmware, like the dell_rbu driver for Dell laptops.<br />
<br />
BTW, the convention for kernel patches is to start them once level higher:<br />
diff -Nurp kernel-2.6.14-vanilla kernel-2.6.14-patched<br />
<br />
--[[User:Thinker|Thinker]] 17:12, 16 Dec 2005 (CET)<br />
----<br />
<br />
Of course it's from the wrong level, as usual I was just lazy/inattentive. And at one point I'll remember who likes what patch format, promise. ;)<br />
<br />
A patch target as in "create a new file holding a correct diff to current kernel source" would be rather difficult, since line numbers might change etc., but applying the patch should be straighforward with a bit of sed. Of course I could just do that, create a patch with the diff command and then apply the new patch file in reverse. ;)<br />
<br />
--[[User:Spiney|spiney]] 18:36, 16 Dec 2005 (CET)<br />
----<br />
<br />
If it does that on a local copy (no changes the original kernel tree) and cleans up after itself, that's fine with me. :-)<br />
<br />
--[[User:Thinker|Thinker]] 18:50, 16 Dec 2005 (CET)<br />
----<br />
<br />
Ok, here's a shell script that creates the patch, feel free to use it under the terms of the GPL. For example call it from your Makefile with the patch target: (I didn't want to put all the script into the Makefile, since the rules about escaping in Makefiles, well, escape me ;)<br />
<br />
<pre><br />
#!/bin/bash<br />
<br />
KDIR=/lib/modules/$(uname -r)/build<br />
FDIR=drivers/firmware<br />
OPWD=$(pwd)<br />
<br />
TMPDIR=$(mktemp -d)<br />
cd $TMPDIR<br />
<br />
mkdir -p a/$FDIR<br />
cp $KDIR/$FDIR/{Kconfig,Makefile} a/$FDIR<br />
cp -r a b<br />
sed -i -e '/endmenu/i\<br />
config IBM_SMAPI\<br />
tristate "IBM ThinkPad SMAPI Support"\<br />
depends on X86\<br />
---help---\<br />
This adds SMAPI support on IBM ThinkPads, mostly used for battery\<br />
charge control. For more information about this driver see\<br />
<http://www.thinkwiki.org/wiki/SMAPI_support_for_Linux> .\<br />
\<br />
If you have an IBM ThinkPad laptop, say Y or M here.\<br />
' b/$FDIR/Kconfig<br />
sed -i -e '$a\<br />
obj-$(CONFIG_IBM_SMAPI) += tp_smapi.o' b/$FDIR/Makefile<br />
cp $OPWD/tp_smapi.c b/$FDIR<br />
diff -Nurp a b > $OPWD/tp_smapi-$(uname -r).patch<br />
rm -r a b<br />
cd $OPWD<br />
</pre><br />
<br />
BTW, [http://qbnz.com/highlighter/ GeSHi]-based syntax-highlighting would be great...<br />
<br />
--[[User:Spiney|spiney]] 19:28, 16 Dec 2005 (CET)<br />
----<br />
<br />
Ah, neat sed foo. How about [http://tpctl.sourceforge.net/tmp/Makefile this] escapade, then? <br />
<br />
What's the sed spell needed to replace the Makefile's<br />
VER := 0.13<br />
with auto-parsing of<br />
#define TP_VERSION "0.13"<br />
from tp_smapi.c?<br />
<br />
--[[User:Thinker|Thinker]] 20:37, 16 Dec 2005 (CET)<br />
----<br />
<br />
Hmm, something like<br />
VERFROMC=$(sed -ne 's/^#define TP_VERSION "\(.*\)"/\1/gp' tp_smapi.c)<br />
sed -i -e "s/^VER := .*$/VER := $VERFROMC/" Makefile<br />
should do (untested, from the top of my head, maybe the temporary variable isn't even necessary?). And neat Makefile wizardry, at one point I'll learn the syntax.<br />
<br />
--[[User:Spiney|spiney]] 20:44, 16 Dec 2005 (CET)<br />
----<br />
<br />
Makefile escaping is horrible, keep avoiding it... Anyway, the updated [http://tpctl.sourceforge.net/tmp/Makefile make patch] seems to do the right thing.<br />
<br />
--[[User:Thinker|Thinker]] 21:36, 16 Dec 2005 (CET)<br />
----<br />
<br />
Small documentation request: just needed to create a patch for the not-yet-installed 2.6.16-rc2, which is no problem with<br />
make KSRC=/path/to/linux-2.6.16-rc2 KVER=2.6.16-rc2 patch<br />
but I guess it would be a good addition to the README file. :)<br />
<br />
--[[User:Spiney|spiney]] 10:48, 8 February 2006 (CET)<br />
----<br />
<br />
Right, added (to next release).<br />
<br />
--[[User:Thinker|Thinker]] 13:40, 8 February 2006 (CET)<br />
----<br />
<br />
==Installation questions==<br />
Amazing! I've loaded this module in my T43 which is running SuSE 10 with the kernel of 2.6.13-15. I have three points to share:<br />
<br />
1. The battery control part seems to work but has a minor problem. I set the stop_charge_threshold to 70, but the battery stops charging at 55%. Don't know why and how to fix it. :P<br />
<br />
2. I don't have the cd speed control function. Here is what I have under /sys/devices/platform/smapi/:<br />
<br />
./ ../ ac_connected BAT0/ BAT1/ bus@ driver@ power/<br />
<br />
3. SuSE 10 doesn't have the necessary C files under .../drivers/hwmon/, I copied them from a 2.6.14.5 kernel source. Maybe it causes the two problems above. :(<br />
<br />
When I have time, I'll install the new kernel to see if the problems are gone and report the result.<br />
<br />
--[[User:68.51.153.96|68.51.153.96]] 04:31, 2 Jan 2006 (CET)<br />
----<br />
<br />
1. It should stop charging at 70, but will only ''start'' charging when remaining capacity has dipped below <tt>start_charge_thresh</tt>.<br />
<br />
2. See the note about PROVIDE_CD_SPEED.<br />
<br />
3. That's should be needed only for patching the HDAPS driver in order to make it compatible with tp_smapi. If your kernel (which version is it?) doens't inlude the HDAPS driver anyway, you don't need to patch....<br />
<br />
--[[User:Thinker|Thinker]] 09:28, 2 Jan 2006 (CET)<br />
----<br />
<br />
Thanks Thinker.<br />
<br />
1. I discharged and recharged the battery again. This time, it stops at 68% percent, which is pretty good.<br />
<br />
2. I missed the NOTE in README, for I just followed this wiki. :P<br />
<br />
3. My kernel version is 2.6.13-15.<br />
<br />
By the way, I just got this T43 whose model number is 266896U. I feel that the noise of the fan is much louder than my previous T21. I think it is so since it has a CPU with bigger power but am wondering if other T43 has the same big noise?<br />
<br />
--[[User:Tyne|Tyne]] 00:14, 3 Jan 2006 (CET)<br />
----<br />
<br />
The note about PROVIDE_CD_SPEED is also in the Wiki...<br />
<br />
About the T43 fan noise: yes, this is a very common (and annoying) problem. See [[Problem_with_fan_noise]] and our [[ACPI fan control script]], and send Lenovo a complaint in hope they'll fix this at the firmware level.<br />
<br />
--[[User:Thinker|Thinker]] 08:48, 3 Jan 2006 (CET)<br />
----<br />
<br />
== Formatting ==<br />
<br />
Wyrfel, that was some heavy editing you did... I agree with most changes (including the saner color choice). I did like those HINT floats, though - they keep the hints from interrupting the flow of text too much, and this particular text needs any help it can get.<br />
<br />
--[[User:Thinker|Thinker]] 17:04, 3 Jan 2006 (CET)<br />
----<br />
Hei Thinker,<br />
<br />
I'll look into it again. I felt that the floating HINTs were tearing the text apart too much. Maybe we could fix it by placing the clear marks somewhere else.<br />
<br />
[[User:Wyrfel|Wyrfel]] 18:46, 3 Jan 2006 (CET)<br />
----<br />
<br />
== Dual battery operation with tp_smapi ==<br />
<br />
It looks like it is working quite fine with tp_smapi-0.13 and 2.6.15 (it may also work with other versions, but those are the ones I have running right now).<br />
<br />
The juicy details:<br />
<br />
{{cmdroot|cd /sys/devices/platform/smapi/}}<br />
{{cmdroot|cat ac_connected}}<br />
<br />
{{cmdresult|0}}<br />
{{cmdroot|cat BAT{0,1}/state}}<br />
{{cmdresult|discharging}}<br />
{{cmdresult|idle}}<br />
<br />
{{cmdroot|echo 1 > BAT1/force_discharge1}}<br />
{{cmdroot|cat BAT{0,1}/state}}<br />
{{cmdresult|idle}}<br />
{{cmdresult|discharging}}<br />
<br />
Checking capacity values shows that the corrent battery is being depleted.<br />
<br />
And remember, before you yank the CD/DVD drive out, issue:<br />
<br />
{{cmdroot|cat eject > /proc/acpi/ibm/bay}}<br />
<br />
----<br />
<br />
Great! Which ThinkPad model is it? Could you also {{cmdroot|cat /sys/devices/platform/smapi/BAT{0,1}/force_discharge2}} and report the dmesg output (after {{cmdroot|make load}} or {{cmdroot|1=modprobe tp_smapi debug=1}})?<br />
<br />
About the eject command, I think it should be possible to do that automatically when the Ultrabay handle is ejected, via <tt>acpid</tt>.<br />
<br />
--[[User:Thinker|Thinker]] 15:45, 10 Jan 2006 (CET)<br />
----<br />
<br />
It's a T43 (2669). cat'ing force_discharge2 gives me an I/O error and I see<br />
<br />
tp_smapi: cannot get force_discharge2 of battery 0: bx=2103<br />
<br />
tp_smapi: cannot get force_discharge2 of battery 1: bx=2103<br />
<br />
I find these errors irrelevant from the user's point of view, though. <br />
<br />
Indeed, it should be possible to automatise the "eject" command. I should also be noted that once a force_discharge1 is set, it will NOT unset automatically, event when the AC is plugged back in. An obvious fix is to fiddle with the appropriate ACPI event to force_discharge1 back to 0 for all batteries once the AC is attached.<br />
<br />
----<br />
<br />
Thanks, this eliminates the last situation I imagined <tt>force_discharge2</tt> might work. The next tp_smapi version will remove <tt>force_discharge2</tt> and rename <tt>force_discharge1</tt> to <tt>force_discharge</tt>.<br />
<br />
If you write those ACPI scripts, it would be great if you put them on the Wiki.<br />
<br />
--[[User:Thinker|Thinker]] 16:31, 10 Jan 2006 (CET)<br />
----<br />
<br />
Well, I still do not preclude the fact that <tt>force_discharge2</tt> may be useful for something else on other models.<br />
<br />
The ACPI scripts (as well as an installation guide) is underway. It may take a while, though.<br />
<br />
----<br />
<br />
See the new article: [[Using an Ultrabay battery]].<br />
<br />
--[[User:Thinker|Thinker]] 17:05, 10 Jan 2006 (CET)<br />
----<br />
<br />
Hei Thinker,<br />
<br />
i just renamed the new page. Will adjust your links later on. Keeping the redirect page until that's done. Please set any new links you create to the new page (the pages of the individual UltraBay batteries should contain a pointer).<br />
<br />
On a sidenote: I would like to split the SMAPI support under Linux page into a tp_smapi driver page, just listing the features, and a "How to use tp_smapi" page. I would also split the thinkpad/tpctl page off that again. Any objections?<br />
<br />
[[User:Wyrfel|Wyrfel]] 20:42, 10 Jan 2006 (CET)<br />
----<br />
<br />
ACK about the page rename (the old one did sound a bit out of line to my ear, but I couldn't spot why...).<br />
<br />
About the splitting tp_smapi vs. thinkpad/tpctl, no objection.<br />
<br />
About splitting tp_smapi: currently most of that section doubles as both a spec and a HOWTO, which I think is a convenient and concise way to describe things (hey, it must be right, the Perl docs do it!). I'm not sure there's much benefit in duplicating that. Perhaps we should wait for a critical mass of additional lore to accumulate?<br />
<br />
--[[User:Thinker|Thinker]] 21:04, 10 Jan 2006 (CET)<br />
----<br />
Ok, i agree on the latter.<br />
<br />
[[User:Wyrfel|Wyrfel]] 00:57, 11 Jan 2006 (CET)<br />
----<br />
<br />
==Article name capitalization== <br />
<br />
Wikimedia autocapitalizes the article name upon submit. How do I concince Wikimedia that I really want a lowercase "t"? The underline is probably too much too ask...<br />
<br />
--[[User:Thinker|Thinker]] 11:03, 11 Jan 2006 (CET)<br />
----<br />
<br />
Impossible, according to [http://en.wikipedia.org/wiki/Wikipedia:Canonicalization Wikipedia:Canonicalization].<br />
<br />
--[[User:Thinker|Thinker]] 12:04, 11 Jan 2006 (CET)<br />
----<br />
<br />
==Status Table==<br />
For at least the T series i think that charge control was not supported prior to the T42, hardware/BIOS side. Perhaps "N/A" flags would be better here?<br />
<br />
I also created <nowiki>{{Isup}}</nowiki> style templates for status, they just include images, like {{Isup}}.<br />
Not emotional about it, just wanted to let you know in case you want to use them.<br />
<br />
Third and last...would it possibly be better to make the table headers more human readable like i.e. "lower charge threshold" or something like that instead of "start_charge_thresh"?<br />
<br />
[[User:Wyrfel|Wyrfel]] 19:21, 11 Jan 2006 (CET)<br />
----<br />
<br />
About "N/A", sure, if we get reliable data about the hardware capabilities. Alas, most negative reports were just "it doesn't work", and in some cases gave contradictory information (SMAPI interface says a function is unsupported but user says it works under Windows).<br />
<br />
About {{Iyes}} and friends, they're very cute, but I think think they're harder to parse visually and would add some clutter to an already dense table.<br />
<br />
The table headers are just the names of the control files - that's important to keep, sine it's the most natural lookup key. Adding friendly description would be great, if we can fit them in (not everyone has an SXGA+ display...). I tried and failed.<br />
<br />
--[[User:Thinker|Thinker]] 20:38, 11 Jan 2006 (CET)<br />
----<br />
<br />
I have a T41p and the windows tools still don't offer me battery management, even though it's quite a while since the T42 came out.<br />
<br />
I'm ok with the rest.<br />
<br />
[[User:Wyrfel|Wyrfel]] 22:35, 11 Jan 2006 (CET)<br />
----<br />
<br />
For the {{X40}}, I can report success using the stop_charge_thresh feature with BIOS v2.03 (1UETC8WW) and Embedded Controller Program v1.60 (1UHTB0WW).<br />
<br />
[[User:Peterco|Peterco]] 12:07, 28 February 2006 (CET)<br />
----<br />
<br />
For the {{T60}}, I can report that the force_discharge feature is working fine.<br />
<br />
--[[User:Gmetal|Gmetal]] 16:33, 19 January 2007 (CET)<br />
<br />
== Z60t ==<br />
<br />
Tested on Z60t. No errors using cat. Setting thresholds works. Status and capacity queries work. --[[User:Alon|Alon]] 21:44, 4 May 2006 (CEST)<br />
<br />
== Problem setting thresholds with X40 ==<br />
<br />
My X40, kernel 2.6.16 and tp_smapi 0.20. I try to set the thresholds to 40% and 90% using:<br />
<pre><br />
# echo 90 > stop_charge_thresh<br />
# echo 40 > start_charge_thresh<br />
</pre><br />
which should work, and the kernel reports from dmesg:<br />
<pre><br />
tp_smapi: successfully loaded (smapi_port=0xb2).<br />
tp_smapi: battery 0: changed start threshold to 85(+1)<br />
tp_smapi: battery 0: changed stop threshold to 90<br />
tp_smapi: battery 0: changed start threshold to 39(+1)<br />
</pre><br />
but, on confirmation here is what happens:<br />
<pre><br />
# cat stop_charge_thresh<br />
90<br />
# cat start_charge_thresh<br />
91<br />
</pre><br />
Any clues as to why start doesn't keep? Or why its always at 1 above stop_charge_thresh?<br />
<br />
--[[User:Xmm0|Xmm0]] 15:01, 17 May 2006 (CEST)<br />
----<br />
<br />
Is it any different if you first set start_charge_thresh and then stop_charge_thresh? <br />
<br />
Can you please load tp_smapi with module option "debug=1" and report the dmesg output genereated by each command?<br />
<br />
--[[User:Thinker|Thinker]] 16:31, 17 May 2006 (CEST)<br />
----<br />
<br />
== Battery daemon feedback requested ==<br />
<br />
I am writing a battery-management daemon to control charging and discharging BAT0 and BAT1 in accordance with usage patterns that extend Li-Ion and Li-Py battery life.<br />
<br />
By default, the machine fully discharges BAT1 first, and it is said that deep-cycling all the time dramatically shortens their lifetime.<br />
<br />
My Z61t is the test machine, and it is configured with two batteries, the stock 4-cell, and an "Advanced Ultrabay", which about doubles the runtime of the machine.<br />
<br />
Currently there are two "modes" of the daemon:<br />
<br />
Discharging mode.<br />
<pre><br />
* look at the "remaining_percent" values for both batteries<br />
* if one is more than THRESHOLD percent less than the other one, <br />
force discharge from the battery with more capacity left<br />
(the current value for THRESHOLD is 10%)<br />
</pre><br />
I believe the preceeding will prevent either battery from being deep-cycled disproportionately.<br />
<br />
Charging mode. I am less sure what the "right" algorithm is here. The following is a proposal.<br />
<pre><br />
* look at the "remaining_percent" values for both batteries<br />
* if one is more than THRESHOLD percent less than the other one, <br />
force charging to the battery with less capacity left<br />
* honor pre-set values in stop_charge_thresh and start_charge_thresh<br />
</pre><br />
<br />
I would like to get feedback in the form of "better" algorithms or requests for this daemon.<br />
<br />
--[[User:Zak Smith|Zak]] 19:03, 12 September 2006 (CEST)<br />
<br />
It sounds like your algorithm will indeed minimize wear on both batteries. A side benefit is that charging will toggle between the batteries, which may help keep them cooler while charging and thus prolong their life. OTOH, if you plan to occasionally swap the UltraBay battery for other devices, you may want to fully charge the system battery (up to stop_charge_thresh) first.<br />
<br />
--[[User:Thinker|Thinker]] 22:57, 12 September 2006 (CEST)<br />
<br />
<br />
I have noticed that when force_discharge is set and the batteries switch, the gnome battery monitoring applet gets totally confused about remaining runtime. Besides being a nuisance, this could presumably cause premature emergency shutduwn.<br />
<br />
I have also noticed that the reported remaining runtimes vary greatly between acpi, the applet, and /proc/acpi/battery/*/state<br />
<br />
--[[User:Zak Smith|Zak]] 21:46, 14 September 2006 (CEST)<br />
<br />
What do you mean by "acpi" vs. "/proc/acpi/battery/*/state"? <br />
<br />
The most accurate readout is probably {{path|/sys/devices/platform/smapi/BAT0/remaining_running_time}}, but I don't think any applet uses that yet.<br />
<br />
--[[User:Thinker|Thinker]] 12:07, 15 September 2006 (CEST)<br />
<br />
By acpi, I meant the output of the acpi (1) command. I'll get some comparative numbers later and post them here.<br />
<br />
--[[User:Zak Smith|Zak]] 20:37, 15 September 2006 (CEST)<br />
<br />
Odd, my version of {{path|/usr/bin/acpi}} doesn't report remaining time, just percent (which is the same as {{path|/sys/devices/platform/smapi/BAT0/remaining_percent}}).<br />
<br />
--[[User:Thinker|Thinker]] 21:32, 15 September 2006 (CEST)<br />
<br />
I have been running batteryd for a while with good results. I will upload it here shortly.<br />
<br />
I disabled the preferential charging mode, and only control discharging.<br />
<br />
--[[User:Zak Smith|Zak]] 23:15, 14 November 2006 (CET)<br />
<br />
http://demigod.org/~zak/src/batteryd.cc<br />
<br />
--[[User:Zak Smith|Zak]] 20:18, 5 December 2006 (CET)<br />
<br />
== Instructions for X60 with Bios 1.11 under Debian Etch ==<br />
<br />
Could someone please provide step-by-step instructions of how to make this work with Debian? What have I to do after apt-get install kernel-patch-tpsmapi? Thank you!<br />
<br />
--[[User:PeterBursch|PeterBursch]] 21:39, 15 September 2006 (CEST)</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=Talk:Tp_smapi&diff=27750Talk:Tp smapi2007-01-19T15:33:27Z<p>Gmetal: /* Status Table */</p>
<hr />
<div>== Feedback ==<br />
<br />
Great, great work! Really! This completely rocks. I just stopped my battery from charging at 77% and restarted charging a bit later, no problems whatsoever. BTW, this is on kernel 2.6.14.3.<br />
<br />
--[[User:Spiney|spiney]] 21:25, 5 Dec 2005 (CET)<br />
----<br />
None of the fuctions is working on my T40, kernel 2.6.14-mm2.<br />
<br />
--[[User:Lammic|lammic]], 2005.12.05<br />
<br />
Works for me on a T41 running 2.6.12-10-686 (Ubuntu 5.10).<br />
<br />
--[[User:berndtnm|berndtnm]], 2005.12.06<br />
<br />
Including stop_charge_thresh? That one seems to be missing on the T42p.<br />
<br />
--[[User:Thinker|Thinker]] 00:46, 7 Dec 2005 (CET)<br />
----<br />
<br />
tp_smapi works just fine on an R52 with Ubuntu Breezy stock kernel.<br />
<br />
--[[User:Micampe|Micampe]] 12:52, 7 Dec 2005 (CET)<br />
<br />
----<br />
<br />
''To set the thresholds for starting and stopping battery charging (in percent of current capacity):''<br />
<br />
'''current''' really? That'd be weird, I'd expect it to be percent of '''total''' capacity.<br />
<br />
--[[User:Micampe|Micampe]] 14:39, 7 Dec 2005 (CET)<br />
<br />
"Current full charge capacity", as opposed to "current remaining capacity" or "designed full charge capacity"...<br />
<br />
--[[User:Thinker|Thinker]] 15:05, 7 Dec 2005 (CET)<br />
----<br />
<br />
Battery features don't work with my T41p. I can't check this with windows. Can anybody try these features?<br />
<br />
-- Nils, 7 Dec 2005<br />
----<br />
<br />
Nils, does cdrom_speed work for you on the T41p? Could you provide the details requested in the README (dmesg etc.)?<br />
<br />
--[[User:Thinker|Thinker]] 21:57, 7 Dec 2005 (CET)<br />
----<br />
<br />
CDRom Speed seems to work. (I see no warnings, but I have to do a speed test.) Now, I've send all outputs to the email-address in the readme.<br />
<br />
-- Nils, 8 Dec 2005<br />
----<br />
<br />
All the features except the stop_charge_thresh seem to work here on a t42p. <br />
One note, the start_charge_thresh seems to really be stop_charge_thresh. Ie, If I set that to lower than my current battery %, it will never charge, <br />
and if I set it to 100 the battery charges all the way. <br />
<br />
--[[User:Nirik|Nirik]] 16 Dec 2005<br />
----<br />
<br />
Nirik, "all the features" as of which version? For example, do the force_discharge{1,2} in tp_smapi 0.12 also work for you? See the table in the article page. About start_charge, that's odd. Can you send me a log of what you did, what was the result a what was the dmesg output for each operation?<br />
<br />
--[[User:Thinker|Thinker]] 14:16, 16 Dec 2005 (CET)<br />
----<br />
<br />
System T40p:<br />
<br />
<pre><br />
fairlight:/sys/devices/platform/smapi/BAT0# echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge1<br />
fairlight:/sys/devices/platform/smapi/BAT0# echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge2<br />
fairlight:/sys/devices/platform/smapi/BAT0# dmesg <br />
tp_smapi: req_in: BX=2118 CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=8680 BX=2118 CX=100 DX=b2 DI=0 SI=0 ret=-38<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2118)<br />
tp_smapi: cannot get force_discharge1 of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: req_in: BX=2104 CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=80 BX=2103 CX=100 DX=78 DI=0 SI=0 ret=0<br />
tp_smapi: cannot get force_discharge2 of battery 0: bx=2103<br />
</pre><br />
<br />
So it seems force_discharge1 is not supported at all. But force_discharge2? By the way, i think wiki is a _very_ good idea for collecting information, but not for discussion. I would prefer a maillinglist. We can use sourceforge.<br />
<br />
--[[User|StefanSchmidt]]<br />
<br />
force_discharge2 is indicating a real error condition (bx=2103 which has bit 0x02 on), but I have no idea what the error is or how to fix it. Sorry. If you can trigger this function under Windows and have SoftICE or equivalent, maybe it can be worked out.<br />
<br />
About the Wiki discussion, I'm not sure a mailing list is justified yet, but you can use the linux-thinkpad list or the e-mail address in the README. <br />
<br />
--[[User:Thinker|Thinker]] 21:42, 16 Dec 2005 (CET)<br />
<br />
OK, then i use linux-thinkpad to get more people involved. I'am away the next weeks, but i hope to find some time to hacking on tp_smapi.<br />
<br />
--[[User:StefanSchmidt]]<br />
----<br />
<br />
Someone reported cd_speed works on T42 but on mine, it doesn't: this is 2378DXU<br />
<br />
--[[User:eBug]] 22:55, 17 Dec 2005 (CET)<br />
----<br />
<br />
eBug, how does it fail? If the file doesn't exist, it means you didn't enable PROVIDE_CD_SPEED (see the README). If it does exist, can you provide the dmesg output when you read an write to the file?<br />
<br />
--[[User:Thinker|Thinker]] 11:53, 18 Dec 2005 (CET)<br />
----<br />
<br />
To confirm:<br />
tp_smapi 0.13 works with hdaps module loaded on T41 (2373-8RG). However, force_discharge*, inhibit_charge_minutes, start_charge_thresh, stop_charge_thresh don't seem to be implemented on this model.<br />
<br />
--[[User:LJSBRokken|LJSBrokken]] 21 Dec 2005<br />
----<br />
<br />
tp_smapi version 0.13 with T23 (2647-3QG) (I have dual batteries)...<br />
<br />
None of the functions which make any changes work...<br />
<br />
<pre># cd /sys/devices/platform/smapi && cat BAT*/* > /dev/null<br />
cat: BAT0/force_discharge1: Function not implemented<br />
cat: BAT0/force_discharge2: Input/output error<br />
cat: BAT0/inhibit_charge_minutes: Function not implemented<br />
cat: BAT0/start_charge_thresh: Function not implemented<br />
cat: BAT0/stop_charge_thresh: Function not implemented<br />
cat: BAT1/force_discharge1: Function not implemented<br />
cat: BAT1/force_discharge2: Input/output error<br />
cat: BAT1/inhibit_charge_minutes: Function not implemented<br />
cat: BAT1/start_charge_thresh: Function not implemented<br />
cat: BAT1/stop_charge_thresh: Function not implemented</pre><br />
<br />
However, all the battery status information is available, and functions appear for both BAT0 and BAT1, regardless of when the UltraBay battery was inserted or ejected- this is very useful, it is the only way I can monitor my UltraBay battery unless it was present on boot.<br />
<br />
--[[User:SystemParadox|SystemParadox]] 21:51, 4 Jan 2006 (CET)<br />
----<br />
<br />
SystemParadox, what's the dmesg output produced by "cat BAT0/force_discharge2"?<br />
<br />
--[[User:Thinker|Thinker]] 22:02, 4 Jan 2006 (CET)<br />
----<br />
<br />
After the upgrade to 0.14 (with kernel 2.6.15, using the patch) I can't use inhibit_charge and start/stop_charge_thresh any longer (getting an input/output error), the dmesg debug output when {{cmd|cat|}}-ing those three files:<br />
<br />
<pre><br />
tp_smapi: tp_smapi 0.14 loading...<br />
tp_smapi: successfully loaded (smapi_port=0xb2).<br />
tp_smapi: req_in: BX=2114 CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=ea210080 BX=ec192114 CX=c18d0700 DX=f7cc00b2 DI=f7f50000 SI=c18d0000 ret=-5<br />
tp_smapi: SMAPI error: Unknown error code (func=2114)<br />
tp_smapi: cannot get inhibit charge of battery 0: Unknown error code<br />
tp_smapi: req_in: BX=2116 CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=c03b0080 BX=c18d2116 CX=c0160328 DX=ec7600b2 DI=ec760000 SI=a0810000 ret=-5<br />
tp_smapi: SMAPI error: Unknown error code (func=2116)<br />
tp_smapi: cannot get start thresh of battery 0: Unknown error code<br />
tp_smapi: req_in: BX=211a CX=100 DI=0 SI=0<br />
tp_smapi: req_out: AX=c03b0080 BX=c18d211a CX=c016032c DX=eb4500b2 DI=eb450000 SI=241e0000 ret=-5<br />
tp_smapi: SMAPI error: Unknown error code (func=211a)<br />
tp_smapi: cannot get stop thresh of battery 0: Unknown error code<br />
</pre><br />
<br />
--[[User:Spiney|spiney]] 08:12, 10 Jan 2006 (CET)<br />
----<br />
<br />
Oops, the transition to 32-bit SMAPI calls was broken. Fixed in 0.15. Thanks for the quick report!<br />
<br />
--[[User:Thinker|Thinker]] 12:10, 10 Jan 2006 (CET)<br />
----<br />
<br />
Yep, 0.15 works again. Quick response, bravo! :)<br />
<br />
--[[User:Spiney|spiney]] 12:23, 10 Jan 2006 (CET)<br />
----<br />
<br />
On a T22, nothing seems to work with 0.16.<br />
<br />
[[http://www.rafb.net/paste/results/fcUUDs49.html|dmesg output]] when doing cat *<br />
<br />
I am using an Ultrabay2000 battery, so it would be really usefull to be able to control that<br />
<br />
--[[User:nusse|nusse]]<br />
----<br />
<br />
Nusse: Not even the extended battery status? That does work on T23. About the control features, I believe they're not available on the T23; did you have any kind of (dis)charge control under WindowS?<br />
<br />
--[[User:Thinker|Thinker]] 20:59, 11 Jan 2006 (CET)<br />
----<br />
<br />
I don't really know what 'extended battery' status means, but here an example:<br />
<pre><br />
$ cat current_* /sys/devices/platform/smapi/BAT1<br />
cat: current_avg: Input/output error<br />
cat: current_now: Input/output error<br />
</pre><br />
This is what happens when i cat any file in this directory and also in ../BAT1 :(<br />
<br />
--[[User:nusse|nusse]] Thu Jan 12 22:07:26 CET 2006<br />
----<br />
<br />
Nusse: Yes, that's what I meant. What's the {{cmdroot|dmesg}} output generated by these commands?<br />
<br />
--[[User:Thinker|Thinker]] 00:27, 13 Jan 2006 (CET)<br />
----<br />
<br />
<br />
Thinker: I attached some link to my first comment but it seems to be down and the link was wrong anyway.<br />
<pre><br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2118)<br />
tp_smapi: cannot get force_discharge of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2114)<br />
tp_smapi: cannot get inhibit charge of battery 0: Function is not supported by SMAPI BIOS<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2116)<br />
tp_smapi: cannot get start thresh of battery 0: Function is not supported by SMAPI BIOS<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=211a)<br />
tp_smapi: cannot get stop thresh of battery 0: Function is not supported by SMAPI BIOS<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
thinkpad controller read(%hx,%hx): failed writing to 0x1610<br />
</pre><br />
<br />
--[[User:nusse|nusse]] Fri Jan 13 14:35:57 CET 2006<br />
----<br />
<br />
Nusse: Thanks; but there's not much we can do. Maybe the T22 uses a different interface, or doesn't have that feature.<br />
<br />
--[[User:Thinker|Thinker]] 23:23, 15 January 2006 (CET)<br />
----<br />
<br />
Thinker: Is there anything I can do to check if the interface is different? Changing 0x1610 to some random number?<br />
<br />
Is there a chance to get it by try and error?<br />
<br />
--[[User:nusse|nusse]] Mon Jan 16 19:10:12 CET 2006<br />
----<br />
<br />
0x1610 is the number of an IO port it writes to, so changing it to a random number will pretty much guarantee a system crash...<br />
<br />
The only way I can think of for figuring out the T22 interface is to see what the Windows software does.<br />
<br />
--[[User:Thinker|Thinker]] 19:47, 16 January 2006 (CET)<br />
----<br />
<br />
I have a R40 (2722-B3G), and several things don't work with 0.16 on linux 2.6.15.1:<br />
<br />
<pre><br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2118)<br />
tp_smapi: cannot get force_discharge of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2114)<br />
tp_smapi: cannot get inhibit charge of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2116)<br />
tp_smapi: cannot get start thresh of battery 0: Function is not supported by SMAPI BIOS<br />
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=211a)<br />
tp_smapi: cannot get stop thresh of battery 0: Function is not supported by SMAPI BIOS<br />
</pre><br />
<br />
Don't know about Windows, haven't booted it for weeks nor used it for years...<br />
<br />
--[[User:Wonka|Wonka]] 19:00, 19 January 2006 (CET)<br />
----<br />
<br />
Wonka: do the other features (i.e., extended battery status) work on your R40?<br />
<br />
--[[User:Thinker|Thinker]] 20:30, 20 January 2006 (CET)<br />
----<br />
<br />
--[[User:lisch|lisch]] 16:14, 11 April 2006 (CDT)<br />
<br />
On my X32, with two batteries, I get just what I expect. Looks good:<br />
<pre>$ cat BAT?/* > /dev/null<br />
cat: BAT0/force_discharge: Function not implemented<br />
cat: BAT0/inhibit_charge_minutes: Function not implemented<br />
cat: BAT0/start_charge_thresh: Function not implemented<br />
cat: BAT0/stop_charge_thresh: Function not implemented<br />
cat: BAT1/force_discharge: Function not implemented<br />
cat: BAT1/inhibit_charge_minutes: Function not implemented<br />
cat: BAT1/start_charge_thresh: Function not implemented<br />
cat: BAT1/stop_charge_thresh: Function not implemented<br />
$<br />
</pre><br />
==Changing the CD speed when the CD is being accessed will hang your computer==<br />
<br />
I don't have this problem on my T40p. CDROM is mounted and file on CD is opened. Change speed do '''not''' hang my system.<br />
<br />
-- Stefan Schmidt<br />
----<br />
<br />
An open file looks fine if you're not reading/writing at that point. But my T43 does hangs on this:<br />
# dd if=/dev/scd0 of=/dev/null &<br />
# echo 1 > /sys/devices/platform/smapi/cdrom_speed<br />
<br />
--[[User:Thinker|Thinker]] 16:41, 7 Dec 2005 (CET)<br />
----<br />
<br />
OK, sorry. I was to fast. My system hangs on this commands, too. :(<br />
<br />
-- Stefan Schmidt<br />
<br />
Works well. Great.<br />
<br />
T42 2373-8zh. Working :cdrom_speed and start_charge_thresh. Untest : inhibit_charge_minutes.<br />
<br />
-- Haifeng Chen<br />
<br />
cdrom_speed works on my T40.<br />
<br />
-- [[User:Lammic|lammic]], 2005.12.09<br />
<br />
== Kernel Patch? ==<br />
<br />
Hello Thinker,<br />
<br />
would it be possible to provide the SMAPI support as kernel patch as well? Something along the lines of: (0.12 against 2.6.15-rc5)<br />
<br />
''(deleted, see below for how to create a patch file)''<br />
<br />
Deleted the tp_smapi.c file at the end, out of obvious reasons, and I'm not sure about the placement in the ACPI section, OTOH there it would be found easily next to ibm_acpi.<br />
<br />
Providing a patch would help when recompiling the kernel often, I hate recompiling external modules every time (even got me a kernel-upgrade script to do most of it automatically). But of course it's up to you. :)<br />
<br />
--[[User:Spiney|spiney]] 09:52, 16 Dec 2005 (CET)<br />
----<br />
<br />
I'll be glad to add this, but I don't want to go through additional manual steps in the release process (there are already quite a few). Can you add a "make patch" functionality to the Makefile, or something of the sort, to automatically generate a full patch (including tp_smapi.c) against current kernel sources?<br />
<br />
Also, this shouldn't be under drivers/acpi, since it doesn't use ACPI at all (that's why I didn't make it a patch to ibm_acpi). I think the right place is drivers/firmware, like the dell_rbu driver for Dell laptops.<br />
<br />
BTW, the convention for kernel patches is to start them once level higher:<br />
diff -Nurp kernel-2.6.14-vanilla kernel-2.6.14-patched<br />
<br />
--[[User:Thinker|Thinker]] 17:12, 16 Dec 2005 (CET)<br />
----<br />
<br />
Of course it's from the wrong level, as usual I was just lazy/inattentive. And at one point I'll remember who likes what patch format, promise. ;)<br />
<br />
A patch target as in "create a new file holding a correct diff to current kernel source" would be rather difficult, since line numbers might change etc., but applying the patch should be straighforward with a bit of sed. Of course I could just do that, create a patch with the diff command and then apply the new patch file in reverse. ;)<br />
<br />
--[[User:Spiney|spiney]] 18:36, 16 Dec 2005 (CET)<br />
----<br />
<br />
If it does that on a local copy (no changes the original kernel tree) and cleans up after itself, that's fine with me. :-)<br />
<br />
--[[User:Thinker|Thinker]] 18:50, 16 Dec 2005 (CET)<br />
----<br />
<br />
Ok, here's a shell script that creates the patch, feel free to use it under the terms of the GPL. For example call it from your Makefile with the patch target: (I didn't want to put all the script into the Makefile, since the rules about escaping in Makefiles, well, escape me ;)<br />
<br />
<pre><br />
#!/bin/bash<br />
<br />
KDIR=/lib/modules/$(uname -r)/build<br />
FDIR=drivers/firmware<br />
OPWD=$(pwd)<br />
<br />
TMPDIR=$(mktemp -d)<br />
cd $TMPDIR<br />
<br />
mkdir -p a/$FDIR<br />
cp $KDIR/$FDIR/{Kconfig,Makefile} a/$FDIR<br />
cp -r a b<br />
sed -i -e '/endmenu/i\<br />
config IBM_SMAPI\<br />
tristate "IBM ThinkPad SMAPI Support"\<br />
depends on X86\<br />
---help---\<br />
This adds SMAPI support on IBM ThinkPads, mostly used for battery\<br />
charge control. For more information about this driver see\<br />
<http://www.thinkwiki.org/wiki/SMAPI_support_for_Linux> .\<br />
\<br />
If you have an IBM ThinkPad laptop, say Y or M here.\<br />
' b/$FDIR/Kconfig<br />
sed -i -e '$a\<br />
obj-$(CONFIG_IBM_SMAPI) += tp_smapi.o' b/$FDIR/Makefile<br />
cp $OPWD/tp_smapi.c b/$FDIR<br />
diff -Nurp a b > $OPWD/tp_smapi-$(uname -r).patch<br />
rm -r a b<br />
cd $OPWD<br />
</pre><br />
<br />
BTW, [http://qbnz.com/highlighter/ GeSHi]-based syntax-highlighting would be great...<br />
<br />
--[[User:Spiney|spiney]] 19:28, 16 Dec 2005 (CET)<br />
----<br />
<br />
Ah, neat sed foo. How about [http://tpctl.sourceforge.net/tmp/Makefile this] escapade, then? <br />
<br />
What's the sed spell needed to replace the Makefile's<br />
VER := 0.13<br />
with auto-parsing of<br />
#define TP_VERSION "0.13"<br />
from tp_smapi.c?<br />
<br />
--[[User:Thinker|Thinker]] 20:37, 16 Dec 2005 (CET)<br />
----<br />
<br />
Hmm, something like<br />
VERFROMC=$(sed -ne 's/^#define TP_VERSION "\(.*\)"/\1/gp' tp_smapi.c)<br />
sed -i -e "s/^VER := .*$/VER := $VERFROMC/" Makefile<br />
should do (untested, from the top of my head, maybe the temporary variable isn't even necessary?). And neat Makefile wizardry, at one point I'll learn the syntax.<br />
<br />
--[[User:Spiney|spiney]] 20:44, 16 Dec 2005 (CET)<br />
----<br />
<br />
Makefile escaping is horrible, keep avoiding it... Anyway, the updated [http://tpctl.sourceforge.net/tmp/Makefile make patch] seems to do the right thing.<br />
<br />
--[[User:Thinker|Thinker]] 21:36, 16 Dec 2005 (CET)<br />
----<br />
<br />
Small documentation request: just needed to create a patch for the not-yet-installed 2.6.16-rc2, which is no problem with<br />
make KSRC=/path/to/linux-2.6.16-rc2 KVER=2.6.16-rc2 patch<br />
but I guess it would be a good addition to the README file. :)<br />
<br />
--[[User:Spiney|spiney]] 10:48, 8 February 2006 (CET)<br />
----<br />
<br />
Right, added (to next release).<br />
<br />
--[[User:Thinker|Thinker]] 13:40, 8 February 2006 (CET)<br />
----<br />
<br />
==Installation questions==<br />
Amazing! I've loaded this module in my T43 which is running SuSE 10 with the kernel of 2.6.13-15. I have three points to share:<br />
<br />
1. The battery control part seems to work but has a minor problem. I set the stop_charge_threshold to 70, but the battery stops charging at 55%. Don't know why and how to fix it. :P<br />
<br />
2. I don't have the cd speed control function. Here is what I have under /sys/devices/platform/smapi/:<br />
<br />
./ ../ ac_connected BAT0/ BAT1/ bus@ driver@ power/<br />
<br />
3. SuSE 10 doesn't have the necessary C files under .../drivers/hwmon/, I copied them from a 2.6.14.5 kernel source. Maybe it causes the two problems above. :(<br />
<br />
When I have time, I'll install the new kernel to see if the problems are gone and report the result.<br />
<br />
--[[User:68.51.153.96|68.51.153.96]] 04:31, 2 Jan 2006 (CET)<br />
----<br />
<br />
1. It should stop charging at 70, but will only ''start'' charging when remaining capacity has dipped below <tt>start_charge_thresh</tt>.<br />
<br />
2. See the note about PROVIDE_CD_SPEED.<br />
<br />
3. That's should be needed only for patching the HDAPS driver in order to make it compatible with tp_smapi. If your kernel (which version is it?) doens't inlude the HDAPS driver anyway, you don't need to patch....<br />
<br />
--[[User:Thinker|Thinker]] 09:28, 2 Jan 2006 (CET)<br />
----<br />
<br />
Thanks Thinker.<br />
<br />
1. I discharged and recharged the battery again. This time, it stops at 68% percent, which is pretty good.<br />
<br />
2. I missed the NOTE in README, for I just followed this wiki. :P<br />
<br />
3. My kernel version is 2.6.13-15.<br />
<br />
By the way, I just got this T43 whose model number is 266896U. I feel that the noise of the fan is much louder than my previous T21. I think it is so since it has a CPU with bigger power but am wondering if other T43 has the same big noise?<br />
<br />
--[[User:Tyne|Tyne]] 00:14, 3 Jan 2006 (CET)<br />
----<br />
<br />
The note about PROVIDE_CD_SPEED is also in the Wiki...<br />
<br />
About the T43 fan noise: yes, this is a very common (and annoying) problem. See [[Problem_with_fan_noise]] and our [[ACPI fan control script]], and send Lenovo a complaint in hope they'll fix this at the firmware level.<br />
<br />
--[[User:Thinker|Thinker]] 08:48, 3 Jan 2006 (CET)<br />
----<br />
<br />
== Formatting ==<br />
<br />
Wyrfel, that was some heavy editing you did... I agree with most changes (including the saner color choice). I did like those HINT floats, though - they keep the hints from interrupting the flow of text too much, and this particular text needs any help it can get.<br />
<br />
--[[User:Thinker|Thinker]] 17:04, 3 Jan 2006 (CET)<br />
----<br />
Hei Thinker,<br />
<br />
I'll look into it again. I felt that the floating HINTs were tearing the text apart too much. Maybe we could fix it by placing the clear marks somewhere else.<br />
<br />
[[User:Wyrfel|Wyrfel]] 18:46, 3 Jan 2006 (CET)<br />
----<br />
<br />
== Dual battery operation with tp_smapi ==<br />
<br />
It looks like it is working quite fine with tp_smapi-0.13 and 2.6.15 (it may also work with other versions, but those are the ones I have running right now).<br />
<br />
The juicy details:<br />
<br />
{{cmdroot|cd /sys/devices/platform/smapi/}}<br />
{{cmdroot|cat ac_connected}}<br />
<br />
{{cmdresult|0}}<br />
{{cmdroot|cat BAT{0,1}/state}}<br />
{{cmdresult|discharging}}<br />
{{cmdresult|idle}}<br />
<br />
{{cmdroot|echo 1 > BAT1/force_discharge1}}<br />
{{cmdroot|cat BAT{0,1}/state}}<br />
{{cmdresult|idle}}<br />
{{cmdresult|discharging}}<br />
<br />
Checking capacity values shows that the corrent battery is being depleted.<br />
<br />
And remember, before you yank the CD/DVD drive out, issue:<br />
<br />
{{cmdroot|cat eject > /proc/acpi/ibm/bay}}<br />
<br />
----<br />
<br />
Great! Which ThinkPad model is it? Could you also {{cmdroot|cat /sys/devices/platform/smapi/BAT{0,1}/force_discharge2}} and report the dmesg output (after {{cmdroot|make load}} or {{cmdroot|1=modprobe tp_smapi debug=1}})?<br />
<br />
About the eject command, I think it should be possible to do that automatically when the Ultrabay handle is ejected, via <tt>acpid</tt>.<br />
<br />
--[[User:Thinker|Thinker]] 15:45, 10 Jan 2006 (CET)<br />
----<br />
<br />
It's a T43 (2669). cat'ing force_discharge2 gives me an I/O error and I see<br />
<br />
tp_smapi: cannot get force_discharge2 of battery 0: bx=2103<br />
<br />
tp_smapi: cannot get force_discharge2 of battery 1: bx=2103<br />
<br />
I find these errors irrelevant from the user's point of view, though. <br />
<br />
Indeed, it should be possible to automatise the "eject" command. I should also be noted that once a force_discharge1 is set, it will NOT unset automatically, event when the AC is plugged back in. An obvious fix is to fiddle with the appropriate ACPI event to force_discharge1 back to 0 for all batteries once the AC is attached.<br />
<br />
----<br />
<br />
Thanks, this eliminates the last situation I imagined <tt>force_discharge2</tt> might work. The next tp_smapi version will remove <tt>force_discharge2</tt> and rename <tt>force_discharge1</tt> to <tt>force_discharge</tt>.<br />
<br />
If you write those ACPI scripts, it would be great if you put them on the Wiki.<br />
<br />
--[[User:Thinker|Thinker]] 16:31, 10 Jan 2006 (CET)<br />
----<br />
<br />
Well, I still do not preclude the fact that <tt>force_discharge2</tt> may be useful for something else on other models.<br />
<br />
The ACPI scripts (as well as an installation guide) is underway. It may take a while, though.<br />
<br />
----<br />
<br />
See the new article: [[Using an Ultrabay battery]].<br />
<br />
--[[User:Thinker|Thinker]] 17:05, 10 Jan 2006 (CET)<br />
----<br />
<br />
Hei Thinker,<br />
<br />
i just renamed the new page. Will adjust your links later on. Keeping the redirect page until that's done. Please set any new links you create to the new page (the pages of the individual UltraBay batteries should contain a pointer).<br />
<br />
On a sidenote: I would like to split the SMAPI support under Linux page into a tp_smapi driver page, just listing the features, and a "How to use tp_smapi" page. I would also split the thinkpad/tpctl page off that again. Any objections?<br />
<br />
[[User:Wyrfel|Wyrfel]] 20:42, 10 Jan 2006 (CET)<br />
----<br />
<br />
ACK about the page rename (the old one did sound a bit out of line to my ear, but I couldn't spot why...).<br />
<br />
About the splitting tp_smapi vs. thinkpad/tpctl, no objection.<br />
<br />
About splitting tp_smapi: currently most of that section doubles as both a spec and a HOWTO, which I think is a convenient and concise way to describe things (hey, it must be right, the Perl docs do it!). I'm not sure there's much benefit in duplicating that. Perhaps we should wait for a critical mass of additional lore to accumulate?<br />
<br />
--[[User:Thinker|Thinker]] 21:04, 10 Jan 2006 (CET)<br />
----<br />
Ok, i agree on the latter.<br />
<br />
[[User:Wyrfel|Wyrfel]] 00:57, 11 Jan 2006 (CET)<br />
----<br />
<br />
==Article name capitalization== <br />
<br />
Wikimedia autocapitalizes the article name upon submit. How do I concince Wikimedia that I really want a lowercase "t"? The underline is probably too much too ask...<br />
<br />
--[[User:Thinker|Thinker]] 11:03, 11 Jan 2006 (CET)<br />
----<br />
<br />
Impossible, according to [http://en.wikipedia.org/wiki/Wikipedia:Canonicalization Wikipedia:Canonicalization].<br />
<br />
--[[User:Thinker|Thinker]] 12:04, 11 Jan 2006 (CET)<br />
----<br />
<br />
==Status Table==<br />
For at least the T series i think that charge control was not supported prior to the T42, hardware/BIOS side. Perhaps "N/A" flags would be better here?<br />
<br />
I also created <nowiki>{{Isup}}</nowiki> style templates for status, they just include images, like {{Isup}}.<br />
Not emotional about it, just wanted to let you know in case you want to use them.<br />
<br />
Third and last...would it possibly be better to make the table headers more human readable like i.e. "lower charge threshold" or something like that instead of "start_charge_thresh"?<br />
<br />
[[User:Wyrfel|Wyrfel]] 19:21, 11 Jan 2006 (CET)<br />
----<br />
<br />
About "N/A", sure, if we get reliable data about the hardware capabilities. Alas, most negative reports were just "it doesn't work", and in some cases gave contradictory information (SMAPI interface says a function is unsupported but user says it works under Windows).<br />
<br />
About {{Iyes}} and friends, they're very cute, but I think think they're harder to parse visually and would add some clutter to an already dense table.<br />
<br />
The table headers are just the names of the control files - that's important to keep, sine it's the most natural lookup key. Adding friendly description would be great, if we can fit them in (not everyone has an SXGA+ display...). I tried and failed.<br />
<br />
--[[User:Thinker|Thinker]] 20:38, 11 Jan 2006 (CET)<br />
----<br />
<br />
I have a T41p and the windows tools still don't offer me battery management, even though it's quite a while since the T42 came out.<br />
<br />
I'm ok with the rest.<br />
<br />
[[User:Wyrfel|Wyrfel]] 22:35, 11 Jan 2006 (CET)<br />
----<br />
<br />
For the {{X40}}, I can report success using the stop_charge_thresh feature with BIOS v2.03 (1UETC8WW) and Embedded Controller Program v1.60 (1UHTB0WW).<br />
<br />
[[User:Peterco|Peterco]] 12:07, 28 February 2006 (CET)<br />
----<br />
<br />
For the {{T60}}, I can report that the force_recharge feature is working fine.<br />
<br />
--[[User:Gmetal|Gmetal]] 16:33, 19 January 2007 (CET)<br />
<br />
== Z60t ==<br />
<br />
Tested on Z60t. No errors using cat. Setting thresholds works. Status and capacity queries work. --[[User:Alon|Alon]] 21:44, 4 May 2006 (CEST)<br />
<br />
== Problem setting thresholds with X40 ==<br />
<br />
My X40, kernel 2.6.16 and tp_smapi 0.20. I try to set the thresholds to 40% and 90% using:<br />
<pre><br />
# echo 90 > stop_charge_thresh<br />
# echo 40 > start_charge_thresh<br />
</pre><br />
which should work, and the kernel reports from dmesg:<br />
<pre><br />
tp_smapi: successfully loaded (smapi_port=0xb2).<br />
tp_smapi: battery 0: changed start threshold to 85(+1)<br />
tp_smapi: battery 0: changed stop threshold to 90<br />
tp_smapi: battery 0: changed start threshold to 39(+1)<br />
</pre><br />
but, on confirmation here is what happens:<br />
<pre><br />
# cat stop_charge_thresh<br />
90<br />
# cat start_charge_thresh<br />
91<br />
</pre><br />
Any clues as to why start doesn't keep? Or why its always at 1 above stop_charge_thresh?<br />
<br />
--[[User:Xmm0|Xmm0]] 15:01, 17 May 2006 (CEST)<br />
----<br />
<br />
Is it any different if you first set start_charge_thresh and then stop_charge_thresh? <br />
<br />
Can you please load tp_smapi with module option "debug=1" and report the dmesg output genereated by each command?<br />
<br />
--[[User:Thinker|Thinker]] 16:31, 17 May 2006 (CEST)<br />
----<br />
<br />
== Battery daemon feedback requested ==<br />
<br />
I am writing a battery-management daemon to control charging and discharging BAT0 and BAT1 in accordance with usage patterns that extend Li-Ion and Li-Py battery life.<br />
<br />
By default, the machine fully discharges BAT1 first, and it is said that deep-cycling all the time dramatically shortens their lifetime.<br />
<br />
My Z61t is the test machine, and it is configured with two batteries, the stock 4-cell, and an "Advanced Ultrabay", which about doubles the runtime of the machine.<br />
<br />
Currently there are two "modes" of the daemon:<br />
<br />
Discharging mode.<br />
<pre><br />
* look at the "remaining_percent" values for both batteries<br />
* if one is more than THRESHOLD percent less than the other one, <br />
force discharge from the battery with more capacity left<br />
(the current value for THRESHOLD is 10%)<br />
</pre><br />
I believe the preceeding will prevent either battery from being deep-cycled disproportionately.<br />
<br />
Charging mode. I am less sure what the "right" algorithm is here. The following is a proposal.<br />
<pre><br />
* look at the "remaining_percent" values for both batteries<br />
* if one is more than THRESHOLD percent less than the other one, <br />
force charging to the battery with less capacity left<br />
* honor pre-set values in stop_charge_thresh and start_charge_thresh<br />
</pre><br />
<br />
I would like to get feedback in the form of "better" algorithms or requests for this daemon.<br />
<br />
--[[User:Zak Smith|Zak]] 19:03, 12 September 2006 (CEST)<br />
<br />
It sounds like your algorithm will indeed minimize wear on both batteries. A side benefit is that charging will toggle between the batteries, which may help keep them cooler while charging and thus prolong their life. OTOH, if you plan to occasionally swap the UltraBay battery for other devices, you may want to fully charge the system battery (up to stop_charge_thresh) first.<br />
<br />
--[[User:Thinker|Thinker]] 22:57, 12 September 2006 (CEST)<br />
<br />
<br />
I have noticed that when force_discharge is set and the batteries switch, the gnome battery monitoring applet gets totally confused about remaining runtime. Besides being a nuisance, this could presumably cause premature emergency shutduwn.<br />
<br />
I have also noticed that the reported remaining runtimes vary greatly between acpi, the applet, and /proc/acpi/battery/*/state<br />
<br />
--[[User:Zak Smith|Zak]] 21:46, 14 September 2006 (CEST)<br />
<br />
What do you mean by "acpi" vs. "/proc/acpi/battery/*/state"? <br />
<br />
The most accurate readout is probably {{path|/sys/devices/platform/smapi/BAT0/remaining_running_time}}, but I don't think any applet uses that yet.<br />
<br />
--[[User:Thinker|Thinker]] 12:07, 15 September 2006 (CEST)<br />
<br />
By acpi, I meant the output of the acpi (1) command. I'll get some comparative numbers later and post them here.<br />
<br />
--[[User:Zak Smith|Zak]] 20:37, 15 September 2006 (CEST)<br />
<br />
Odd, my version of {{path|/usr/bin/acpi}} doesn't report remaining time, just percent (which is the same as {{path|/sys/devices/platform/smapi/BAT0/remaining_percent}}).<br />
<br />
--[[User:Thinker|Thinker]] 21:32, 15 September 2006 (CEST)<br />
<br />
I have been running batteryd for a while with good results. I will upload it here shortly.<br />
<br />
I disabled the preferential charging mode, and only control discharging.<br />
<br />
--[[User:Zak Smith|Zak]] 23:15, 14 November 2006 (CET)<br />
<br />
http://demigod.org/~zak/src/batteryd.cc<br />
<br />
--[[User:Zak Smith|Zak]] 20:18, 5 December 2006 (CET)<br />
<br />
== Instructions for X60 with Bios 1.11 under Debian Etch ==<br />
<br />
Could someone please provide step-by-step instructions of how to make this work with Debian? What have I to do after apt-get install kernel-patch-tpsmapi? Thank you!<br />
<br />
--[[User:PeterBursch|PeterBursch]] 21:39, 15 September 2006 (CEST)</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=User_talk:Gmetal&diff=27749User talk:Gmetal2007-01-19T09:43:42Z<p>Gmetal: </p>
<hr />
<div>=Installing Gentoo Linux 2006.1 on a Thinkpad T60=<br />
<br />
This page details my efforts on installing Gentoo Linux on my Lenovo Thinkpad T60 Model No. 2007FVG.<br />
My laptop has the following hardware configuration:<br />
<br />
* Audio: AD1981HD <br />
* 15in TFT (1400 x 1050)<br />
* Mobile Intel 945PM Express <br />
* Bluetooth<br />
* Gigabit Ethernet<br />
* Wireless LAN IEEE 802.11(a/b/g/n)<br />
* DVD-Writer <br />
* Core 2 Duo - T5600 (1.83 GHz)<br />
* 1 GB RAM<br />
* 120 GB SATA-150 HDD<br />
* Trusted Platform Module (TPM 1.2) Security Chip <br />
* Fingerprint reader <br />
* ATI Mobility Radeon X1400 PCIe (x16) 128 MB <br />
<br />
= Preliminary Steps and Gentoo Linux Setup =<br />
<br />
First step was to make space for my Linux partitions. Booted into Knoppix, resized the Windows partition (freeing about 90Gb of space for<br />
Linux) using QTParted. The hidden partition used by IBM/Lenovo for restoring the laptop was left untouched. I then created an extended partition<br />
on the free space and created the logical partitions for Linux. This machine is 64-bits, but I also wanted to be able to have a 32-bit environment. <br />
So I created two root partitions and a separate home partition. Furthermore, I also placed the directory holding the distfiles and portage into two<br />
separate partitions. All in all this is how drive was partitioned:<br />
<br />
* /dev/sda1 Windows NTFS<br />
* /dev/sda2 IBM Rescue partition<br />
* /dev/sda3 Extended partition<br />
* /dev/sda5 Boot partition<br />
* /dev/sda6 Swap artition<br />
* /dev/sda7 Portage partition<br />
* /dev/sda8 Distfiles partition<br />
* /dev/sda9 Gentoo64 root<br />
* /dev/sda10 Gentoo32 root<br />
* /dev/sda11 /home partition<br />
<br />
Once this was finished I proceeded to reboot and use the Gentoo Linux 2006.1 installation cd for the AMD64 architecture (which is what should be used <br />
for a 64-bit installation on a Core 2 Duo). <br />
<br />
=64-bit Gentoo Linux 2006.1 Installation=<br />
<br />
The installation was quite smooth and was done according to the Gentoo Handbook: [http://www.gentoo.org/doc/en/handbook/index.xml]<br />
The only glitch the kernel that I built, which was done with a manual <br />
<br />
{{cmdroot|make menuconfig}}<br />
<br />
and not with Gentoo's genkernel.<br />
Once I restarted the laptop, my kernel booted fine but was unable to mount the root partition. Turns out that it needed the following <br />
.config entries:<br />
* CONFIG_PARTITION_ADVANCED<br />
* CONFIG_MSDOS_PARTITION<br />
Once I added these entries to my .config and rebuilt the kernel, everything went fine and I booted into Linux.<br />
<br />
== Hardware Configuration ==<br />
<br />
The flags used for compiling the 64-bit partition are the following:<br />
<br />
* kde mp3 mpeg xv sdl quicktime nptl gtk gtk2 jpeg tiff nptlonly alsa qt qt3 qt4 dvd cdr dvdr aac ipv6 trutype emul-linux-x86 png X opengl<br />
<br />
The result of <br />
<br />
{{cmdroot|lspci} <br />
<br />
is the following:<br />
<br />
* 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)<br />
* 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)<br />
* 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
* 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
* 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
* 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
* 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
* 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
* 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
* 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)<br />
* 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller AHCI (rev 02)<br />
* 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
* 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
* 03:00.0 Network controller: Atheros Communications, Inc. Unknown device 0024 (rev 01)<br />
* 15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller<br />
<br />
== Hardware working out of the box ==<br />
<br />
The integrated gigabit ethernet controller works fine with the e1000 driver:<br />
<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
<br />
The USB controllers also work fine with the ehci_hcd and uhci_hcd drivers found in the kernel:<br />
<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
<br />
This version of the laptop has an integrated SATA controller, and its HDD is also SATA. To get it working<br />
you need to use the AHCI driver:<br />
<br />
* CONFIG_SATA_AHCI<br />
<br />
I also added the following Kernel options (not sure if they are needed though):<br />
<br />
* CONFIG_ATA_PIIX<br />
* CONFIG_PATA_MPIIX<br />
<br />
This laptop also includes an integrated Bluetooth adapter. It is reported as a USB device with a Broadcom<br />
Bluetooth chip. More specifically <br />
<br />
{{cmdroot|lsusb -v}}<br />
<br />
is reporting the following:<br />
<br />
* Bus 004 Device 004: ID 0a5c:2110 Broadcom Corp.<br />
* Device Descriptor:<br />
* bLength 18<br />
* bDescriptorType 1<br />
* bcdUSB 2.00<br />
* bDeviceClass 224 Wireless<br />
* bDeviceSubClass 1 Radio Frequency<br />
* bDeviceProtocol 1 Bluetooth<br />
* bMaxPacketSize0 64<br />
* idVendor 0x0a5c Broadcom Corp.<br />
* idProduct 0x2110<br />
* bcdDevice 1.00<br />
* iManufacturer 1 Broadcom Corp<br />
* iProduct 2 BCM2045B<br />
* iSerial 0<br />
* bNumConfigurations 1<br />
<br />
This device appears to be working fine by including Bluetooth support in the kernel, and using the hci_usb<br />
driver. It does not seem that for this device to work the BCM203x driver is required (it is not loaded by the kernel).<br />
To get it to work, I also needed to emerge bluez-libs and bluez-utils. I must also note that it can be turned on and off<br />
by using the laptop's Function key and F4.<br />
<br />
The audio part was a bit tricky to get it to work properly. The integrated audio chipset uses the snd_hda_intel ALSA<br />
driver (export ALSA_CARDS="hda-intel"). However, I had to use version 1.0.14_rc1 to get it to compile. Eventually, <br />
everything was working fine, but I realised that I needed to run alsaconf or restart the alsasound script each time to <br />
get sound working, because the driver wasn't being loaded correctly. Eventually I came across this post <br />
[http://www.ussg.iu.edu/hypermail/linux/kernel/0610.0/1429.html] which solved my problems. After enabling the integrated<br />
modem from the BIOS, my problem went away. <br />
<br />
HDAPS appears to be working fine. Compiled the kernel with:<br />
<br />
* CONFIG_SENSORS_HDAPS=m<br />
<br />
and emerged app-laptop/hdapsd, and it appears that IBM's HDD shock protection mechanism is working fine. You must also run:<br />
{{cmdroot|rc-update add hdapsd default}}<br />
to make the hdapsd daemon start up at boot time. <br />
<br />
== Hardware Partly working == <br />
<br />
<br />
= TODO =<br />
<br />
Finish the remaining sections</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=User_talk:Gmetal&diff=27748User talk:Gmetal2007-01-19T09:41:49Z<p>Gmetal: </p>
<hr />
<div>=Installing Gentoo Linux 2006.1 on a Thinkpad T60=<br />
<br />
This page details my efforts on installing Gentoo Linux on my Lenovo Thinkpad T60 Model No. 2007FVG.<br />
My laptop has the following hardware configuration:<br />
<br />
* Audio: AD1981HD <br />
* 15in TFT (1400 x 1050)<br />
* Mobile Intel 945PM Express <br />
* Bluetooth<br />
* Gigabit Ethernet<br />
* Wireless LAN IEEE 802.11(a/b/g/n)<br />
* DVD-Writer <br />
* Core 2 Duo - T5600 (1.83 GHz)<br />
* 1 GB RAM<br />
* 120 GB SATA-150 HDD<br />
* Trusted Platform Module (TPM 1.2) Security Chip <br />
* Fingerprint reader <br />
* ATI Mobility Radeon X1400 PCIe (x16) 128 MB <br />
<br />
= Preliminary Steps and Gentoo Linux Setup =<br />
<br />
First step was to make space for my Linux partitions. Booted into Knoppix, resized the Windows partition (freeing about 90Gb of space for<br />
Linux) using QTParted. The hidden partition used by IBM/Lenovo for restoring the laptop was left untouched. I then created an extended partition<br />
on the free space and created the logical partitions for Linux. This machine is 64-bits, but I also wanted to be able to have a 32-bit environment. <br />
So I created two root partitions and a separate home partition. Furthermore, I also placed the directory holding the distfiles and portage into two<br />
separate partitions. All in all this is how drive was partitioned:<br />
<br />
* /dev/sda1 Windows NTFS<br />
* /dev/sda2 IBM Rescue partition<br />
* /dev/sda3 Extended partition<br />
* /dev/sda5 Boot partition<br />
* /dev/sda6 Swap artition<br />
* /dev/sda7 Portage partition<br />
* /dev/sda8 Distfiles partition<br />
* /dev/sda9 Gentoo64 root<br />
* /dev/sda10 Gentoo32 root<br />
* /dev/sda11 /home partition<br />
<br />
Once this was finished I proceeded to reboot and use the Gentoo Linux 2006.1 installation cd for the AMD64 architecture (which is what should be used <br />
for a 64-bit installation on a Core 2 Duo). <br />
<br />
=64-bit Gentoo Linux 2006.1 Installation=<br />
<br />
The installation was quite smooth and was done according to the Gentoo Handbook: [http://www.gentoo.org/doc/en/handbook/index.xml]<br />
The only glitch the kernel that I built, which was done with a manual {{cmdroot|make menuconfig}} and not with Gentoo's genkernel.<br />
Once I restarted the laptop, my kernel booted fine but was unable to mount the root partition. Turns out that it needed the following <br />
.config entries:<br />
* CONFIG_PARTITION_ADVANCED<br />
* CONFIG_MSDOS_PARTITION<br />
Once I added these entries to my .config and rebuilt the kernel, everything went fine and I booted into Linux.<br />
<br />
== Hardware Configuration ==<br />
<br />
The flags used for compiling the 64-bit partition are the following:<br />
<br />
* kde mp3 mpeg xv sdl quicktime nptl gtk gtk2 jpeg tiff nptlonly alsa qt qt3 qt4 dvd cdr dvdr aac ipv6 trutype emul-linux-x86 png X opengl<br />
<br />
The result of {{cmdroot|lspci} is the following:<br />
<br />
* 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)<br />
* 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)<br />
* 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
* 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
* 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
* 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
* 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
* 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
* 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
* 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)<br />
* 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller AHCI (rev 02)<br />
* 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
* 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
* 03:00.0 Network controller: Atheros Communications, Inc. Unknown device 0024 (rev 01)<br />
* 15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller<br />
<br />
== Hardware working out of the box ==<br />
<br />
The integrated gigabit ethernet controller works fine with the e1000 driver:<br />
<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
<br />
The USB controllers also work fine with the ehci_hcd and uhci_hcd drivers found in the kernel:<br />
<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
<br />
This version of the laptop has an integrated SATA controller, and its HDD is also SATA. To get it working<br />
you need to use the AHCI driver:<br />
<br />
* CONFIG_SATA_AHCI<br />
<br />
I also added the following Kernel options (not sure if they are needed though):<br />
<br />
* CONFIG_ATA_PIIX<br />
* CONFIG_PATA_MPIIX<br />
<br />
This laptop also includes an integrated Bluetooth adapter. It is reported as a USB device with a Broadcom<br />
Bluetooth chip. More specifically {{cmdroot|lsusb -v}} is reporting the following:<br />
<br />
* Bus 004 Device 004: ID 0a5c:2110 Broadcom Corp.<br />
* Device Descriptor:<br />
* bLength 18<br />
* bDescriptorType 1<br />
* bcdUSB 2.00<br />
* bDeviceClass 224 Wireless<br />
* bDeviceSubClass 1 Radio Frequency<br />
* bDeviceProtocol 1 Bluetooth<br />
* bMaxPacketSize0 64<br />
* idVendor 0x0a5c Broadcom Corp.<br />
* idProduct 0x2110<br />
* bcdDevice 1.00<br />
* iManufacturer 1 Broadcom Corp<br />
* iProduct 2 BCM2045B<br />
* iSerial 0<br />
* bNumConfigurations 1<br />
<br />
This device appears to be working fine by including Bluetooth support in the kernel, and using the hci_usb<br />
driver. It does not seem that for this device to work the BCM203x driver is required (it is not loaded by the kernel).<br />
To get it to work, I also needed to emerge bluez-libs and bluez-utils. I must also note that it can be turned on and off<br />
by using the laptop's Function key and F4.<br />
<br />
The audio part was a bit tricky to get it to work properly. The integrated audio chipset uses the snd_hda_intel ALSA<br />
driver (export ALSA_CARDS="hda-intel"). However, I had to use version 1.0.14_rc1 to get it to compile. Eventually, <br />
everything was working fine, but I realised that I needed to run alsaconf or restart the alsasound script each time to <br />
get sound working, because the driver wasn't being loaded correctly. Eventually I came across this post <br />
[http://www.ussg.iu.edu/hypermail/linux/kernel/0610.0/1429.html] which solved my problems. After enabling the integrated<br />
modem from the BIOS, my problem went away. <br />
<br />
HDAPS appears to be working fine. Compiled the kernel with:<br />
<br />
* CONFIG_SENSORS_HDAPS=m<br />
<br />
and emerged app-laptop/hdapsd, and it appears that IBM's HDD shock protection mechanism is working fine. You must also run:<br />
{{cmdroot|rc-update add hdapsd default} to make the hdapsd daemon start up at boot time. <br />
<br />
== Hardware Partly working == <br />
<br />
<br />
= TODO =<br />
<br />
Finish the remaining sections</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=User_talk:Gmetal&diff=27719User talk:Gmetal2007-01-17T15:09:30Z<p>Gmetal: </p>
<hr />
<div>=Installing Gentoo Linux 2006.1 on a Thinkpad T60=<br />
<br />
This page details my efforts on installing Gentoo Linux on my Lenovo Thinkpad T60 Model No. 2007FVG.<br />
My laptop has the following hardware configuration:<br />
<br />
* Audio: AD1981HD <br />
* 15in TFT (1400 x 1050)<br />
* Mobile Intel 945PM Express <br />
* Bluetooth<br />
* Gigabit Ethernet<br />
* Wireless LAN IEEE 802.11(a/b/g/n)<br />
* DVD-Writer <br />
* Core 2 Duo - T5600 (1.83 GHz)<br />
* 1 GB RAM<br />
* 120 GB SATA-150 HDD<br />
* Trusted Platform Module (TPM 1.2) Security Chip <br />
* Fingerprint reader <br />
* ATI Mobility Radeon X1400 PCIe (x16) 128 MB <br />
<br />
= Preliminary Steps and Gentoo Linux Setup =<br />
<br />
First step was to make space for my Linux partitions. Booted into Knoppix, resized the Windows partition (freeing about 90Gb of space for<br />
Linux) using QTParted. The hidden partition used by IBM/Lenovo for restoring the laptop was left untouched. I then created an extended partition<br />
on the free space and created the logical partitions for Linux. This machine is 64-bits, but I also wanted to be able to have a 32-bit environment. <br />
So I created two root partitions and a separate home partition. Furthermore, I also placed the directory holding the distfiles and portage into two<br />
separate partitions. All in all this is how drive was partitioned:<br />
<br />
* /dev/sda1 Windows NTFS<br />
* /dev/sda2 IBM Rescue partition<br />
* /dev/sda3 Extended partition<br />
* /dev/sda5 Boot partition<br />
* /dev/sda6 Swap artition<br />
* /dev/sda7 Portage partition<br />
* /dev/sda8 Distfiles partition<br />
* /dev/sda9 Gentoo64 root<br />
* /dev/sda10 Gentoo32 root<br />
* /dev/sda11 /home partition<br />
<br />
Once this was finished I proceeded to reboot and use the Gentoo Linux 2006.1 installation cd for the AMD64 architecture (which is what should be used <br />
for a 64-bit installation on a Core 2 Duo). <br />
<br />
=64-bit Gentoo Linux 2006.1 Installation=<br />
<br />
The installation was quite smooth and was done according to the Gentoo Handbook: [http://www.gentoo.org/doc/en/handbook/index.xml]<br />
The only glitch the kernel that I built, which was done with a manual {{cmdroot|make menuconfig}} and not with Gentoo's genkernel.<br />
Once I restarted the laptop, my kernel booted fine but was unable to mount the root partition. Turns out that it needed the following <br />
.config entries:<br />
* CONFIG_PARTITION_ADVANCED<br />
* CONFIG_MSDOS_PARTITION<br />
Once I added these entries to my .config and rebuilt the kernel, everything went fine and I booted into Linux.<br />
<br />
== Hardware Configuration ==<br />
<br />
The flags used for compiling the 64-bit partition are the following:<br />
<br />
* kde mp3 mpeg xv sdl quicktime nptl gtk gtk2 jpeg tiff nptlonly alsa qt qt3 qt4 dvd cdr dvdr aac ipv6 trutype emul-linux-x86 png X opengl<br />
<br />
The result of {{cmdroot|lspci} is the following:<br />
<br />
* 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)<br />
* 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)<br />
* 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
* 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
* 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
* 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
* 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
* 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
* 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
* 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)<br />
* 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller AHCI (rev 02)<br />
* 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
* 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
* 03:00.0 Network controller: Atheros Communications, Inc. Unknown device 0024 (rev 01)<br />
* 15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller<br />
<br />
== Hardware working out of the box ==<br />
<br />
The integrated gigabit ethernet controller works fine with the e1000 driver:<br />
<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
<br />
The USB controllers also work fine with the ehci_hcd and uhci_hcd drivers found in the kernel:<br />
<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
<br />
This version of the laptop has an integrated SATA controller, and its HDD is also SATA. To get it working<br />
you need to use the AHCI driver:<br />
<br />
* CONFIG_SATA_AHCI<br />
<br />
I also added the following Kernel options (not sure if they are needed though):<br />
<br />
* CONFIG_ATA_PIIX<br />
* CONFIG_PATA_MPIIX<br />
<br />
This laptop also includes an integrated Bluetooth adapter. It is reported as a USB device with a Broadcom<br />
Bluetooth chip. More specifically {{cmdroot|lsusb -v}} is reporting the following:<br />
<br />
* Bus 004 Device 004: ID 0a5c:2110 Broadcom Corp.<br />
* Device Descriptor:<br />
* bLength 18<br />
* bDescriptorType 1<br />
* bcdUSB 2.00<br />
* bDeviceClass 224 Wireless<br />
* bDeviceSubClass 1 Radio Frequency<br />
* bDeviceProtocol 1 Bluetooth<br />
* bMaxPacketSize0 64<br />
* idVendor 0x0a5c Broadcom Corp.<br />
* idProduct 0x2110<br />
* bcdDevice 1.00<br />
* iManufacturer 1 Broadcom Corp<br />
* iProduct 2 BCM2045B<br />
* iSerial 0<br />
* bNumConfigurations 1<br />
<br />
This device appears to be working fine by including Bluetooth support in the kernel, and using the hci_usb<br />
driver. It does not seem that for this device to work the BCM203x driver is required (it is not loaded by the kernel).<br />
To get it to work, I also needed to emerge bluez-libs and bluez-utils. I must also note that it can be turned on and off<br />
by using the laptop's Function key and F4.<br />
<br />
The audio part was a bit tricky to get it to work properly. The integrated audio chipset uses the snd_hda_intel ALSA<br />
driver (export ALSA_CARDS="hda-intel"). However, I had to use version 1.0.14_rc1 to get it to compile. Eventually, <br />
everything was working fine, but I realised that I needed to run alsaconf or restart the alsasound script each time to <br />
get sound working, because the driver wasn't being loaded correctly. Eventually I came across this post <br />
[http://www.ussg.iu.edu/hypermail/linux/kernel/0610.0/1429.html] which solved my problems. After enabling the integrated<br />
modem from the BIOS, my problem went away. <br />
<br />
== Hardware Partly working == <br />
<br />
<br />
= TODO =<br />
<br />
Finish the remaining sections</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=User_talk:Gmetal&diff=27718User talk:Gmetal2007-01-17T15:08:19Z<p>Gmetal: </p>
<hr />
<div>=Installing Gentoo Linux 2006.1 on a Thinkpad T60=<br />
<br />
This page details my efforts on installing Gentoo Linux on my Lenovo Thinkpad T60 Model No. 2007FVG.<br />
My laptop has the following hardware configuration:<br />
<br />
* Audio: AD1981HD <br />
* 15in TFT (1400 x 1050)<br />
* Mobile Intel 945PM Express <br />
* Bluetooth<br />
* Gigabit Ethernet<br />
* Wireless LAN IEEE 802.11(a/b/g/n)<br />
* DVD-Writer <br />
* Core 2 Duo - T5600 (1.83 GHz)<br />
* 1 GB RAM<br />
* 120 GB SATA-150 HDD<br />
* Trusted Platform Module (TPM 1.2) Security Chip <br />
* Fingerprint reader <br />
* ATI Mobility Radeon X1400 PCIe (x16) 128 MB <br />
<br />
= Preliminary Steps and Gentoo Linux Setup =<br />
<br />
First step was to make space for my Linux partitions. Booted into Knoppix, resized the Windows partition (freeing about 90Gb of space for<br />
Linux) using QTParted. The hidden partition used by IBM/Lenovo for restoring the laptop was left untouched. I then created an extended partition<br />
on the free space and created the logical partitions for Linux. This machine is 64-bits, but I also wanted to be able to have a 32-bit environment. <br />
So I created two root partitions and a separate home partition. Furthermore, I also placed the directory holding the distfiles and portage into two<br />
separate partitions. All in all this is how drive was partitioned:<br />
<br />
* /dev/sda1 Windows NTFS<br />
* /dev/sda2 IBM Rescue partition<br />
* /dev/sda3 Extended partition<br />
* /dev/sda5 Boot partition<br />
* /dev/sda6 Swap artition<br />
* /dev/sda7 Portage partition<br />
* /dev/sda8 Distfiles partition<br />
* /dev/sda9 Gentoo64 root<br />
* /dev/sda10 Gentoo32 root<br />
* /dev/sda11 /home partition<br />
<br />
Once this was finished I proceeded to reboot and use the Gentoo Linux 2006.1 installation cd for the AMD64 architecture (which is what should be used <br />
for a 64-bit installation on a Core 2 Duo). <br />
<br />
=64-bit Gentoo Linux 2006.1 Installation=<br />
<br />
The installation was quite smooth and was done according to the Gentoo Handbook: [http://www.gentoo.org/doc/en/handbook/index.xml]<br />
The only glitch the kernel that I built, which was done with a manual {{cmdroot|make menuconfig}} and not with Gentoo's genkernel.<br />
Once I restarted the laptop, my kernel booted fine but was unable to mount the root partition. Turns out that it needed the following <br />
.config entries:<br />
* CONFIG_PARTITION_ADVANCED<br />
* CONFIG_MSDOS_PARTITION<br />
Once I added these entries to my .config and rebuilt the kernel, everything went fine and I booted into Linux.<br />
<br />
== Hardware Configuration ==<br />
<br />
The flags used for compiling the 64-bit partition are the following:<br />
<br />
* kde mp3 mpeg xv sdl quicktime nptl gtk gtk2 jpeg tiff nptlonly alsa qt qt3 qt4 dvd cdr dvdr aac ipv6 trutype emul-linux-x86 png X opengl<br />
<br />
The result of {{cmdroot|lspci} is the following:<br />
<br />
* 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)<br />
* 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)<br />
* 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
* 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
* 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
* 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
* 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
* 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
* 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
* 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)<br />
* 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller AHCI (rev 02)<br />
* 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
* 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
* 03:00.0 Network controller: Atheros Communications, Inc. Unknown device 0024 (rev 01)<br />
* 15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller<br />
<br />
== Hardware working out of the box ==<br />
<br />
The integrated gigabit ethernet controller works fine with the e1000 driver:<br />
<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
<br />
The USB controllers also work fine with the ehci_hcd and uhci_hcd drivers found in the kernel:<br />
<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
<br />
This version of the laptop has an integrated SATA controller, and its HDD is also SATA. To get it working<br />
you need to use the AHCI driver:<br />
<br />
* CONFIG_SATA_AHCI<br />
<br />
I also added the following Kernel options (not sure if they are needed though):<br />
<br />
* CONFIG_ATA_PIIX<br />
* CONFIG_PATA_MPIIX<br />
<br />
This laptop also includes an integrated Bluetooth adapter. It is reported as a USB device with a Broadcom<br />
Bluetooth chip. More specifically {{cmdroot|lsusb -v}} is reporting the following:<br />
<br />
* Bus 004 Device 004: ID 0a5c:2110 Broadcom Corp.<br />
* Device Descriptor:<br />
* bLength 18<br />
* bDescriptorType 1<br />
* bcdUSB 2.00<br />
* bDeviceClass 224 Wireless<br />
* bDeviceSubClass 1 Radio Frequency<br />
* bDeviceProtocol 1 Bluetooth<br />
* bMaxPacketSize0 64<br />
* idVendor 0x0a5c Broadcom Corp.<br />
* idProduct 0x2110<br />
* bcdDevice 1.00<br />
* iManufacturer 1 Broadcom Corp<br />
* iProduct 2 BCM2045B<br />
* iSerial 0<br />
* bNumConfigurations 1<br />
<br />
This device appears to be working fine by including Bluetooth support in the kernel, and using the hci_usb<br />
driver. It does not seem that for this device to work the BCM203x driver is required (it is not loaded by the kernel).<br />
To get it to work, I also needed to emerge bluez-libs and bluez-utils. I must also note that it can be turned on and off<br />
by using the laptop's Function key and F4.<br />
<br />
The audio part was a bit tricky to get it to work properly. The integrated audio chipset uses the snd_hda_intel ALSA<br />
driver (export ALSA_CARDS="hda-intel"). However, I had to use version 1.0.14_rc1 to get it to compile. Eventually, <br />
everything was working fine, but I realised that I needed to run alsaconf or restart the alsasound script each time to <br />
get sound working, because the driver wasn't being loaded correctly. Eventually I came across this post [[http://www.ussg.iu.edu/hypermail/linux/kernel/0610.0/1429.html]] which solved my problems. After enabling the integrated<br />
modem from the BIOS, my problem went away. <br />
<br />
== Hardware Partly working == <br />
<br />
<br />
= TODO =<br />
<br />
Finish the remaining sections</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=User_talk:Gmetal&diff=27713User talk:Gmetal2007-01-16T16:50:37Z<p>Gmetal: </p>
<hr />
<div>=Installing Gentoo Linux 2006.1 on a Thinkpad T60=<br />
<br />
This page details my efforts on installing Gentoo Linux on my Lenovo Thinkpad T60 Model No. 2007FVG.<br />
My laptop has the following hardware configuration:<br />
<br />
* Audio: AD1981HD <br />
* 15in TFT (1400 x 1050)<br />
* Mobile Intel 945PM Express <br />
* Bluetooth<br />
* Gigabit Ethernet<br />
* Wireless LAN IEEE 802.11(a/b/g/n)<br />
* DVD-Writer <br />
* Core 2 Duo - T5600 (1.83 GHz)<br />
* 1 GB RAM<br />
* 120 GB SATA-150 HDD<br />
* Trusted Platform Module (TPM 1.2) Security Chip <br />
* Fingerprint reader <br />
* ATI Mobility Radeon X1400 PCIe (x16) 128 MB <br />
<br />
= Preliminary Steps and Gentoo Linux Setup =<br />
<br />
First step was to make space for my Linux partitions. Booted into Knoppix, resized the Windows partition (freeing about 90Gb of space for<br />
Linux) using QTParted. The hidden partition used by IBM/Lenovo for restoring the laptop was left untouched. I then created an extended partition<br />
on the free space and created the logical partitions for Linux. This machine is 64-bits, but I also wanted to be able to have a 32-bit environment. <br />
So I created two root partitions and a separate home partition. Furthermore, I also placed the directory holding the distfiles and portage into two<br />
separate partitions. All in all this is how drive was partitioned:<br />
* /dev/sda1 Windows NTFS<br />
* /dev/sda2 IBM Rescue partition<br />
* /dev/sda3 Extended partition<br />
* /dev/sda5 Boot partition<br />
* /dev/sda6 Swap artition<br />
* /dev/sda7 Portage partition<br />
* /dev/sda8 Distfiles partition<br />
* /dev/sda9 Gentoo64 root<br />
* /dev/sda10 Gentoo32 root<br />
* /dev/sda11 /home partition<br />
Once this was finished I proceeded to reboot and use the Gentoo Linux 2006.1 installation cd for the AMD64 architecture (which is what should be used <br />
for a 64-bit installation on a Core 2 Duo). <br />
<br />
The installation was quite smooth and was done according to the Gentoo Handbook: [http://www.gentoo.org/doc/en/handbook/index.xml]<br />
The only glitch the kernel that I built, which was done with a manual {{cmdroot|make menuconfig}} and not with Gentoo's genkernel.<br />
Once I restarted the laptop, my kernel booted fine but was unable to mount the root partition. Turns out that it needed the following <br />
.config entries:<br />
* CONFIG_PARTITION_ADVANCED<br />
* CONFIG_MSDOS_PARTITION<br />
Once I added these entries to my .config and rebuilt the kernel, everything went fine and I booted into Linux.<br />
<br />
= Hardware Configuration =<br />
<br />
The flags used for compiling the 64-bit partition are the following:<br />
<br />
* kde mp3 mpeg xv sdl quicktime nptl gtk gtk2 jpeg tiff nptlonly alsa qt qt3 qt4 dvd cdr dvdr aac ipv6 trutype emul-linux-x86 png X opengl<br />
<br />
The result of {{cmdroot|lspci} is the following:<br />
<br />
* 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)<br />
* 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)<br />
* 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
* 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
* 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
* 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
* 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
* 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
* 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
* 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)<br />
* 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller AHCI (rev 02)<br />
* 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
* 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
* 03:00.0 Network controller: Atheros Communications, Inc. Unknown device 0024 (rev 01)<br />
* 15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller<br />
<br />
= Hardware working out of the box =<br />
<br />
The integrated gigabit ethernet controller works fine with the e1000 driver:<br />
<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
<br />
The USB controllers also work fine with the ehci_hcd and uhci_hcd drivers found in the kernel:<br />
<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
<br />
This version of the laptop has an integrated SATA controller, and its HDD is also SATA. To get it working<br />
you need to use the AHCI driver:<br />
<br />
* CONFIG_SATA_AHCI<br />
<br />
I also added the following Kernel options (not sure if they are needed though):<br />
<br />
* CONFIG_ATA_PIIX<br />
* CONFIG_PATA_MPIIX<br />
<br />
This laptop also includes an integrated Bluetooth adapter. It is reported as a USB device with a Broadcom<br />
Bluetooth chip. More specifically {{cmdroot|lsusb -v}} is reporting the following:<br />
<br />
* Bus 004 Device 004: ID 0a5c:2110 Broadcom Corp.<br />
* Device Descriptor:<br />
* bLength 18<br />
* bDescriptorType 1<br />
* bcdUSB 2.00<br />
* bDeviceClass 224 Wireless<br />
* bDeviceSubClass 1 Radio Frequency<br />
* bDeviceProtocol 1 Bluetooth<br />
* bMaxPacketSize0 64<br />
* idVendor 0x0a5c Broadcom Corp.<br />
* idProduct 0x2110<br />
* bcdDevice 1.00<br />
* iManufacturer 1 Broadcom Corp<br />
* iProduct 2 BCM2045B<br />
* iSerial 0<br />
* bNumConfigurations 1<br />
<br />
This device appears to be working fine by including Bluetooth support in the kernel, and using the hci_usb<br />
driver. It does not seem that for this device to work the BCM203x driver is required (it is not loaded by the kernel).<br />
To get it to work, I also needed to emerge bluez-libs and bluez-utils. I must also note that it can be turned on and off<br />
by using the laptop's Function key and F4.<br />
<br />
= Hardware Partly working = <br />
<br />
Audio, hda-intel, post in: [http://forums.gentoo.org/viewtopic-t-523577-highlight-alsaconf+alsasound.html]<br />
<br />
= TODO =<br />
<br />
Finish the remaining sections</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=User_talk:Gmetal&diff=27710User talk:Gmetal2007-01-16T15:30:51Z<p>Gmetal: </p>
<hr />
<div>=Installing Gentoo Linux 2006.1 on a Thinkpad T60=<br />
<br />
This page details my efforts on installing Gentoo Linux on my Lenovo Thinkpad T60 Model No. 2007FVG.<br />
My laptop has the following hardware configuration:<br />
<br />
* Audio: AD1981HD <br />
* 15in TFT (1400 x 1050)<br />
* Mobile Intel 945PM Express <br />
* Bluetooth<br />
* Gigabit Ethernet<br />
* Wireless LAN IEEE 802.11(a/b/g/n)<br />
* DVD-Writer <br />
* Core 2 Duo - T5600 (1.83 GHz)<br />
* 1 GB RAM<br />
* 120 GB SATA-150 HDD<br />
* Trusted Platform Module (TPM 1.2) Security Chip <br />
* Fingerprint reader <br />
* ATI Mobility Radeon X1400 PCIe (x16) 128 MB <br />
<br />
= Preliminary Steps and Gentoo Linux Setup =<br />
<br />
First step was to make space for my Linux partitions. Booted into Knoppix, resized the Windows partition (freeing about 90Gb of space for<br />
Linux) using QTParted. The hidden partition used by IBM/Lenovo for restoring the laptop was left untouched. I then created an extended partition<br />
on the free space and created the logical partitions for Linux. This machine is 64-bits, but I also wanted to be able to have a 32-bit environment. <br />
So I created two root partitions and a separate home partition. Furthermore, I also placed the directory holding the distfiles and portage into two<br />
separate partitions. All in all this is how drive was partitioned:<br />
* /dev/sda1 Windows NTFS<br />
* /dev/sda2 IBM Rescue partition<br />
* /dev/sda3 Extended partition<br />
* /dev/sda5 Boot partition<br />
* /dev/sda6 Swap artition<br />
* /dev/sda7 Portage partition<br />
* /dev/sda8 Distfiles partition<br />
* /dev/sda9 Gentoo64 root<br />
* /dev/sda10 Gentoo32 root<br />
* /dev/sda11 /home partition<br />
Once this was finished I proceeded to reboot and use the Gentoo Linux 2006.1 installation cd for the AMD64 architecture (which is what should be used <br />
for a 64-bit installation on a Core 2 Duo). <br />
<br />
The installation was quite smooth and was done according to the Gentoo Handbook: [http://www.gentoo.org/doc/en/handbook/index.xml]<br />
The only glitch the kernel that I built, which was done with a manual {{cmdroot|make menuconfig}} and not with Gentoo's genkernel.<br />
Once I restarted the laptop, my kernel booted fine but was unable to mount the root partition. Turns out that it needed the following <br />
.config entries:<br />
* CONFIG_PARTITION_ADVANCED<br />
* CONFIG_MSDOS_PARTITION<br />
Once I added these entries to my .config and rebuilt the kernel, everything went fine and I booted into Linux.<br />
<br />
= Hardware Configuration =<br />
<br />
The flags used for compiling the 64-bit partition are the following:<br />
<br />
* kde mp3 mpeg xv sdl quicktime nptl gtk gtk2 jpeg tiff nptlonly alsa qt qt3 qt4 dvd cdr dvdr aac ipv6 trutype emul-linux-x86 png X opengl<br />
<br />
The result of {{cmdroot|lspci} is the following:<br />
<br />
* 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)<br />
* 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)<br />
* 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
* 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
* 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
* 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
* 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
* 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
* 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
* 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)<br />
* 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller AHCI (rev 02)<br />
* 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
* 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
* 03:00.0 Network controller: Atheros Communications, Inc. Unknown device 0024 (rev 01)<br />
* 15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller<br />
<br />
= Hardware working out of the box =<br />
<br />
The integrated gigabit ethernet controller works fine with the e1000 driver:<br />
<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
<br />
The USB controllers also work fine with the ehci_hcd and uhci_hcd drivers found in the kernel:<br />
<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
<br />
This version of the laptop has an integrated SATA controller, and its HDD is also SATA. To get it working<br />
you need to use the AHCI driver:<br />
<br />
* CONFIG_SATA_AHCI<br />
<br />
I also added the following Kernel options (not sure if they are needed though):<br />
<br />
* CONFIG_ATA_PIIX<br />
* CONFIG_PATA_MPIIX<br />
<br />
This laptop also includes an integrated Bluetooth adapter. It is reported as a USB device with a Broadcom<br />
Bluetooth chip. More specifically {{cmdroot|lsusb -v}} is reporting the following:<br />
<br />
* Bus 004 Device 004: ID 0a5c:2110 Broadcom Corp.<br />
* Device Descriptor:<br />
* bLength 18<br />
* bDescriptorType 1<br />
* bcdUSB 2.00<br />
* bDeviceClass 224 Wireless<br />
* bDeviceSubClass 1 Radio Frequency<br />
* bDeviceProtocol 1 Bluetooth<br />
* bMaxPacketSize0 64<br />
* idVendor 0x0a5c Broadcom Corp.<br />
* idProduct 0x2110<br />
* bcdDevice 1.00<br />
* iManufacturer 1 Broadcom Corp<br />
* iProduct 2 BCM2045B<br />
* iSerial 0<br />
* bNumConfigurations 1<br />
<br />
This device appears to be working fine by including Bluetooth support in the kernel, and using the hci_usb<br />
driver. It does not seem that for this device to work the BCM203x driver is required (it is not loaded by the kernel).<br />
To get it to work, I also needed to emerge bluez-libs and bluez-utils. I must also note that it can be turned on and off<br />
by using the laptop's Function key and F4.<br />
<br />
= Hardware Partly working = <br />
<br />
Audio, hda-intel<br />
<br />
= TODO =<br />
<br />
Finish the remaining sections</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=User_talk:Gmetal&diff=27708User talk:Gmetal2007-01-16T07:44:04Z<p>Gmetal: </p>
<hr />
<div>=Installing Gentoo Linux 2006.1 on a Thinkpad T60=<br />
<br />
This page details my efforts on installing Gentoo Linux on my Lenovo Thinkpad T60 Model No. 2007FVG.<br />
My laptop has the following hardware configuration:<br />
<br />
* Audio: AD1981HD <br />
* 15in TFT (1400 x 1050)<br />
* Mobile Intel 945PM Express <br />
* Bluetooth<br />
* Gigabit Ethernet<br />
* Wireless LAN IEEE 802.11(a/b/g/n)<br />
* DVD-Writer <br />
* Core 2 Duo - T5600 (1.83 GHz)<br />
* 1 GB RAM<br />
* 120 GB SATA-150 HDD<br />
* Trusted Platform Module (TPM 1.2) Security Chip <br />
* Fingerprint reader <br />
* ATI Mobility Radeon X1400 PCIe (x16) 128 MB <br />
<br />
= Preliminary Steps and Gentoo Linux Setup =<br />
<br />
First step was to make space for my Linux partitions. Booted into Knoppix, resized the Windows partition (freeing about 90Gb of space for<br />
Linux) using QTParted. The hidden partition used by IBM/Lenovo for restoring the laptop was left untouched. I then created an extended partition<br />
on the free space and created the logical partitions for Linux. This machine is 64-bits, but I also wanted to be able to have a 32-bit environment. <br />
So I created two root partitions and a separate home partition. Furthermore, I also placed the directory holding the distfiles and portage into two<br />
separate partitions. All in all this is how drive was partitioned:<br />
* /dev/sda1 Windows NTFS<br />
* /dev/sda2 IBM Rescue partition<br />
* /dev/sda3 Extended partition<br />
* /dev/sda5 Boot partition<br />
* /dev/sda6 Swap artition<br />
* /dev/sda7 Portage partition<br />
* /dev/sda8 Distfiles partition<br />
* /dev/sda9 Gentoo64 root<br />
* /dev/sda10 Gentoo32 root<br />
* /dev/sda11 /home partition<br />
Once this was finished I proceeded to reboot and use the Gentoo Linux 2006.1 installation cd for the AMD64 architecture (which is what should be used <br />
for a 64-bit installation on a Core 2 Duo). <br />
<br />
The installation was quite smooth and was done according to the Gentoo Handbook: [http://www.gentoo.org/doc/en/handbook/index.xml]<br />
The only glitch the kernel that I built, which was done with a manual {{cmdroot|make menuconfig}} and not with Gentoo's genkernel.<br />
Once I restarted the laptop, my kernel booted fine but was unable to mount the root partition. Turns out that it needed the following <br />
.config entries:<br />
* CONFIG_PARTITION_ADVANCED<br />
* CONFIG_MSDOS_PARTITION<br />
Once I added these entries to my .config and rebuilt the kernel, everything went fine and I booted into Linux.<br />
<br />
= Hardware Configuration =<br />
<br />
The flags used for compiling the 64-bit partition are the following:<br />
<br />
* kde mp3 mpeg xv sdl quicktime nptl gtk gtk2 jpeg tiff nptlonly alsa qt qt3 qt4 dvd cdr dvdr aac ipv6 trutype emul-linux-x86 png X opengl<br />
<br />
The result of {{cmdroot|lspci} is the following:<br />
<br />
* 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)<br />
* 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)<br />
* 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
* 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
* 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
* 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
* 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
* 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
* 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
* 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)<br />
* 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller AHCI (rev 02)<br />
* 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
* 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
* 03:00.0 Network controller: Atheros Communications, Inc. Unknown device 0024 (rev 01)<br />
* 15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller<br />
<br />
= Hardware working out of the box =<br />
<br />
The integrated gigabit ethernet controller works fine with the e1000 driver:<br />
<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
<br />
The USB controllers also work fine with the ehci_hcd and uhci_hcd drivers found in the kernel:<br />
<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
<br />
This version of the laptop has an integrated SATA controller, and its HDD is also SATA. To get it working<br />
you need to use the AHCI driver:<br />
<br />
* CONFIG_SATA_AHCI<br />
<br />
I also added the following Kernel options (not sure if they are needed though):<br />
<br />
* CONFIG_ATA_PIIX<br />
* CONFIG_PATA_MPIIX</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=User_talk:Gmetal&diff=27707User talk:Gmetal2007-01-16T07:43:42Z<p>Gmetal: </p>
<hr />
<div>=Installing Gentoo Linux 2006.1 on a Thinkpad T60=<br />
<br />
This page details my efforts on installing Gentoo Linux on my Lenovo Thinkpad T60 Model No. 2007FVG.<br />
My laptop has the following hardware configuration:<br />
<br />
* Audio: AD1981HD <br />
* 15'' TFT (1400 x 1050)<br />
* Mobile Intel 945PM Express <br />
* Bluetooth<br />
* Gigabit Ethernet<br />
* Wireless LAN IEEE 802.11(a/b/g/n)<br />
* DVD-Writer <br />
* Core 2 Duo - T5600 (1.83 GHz)<br />
* 1 GB RAM<br />
* 120 GB SATA-150 HDD<br />
* Trusted Platform Module (TPM 1.2) Security Chip <br />
* Fingerprint reader <br />
* ATI Mobility Radeon X1400 PCIe (x16) 128 MB <br />
<br />
= Preliminary Steps and Gentoo Linux Setup =<br />
<br />
First step was to make space for my Linux partitions. Booted into Knoppix, resized the Windows partition (freeing about 90Gb of space for<br />
Linux) using QTParted. The hidden partition used by IBM/Lenovo for restoring the laptop was left untouched. I then created an extended partition<br />
on the free space and created the logical partitions for Linux. This machine is 64-bits, but I also wanted to be able to have a 32-bit environment. <br />
So I created two root partitions and a separate home partition. Furthermore, I also placed the directory holding the distfiles and portage into two<br />
separate partitions. All in all this is how drive was partitioned:<br />
* /dev/sda1 Windows NTFS<br />
* /dev/sda2 IBM Rescue partition<br />
* /dev/sda3 Extended partition<br />
* /dev/sda5 Boot partition<br />
* /dev/sda6 Swap artition<br />
* /dev/sda7 Portage partition<br />
* /dev/sda8 Distfiles partition<br />
* /dev/sda9 Gentoo64 root<br />
* /dev/sda10 Gentoo32 root<br />
* /dev/sda11 /home partition<br />
Once this was finished I proceeded to reboot and use the Gentoo Linux 2006.1 installation cd for the AMD64 architecture (which is what should be used <br />
for a 64-bit installation on a Core 2 Duo). <br />
<br />
The installation was quite smooth and was done according to the Gentoo Handbook: [http://www.gentoo.org/doc/en/handbook/index.xml]<br />
The only glitch the kernel that I built, which was done with a manual {{cmdroot|make menuconfig}} and not with Gentoo's genkernel.<br />
Once I restarted the laptop, my kernel booted fine but was unable to mount the root partition. Turns out that it needed the following <br />
.config entries:<br />
* CONFIG_PARTITION_ADVANCED<br />
* CONFIG_MSDOS_PARTITION<br />
Once I added these entries to my .config and rebuilt the kernel, everything went fine and I booted into Linux.<br />
<br />
= Hardware Configuration =<br />
<br />
The flags used for compiling the 64-bit partition are the following:<br />
<br />
* kde mp3 mpeg xv sdl quicktime nptl gtk gtk2 jpeg tiff nptlonly alsa qt qt3 qt4 dvd cdr dvdr aac ipv6 trutype emul-linux-x86 png X opengl<br />
<br />
The result of {{cmdroot|lspci} is the following:<br />
<br />
* 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)<br />
* 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)<br />
* 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
* 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
* 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
* 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
* 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
* 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
* 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
* 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)<br />
* 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller AHCI (rev 02)<br />
* 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
* 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
* 03:00.0 Network controller: Atheros Communications, Inc. Unknown device 0024 (rev 01)<br />
* 15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller<br />
<br />
= Hardware working out of the box =<br />
<br />
The integrated gigabit ethernet controller works fine with the e1000 driver:<br />
<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
<br />
The USB controllers also work fine with the ehci_hcd and uhci_hcd drivers found in the kernel:<br />
<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
<br />
This version of the laptop has an integrated SATA controller, and its HDD is also SATA. To get it working<br />
you need to use the AHCI driver:<br />
<br />
* CONFIG_SATA_AHCI<br />
<br />
I also added the following Kernel options (not sure if they are needed though):<br />
<br />
* CONFIG_ATA_PIIX<br />
* CONFIG_PATA_MPIIX</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=User_talk:Gmetal&diff=27706User talk:Gmetal2007-01-16T07:41:07Z<p>Gmetal: </p>
<hr />
<div>=Installing Gentoo Linux 2006.1 on a Thinkpad T60=<br />
<br />
This page details my efforts on installing Gentoo Linux on my Lenovo Thinkpad T60 Model No. 2007FVG.<br />
My laptop has the following hardware configuration:<br />
<br />
* Audio: AD1981HD <br />
* 15'' TFT (1400 x 1050)<br />
* Mobile Intel 945PM Express <br />
* Bluetooth<br />
* Gigabit Ethernet<br />
* Wireless LAN IEEE 802.11(a/b/g/n)<br />
* DVD-Writer <br />
* Core 2 Duo - T5600 (1.83 GHz)<br />
* 1 GB RAM<br />
* 120 GB SATA-150 HDD<br />
* Trusted Platform Module (TPM 1.2) Security Chip <br />
* Fingerprint reader <br />
* ATI Mobility Radeon X1400 PCIe (x16) 128 MB <br />
<br />
== Preliminary Steps and Gentoo Linux Setup ==<br />
<br />
First step was to make space for my Linux partitions. Booted into Knoppix, resized the Windows partition (freeing about 90Gb of space for<br />
Linux) using QTParted. The hidden partition used by IBM/Lenovo for restoring the laptop was left untouched. I then created an extended partition<br />
on the free space and created the logical partitions for Linux. This machine is 64-bits, but I also wanted to be able to have a 32-bit environment. <br />
So I created two root partitions and a separate home partition. Furthermore, I also placed the directory holding the distfiles and portage into two<br />
separate partitions. All in all this is how drive was partitioned:<br />
* /dev/sda1 Windows NTFS<br />
* /dev/sda2 IBM Rescue partition<br />
* /dev/sda3 Extended partition<br />
* /dev/sda5 Boot partition<br />
* /dev/sda6 Swap artition<br />
* /dev/sda7 Portage partition<br />
* /dev/sda8 Distfiles partition<br />
* /dev/sda9 Gentoo64 root<br />
* /dev/sda10 Gentoo32 root<br />
* /dev/sda11 /home partition<br />
Once this was finished I proceeded to reboot and use the Gentoo Linux 2006.1 installation cd for the AMD64 architecture (which is what should be used <br />
for a 64-bit installation on a Core 2 Duo). <br />
<br />
The installation was quite smooth and was done according to the Gentoo Handbook: [http://www.gentoo.org/doc/en/handbook/index.xml]<br />
The only glitch the kernel that I built, which was done with a manual {{cmdroot|make menuconfig}} and not with Gentoo's genkernel.<br />
Once I restarted the laptop, my kernel booted fine but was unable to mount the root partition. Turns out that it needed the following <br />
.config entries:<br />
* CONFIG_PARTITION_ADVANCED<br />
* CONFIG_MSDOS_PARTITION<br />
Once I added these entries to my .config and rebuilt the kernel, everything went fine and I booted into Linux.<br />
<br />
== Hardware Configuration ==<br />
<br />
The flags used for compiling the 64-bit partition are the following:<br />
<br />
* kde mp3 mpeg xv sdl quicktime nptl gtk gtk2 jpeg tiff nptlonly alsa qt qt3 qt4 dvd cdr dvdr aac ipv6 trutype emul-linux-x86 png X opengl<br />
<br />
The result of {{cmdroot|lspci} is the following:<br />
<br />
* 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)<br />
* 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)<br />
* 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)<br />
* 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)<br />
* 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)<br />
* 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)<br />
* 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
* 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)<br />
* 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)<br />
* 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)<br />
* 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller AHCI (rev 02)<br />
* 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)<br />
* 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
* 03:00.0 Network controller: Atheros Communications, Inc. Unknown device 0024 (rev 01)<br />
* 15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller<br />
<br />
== Hardware working out of the box ==<br />
<br />
The integrated gigabit ethernet controller works fine with the e1000 driver:<br />
<br />
* 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller<br />
<br />
The USB controllers also work fine with the ehci_hcd and uhci_hcd drivers found in the kernel:<br />
<br />
* 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)<br />
* 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)<br />
* 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)<br />
* 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)<br />
* 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)<br />
<br />
This version of the laptop has an integrated SATA controller, and its HDD is also SATA. To get it working<br />
you need to use the AHCI driver:<br />
<br />
* CONFIG_SATA_AHCI<br />
<br />
I also added the following Kernel options (not sure if they are needed though):<br />
<br />
* CONFIG_ATA_PIIX<br />
* CONFIG_PATA_MPIIX</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=User_talk:Gmetal&diff=27703User talk:Gmetal2007-01-15T15:11:21Z<p>Gmetal: </p>
<hr />
<div>=Installing Gentoo Linux 2006.1 on a Thinkpad T60=<br />
<br />
This page details my efforts on installing Gentoo Linux on my Lenovo Thinkpad T60 Model No. 2007FVG.<br />
My laptop has the following hardware configuration:<br />
<br />
* Audio: AD1981HD <br />
* 15'' TFT (1400 x 1050)<br />
* Mobile Intel 945PM Express <br />
* Bluetooth<br />
* Gigabit Ethernet<br />
* Wireless LAN IEEE 802.11(a/b/g/n)<br />
* DVD-Writer <br />
* Core 2 Duo - T5600 (1.83 GHz)<br />
* 1 GB RAM<br />
* 120 GB SATA-150 HDD<br />
* Trusted Platform Module (TPM 1.2) Security Chip <br />
* Fingerprint reader <br />
* ATI Mobility Radeon X1400 PCIe (x16) 128 MB <br />
<br />
== Preliminary Steps and Gentoo Linux Setup ==<br />
<br />
First step was to make space for my Linux partitions. Booted into Knoppix, resized the Windows partition (freeing about 90Gb of space for<br />
Linux) using QTParted. The hidden partition used by IBM/Lenovo for restoring the laptop was left untouched. I then created an extended partition<br />
on the free space and created the logical partitions for Linux. This machine is 64-bits, but I also wanted to be able to have a 32-bit environment. <br />
So I created two root partitions and a separate home partition. Furthermore, I also placed the directory holding the distfiles and portage into two<br />
separate partitions. All in all this is how drive was partitioned:<br />
* /dev/sda1 Windows NTFS<br />
* /dev/sda2 IBM Rescue partition<br />
* /dev/sda3 Extended partition<br />
* /dev/sda5 Boot partition<br />
* /dev/sda6 Swap artition<br />
* /dev/sda7 Portage partition<br />
* /dev/sda8 Distfiles partition<br />
* /dev/sda9 Gentoo64 root<br />
* /dev/sda10 Gentoo32 root<br />
* /dev/sda11 /home partition<br />
Once this was finished I proceeded to reboot and use the Gentoo Linux 2006.1 installation cd for the AMD64 architecture (which is what should be used <br />
for a 64-bit installation on a Core 2 Duo). <br />
<br />
The installation was quite smooth and was done according to the Gentoo Handbook: [http://www.gentoo.org/doc/en/handbook/index.xml]<br />
The only glitch the kernel that I built, which was done with a manual {{cmdroot|make menuconfig}} and not with Gentoo's genkernel.<br />
Once I restarted the laptop, my kernel booted fine but was unable to mount the root partition. Turns out that it needed the following <br />
.config entries:<br />
* CONFIG_PARTITION_ADVANCED<br />
* CONFIG_MSDOS_PARTITION<br />
Once I added these entries to my .config and rebuilt the kernel, everything went fine and I booted into Linux.</div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=User_talk:Gmetal&diff=27702User talk:Gmetal2007-01-15T14:37:03Z<p>Gmetal: </p>
<hr />
<div></div>Gmetalhttps://www.thinkwiki.org/w/index.php?title=User_talk:Gmetal&diff=27701User talk:Gmetal2007-01-15T14:34:45Z<p>Gmetal: </p>
<hr />
<div>=Installing Gentoo Linux 2006.1 on a Thinkpad T60=<br />
<br />
This document details my efforts on installing Gentoo Linux on my Lenovo Thinkpad T60 Model No. 2007FVG.</div>Gmetal