[ltp] /proc/acpi/ibm/bay gone with ThinkPad ACPI Extras v0.19-20080107/2.6.24

[Marc MERLIN]

On Thu, Jan 31, 2008 at 06:49:48PM -0200, Henrique de Moraes Holschuh wrote:
> On Thu, 31 Jan 2008, Marc MERLIN wrote:
> > gandalf:~# lsmod | grep thinkpad
> > gandalf:~# lsmod | grep bay
> > bay                     7040  0 
> > dock                   11412  1 bay
> > gandalf:~# uname -r
> > 2.6.24-slab-tpacpi0.19-p4core2smp-preempt-1khz-noticks-marc8
> > 
> > After that, indeed, releasing the eject hatch (without ejecting) doesn't generate
> > any acpi event, or anything I can see in either /var/log/syslog /var/log/acpid
> 
> I think you get an event through udev when using the ACPI generic bay and
> dock.  udevmonitor will tell you more (works like acpi_listen).

Indeed. This is what I currently get with a battery in the bay:
UDEV  [1201818152.927552] change   /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0C09:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
UEVENT[1201818152.934954] remove   /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0C09:00/PNP0C0A:01/power_supply/BAT1 (power_supply)
UDEV  [1201818152.939496] remove   /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0C09:00/PNP0C0A:01/power_supply/BAT1 (power_supply)

> > Shouldn't thinkpad_acpi output some message at load time that says
> > whether it saw the bay or if it was busy?
> 
> It does, when in debug mode.  I am not sure I should make it more verbose
> without the debug switch, because it would be really noisy to log whether
> each subdriver loaded sucessfully or not by default...
 
Yeah, I found debug mode in the source later.
I recommend you at least log the bay error even if not in debug mode

Hopefully what I sent you seperately will help.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/