LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook
Reload this Page Ubuntu: Thinkpad ultrabase won't allow disconnect
User Name
Password
Linux - Laptop and Netbook Having a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).

Notices

Reply
 
LinkBack Search this Thread
Old 08-22-2006, 06:16 AM   #1
PlantPerson
Member
 
Registered: Jun 2004
Distribution: Debian
Posts: 33

Rep: Reputation: 15
Ubuntu: Thinkpad ultrabase won't allow disconnect

I installed Ubuntu Dapper on my new IBM/Lenovo X60 last night. It works fairly well. However, the Thinkpad docking base is not allowing me to disconnect the computer if Ubuntu is running. The base has this button which you're supposed to push before disconnecting. Under windows, this button sends some kind of signal to the computer, which then responds and tells the base it's ok to disconnect. You then pull a lever and the computer comes free. But under Ubuntu, after the button is pressed, the "ok" light on the base stays red, and if I pull the release lever, the computer starts beeping shrill and loud until I reconnect it. Any idea how to fix this?
 
Old 10-14-2009, 11:18 AM   #2
SaintDanBert
Member
 
Registered: Jan 2009
Location: Austin, TX
Distribution: Mint-11, v11.04 Ubuntu & Kubuntu
Posts: 933
Blog Entries: 3

Rep: Reputation: 51
Ultrabase trouble STILL with Ubuntu Hardy (v8.04.3 LTS)
The original question was for Dapper on an X60. I renew this question for Hardy on X61-Tablet.

I have an EmperorLinux Raven Tablet (Lenovo Thinkpad X61 Tablet) with the Ultrabase dock or port-replicator or side-car or ...

Ubuntu Hardy won't ... Windows XP Pro Tablet Edition works ...

The DVD drive is in the ultrabase. With windows, I can
  • "stop" the DVD and
  • remove the drive carrier from the bay.
  • Insert a different DVD drive or HDD carrier.
  • Windows notices the changes and makes the new device available and ready for use.
  • stop and remove this other drive
  • revert to the DVD
  • repeat forever

With Ubuntu, shutdown and reboot are required.
 
Old 10-14-2009, 12:55 PM   #3
Wim Sturkenboom
Senior Member
 
Registered: Jan 2005
Location: Roodepoort, South Africa
Distribution: Slackware 10.1/10.2/12, Ubuntu 10.04, Crunchbang Statler
Posts: 3,325

Rep: Reputation: 168Reputation: 168
You don't state which ultradock. Some research showed e.g.
X3: http://www.thinkwiki.org/wiki/UltraB...#Linux_support
X6: http://www.thinkwiki.org/wiki/UltraB...older_style.29 or http://www.thinkwiki.org/wiki/UltraB...newer_style.29
 
Old 10-14-2009, 04:02 PM   #4
SaintDanBert
Member
 
Registered: Jan 2009
Location: Austin, TX
Distribution: Mint-11, v11.04 Ubuntu & Kubuntu
Posts: 933
Blog Entries: 3

Rep: Reputation: 51
Quote:
Originally Posted by Wim Sturkenboom View Post
Mine is the X6 Ultrabase.

ANALYSIS:
Part of the problem revolves around dynamic device creation and activation. (Is that udev? ) The DVD does not really exist until you load media. When you unload media, the device "goes away" again. This means there is no DVD device to "stop."

In a similar way, the ultrabay HDD is not really USB or eSata.
(I think it is EIDE doing pretend USB.) Thus it does not play
the usb/firewire/eSATA unmount and disconnect game nicely.

Again I repeat: WinXP works ... Ubuntu Hardy fails ...

Thanks for these links. I'll check them out and report back.

Cheers,
~~~ 0;-Dan
 
Old 10-14-2009, 04:12 PM   #5
SaintDanBert
Member
 
Registered: Jan 2009
Location: Austin, TX
Distribution: Mint-11, v11.04 Ubuntu & Kubuntu
Posts: 933
Blog Entries: 3

Rep: Reputation: 51
Quote:
Originally Posted by Wim Sturkenboom View Post
QUESTION: How does one know if they have the "older style" or "newer style" of X6 Ultrabase?

