https://www.thinkwiki.org/w/api.php?action=feedcontributions&user=80.42.236.205&feedformat=atomThinkWiki - User contributions [en]2024-03-29T05:48:51ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=Talk:SMAPI_support_for_Linux&diff=14177Talk:SMAPI support for Linux2006-01-04T20:55:41Z<p>80.42.236.205: /* Feedback */</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 />
==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 />
== "thinkpad" module kernel compatibility ==<br />
<br />
Ajunge, how do you compile the "thinkpad" module compile on kernel >=2.6.9? The latest thinkpad version (5.8) still uses "get_cpu_ptr" and "set_cpu_ptr", which were removed in 2.6.9.<br />
<br />
--[[User:Thinker|Thinker]] 13:53, 10 Dec 2005 (CET)<br />
----<br />
<br />
The Debian thinkpad-source package in unstable (version 5.8-4) works just fine; I'm compiling it with 2.6.14 without any problems. And get_cpu_ptr is present; it's defined in include/linux/percpu.h.<br />
<br />
--[[User:TedTso|TedTso]] 18:56, 17 Dec 2005 (EDT)<br />
----<br />
<br />
Stock thinkpad_5.8.tar.gz doesn't #include percpu.h anyway, and doesn't compile on vanilla 2.6.14.3 or 2.6.15-rc5. Maybe Debian patched it? In that case the article page should ref the patch.<br />
<br />
--[[User:Thinker|Thinker]] 11:50, 18 Dec 2005 (CET)<br />
----<br />
<br />
Oops, my mistake. I forgot that I had patched my copy of thinkpadpm.c. I replaced the use of get_cpu_ptr and set_cpu_ptr with get_cpu_val() and set_cpu_val(). I just double checked, and it tpctl is working for me on 2.6.15-rc5.<br />
<br />
--[[User:TedTso|TedTso]] 14:45, 19 Dec 2005 (EDT)<br />
----<br />
<br />
Care to send a patch? It would be useful on the article page, and maybe we can get it into upstream.<br />
<br />
--[[User:Thinker|Thinker]] 23:11, 19 Dec 2005 (CET)<br />
----<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 />
==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 />
----</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=Talk:SMAPI_support_for_Linux&diff=14176Talk:SMAPI support for Linux2006-01-04T20:51:13Z<p>80.42.236.205: /* Feedback */</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 />
{{cmdroot|cd /sys/devices/platform/smapi && cat BAT*/* > /dev/null}}<br />
{{cmdresult|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}}<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:80.42.236.205|80.42.236.205]] 21:51, 4 Jan 2006 (CET)<br />
----<br />
<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 />
== "thinkpad" module kernel compatibility ==<br />
<br />
Ajunge, how do you compile the "thinkpad" module compile on kernel >=2.6.9? The latest thinkpad version (5.8) still uses "get_cpu_ptr" and "set_cpu_ptr", which were removed in 2.6.9.<br />
<br />
--[[User:Thinker|Thinker]] 13:53, 10 Dec 2005 (CET)<br />
----<br />
<br />
The Debian thinkpad-source package in unstable (version 5.8-4) works just fine; I'm compiling it with 2.6.14 without any problems. And get_cpu_ptr is present; it's defined in include/linux/percpu.h.<br />
<br />
--[[User:TedTso|TedTso]] 18:56, 17 Dec 2005 (EDT)<br />
----<br />
<br />
Stock thinkpad_5.8.tar.gz doesn't #include percpu.h anyway, and doesn't compile on vanilla 2.6.14.3 or 2.6.15-rc5. Maybe Debian patched it? In that case the article page should ref the patch.<br />
<br />
--[[User:Thinker|Thinker]] 11:50, 18 Dec 2005 (CET)<br />
----<br />
<br />
Oops, my mistake. I forgot that I had patched my copy of thinkpadpm.c. I replaced the use of get_cpu_ptr and set_cpu_ptr with get_cpu_val() and set_cpu_val(). I just double checked, and it tpctl is working for me on 2.6.15-rc5.<br />
<br />
--[[User:TedTso|TedTso]] 14:45, 19 Dec 2005 (EDT)<br />
----<br />
<br />
Care to send a patch? It would be useful on the article page, and maybe we can get it into upstream.<br />
<br />
--[[User:Thinker|Thinker]] 23:11, 19 Dec 2005 (CET)<br />
----<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 />
==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 />
----</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=Ultrabay_2000_Battery&diff=14494Ultrabay 2000 Battery2006-01-04T14:51:48Z<p>80.42.236.205: </p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== UltraBay 2000 Battery ===<br />
This is a battery that slides into a supported UltraBay 2000.<br />
<br />
=== Features ===<br />
* 10.8V Lithium-Ion<br />
* 9 cells<br />
* Up to 3 hours of battery life<br />
* Weight: 268g (0.59 lbs)<br />
* Charge time: 2.0 h<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:ultrabay2000battery.gif|UltraBay 2000 Battery]]<br />
|}<br />
<br />
=== IBM Partnumbers ===<br />
*Marketing PN: 02K6646<br />
*FRU PN: 02K6645<br />
<br />
=== Linux Support ===<br />
The second battery is correctly detected by either the APM or ACPI subsystem. However, the Linux ACPI subsystem only scans for batteries on boot. This means that the second battery must be present at boot time, or you will not be able to get any info for it via {{path|/proc/acpi/battery/BAT1}}.<br />
<br />
With kernel 2.6.14.2 (possibly only with [[ibm-acpi]]) there is a sysfs file: {{path|/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject}}. There isn't one for BAT0, but {{cmdroot|cat /proc/acpi/battery/BAT0/*}} shows {{cmdresult|not present}} when there is no internal battery. <br />
<br />
For BAT1 all the states go to 0, critical, etc. .<br />
<br />
{{cmdroot|echo 1 > /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject}} will remove {{path|/proc/acpi/battery/BAT1}} and turn off the UltraBay led. Interestingly the battery will still be discharging (charging not tested) until it is physically removed.<br />
<br />
Also, if you compile the battery module of ACPI as a module, boot with the UltraBay battery present, remove the UltraBay battery (without doing the eject above), {{path|/proc/acpi/battery/BAT1}} is still there, while after {{cmdroot|rmmod battery && modprobe battery}} {{path|/proc/acpi/battery/BAT1}} is gone (BAT0 is back). Put the battery back in and {{path|/proc/acpi/battery/BAT1}} is still missing, do {{cmdroot|rmmod battery && modprobe battery}} and {{path|/proc/acpi/battery/BAT1}} is back.<br />
<br />
If you boot without the second battery <tt>BAT1</tt> never appears in {{path|/proc}} or {{path|/sys}}.<br />
<br />
If you eject using the sysfs file above, <tt>BAT1</tt> disappears from both {{path|/proc}} and {{path|/sys}} and never comes back.<br />
<br />
Fortunately, the battery status is accessible independently of the ACPI system. The [[SMAPI support for Linux|tp_smapi]] module gives battery status (and other features) via the sysfs interface in {{path|/sys/devices/platform/smapi/BAT{0,1}}}. The BAT1 interface is always present, regardless of whether the battery is present, was present on boot, or was ejected using the sysfs interface above.<br />
<br />
Unfortunately, all battery monitor scripts/applets currently use the ACPI interface to get battery status information.<br />
<br />
Test machine: T23.<br />
<br />
=== Battery Control ===<br />
<br />
The system only charges/discharges one battery at a time.<br />
If you have both batteries present, the system will completely deplete the UltraBay battery before using the main battery.<br />
When charging, the system will completely charge the main battery before it starts on the UltraBay battery.<br />
<br />
{{WARN|You need to keep an eye on the charge in the UltraBay battery and physically remove it from the bay when it gets too low. Failure to do so will result in the system completely discharging the UltraBay battery. This will significantly reduce the lifetime of your battery. }}<br />
<br />
Switching between the batteries is instant, so if you pull the UltraBay battery from the bay when it is being discharged, the system will instantly switch to the main battery. You can therefore use the UltraBay battery to hot-swap the main battery (i.e., replace it without the need to reboot, hibernate or use an external power adapter).<br />
<br />
Someone suggested that the [[SMAPI support for Linux|tp_smapi]] module could be used to control which battery gets used first. As of tp_smapi-0.13, the only way this could be possible is using <tt>force_discharge</tt>. But none of the functions to manipulate the battery are implemented on the T23 (may work on T30 though).<br />
<br />
=== Supported with ===<br />
*ThinkPad {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{A30p}}, {{A31}}, {{A31p}}<br />
*ThinkPad {{R30}}, {{R31}}, {{R32}}, {{R40}}<br />
*ThinkPad {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}<br />
<br />
<br />
[[Category:Components]]</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=Ultrabay_2000_Battery&diff=14149Ultrabay 2000 Battery2006-01-04T14:00:20Z<p>80.42.236.205: /* Linux Support */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== UltraBay 2000 Battery ===<br />
This is a battery that slides into a supported UltraBay 2000.<br />
<br />
=== Features ===<br />
* 10.8V Lithium-Ion<br />
* 9 cells<br />
* Up to 3 hours of battery life<br />
* Weight: 268g (0.59 lbs)<br />
* Charge time: 2.0 h<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:ultrabay2000battery.gif|UltraBay 2000 Battery]]<br />
|}<br />
<br />
=== IBM Partnumbers ===<br />
*Marketing PN: 02K6646<br />
*FRU PN: 02K6645<br />
<br />
=== Linux Support ===<br />
The second battery is correctly detected by either the APM or ACPI subsystem. However, the Linux ACPI subsystem only scans for batteries on boot. This means that the second battery must be present at boot time, or you will not be able to get any info for it via {{path|/proc/acpi/battery/BAT1}}.<br />
<br />
With kernel 2.6.14.2 (possibly only with [[ibm-acpi]]) there is a sysfs file: {{path|/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject}}. There isn't one for BAT0, but {{cmdroot|cat /proc/acpi/battery/BAT0/*}} shows {{cmdresult|not present}} when there is no internal battery. <br />
<br />
For BAT1 all the states go to 0, critical, etc. .<br />
<br />
{{cmdroot|echo 1 > /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject}} will remove {{path|/proc/acpi/battery/BAT1}} and turn off the UltraBay led. Interestingly the battery will still be discharging (charging not tested) until it is physically removed.<br />
<br />
Also, if you compile the battery module of ACPI as a module, boot with the UltraBay battery present, remove the UltraBay battery (without doing the eject above), {{path|/proc/acpi/battery/BAT1}} is still there, while after {{cmdroot|rmmod battery && modprobe battery}} {{path|/proc/acpi/battery/BAT1}} is gone (BAT0 is back). Put the battery back in and {{path|/proc/acpi/battery/BAT1}} is still missing, do {{cmdroot|rmmod battery && modprobe battery}} and {{path|/proc/acpi/battery/BAT1}} is back.<br />
<br />
If you boot without the second battery <tt>BAT1</tt> never appears in {{path|/proc}} or {{path|/sys}}.<br />
<br />
If you eject using the sysfs file above, <tt>BAT1</tt> disappears from both {{path|/proc}} and {{path|/sys}} and never comes back.<br />
<br />
Fortunately, the battery status is accessible independently of the ACPI system. The [[SMAPI support for Linux|tp_smapi]] module gives battery status (and other features) via the sysfs interface in {{path|/sys/devices/platform/smapi/BAT{0,1}}}. The BAT1 interface is always present, regardless of whether the battery is present, was present on boot, or was ejected using the sysfs interface above.<br />
<br />
Unfortunately, all battery monitor scripts/applets currently use the ACPI interface to get battery status information.<br />
<br />
Test machine: T23.<br />
<br />
=== Supported with ===<br />
*ThinkPad {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{A30p}}, {{A31}}, {{A31p}}<br />
*ThinkPad {{R30}}, {{R31}}, {{R32}}, {{R40}}<br />
*ThinkPad {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}<br />
<br />
<br />
[[Category:Components]]</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=Ultrabay&diff=14019Ultrabay2006-01-03T16:41:23Z<p>80.42.236.205: /* Linux Support */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:UltraBay.jpg|UltraBay drives]] __NOTOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== IBM UltraBay ===<br />
UltraBay{{footnote|1}} is IBM's name for the swapable drive slot. With IBMs words: "The ThinkPad UltraBay, also standard with the system, is an intelligent bay that switches its pinout signals to allow the installation of standard and optional features in what would normally be just the FDD bay." Introduced back in the times of the 770 Thinkpads, this technology has gone through redesigns with almost every new generation of Thinkpad models, possibly leading to some confusion that is hopefully cleared up here. The following table gives an overview of the different UltraBay types, in which models they occurred and what drives are available for them.<br />
Note that the optical drive bay in G series Thinkpads is not an UltraBay in that the drives are fixed and not removable.<br />
<br />
On the media side different UltraBays relate to the form factor of the drives they accept, e.g early A, T and X series models can accept UltraBay devices up to 12.5mm in thickness, whereas current T and X series machines are limited to devices no more than 9.5mm thick.<br />
</div><br />
|}<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|+Overview over UltraBay types and available devices<br />
! width=140px|UltraBay Type !! featured in !! available drives (see [[UltraBay Devices]] for details)<br />
<br />
|-<br />
| [[Image:Icon20_ultrabay.png]] UltraBay || {{355}}, {{355C}}, {{355Cs}}, {{360}}, {{360C}}, {{360Cs}}, {{360P}}, {{360CE}}, {{360CSE}}, {{360PE}}, {{370C}}, {{750}}, {{750C}}, {{750Cs}}, {{750P}}, {{755C}}, {{755CE}}, {{755Cs}}, {{755CSE}}, {{755CV}}, {{755CX}}, {{760C}}, {{760L}}, {{760E}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], 2.88 MB diskette, PCMCIA Cartridge, IBM Wireless Modem ARDIS, IBM Wireless Modem<br />
|-<br />
| [[Image:Icon20_ultrabay.png]] UltraBay Thick|| {{755CD}}, {{755CDV}}, {{760CD}}, {{760E}}, {{760ED}}, {{760EL}}, {{760ELD}}, {{760LD}}, {{760XD}}, {{760XL}}, {{765D}}, {{765L}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], 2.88 MB diskette, PCMCIA Cartridge, IBM Wireless Modem ARDIS, IBM Wireless Modem<br />
|-<br />
| [[Image:Icon20_ultrabayii.png]] UltraBay II || {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}, [[SelectaDock III]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayfx.png]] UltraBay FX|| {{390}}, {{390E}}, {{390X}}, {{i1720}}, {{i1721}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultraslimbay.png]] UltraslimBay || {{600}}, {{600E}}, {{600X}}, [[UltraBase]], [[Portable Drive Bay]]|| [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabay2000.png]] UltraBay 2000 || {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{T20}}, {{T21}}, {{T22}}, {{T23}}, [[ThinkPad Dock|Dock]], [[ThinkPad Dock II|Dock II]], [[UltraBase X2]], [[Portable Drive Bay 2000]]|| [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_ls240.png|SuperDisk LS-240 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_cdrw.png|CD-RW Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayplus.png]] UltraBay Plus || {{A30}}, {{A30p}}, {{A31}}, {{A31p}}, {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{T23}}, {{T30}}, [[UltraBase X3]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_ls240.png|SuperDisk LS-240 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_cdrw.png|CD-RW Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], WorkPad Cradle, Numpad<br />
|-<br />
| [[Image:Icon20_ultrabayslim.png]] UltraBay Slim || {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{Z60t}}, [[UltraBase X4]], [[ThinkPad X4 Dock]] || [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayenh.png]] UltraBay Enhanced || {{R50}}, {{R50p}}, {{R51}}, {{R52}}, {{Z60m}} [[ ThinkPad Advanced Dock]]|| [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
|}<br />
<br />
{| border="1" cellspacing="0" cellpadding="2" style="text-align:center;"<br />
|+Compatibility Matrix (read columns as slots with rows as devices that are compatible)<br />
! Slots<hr />Devices!! [[Image:Icon20_ultrabay.png]]<br />UltraBay<br />&nbsp; !! [[Image:Icon20_ultrabay.png]]<br />UltraBay<br />Thick !! [[Image:Icon20_ultrabayii.png]]<br />UltraBay<br />II !! [[Image:Icon20_ultrabayfx.png]]<br />UltraBay<br />FX !! [[Image:Icon20_ultraslimbay.png]]<br />UltraslimBay<br />&nbsp; !! [[Image:Icon20_ultrabay2000.png]]<br />UltraBay<br />2000 !! [[Image:Icon20_ultrabayplus.png]]<br />UltraBay<br />Plus !! [[Image:Icon20_ultrabayslim.png]]<br />UltraBay<br />Slim !! [[Image:Icon20_ultrabayenh.png]]<br />UltraBay<br />Enhanced<br />
|-<br />
|'''UltraBay''' || yes || yes || [[Ultrabay Drive Adapter for Ultrabay II|Adapter]] || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay Thick''' || - || yes || [[Ultrabay Drive Adapter for Ultrabay II|Adapter]] || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay II''' || - || - || yes || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay FX''' || - || - || - || yes || - || - || - || - || -<br />
|-<br />
|'''UltraslimBay''' || - || - || - || - || yes || - || - || - || -<br />
|-<br />
|'''UltraBay 2000''' || - || - || - || - || - || yes || yes || - || -<br />
|-<br />
|'''UltraBay Plus''' || - || - || - || - || - || - || yes || - || -<br />
|-<br />
|'''UltraBay Slim''' || - || - || - || - || - || [[Ultrabay Slim Drive Adapter for Ultrabay 2000|Adapter]] || [[Ultrabay Slim Drive Adapter for Ultrabay 2000|Adapter]] || yes || yes<br />
|-<br />
|'''UltraBay Enhanced''' || - || - || - || - || - || [[Ultrabay Enhanced Drive Adapter for Ultrabay 2000|Adapter]] || [[Ultrabay Enhanced Drive Adapter for Ultrabay 2000|Adapter]] || - || yes<br />
|}<br />
<br />
===Characteristics===<br />
*UltraBay: no hot swapping<br />
*UltraBay Thick: Thicker version of UltraBay to support CD-ROM drive<br />
*UltraBay II: supports hot swapping, blending has cut out edge on the right<br />
*UltraBay FX: the combined floppy drive and CD-ROM, DVD or CDRW mechanism found in the 390/390E/390X<br />
*UltraSlimBay: supports hot swapping; Frame, rectangle like blending<br />
*UltraBay 2000: supports hot swapping; Frame, blending has cut out egde on the right<br />
*UltraBay Plus: same as UltraBay 2000, but can take the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46440 UltraBay Plus Device Carrier] which in turn can hold the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46440 UltraBay Plus WorkPad Cradle] or the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46440 UltraBay Plus Numeric Keypad]<br />
*UltraBay Slim: supports hot swapping; notably thinner than UltraBay 2000, cut out right edge in blending<br />
*UltraBay Enhanced: supports hot swapping; slightly thicker than UltraBay Slim, but accepts UltraBay Slim devices<br />
<br />
==Linux Support==<br />
The pinout switching is done by the BIOS and hardware, so that it is completely transparent to the operating system.<br />
*Floppy drives are supported by the standard floppy driver.<br />
*ZIP drive support is possible through the ide-disk driver.<br />
*IDE hard disks and optical drives are supported by the IDE or <tt>ata_piix</tt> driver in the linux kernel. SCSI emulation via ide-scsi is possible. <br />
*Batteries are automatically handled by the hardware (and can be controlled by using [[SMAPI support for Linux|tp_smapi]]).<br />
*UltraBay Plus devices should be handled by the USB subsystem, but if the devices are is not known.<br />
<br />
Hotswapping is supposed to be supported as well, using hdparm to (un)register devices. This seems to be broken with 2.6 kernels (see below). <br />
<br />
Under Debian try using the hotswap package (tested with kernel 2.6.13 and a T42).<br />
<br />
The IBM-ACPI kernel module (http://ibm-acpi.sourceforge.net) has an eject function ("echo eject > /proc/acpi/ibm/bay"). This only manages the ACPI calls to power down the device and the bay. It does not actually unregister the device from the IDE driver. <br />
To unregister the device, use the Debian hotswap package. This also allows the drive to swapped as a normal user by default, which is useful. You should use hotswap to unregister the device and then "echo eject > /proc/acpi/ibm/bay" (though this does not appear to be necessary). Works great. Test machine was a T23 (kernel 2.6.14.2).<br />
<br />
Only IDE devices (HDD's, optical drives, zip drives?) need special treatment- batteries, floppies and other devices can just be pulled from the bay, provided they are not mounted or in use at the time.<br />
<br />
==External Sources==<br />
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-50366 IBMs page on using a second hard drive adapter in the Ultrabay 2000 slot under Linux]<br />
<br />
{{footnotes|<br />
#IBM originally used the spelling UltraBay with a capital B and later switched to Ultrabay with a lower b. We are sticking with the capital B here.<br />
}}<br />
<br />
[[Category:Glossary]]</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=Ultrabay&diff=14016Ultrabay2006-01-03T16:38:53Z<p>80.42.236.205: /* Linux Support */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:UltraBay.jpg|UltraBay drives]] __NOTOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== IBM UltraBay ===<br />
UltraBay{{footnote|1}} is IBM's name for the swapable drive slot. With IBMs words: "The ThinkPad UltraBay, also standard with the system, is an intelligent bay that switches its pinout signals to allow the installation of standard and optional features in what would normally be just the FDD bay." Introduced back in the times of the 770 Thinkpads, this technology has gone through redesigns with almost every new generation of Thinkpad models, possibly leading to some confusion that is hopefully cleared up here. The following table gives an overview of the different UltraBay types, in which models they occurred and what drives are available for them.<br />
Note that the optical drive bay in G series Thinkpads is not an UltraBay in that the drives are fixed and not removable.<br />
<br />
On the media side different UltraBays relate to the form factor of the drives they accept, e.g early A, T and X series models can accept UltraBay devices up to 12.5mm in thickness, whereas current T and X series machines are limited to devices no more than 9.5mm thick.<br />
</div><br />
|}<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|+Overview over UltraBay types and available devices<br />
! width=140px|UltraBay Type !! featured in !! available drives (see [[UltraBay Devices]] for details)<br />
<br />
|-<br />
| [[Image:Icon20_ultrabay.png]] UltraBay || {{355}}, {{355C}}, {{355Cs}}, {{360}}, {{360C}}, {{360Cs}}, {{360P}}, {{360CE}}, {{360CSE}}, {{360PE}}, {{370C}}, {{750}}, {{750C}}, {{750Cs}}, {{750P}}, {{755C}}, {{755CE}}, {{755Cs}}, {{755CSE}}, {{755CV}}, {{755CX}}, {{760C}}, {{760L}}, {{760E}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], 2.88 MB diskette, PCMCIA Cartridge, IBM Wireless Modem ARDIS, IBM Wireless Modem<br />
|-<br />
| [[Image:Icon20_ultrabay.png]] UltraBay Thick|| {{755CD}}, {{755CDV}}, {{760CD}}, {{760E}}, {{760ED}}, {{760EL}}, {{760ELD}}, {{760LD}}, {{760XD}}, {{760XL}}, {{765D}}, {{765L}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], 2.88 MB diskette, PCMCIA Cartridge, IBM Wireless Modem ARDIS, IBM Wireless Modem<br />
|-<br />
| [[Image:Icon20_ultrabayii.png]] UltraBay II || {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}, [[SelectaDock III]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayfx.png]] UltraBay FX|| {{390}}, {{390E}}, {{390X}}, {{i1720}}, {{i1721}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultraslimbay.png]] UltraslimBay || {{600}}, {{600E}}, {{600X}}, [[UltraBase]], [[Portable Drive Bay]]|| [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabay2000.png]] UltraBay 2000 || {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{T20}}, {{T21}}, {{T22}}, {{T23}}, [[ThinkPad Dock|Dock]], [[ThinkPad Dock II|Dock II]], [[UltraBase X2]], [[Portable Drive Bay 2000]]|| [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_ls240.png|SuperDisk LS-240 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_cdrw.png|CD-RW Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayplus.png]] UltraBay Plus || {{A30}}, {{A30p}}, {{A31}}, {{A31p}}, {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{T23}}, {{T30}}, [[UltraBase X3]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_ls240.png|SuperDisk LS-240 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_cdrw.png|CD-RW Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], WorkPad Cradle, Numpad<br />
|-<br />
| [[Image:Icon20_ultrabayslim.png]] UltraBay Slim || {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{Z60t}}, [[UltraBase X4]], [[ThinkPad X4 Dock]] || [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayenh.png]] UltraBay Enhanced || {{R50}}, {{R50p}}, {{R51}}, {{R52}}, {{Z60m}} [[ ThinkPad Advanced Dock]]|| [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
|}<br />
<br />
{| border="1" cellspacing="0" cellpadding="2" style="text-align:center;"<br />
|+Compatibility Matrix (read columns as slots with rows as devices that are compatible)<br />
! Slots<hr />Devices!! [[Image:Icon20_ultrabay.png]]<br />UltraBay<br />&nbsp; !! [[Image:Icon20_ultrabay.png]]<br />UltraBay<br />Thick !! [[Image:Icon20_ultrabayii.png]]<br />UltraBay<br />II !! [[Image:Icon20_ultrabayfx.png]]<br />UltraBay<br />FX !! [[Image:Icon20_ultraslimbay.png]]<br />UltraslimBay<br />&nbsp; !! [[Image:Icon20_ultrabay2000.png]]<br />UltraBay<br />2000 !! [[Image:Icon20_ultrabayplus.png]]<br />UltraBay<br />Plus !! [[Image:Icon20_ultrabayslim.png]]<br />UltraBay<br />Slim !! [[Image:Icon20_ultrabayenh.png]]<br />UltraBay<br />Enhanced<br />
|-<br />
|'''UltraBay''' || yes || yes || [[Ultrabay Drive Adapter for Ultrabay II|Adapter]] || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay Thick''' || - || yes || [[Ultrabay Drive Adapter for Ultrabay II|Adapter]] || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay II''' || - || - || yes || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay FX''' || - || - || - || yes || - || - || - || - || -<br />
|-<br />
|'''UltraslimBay''' || - || - || - || - || yes || - || - || - || -<br />
|-<br />
|'''UltraBay 2000''' || - || - || - || - || - || yes || yes || - || -<br />
|-<br />
|'''UltraBay Plus''' || - || - || - || - || - || - || yes || - || -<br />
|-<br />
|'''UltraBay Slim''' || - || - || - || - || - || [[Ultrabay Slim Drive Adapter for Ultrabay 2000|Adapter]] || [[Ultrabay Slim Drive Adapter for Ultrabay 2000|Adapter]] || yes || yes<br />
|-<br />
|'''UltraBay Enhanced''' || - || - || - || - || - || [[Ultrabay Enhanced Drive Adapter for Ultrabay 2000|Adapter]] || [[Ultrabay Enhanced Drive Adapter for Ultrabay 2000|Adapter]] || - || yes<br />
|}<br />
<br />
===Characteristics===<br />
*UltraBay: no hot swapping<br />
*UltraBay Thick: Thicker version of UltraBay to support CD-ROM drive<br />
*UltraBay II: supports hot swapping, blending has cut out edge on the right<br />
*UltraBay FX: the combined floppy drive and CD-ROM, DVD or CDRW mechanism found in the 390/390E/390X<br />
*UltraSlimBay: supports hot swapping; Frame, rectangle like blending<br />
*UltraBay 2000: supports hot swapping; Frame, blending has cut out egde on the right<br />
*UltraBay Plus: same as UltraBay 2000, but can take the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46440 UltraBay Plus Device Carrier] which in turn can hold the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46440 UltraBay Plus WorkPad Cradle] or the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46440 UltraBay Plus Numeric Keypad]<br />
*UltraBay Slim: supports hot swapping; notably thinner than UltraBay 2000, cut out right edge in blending<br />
*UltraBay Enhanced: supports hot swapping; slightly thicker than UltraBay Slim, but accepts UltraBay Slim devices<br />
<br />
==Linux Support==<br />
The pinout switching is done by the BIOS and hardware, so that it is completely transparent to the operating system.<br />
*Floppy drives are supported by the standard floppy driver.<br />
*ZIP drive support is possible through the ide-disk driver.<br />
*IDE hard disks and optical drives are supported by the IDE or <tt>ata_piix</tt> driver in the linux kernel. SCSI emulation via ide-scsi is possible. <br />
*Batteries are automatically handled by the hardware (and can be controlled by using [[SMAPI support for Linux|tp_smapi]]).<br />
*UltraBay Plus devices should be handled by the USB subsystem, but if the devices are is not known.<br />
<br />
Hotswapping is supposed to be supported as well, using hdparm to (un)register devices. This seems to be broken with 2.6 kernels (see below). <br />
<br />
Under Debian try using the hotswap package (tested with kernel 2.6.13 and a T42).<br />
<br />
The IBM-ACPI kernel module (http://ibm-acpi.sourceforge.net) has an eject function ("echo eject > /proc/acpi/ibm/bay"). This only manages the ACPI calls to power down the device and the bay. It does not actually unregister the device from the IDE driver. <br />
To unregister the device, use the Debian hotswap package. This also allows the drive to swapped as a normal user by default, which is useful. You should use hotswap to unregister the device and then "echo eject > /proc/acpi/ibm/bay" (though this does not appear to be necessary). Works great. Test machine was a T23.<br />
<br />
Only IDE devices (HDD's, optical drives, zip drives?) need special treatment- batteries, floppies and other devices can just be pulled from the bay, provided they are not mounted or in use at the time.<br />
<br />
==External Sources==<br />
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-50366 IBMs page on using a second hard drive adapter in the Ultrabay 2000 slot under Linux]<br />
<br />
{{footnotes|<br />
#IBM originally used the spelling UltraBay with a capital B and later switched to Ultrabay with a lower b. We are sticking with the capital B here.<br />
}}<br />
<br />
[[Category:Glossary]]</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=Ultrabay_2000_Battery&diff=14018Ultrabay 2000 Battery2006-01-03T16:31:15Z<p>80.42.236.205: /* Linux Support */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== UltraBay 2000 Battery ===<br />
This is a battery that slides into a supported UltraBay 2000.<br />
<br />
=== Features ===<br />
* 10.8V Lithium-Ion<br />
* 9 cells<br />
* Up to 3 hours of battery life<br />
* Weight: 268g (0.59 lbs)<br />
* Charge time: 2.0 h<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:ultrabay2000battery.gif|UltraBay 2000 Battery]]<br />
|}<br />
<br />
=== IBM Partnumbers ===<br />
*Marketing PN: 02K6646<br />
*FRU PN: 02K6645<br />
<br />
=== Linux Support ===<br />
The second battery is correctly detected by either the APM or ACPI subsystem.<br />
<br />
However, the Linux ACPI subsystem only scans for batteries on boot. This means that the second battery must be present at boot time, or you will not be able to get any info for it.<br />
<br />
We need to find a way of telling the ACPI subsystem to rescan for batteries.<br />
<br />
With kernel 2.6.14.2 (possibly only with IBM_ACPI) there is a sysfs file: /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject. There isn't one for BAT0, but then /proc/acpi/battery/BAT0/* shows "not present" when there is no battery. For BAT1 all the states go to 0, critical, etc. "echo 1 > /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject" will remove /proc/acpi/battery/BAT1 and turn off the ultrabay light. Interestingly the battery will still be discharging (charging not tested) until it is physically removed.<br />
<br />
Also, if you compile the battery module of ACPI as a module, boot with the ultrabay battery present, remove the ultrabay battery (without doing the eject above), /proc/acpi/battery/BAT1 is still there, rmmod battery, modprobe battery, /proc/acpi/battery/BAT1 is gone (BAT0 is back), put the battery back in, /proc/acpi/battery/BAT1 still missing, rmmod battery, modprobe battery, /proc/acpi/battery/BAT1 is back.<br />
If you boot without the second battery BAT1 never shows up.<br />
If you eject using the sysfs file above, BAT1 disappears from both /proc and /sys and never comes back.<br />
<br />
Test machine: T23.<br />
<br />
=== Supported with ===<br />
*ThinkPad {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{A30p}}, {{A31}}, {{A31p}}<br />
*ThinkPad {{R30}}, {{R31}}, {{R32}}, {{R40}}<br />
*ThinkPad {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}<br />
<br />
<br />
[[Category:Components]]</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=Ultrabay_2000_Battery&diff=14014Ultrabay 2000 Battery2006-01-03T13:27:59Z<p>80.42.236.205: /* Linux Support */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== UltraBay 2000 Battery ===<br />
This is a battery that slides into a supported UltraBay 2000.<br />
<br />
=== Features ===<br />
* 10.8V Lithium-Ion<br />
* 9 cells<br />
* Up to 3 hours of battery life<br />
* Weight: 268g (0.59 lbs)<br />
* Charge time: 2.0 h<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:ultrabay2000battery.gif|UltraBay 2000 Battery]]<br />
|}<br />
<br />
=== IBM Partnumbers ===<br />
*Marketing PN: 02K6646<br />
*FRU PN: 02K6645<br />
<br />
=== Linux Support ===<br />
The second battery is correctly detected by either the APM or ACPI subsystem.<br />
<br />
However, the Linux ACPI subsystem only scans for batteries on boot. This means that the second battery must be present at boot time, or you will not be able to get any info for it.<br />
<br />
We need to find a way of telling the ACPI subsystem to rescan for batteries.<br />
<br />
=== Supported with ===<br />
*ThinkPad {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{A30p}}, {{A31}}, {{A31p}}<br />
*ThinkPad {{R30}}, {{R31}}, {{R32}}, {{R40}}<br />
*ThinkPad {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}<br />
<br />
<br />
[[Category:Components]]</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=Ultrabay&diff=13943Ultrabay2005-12-01T19:53:40Z<p>80.42.236.205: /* Linux Support */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:UltraBay.jpg|UltraBay drives]] __NOTOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== IBM UltraBay ===<br />
UltraBay{{footnote|1}} is IBM's name for the swapable drive slot. With IBMs words: "The ThinkPad UltraBay, also standard with the system, is an intelligent bay that switches its pinout signals to allow the installation of standard and optional features in what would normally be just the FDD bay." Introduced back in the times of the 770 Thinkpads, this technology has gone through redesigns with almost every new generation of Thinkpad models, possibly leading to some confusion that is hopefully cleared up here. The following table gives an overview of the different UltraBay types, in which models they occurred and what drives are available for them.<br />
Note that the optical drive bay in G series Thinkpads is not an UltraBay in that the drives are fixed and not removable.<br />
<br />
On the media side different UltraBays relate to the form factor of the drives they accept, e.g early A, T and X series models can accept UltraBay devices up to 12.5mm in thickness, whereas current T and X series machines are limited to devices no more than 9.5mm thick.<br />
</div><br />
|}<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|+Overview over UltraBay types and available devices<br />
! width=140px|UltraBay Type !! featured in !! available drives (see [[UltraBay Devices]] for details)<br />
<br />
|-<br />
| [[Image:Icon20_ultrabay.png]] UltraBay || {{355}}, {{355C}}, {{355Cs}}, {{360}}, {{360C}}, {{360Cs}}, {{360P}}, {{360CE}}, {{360CSE}}, {{360PE}}, {{370C}}, {{750}}, {{750C}}, {{750Cs}}, {{750P}}, {{755C}}, {{755CE}}, {{755Cs}}, {{755CSE}}, {{755CV}}, {{755CX}}, {{760C}}, {{760L}}, {{760E}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], 2.88 MB diskette, PCMCIA Cartridge, IBM Wireless Modem ARDIS, IBM Wireless Modem<br />
|-<br />
| [[Image:Icon20_ultrabay.png]] UltraBay Thick|| {{755CD}}, {{755CDV}}, {{760CD}}, {{760E}}, {{760ED}}, {{760EL}}, {{760ELD}}, {{760LD}}, {{760XD}}, {{760XL}}, {{765D}}, {{765L}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], 2.88 MB diskette, PCMCIA Cartridge, IBM Wireless Modem ARDIS, IBM Wireless Modem<br />
|-<br />
| [[Image:Icon20_ultrabayii.png]] UltraBay II || {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}, [[SelectaDock III]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayfx.png]] UltraBay FX|| {{390}}, {{390E}}, {{390X}}, {{i1720}}, {{i1721}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultraslimbay.png]] UltraslimBay || {{600}}, {{600E}}, {{600X}}, [[UltraBase]], [[Portable Drive Bay]]|| [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabay2000.png]] UltraBay 2000 || {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{T20}}, {{T21}}, {{T22}}, {{T23}}, [[ThinkPad Dock|Dock]], [[ThinkPad Dock II|Dock II]], [[UltraBase X2]], [[Portable Drive Bay 2000]]|| [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_ls240.png|SuperDisk LS-240 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_cdrw.png|CD-RW Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayplus.png]] UltraBay Plus || {{A30}}, {{A30p}}, {{A31}}, {{A31p}}, {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{T23}}, {{T30}}, [[UltraBase X3]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_ls240.png|SuperDisk LS-240 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_cdrw.png|CD-RW Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], WorkPad Cradle, Numpad<br />
|-<br />
| [[Image:Icon20_ultrabayslim.png]] UltraBay Slim || {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{Z60t}}, [[UltraBase X4]], [[ThinkPad X4 Dock]] || [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayenh.png]] UltraBay Enhanced || {{R50}}, {{R50p}}, {{R51}}, {{R52}}, {{Z60m}} [[ ThinkPad Advanced Dock]]|| [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
|}<br />
<br />
{| border="1" cellspacing="0" cellpadding="2" style="text-align:center;"<br />
|+Compatibility Matrix (read columns as slots with rows as devices that are compatible)<br />
! Slots<hr />Devices!! [[Image:Icon20_ultrabay.png]]<br />UltraBay<br />&nbsp; !! [[Image:Icon20_ultrabay.png]]<br />UltraBay<br />Thick !! [[Image:Icon20_ultrabayii.png]]<br />UltraBay<br />II !! [[Image:Icon20_ultrabayfx.png]]<br />UltraBay<br />FX !! [[Image:Icon20_ultraslimbay.png]]<br />UltraslimBay<br />&nbsp; !! [[Image:Icon20_ultrabay2000.png]]<br />UltraBay<br />2000 !! [[Image:Icon20_ultrabayplus.png]]<br />UltraBay<br />Plus !! [[Image:Icon20_ultrabayslim.png]]<br />UltraBay<br />Slim !! [[Image:Icon20_ultrabayenh.png]]<br />UltraBay<br />Enhanced<br />
|-<br />
|'''UltraBay''' || yes || yes || [[Ultrabay Drive Adapter for Ultrabay II|Adapter]] || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay Thick''' || - || yes || [[Ultrabay Drive Adapter for Ultrabay II|Adapter]] || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay II''' || - || - || yes || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay FX''' || - || - || - || yes || - || - || - || - || -<br />
|-<br />
|'''UltraslimBay''' || - || - || - || - || yes || - || - || - || -<br />
|-<br />
|'''UltraBay 2000''' || - || - || - || - || - || yes || yes || - || -<br />
|-<br />
|'''UltraBay Plus''' || - || - || - || - || - || - || yes || - || -<br />
|-<br />
|'''UltraBay Slim''' || - || - || - || - || - || [[Ultrabay Slim Drive Adapter for Ultrabay 2000|Adapter]] || [[Ultrabay Slim Drive Adapter for Ultrabay 2000|Adapter]] || yes || yes<br />
|-<br />
|'''UltraBay Enhanced''' || - || - || - || - || - || [[Ultrabay Enhanced Drive Adapter for Ultrabay 2000|Adapter]] || [[Ultrabay Enhanced Drive Adapter for Ultrabay 2000|Adapter]] || - || yes<br />
|}<br />
<br />
===Characteristics===<br />
*UltraBay: no hot swapping<br />
*UltraBay Thick: Thicker version of UltraBay to support CD-ROM drive<br />
*UltraBay II: supports hot swapping, blending has cut out egde on the right<br />
*UltraBay FX: the combined floppy drive and CD-ROM, DVD or CDRW mechanism found in the 390/390E/390X<br />
*UltraSlimBay: supports hot swapping; Frame, rectangle like blending<br />
*UltraBay 2000: supports hot swapping; Frame, blending has cut out egde on the right<br />
*UltraBay Plus: same as UltraBay 2000, but can take the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46440 UltraBay Plus Device Carrier] which in turn can hold the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46440 UltraBay Plus WorkPad Cradle] or the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46440 UltraBay Plus Numeric Keypad]<br />
*UltraBay Slim: supports hot swapping; notably thinner than UltraBay 2000, cut out right edge in blending<br />
*UltraBay Enhanced: supports hot swapping; slightly thicker than UltraBay Slim, but accepts UltraBay Slim devices<br />
<br />
==Linux Support==<br />
The pinout switching is done by the BIOS and hardware, so that it is completely transparent to the operating system.<br />
*Floppy drives are supported by the standard floppy driver.<br />
*ZIP drive support is possible through the ide-disk driver.<br />
*IDE drives are supported by the IDE driver in the linux kernel. SCSI emulation via ide-scsi is possible. *Batteries are BIOS controlled, anyway.<br />
*UltraBay Plus devices should be handled by the USB subsystem, but if the devices are is not known.<br />
<br />
Hotswapping is supposed to be supported as well, using hdparm to (un)register devices. This seems to be broken with 2.6 kernels (see below). <br />
<br />
Under Debian try using the hotswap package (tested with kernel 2.6.13 and a T42).<br />
<br />
The IBM-ACPI kernel module (http://ibm-acpi.sourceforge.net) has an eject function ("echo eject > /proc/acpi/ibm/bay"). This appears to be broken (tested with kernel 2.6.8.1 and kernel 2.6.14.2). After re-inserting the drive it cannot read CDs- it tries for ages and locks the system for long periods of time.<br />
Debian hotswap works though (compiled from source on Slackware 9.1), and allows the drive to swapped as a normal user by default, which is useful. Strangely, after doing a swap with Debian hotswap the IBM-ACPI swapping works. Debian hotswap shows the device as still present if you use the IBM-ACPI eject, even if the drive isn't physically attached. Looks like the IBM-ACPI eject function doesn't unregister the device properly. Test machine was a T23.<br />
<br />
Only IDE devices (HDD's, optical drives, zip drives?) need special treatment- batteries, floppies and other devices can just be pulled from the bay, provided they are not mounted or in use at the time.<br />
<br />
==External Sources==<br />
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-50366 IBMs page on using a second hard drive adapter in the Ultrabay 2000 slot under Linux]<br />
<br />
{{footnotes|<br />
#IBM originally used the spelling UltraBay with a capital B and later switched to Ultrabay with a lower b. We are sticking with the capital B here.<br />
}}<br />
<br />
[[Category:Glossary]]</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=CS4299&diff=16662CS42992005-11-30T21:57:27Z<p>80.42.236.205: /* Dmixing */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== CS4299 ===<br />
This is a Cirrus Logic AC'97 Audio controller<br />
<br />
This chip is sometimes incorrectly called CS4229 in IBM documentation<br />
=== Features ===<br />
* Chipset: CS4299<br />
* Interface: AC'97 2.1<br />
</div><br />
|style="vertical-align:top" |<br />
|}<br />
<br />
=== Linux OSS driver ===<br />
This sound chip is supported by the i810_audio kernel module.<br />
<br />
=== Linux ALSA driver ===<br />
This sound chip is supported by the snd-intel8x0 kernel module.<br />
<br />
==== Dmixing ====<br />
The CS4299 is not capable of hardware mixing. This means that only one sound stream can be played at any time. <br />
You must get the software to do the mixing for it (this will load your CPU).<br />
The ALSA implementation of this is called DMIX. You can also run sound servers like ESD or ArtsD, but not all applications will use them.<br />
Recent ALSA distributions have dmixing setup and enabled by default. <br />
<br />
Otherwise just add the following to {{path|/etc/asound.conf}} :<br />
pcm.dsp0 {<br />
type plug<br />
slave.pcm dmix<br />
}<br />
# mixer0 can stay unchanged, because<br />
# it isn't used anyway, I guess ;)<br />
ctl.mixer0 {<br />
type hw<br />
card 0<br />
}<br />
<br />
Now the only problem is how to tell applications to use the DMIX channel instead of dsp0.<br />
<br />
=== ThinkPads this chip may be found in ===<br />
* {{A21e}}, {{A22e}}<br />
* {{A30}}, {{A30p}}<br />
* {{T23}}<br />
* {{X22}}, {{X23}}, {{X24}}<br />
* {{i1200}}, {{i1210}}, {{i1230}}, {{i1250}}, {{i1260}}<br />
* {{i1300}}, {{i1330}}, {{i1370}}<br />
<br />
[[Category:Components]]</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=CS4299&diff=12694CS42992005-11-30T21:57:00Z<p>80.42.236.205: /* Dmixing */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== CS4299 ===<br />
This is a Cirrus Logic AC'97 Audio controller<br />
<br />
This chip is sometimes incorrectly called CS4229 in IBM documentation<br />
=== Features ===<br />
* Chipset: CS4299<br />
* Interface: AC'97 2.1<br />
</div><br />
|style="vertical-align:top" |<br />
|}<br />
<br />
=== Linux OSS driver ===<br />
This sound chip is supported by the i810_audio kernel module.<br />
<br />
=== Linux ALSA driver ===<br />
This sound chip is supported by the snd-intel8x0 kernel module.<br />
<br />
==== Dmixing ====<br />
The CS4299 is not capable of hardware mixing. This means that only one sound stream can be played at any time. <br />
You must get the software to do the mixing for it (this will load your CPU).<br />
The ALSA implementation of this is called DMIX. You can also run sound servers like ESD or ArtsD, but not all applications will use them.<br />
Recent ALSA distributions have dmixing setup and enabled by default. <br />
<br />
Otherwise just add the following to {{path|/etc/asound.conf}} :<br />
pcm.dsp0 {<br />
type plug<br />
slave.pcm dmix<br />
}<br />
# mixer0 can stay unchanged, because<br />
# it isn't used anyway, I guess ;)<br />
ctl.mixer0 {<br />
type hw<br />
card 0<br />
}<br />
<br />
Now the only problem is how to tell applications to use the DMIX channel.<br />
<br />
=== ThinkPads this chip may be found in ===<br />
* {{A21e}}, {{A22e}}<br />
* {{A30}}, {{A30p}}<br />
* {{T23}}<br />
* {{X22}}, {{X23}}, {{X24}}<br />
* {{i1200}}, {{i1210}}, {{i1230}}, {{i1250}}, {{i1260}}<br />
* {{i1300}}, {{i1330}}, {{i1370}}<br />
<br />
[[Category:Components]]</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=CS4299&diff=12693CS42992005-11-30T21:56:40Z<p>80.42.236.205: /* Dmixing */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== CS4299 ===<br />
This is a Cirrus Logic AC'97 Audio controller<br />
<br />
This chip is sometimes incorrectly called CS4229 in IBM documentation<br />
=== Features ===<br />
* Chipset: CS4299<br />
* Interface: AC'97 2.1<br />
</div><br />
|style="vertical-align:top" |<br />
|}<br />
<br />
=== Linux OSS driver ===<br />
This sound chip is supported by the i810_audio kernel module.<br />
<br />
=== Linux ALSA driver ===<br />
This sound chip is supported by the snd-intel8x0 kernel module.<br />
<br />
==== Dmixing ====<br />
The CS4299 is not capable of hardware mixing. This means that only one sound stream can be played at any time. <br />
You must get the software to do the mixing for it (this will load your CPU).<br />
The ALSA implementation of this is called DMIX. You can also run sound servers like ESD or ArtsD, but not all applications will use them.<br />
Recent ALSA distributions have dmixing setup and enabled by default. <br />
<br />
Otherwise just add the following to {{path|/etc/asound.conf}} :<br />
pcm.dsp0 {<br />
type plug<br />
slave.pcm dmix<br />
}<br />
# mixer0 can stay unchanged, because<br />
# it isn't used anyway, I guess ;)<br />
ctl.mixer0 {<br />
type hw<br />
card 0<br />
}<br />
<br />
<br />
Now the only problem is how to tell applications to use the DMIX channel.<br />
<br />
=== ThinkPads this chip may be found in ===<br />
* {{A21e}}, {{A22e}}<br />
* {{A30}}, {{A30p}}<br />
* {{T23}}<br />
* {{X22}}, {{X23}}, {{X24}}<br />
* {{i1200}}, {{i1210}}, {{i1230}}, {{i1250}}, {{i1260}}<br />
* {{i1300}}, {{i1330}}, {{i1370}}<br />
<br />
[[Category:Components]]</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=CS4299&diff=12692CS42992005-11-30T21:56:03Z<p>80.42.236.205: /* Dmixing */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== CS4299 ===<br />
This is a Cirrus Logic AC'97 Audio controller<br />
<br />
This chip is sometimes incorrectly called CS4229 in IBM documentation<br />
=== Features ===<br />
* Chipset: CS4299<br />
* Interface: AC'97 2.1<br />
</div><br />
|style="vertical-align:top" |<br />
|}<br />
<br />
=== Linux OSS driver ===<br />
This sound chip is supported by the i810_audio kernel module.<br />
<br />
=== Linux ALSA driver ===<br />
This sound chip is supported by the snd-intel8x0 kernel module.<br />
<br />
==== Dmixing ====<br />
The CS4299 is not capable of hardware mixing. This means that only one sound stream can be played at any time. <br />
You must get the software to do the mixing for it (this will load your CPU).<br />
The ALSA implementation of this is called DMIX. You can also run sound servers like ESD or ArtsD, but not all software will use them.<br />
Recent ALSA distributions have dmixing setup and enabled by default. <br />
<br />
Otherwise just add the following to {{path|/etc/asound.conf}} :<br />
pcm.dsp0 {<br />
type plug<br />
slave.pcm dmix<br />
}<br />
# mixer0 can stay unchanged, because<br />
# it isn't used anyway, I guess ;)<br />
ctl.mixer0 {<br />
type hw<br />
card 0<br />
}<br />
<br />
<br />
Now the only problem is how to tell applications to use the DMIX channel.<br />
<br />
=== ThinkPads this chip may be found in ===<br />
* {{A21e}}, {{A22e}}<br />
* {{A30}}, {{A30p}}<br />
* {{T23}}<br />
* {{X22}}, {{X23}}, {{X24}}<br />
* {{i1200}}, {{i1210}}, {{i1230}}, {{i1250}}, {{i1260}}<br />
* {{i1300}}, {{i1330}}, {{i1370}}<br />
<br />
[[Category:Components]]</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=S3_SuperSavage_IX/C&diff=12695S3 SuperSavage IX/C2005-11-30T21:49:32Z<p>80.42.236.205: /* Linux kernel Framebuffer driver */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== S3 SuperSavage IX/C ===<br />
This is a S3 video adapter<br><br />
S3 is now owned by Via Technologies<br />
<br />
=== Features ===<br />
* Chipset: S3<br />
* PCI ID: 5333:8c2e<br />
* AGP 4X<br />
* 16MB SDRAM video memory<br />
</div><br />
|style="vertical-align:top" |<br />
|}<br />
<br />
=== Linux X.Org driver ===<br />
This chip is supported by the '[[savage]]' driver as part of the X.Org distribution<br />
<br />
==== ThinkPad LCD ====<br />
Display on the internal LCD works as long as you set the monitor settings correct.<br />
<br />
==== External VGA port ====<br />
Works without trouble, even as Dualhead with xinerama. For swtching on/off use s3switch (also works for TVout).<br />
<br />
==== SVideo port ====<br />
works.<br />
<br />
=== Linux kernel Framebuffer driver ===<br />
This chip will work with either the 'vesa' or 'savagefb' driver as part of any recent 2.4 or 2.6 kernel.<br />
<br />
***fix needed***<br />
Suspend-to-RAM does not work if the framebuffer is enabled. Suspending with X running is fine, so long as the framebuffer is disabled and X is using its own savage driver. With vesafb the screen is frozen on resume (but the system is still running fine behind it). With savagefb it won't even try to wake up! Tried everything!<br />
vesafb-tng allows the use of a modular framebuffer, which will probably fix this, but how do you unload a framebuffer module? Is it possible to detach the VC from it and reattach it when the module is loaded on resume?<br />
<br />
=== ThinkPads this chip may be found in ===<br />
* {{T23}}<br />
<br />
[[Category:Components]]</div>80.42.236.205https://www.thinkwiki.org/w/index.php?title=Ultrabay&diff=12717Ultrabay2005-11-30T20:15:28Z<p>80.42.236.205: /* Linux Support */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:UltraBay.jpg|UltraBay drives]] __NOTOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== IBM UltraBay ===<br />
UltraBay{{footnote|1}} is IBM's name for the swapable drive slot. With IBMs words: "The ThinkPad UltraBay, also standard with the system, is an intelligent bay that switches its pinout signals to allow the installation of standard and optional features in what would normally be just the FDD bay." Introduced back in the times of the 770 Thinkpads, this technology has gone through redesigns with almost every new generation of Thinkpad models, possibly leading to some confusion that is hopefully cleared up here. The following table gives an overview of the different UltraBay types, in which models they occurred and what drives are available for them.<br />
Note that the optical drive bay in G series Thinkpads is not an UltraBay in that the drives are fixed and not removable.<br />
<br />
On the media side different UltraBays relate to the form factor of the drives they accept, e.g early A, T and X series models can accept UltraBay devices up to 12.5mm in thickness, whereas current T and X series machines are limited to devices no more than 9.5mm thick.<br />
</div><br />
|}<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|+Overview over UltraBay types and available devices<br />
! width=140px|UltraBay Type !! featured in !! available drives (see [[UltraBay Devices]] for details)<br />
<br />
|-<br />
| [[Image:Icon20_ultrabay.png]] UltraBay || {{355}}, {{355C}}, {{355Cs}}, {{360}}, {{360C}}, {{360Cs}}, {{360P}}, {{360CE}}, {{360CSE}}, {{360PE}}, {{370C}}, {{750}}, {{750C}}, {{750Cs}}, {{750P}}, {{755C}}, {{755CE}}, {{755Cs}}, {{755CSE}}, {{755CV}}, {{755CX}}, {{760C}}, {{760L}}, {{760E}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], 2.88 MB diskette, PCMCIA Cartridge, IBM Wireless Modem ARDIS, IBM Wireless Modem<br />
|-<br />
| [[Image:Icon20_ultrabay.png]] UltraBay Thick|| {{755CD}}, {{755CDV}}, {{760CD}}, {{760E}}, {{760ED}}, {{760EL}}, {{760ELD}}, {{760LD}}, {{760XD}}, {{760XL}}, {{765D}}, {{765L}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], 2.88 MB diskette, PCMCIA Cartridge, IBM Wireless Modem ARDIS, IBM Wireless Modem<br />
|-<br />
| [[Image:Icon20_ultrabayii.png]] UltraBay II || {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}, [[SelectaDock III]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayfx.png]] UltraBay FX|| {{390}}, {{390E}}, {{390X}}, {{i1720}}, {{i1721}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultraslimbay.png]] UltraslimBay || {{600}}, {{600E}}, {{600X}}, [[UltraBase]], [[Portable Drive Bay]]|| [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabay2000.png]] UltraBay 2000 || {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{T20}}, {{T21}}, {{T22}}, {{T23}}, [[ThinkPad Dock|Dock]], [[ThinkPad Dock II|Dock II]], [[UltraBase X2]], [[Portable Drive Bay 2000]]|| [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_ls240.png|SuperDisk LS-240 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_cdrw.png|CD-RW Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayplus.png]] UltraBay Plus || {{A30}}, {{A30p}}, {{A31}}, {{A31p}}, {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{T23}}, {{T30}}, [[UltraBase X3]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_ls240.png|SuperDisk LS-240 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_cdrw.png|CD-RW Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], WorkPad Cradle, Numpad<br />
|-<br />
| [[Image:Icon20_ultrabayslim.png]] UltraBay Slim || {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{Z60t}}, [[UltraBase X4]], [[ThinkPad X4 Dock]] || [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayenh.png]] UltraBay Enhanced || {{R50}}, {{R50p}}, {{R51}}, {{R52}}, {{Z60m}} [[ ThinkPad Advanced Dock]]|| [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
|}<br />
<br />
{| border="1" cellspacing="0" cellpadding="2" style="text-align:center;"<br />
|+Compatibility Matrix (read columns as slots with rows as devices that are compatible)<br />
! Slots<hr />Devices!! [[Image:Icon20_ultrabay.png]]<br />UltraBay<br />&nbsp; !! [[Image:Icon20_ultrabay.png]]<br />UltraBay<br />Thick !! [[Image:Icon20_ultrabayii.png]]<br />UltraBay<br />II !! [[Image:Icon20_ultrabayfx.png]]<br />UltraBay<br />FX !! [[Image:Icon20_ultraslimbay.png]]<br />UltraslimBay<br />&nbsp; !! [[Image:Icon20_ultrabay2000.png]]<br />UltraBay<br />2000 !! [[Image:Icon20_ultrabayplus.png]]<br />UltraBay<br />Plus !! [[Image:Icon20_ultrabayslim.png]]<br />UltraBay<br />Slim !! [[Image:Icon20_ultrabayenh.png]]<br />UltraBay<br />Enhanced<br />
|-<br />
|'''UltraBay''' || yes || yes || [[Ultrabay Drive Adapter for Ultrabay II|Adapter]] || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay Thick''' || - || yes || [[Ultrabay Drive Adapter for Ultrabay II|Adapter]] || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay II''' || - || - || yes || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay FX''' || - || - || - || yes || - || - || - || - || -<br />
|-<br />
|'''UltraslimBay''' || - || - || - || - || yes || - || - || - || -<br />
|-<br />
|'''UltraBay 2000''' || - || - || - || - || - || yes || yes || - || -<br />
|-<br />
|'''UltraBay Plus''' || - || - || - || - || - || - || yes || - || -<br />
|-<br />
|'''UltraBay Slim''' || - || - || - || - || - || [[Ultrabay Slim Drive Adapter for Ultrabay 2000|Adapter]] || [[Ultrabay Slim Drive Adapter for Ultrabay 2000|Adapter]] || yes || yes<br />
|-<br />
|'''UltraBay Enhanced''' || - || - || - || - || - || [[Ultrabay Enhanced Drive Adapter for Ultrabay 2000|Adapter]] || [[Ultrabay Enhanced Drive Adapter for Ultrabay 2000|Adapter]] || - || yes<br />
|}<br />
<br />
===Characteristics===<br />
*UltraBay: no hot swapping<br />
*UltraBay Thick: Thicker version of UltraBay to support CD-ROM drive<br />
*UltraBay II: supports hot swapping, blending has cut out egde on the right<br />
*UltraBay FX: the combined floppy drive and CD-ROM, DVD or CDRW mechanism found in the 390/390E/390X<br />
*UltraSlimBay: supports hot swapping; Frame, rectangle like blending<br />
*UltraBay 2000: supports hot swapping; Frame, blending has cut out egde on the right<br />
*UltraBay Plus: same as UltraBay 2000, but can take the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46440 UltraBay Plus Device Carrier] which in turn can hold the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46440 UltraBay Plus WorkPad Cradle] or the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46440 UltraBay Plus Numeric Keypad]<br />
*UltraBay Slim: supports hot swapping; notably thinner than UltraBay 2000, cut out right edge in blending<br />
*UltraBay Enhanced: supports hot swapping; slightly thicker than UltraBay Slim, but accepts UltraBay Slim devices<br />
<br />
==Linux Support==<br />
The pinout switching is done by the BIOS and hardware, so that it is completely transparent to the operating system.<br />
*Floppy drives are supported by the standard floppy driver.<br />
*ZIP drive support is possible through the ide-disk driver.<br />
*IDE drives are supported by the IDE driver in the linux kernel. SCSI emulation via ide-scsi is possible. *Batteries are BIOS controlled, anyway.<br />
*UltraBay Plus devices should be handled by the USB subsystem, but if the devices are is not known.<br />
<br />
Hotswapping is supposed to be supported as well, using hdparm to (un)register devices. This seems to be broken with 2.6 kernels (see below). <br />
<br />
Under Debian try using the hotswap package (tested with kernel 2.6.13 and a T42).<br />
<br />
The IBM-ACPI kernel module (http://ibm-acpi.sourceforge.net) has an eject function ("echo eject > /proc/acpi/ibm/bay"). This was broken when tested with kernel 2.6.8.1 (after re-inserting the drive it would not read CDs).<br />
It has since been made part of the official kernel, and the hotswap function has been fixed. Tested with kernel 2.6.14.2 and IBM-ACPI built-in. Debian hotswap also works (compiled from source on Slackware 9.1). Test machine was a T23.<br />
<br />
Only IDE devices (HDD's, optical drives, zip drives?) need special treatment- batteries, floppies and other devices can just be pulled from the bay, provided they are not mounted or in use at the time.<br />
<br />
==External Sources==<br />
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-50366 IBMs page on using a second hard drive adapter in the Ultrabay 2000 slot under Linux]<br />
<br />
{{footnotes|<br />
#IBM originally used the spelling UltraBay with a capital B and later switched to Ultrabay with a lower b. We are sticking with the capital B here.<br />
}}<br />
<br />
[[Category:Glossary]]</div>80.42.236.205