[ibm-acpi-devel] FC6 / IBM x31 / ACPI Fan control Help
I've tried for months to get this to work: control my fan speed in Fedore Core 6 (kernel 2.6.20-1.2948) on my thinkpad x31. The first clue I can think of to help, is that I don't have the /proc/acpi/ibm/fan and /proc/acpi/ibm/ecdump files. Where do I get them? I feel this the heart of the problem. I would be very very grateful if I could help on this. Thanks, Robert - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
Re: [ibm-acpi-devel] Caching the results of acpi_get_handle() in a driver: is it valid?
Handles from a DSDT are in fact permanent. Once a SSDT is unloaded, however, those handles are invalid. We are considering making these handles "real" handles instead of simply pointers to catch the use of an invalid handle. > -Original Message- > From: [EMAIL PROTECTED] [mailto:linux-acpi- > [EMAIL PROTECTED] On Behalf Of Henrique de Moraes Holschuh > Sent: Wednesday, February 07, 2007 11:44 AM > To: [email protected] > Cc: [email protected] > Subject: Caching the results of acpi_get_handle() in a driver: is it > valid? > > The code I inherited in ibm-acpi does heavy caching of acpi_get_handle() > results. It stores the results of acpi_get_handle() for a number of nodes > at module init, and uses the stored results during its lifetime. > > Is that a valid use of the handles returned by acpi_get_handle()? In > particular, what happens to handlers when a SSDT gets loaded or unloaded > at > runtime? Do handles that came from the DSDT change? What if the handler > was to a node in the SSDT being unloaded? What if the handler is > overriden > by a new loaded SSDT? > > While the vast majority of the handlers ibm-acpi caches are in the DSDT > and > very unlikely to change through a SSDT load, I'd still like to make sure > the > driver is doing the right thing... > > PS: not caching the results is always possible, but that will mean various > calls to acpi_get_handle() per second. > > -- > "One disk to rule them all, One disk to find them. One disk to bring > them all and in the darkness grind them. In the Land of Redmond > where the shadows lie." -- The Silicon Valley Tarot > Henrique Holschuh > - > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
[ibm-acpi-devel] Linux Bug Report As requested - unhandled HKEY event 0x6031
from /var/log/syslog Nov 9 00:06:26 rob-ThinkPad-P70 cinnamon-screensaver-dialog: pam_ecryptfs: >> seteuid error > > Nov 9 00:06:47 rob-ThinkPad-P70 kernel: [18773.898701] thinkpad_acpi: >> unknown possible thermal alarm or keyboard event received > > Nov 9 00:06:47 rob-ThinkPad-P70 kernel: [18773.898708] thinkpad_acpi: >> unhandled HKEY event 0x6031 > > Nov 9 00:06:47 rob-ThinkPad-P70 kernel: [18773.898712] thinkpad_acpi: >> please report the conditions when this event happened to >> [email protected] > > running RELEASE=18 > > CODENAME=sarah > > EDITION="Cinnamon 64-bit" > > DESCRIPTION="Linux Mint 18 Sarah" > > DESKTOP=Gnome > > TOOLKIT=GTK > > NEW_FEATURES_URL=http://www.linuxmint.com/rel_sarah_cinnamon_whatsnew.php > > RELEASE_NOTES_URL=http://www.linuxmint.com/rel_sarah_cinnamon.php > > USER_GUIDE_URL=help:linuxmint > > GRUB_TITLE=Linux Mint 18 Cinnamon 64-bit > > > This is on a Thinkpad P70 laptop; I left the laptop along for about 30mins and mint put it on standby and turned off the monitors. Upon logging in everything seemed fine. Within a few seconds or perhaps a minute, the monitors went black, but everything recovered, so I looked at the logs to see what happened, and is posted above. im new to linux, but if there is any other info you need, let me know. Hope this helps. Best Regards, Rob Lee -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
[ibm-acpi-devel] [Fwd: ThinkPad X40 brightness]
I did not see any reply to the previous message, or it appearing on the mailing list archive, so I hope it is not getting stuck in a spam filter. I also tested a ThinkPad T41 today with Radeon RV250, and it reports using brightness_mode=3 Other the that the behavior is identical to that of the X40, in that the brightness keys do not generate any events, but do work, and actual_brightness does change when using the keys. Original Message Subject:ThinkPad X40 brightness Date: Tue, 04 Aug 2009 14:39:05 +0200 From: Robert de Rooy To: [email protected] The latest kernel (2.6.31-rc5-git2) requests to send a report if brightness works on a ThinkPad X40 with Intel 855GM, it reports it is using brightness_mode=2 Not sure what needs to be tested, but the brightness keys work, but do not cause any HAL events by default (so no OSD). The brightness is reduced when switching to battery mode, and increased again when plugged into the mains power. Neither of these actions cause any messages in syslog, so this seems to be completely hardware managed. I checked /sys/devices/virtual/backlight/* and I can change the brightness by putting a different value into brightness. When pressing the brightness up/down buttons, the brightness file does not change, but actual_brightness does. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
[ibm-acpi-devel] ThinkPad X40 brightness
The latest kernel (2.6.31-rc5-git2) requests to send a report if brightness works on a ThinkPad X40 with Intel 855GM, it reports it is using brightness_mode=2 Not sure what needs to be tested, but the brightness keys work, but do not cause any HAL events by default (so no OSD). The brightness is reduced when switching to battery mode, and increased again when plugged into the mains power. Neither of these actions cause any messages in syslog, so this seems to be completely hardware managed. I checked /sys/devices/virtual/backlight/* and I can change the brightness by putting a different value into brightness. When pressing the brightness up/down buttons, the brightness file does not change, but actual_brightness does. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
[ibm-acpi-devel] T41 Volume/Brightness with 2.6.33-rc3-git1
Hi, Seeing that the new subsystem drivers have been merged, I tried the latest kernel on my T41 running F12. $ dmesg |grep -i thinkpad thinkpad_acpi: ThinkPad ACPI Extras v0.24 thinkpad_acpi: http://ibm-acpi.sf.net/ thinkpad_acpi: ThinkPad BIOS 1RETDRWW (3.23 ), EC 1RHT71WW-3.04 thinkpad_acpi: IBM ThinkPad T41 , model 2373TG5 thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked thinkpad_acpi: Console audio control enabled, mode: monitor (read only) input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input10 But I am not seeing anything regarding a new ALSA device, either in dmesg or in the Gnome sound applet. And when I run 'lshal --monitor' and press the volume or brightness keys I do not see any events either. The proc/sysfs values do change when the keys are pressed, and tpb reports the key presses. Am I doing something wrong? $ cat .config|grep THINKPAD CONFIG_THINKPAD_ACPI=m CONFIG_THINKPAD_ACPI_ALSA_SUPPORT=y # CONFIG_THINKPAD_ACPI_DEBUGFACILITIES is not set # CONFIG_THINKPAD_ACPI_DEBUG is not set # CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not set CONFIG_THINKPAD_ACPI_VIDEO=y CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
[ibm-acpi-devel] thinkpad_acpi alsa sub-driver with 2.6.33-rc3-git2
On 09/01/10 14:48, Henrique de Moraes Holschuh wrote: > On Thu, 07 Jan 2010, Robert de Rooy wrote: > >> thinkpad_acpi: Console audio control enabled, mode: monitor (read only) >> >> But I am not seeing anything regarding a new ALSA device, either in >> dmesg or in the Gnome sound applet. And when I run 'lshal --monitor' >> and press the volume or brightness keys I do not see any events >> either. >> > It will be in one of the last alsa card slots by default. Use > /proc/asound/* to locate it, or ask the ALSA lib about the installed > cards... > > You can use the index= parameter to tell it at which slot you want it to try > to install the card. index=3 would place it in the third slot, for example. > > Maybe a HAL .fdi file would also help gnome find it? I can't help you > there, but someone in the freedesktop.org or in the linux-thinkpad ML might. > > Thanks Henrique, Your right, I checked /proc/asound and indeed I have a ThinkPadEC directory. $ cat /proc/asound/cards 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4 Intel 82801DB-ICH4 with AD1981B at irq 11 1 [Modem ]: ICH-MODEM - Intel 82801DB-ICH4 Modem Intel 82801DB-ICH4 Modem at irq 11 29 [ThinkPadEC ]: ThinkPad EC - ThinkPad Console Audio Control ThinkPad Console Audio Control at EC reg 0x30, fw 1RHT71WW-3.04 When I run alsamixer, I can change to ThinkPadEC device and see the button presses change the volume and mute, so that all seems to work. But the question now is, how are you supposed to make use of this new volume/mute device under a modern distribution like Fedora 12? The gnome-volume-control-applet does not show any change when pressing the buttons, and indeed gnome-volume-control does not even show the device (or the modem for that matter) under the Hardware tab. Changing the alsa index from the default 29 to 3 does not change anything in this regard. Revent versions of gnome-volume-control use PulseAudio, so it is probably filtering the devices. But running 'pactl list' does not show any other devices either. I put some RedHat people on cc: that where involved with the volume-control makeover in F11 as I am hoping that Fedora 13 will have all of this working out of the box (assuming it gets the 2.6.33 kernel). When I have a bit of time, I might try it on my T60 also. $ gnome-volume-control --debug ** (gnome-volume-control:3474): DEBUG: Enabling debugging ** (gnome-volume-control:3474): DEBUG: Updating client: index=15 name='ConsoleKit Session /org/freedesktop/ConsoleKit/Session4' ** (gnome-volume-control:3474): DEBUG: Updating client: index=16 name='GNOME Volume Control Media Keys' ** (gnome-volume-control:3474): DEBUG: Updating client: index=21 name='XSMP Session on gnome-session as 1031493bc4bfda509212631966208194650029240029' ** (gnome-volume-control:3474): DEBUG: Updating client: index=22 name='GNOME Volume Control Applet' ** (gnome-volume-control:3474): DEBUG: Updating client: index=26 name='libcanberra' ** (gnome-volume-control:3474): DEBUG: Updating client: index=27 name='GNOME Volume Control Dialog' ** (gnome-volume-control:3474): DEBUG: Updating sink: index=0 name='alsa_output.pci-_00_1f.5.analog-stereo' description='Internal Audio Analog Stereo' map='front-left,front-right' ** (gnome-volume-control:3474): DEBUG: Updating source: index=0 name='alsa_output.pci-_00_1f.5.analog-stereo.monitor' description='Monitor of Internal Audio Analog Stereo' ** (gnome-volume-control:3474): DEBUG: Updating source: index=1 name='alsa_input.pci-_00_1f.5.analog-stereo' description='Internal Audio Analog Stereo' ** (gnome-volume-control:3474): DEBUG: Udpating card alsa_card.pci-_00_1f.5 (index: 0 driver: module-alsa-card.c): ** (gnome-volume-control:3474): DEBUG: Profile 'output:analog-stereo': 0 sources 1 sinks ** (gnome-volume-control:3474): DEBUG: Profile 'output:analog-stereo+input:analog-stereo': 1 sources 1 sinks (Current) ** (gnome-volume-control:3474): DEBUG: Profile 'input:analog-stereo': 1 sources 0 sinks ** (gnome-volume-control:3474): DEBUG: Profile 'off': 0 sources 0 sinks ** (gnome-volume-control:3474): DEBUG: Property: 'alsa.card' = '0' ** (gnome-volume-control:3474): DEBUG: Property: 'alsa.card_name' = 'Intel 82801DB-ICH4' ** (gnome-volume-control:3474): DEBUG: Property: 'alsa.long_card_name' = 'Intel 82801DB-ICH4 with AD1981B at irq 11' ** (gnome-volume-control:3474): DEBUG: Property: 'alsa.driver_name' = 'snd_intel8x0' ** (gnome-volume-control:3474): DEBUG: Property: 'device.bus_path' = 'pci-:00:1
[ibm-acpi-devel] T41 Brightness with 2.6.33-rc3-git2
On 09/01/10 14:48, Henrique de Moraes Holschuh wrote: > On Thu, 07 Jan 2010, Robert de Rooy wrote: > >> thinkpad_acpi: Console audio control enabled, mode: monitor (read only) >> >> But I am not seeing anything regarding a new ALSA device, either in >> dmesg or in the Gnome sound applet. And when I run 'lshal --monitor' >> and press the volume or brightness keys I do not see any events >> either. >> > It will be in one of the last alsa card slots by default. Use > /proc/asound/* to locate it, or ask the ALSA lib about the installed > cards... > > You can use the index= parameter to tell it at which slot you want it to try > to install the card. index=3 would place it in the third slot, for example. > > Maybe a HAL .fdi file would also help gnome find it? I can't help you > there, but someone in the freedesktop.org or in the linux-thinkpad ML might. > > I thought it best to separate the brightness from the volume discussion. As to the brightness issue, I still do not get any output when I press the brightness buttons in /dev/input/event10, while I do get output on things like Fn-Space. I enabled the thinkpad_acpi debug options, but that does not seem to make any difference either. On my T60 where the acpi video driver handles the backlight I do get OSD without needing tpb, but on the T41 where it is handled by thinkpad_acpi, I do not. thinkpad_acpi does report the correct status in sysfs, so this is just a reporting issue, but I thought this was supposed to be fixed with the latest update to thinkpad_acpi? -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
Re: [ibm-acpi-devel] thinkpad_acpi alsa sub-driver with 2.6.33-rc3-git2
On 11/01/10 17:44, Lennart Poettering wrote: > > Very nice! When will this be merged? This is already upstream in 2.6.33-rc3 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
Re: [ibm-acpi-devel] T41 Brightness with 2.6.33-rc3-git2
On 11/01/10 21:43, Henrique de Moraes Holschuh wrote: > On Mon, 11 Jan 2010, Robert de Rooy wrote: > >> As to the brightness issue, I still do not get any output when I press >> the brightness buttons in /dev/input/event10, while I do get output on >> things like Fn-Space. I enabled the thinkpad_acpi debug options, but >> that does not seem to make any difference either. >> > Brightness changes get exposed through backlight interface events, not > through input devices. Since this is a somewhat new feature of the > backlight interface, userspace seems not to have caught up to it yet. > > >> On my T60 where the acpi video driver handles the backlight I do get OSD >> without needing tpb, but on the T41 where it is handled by >> thinkpad_acpi, I do not. thinkpad_acpi does report the correct status in >> > Well, I don't know what events the acpi video driver is leaking that > userspace is keying to. > > >> sysfs, so this is just a reporting issue, but I thought this was >> supposed to be fixed with the latest update to thinkpad_acpi? >> > It is, the *proper* events for a non-ACPI backlight interface are all there, > you can see them using any C program that does poll() or select() in the > actual_brightness sysfs attribute, or if you use udevadm to see the uevents > the kernel is issuing. > > Which doesn't mean userspace is listening to them, yet. > > Lets try to add the gnome-power-manager developers to the discussion. Guys, basically the thinkpad_acpi driver has had some updates in 2.6.33-rc3 which include improved support for backlight on older thinkpads. Now on my old ThinkPad T41 pressing the buttons changes backlight, and the backlight sysfs entries change, but no OSD from gnome-power-manager On my newer ThinkPad T60 where backlight is handled by the acpi video driver, I do get OSD from gnome-power-manager. So what is gnome-power-manager using to keep track of backlight changes? -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
[ibm-acpi-devel] Fwd: Re: T41 Brightness with 2.6.33-rc3-git2
And obviously the gnome-power-manager-list turns out to be member only, so it bounced Original Message Subject:Re: [ibm-acpi-devel] T41 Brightness with 2.6.33-rc3-git2 Date: Mon, 11 Jan 2010 22:50:41 +0100 From: Robert de Rooy To: Henrique de Moraes Holschuh CC: [email protected], [email protected] On 11/01/10 21:43, Henrique de Moraes Holschuh wrote: On Mon, 11 Jan 2010, Robert de Rooy wrote: As to the brightness issue, I still do not get any output when I press the brightness buttons in /dev/input/event10, while I do get output on things like Fn-Space. I enabled the thinkpad_acpi debug options, but that does not seem to make any difference either. Brightness changes get exposed through backlight interface events, not through input devices. Since this is a somewhat new feature of the backlight interface, userspace seems not to have caught up to it yet. On my T60 where the acpi video driver handles the backlight I do get OSD without needing tpb, but on the T41 where it is handled by thinkpad_acpi, I do not. thinkpad_acpi does report the correct status in Well, I don't know what events the acpi video driver is leaking that userspace is keying to. sysfs, so this is just a reporting issue, but I thought this was supposed to be fixed with the latest update to thinkpad_acpi? It is, the *proper* events for a non-ACPI backlight interface are all there, you can see them using any C program that does poll() or select() in the actual_brightness sysfs attribute, or if you use udevadm to see the uevents the kernel is issuing. Which doesn't mean userspace is listening to them, yet. Lets try to add the gnome-power-manager developers to the discussion. Guys, basically the thinkpad_acpi driver has had some updates in 2.6.33-rc3 which include improved support for backlight on older thinkpads. Now on my old ThinkPad T41 pressing the buttons changes backlight, and the backlight sysfs entries change, but no OSD from gnome-power-manager On my newer ThinkPad T60 where backlight is handled by the acpi video driver, I do get OSD from gnome-power-manager. So what is gnome-power-manager using to keep track of backlight changes? -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
[ibm-acpi-devel] thinkpad_acpi alsa sub-driver with 2.6.33-rc4
Just an FYI that I also tried it on my T60 with the same result as on the T41 $ cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xee24 irq 30 29 [ThinkPadEC ]: ThinkPad EC - ThinkPad Console Audio Control ThinkPad Console Audio Control at EC reg 0x30, fw 79HT50WW-1.07 $ dmesg |grep thinkpad thinkpad_acpi: ThinkPad ACPI Extras v0.24 thinkpad_acpi: http://ibm-acpi.sf.net/ thinkpad_acpi: ThinkPad BIOS 79ETE5WW (2.25 ), EC 79HT50WW-1.07 thinkpad_acpi: Lenovo ThinkPad T60, model 1951CZ1 thinkpad_acpi: radio switch found; radios are enabled thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked thinkpad_acpi: Standard ACPI backlight interface available, not loading native one. thinkpad_acpi: Console audio control enabled, mode: monitor (read only) input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input8 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
[ibm-acpi-devel] ThinkPad X40 Dock support?
Hi, Has anyone got working Dock support on a X40? When I press the eject button on the "ThinkPad X4 Dock" nothing shows in "udevadm monitor", which it does do on my T60 when I press the eject button on its dock. Here is what syslog shows on the X40 with F12 kernel-2.6.31.12-174.2.19.fc12.i686 # dmesg |grep -i acpi BIOS-e820: 4f6e - 4f6f7000 (ACPI data) BIOS-e820: 4f6f7000 - 4f6f9000 (ACPI NVS) ACPI: RSDP 000f6d10 00024 (v02 IBM ) ACPI: XSDT 4f6e7e57 00054 (v01 IBMTP-1U2080 LTP ) ACPI: FACP 4f6e7f00 000F4 (v03 IBMTP-1U2080 IBM 0001) ACPI Warning: 32/64X length mismatch in Gpe1Block: 0/32 20090521 tbfadt-527 ACPI Warning: Optional field Gpe1Block has zero address or length: 102C/0 20090521 tbfadt-558 ACPI: DSDT 4f6e80e7 0ECE9 (v01 IBMTP-1U2080 MSFT 010E) ACPI: FACS 4f6f8000 00040 ACPI: SSDT 4f6e80b4 00033 (v01 IBMTP-1U2080 MSFT 010E) ACPI: ECDT 4f6f6dd0 00052 (v01 IBMTP-1U2080 IBM 0001) ACPI: TCPA 4f6f6e22 00032 (v01 IBMTP-1U2080 PTL 0001) ACPI: APIC 4f6f6e54 0005A (v01 IBMTP-1U2080 IBM 0001) ACPI: BOOT 4f6f6fd8 00028 (v01 IBMTP-1U2080 LTP 0001) ACPI: Local APIC address 0xfee0 ACPI: PM-Timer IO Port: 0x1008 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Using ACPI (MADT) for SMP configuration information ACPI: Core revision 20090521 ACPI: bus type pci registered ACPI: EC: EC description table is found, configuring boot EC ACPI: Interpreter enabled ACPI: (supports S0 S3 S4 S5) ACPI: Using IOAPIC for interrupt routing ACPI: EC: GPE = 0x1c, I/O: command/status = 0x66, data = 0x62 ACPI: Power Resource [PUBS] (on) ACPI: ACPI Dock Station Driver: 4 docks/bays found ACPI: PCI Root Bridge [PCI0] (:00) pci :00:1f.0: quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11) ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11) PCI: Using ACPI for IRQ routing pnp: PnP ACPI init ACPI: bus type pnp registered pnp: PnP ACPI: found 12 devices ACPI: ACPI bus type pnp unregistered apm: overridden by ACPI. acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 acpiphp: Slot [1] registered ACPI: AC Adapter [AC] (on-line) ACPI: Power Button [PWRF] ACPI: Lid Switch [LID] ACPI: Sleep Button [SLPB] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3]) ACPI: Processor [CPU0] (supports 8 throttling states) ACPI: Thermal Zone [THM0] (57 C) ACPI: Battery Slot [BAT0] (battery present) ehci_hcd :00:1d.7: power state changed by ACPI to D0 uhci_hcd :00:1d.0: power state changed by ACPI to D0 uhci_hcd :00:1d.1: power state changed by ACPI to D0 ACPI: Video Device [VID] (multi-head: yes rom: no post: no) i915 :00:02.0: power state changed by ACPI to D0 parport_pc 00:0a: reported by Plug and Play ACPI thinkpad_acpi: ThinkPad ACPI Extras v0.23 thinkpad_acpi: http://ibm-acpi.sf.net/ thinkpad_acpi: ThinkPad BIOS 1UETD3WW (2.08 ), EC 1UHTB0WW-1.60 thinkpad_acpi: IBM ThinkPad X40, model 2386F1U Registered led device: tpacpi::thinklight Registered led device: tpacpi::power Registered led device: tpacpi::standby -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
Re: [ibm-acpi-devel] ThinkPad X40 Dock support?
On 16/02/10 14:56, Henrique de Moraes Holschuh wrote: > Look at this one: > http://bugzilla.kernel.org/show_bug.cgi?id=15000 > > And this patch: > http://patchwork.kernel.org/patch/76123/ > > Maybe they fix your issue? Should be shipped in 2.6.32.9, I hope. > > Thanks Henrique! I will try to find some time to to build a kernel. The patch is only a one-liner, so should be easy. -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
[ibm-acpi-devel] unhandled HKEY event 0x4010 and 0x4011
When hot docking a ThinkPad T410 on a "ThinkPad Mini Dock Series 3" while running kernel 2.6.34.6, I get the following; Sep 7 20:57:13 t410 kernel: thinkpad_acpi: EC reports that Thermal Table has changed Sep 7 20:57:13 t410 kernel: thinkpad_acpi: unhandled HKEY event 0x4010 Sep 7 20:57:13 t410 kernel: thinkpad_acpi: please report the conditions when this event happened to [email protected] Sep 7 20:57:13 t410 kernel: usb 1-1.5: new high speed USB device using ehci_hcd and address 8 Sep 7 20:57:13 t410 kernel: usb 1-1.5: New USB device found, idVendor=17ef, idProduct=100a Sep 7 20:57:13 t410 kernel: usb 1-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Sep 7 20:57:13 t410 kernel: hub 1-1.5:1.0: USB hub found Sep 7 20:57:13 t410 kernel: hub 1-1.5:1.0: 6 ports detected Sep 7 20:57:14 t410 kernel: thinkpad_acpi: unhandled HKEY event 0x4010 Sep 7 20:57:14 t410 kernel: thinkpad_acpi: please report the conditions when this event happened to [email protected] Sep 7 20:57:14 t410 kernel: thinkpad_acpi: unhandled HKEY event 0x4010 Sep 7 20:57:14 t410 kernel: thinkpad_acpi: please report the conditions when this event happened to [email protected] While undocking gives Sep 7 21:06:57 t410 kernel: usb 1-1.5: USB disconnect, address 8 Sep 7 21:06:58 t410 kernel: thinkpad_acpi: EC reports that Thermal Table has changed Sep 7 21:06:58 t410 kernel: thinkpad_acpi: unhandled HKEY event 0x4011 Sep 7 21:06:58 t410 kernel: thinkpad_acpi: please report the conditions when this event happened to [email protected] Here are earlier messages displayed by thinkpad_acpi when initialized thinkpad_acpi: ThinkPad ACPI Extras v0.24 thinkpad_acpi: http://ibm-acpi.sf.net/ thinkpad_acpi: ThinkPad BIOS 6IET68WW (1.28 ), EC 6IHT36WW-1.11 thinkpad_acpi: Lenovo ThinkPad T410, model 2522AT6 thinkpad_acpi: radio switch found; radios are enabled thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked thinkpad_acpi: Standard ACPI backlight interface available, not loading native one. thinkpad_acpi: Console audio control enabled, mode: monitor (read only) input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input8 -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
Re: [ibm-acpi-devel] unhandled HKEY event 0x4010 and 0x4011
FYI, these newer series 3 "docks" no longer register themselves as a dock through ACPI. Instead they function more like port replicators. As such I think the HKEY event is just a way to detect a dock/undock event which can be used to trigger things like re-configuring the displays. On 07/09/10 21:09, Robert de Rooy wrote: > When hot docking a ThinkPad T410 on a "ThinkPad Mini Dock Series 3" > while running kernel 2.6.34.6, I get the following; > > Sep 7 20:57:13 t410 kernel: thinkpad_acpi: EC reports that Thermal > Table has changed > Sep 7 20:57:13 t410 kernel: thinkpad_acpi: unhandled HKEY event 0x4010 > Sep 7 20:57:13 t410 kernel: thinkpad_acpi: please report the > conditions when this event happened to > [email protected] > Sep 7 20:57:13 t410 kernel: usb 1-1.5: new high speed USB device > using ehci_hcd and address 8 > Sep 7 20:57:13 t410 kernel: usb 1-1.5: New USB device found, > idVendor=17ef, idProduct=100a > Sep 7 20:57:13 t410 kernel: usb 1-1.5: New USB device strings: Mfr=0, > Product=0, SerialNumber=0 > Sep 7 20:57:13 t410 kernel: hub 1-1.5:1.0: USB hub found > Sep 7 20:57:13 t410 kernel: hub 1-1.5:1.0: 6 ports detected > Sep 7 20:57:14 t410 kernel: thinkpad_acpi: unhandled HKEY event 0x4010 > Sep 7 20:57:14 t410 kernel: thinkpad_acpi: please report the > conditions when this event happened to > [email protected] > Sep 7 20:57:14 t410 kernel: thinkpad_acpi: unhandled HKEY event 0x4010 > Sep 7 20:57:14 t410 kernel: thinkpad_acpi: please report the > conditions when this event happened to > [email protected] > > While undocking gives > > Sep 7 21:06:57 t410 kernel: usb 1-1.5: USB disconnect, address 8 > Sep 7 21:06:58 t410 kernel: thinkpad_acpi: EC reports that Thermal > Table has changed > Sep 7 21:06:58 t410 kernel: thinkpad_acpi: unhandled HKEY event 0x4011 > Sep 7 21:06:58 t410 kernel: thinkpad_acpi: please report the > conditions when this event happened to > [email protected] > > Here are earlier messages displayed by thinkpad_acpi when initialized > > thinkpad_acpi: ThinkPad ACPI Extras v0.24 > thinkpad_acpi: http://ibm-acpi.sf.net/ > thinkpad_acpi: ThinkPad BIOS 6IET68WW (1.28 ), EC 6IHT36WW-1.11 > thinkpad_acpi: Lenovo ThinkPad T410, model 2522AT6 > thinkpad_acpi: radio switch found; radios are enabled > thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness > control, supported by the ACPI video driver > thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... > thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked > thinkpad_acpi: Standard ACPI backlight interface available, not > loading native one. > thinkpad_acpi: Console audio control enabled, mode: monitor (read only) > input: ThinkPad Extra Buttons as > /devices/platform/thinkpad_acpi/input/input8 -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
Re: [ibm-acpi-devel] unhandled HKEY event 0x4010 and 0x4011
Guys, Here is an interesting blog from Lenovo talking about the dock design change http://lenovoblogs.com/insidethebox/?p=290 Basically these docks do not have any features like PCI devices/slots, Ultrabay and such. And all the ports on the Dock are visible in the OS regardless if your docked or not, so no new devices are added on dock (other then a USB hub). As such I don't think it is really necessary to fully emulate a dock, all that should be needed are some events for userspace. Here are the various series 3 specs; http://www.thinkwiki.org/wiki/ThinkPad_Port_Replicator_Series_3 http://www.thinkwiki.org/wiki/ThinkPad_Mini_Dock_Series_3 http://www.thinkwiki.org/wiki/ThinkPad_Mini_Dock_Plus_Series_3 http://www.thinkwiki.org/wiki/ThinkPad_Mini_Dock_Plus_Series_3_for_Mobile_Workstations -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
[ibm-acpi-devel] Mute button/LED
As to the question of which ThinkPads have the button, here are the once that I know that have it; T410, T410i, T410s T510, T510i W510 The ThinkPad X201, X201i, X201s, W701 and W701ds strangely enough do *not* have the new layout. Regards, Robert -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
[ibm-acpi-devel] Detect dock/undock on hotplug dock with kernel 3.0?
Hi, Now that a patch bas been added to the 3.0 kernel to handle the hotplug events for the newer Docks, how do I act upon those? In the past with the ACPI docks, I would write a udev rule that looked for a docked event and run a script, but now I don't get any udev dock event, and the acpi dock.0 sysfs entry remains at 0. Here is what I get; Syslog thinkpad_acpi: undocked from hotplug port replicator thinkpad_acpi: docked into hotplug port replicator $ udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1312457755.972643] remove /devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0 (usb) KERNEL[1312457755.972752] remove /devices/pci:00/:00:1a.0/usb1/1-1/1-1.5 (usb) UDEV [1312457755.973813] remove /devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0 (usb) UDEV [1312457755.975058] remove /devices/pci:00/:00:1a.0/usb1/1-1/1-1.5 (usb) KERNEL[1312457756.477813] change /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/ACPI0003:00/power_supply/AC (power_supply) UDEV [1312457756.490313] change /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/ACPI0003:00/power_supply/AC (power_supply) KERNEL[1312457756.691886] change /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [1312457756.693001] change /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[1312457761.610276] add /devices/pci:00/:00:1a.0/usb1/1-1/1-1.5 (usb) KERNEL[1312457761.610498] add /devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0 (usb) UDEV [1312457761.615358] add /devices/pci:00/:00:1a.0/usb1/1-1/1-1.5 (usb) UDEV [1312457761.616916] add /devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0 (usb) KERNEL[1312457761.619800] change /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/ACPI0003:00/power_supply/AC (power_supply) UDEV [1312457761.664903] change /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/ACPI0003:00/power_supply/AC (power_supply) KERNEL[1312457761.850873] change /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [1312457761.852186] change /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/PNP0C0A:00/power_supply/BAT0 (power_supply) I also searched through sysfs and proc, but could not find anything that confirms that the ThinkPad is in fact docked. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ ibm-acpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