QUESTION: Are there grep strings for lspci or lshw ?

Cheers,
~~~ 0;-Dan
 
Old 10-14-2009, 04:48 PM   #6
SaintDanBert
Member
 
Registered: Jan 2009
Location: Austin, TX
Distribution: Mint-11, v11.04 Ubuntu & Kubuntu
Posts: 933
Blog Entries: 3

Rep: Reputation: 51
Quote:
Originally Posted by SaintDanBert View Post
Mine is the X6 Ultrabase.
...
I'll check them out and report back.
...
I have two ultrabay-slim modules: one DVD-RW; one HDD.
WinXP/Pro works ... Ubuntu fails.
  • "stop" the DVD
  • remove DVD module
  • insert HDD module
  • use the HDD (backup and archives)
  • "stop" the HDD
  • remove HDD module
  • insert DVD module
  • use the DVD module

Looking here cuz it is the newest:
Code:
http://www.thinkwiki.org/wiki/UltraBase_X6#UltraBase_X6_under_Linux_.28newer_style.29
Both thinkpad_acpi module and acpid daemon process are present.

I do not find the docker command
... I found a package that identifies as "WindowMaker dock app"
and panel docking. I don't see how this applies. Please clarify.
... the openSUSE DockUtils project page announces that it is obsolete.

I do not find a /usr/lib/docutils folder.
The only "dock" anything is part of /usr/lib/hal/scripts
(unless you are interested in GUI desktop widget docking)

I googled (verb, transitive, meaning "to search") and found
Code:
http://southofdallas.com/?p=130
This looks like it might be useful, but I have not worked the text yet.

Cheers,
~~~ 0;-Dan
 
Old 10-14-2009, 04:56 PM   #7
SaintDanBert
Member
 
Registered: Jan 2009
Location: Austin, TX
Distribution: Mint-11, v11.04 Ubuntu & Kubuntu
Posts: 933
Blog Entries: 3

Rep: Reputation: 51
Quote:
Originally Posted by Wim Sturkenboom View Post
I went here:
Code:
http://www.thinkwiki.org/wiki/UltraBase_X6#UltraBase_X6_under_Linux_.28older_style.29
This page offers the same information about the same parts and packages as the "newer_style" page so it didn't offer much help here, either.

~~~ 0;-Dan
 
Old 10-14-2009, 05:05 PM   #8
SaintDanBert
Member
 
Registered: Jan 2009
Location: Austin, TX
Distribution: Mint-11, v11.04 Ubuntu & Kubuntu
Posts: 933
Blog Entries: 3

Rep: Reputation: 51
Quote:
Originally Posted by Wim Sturkenboom View Post
I went here:
Code:
http://www.thinkwiki.org/wiki/UltraBase_X3#Linux_support
It included these links:
Code:
http://www.thinkwiki.org/wiki/How_to_hotswap_the_UltraBase
... links to ...
http://jmtd.net/computing/hardware/x40/dock/
=== AND ===
http://www.thinkwiki.org/wiki/How_to_hotswap_Ultrabay_devices
Both of these pages do some pretty arcane things like echo numbers into /proc entries and various manipulations of /devices. With all of the scripts and bits and such, I'll try these soon and report.

Cheers,
~~~ 0;-Dan
 
Old 10-14-2009, 06:27 PM   #9
SaintDanBert
Member
 
Registered: Jan 2009
Location: Austin, TX
Distribution: Mint-11, v11.04 Ubuntu & Kubuntu
Posts: 933
Blog Entries: 3

Rep: Reputation: 51
lots of errors ... but some progress
As I understand things, The ultrabay X6 drives are PATA hardware with "rigging" to play eSATA. My ultrabay had the DVD-RW installed.
I get the following:
Code:
user@host$ sudo lshw
    ...
    *-ide
        description: IDE Channel 0
        physical id: 0
        bus info: ide@0
        logical name: ide0
        clock: 33MHz
        *-cdrom
           description: DVD-RAM writer
           product: MATSHITADVD-RAM UJ-852
           physical id: 0
           bus info: ide@0.0
           logical name: /dev/hda
           version: RB02
           serial: HC43 439385
           capabilities: packet atapi cdrom removable nonmagnetic 
               dma lba iordy audio cd-r cd-rw dvd dvd-r dvd-ram
               configuration: mode=udma2 status=nodisc
    ...
