AUO B140XW01 V.1 LCD screen
Screen Size 14 Inch
Resolution Pixels1366x768
Backlight TypeLED
Aspect Ratio 16:9
Screen Surface
Data Connection 40-Pin
Application Laptop or Notebook
AUO B140XW01 V.1 LCD screen
After recent (9.04) hotkey-setup update, it stopped generating acpi
events on my X40.
Any ideas?
I used to fiddle with /etc/modprobe.d/thinkpad_acpi.modprobe and passed
hotkey=enable brightness_mode=1 to it, but I'd rather not fiddle with
default settings of Ubuntu.
Besides, it should just
** Attachment added: please test this debdiff
http://launchpadlibrarian.net/19724052/hotkey-setup_0.1-23ubuntu8.debdiff
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40, R52
https://bugs.launchpad.net/bugs/222796
You received this bug notification because you are a
This morning I shipped my Notebook back to my onlinetrade...
After one week of investigation I found the reason why it doesnt work
correct an a SL500...
http://mailman.linux-thinkpad.org/pipermail/linux-
thinkpad/2008-October/044992.html
It isnt a bug. The incompatibel fimrware is the reason
Hey guys!
Last Saturday I got my brandnew Lenovo Thinkpad LS500 NRJ9AGE and installed
Intrepid Ibex (8.10) 64bit.
The problems concerning the hotkeys are still up2date for this modell. I read
that with hotkey-setup 0.1.28ubuntu7 the problems should be fixed, but
unfortunately not for my SL500.
I've just installed Intrepid from the Alternate CD and brightness works
just fine on my R52 18586MM. I've made no customisations, no
configuration changes, or any fixes and I started from a virgin disk
(well, reformatted :)
The Access IBM key doesn't appear to work out of the box.
--
Brightness
I120 fixes the mute key, I still have the problem that volume down
stops totems play in addition to lowering the volume. I plan to
reinstall my system - but not today 8-)
I can test the keys on Thinkpad T30, X60s , X61 and T61.
--
Brightness up not generating ACPI event on Thinkpad T43p, T42,
One more update :-) This time with good news.
I removed all post-install customizations from Intrepid, and setting
I120 does in fact work correctly wrt the T60p Mute button. Naked
config defaults to ACPI keyboard mappings, and those work correctly on
my T60p with the single modification to
Sorry for the delay ... can I remove gnome key settings with gconftool
--recursive-delete?
$ xkbcomp -xkb :0
Warning: Could not load keyboard geometry for :0
BadAlloc (insufficient resources for operation)
Resulting keymap file will not describe
Bryce Harrington wrote on 2008-10-28:
One thing to test might be to edit your /usr/share/X11/xkb/keycodes/evdev and
see if changing this:
I160 = 160; // #define KEY_COFFEE 152
to
I120 = 160; // #define KEY_COFFEE 152
makes the Mute key actually mute the speaker (which
Opps! wrote too soon. setting I120 no longer locks X, however it
changes the mute key functionality to the same as up volume.
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40, R52
https://bugs.launchpad.net/bugs/222796
You received this bug notification because you
In Hardy, xkb generally mapped:
I20 = XF86AudioMute
I160 = XF86ScreenSaver
For default xkb_keycodes evdev, keycode 160 = I160
However for xkb_keycodes basic, keycode 160 = I20
There are bunches of kludges for different keyboard layouts to map both
of these keys differently, but none of
One thing to test might be to edit your
/usr/share/X11/xkb/keycodes/evdev and see if changing this:
I160 = 160; // #define KEY_COFFEE 152
to
I120 = 160; // #define KEY_COFFEE 152
makes the Mute key actually mute the speaker (which works for me on
DSHR, another random idea - can you check your System Preferences
Keyboard Shortcuts and see what key is set for handling mute?
What I'm wondering is, if you upgraded from Hardy, and GNOME was hanging
on to an old keyboard mapping for the key from when you used basic,
then perhaps possibly it's
Oh, also we need the output of `xkbcomp -xkb :0 -`
Both `xkbcomp -xkb :0 -` and `setxkbmap -print` are always needed for
keyboard problems.
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40, R52
https://bugs.launchpad.net/bugs/222796
You received this bug notification
I forwarded the issue to
https://bugs.freedesktop.org/show_bug.cgi?id=18255, but we need the
aforementioned information before troubleshooting can be done.
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40, R52
https://bugs.launchpad.net/bugs/222796
You received this bug
Concentrating on the Mute Key on Thinkpad X60s:
# lsinput
/dev/input/event0
bustype : BUS_ADB
vendor : 0x1
product : 0x1
version : 256
name: Macintosh mouse button emulation
bits ev : EV_SYN EV_KEY EV_REL
/dev/input/event1
bustype : BUS_I8042
vendor : 0x1
product
And here is the output from a verbose g-p-m:
TI:23:07:40 TH:0x86b2640FI:gpm-button.c
FN:gpm_button_filter_x_events,122
- Key 160 mapped to HAL key lock
TI:23:07:40 TH:0x86b2640FI:gpm-manager.c
FN:button_pressed_cb,1020
- Button press event type=lock
TI:23:07:40
The mute key is recognized by gnome-power-manager as key 160, the reason
seems to be a wrong mapping in X - don't know how to change that. Is
xmodmap still the way to go? I'm using an evdev managed keyboard.
$ xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode
Hi,
I have a thinkpad x41 tablet.
Brigthness up is working very randomly.
I have the strong effect that if the notebook is running on battery the
brigthness goes down without pressing any brightness key. If it then press the
brightness up key it takes a very long time after the keypress is
I have an X60s. The recent hotkey update made by volume up/down keys
worked (they had worked in Hardy, but regressed in Intrepid Beta).
However, the mute hotkey invokes Lock Screen.
I believe a previous reporter with an X60s noted that a brightness key
made music/audio stop playing. This
On Tue, Oct 14, 2008 at 01:14:44PM -, Jane Silber wrote:
I have an X60s. The recent hotkey update made by volume up/down keys
worked (they had worked in Hardy, but regressed in Intrepid Beta).
However, the mute hotkey invokes Lock Screen.
I believe a previous reporter with an X60s noted
My mute key locks the screen, same situation as described by Jane:
[EMAIL PROTECTED]:~$ acpi_listen
ibm/hotkey HKEY 0080 1017
[EMAIL PROTECTED]:~$ lshal -m
Start monitoring devicelist:
-
16:46:36.257: computer_logicaldev_input_5 condition
On Tue, Oct 14, 2008 at 02:50:25PM -, DSHR wrote:
My mute key locks the screen, same situation as described by Jane:
[EMAIL PROTECTED]:~$ acpi_listen
ibm/hotkey HKEY 0080 1017
[EMAIL PROTECTED]:~$ lshal -m
Start monitoring devicelist:
On Mon, Oct 13, 2008 at 10:07:45PM -, DSHR wrote:
hotkey-setup (0.1-23ubuntu6) in intrepid fixes the problem of no OSD for
the volume keys on Lenovo X60s. The former working (without OSD) mute
key actually locks the screen now. This effect is new - never observed
that before.
Results on
hotkey-setup (0.1-23ubuntu6) in intrepid fixes the problem of no OSD for
the volume keys on Lenovo X60s. The former working (without OSD) mute
key actually locks the screen now. This effect is new - never observed
that before. The volume keys do work correctly now:
Volume Up; correct function,
hotkey-setup (0.1-23ubuntu6) in intrepid fixes the problem of no OSD for
the volume keys on Lenovo X60s. The former working (without OSD) mute
key actually locks the screen now. This effect is new - never observed
that before.
Results on Intrepid Beta on Lenovo X60s:
Lock Screen: Works and
I've uploaded a new hotkey-setup package to my PPA for testing:
deb http://ppa.launchpad.net/mdz/ubuntu intrepid main
deb-src http://ppa.launchpad.net/mdz/ubuntu intrepid main
** Attachment added: debdiff for 0.1-23ubuntu6
http://launchpadlibrarian.net/18497499/hotkey-setup-222796.diff
--
Tested on a Thinkpad X300 which had working hotkeys already and Matt's
change does not seem to have caused any regressions.
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40, R52
https://bugs.launchpad.net/bugs/222796
You received this bug notification because you are a
The various ThinkPad models are known to behave differently in various
tricky ways, and so I would appreciate broader testing of this package
(hotkey-setup 0.1-23ubuntu6).
If you have a ThinkPad (any model), please:
1. Before testing, make a note of which hotkeys work and which (if any) don't:
tjaalton mdz: works on my X61 like before, so no regressions there
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40, R52
https://bugs.launchpad.net/bugs/222796
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Unpatched Ubuntu 8.04 on ThinkPad SL500:
Lock Screen (Fn+F2) does nothing
Battery status (Fn+F3) does nothing (but I can't get what it's supposed to do,
I see bat status correctly with the gnome applet)
Sleep (Fn+F4) works
Wifi/RF kill works
Switch displays works but with some problems (gnome
BTW, I've just downgraded to hotkey-setup 0.1-17 (hardy) and it gives
just the same errors, but dpkg does not exit with error and the package
results correctly installed.
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40, R52
https://bugs.launchpad.net/bugs/222796
You
I got another test report for an X60s. The new hotkey-setup got the
volume up/down keys working where they were not before, and did not
regress any other hot keys.
However, the mute key still doesn't work there (it does lock screen
instead). This isn't significantly worse than before, though,
Invalidating the linux task on this bug, since I don't think we want to
fix this in the kernel (only in hotkey-setup)
** Changed in: linux (Ubuntu Intrepid)
Status: Triaged = Invalid
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40, R52
Confirmed that the combination of starting thinkpad-keys and using an
ibm-acpi hotkey mask of 0xff fixed the problem.
I'm attaching the acpid output showing the events generated by:
- volume down
- volume up
- mute
- brightness down
- brightness up
** Attachment added: acpid log showing
update:
[EMAIL PROTECTED]:~$ cat /boot/config-2.6.27-rc9 | grep -i thinkpad
CONFIG_THINKPAD_ACPI=m
# CONFIG_THINKPAD_ACPI_DEBUG is not set
CONFIG_THINKPAD_ACPI_BAY=y
CONFIG_THINKPAD_ACPI_VIDEO=y
CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y
# modprobe thinkpad_acpi
FATAL: Error inserting thinkpad_acpi
On Mon, Oct 13, 2008 at 01:48:44PM -, Lucio Crusca wrote:
update:
[EMAIL PROTECTED]:~$ cat /boot/config-2.6.27-rc9 | grep -i thinkpad
CONFIG_THINKPAD_ACPI=m
# CONFIG_THINKPAD_ACPI_DEBUG is not set
CONFIG_THINKPAD_ACPI_BAY=y
CONFIG_THINKPAD_ACPI_VIDEO=y
Tested on my Thinkpad T60:
TASK old package new package
Lock Screen y y
Battery status y y
Sleepn n
Wifi/RF kill y n
Switch displays n
I've now tested current Intrepid on the system I mentioned in comment
10, and confirmed that there is a problem there.
lock screen: works
sleep: works
RF kill: works
detect screens: works
hibernate: didn't test (live CD)
brightness: works (in hardware), but no software event and thus no OSD
I'm preparing an upload to revert the default mask to 0xff, as it
was in Hardy. This should fix things for anyone for whom the workaround
in https://bugs.edge.launchpad.net/ubuntu/+source/hotkey-
setup/+bug/222796/comments/5 works.
However, the original bug description seems to describe a
Bug 256887 explains why the mask was changed in Intrepid. Timo, it
appears that the default mask is not working properly at least for some
models.
** Tags added: regression-potential
** Tags removed: regression
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40, R52
Tested on my Thinkpad T61p
Before After
Volume upyesyes
Volume downyesyes
Mute yesyes
Battery status yesyes
Brightness up yesyes
Brightness down yes
The newer hotkey-setup is definitively better for my ThinkPad T30.
Results for IBM ThinkPad T30 (2366-92U)
Results on Hardy:
Lock Screen: Works and generates ACPI event
Sleep: Works and generates ACPI event
Switch displays: generates ACPI event (no external monitor for testing)
Hibernate:
Thanks to everyone who helped in testing. I have enough confidence in
the changes now that I've uploaded them to Intrepid. They should be
available within an hour or so, at which time it will no longer be
necessary to use the PPA in order to get this fix.
--
Brightness up not generating ACPI
This bug was fixed in the package hotkey-setup - 0.1-23ubuntu6
---
hotkey-setup (0.1-23ubuntu6) intrepid; urgency=low
* Revert 0.1-23ubuntu4 and use a different method to set the hotkey
mask:
+ Add hotkey mask definitions to ibm.hk
+ Use the sysfs interface rather than the
The brightness buttons on my T61 do correctly generate ACPI events, but
are subject to bug 280646 (should be fixed now)
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40, R52
https://bugs.launchpad.net/bugs/222796
You received this bug notification because you are a
The brightness keys work fine on my T42 running 8.04/Hardy. I haven't
tested Intrepid there yet.
** Changed in: linux (Ubuntu Intrepid)
Importance: Undecided = Medium
Status: New = Triaged
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40, R52
No, this is not fixed in intrepid as of today on a R52. The workaround
still works, too.
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40, R52
https://bugs.launchpad.net/bugs/222796
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I believe when I loaded the beta livecd on my T61 the brightness buttons
worked. I checked because I remembered they were not functional in the
Hardy beta for a while. I can check again if anyone thinks it will be
of use.
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31,
** Changed in: hotkey-setup (Ubuntu)
Importance: Undecided = Medium
Status: New = Triaged
** Tags added: regression
** Summary changed:
- Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40
+ Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40,
Can anyone comment on whether this is fixed in Intrepid? Please test
the beta and report.
--
Brightness up not generating ACPI event on Thinkpad T43p, T42, X31, X40, R52
https://bugs.launchpad.net/bugs/222796
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm reassigning this to the hotkey-setup package, as the hotkey-setup
init script is likely the best place to fix this. /proc/acpi/ibm/hotkey
initializes to 0x008c7fff, and the hotkey-setup init script only
modifies it to 0x00ff7fff, leaving the missing bit as the one
controlling the brightness
the above command does help, is there anyway to make this permanent?
also another problem related to this im having is when i unplug the
powercord the brightness will drop down like normal, when i replug the
power the brightness will not go all the way up. Ill unplug the power
again the
Hi,
I think I have at least found a workaround (after someone else pushed me in the
right direction): if you do
sudo su
echo enable,0xff /proc/acpi/ibm/hotkey
both buttons generate acpi events and show the OSD.
But now: how to make it permanent?
--
Brightness up not generating ACPI event
55 matches
Mail list logo
