[TOSHIBA NB 300] brightness keys don't produce an input event

[travauxpublics]

On my Netbook TOSHIBA NB 300 i have no control (hardware like software) of brightness (also i read on ubuntu forum that this bug is discuss under Ubuntu 9.10). The keyboard does not help any more, like Ubuntu 10.04 does not recognize this function.

PS : You can send me an email in french if it's your native language :-)

Thanks.
----
Description: Ubuntu lucid (development branch)
Release: 10.04
Noyau linux : 2.6.32-12 generic
Gnome : 2.29.6
Proc : Atom n 450

ProblemType: Bug
Architecture: i386
Date: Sun Jan 31 18:49:57 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/yelp
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100128)
Package: yelp 2.28.0+webkit-1ubuntu1
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
SourcePackage: yelp
Uname: Linux 2.6.32-12-generic i686

[Martin Pitt (pitti)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Please exercise the steps at https://wiki.ubuntu.com/Hotkeys/Troubleshooting to determine at which level your hotkey problems occur, and attach the collected information. Thanks!

[travauxpublics (travauxpublics)]

Bonjour,
Thanks to take time at this problem.

I'm not really understand what you want I do (my english is so bad).
I use Lucid (daily live 20100217) with a live USB (i have return under 9.10
on my netbook TOSHIBA NB 300 - Atom N450, GMA 3150)
I have read the page that you give. So I make this in a terminal :

To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

ubuntu@ubuntu:~$ killall gnome-settings-daemon gnome-power-manager
gnome-power-manager: no process found
ubuntu@ubuntu:~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\)
*\(.*\), .*$/keycode \2 = \3, state = \1/p'

I just obtain what you can see in the printscreen. Nothing else.

I will test this under Karmic.
--
tp

2010/2/15 Martin Pitt <email address hidden>

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> Please exercise the steps at
> https://wiki.ubuntu.com/Hotkeys/Troubleshooting to determine at which
> level your hotkey problems occur, and attach the collected information.
> Thanks!
>
> ** Changed in: udev (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: udev (Ubuntu)
> Assignee: Martin Pitt (pitti) => (unassigned)
>
> --
> No control of brightness and Wifi on TOSHIBA NB 300
> https://bugs.launchpad.net/bugs/515214
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Lionel Le Folgoc (mrpouit)]

Same here, no keypress detected in xev, udev nor acpi_listen. So this is probably a bug in the kernel, according to the wiki page...

[Lionel Le Folgoc (mrpouit)]

(on lucid up-to-date, of course)

[Lionel Le Folgoc (mrpouit)]

Unfortunately, I can't add a linux task, lp keeps on giving me time outs when I try.

[Antonio Sánchez (antoniosanchez)]

Following hotkey troubleshooting when I arrive at the point of "find broken scan codes" typing the combination of Fn+F7 (brightness up), Fn+F6 (brightness down) and Fn+F8 (wifi swicht) it doesn't produce any result.

root@nb300:/lib/udev# ./keymap -i input/event4
Press ESC to finish

scan code: 0x01 key code: esc

root@nb300:/lib/udev#

[Martin Pitt (pitti)]

Antonio,

I don't have an udev dump from you, so I can't tell which other device you should try. The easiest thing might be to try all event devices from event1, event2, ... until you hit the one which reacts to the brightness/wifi key. (Or get an error that the device doesn't exist, in which case you tried them all, and it's a kernel bug). Thanks!

[Antonio Sánchez (antoniosanchez)]

I've just tried the rest of the devices:

root@pc161-0:/lib/udev# ./keymap input/event1
### evdev 1.0.0., driver 'Power Button'
root@pc161-0:/lib/udev# ./keymap input/event2
### evdev 1.0.0., driver 'Power Button'
root@pc161-0:/lib/udev# ./keymap input/event3
### evdev 1.0.0., driver 'Macintosh mouse button emulation'
root@pc161-0:/lib/udev# ./keymap input/event5
### evdev 1.0.0., driver 'Chicony USB 2.0 Camera'
root@pc161-0:/lib/udev# ./keymap input/event6
### evdev 1.0.0., driver 'HDA Digital PCBeep'
root@pc161-0:/lib/udev# ./keymap input/event7
### evdev 1.0.0., driver 'SynPS/2 Synaptics TouchPad'
root@pc161-0:/lib/udev# ./keymap input/event8
error open('/dev/input/event8'): No such file or directory

and I attach the dump of input/event4.

Please tell me if we need any other test.

Thank you very much Martin.

[Antonio Sánchez (antoniosanchez)]

Attached the rest of the logs proposed in hotkeys troubleshooting.

[Martin Pitt (pitti)]

Thanks. So since they do not produce events on any input device, this needs to be fixed in the kernel. Reassigning.

[penalvch (penalvch)]

travauxpublics, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[travauxpublics (travauxpublics)]

Ok with Ubuntu 12.04 and Xubuntu 12.04. Thanks a lot for your work.
-----Original Message-----
From: "Christopher M. Penalver" <email address hidden>
Sender: <email address hidden>
Date: Tue, 24 Jul 2012 08:06:02
To: <email address hidden>
Reply-To: Bug 515214 <email address hidden>
Subject: [Bug 515214] Re: [TOSHIBA NB 300] brightness keys don't produce an
 input event

travauxpublics, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? Can you try with the latest development release of Ubuntu? ISO CD
images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the
development release from a Terminal
(Applications->Accessories->Terminal). It will automatically gather and
attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would
be great. It will allow additional upstream developers to examine the
issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do
not test the kernel in the daily folder, but the one all the way at the
bottom. Once you've tested the upstream kernel, please remove the
'needs-upstream-testing' tag. This can be done by clicking on the yellow
pencil icon next to the tag located at the bottom of the bug description
and deleting the 'needs-upstream-testing' text. As well, please comment
on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not
boot, please add the tag: 'kernel-unable-to-test-upstream', and comment
as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

** Summary changed:

- [TOSHIBA NB 300] brightness and wifi keys don't produce an input event
+ [TOSHIBA NB 300] brightness keys don't produce an input event

** Description changed:

  On my Netbook TOSHIBA NB 300 i have no control (hardware like software)
  of brightness (also i read on ubuntu forum that this bug is discuss
  under Ubuntu 9.10). The keyboard does not help any more, like Ubuntu
- 10.04 does not recognize this fonction. Also, impossible to
- enable/disable wifi. I must load wifi ON under Windows seven to have
- wifi under Ubuntu 10.04. But wifi is ok under this condition.
+ 10.04 does not recognize this function.

  PS : You can send me an email in french if it's your native language :-)

  Thanks.
  ----
  Description: Ubuntu lucid (development branch)
  Release: 10.04
  Noyau linux : 2.6.32-12 generic
  Gnome : 2.29.6
  Proc : Atom n 450

  ProblemType: Bug
  Architecture: i386
  Date: Sun Jan 31 18:49:57 2010
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/bin/yelp
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100128)
  Package: yelp 2.28.0+webkit-1u...

[penalvch (penalvch)]

travauxpublics, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.