I pushed the hard button to request undock of the entire ultrabay.
Blink ... blink ... click ... whirr ... change of lights ...
The hardware indicated it was okay to mechanically remove the ultrabay. Then the following appeared in /var/log/messages
Code:
Oct 14 17:50:17 mumbles kernel: ACPI: undocking
Oct 14 17:50:17 mumbles kernel: usb 5-4: USB disconnect, address 4
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:50:18 mumbles kernel: hda: status error: status=0x00 { }
Oct 14 17:50:18 mumbles kernel: ide: failed opcode was: unknown
...
... the above sequence repeated quite a few times ...
...
I removed the ultrabay entirely without incident.
Then the following appeared in /var/log/messages
Code:
Oct 14 17:52:12 mumbles kernel: hda: status error: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error }
Oct 14 17:52:12 mumbles kernel: hda: status error: error=0x7f { IllegalLengthIndication EndOfMedia AbortedCommand MediaChangeRequested LastFailedSense=0x07 }
Oct 14 17:52:12 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:52:12 mumbles kernel: hda: status error: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error }Oct 14 17:52:32 mumbles kernel: hda: status error: error=0x7f { IllegalLengthIndication EndOfMedia AbortedCommand MediaChangeRequested LastFailedSense=0x07 }
...
... the above sequence repeated quite a few times ...
...
I re-connected the ultrabay.
Then the following appeared in /var/log/messages
Code:
Oct 14 17:52:32 mumbles kernel: ide: failed opcode was: unknown
Oct 14 17:52:32 mumbles kernel: ACPI: docking
Oct 14 17:52:32 mumbles kernel: usb 5-4: new high speed USB device using ehci_hcd and address 16
Oct 14 17:52:32 mumbles kernel: Device driver usbdev5.16_ep00 lacks bus and class support for being resumed.
Oct 14 17:52:32 mumbles kernel: usb 5-4: configuration #1 chosen from 1 choice
Oct 14 17:52:32 mumbles kernel: hub 5-4:1.0: USB hub found
Oct 14 17:52:32 mumbles kernel: hub 5-4:1.0: 4 ports detected
Oct 14 17:52:32 mumbles kernel: Device driver usbdev5.16_ep81 lacks bus and class support for being resumed.
All seemed to go well but when I loaded a commercial audio CD, I locked the box forcing big-red-switch(see note 1) command.

REMEMBER:

my kernel is: v2.6.22.1 (with EmperorLinux patches)
my distro is: Ubuntu Hardy Heron (v8.04.3 LTS) complete patches
my hardware is: EmperorLinux Raven Tablet (Lenovo Thinkpad X61 Tablet)
Cheers,
~~~ 0;-Dan

_______________
1. For you young pups, the big red switch was the power switch on the side of the original IBM PC-1 and XT computers. When things locked up, you cycled the power forcing a reset and restart. 8d:-}
Last edited by SaintDanBert; 10-14-2009 at 07:06 PM. Reason: correction
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Ubuntu on a Thinkpad 600 zapaces Linux - Newbie 2 08-23-2009 01:21 PM
Ubuntu runs slowly on celeron-m IBM thinkpad Th3James Linux - General 2 05-07-2007 08:36 PM
LXer: Ubuntu Linux On Thinkpad T43p: Wow! LXer Syndicated Linux News 0 08-10-2006 07:21 PM
Wireless Card in Thinkpad 600 w/ Ubuntu bear vs shawn Linux - Laptop and Netbook 2 04-28-2006 03:18 AM
Installing UBUNTU 5.04 on ThinkPad R40 nandipinto Linux - Laptop and Netbook 1 09-28-2005 09:21 AM


All times are GMT -5. The time now is 08:11 AM.

Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
 
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: @linuxquestions
Open Source Consulting | Domain Registration