Hi Maxim, Sorry, I did a mistake with the bright buttons The code is: BRIGHT UP Event: time 1284322292.776903, type 4 (Misc), code 4 (ScanCode), value 800f043a Event: time 1284322292.776931, type 1 (Key), code 225 (Brightness up), value 1 Event: time 1284322292.776935, -------------- Report Sync ------------ Event: time 1284322292.883125, type 4 (Misc), code 4 (ScanCode), value 800f043a Event: time 1284322293.021895, type 1 (Key), code 225 (Brightness up), value 2 Event: time 1284322293.061858, type 1 (Key), code 225 (Brightness up), value 2 Event: time 1284322293.101852, type 1 (Key), code 225 (Brightness up), value 2 Event: time 1284322293.141828, type 1 (Key), code 225 (Brightness up), value 2 Event: time 1284322293.181863, type 1 (Key), code 225 (Brightness up), value 2 Event: time 1284322293.221853, type 1 (Key), code 225 (Brightness up), value 2 Event: time 1284322293.231840, type 1 (Key), code 225 (Brightness up), value 0 Event: time 1284322293.231849, -------------- Report Sync ------------
BRIGHT DOWN Event: time 1284322261.791224, type 4 (Misc), code 4 (ScanCode), value 800f0480 Event: time 1284322261.791235, type 1 (Key), code 224 (Brightness down), value 1 Event: time 1284322261.791238, -------------- Report Sync ------------ Event: time 1284322261.897541, type 4 (Misc), code 4 (ScanCode), value 800f0480 Event: time 1284322262.003797, type 4 (Misc), code 4 (ScanCode), value 800f0480 Event: time 1284322262.034319, type 1 (Key), code 224 (Brightness down), value 2 Event: time 1284322262.074306, type 1 (Key), code 224 (Brightness down), value 2 Event: time 1284322262.114313, type 1 (Key), code 224 (Brightness down), value 2 Event: time 1284322262.153407, type 1 (Key), code 224 (Brightness down), value 2 Event: time 1284322262.194318, type 1 (Key), code 224 (Brightness down), value 2 Event: time 1284322262.233583, type 1 (Key), code 224 (Brightness down), value 2 Event: time 1284322262.274293, type 1 (Key), code 224 (Brightness down), value 2 Event: time 1284322262.312470, type 1 (Key), code 224 (Brightness down), value 2 Event: time 1284322262.354077, type 1 (Key), code 224 (Brightness down), value 0 Event: time 1284322262.354085, -------------- Report Sync ------------ About Windows buttons, in windows open the Media Center, I think in Ubuntu shall open XBMC, for example, and then I'll assing keyboard shortcut. What do you think? I don't kwon how to assing keyboard shortcuts, but I'll look for in google. How can I do to update with the errors fixed? Best Regards, Jordi 2010/9/12 Maxim Levitsky <maximlevit...@gmail.com> > >BUTTONS WITHOUT CODE > >MEDIA_KEY -> I think shall open TOTEM > >Event: time 1284210623.832037, type 4 (Misc), code 4 (ScanCode), value > 800f046f > >Event: time 1284210623.938322, type 4 (Misc), code 4 (ScanCode), value > 800f046f > Fixed, but you will need to assign the key an application. > Use keyboard shotcuts. > Same applies to many keys below. > > >START/STOP LAPTOP MEDIA BUTTON -> This button shall start and stop the > laptop media buttons > >Event: time 1284210685.489937, type 4 (Misc), code 4 (ScanCode), value > 800f0481 > >Event: time 1284210685.594641, type 4 (Misc), code 4 (ScanCode), value > 800f0481 > Fixed. > > >Bright up and bright down only works the firs time than I pulse, after > doesn¡t works. > Not my fault unfortunately. gnome-power-manger really assumes you press > these keys on keyboard. > > >BRIGHT UP > >Event: time 1284210785.200374, type 4 (Misc), code 4 (ScanCode), value > 800f0480 > >Event: time 1284210785.200404, type 1 (Key), code 224 (Brightness down), > value 1 > Please double check that this button is brightness up, and not down. > > > >BRIGHT DOWN > >Event: time 1284210827.712463, type 4 (Misc), code 4 (ScanCode), value > 800f043a > >Event: time 1284210827.712490, type 1 (Key), code 225 (Brightness up), > value 1 > Same here. > > >WINDOWS BUTTON -> I think shall open Aplicattion Menu > >Event: time 1284210945.027445, type 4 (Misc), code 4 (ScanCode), value > 800f040d > >Event: time 1284210945.027471, type 1 (Key), code 148 (Prog1), value 1 > This key works. > I don't think you could assign it to Application menu easily. > Probably would need to assign it some shell script with dbus instructions. > Anyway, its gnome limitation. > > > >DVD BUTTON -> I think shall open XINE > >Event: time 1284210966.345781, type 4 (Misc), code 4 (ScanCode), value > 800f0424 > >Event: time 1284210966.345806, type 1 (Key), code 389 (DVD), value 1 > Now fixed, but again, assign it in keyboard shortcuts. > Understand that now these keys send different keycodes, that are much more > generic. > So you need to assign them. Or ask X devs to fix the 248 limit. > > >INFORMATION BUTTON -> I don't know which is the normal use > >Event: time 1284211075.753796, type 4 (Misc), code 4 (ScanCode), value > 800f040f > >Event: time 1284211075.753821, type 1 (Key), code 358 (Info), value 1 > >Fixed, will open help by default. > > >ARROW LEFT (BUT DIFFERENT THAT THE MOVEMENT LEFT, RIGHT, UP, DOWN > BUTTONS) > >-> I don't know which is the normal use > >Event: time 1284211246.823264, type 4 (Misc), code 4 (ScanCode), value > 800f0423 > >Event: time 1284211246.823279, type 1 (Key), code 1 (Esc), value 1 > This is assigned to Esc key. > I think the key means cancel. > > -- > ENE CIR Receiver chip don't work > https://bugs.launchpad.net/bugs/501923 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “linux” package in Ubuntu: In Progress > > Bug description: > I'm an Ubuntu 9.10 64 bits user, and I get a Toshiba A500-141 laptop. > > I try to use the IRDA Remote controller (RC6ir), and the Receiver is an ENE > CIR Receiver, model ENE0200. > jo...@jordi-ubuntu:~$ lspnp > 00:00 PNP0a08 (unknown) > 00:01 ENE0200 (unknown) > 00:02 PNP0200 AT DMA controller > 00:03 PNP0103 High-Precision Event Timer > 00:04 PNP0c04 Math coprocessor > 00:05 PNP0c02 Motherboard resources > 00:06 PNP0b00 AT real-time clock > 00:07 PNP0303 IBM enhanced keyboard (101/102-key, PS/2 mouse support) > 00:08 SYN0712 (unknown) > 00:09 PNP0c02 Motherboard resources > jo...@jordi-ubuntu:~$ > > I'm looking for the drivers but I think it isn't supported in linux. > > Awaiting your news. > > Thank you very much > > ProblemType: Bug > Architecture: amd64 > CheckboxSubmission: bcebcd0afb07ebec631dbc27ef4e6ef0 > CheckboxSystem: b1865df84255b8716d3bcc269ff410d1 > Date: Thu Dec 31 17:02:29 2009 > DistroRelease: Ubuntu 9.10 > ExecutablePath: /usr/bin/yelp > InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) > NonfreeKernelModules: fglrx > Package: yelp 2.28.0-0ubuntu2 > ProcEnviron: > LANG=es_ES.UTF-8 > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.31-16.53-generic > SourcePackage: yelp > Uname: Linux 2.6.31-16-generic x86_64 > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/501923/+subscribe > -- ENE CIR Receiver chip don't work https://bugs.launchpad.net/bugs/501923 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
