ThinkWiki - User contributions [en]

User:Roo

2013-08-16T19:29:29Z

Roo: Ping Edit

Email roo -At- eserver.homelinux.org<br />
xmpp root -At- eserver.homelinux.org

== Machine ==

[[:Category:T61p|Thinkpad T61p]]

== Ping Edit ==
account is alive

Category:T61p

2012-03-06T08:20:21Z

Roo: Removed Maintenace Manual for the non p Version

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad T61p ===
This pages gives an overview of all ThinkPad T61p related topics.

ref: {{LNVDOCURL|PD004986|Lenovo Support & downloads - Overview - ThinkPad T61, T61p}}<br>
ref: {{LNVDOCURL|PD008989|Lenovo Detailed Specifications - ThinkPad T61/T61p}}

==== Standard Features ====
* One of the following standard voltage processors:
** [[Intel Core 2 Duo (Merom)]] 1.8, 2.0, 2.2, 2.4 or 2.6 GHz 800MHz, 2-4MB L2 Cache CPU
** [[Intel Core 2 Duo (Penryn)]] 2.1, 2.4, 2.5, 2.6 GHz 800MHz FSB, 3-6MB L2 Cache CPU
* One of the following discrete graphics adapters:
** [[nVidia Quadro FX 570M]] (128 MB) (Only in 14.1")
** [[nVidia Quadro FX 570M]] (256 MB) (Only in 15.4")
* One of the following displays:
** 14.1" TFT display with 1400x1050 (SXGA+) resolution
** 14.1" TFT display with 1400x900 (WXGA+) resolution
** 15.4" TFT display with 1680x1050 (WSXGA+) resolution
** 15.4" TFT display with 1920x1200 (WUXGA) resolution
* 1 or 2 GB [[PC2-5300]] memory standard upgradable to 4 GB (Also see the [[unofficial maximum memory specs]] for this model.)
* 60, 80, 100, 120, or 160 GB 5400 rpm 2.5" SATA HDD
* 60, 100, 120, 160, or 200 GB 7200 rpm 2.5" SATA HDD
** [[Full Disk Encryption (FDE)]] Available on some models
* Intel HD Audio with [[AD1984|AD1984JCP]] codec
* [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* [[UltraBay|UltraBay Slim]] with one of the following:
** [[UltraBay Slim Super Multi-Burner Drive]]
* [[MiniPCI Express slot]] 1 with one of the following:
** None (empty)
** [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]
** [[ThinkPad 11a/b/g/n Wireless LAN Mini Express Adapter]]
** [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]
** [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter]]
* [[MiniPCI Express slot]] 2 with one of the following:
** None (empty, not upgradable)
** [[Sierra Wireless MC5720|Verizon 1xEV-DO WWAN Adapter]]
** 1GB [[Intel® Turbo Memory hard drive cache]]
* [[MiniPCI Express slot]] 3 with one of the following:
** None (empty, not upgradable)
** [[Wireless USB (UWB)]]
* 1 [[CardBus slot]] (Type 2)
* 1 Slot with one of the following:
** [[ExpressCard slot|ExpressCard/54 slot]]
** [[Lenovo_Integrated_Smart_Card_Reader|SmartCard reader]]
* [[Ricoh_R5C843|4-in-1 Memory reader]]
* [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
* [[Active Protection System]]
* [[Integrated Fingerprint Reader]] on select models
* [[ThinkPad_Bluetooth_with_Enhanced_Data_Rate_(BDC-2)|Bluetooth]] on select models
* [[ThinkPad 56K Modem (MDC-1.5)]]
* [[UltraNav]] (TrackPoint / Touchpad combo)
* [[Firewire Port|Firewire 400]] (IEEE1394a) on select models
* [[Intel Active Management Technology (AMT)]] on select models
* [[Centrino Pro]] on select models
</div>
|style="vertical-align:top" |
[[Image:t60-models_nov06.jpg|ThinkPad T61]]
|}

==== Resources ====
* {{LNVDOCURL|PD004986|T61 Product Overview}}
* {{LNVDOCURL|UM000396|T61/p 15.4" Widescreen Hardware Maintenance Manual}}
* {{LNVDOCURL|UM001177|T61,T61p 14.1" standard screen Hardware Maintenance Manual}}
* {{LNVDOCURL|UM000546|T60/p Service and Troubleshooting Guide}}
* {{LNVDOCURL|UM001438|T61 Setup Guide}}
* [http://www5.pc.ibm.com/europe/me.nsf/LenovoDetail?OpenAgent&key=Notebooks:ThinkPad:ThinkPad+T+Series:Data+Sheet:English&&cntry=EUROPE-L T61 DataSheet]
* {{LNVDOCURL|PD004527|T61/p 14.1" (standard screen) System service parts}}
* {{LNVDOCURL|PD004343|T61/p 15.4" System service parts}}

==== Reviews ====
* [http://www.xyzcomputing.com/index.php?option=content&task=view&id=1134 XYZ Computing], 2007-08-20
* [http://www.laptopmag.com/Review/Lenovo-ThinkPad-T61p.htm LAPTOP Magazine], 2007-08-08
* [http://www.notebookreview.com/default.asp?newsID=3889 NotebookReview.com], 2007-08-14
* [http://reviews.digitaltrends.com/review4745.html DigitalTrends], 2007-09-11
* [http://www.notebookcheck.com/Test-Lenovo-Thinkpad-T61p-Notebook.4401.0.html Notebookcheck.com], ??-08-2007 (german)

====Installation Instructions====
* [[Installation instructions for the ThinkPad T61p]]

[[Category:T Series]]

Category:T61p

2012-03-06T08:19:08Z

Roo: Added Maintenance Manuals for the different Versions

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad T61p ===
This pages gives an overview of all ThinkPad T61p related topics.

ref: {{LNVDOCURL|PD004986|Lenovo Support & downloads - Overview - ThinkPad T61, T61p}}<br>
ref: {{LNVDOCURL|PD008989|Lenovo Detailed Specifications - ThinkPad T61/T61p}}

==== Standard Features ====
* One of the following standard voltage processors:
** [[Intel Core 2 Duo (Merom)]] 1.8, 2.0, 2.2, 2.4 or 2.6 GHz 800MHz, 2-4MB L2 Cache CPU
** [[Intel Core 2 Duo (Penryn)]] 2.1, 2.4, 2.5, 2.6 GHz 800MHz FSB, 3-6MB L2 Cache CPU
* One of the following discrete graphics adapters:
** [[nVidia Quadro FX 570M]] (128 MB) (Only in 14.1")
** [[nVidia Quadro FX 570M]] (256 MB) (Only in 15.4")
* One of the following displays:
** 14.1" TFT display with 1400x1050 (SXGA+) resolution
** 14.1" TFT display with 1400x900 (WXGA+) resolution
** 15.4" TFT display with 1680x1050 (WSXGA+) resolution
** 15.4" TFT display with 1920x1200 (WUXGA) resolution
* 1 or 2 GB [[PC2-5300]] memory standard upgradable to 4 GB (Also see the [[unofficial maximum memory specs]] for this model.)
* 60, 80, 100, 120, or 160 GB 5400 rpm 2.5" SATA HDD
* 60, 100, 120, 160, or 200 GB 7200 rpm 2.5" SATA HDD
** [[Full Disk Encryption (FDE)]] Available on some models
* Intel HD Audio with [[AD1984|AD1984JCP]] codec
* [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* [[UltraBay|UltraBay Slim]] with one of the following:
** [[UltraBay Slim Super Multi-Burner Drive]]
* [[MiniPCI Express slot]] 1 with one of the following:
** None (empty)
** [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]
** [[ThinkPad 11a/b/g/n Wireless LAN Mini Express Adapter]]
** [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]
** [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter]]
* [[MiniPCI Express slot]] 2 with one of the following:
** None (empty, not upgradable)
** [[Sierra Wireless MC5720|Verizon 1xEV-DO WWAN Adapter]]
** 1GB [[Intel® Turbo Memory hard drive cache]]
* [[MiniPCI Express slot]] 3 with one of the following:
** None (empty, not upgradable)
** [[Wireless USB (UWB)]]
* 1 [[CardBus slot]] (Type 2)
* 1 Slot with one of the following:
** [[ExpressCard slot|ExpressCard/54 slot]]
** [[Lenovo_Integrated_Smart_Card_Reader|SmartCard reader]]
* [[Ricoh_R5C843|4-in-1 Memory reader]]
* [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
* [[Active Protection System]]
* [[Integrated Fingerprint Reader]] on select models
* [[ThinkPad_Bluetooth_with_Enhanced_Data_Rate_(BDC-2)|Bluetooth]] on select models
* [[ThinkPad 56K Modem (MDC-1.5)]]
* [[UltraNav]] (TrackPoint / Touchpad combo)
* [[Firewire Port|Firewire 400]] (IEEE1394a) on select models
* [[Intel Active Management Technology (AMT)]] on select models
* [[Centrino Pro]] on select models
</div>
|style="vertical-align:top" |
[[Image:t60-models_nov06.jpg|ThinkPad T61]]
|}

==== Resources ====
* {{LNVDOCURL|PD004986|T61 Product Overview}}
* {{LNVDOCURL|UM000396|T61/p 15.4" Widescreen Hardware Maintenance Manual}}
* {{LNVDOCURL|UM001583|T61 14.1 Hardware Maintenance Manual}}
* {{LNVDOCURL|UM001177|T61,T61p 14.1" standard screen Hardware Maintenance Manual}}
* {{LNVDOCURL|UM000546|T60/p Service and Troubleshooting Guide}}
* {{LNVDOCURL|UM001438|T61 Setup Guide}}
* [http://www5.pc.ibm.com/europe/me.nsf/LenovoDetail?OpenAgent&key=Notebooks:ThinkPad:ThinkPad+T+Series:Data+Sheet:English&&cntry=EUROPE-L T61 DataSheet]
* {{LNVDOCURL|PD004527|T61/p 14.1" (standard screen) System service parts}}
* {{LNVDOCURL|PD004343|T61/p 15.4" System service parts}}

==== Reviews ====
* [http://www.xyzcomputing.com/index.php?option=content&task=view&id=1134 XYZ Computing], 2007-08-20
* [http://www.laptopmag.com/Review/Lenovo-ThinkPad-T61p.htm LAPTOP Magazine], 2007-08-08
* [http://www.notebookreview.com/default.asp?newsID=3889 NotebookReview.com], 2007-08-14
* [http://reviews.digitaltrends.com/review4745.html DigitalTrends], 2007-09-11
* [http://www.notebookcheck.com/Test-Lenovo-Thinkpad-T61p-Notebook.4401.0.html Notebookcheck.com], ??-08-2007 (german)

====Installation Instructions====
* [[Installation instructions for the ThinkPad T61p]]

[[Category:T Series]]

CompactFlash boot drive

2011-12-27T18:59:44Z

Roo: /* useful links */

__NOTOC__
[[image:Addonics.JPG|thumb|Addonics Dual CF-IDE HDD Adapter with 8GB SanDisk Extreme IV CompactFlash]]
Changing your HDD for a CF boot drive (CompactFlash card on CF-PATA/SATA adapter) is an alternative to using SSD to boost the performance.

This is primarily done by ThinkPad {{X40}}, {{X41}} and {{X41 Tablet}} series owners due to the extremely slow speed of 1.8" HDD.

Previously, using Compact Flash cards meant giving up on storage capacity. Nowadays the biggest available CF sizes are up to 100 GB so you even gain more storage space compared to a classic 1.8" HDD.

ThinkPads utilizing PATA controller for the HDD slot can recognize both CF cards installed on a dual adapter. While newer ThinkPads, such as X41, which utilize SATA controller, can only recognize the single card installed on the primary slot.

===Advantages of CF boot drive===
* Much faster access time (<1ms for CF, >20ms for 4200RPM HDD and >15ms for 5400RPM HDD)
* Higher read throughput for >8KB blocks (may differ depending on brand, model, partition type and cluster size)
* Higher write throughput for >64KB blocks (may differ depending on brand, model, partition type and cluster size)
* Minimal risk of mechanical damage due to shock and vibration. [[Active Protection System]] is therefore unnecessary)
* Does not generate any noise or vibrations
* (Possibly) a slight increase in battery life
* (Possibly) less heat being generated

===Disadvantages of CF boot drive===
* Lower read throughput for <8KB blocks (may differ depending on brand, model, partition type and cluster size)
* Lower write throughput for <64KB blocks (may differ depending on brand, model, partition type and cluster size)
* Lower capacity
* Higher price per GB
* Not officially supported
* Invoke boot error 2010 on certain ThinkPads, including the X41 series

{{NOTE|A often mentioned disadvantage of flash-based storage is the limited number of write cycles (typically 100,000 for the current generation Single-Level Cell (SLC) NAND, the type usually used in the faster CF cards). This should not however be as much of an issue because...<br>
* The 100,000 write cycles applies to each address block separately in the card, not to the card as a whole<br>
* The flash controller automatically distribute write operations evenly (wear leveling), so that the number of writes to each address block is kept low<br>
Therefore, it should take years of typical real world usage to render a current flash memory card based on SLC NAND unusable<br>

However, manufacturers have started in 2008 using Multi-Level Cell (MLC) NAND to make SSD. MLC NAND typically has only about 10,000 write cycles. To complicate things further a company called EasyCo claims her Managed Flash Technology (MFT) "increases the write-life of Flash Disks more than 50-fold", which could be what made possible the launch of SSD based on MLC NAND. <br>

If in doubt, check with the manufacturer directly for details.

See [http://www.storagesearch.com/ssdmyths-endurance.html] and [http://www.storagesearch.com/ssd-slc-mlc-notes.html] for more information.}}

==What you need==
* A passive CF to PATA/SATA adapter
** Sadly, the X30's native CF slot does not appear to be bootable, so you're stuck using an adapter in the PATA drive sled like everyone else.
* One or more CompactFlash cards with the following parameters:
** (For Windows) Identify itself as a fixed disk instead of removable media
** (Preferably) UDMA support
** (Preferably) 266X speed or better

==CF to PATA/SATA adapter==
===CF to PATA (IDE)===
These adapters will work with both ThinkPads with 1.8" and 2.5" HDD slot with PATA interface
* Addonics AD44MIDECF (single slot) [http://www.addonics.com/products/flash_memory_reader/ad44midecf.asp]
* Addonics AD44MIDE2CF (dual slot) [http://www.addonics.com/products/flash_memory_reader/ad44midecf.asp]

{{WARN|Many of the adapters sold in eBay may not be usable for x40 as their #1 pin is on the left side (looking from the top, usually marked by a white diagonal line). The #1 pin should be on the right side as the Addonics series. Flipping the insertion of popular "V B1" adapter works but there is no guarantee of performance and space may not permit. On the other hand PA-CF18H adapter has been reported to work fine and may be a good alternative for Addonics converters. Please read page 15 of the forum discussion link below this page.}}

{{WARN|The second (slave) slots on dual slot adapters do not work on newer ThinkPads, including the {{X41}}, {{X41T}}, {{T43}}, {{T43p}} and {{R52}}. Because their IDE interface is actually connected to the SATA controller via an IDE-SATA bridge.
The second slot works fine on the others, like the X40, which use a native PATA controller, and 2 separated drives will be recognized.}}

{{WARN|On the {{X41}}, {{X41T}}, {{T43}}, {{T43p}} and {{R52}}, the system will complain that an unsupported disk is installed (Error 2010), but will continue to boot after 5-10 seconds or after pressing enter (assuming you have a recent BIOS installed). The beeps can be muted by using the hardware mute button before the last shutdown/reboot}}

===CF to SATA===
These adapters are needed for newer ThinkPads with native SATA interface.
{{Todo|If someone has tested any, please add them here}}

==CompactFlash cards==

===Speed===
While many CF cards claim to have high throughput, it's not necessarily a good indicator. As the claimed throughput is usually only attainable in specific situations (usually sequential and large block operations). But in typical usage as a boot drive, it usually involves lots of random and small block operations.

Therefore, the actual performance figures can only be found out via real world benchmarks.

Below is a list of some of the cards reported to be working, it's by no mean authoritative and final.

{{WARN|
Most CompactFlash cards by default identify themselves as '''removable media''' instead of '''fixed disk'''. Which is fine for Linux, but not for Windows.

If you have to use a CF card that has the type bits set to Removable and want to install Windows XP you can work around it as follows;
* Use Linux to partition the drive with a FAT32 partition (you can boot from one of the LiveCD/LiveUSB distributions for this), and set the partition bootable.
* Start the install of Windows, during install you will be given the opportunity to migrate to NTFS
* After the install is finished you will need to install the Hitachi microdrive disk drivers (google for XPfildrvr1224.zip), which will mask the removable bits and should allow suspend and other operations that fail on a removable drive to work.}}

===Transcend 133X/266X/300X===
These cards are known to identify themselves as fixed disk via CF-IDE adapters without any manual intervention, and is of good value, and speed (for 266X/300X).

===SanDisk Extreme===
SanDisk used to provide a utility (when asked) under NDA to change the type bit to Fixed disk. It has however changed it stance on this and now refuses to provide it. This utility (ATCFWCHG.COM) however can be found for download at various places (try Google).

You will need to boot DOS and run it with the CF configured as either the master on the primary IDE interface or the master on the secondary interface. It will not work if the drive is attached as a slave or to any other interfaces.

To set a SanDisk Extreme adapter attached to the primary IDE interface to Fixed disk
ATCFWCHG.COM /P /F
To set a SanDisk Extreme adapter attached to the secondary IDE interface (Ultrabay) to Fixed disk
ATCFWCHG.COM /S /F

{{NOTE|It seems that the ATCFWCHG.EXE utility is incompatible with SATA to IDE bridges, such as found in the X41. In those cases you will have to connect the CF card to another computer or ThinkPad with a regular IDE (PATA) interface to change the flag, after which you can put it into the ThinkPad X41.}}

===SanDisk Ultra II 4 GB===
This card doesn't work with the Debian stable 2.6.26 kernel in a X41 tablet with SATA controller, it seems to be to slow.

===Kingston Ultimate===
The Kingston Ultimate CF card ships as CF-Removable, and although Kingston admits it is possible to change the type to Fixed disk, it was not willing when asked to provide a tool/application for this purpose.

But supposedly the Kingston card automatically changes ID based on the adapter used, so it will ID as fixed disk when used with an IDE-CF or SATA-CF adapter, but will ID as CF-Removable when used with a PCMCIA adapter.

===Silicon Power 300X===
to be updated

===Photofast 533X===
Works fine, read performance up to 43mbit/s acording to hdparm

==Storage capacity issues==
Due to the limited capacity for high speed CF cards, the space may not be enough for some users. As a typical OS may already consume 3-4GB already. Here are some suggestions on how to work around it. Each of the below suggestion has its pros and cons, and should be selected on a case-to-case basis.
* Put only the OS and frequently accessed files on the main CF card
* (If dual-CF is possible) Add a second CF card, which will show up as an additional drive. Moreover since the speed needs not be as fast as the main CF card, a slower card with larger capacity could be desirable.
* On certain ThinkPads, there is an internal card reader (e.g. CF on X20/X30, and SD/SDHC on X40/X41/X60/X61) which can house another flash card. However, the speed is certainly to be worse than connecting to the PATA/SATA interface.
* Use a PC Card/ExpressCard SSD drive. However, the price of SSD is likely to be more expensive than flash cards.
* Use a PC Card/ExpressCard flash reader to house another flash card.
* Use a USB drive. Take mind that the drive will stick out, which is less desirable as a permanent solution (appearance/damage/speed especially if USB 2.0 is not supported)
* (If network access is readily available) Store the files on a network drive (e.g. server disk/NAS)

==Linux issues==
With the Addonics adapters listed above (and possibly with other ones as well), the kernel's libata driver might warn about a 40-wire cable and default to UDMA/33 operation:

<pre>
[ 27.831146] ata1.00: limited to UDMA/33 due to 40-wire cable
[ 27.846808] ata1.00: configured for UDMA/33
</pre>

This has been observed with version 2.6.24 of the kernel, and it may affect older ones, too. A patch is available from [http://permalink.gmane.org/gmane.linux.ide/26879] that adds a <tt>force_cbl</tt> kernel parameter. After applying the patch and recompiling the kernel, you can then set <tt>force_cbl=80</tt>:

<pre>
[ 7.140864] ata1: forcing 80c
[ 7.140886] ata1.00: CFA: LEXAR ATA FLASH CARD, 20071016, max UDMA/100
[ 7.140890] ata1.00: 7831152 sectors, multi 0: LBA
[ 7.140908] ata1.00: forcing 80c
[ 7.141625] ata1.00: configured for UDMA/100
</pre>

With the patch enabled, the above system achieves 42MB/sec read performance according to <tt>hdparm</tt>. Without it, performance suffers: 23MB/sec.

==Linux tuning==
* edit /etc/fstab and add the option noatime to disable writing of last access timestamps on each file or directory access for each ext3 filesystem
LABEL=/ / ext3 defaults,noatime 1 1
* disable swap (remove swap volume from /etc/fstab), just make sure you have enough memory installed (which since memory is cheap, should be easy to just max out the machine!)
* increase writeback time (add the following line to /etc/rc.local)
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
* remove beagle (if installed) from your system, it indexes the filesystem, but causes disk activity and keeps your cpu busy
rpm -e beagle beagle-gnome beagle-evolution

== Windows tuning==
*** Instead of throwing together all kind of tweaks here, it's probably better to keep the tweaks be CF boot-specific... And link to another page showing the more generic tweaks... ***
Due to the space constraints of CF, you will want to do some tuning of Windows. In addition there are some tunes that help performance, and can even help in the case where your not changing your HDD to CF.
* Do a minimal Windows XP install (not a recovery) with nLite, this allows you to remove components of Windows before they even get to the HDD, such as Movie Maker, Windows Messenger and Outlook Express that you might not need, while at the same time slipstreaming the latest ServicePack (SP3 for XP). Alternatively if you cannot reinstall, you can try the public domain xplite program, but for it to be useful you need to pay, and it does not work with SP3.
* Disable NTFS from updating the last access of a file or directory on each access. This causes NTFS to do a write for each file read operation and writes are always slower, and with flash storage might not be a good idea, for this you need to set NtfsDisableLastAccessUpdate in your registry.
* Disable Indexing of the drive (drive properties)
* Compress the drive (NTFS only), this saves space and might in some cases even be faster as it will require less disk access (drive properties)
* Disable swap (system properties), just make sure you have enough memory (just max out the machine, RAM is cheap these days)
* Disable windows system restore (system properties), if you feel you can live without it. It reserves a defined amount of space for this purpose
* Do not enable Hibernation, it requires a huge hibernation file and suspend should be good enough.
* Disable programs from starting on boot that you do not need (do you really need Java, Adobe, Apple iTunes, etc from starting on boot each time?) with a program such as MSCONFIG (->Start ->Run -> msconfig)
* Disable Windows services that you do not need from starting on boot
* Only install the IBM/Lenovo applications you truly know you will need (in my case, only the Hotkey utility and the Wireless drivers package to be able to disable wireless with Fn-F5)
* Never do a full install of an application, do a custom install and prune the options to remove all the stuff you will never use
* Disable HW devices in device manager that you do not need (in my case, the Modem and Infrared)
* Only install drivers you actually need (video, ethernet, wireless and sound in my case), and remove the C:\DRIVERS directory after your done.
* Do not run defrag, it is pointless on flash media and just causes unnecessary writes!
With this I was able to Install Windows XP (SP3) with Office 2003 (SP2), IE7, WMP 11, Symantec Client Security, Adobe acrobat reader, Firefox, Thunderbird, Pidgin and Palm Desktop in addition to the necessary drivers in under 4GB of an 8GB CF card on a ThinkPad X40.

==useful links==
* [http://forum.thinkpads.com/viewtopic.php?t=41568 ThinkPads Forum discussion on the subject]
* [http://www.hjreggel.net/cardspeed/index.html Flash memory speed - check out the UDMA CF link]
* [http://www.nliteos.com/ nLite - Utility to create a minimal Windows install CD with fixes and drivers]
* [http://www.daniel-boehmer.de/cf-ssd.html using Compact Flash cards as SSD alternative]

Category:T61p

2011-11-05T18:43:28Z

Roo: replaced old ibm MIGR URLS with LNVDOCURL template

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad T61p ===
This pages gives an overview of all ThinkPad T61p related topics.

ref: {{LNVDOCURL|PD004986|Lenovo Support & downloads - Overview - ThinkPad T61, T61p}}<br>
ref: {{LNVDOCURL|PD008989|Lenovo Detailed Specifications - ThinkPad T61/T61p}}

==== Standard Features ====
* One of the following standard voltage processors:
** [[Intel Core 2 Duo (Merom)]] 1.8, 2.0, 2.2, 2.4 or 2.6 GHz 800MHz, 2-4MB L2 Cache CPU
** [[Intel Core 2 Duo (Penryn)]] 2.1, 2.4, 2.5, 2.6 GHz 800MHz FSB, 3-6MB L2 Cache CPU
* One of the following discrete graphics adapters:
** [[nVidia Quadro FX 570M]] (128 MB) (Only in 14.1")
** [[nVidia Quadro FX 570M]] (256 MB) (Only in 15.4")
* One of the following displays:
** 14.1" TFT display with 1400x1050 (SXGA+) resolution
** 14.1" TFT display with 1400x900 (WXGA+) resolution
** 15.4" TFT display with 1680x1050 (WSXGA+) resolution
** 15.4" TFT display with 1920x1200 (WUXGA) resolution
* 1 or 2 GB [[PC2-5300]] memory standard upgradable to 4 GB (Also see the [[unofficial maximum memory specs]] for this model.)
* 60, 80, 100, 120, or 160 GB 5400 rpm 2.5" SATA HDD
* 60, 100, 120, 160, or 200 GB 7200 rpm 2.5" SATA HDD
** [[Full Disk Encryption (FDE)]] Available on some models
* Intel HD Audio with [[AD1984|AD1984JCP]] codec
* [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* [[UltraBay|UltraBay Slim]] with one of the following:
** [[UltraBay Slim Super Multi-Burner Drive]]
* [[MiniPCI Express slot]] 1 with one of the following:
** None (empty)
** [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]
** [[ThinkPad 11a/b/g/n Wireless LAN Mini Express Adapter]]
** [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]
** [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter]]
* [[MiniPCI Express slot]] 2 with one of the following:
** None (empty, not upgradable)
** [[Sierra Wireless MC5720|Verizon 1xEV-DO WWAN Adapter]]
** 1GB [[Intel® Turbo Memory hard drive cache]]
* [[MiniPCI Express slot]] 3 with one of the following:
** None (empty, not upgradable)
** [[Wireless USB (UWB)]]
* 1 [[CardBus slot]] (Type 2)
* 1 Slot with one of the following:
** [[ExpressCard slot|ExpressCard/54 slot]]
** [[Lenovo_Integrated_Smart_Card_Reader|SmartCard reader]]
* [[Ricoh_R5C843|4-in-1 Memory reader]]
* [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
* [[Active Protection System]]
* [[Integrated Fingerprint Reader]] on select models
* [[ThinkPad_Bluetooth_with_Enhanced_Data_Rate_(BDC-2)|Bluetooth]] on select models
* [[ThinkPad 56K Modem (MDC-1.5)]]
* [[UltraNav]] (TrackPoint / Touchpad combo)
* [[Firewire Port|Firewire 400]] (IEEE1394a) on select models
* [[Intel Active Management Technology (AMT)]] on select models
* [[Centrino Pro]] on select models
</div>
|style="vertical-align:top" |
[[Image:t60-models_nov06.jpg|ThinkPad T61]]
|}

==== Resources ====
* {{LNVDOCURL|PD004986|T61 Product Overview}}
* {{LNVDOCURL|UM001583|T61 Hardware Maintenance Manual}}
* {{LNVDOCURL|UM000546|T60/p Service and Troubleshooting Guide}}
* {{LNVDOCURL|UM001438|T61 Setup Guide}}
* [http://www5.pc.ibm.com/europe/me.nsf/LenovoDetail?OpenAgent&key=Notebooks:ThinkPad:ThinkPad+T+Series:Data+Sheet:English&&cntry=EUROPE-L T61 DataSheet]
* {{LNVDOCURL|PD004527|T61/p 14.1" (standard screen) System service parts}}
* {{LNVDOCURL|PD004343|T61/p 15.4" System service parts}}

==== Reviews ====
* [http://www.xyzcomputing.com/index.php?option=content&task=view&id=1134 XYZ Computing], 2007-08-20
* [http://www.laptopmag.com/Review/Lenovo-ThinkPad-T61p.htm LAPTOP Magazine], 2007-08-08
* [http://www.notebookreview.com/default.asp?newsID=3889 NotebookReview.com], 2007-08-14
* [http://reviews.digitaltrends.com/review4745.html DigitalTrends], 2007-09-11
* [http://www.notebookcheck.com/Test-Lenovo-Thinkpad-T61p-Notebook.4401.0.html Notebookcheck.com], ??-08-2007 (german)

====Installation Instructions====
* [[Installation instructions for the ThinkPad T61p]]

[[Category:T Series]]

Template talk:IBMDOCURL

2011-11-05T18:29:37Z

Roo: /* moved description to the mainpage */ new section

= Usage guidelines =

{{WARN|MIGR Documents are being moved to Lenovo's support website, and getting renamed to DC123456 format. Luckily they put in a legacy link we can use for now, but where possible the new format should be used, for which a new [[Template_talk:LNVDOCURL|LNVDOCURL]] template has been created.}}

Use this template to link to any IBM/Lenovo MIGR documents. The MIGR and other Lenovo and IBM documents are kept in a database system accessed by a base URI. That base URI has been changed at least three times already, which causes a MASSIVE amount of broken links everywhere in ThinkWiki.

By using this template, we can fix them all in a central location.

Usage:
<nowiki>
{{IBMDOCURL|MIGR-12345|Hardware documentation for ThinkPad AK-47}}
</nowiki>

== moved description to the mainpage ==

i've moved the usage/description to the mainpage --[[User:Roo|Roo]] 19:29, 5 November 2011 (CET)

Template:ThinkWiki News

2011-11-05T17:01:48Z

Roo: replaced Template_talk:IBMDOCURL|LNVDOCURL with Template:IBMDOCURL|LNCDOCURL

{|
{{News|15.10.2011|We are pleases to announce our new partnership with [http://www.thinkpads.com/ thinkpads.com]}}
{{News|28.06.2011|ThinkWiki has been upgraded to [[Special:Version|MediaWiki 1.17.0]].}}
{{News|07.06.2011|'''ibm.com MIGR Doc links are dead!''' Please convert any dead links to use the [[Template:IBMDOCURL|IBMDOCURL]] or [[Template:LNVDOCURL|LNVDOCURL]] template}}
{{News|20.03.2011|User account creation temporarily disabled, until we have an effective way to reduce SPAM.}}
{{News|08.02.2011|ThinkWiki has been upgraded to [[Special:Version|MediaWiki 1.16.2]].}}
{{News|17.05.2010|ThinkWiki got shiny new [[ThinkWiki:Hardware|hardware]]!}}
|}

Category:X61 Tablet

2011-11-05T16:59:16Z

Roo: replaced old ibm MIGR URLS with LNVDOCURL template

Template:IBMDOCURL

2011-11-05T16:57:16Z

Roo:

= Usage guidelines =

{{WARN|MIGR Documents are being moved to Lenovo's support website, and getting renamed to DC123456 format. Luckily they put in a legacy link we can use for now, but where possible the new format should be used, for which a new [[Template_talk:LNVDOCURL|LNVDOCURL]] template has been created.}}

Use this template to link to any IBM/Lenovo MIGR documents. The MIGR and other Lenovo and IBM documents are kept in a database system accessed by a base URI. That base URI has been changed at least three times already, which causes a MASSIVE amount of broken links everywhere in ThinkWiki.

By using this template, we can fix them all in a central location.

Usage:
<nowiki>
{{IBMDOCURL|MIGR-12345|Hardware documentation for ThinkPad AK-47}}
</nowiki>
<onlyinclude>[http://support.lenovo.com/en_US/downloads/detail.page?&LegacyDocID={{{1}}} {{{2}}}]</onlyinclude>

Template:LNVDOCURL

2011-11-05T16:55:37Z

Roo: replaced noinclude with onlyinclude

= Usage guidelines =

Use this template to link to any Lenovo DS documents. The DS and other Lenovo documents are kept in a database system accessed by a base URI. That base URI has been changed at least twice already, which causes a MASSIVE amount of broken links everywhere in ThinkWiki.

By using this template, we can fix them all in a central location.

Usage:
<nowiki>
{{LNVDOCURL|DS12345|Hardware documentation for ThinkPad AK-47}}
</nowiki>
<onlyinclude>[http://support.lenovo.com/en_US/downloads/detail.page?DocID={{{1}}} {{{2}}}]</onlyinclude>

Template:LNVDOCURL

2011-11-05T16:49:49Z

Roo: copied the usage description to the template with noinclude

<noinclude>
= Usage guidelines =

Use this template to link to any Lenovo DS documents. The DS and other Lenovo documents are kept in a database system accessed by a base URI. That base URI has been changed at least twice already, which causes a MASSIVE amount of broken links everywhere in ThinkWiki.

By using this template, we can fix them all in a central location.

Usage:
<nowiki>
{{LNVDOCURL|DS12345|Hardware documentation for ThinkPad AK-47}}
</nowiki>
</noinclude>
[http://support.lenovo.com/en_US/downloads/detail.page?DocID={{{1}}} {{{2}}}]

Template:IBMDOCURL

2011-11-05T16:46:43Z

Roo:

<noinclude>
= Usage guidelines =

{{WARN|MIGR Documents are being moved to Lenovo's support website, and getting renamed to DC123456 format. Luckily they put in a legacy link we can use for now, but where possible the new format should be used, for which a new [[Template_talk:LNVDOCURL|LNVDOCURL]] template has been created.}}

Use this template to link to any IBM/Lenovo MIGR documents. The MIGR and other Lenovo and IBM documents are kept in a database system accessed by a base URI. That base URI has been changed at least three times already, which causes a MASSIVE amount of broken links everywhere in ThinkWiki.

By using this template, we can fix them all in a central location.

Usage:
<nowiki>
{{IBMDOCURL|MIGR-12345|Hardware documentation for ThinkPad AK-47}}
</nowiki>
</noinclude>
[http://support.lenovo.com/en_US/downloads/detail.page?&LegacyDocID={{{1}}} {{{2}}}]

Template:IBMDOCURL

2011-11-05T16:43:30Z

Roo: copied the usage description to the template with noinclude

<noinclude>
= Usage guidelines =

{{WARN|MIGR Documents are being moved to Lenovo's support website, and getting renamed to DC123456 format. Luckily they put in a legacy link we can use for now, but where possible the new format should be used, for which a new [[Template_talk:LNVDOCURL|LNVDOCURL]] template has been created.}}

Use this template to link to any IBM/Lenovo MIGR documents. The MIGR and other Lenovo and IBM documents are kept in a database system accessed by a base URI. That base URI has been changed at least three times already, which causes a MASSIVE amount of broken links everywhere in ThinkWiki.

By using this template, we can fix them all in a central location.

Usage:
<nowiki>
{{IBMDOCURL|MIGR-12345|Hardware documentation for ThinkPad AK-47}}
</nowiki>
</noinclude>

[http://support.lenovo.com/en_US/downloads/detail.page?&LegacyDocID={{{1}}} {{{2}}}]

How to hotswap Ultrabay devices

2010-01-08T16:50:25Z

Roo: /* Script for Ultrabay eject */ added link to possible fix on discussion page

The following discusses hotswap (AKA "hotplug") of devices in the [[Ultrabay]].

This page has a lot of old information. Some cleanup might be useful.

==Which driver?==
This may be confusing, so first a quick history lesson.

Older ThinkPads (up to the R51, T42p and X40) were fully IDE (PATA) for both the internal HDD and Ultrabay. For these there are two drivers, the modern libata based {{path|ata_piix}} and the old legacy {{path|piix}}/{{path|ide-disk}} combo. Most modern distributions will default to the {{path|ata_piix}} driver, which is really what you want anyway.

ThinkPads like the R52, T43, T43p, X41 and X41 Tablet are strange hybrids. They have a Serial-ATA (SATA) chipset for the internal disk controller, but the actual disk is still legacy IDE, using a separate SATA-PATA bridge chip. The Ultrabay, though, is still connected to the legacy IDE host controller. This results in a setup where the internal disk is handled by a SATA driver and the Ultrabay is handled by either {{path|ata_piix}} or {{path|piix}}/{{path|ide-disk}}.

ThinkPads like the R60, T60 and Z60 series are also hybrids, but they use a native SATA HDD internal. Ultrabay still uses legacy IDE (PATA) though. So just like with the previous models you end up with two separate drivers for the internal HDD and the Ultrabay.

The latest generation ThinkPads like the R400, R500, T400, T500, W500, W700, X200, and X301 are all fully SATA for both the internal HDD and the Ultrabay device, so both are handled by the same SATA driver.
{{Todo|Figure out in which category the X60 series ThinkPads truly belong. Some of these machines might have been shipped with a 1.8" HDD which is likely to be PATA, in fact the HMM even states so. But tabook and ltwbook only lists SATA models, so the 1.8" model might never have shipped. But even if it did there will be a SATA-PATA bridge chip, so from the OS it will look like SATA.}}

{| border="1" cellspacing="0" cellpadding="2"
|+Overview of disk interface types
! Thinkpad !! internal HDD !! Ultrabay !! Modern Driver !! Old Driver
|-
| {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{A30p}}, {{A31}}, {{A31p}} || Legacy 2.5" IDE (PATA) || Legacy IDE (PATA) || ata_piix || piix + ide-disk
|-
| {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{R50}}, {{R50e}}, {{R50p}}, {{R51}} || Legacy 2.5" IDE (PATA) || Legacy IDE (PATA) || ata_piix || piix + ide-disk
|-
| {{R52}} || Legacy 2.5" PATA HDD with conversion to SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{R60}}, {{R61}} || 2.5" SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{R400}}, {{R500}} ||2.5" SATA || SATA || ahci || -
|-
| {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}} || Legacy 2.5" IDE (PATA) || Legacy IDE (PATA) || ata_piix || piix + ide-disk
|-
| {{T43}}, {{T43p}} || Legacy 2.5" PATA HDD with conversion to SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{T60}}, {{T60p}}, {{T61}}, {{T61p}} || 2.5" SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{T400}}, {{T500}} ||2.5" SATA || SATA || ahci || -
|-
| {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X32}} || Legacy 2.5" IDE (PATA) || Legacy IDE (PATA) || ata_piix || piix + ide-disk
|-
| {{X40}} || Legacy 1.8" IDE (PATA) || Legacy IDE (PATA) || ata_piix || piix + ide-disk
|-
| {{X41}}, {{X41t}} || Legacy 1.8" PATA HDD with conversion to SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{X60}}, {{X60s}}, {{x60t}}, {{x61}}, {{x61s}}, {{x61t}} || 2.5" HDD is SATA, 1.8" HDD is PATA with SATA conversion || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{X300}} ||2.5" SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
| {{X200}}, {{X200 Tablet}}, {{X301}} ||2.5" SATA || SATA || ahci || -
|-
| {{W500}}, {{W700}} ||2.5" SATA || SATA || ahci || -
|-
| {{Z60m}}, {{Z60t}}, {{Z61e}}, {{Z61m}}, {{Z61p}}, {{Z61t}} || 2.5" SATA || Legacy IDE (PATA) || ahci + ata_piix || -
|-
|}

{{NOTE|Debian users: at least up the the kernel released with Lenny, Debian applies a patch in the Debian kernel sources which prevents the use of <tt>ata_piix</tt> with PATA devices (like the IDE bus for the Ultrabay). You will have to either use an upstream kernel or (re)patch the Debian kernel sources.
You may want to have a look at the following Debian bug reports as well: [http://bugs.debian.org/444182 #444182], [http://bugs.debian.org/463833 #463833].}}

==Modern systems (using the <tt>ahci</tt> or <tt>ata_piix</tt> drivers)==
The following applies when using the <tt>ahci</tt> or <tt>ata_piix</tt> driver (which supercedes the old <tt>ide_disk</tt> driver).

You should at least be using a distribution with kernel 2.6.23. If you have a distribution with an older kernel, please update your distribution, as in addition to a newer kernel, you will need some of the newer userland tools.

===Using libata-acpi and udev===

Starting from kernel 2.6.26-rc5, it's possible to use <tt>libata-acpi</tt> in combination with udev to hotswap. Please check if CONFIG_ATA_ACPI is enabled in your kernel configuration.

For 2.6.25, you need two patches which can be easily backported ([http://article.gmane.org/gmane.linux.acpi.devel/31159],[http://article.gmane.org/gmane.linux.acpi.devel/31369]).

Create a file {{path|/etc/udev/rules.d/50-thinkpad-ultrabay.rules}} with the following contents:
<pre>
ENV{BAY_EVENT}=="3", ACTION=="change", SUBSYSTEM=="scsi", RUN+="/usr/local/sbin/ultrabay_eject"
</pre>
Then ensure it has the right permissions
chown root:root /etc/udev/rules.d/50-thinkpad-ultrabay.rules
chmod 644 /etc/udev/rules.d/50-thinkpad-ultrabay.rules
For Red Hat/Fedora and other systems with selinux, you also need to set the security context:
chcon system_u:object_r:etc_runtime_t:s0 /etc/udev/rules.d/50-thinkpad-ultrabay.rules

Now create the below ultrabay-eject script

===Script for Ultrabay eject===

The following script does the following:
* Automatically unmounts the relevant filesystems and power off the Ultrabay when the Ultrabay eject lever is released. Screams if some filesystem can't be unmounted.

Create a executable file {{path|/usr/local/sbin/ultrabay_eject}} with the following content. Note if you want to be able to run it directly (not by the UDEV eject script), then you need to manually edit the DEVPATH variable near the top of the script.
<pre>
#!/bin/bash

# Change the following DEVPATH= to match your system, if you want to run this directly instead of having it called by the udev eject script
# To find the right value, insert the UltraBay optical drive and run:
# udevadm info --query=path --name=/dev/sr0 | perl -pe 's!/block/...$!!'
if [ "$DEVPATH" = "" ]
then
DEVPATH="/devices/pci0000:00/0000:00:1f.2/host1/target1:0:0/1:0:0:0"
fi

shopt -s nullglob
export DISPLAY=:0.0 # required for notify-send
ULTRABAY_SYSDIR=/sys$DEVPATH

# Find generic dock interface for UltraBay
dock=$( /bin/grep -l ata_bay /sys/devices/platform/dock.?/type )
dock=${dock%%/type}
if [ -n "$dock" -a -d "$dock" ]; then
logger ultrabay_eject starting eject of $dock
else
logger ultrabay_eject cannot locate bay dock device
notify-send -u critical -t 100000 "ThinkPad Ultrabay eject failed" "Cannot locate bay dock device"
fi

# Umount the filesystem(s) backed by the given major:minor device(s)
unmount_rdev() { perl - "$@" <<'EOPERL' # let's do it in Perl
for $major_minor (@ARGV) {
$major_minor =~ m/^(\d+):(\d+)$/ or die;
push(@tgt_rdevs, ($1<<8)|$2);
}
# Sort by reverse length of mount point, to unmount sub-directories first
open MOUNTS,"</proc/mounts" or die "$!";
@mounts=sort { length($b->[1]) <=> length($a->[1]) } map { [ split ] } <MOUNTS>;
close MOUNTS;
foreach $m (@mounts) {
($dev,$dir)=@$m;
next unless -b $dev; $rdev=(stat($dev))[6];
next unless grep($_==$rdev, @tgt_rdevs);
system("umount","-v","$dir")==0 or $bad=1;
if ($bad == 1) {
system("logger","ultrabay_eject","ERROR unmounting",$dev,$dir);
system("notify-send -u critical -t 100000 \"Error unmounting $dir\" \"Unmounting of $dir on $dev failed!\"");
} else {
system("logger","ultrabay_eject","unmounted",$dev,$dir);
system("notify-send -u normal -t 5000 \"Unmounted $dir\"");
};
}
exit 1 if $bad;
EOPERL
}

# Get the UltraBay's /dev/foo block device node
ultrabay_dev_node() {
UDEV_PATH="`readlink -e "$ULTRABAY_SYSDIR/block/"*`" || return 1
UDEV_NAME="`udevadm info --query=name --path=$UDEV_PATH`" || return 1
echo /dev/$UDEV_NAME
}

if [ $( cat $dock/docked ) == 0 ]; then
logger ultrabay_eject dock reports empty
else
if [ -d $ULTRABAY_SYSDIR ]; then
logger ultrabay_eject dock occupied, shutting down storage device $DEVPATH
sync
# Unmount filesystems backed by this device
## This seems to be very inelegant and prone to failure
unmount_rdev `cat $ULTRABAY_SYSDIR/block/*/dev \
$ULTRABAY_SYSDIR/block/*/*/dev` \
|| {
logger ultrabay_eject umounting failed
echo 2 > /proc/acpi/ibm/beep # triple error tone
notify-send -u critical -t 100000 "ThinkPad Ultrabay eject failed" "Please do not pull the device, doing so could cause file corruption and possibly hang the system. Unmounting of the filesystem on the ThinkPad Ultrabay device failed. Please put the eject leaver back in place, and try to unmount the filesystem manually. If this succeeds you can try the eject again"
exit 1;
}
sync
# Nicely power off the device
DEVNODE=`ultrabay_dev_node` && hdparm -Y $DEVNODE
# Let HAL+KDE notice the unmount and let the disk spin down
sleep 0.5
# Unregister this SCSI device:
sync
echo 1 > $ULTRABAY_SYSDIR/delete
else
logger ultrabay_eject bay occupied but incorrect device path $DEVPATH
notify-send -u critical -t 100000 "ThinkPad Ultrabay eject failed" "Bay occupied but incorrect device path"
echo 2 > /proc/acpi/ibm/beep # triple error tone
exit 1
fi
fi

# We need sleep here so someone can disconnect the bay and the drive
sleep 1

# Turn off power to the UltraBay
logger ultrabay_eject undocking $dock
echo 1 > $dock/undock

# Tell the user we're OK
logger ultrabay_eject done
echo 12 > /proc/acpi/ibm/beep
notify-send -u normal -t 10000 "Safe to remove device" "The ThinkPad Ultrabay device can now safely be removed"
</pre>
an possible fix for the notify not working thing is here [[Talk:How_to_hotswap_Ultrabay_devices#get_notify-send_working]]

Then make sure ownership and permissions are set correct
chown root:root /usr/local/sbin/ultrabay_eject
chmod 555 /usr/local/sbin/ultrabay_eject

If the <tt>ata_piix</tt> driver is built in the kernel, it will catch bay events and you will see the
following message in your system log:
<pre>
thinkpad_acpi: another device driver is already handling bay events
thinkpad_acpi: disabling subdriver bay
</pre>
You should load <tt>thinkpad_acpi</tt> before <tt>ata_piix</tt> if you want it to handle bay events.

===Script for Ultrabay insert===
{{WARN|Only needed for kernels prior to 2.6.26}}
Create {{path|/usr/local/sbin/ultrabay_insert}} with the following content:
#!/bin/bash
echo 12 > /proc/acpi/ibm/beep
sync
echo 0 0 0 > /sys/class/scsi_host/host1/scan

and set the right permissions
chown root:root /usr/local/sbin/ultrabay_insert
chmod 555 /usr/local/sbin/ultrabay_insert

===Using the generic bay driver and udev===
{{WARN|If you have kernel 2.6.26 or newer, please use the above [[#Using libata-acpi and udev]] method instead}}
Starting from kernel 2.6.23-rc3, it's possible to use the generic <tt>bay</tt> driver in combination with udev to hotswap. Please check if CONFIG_ACPI_BAY is enabled (module or built-in) in your kernel configuration.

Create {{path|/etc/udev/rules.d/ibm-ultrabay.rules}}:
ENV{BAY_EVENT}=="3", KERNEL=="bay.0", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_eject"
ENV{BAY_EVENT}=="1", KERNEL=="bay.0", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_insert"

Starting with kernel 2.6.28, the <tt>bay</tt> driver was removed from the mainline kernel. The <tt>dock</tt> driver replaced it completely. Make sure CONFIG_ACPI_DOCK is enabled in the kernel, and use the following udev rules:

ENV{EVENT}=="undock", KERNEL=="dock.2", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_eject"
ENV{EVENT}=="dock", KERNEL=="dock.2", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_insert"

However, the ultra_eject script needs to be changed, otherwise udev goes into an infinite event loop. It will send undock events every few seconds forever. That means as soon as the ultrabay is plugged in again, it will be immediately ejected. For kernels 2.6.28 and higher, the bay cannot be powered off using this method, so change the end of the script to read:
# Turn off power to the UltraBay:
if [ -d /sys/devices/platform/bay.0 ]; then
echo 1 > /sys/devices/platform/bay.0/eject
elif [ -e /proc/acpi/ibm/bay ]; then
echo eject > /proc/acpi/ibm/bay
fi
# Tell the user we're OK
echo 12 > /proc/acpi/ibm/beep

Alternatively, instead of modifying the script, use the libata-acpi method below.
This was tested on a T61p running Gentoo with tuxonice 2.6.28-r8 without any issues.

===HAL support===
{{HELP| If the script below does not work, please provide your lshal output on the [[Talk:How_to_hotswap_Ultrabay_devices]] page}}
{{NOTE| If your HAL version is older then 0.5.11, you need to replace "info.parent" with "storage.physical_device".}}

HAL support is only needed for proper notification to your desktop applications, such as Gnome and KDE. You will still require the udev script to handle the proper removal.

To tell HAL that devices connected to the UltraBay port are hotpluggable, you need to create a file {{path|/etc/hal/fdi/information/10-thinkpad-ultrabay.fdi}} with the following content:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 



<deviceinfo version="0.2">
<device>
<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" prefix="ThinkPad">
<match key="/org/freedesktop/Hal/devices/computer:system.hardware.vendor" string="IBM">


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="A20;A21;A22;T20;T21;T22;X20;X21">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_7111_scsi_host_0_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="T23;T30;X22;X23;X24;X30">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_248a_scsi_host_0_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="A30;A31">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_248a_scsi_host_scsi_device_lun0_0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_248a_scsi_host_0_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="R50;R51;T40;T41;T42;X31;X32;X40">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_24ca_scsi_host_0_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="R52;T43;X41;Z60">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>

</match>
<match key="/org/freedesktop/Hal/devices/computer:system.hardware.vendor" string="LENOVO">


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="T60;Z61">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_27df_scsi_host_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="R60;X60">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_27c4_scsi_host_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="R61;T61;X300">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_2850_scsi_host_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>


<match key="/org/freedesktop/Hal/devices/computer:system.hardware.version" contains_outof="R400;R500;T400;T500;W500;W700;X200;X301">
<match key="storage.bus" string_outof="pci;scsi">
<match key="info.parent" string="/org/freedesktop/Hal/devices/pci_8086_2929_scsi_host_0_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>
</match>

</match>
</match>
</device>
</deviceinfo>
</pre>

Then ensure it has the right permissions

chown root:root /etc/hal/fdi/information/10-thinkpad-ultrabay.fdi
chmod 644 /etc/hal/fdi/information/10-thinkpad-ultrabay.fdi

To check the effect, look at your lshal output, the section for your optical disk (/dev/sr0 typically) or your 2nd hdd (/dev/sdb typically) should have storage.hotpluggable = true after restarting your hal deamon or rebooting.

==When using the <tt>ide-disk</tt> driver==
The following applies if you use the <tt>ide-disk</tt> driver for the UltraBay device.<BR>
<b>Note that essentially, you shouldn't be using this driver, and use ata_piix instead unless you're running an older kernel where ata_piix won't work for you</b>

Hotswapping is supposed to be supported as well, using either hdparm/[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] or [[lt_hotswap]] to (un)register IDE devices. The latter is the recommended method with kernels from 2.6, since it will leave DMA working. However, for recent models (R52, T43, X41, Z60 and later) no method is known to work while maintaining DMA support; see [[Problems with SATA and Linux]].

Only IDE devices (HDD's, optical drives, zip drives) require 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. However, you should still power them down first using the [[thinkpad-acpi]] eject function.

The [[thinkpad-acpi]] kernel module has an eject function ({{cmdroot|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. {{cmdroot|cat /proc/acpi/ibm/bay}} shows "unoccupied" unless an IDE device is present, but the eject function still works and should still be used.

To unregister the device, you can either use the [http://packages.debian.org/unstable/admin/hotswap Debian hotswap] package, or [[lt_hotswap]]. Note that lt_hotswap doesn't seem to even build on recent (at 2.6.22 or newer, although it probably broke before 2.6.22) and on newer kernels, you should not build/load the old IDE PIIX (CONFIG_BLK_DEV_PIIX) and use the natively hotswapping ata_piix (CONFIG_ATA_PIIX) as explained on the top of this page.

[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] also allows the drive to be swapped as a normal user by default, which is useful. You should use <tt>hotswap</tt> to unregister the device and then {{cmdroot|echo eject > /proc/acpi/ibm/bay}}. However, if you use this method on a 2.6 kernel, you will lose DMA support for the reinserted drive. This is due to kernel issues. This method was reported to work on a ThinkPad {{T23}} (kernels 2.6.8.1, 2.6.14.2 and 2.6.15-arch) and {{T42}} (kernel 2.6.13), but fails on a ThinkPad {{T43}} (kernel 2.6.14.3).

[[lt_hotswap]] is now the recommended method to un- and reregister the IDE device. It installs as a kernel module and has support for automatically unregistering (if loaded with the auto_eject=1 option) the device when the eject event is generated by [[thinkpad-acpi]]. It will leave DMA support intact. It has supported to work on a ThinkPad {{T22}} and {{T40}} and should work with many other models (but not recent models which require the <tt>ata_piix</tt> driver for disk DMA support). With the [[lt_hotswap]] kernel module loaded, run: {{cmdroot|modprobe -r ide_cd && modprobe -r cdrom && echo "MSTR eject" > /proc/acpi/lths}}

===HAL support===

HAL support also can also be configured To do so, create the file {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as follows:
<pre>
<?xml version="1.0" encoding="UTF-8"?> 

<deviceinfo version="0.2">
<device>


<match key="storage.bus" string="ide">
<match key="storage.physical_device" string="/org/freedesktop/Hal/devices/pci_8086_24ca_ide_1_0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>

</device>
</deviceinfo>
</pre>
For more details see HAL section for ata driver.

==Password protected HDD==

If you are hot-swapping a hard disk on a Ultrabay HDD tray, and the HDD has a password set, you will have to enter the password before it can be used. In theory you should be able to do so with hdparm as follows for a Master password:
hdparm --security-unlock PASSWD /dev/sdb
Or if it is a user password
hdparm --security-unlock PASSWD --user-master u /dev/sdb

However on my system with Fedora 11 the above returns "SECURITY_UNLOCK: Input/output error"

As such the only available option is to reboot and let the BIOS unlock the HDD.

[[Category:Scripts]]
[[Category:HOWTOs]]

Talk:How to hotswap Ultrabay devices

2010-01-08T16:47:36Z

Roo: /* get notify-send working */ replaced w with lastlog as w has an username length limit

=Recent Ubuntu versions=
I think, it must be mentioned that hotswapping Ultrabay devices using recent distros
is by far not that hard as before. I'm using Ubuntu 9.04 on Z61m and in my case hotswapping
Ultrabay DVD-RW works out-of-the-box without any scripts or whatsoever. The article
however suggests that one always needs some ejecting scripts which might confuse certain
users. So it would be nice to add something like: "If you are using Ubuntu *.** everything should
work out-of-the-box"

--[[User:Bombenbach|Bombenbach]] 12:01, 9 August 2009 (UTC)

Really? Did you try to swap out a Ultrabay device with mounted filesystem? Good luck!
The udev handler and eject script are there for a reason. By default no action is taken when you pull out a device, which can cause real problems if not handled properly.

--[[User:Tonko|Tonko]] 09:31, 10 August 2009 (UTC)

Well, actually I couldn't imagine that someone would like to pull out an Ultrabay device with mounted file system.
As far a usb flash drives are concerned, you won't do that either, right? My point was, that if the file system is '''properly unmounted''', I can simply pull my Ultrabay DVD-RW out without any freezes or crashes. And when I put it back again, the drive is automatically recognized by Ubuntu so that I can use it. I don't have an Ultrabay HDD, but I assume that if it works with DVD-RW it also should work with HDD. Correct me if I'm wrong. If the sole purpose of eject script is hotswapping Ultrabay devices '''with mounted filesystem''' then I still think that it would be nice to point it out in the article.

--[[User:Bombenbach|Bombenbach]] 07:52, 11 August 2009 (UTC)

By default on most modern distributions based on a recent kernel with libata, the libata driver gets to cleanup the mess after the fact, if you pull out an ultrabay device without first
* unmounting the filesystem
* powering down the device
You may be lucky, or you might end up with a hung system, corrupted filesystem, etc. Your choice.

There is work going on upstream to resolve this with DeviceKit-disks, but that depends on a patch to the Linux kernel, which has not made it in yet, since right now there is no correlation between the udev event and the actual Bay device, and since you can have multiple Bay devices (in fact your ThinkPad likely has 3) this correlation is needed, otherwise DeviceKit-disks would need to know about every single Laptop out there and the mapping between the Bay numbering and the actual devices (something the kernel can easily just provide instead).

Here is a Feature request against DeviceKit-disks that provides some status information
http://bugs.freedesktop.org/show_bug.cgi?id=23110

--[[User:Tonko|Tonko]] 09:07, 11 August 2009 (UTC)

=HAL script=

If the script works, your lshal output should contain something similar to this. In this case the Ultrabay device was a second HDD (/dev/sdb).

Note that in the example, storage.hotpluggable = true while before it was false, so the script worked.
<pre>
udi = '/org/freedesktop/Hal/devices/storage_serial_SATA_HTS726060M9AT00_MRH453M4H11ARB'
block.device = '/dev/sdb' (string)
block.is_volume = false (bool)
block.major = 8 (0x8) (int)
block.minor = 16 (0x10) (int)
block.storage_device = '/org/freedesktop/Hal/devices/storage_serial_SATA_HTS726060M9AT00_MRH453M4H11ARB' (string)
info.capabilities = {'storage', 'block'} (string list)
info.category = 'storage' (string)
info.parent = '/org/freedesktop/Hal/devices/pci_8086_24ca_scsi_host_0_scsi_device_lun0' (string)
info.product = 'HTS726060M9AT00' (string)
info.udi = '/org/freedesktop/Hal/devices/storage_serial_SATA_HTS726060M9AT00_MRH453M4H11ARB' (string)
info.vendor = 'ATA' (string)
linux.hotplug_type = 3 (0x3) (int)
linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1f.1/host1/target1:0:0/1:0:0:0/block/sdb' (string)
storage.automount_enabled_hint = true (bool)
storage.bus = 'pci' (string)
storage.drive_type = 'disk' (string)
storage.firmware_version = 'MH4O' (string)
storage.hotpluggable = true (bool)
storage.lun = 0 (0x0) (int)
storage.media_check_enabled = false (bool)
storage.model = 'HTS726060M9AT00' (string)
storage.no_partitions_hint = false (bool)
storage.originating_device = '/org/freedesktop/Hal/devices/computer' (string)
storage.partitioning_scheme = 'mbr' (string)
storage.removable = false (bool)
storage.removable.media_available = true (bool)
storage.removable.media_size = 60011642880 (0xdf8f90000) (uint64)
storage.requires_eject = false (bool)
storage.serial = 'SATA_HTS726060M9AT00_MRH453M4H11ARB' (string)
storage.size = 60011642880 (0xdf8f90000) (uint64)
storage.vendor = 'ATA' (string)
</pre>

{| border=1
|+ Known South Bridge PCI IDs
! ID !! ThinkPad model !! South Bridge chip (for Ultrabay) !! parent device (host_0, lun0 = 2nd ATA controller, master device)
|-
| 8086_7111 || A20m, A20p, A21e, A21m, A21p, A22e, A22m, A22p, T20, T21, T22, X20, X21 || Intel 82371AB/EB/MB PIIX4 IDE || /org/freedesktop/Hal/devices/pci_8086_7111_scsi_host_0_scsi_device_lun0
|-
| 8086_248a || T23, T30, X22, X23, X24, X30|| Intel 82801CAM IDE U100 (rev 2) || /org/freedesktop/Hal/devices/pci_8086_248a_scsi_host_0_scsi_device_lun0
|-
| 8086_248a || A30, A30p, A31, A31p|| Intel 82801CAM IDE U100 (rev 2) || /org/freedesktop/Hal/devices/pci_8086_248a_scsi_host_scsi_device_lun0_0<br>/org/freedesktop/Hal/devices/pci_8086_248a_scsi_host_0_scsi_device_lun0
|-
| 8086_24ca || R50, R51, T40, T40p, T41, T41p, T42, T42p, X31, X32, X40 || Intel 82801DBM (ICH4-M) || /org/freedesktop/Hal/devices/pci_8086_24ca_scsi_host_0_scsi_device_lun0
|-
| 8086_2653 || R52, T43, T43p, X41, Z60m, Z60t || Intel 82801FBM (ICH6-M) || /org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0
|-
| 8086_27c4 || R60, X60 || Intel 82801GBM (ICH7 Family) || /org/freedesktop/Hal/devices/pci_8086_27c4_scsi_host_scsi_device_lun0
|-
| 8086_27df || T60, T60p, Z61m, Z61t, Z61p || Intel 82801GBM/GHM (ICH7 Family) || /org/freedesktop/Hal/devices/pci_8086_27df_scsi_host_scsi_device_lun0
|-
| 8086_2850 || R61, T61, T61p, X300 || Intel 82801H (ICH8 Family) || /org/freedesktop/Hal/devices/pci_8086_2850_scsi_host_scsi_device_lun0
|-
| 8086_2929 || R400, R500, T400, T500, W500, W700, X200, X301 || Intel 82801I ICH9 Family || /org/freedesktop/Hal/devices/pci_8086_2929_scsi_host_0_scsi_device_lun0
|}
==lshal output==
Please place your lshal output here if you had problems

lshal of my A31: [http://nopaste.org/p/a4p6x9tSob http://nopaste.org/p/a4p6x9tSob]

Thanks! If I understand the output correctly you have one Toshiba Combo DVD-ROM/CD-RW R2002 in one ultrabay connected as slave to the primary IDE controller, and one Toshiba DVD-ROM C2512 in the second ultrabay connected as master to the secondary IDE controller. Can you confirm? I have added it to the table.

I have a Thinkpad T43 and I found out from my lshal output that I had to use parent device:
pci_8086_2653_scsi_host_0_scsi_device_lun0 instead of
pci_8086_2653_scsi_host_scsi_device_lun0 (notice the added 0).
This is the ultrabay, however, the internal disk still use the "original" parent device (the one without the 0).
I think this information should be added to the table.
Specs:
Thinkpad T43 (machine type 2668),
Mandriva One 2009.1,
haldaemon 0.5.12

Thanks, it is possible that you have AHCI mode disabled in the BIOS for your HDD?
--[[User:Tonko|Tonko]] 11:00, 31 July 2009 (UTC)

= bash script for hotswapping UltraBay =

Here is my script for hotswapping ultrabay, is more complex, supports swap partition on drive in ultrabay, check holders (useful, when you are using luks) and more :)

{{HELP|Please test on difrent models}}

ultrabay.sh
<pre>
#!/bin/bash
SCSI_DEVICE=""
FORCE_SLEEP="1"
QUIET="0"
SYSLOG="0"
BEEP="0"

Message()
{
MESSAGE="${0/*\//}: $*"
if [ "$QUIET" = "0" ]; then
echo "$MESSAGE"
fi
if [ "$SYSLOG" != "0" ]; then
/usr/bin/logger "$MESSAGE"
fi
true
}

Exit()
{
case "$1" in
"fail")
[ $BEEP != "0" ] && echo 2 > /proc/acpi/ibm/beep
exit 1
;;
"success")
[ $BEEP != "0" ] && echo 12 > /proc/acpi/ibm/beep
exit 0
;;
esac
}

Usage()
{
echo "usage: ${0/*\/} [options]"
echo "options:"
echo " -d <path> SCSI device (required)"
echo " -s Ignore fail when putting drive to sleep"
echo " -q No messages"
echo " -l Use syslog for messages (-q has no effect)"
echo " -b Use beep for notification (-q has no effect)"
exit 1
}

Block2Device()
{
/bin/readlink -e "/dev/block/$1"
}

IsSwap()
{
/sbin/swapon -s | grep -q -e "^$1\b"
}

IsMounted()
{
mount | grep -q -e "^$1\b"
}

HasHolders()
{
[ "$(ls "$1/holders")" ]
}

IsBusy()
{
DEVICE=$(Block2Device $(cat "$1/dev"))
if IsSwap "$DEVICE" || IsMounted "$DEVICE" || HasHolders "$1"; then
Message "device '$DEVICE' is busy"
false
else
true
fi
}

SleepDrive()
{
BLOCK=$(cat $SCSI_DEVICE/block/*/dev 2> /dev/null)
DEVICE=$(Block2Device "$BLOCK")
if ! /sbin/hdparm -Y "$DEVICE" &> /dev/null; then
Message "cannot put drive to sleep"
if [ $FORCE_SLEEP = "0" ]; then
true
else
false
fi
fi
}

DeleteScsiDevice()
{
if ! { echo 1 > $SCSI_DEVICE/delete; } &> /dev/null; then
Message "cannot delete device"
false
fi
}

GetDock()
{
grep "$1" /sys/devices/platform/dock.*/type | sed -e s%/type:.*%%
}

IsDocked()
{
[ $(cat $(GetDock "$1")/docked) -ne 0 ]
}

Undock()
{
{ echo 0 > $(GetDock "$1")/undock; } &> /dev/null
if IsDocked "$1"; then
Message "cannot undock UltraBay"
false
else
Message "UltraBay undocked"
true
fi

}

while getopts "d:qlsb" OPTION; do
case $OPTION in
d)
SCSI_DEVICE="$OPTARG"
;;
s)
FORCE_SLEEP="0"
;;
q)
QUIET="1"
;;
l)
SYSLOG="1"
;;
b)
BEEP="1"
;;
?)
Usage
;;
esac
done

if [ -d "$SCSI_DEVICE" ] && IsDocked "ata_bay"; then
sync
for DEV_DIR in $(ls $SCSI_DEVICE/block/*/*/dev $SCSI_DEVICE/block/*/dev | sed -e s/dev$// 2> /dev/null); do
IsBusy "$DEV_DIR" || Exit "fail"
done
sync
SleepDrive || Exit "fail"
DeleteScsiDevice || Exit "fail"
sleep 4
fi

if [ ! -d $SCSI_DEVICE ] && $(IsDocked "ata_bay"); then
if Undock "ata_bay"; then
Exit "success"
else
Exit "fail"
fi
fi

Message "UltraBay is already undocked"
Exit "success"
</pre>

Supported models: {{R400}} - linux-2.6.29
==comments==
Interesting, especially the support for swap partitions. but I have two comments, first your calling your script hotswap.sh and then having udev call ultrabay.sh?

Then your hard coding the location of the Ultrabay device. This is not guaranteed to be correct, although it will be in most cases. In particular the A and W-series machines. A-series had support for more then one Ultrabay device, while W-series has support for more then one internal HDD in addition to the Ultrabay device, so the Ultrabay location will shift. That is why the Ultrabay Eject script on the main page gets the eject device information from udev.

==comments==
Hi, thanks, I fix name of script :)
Udev calling ultrabay.sh with option -d, so it remove correct device, if you want remove device manualy, is default device useful. But option may be required...

==more comments ;)==
You might also have a look at the script on the main page, it has a few extra abilities, such as logging to syslog, beeping and putting up popups on the desktop.

Logging to syslog is simple, just call 'logger' with what you want to log. quite should have no effect on this.

For beeps, similar to what windows does you can echo different values to /proc/acpi/ibm/beep, but it only works if sound is not muted. Unfortunately doing so does seem to generate some annoying messages in syslog.

Lastly you can use notify-send to put up messages on the desktop, but before you can do so you have to do an export DISPLADISPLAY=0:0 /usr/bin/knotify4 --passive-popup : Adresář nebo soubor neexistujeY=:0.0

==Syslog and beep==
OK, scrip now support syslog and beeping :).

Still missing notify-send ;)

I am also thinking that it would be useful in the case of a busy filesystem to tell the user to run something like fuser -mv /dev/sr0<br>
Or perhaps we should run it ourselves automatically and just tell the user what is the cause of the busy filesystem.<br>
--[[User:Tonko|Tonko]] 21:21, 8 June 2009 (UTC)

== get notify-send working ==

Hi there,

I've modified your ultrabay_eject script so that the notify-send is working for the user which is logged onto screen :0
for an unified diff see below, here is the whole modified script

* whole script
<pre>
#!/bin/bash

# Change the following DEVPATH= to match your system, if you want to run this directly instead of having it called by the udev eject script
# To find the right value, insert the UltraBay optical drive and run:
# udevadm info --query=path --name=/dev/sr0 | perl -pe 's!/block/...$!!'
if [ "$DEVPATH" = "" ]
then
DEVPATH="/devices/pci0000:00/0000:00:1f.2/host1/target1:0:0/1:0:0:0"
fi

shopt -s nullglob
export DISPLAY=:0.0 # required for notify-send

DISP0_USER=`lastlog | grep " :0" | awk '{ print $1 }'` # the space before the :0 is needed to exclude ipv6 adresses
DISP0_USER_HOME=`getent passwd ${DISP0_USER} | cut -d':' -f6`
export XAUTHORITY=${DISP0_USER_HOME}/.Xauthority # also required for notify-send

ULTRABAY_SYSDIR=/sys$DEVPATH

# Find generic dock interface for UltraBay
dock=$( /bin/grep -l ata_bay /sys/devices/platform/dock.?/type )
dock=${dock%%/type}
if [ -n "$dock" -a -d "$dock" ]; then
logger ultrabay_eject starting eject of $dock
else
logger ultrabay_eject cannot locate bay dock device
notify-send -u critical -t 100000 "ThinkPad Ultrabay eject failed" "Cannot locate bay dock device"
fi

# Umount the filesystem(s) backed by the given major:minor device(s)
unmount_rdev() { perl - "$@" <<'EOPERL' # let's do it in Perl
for $major_minor (@ARGV) {
$major_minor =~ m/^(\d+):(\d+)$/ or die;
push(@tgt_rdevs, ($1<<8)|$2);
}
# Sort by reverse length of mount point, to unmount sub-directories first
open MOUNTS,"</proc/mounts" or die "$!";
@mounts=sort { length($b->[1]) <=> length($a->[1]) } map { [ split ] } <MOUNTS>;
close MOUNTS;
foreach $m (@mounts) {
($dev,$dir)=@$m;
next unless -b $dev; $rdev=(stat($dev))[6];
next unless grep($_==$rdev, @tgt_rdevs);
system("umount","-v","$dir")==0 or $bad=1;
if ($bad == 1) {
system("logger","ultrabay_eject","ERROR unmounting",$dev,$dir);
system("notify-send -u critical -t 100000 \"Error unmounting $dir\" \"Unmounting of $dir on $dev failed!\"");
} else {
system("logger","ultrabay_eject","unmounted",$dev,$dir);
system("notify-send -u normal -t 5000 \"Unmounted $dir\"");
};
}
exit 1 if $bad;
EOPERL
}

# Get the UltraBay's /dev/foo block device node
ultrabay_dev_node() {
UDEV_PATH="`readlink -e "$ULTRABAY_SYSDIR/block/"*`" || return 1
UDEV_NAME="`udevadm info --query=name --path=$UDEV_PATH`" || return 1
echo /dev/$UDEV_NAME
}

if [ $( cat $dock/docked ) == 0 ]; then
logger ultrabay_eject dock reports empty
else
if [ -d $ULTRABAY_SYSDIR ]; then
logger ultrabay_eject dock occupied, shutting down storage device $DEVPATH
sync
# Unmount filesystems backed by this device
## This seems to be very inelegant and prone to failure
unmount_rdev `cat $ULTRABAY_SYSDIR/block/*/dev \
$ULTRABAY_SYSDIR/block/*/*/dev` \
|| {
logger ultrabay_eject umounting failed
echo 2 > /proc/acpi/ibm/beep # triple error tone
notify-send -u critical -t 100000 "ThinkPad Ultrabay eject failed" "Please do not pull the device, doing so could cause file corruption and possibly hang the system. Unmounting of the filesystem on the ThinkPad Ultrabay device failed. Please put the eject leaver back in place, and try to unmount the filesystem manually. If this succeeds you can try the eject again"
exit 1;
}
sync
# Nicely power off the device
DEVNODE=`ultrabay_dev_node` && hdparm -Y $DEVNODE
# Let HAL+KDE notice the unmount and let the disk spin down
sleep 0.5
# Unregister this SCSI device:
sync
echo 1 > $ULTRABAY_SYSDIR/delete
else
logger ultrabay_eject bay occupied but incorrect device path $DEVPATH
notify-send -u critical -t 100000 "ThinkPad Ultrabay eject failed" "Bay occupied but incorrect device path"
echo 2 > /proc/acpi/ibm/beep # triple error tone
exit 1
fi
fi

# We need sleep here so someone can disconnect the bay and the drive
sleep 1

# Turn off power to the UltraBay
logger ultrabay_eject undocking $dock
echo 1 > $dock/undock

# Tell the user we're OK
logger ultrabay_eject done
echo 12 > /proc/acpi/ibm/beep
notify-send -u normal -t 10000 "Safe to remove device" "The ThinkPad Ultrabay device can now safely be removed"

</pre>

*unified diff
<pre>
--- ultrabay_eject.orig 2010-01-07 22:51:40.000000000 +0100
+++ ultrabay_eject 2010-01-07 22:54:55.000000000 +0100
@@ -10,6 +10,11 @@

shopt -s nullglob
export DISPLAY=:0.0 # required for notify-send
+
+DISP0_USER=`lastlog | grep " :0" | awk '{ print $1 }'` # the space before the :0 is needed to exclude ipv6 adresses
+DISP0_USER_HOME=`getent passwd ${DISP0_USER} | cut -d':' -f6`
+export XAUTHORITY=${DISP0_USER_HOME}/.Xauthority # also required for notify-send
+
ULTRABAY_SYSDIR=/sys$DEVPATH

# Find generic dock interface for UltraBay
</pre>

i hope this is useful to other users as well --[[User:Roo|Roo]] 22:19, 7 January 2010 (UTC)

Talk:How to hotswap Ultrabay devices

2010-01-07T22:19:52Z

Roo: /* get notify-send working */ new section

=Recent Ubuntu versions=
I think, it must be mentioned that hotswapping Ultrabay devices using recent distros
is by far not that hard as before. I'm using Ubuntu 9.04 on Z61m and in my case hotswapping
Ultrabay DVD-RW works out-of-the-box without any scripts or whatsoever. The article
however suggests that one always needs some ejecting scripts which might confuse certain
users. So it would be nice to add something like: "If you are using Ubuntu *.** everything should
work out-of-the-box"

--[[User:Bombenbach|Bombenbach]] 12:01, 9 August 2009 (UTC)

Really? Did you try to swap out a Ultrabay device with mounted filesystem? Good luck!
The udev handler and eject script are there for a reason. By default no action is taken when you pull out a device, which can cause real problems if not handled properly.

--[[User:Tonko|Tonko]] 09:31, 10 August 2009 (UTC)

Well, actually I couldn't imagine that someone would like to pull out an Ultrabay device with mounted file system.
As far a usb flash drives are concerned, you won't do that either, right? My point was, that if the file system is '''properly unmounted''', I can simply pull my Ultrabay DVD-RW out without any freezes or crashes. And when I put it back again, the drive is automatically recognized by Ubuntu so that I can use it. I don't have an Ultrabay HDD, but I assume that if it works with DVD-RW it also should work with HDD. Correct me if I'm wrong. If the sole purpose of eject script is hotswapping Ultrabay devices '''with mounted filesystem''' then I still think that it would be nice to point it out in the article.

--[[User:Bombenbach|Bombenbach]] 07:52, 11 August 2009 (UTC)

By default on most modern distributions based on a recent kernel with libata, the libata driver gets to cleanup the mess after the fact, if you pull out an ultrabay device without first
* unmounting the filesystem
* powering down the device
You may be lucky, or you might end up with a hung system, corrupted filesystem, etc. Your choice.

There is work going on upstream to resolve this with DeviceKit-disks, but that depends on a patch to the Linux kernel, which has not made it in yet, since right now there is no correlation between the udev event and the actual Bay device, and since you can have multiple Bay devices (in fact your ThinkPad likely has 3) this correlation is needed, otherwise DeviceKit-disks would need to know about every single Laptop out there and the mapping between the Bay numbering and the actual devices (something the kernel can easily just provide instead).

Here is a Feature request against DeviceKit-disks that provides some status information
http://bugs.freedesktop.org/show_bug.cgi?id=23110

--[[User:Tonko|Tonko]] 09:07, 11 August 2009 (UTC)

=HAL script=

If the script works, your lshal output should contain something similar to this. In this case the Ultrabay device was a second HDD (/dev/sdb).

Note that in the example, storage.hotpluggable = true while before it was false, so the script worked.
<pre>
udi = '/org/freedesktop/Hal/devices/storage_serial_SATA_HTS726060M9AT00_MRH453M4H11ARB'
block.device = '/dev/sdb' (string)
block.is_volume = false (bool)
block.major = 8 (0x8) (int)
block.minor = 16 (0x10) (int)
block.storage_device = '/org/freedesktop/Hal/devices/storage_serial_SATA_HTS726060M9AT00_MRH453M4H11ARB' (string)
info.capabilities = {'storage', 'block'} (string list)
info.category = 'storage' (string)
info.parent = '/org/freedesktop/Hal/devices/pci_8086_24ca_scsi_host_0_scsi_device_lun0' (string)
info.product = 'HTS726060M9AT00' (string)
info.udi = '/org/freedesktop/Hal/devices/storage_serial_SATA_HTS726060M9AT00_MRH453M4H11ARB' (string)
info.vendor = 'ATA' (string)
linux.hotplug_type = 3 (0x3) (int)
linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1f.1/host1/target1:0:0/1:0:0:0/block/sdb' (string)
storage.automount_enabled_hint = true (bool)
storage.bus = 'pci' (string)
storage.drive_type = 'disk' (string)
storage.firmware_version = 'MH4O' (string)
storage.hotpluggable = true (bool)
storage.lun = 0 (0x0) (int)
storage.media_check_enabled = false (bool)
storage.model = 'HTS726060M9AT00' (string)
storage.no_partitions_hint = false (bool)
storage.originating_device = '/org/freedesktop/Hal/devices/computer' (string)
storage.partitioning_scheme = 'mbr' (string)
storage.removable = false (bool)
storage.removable.media_available = true (bool)
storage.removable.media_size = 60011642880 (0xdf8f90000) (uint64)
storage.requires_eject = false (bool)
storage.serial = 'SATA_HTS726060M9AT00_MRH453M4H11ARB' (string)
storage.size = 60011642880 (0xdf8f90000) (uint64)
storage.vendor = 'ATA' (string)
</pre>

{| border=1
|+ Known South Bridge PCI IDs
! ID !! ThinkPad model !! South Bridge chip (for Ultrabay) !! parent device (host_0, lun0 = 2nd ATA controller, master device)
|-
| 8086_7111 || A20m, A20p, A21e, A21m, A21p, A22e, A22m, A22p, T20, T21, T22, X20, X21 || Intel 82371AB/EB/MB PIIX4 IDE || /org/freedesktop/Hal/devices/pci_8086_7111_scsi_host_0_scsi_device_lun0
|-
| 8086_248a || T23, T30, X22, X23, X24, X30|| Intel 82801CAM IDE U100 (rev 2) || /org/freedesktop/Hal/devices/pci_8086_248a_scsi_host_0_scsi_device_lun0
|-
| 8086_248a || A30, A30p, A31, A31p|| Intel 82801CAM IDE U100 (rev 2) || /org/freedesktop/Hal/devices/pci_8086_248a_scsi_host_scsi_device_lun0_0<br>/org/freedesktop/Hal/devices/pci_8086_248a_scsi_host_0_scsi_device_lun0
|-
| 8086_24ca || R50, R51, T40, T40p, T41, T41p, T42, T42p, X31, X32, X40 || Intel 82801DBM (ICH4-M) || /org/freedesktop/Hal/devices/pci_8086_24ca_scsi_host_0_scsi_device_lun0
|-
| 8086_2653 || R52, T43, T43p, X41, Z60m, Z60t || Intel 82801FBM (ICH6-M) || /org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0
|-
| 8086_27c4 || R60, X60 || Intel 82801GBM (ICH7 Family) || /org/freedesktop/Hal/devices/pci_8086_27c4_scsi_host_scsi_device_lun0
|-
| 8086_27df || T60, T60p, Z61m, Z61t, Z61p || Intel 82801GBM/GHM (ICH7 Family) || /org/freedesktop/Hal/devices/pci_8086_27df_scsi_host_scsi_device_lun0
|-
| 8086_2850 || R61, T61, T61p, X300 || Intel 82801H (ICH8 Family) || /org/freedesktop/Hal/devices/pci_8086_2850_scsi_host_scsi_device_lun0
|-
| 8086_2929 || R400, R500, T400, T500, W500, W700, X200, X301 || Intel 82801I ICH9 Family || /org/freedesktop/Hal/devices/pci_8086_2929_scsi_host_0_scsi_device_lun0
|}
==lshal output==
Please place your lshal output here if you had problems

lshal of my A31: [http://nopaste.org/p/a4p6x9tSob http://nopaste.org/p/a4p6x9tSob]

Thanks! If I understand the output correctly you have one Toshiba Combo DVD-ROM/CD-RW R2002 in one ultrabay connected as slave to the primary IDE controller, and one Toshiba DVD-ROM C2512 in the second ultrabay connected as master to the secondary IDE controller. Can you confirm? I have added it to the table.

I have a Thinkpad T43 and I found out from my lshal output that I had to use parent device:
pci_8086_2653_scsi_host_0_scsi_device_lun0 instead of
pci_8086_2653_scsi_host_scsi_device_lun0 (notice the added 0).
This is the ultrabay, however, the internal disk still use the "original" parent device (the one without the 0).
I think this information should be added to the table.
Specs:
Thinkpad T43 (machine type 2668),
Mandriva One 2009.1,
haldaemon 0.5.12

Thanks, it is possible that you have AHCI mode disabled in the BIOS for your HDD?
--[[User:Tonko|Tonko]] 11:00, 31 July 2009 (UTC)

= bash script for hotswapping UltraBay =

Here is my script for hotswapping ultrabay, is more complex, supports swap partition on drive in ultrabay, check holders (useful, when you are using luks) and more :)

{{HELP|Please test on difrent models}}

ultrabay.sh
<pre>
#!/bin/bash
SCSI_DEVICE=""
FORCE_SLEEP="1"
QUIET="0"
SYSLOG="0"
BEEP="0"

Message()
{
MESSAGE="${0/*\//}: $*"
if [ "$QUIET" = "0" ]; then
echo "$MESSAGE"
fi
if [ "$SYSLOG" != "0" ]; then
/usr/bin/logger "$MESSAGE"
fi
true
}

Exit()
{
case "$1" in
"fail")
[ $BEEP != "0" ] && echo 2 > /proc/acpi/ibm/beep
exit 1
;;
"success")
[ $BEEP != "0" ] && echo 12 > /proc/acpi/ibm/beep
exit 0
;;
esac
}

Usage()
{
echo "usage: ${0/*\/} [options]"
echo "options:"
echo " -d <path> SCSI device (required)"
echo " -s Ignore fail when putting drive to sleep"
echo " -q No messages"
echo " -l Use syslog for messages (-q has no effect)"
echo " -b Use beep for notification (-q has no effect)"
exit 1
}

Block2Device()
{
/bin/readlink -e "/dev/block/$1"
}

IsSwap()
{
/sbin/swapon -s | grep -q -e "^$1\b"
}

IsMounted()
{
mount | grep -q -e "^$1\b"
}

HasHolders()
{
[ "$(ls "$1/holders")" ]
}

IsBusy()
{
DEVICE=$(Block2Device $(cat "$1/dev"))
if IsSwap "$DEVICE" || IsMounted "$DEVICE" || HasHolders "$1"; then
Message "device '$DEVICE' is busy"
false
else
true
fi
}

SleepDrive()
{
BLOCK=$(cat $SCSI_DEVICE/block/*/dev 2> /dev/null)
DEVICE=$(Block2Device "$BLOCK")
if ! /sbin/hdparm -Y "$DEVICE" &> /dev/null; then
Message "cannot put drive to sleep"
if [ $FORCE_SLEEP = "0" ]; then
true
else
false
fi
fi
}

DeleteScsiDevice()
{
if ! { echo 1 > $SCSI_DEVICE/delete; } &> /dev/null; then
Message "cannot delete device"
false
fi
}

GetDock()
{
grep "$1" /sys/devices/platform/dock.*/type | sed -e s%/type:.*%%
}

IsDocked()
{
[ $(cat $(GetDock "$1")/docked) -ne 0 ]
}

Undock()
{
{ echo 0 > $(GetDock "$1")/undock; } &> /dev/null
if IsDocked "$1"; then
Message "cannot undock UltraBay"
false
else
Message "UltraBay undocked"
true
fi

}

while getopts "d:qlsb" OPTION; do
case $OPTION in
d)
SCSI_DEVICE="$OPTARG"
;;
s)
FORCE_SLEEP="0"
;;
q)
QUIET="1"
;;
l)
SYSLOG="1"
;;
b)
BEEP="1"
;;
?)
Usage
;;
esac
done

if [ -d "$SCSI_DEVICE" ] && IsDocked "ata_bay"; then
sync
for DEV_DIR in $(ls $SCSI_DEVICE/block/*/*/dev $SCSI_DEVICE/block/*/dev | sed -e s/dev$// 2> /dev/null); do
IsBusy "$DEV_DIR" || Exit "fail"
done
sync
SleepDrive || Exit "fail"
DeleteScsiDevice || Exit "fail"
sleep 4
fi

if [ ! -d $SCSI_DEVICE ] && $(IsDocked "ata_bay"); then
if Undock "ata_bay"; then
Exit "success"
else
Exit "fail"
fi
fi

Message "UltraBay is already undocked"
Exit "success"
</pre>

Supported models: {{R400}} - linux-2.6.29
==comments==
Interesting, especially the support for swap partitions. but I have two comments, first your calling your script hotswap.sh and then having udev call ultrabay.sh?

Then your hard coding the location of the Ultrabay device. This is not guaranteed to be correct, although it will be in most cases. In particular the A and W-series machines. A-series had support for more then one Ultrabay device, while W-series has support for more then one internal HDD in addition to the Ultrabay device, so the Ultrabay location will shift. That is why the Ultrabay Eject script on the main page gets the eject device information from udev.

==comments==
Hi, thanks, I fix name of script :)
Udev calling ultrabay.sh with option -d, so it remove correct device, if you want remove device manualy, is default device useful. But option may be required...

==more comments ;)==
You might also have a look at the script on the main page, it has a few extra abilities, such as logging to syslog, beeping and putting up popups on the desktop.

Logging to syslog is simple, just call 'logger' with what you want to log. quite should have no effect on this.

For beeps, similar to what windows does you can echo different values to /proc/acpi/ibm/beep, but it only works if sound is not muted. Unfortunately doing so does seem to generate some annoying messages in syslog.

Lastly you can use notify-send to put up messages on the desktop, but before you can do so you have to do an export DISPLADISPLAY=0:0 /usr/bin/knotify4 --passive-popup : Adresář nebo soubor neexistujeY=:0.0

==Syslog and beep==
OK, scrip now support syslog and beeping :).

Still missing notify-send ;)

I am also thinking that it would be useful in the case of a busy filesystem to tell the user to run something like fuser -mv /dev/sr0<br>
Or perhaps we should run it ourselves automatically and just tell the user what is the cause of the busy filesystem.<br>
--[[User:Tonko|Tonko]] 21:21, 8 June 2009 (UTC)

== get notify-send working ==

Hi there,

I've modified your ultrabay_eject script so that the notify-send is working for the user which is logged onto screen :0
for an unified diff see below, here is the whole modified script

* whole script
<pre>
#!/bin/bash

# Change the following DEVPATH= to match your system, if you want to run this directly instead of having it called by the udev eject script
# To find the right value, insert the UltraBay optical drive and run:
# udevadm info --query=path --name=/dev/sr0 | perl -pe 's!/block/...$!!'
if [ "$DEVPATH" = "" ]
then
DEVPATH="/devices/pci0000:00/0000:00:1f.2/host1/target1:0:0/1:0:0:0"
fi

shopt -s nullglob
export DISPLAY=:0.0 # required for notify-send

DISP0_USER=`w | grep ":0 " | awk '{ print $1 }'`
DISP0_USER_HOME=`getent passwd ${DISP0_USER} | cut -d':' -f6`
export XAUTHORITY=${DISP0_USER_HOME}/.Xauthority # also required for notify-send

ULTRABAY_SYSDIR=/sys$DEVPATH

# Find generic dock interface for UltraBay
dock=$( /bin/grep -l ata_bay /sys/devices/platform/dock.?/type )
dock=${dock%%/type}
if [ -n "$dock" -a -d "$dock" ]; then
logger ultrabay_eject starting eject of $dock
else
logger ultrabay_eject cannot locate bay dock device
notify-send -u critical -t 100000 "ThinkPad Ultrabay eject failed" "Cannot locate bay dock device"
fi

# Umount the filesystem(s) backed by the given major:minor device(s)
unmount_rdev() { perl - "$@" <<'EOPERL' # let's do it in Perl
for $major_minor (@ARGV) {
$major_minor =~ m/^(\d+):(\d+)$/ or die;
push(@tgt_rdevs, ($1<<8)|$2);
}
# Sort by reverse length of mount point, to unmount sub-directories first
open MOUNTS,"</proc/mounts" or die "$!";
@mounts=sort { length($b->[1]) <=> length($a->[1]) } map { [ split ] } <MOUNTS>;
close MOUNTS;
foreach $m (@mounts) {
($dev,$dir)=@$m;
next unless -b $dev; $rdev=(stat($dev))[6];
next unless grep($_==$rdev, @tgt_rdevs);
system("umount","-v","$dir")==0 or $bad=1;
if ($bad == 1) {
system("logger","ultrabay_eject","ERROR unmounting",$dev,$dir);
system("notify-send -u critical -t 100000 \"Error unmounting $dir\" \"Unmounting of $dir on $dev failed!\"");
} else {
system("logger","ultrabay_eject","unmounted",$dev,$dir);
system("notify-send -u normal -t 5000 \"Unmounted $dir\"");
};
}
exit 1 if $bad;
EOPERL
}

# Get the UltraBay's /dev/foo block device node
ultrabay_dev_node() {
UDEV_PATH="`readlink -e "$ULTRABAY_SYSDIR/block/"*`" || return 1
UDEV_NAME="`udevadm info --query=name --path=$UDEV_PATH`" || return 1
echo /dev/$UDEV_NAME
}

if [ $( cat $dock/docked ) == 0 ]; then
logger ultrabay_eject dock reports empty
else
if [ -d $ULTRABAY_SYSDIR ]; then
logger ultrabay_eject dock occupied, shutting down storage device $DEVPATH
sync
# Unmount filesystems backed by this device
## This seems to be very inelegant and prone to failure
unmount_rdev `cat $ULTRABAY_SYSDIR/block/*/dev \
$ULTRABAY_SYSDIR/block/*/*/dev` \
|| {
logger ultrabay_eject umounting failed
echo 2 > /proc/acpi/ibm/beep # triple error tone
notify-send -u critical -t 100000 "ThinkPad Ultrabay eject failed" "Please do not pull the device, doing so could cause file corruption and possibly hang the system. Unmounting of the filesystem on the ThinkPad Ultrabay device failed. Please put the eject leaver back in place, and try to unmount the filesystem manually. If this succeeds you can try the eject again"
exit 1;
}
sync
# Nicely power off the device
DEVNODE=`ultrabay_dev_node` && hdparm -Y $DEVNODE
# Let HAL+KDE notice the unmount and let the disk spin down
sleep 0.5
# Unregister this SCSI device:
sync
echo 1 > $ULTRABAY_SYSDIR/delete
else
logger ultrabay_eject bay occupied but incorrect device path $DEVPATH
notify-send -u critical -t 100000 "ThinkPad Ultrabay eject failed" "Bay occupied but incorrect device path"
echo 2 > /proc/acpi/ibm/beep # triple error tone
exit 1
fi
fi

# We need sleep here so someone can disconnect the bay and the drive
sleep 1

# Turn off power to the UltraBay
logger ultrabay_eject undocking $dock
echo 1 > $dock/undock

# Tell the user we're OK
logger ultrabay_eject done
echo 12 > /proc/acpi/ibm/beep
notify-send -u normal -t 10000 "Safe to remove device" "The ThinkPad Ultrabay device can now safely be removed"

</pre>

*unified diff
<pre>
--- ultrabay_eject.orig 2010-01-07 22:51:40.000000000 +0100
+++ ultrabay_eject 2010-01-07 22:54:55.000000000 +0100
@@ -10,6 +10,11 @@

shopt -s nullglob
export DISPLAY=:0.0 # required for notify-send
+
+DISP0_USER=`w | grep ":0 " | awk '{ print $1 }'`
+DISP0_USER_HOME=`getent passwd ${DISP0_USER} | cut -d':' -f6`
+export XAUTHORITY=${DISP0_USER_HOME}/.Xauthority # also required for notify-send
+
ULTRABAY_SYSDIR=/sys$DEVPATH

# Find generic dock interface for UltraBay
</pre>

i hope this is useful to other users as well --[[User:Roo|Roo]] 22:19, 7 January 2010 (UTC)

User:Roo

2010-01-07T22:19:39Z

Roo: â†Created page with 'Email roo -At- eserver.homelinux.org<br /> xmpp root -At- eserver.homelinux.org == Machine == Thinkpad T61p'

Email roo -At- eserver.homelinux.org<br />
xmpp root -At- eserver.homelinux.org

== Machine ==

[[:Category:T61p|Thinkpad T61p]]