Hello, I stumbled upon this (seemingly) wonderful little program in the mere moments before laying down my laptop for bed. I have been frantically attempting to get my remote working on my newly-installed MythTV setup. I have everything in place to make it one hell of a system (and light years ahead of my last install), but I'm missing the remote. I have tried every tutorial and trick I could find relating to Feisty and to the Hauppauge remote. Until I found this.
It's simple, it's virtually idiot proof. But it doesn't work for me. I have been successful in getting MythTV to recognize my remote (as Feisty recognizes it out of the box) for simple things, such as numbers and volume up and down. However, using the arrow keys, the OK button or any of the others do not seem to work. It's frustrating to have to control MythTV from across the room and have to stand up to navigate to the file you are attempting to play.
I have install Gizmod successfully and without incident, but it has not changed the way MythTV reacts to my remote. I have made the following modifications to attempt to get it to work:
modified 510-LIRC-Hauppauge-MythTV.py to read USES_LIRC_REMOTES = [i2c IR (Hauppauge)] - as this is what displays when I type in gizmod
modified GizmoDeviceStrings.py to classify my remote as both a keyboard and as a LIRC remote
Neither of the above modifications, in any combination, have allowed me to control MythTV with my remote. Any further assistance would be greatly appreciated. Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Let me ask you a seemingly stupid question... do you have plain old keyboard and mouse plugged in to your system? If not, or if you are using a fancy all-in-one USB thingy like I am, then that is the most likely cause of the problem.
See, gizmod uses existing devices to simulated key presses and button movement. Which means if there isn't an existing device, it can't simulate squat. The easiest way to confirm this it so start gizmod and look at the first batch of output that lists all the devices it can find. If there isn't one that says keyboard and one that says mouse, then that's the first problem.
-Sean
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the fast reply. Below is the output of the first batch of output. As you can see, there is both a traditional mouse and keyboard attached (Mouse via USB, Keyboard vis PS/2).
Standard - Directory [/dev/input]
Mouse - Macintosh mouse button emulation [/dev/input/event0]
Keyboard - AT Translated Set 2 keyboard [/dev/input/event1]
Mouse - Dell Dell USB Mouse [/dev/input/event2]
Standard - PC Speaker [/dev/input/event3]
LIRC - i2c IR (Hauppauge) [/dev/input/event4]
Standard - Power Button (FF) [/dev/input/event5]
Standard - Power Button (CM) [/dev/input/event6]
As you can also see, I currently have the i2c IR (Hauppauge) as a LIRC device.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, that looks good. Have you tried to run gizmod in dubug mode with the -g flag? Does gizmod recongize any events when you press buttons on the remote?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think the problem is the "Macintosh mouse button emulation" device that gets enumerated as a mouse. I've got this fixed in SVN, so if you're keen you can install from SVN.
Or, if you'd prefer there's another way to fix this:
Edit /etc/gizmod/GizmoDeviceStrings.py
Change the line that says "MOUSE_GIZMOS", and remove the "mouse" field, replacing is with "USB Mouse" (to match your setup) so it'll look something like this:
Standard - Directory [/dev/input]
Standard - Macintosh mouse button emulation [/dev/input/event0]
Keyboard - AT Translated Set 2 keyboard [/dev/input/event1]
Mouse - Dell Dell USB Mouse [/dev/input/event2]
Standard - PC Speaker [/dev/input/event3]
LIRC - i2c IR (Hauppauge) [/dev/input/event4]
Standard - Power Button (FF) [/dev/input/event5]
Standard - Power Button (CM) [/dev/input/event6]
So at least the mouse emulation is now falling under Standard as opposed to Mouse. Sadly, this doesn't fix the problem.
When I run gizmod -g for debug mode (when I have i2c listed as a LIRC device): Sees that I'm pressing some buttons, notable the Vol+ and Vol- but almost nothing else.
When I run gizmod -g for debug mode (when I have i2c listed as a keyboard device): Sees that I'm pressing almost all of my keys, except for the important ones like Up, Down, Left, Right and OK.
When I run gizmod -g for debug mode (when I have i2c listed as a no device, and thus Standard): Sees that I'm pressing almost all of my keys, except for the important ones like Up, Down, Left, Right and OK.
I'll be at work all day, but will gladly try anymore tricks or tips when I get home. I will also try to install SVN when I get home. Thanks again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay I believe the issue may be that you just need to create some new button maps for your remote. I don't have a PVR-350 (just a couple 150s), so I've never tested with its remote!
First of all, when you run "irw" from the command line, and press some buttons do you see lines like this:
00000000000017a0 00 Ch+ Hauppauge_350
(Is the device column set to "Hauppauge_350"?)
Next, take a look at one of the Hauppauge scripts (ie /etc/modules.d/scripts/599-LIRC-Hauppauge-Default.py), do the button strings in there (ie "Power", etc) match the strings that come up with irw?
Thanks,
Tim.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm... from your ubuntu forums post I have a feeling your lirc setup is not going to work.
Basically I don't think ir-kbd-i2c is the right module, but I could be wrong. On my system the module is "lirc_i2c" (which should auto-load lirc_dev).
It appears as if ir-kbd-i2c is a module that tries to make the lirc device an actual keyboard on the system. This really isn't what you want for Gizmod, although it could be made to support this. But as is, this will never work.
If I'm right about what ir-kbd-i2c is doing you're left with two options: 1) stop using it, or 2) write a new set of scripts that support this. They would probably be easy to create as this is the same method that the ATIX10 remote uses, so you could probably base the scripts off of the *ATIX10* scripts.
Thanks,
Tim.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
They are certainly outdated and still does not rectify the problem.
The idea of creating a new set of scripts seems rather daunting especially considering the busy week I face at work (won't have a day off until next Tuesday).
Additionally, the concept of stop using ir-kbd-i2c sounds just fine, but I'm not sure how to do it. I'd love to start over with everything LIRC and remote related, but I'm too far entrenched. I attempted to reinstall LIRC, but it wouldn't even create a /etc/lirc/hardware.conf file. If you could tell me how to back everything out so that I can start over with only Gizmod working, I would be very grateful. The steps I have taken have been documented here: http://www.blogger.com/publish-confirmation.g?blogID=10570758&postID=8144042682037059980×tamp=1187045132038&javascriptEnabled=true
Thanks so much for your time.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm... well first off I'm a Gentoo user, so I didn't really have to do anything aside from emerge lirc (with the hauppauge driver).
You shouldn't need to worry too much about uninstalling or anything, except remove any references in config files to the i2c-kbd driver (in case you set it to autoload on boot or anything). Re-installing lirc should overwrite a previous configuration.
After taking a brief look at what needs to be done on Ubuntu, I can't believe how complicated it is. No wonder you're having problems!
Looks like this chap has a working lirc_i2c setup. Warning if you're using kernel >= 2.6.22 you'll need to install lirc from CVS. Not an issue, but I'd say stick with an older kernel if possible. Make sure you read a few messages down, there's some good tips there. But don't worry too much about people complaining it still doesn't work. If we can get you with lirc_i2c loaded, and lircd running, I guarantee you we'll get Gizmod working.
Basically all you need to do is get lirc installed so that you can modprobe lirc_i2c. Once that's working Gizmod will probably "just work".
Try to remember exactly what steps you've done so if you run into any problems you can just paste them here, and we can get it sorted out.
Good luck!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have been able to very easily get LIRC up and running on another machine running Kubuntu. I used the directions found here: https://help.ubuntu.com/community/Install_Lirc_Feisty and ran into no problems. If I run those same commands on my Myth box, I can't modprobe lirc_i2c as it says the module can't be found. Any ideas on how to start over? I've obviously screwed it up to the point that I can't fix it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I used the one in the repositories. A little more info. I was able to do my irrecord and everything else, but when I type in irw it drops me back to terminal. dmesg | grep -i lirc says
no version for "lirc_unregister_plugin" found: kernel tainted
This is after I have to sudo modprobe lirc_i2c and lirc_pvr150 as well as sudo /usr/sbin/lircd
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ORIGINAL TERMINAL:
lircd-0.8.2-CVS[5858]: accepted new client on /dev/lircd
lircd-0.8.2-CVS[5858]: could not get file information for /dev/lirc
lircd-0.8.2-CVS[5858]: default_init(): No such file or directory
lircd-0.8.2-CVS[5858]: caught signal
Terminated
I created a symlink:
sudo ln -s /dev/lirc0 /dev/lirc
Re-ran irw and it seems to work. Now I just need to edit the lircd.conf file to the proper settings, correct?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Got it working. Found a lircd.conf file for my remote and ran Gizmod and it began to control MythTV. Some tweaking needs to be done (I've lost the ability to Vol+ and Vol-), but for the most part it seems to be working. Now to load lird and modprobe lirc_i2c on startup...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Excellent! Glad to hear it's working. About the vol+ and vol-, do you mean you don't see these buttons giving any output in irw?
To load on startup all you should have to do is add lirc_i2c to the module autoload config file (on Gentoo it's in /etc/modules.autoload.d/, but it's probably different for Ubuntu). And I'm sure the lirc startup script automatically takes care of creating the proper device node, so you should just have to set /etc/init.d/lircd to run at bootup.
Now, once that's done, on to gizmod. What happens when you run gizmod now?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After I posted I went ahead and ran Gizmod and it worked. I was controlling MythTV like it was going out of style. I haven't had time to fix up the boot sequence and all, but I will in the next few days.
As far as the Vol+ and Vol-, when I had the remote pseudo working earlier, when I pressed these buttons, Gnome would turn the volume up and down. Now when I press them, nothing happens. I'm sure it's all in the lircd.conf and Gizmod scripts, so it's just a matter of tweaking those, but that, too, will have to wait until next week.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Awesome! Glad to hear you're getting somewhere with this.
The volume changing should be handled by gizmod now. If not perhaps it's not detecting the sound card correctly. If this is the case can you post the output of "gizmod -g" -- you should see some sound card related stuff after the initial script loading phase.
Thanks,
Tim.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I found this post here (http://ubuntuforums.org/archive/index.php/t-270630.html) and have just created the script that gavinb has suggested. Rebooting now and we'll see if it works.
Huzzah! Not all the buttons are working, but I imagine that's all mapping at this point, so it's time to fix that up.
The question I have now is: Do I map Gizmod or my lircd.conf files to get the desired results.
As of now, the Back/Exit button does not go back nor does it exit in addition the volume control not working. As you suggested, I ran gizmod -g and get back the following:
Standard - Directory [/dev/input]
Standard - Macintosh mouse button emulation [/dev/input/event0]
Keyboard - AT Translated Set 2 keyboard [/dev/input/event1]
Standard - PC Speaker [/dev/input/event2]
Mouse - Dell Dell USB Mouse [/dev/input/event3]
Standard - Power Button (FF) [/dev/input/event4]
Standard - Power Button (CM) [/dev/input/event5]
LIRC - LIRC [/dev/lircd]
Got it working! I'm not exactly what combination of events I just did managed to make it work, but it works now. I still don't see the OSD for volume adjustments, but it works nonetheless. And somehow the Back/Exit button now works as well.
Something I did notice was that I had 3 different lircd.conf files stored into the 1 file (ie it listed 3 different sets of data), so I cleaned that up, changed the keyboard shortcut in Ubuntu and made the Gizmod script hit that shortcut and it works now. See below:
Everything *seems* to be working now. I will keep you posted as anything else arises.
Tim, thank you for your help and support through all of this, I couldn't have otherwise. You've got a nice little app going here and I will certainly recommend it to anyone I come across looking to install MythTV. Thanks again!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I stumbled upon this (seemingly) wonderful little program in the mere moments before laying down my laptop for bed. I have been frantically attempting to get my remote working on my newly-installed MythTV setup. I have everything in place to make it one hell of a system (and light years ahead of my last install), but I'm missing the remote. I have tried every tutorial and trick I could find relating to Feisty and to the Hauppauge remote. Until I found this.
It's simple, it's virtually idiot proof. But it doesn't work for me. I have been successful in getting MythTV to recognize my remote (as Feisty recognizes it out of the box) for simple things, such as numbers and volume up and down. However, using the arrow keys, the OK button or any of the others do not seem to work. It's frustrating to have to control MythTV from across the room and have to stand up to navigate to the file you are attempting to play.
I have install Gizmod successfully and without incident, but it has not changed the way MythTV reacts to my remote. I have made the following modifications to attempt to get it to work:
modified 510-LIRC-Hauppauge-MythTV.py to read USES_LIRC_REMOTES = [i2c IR (Hauppauge)] - as this is what displays when I type in gizmod
modified GizmoDeviceStrings.py to classify my remote as both a keyboard and as a LIRC remote
Neither of the above modifications, in any combination, have allowed me to control MythTV with my remote. Any further assistance would be greatly appreciated. Thanks.
Let me ask you a seemingly stupid question... do you have plain old keyboard and mouse plugged in to your system? If not, or if you are using a fancy all-in-one USB thingy like I am, then that is the most likely cause of the problem.
See, gizmod uses existing devices to simulated key presses and button movement. Which means if there isn't an existing device, it can't simulate squat. The easiest way to confirm this it so start gizmod and look at the first batch of output that lists all the devices it can find. If there isn't one that says keyboard and one that says mouse, then that's the first problem.
-Sean
Thanks for the fast reply. Below is the output of the first batch of output. As you can see, there is both a traditional mouse and keyboard attached (Mouse via USB, Keyboard vis PS/2).
Standard - Directory [/dev/input]
Mouse - Macintosh mouse button emulation [/dev/input/event0]
Keyboard - AT Translated Set 2 keyboard [/dev/input/event1]
Mouse - Dell Dell USB Mouse [/dev/input/event2]
Standard - PC Speaker [/dev/input/event3]
LIRC - i2c IR (Hauppauge) [/dev/input/event4]
Standard - Power Button (FF) [/dev/input/event5]
Standard - Power Button (CM) [/dev/input/event6]
As you can also see, I currently have the i2c IR (Hauppauge) as a LIRC device.
Well, that looks good. Have you tried to run gizmod in dubug mode with the -g flag? Does gizmod recongize any events when you press buttons on the remote?
Hey Jason,
I think the problem is the "Macintosh mouse button emulation" device that gets enumerated as a mouse. I've got this fixed in SVN, so if you're keen you can install from SVN.
Or, if you'd prefer there's another way to fix this:
Edit /etc/gizmod/GizmoDeviceStrings.py
Change the line that says "MOUSE_GIZMOS", and remove the "mouse" field, replacing is with "USB Mouse" (to match your setup) so it'll look something like this:
MOUSE_GIZMOS = ["usb mouse", "trackball", "touchpad"]
Try that, and let me know if that does the trick!
Thanks,
Tim.
Ok, running gizmod now says:
Registering Devices:
Standard - Directory [/dev/input]
Standard - Macintosh mouse button emulation [/dev/input/event0]
Keyboard - AT Translated Set 2 keyboard [/dev/input/event1]
Mouse - Dell Dell USB Mouse [/dev/input/event2]
Standard - PC Speaker [/dev/input/event3]
LIRC - i2c IR (Hauppauge) [/dev/input/event4]
Standard - Power Button (FF) [/dev/input/event5]
Standard - Power Button (CM) [/dev/input/event6]
So at least the mouse emulation is now falling under Standard as opposed to Mouse. Sadly, this doesn't fix the problem.
When I run gizmod -g for debug mode (when I have i2c listed as a LIRC device): Sees that I'm pressing some buttons, notable the Vol+ and Vol- but almost nothing else.
When I run gizmod -g for debug mode (when I have i2c listed as a keyboard device): Sees that I'm pressing almost all of my keys, except for the important ones like Up, Down, Left, Right and OK.
When I run gizmod -g for debug mode (when I have i2c listed as a no device, and thus Standard): Sees that I'm pressing almost all of my keys, except for the important ones like Up, Down, Left, Right and OK.
I'll be at work all day, but will gladly try anymore tricks or tips when I get home. I will also try to install SVN when I get home. Thanks again.
Okay I believe the issue may be that you just need to create some new button maps for your remote. I don't have a PVR-350 (just a couple 150s), so I've never tested with its remote!
First of all, when you run "irw" from the command line, and press some buttons do you see lines like this:
00000000000017a0 00 Ch+ Hauppauge_350
(Is the device column set to "Hauppauge_350"?)
Next, take a look at one of the Hauppauge scripts (ie /etc/modules.d/scripts/599-LIRC-Hauppauge-Default.py), do the button strings in there (ie "Power", etc) match the strings that come up with irw?
Thanks,
Tim.
I thought the same things (see my post on ubuntuforums.org here: http://ubuntuforums.org/showthread.php?p=3177130#post3177130
When I type in irw, I get "connect: No such file or directory"
With irw /dev/input/event4, I get "connect: Connection refused"
With sudo irw /dev/input/event4, I get "connect: Connection refused"
No, xev works just fine (ish), so typing in xev it recognizes most of my buttons. Though notable are the directional and OK ones.
As far as I'm aware, the remote (and drivers, etc) are the same for both the pvr-150 and the pvr-350, though I may be wrong.
Hmm... are you running lircd? (ie /etc/init.d/lircd status)?
Hmm... from your ubuntu forums post I have a feeling your lirc setup is not going to work.
Basically I don't think ir-kbd-i2c is the right module, but I could be wrong. On my system the module is "lirc_i2c" (which should auto-load lirc_dev).
It appears as if ir-kbd-i2c is a module that tries to make the lirc device an actual keyboard on the system. This really isn't what you want for Gizmod, although it could be made to support this. But as is, this will never work.
If I'm right about what ir-kbd-i2c is doing you're left with two options: 1) stop using it, or 2) write a new set of scripts that support this. They would probably be easy to create as this is the same method that the ATIX10 remote uses, so you could probably base the scripts off of the *ATIX10* scripts.
Thanks,
Tim.
Thanks for the advice and a quick update. I was able to get the OK button to recognize by following the instructions found here: http://ivtv.writeme.ch/tiki-index.php?page=remotes
They are certainly outdated and still does not rectify the problem.
The idea of creating a new set of scripts seems rather daunting especially considering the busy week I face at work (won't have a day off until next Tuesday).
Additionally, the concept of stop using ir-kbd-i2c sounds just fine, but I'm not sure how to do it. I'd love to start over with everything LIRC and remote related, but I'm too far entrenched. I attempted to reinstall LIRC, but it wouldn't even create a /etc/lirc/hardware.conf file. If you could tell me how to back everything out so that I can start over with only Gizmod working, I would be very grateful. The steps I have taken have been documented here: http://www.blogger.com/publish-confirmation.g?blogID=10570758&postID=8144042682037059980×tamp=1187045132038&javascriptEnabled=true
Thanks so much for your time.
Hmm... well first off I'm a Gentoo user, so I didn't really have to do anything aside from emerge lirc (with the hauppauge driver).
You shouldn't need to worry too much about uninstalling or anything, except remove any references in config files to the i2c-kbd driver (in case you set it to autoload on boot or anything). Re-installing lirc should overwrite a previous configuration.
After taking a brief look at what needs to be done on Ubuntu, I can't believe how complicated it is. No wonder you're having problems!
Have you tried following instructions similar to these: http://ubuntuforums.org/showthread.php?t=30612&highlight=lirc
Looks like this chap has a working lirc_i2c setup. Warning if you're using kernel >= 2.6.22 you'll need to install lirc from CVS. Not an issue, but I'd say stick with an older kernel if possible. Make sure you read a few messages down, there's some good tips there. But don't worry too much about people complaining it still doesn't work. If we can get you with lirc_i2c loaded, and lircd running, I guarantee you we'll get Gizmod working.
Basically all you need to do is get lirc installed so that you can modprobe lirc_i2c. Once that's working Gizmod will probably "just work".
Try to remember exactly what steps you've done so if you run into any problems you can just paste them here, and we can get it sorted out.
Good luck!
I have been able to very easily get LIRC up and running on another machine running Kubuntu. I used the directions found here: https://help.ubuntu.com/community/Install_Lirc_Feisty and ran into no problems. If I run those same commands on my Myth box, I can't modprobe lirc_i2c as it says the module can't be found. Any ideas on how to start over? I've obviously screwed it up to the point that I can't fix it.
Which lirc driver did you compile with?
I used the one in the repositories. A little more info. I was able to do my irrecord and everything else, but when I type in irw it drops me back to terminal. dmesg | grep -i lirc says
no version for "lirc_unregister_plugin" found: kernel tainted
This is after I have to sudo modprobe lirc_i2c and lirc_pvr150 as well as sudo /usr/sbin/lircd
I don't think you should need lirc_pvr150. Try this:
reboot
modprobe lirc_i2c
lircd -n
in a new console:
irw
if irw connects (ie doesn't exit immediately) press buttons on remote
if irw doesn't connect, see the lircd window and let me know what output it spits out.
Thanks,
Tim.
Ok, fresh reboot.
modprobe lirc_i2c
WARNING: Error inserting lirc_dev (/lib/modules/2.6.20-16-generic/misc/lirc_dev.ko): Operation not permitted
FATAL: Error inserting lirc_i2c (/lib/modules/2.6.20-16-generic/misc/lirc_i2c.ko): Operation not permitted
sudo modprobe lirc_i2c
lircd -n
lircd: can't open or create /var/run/lircd.pid
lircd: Permission denied
sudo lircd -n
lircd-0.8.2-CVS[5858]: lircd(userspace) ready
OTHER TERMINAL:
irw
ORIGINAL TERMINAL:
lircd-0.8.2-CVS[5858]: accepted new client on /dev/lircd
lircd-0.8.2-CVS[5858]: could not get file information for /dev/lirc
lircd-0.8.2-CVS[5858]: default_init(): No such file or directory
lircd-0.8.2-CVS[5858]: caught signal
Terminated
I created a symlink:
sudo ln -s /dev/lirc0 /dev/lirc
Re-ran irw and it seems to work. Now I just need to edit the lircd.conf file to the proper settings, correct?
Got it working. Found a lircd.conf file for my remote and ran Gizmod and it began to control MythTV. Some tweaking needs to be done (I've lost the ability to Vol+ and Vol-), but for the most part it seems to be working. Now to load lird and modprobe lirc_i2c on startup...
Excellent! Glad to hear it's working. About the vol+ and vol-, do you mean you don't see these buttons giving any output in irw?
To load on startup all you should have to do is add lirc_i2c to the module autoload config file (on Gentoo it's in /etc/modules.autoload.d/, but it's probably different for Ubuntu). And I'm sure the lirc startup script automatically takes care of creating the proper device node, so you should just have to set /etc/init.d/lircd to run at bootup.
Now, once that's done, on to gizmod. What happens when you run gizmod now?
After I posted I went ahead and ran Gizmod and it worked. I was controlling MythTV like it was going out of style. I haven't had time to fix up the boot sequence and all, but I will in the next few days.
As far as the Vol+ and Vol-, when I had the remote pseudo working earlier, when I pressed these buttons, Gnome would turn the volume up and down. Now when I press them, nothing happens. I'm sure it's all in the lircd.conf and Gizmod scripts, so it's just a matter of tweaking those, but that, too, will have to wait until next week.
Awesome! Glad to hear you're getting somewhere with this.
The volume changing should be handled by gizmod now. If not perhaps it's not detecting the sound card correctly. If this is the case can you post the output of "gizmod -g" -- you should see some sound card related stuff after the initial script loading phase.
Thanks,
Tim.
I'm back and closer than ever!
I found this post here (http://ubuntuforums.org/archive/index.php/t-270630.html) and have just created the script that gavinb has suggested. Rebooting now and we'll see if it works.
Huzzah! Not all the buttons are working, but I imagine that's all mapping at this point, so it's time to fix that up.
The question I have now is: Do I map Gizmod or my lircd.conf files to get the desired results.
As of now, the Back/Exit button does not go back nor does it exit in addition the volume control not working. As you suggested, I ran gizmod -g and get back the following:
GizmoDaemon v3:3 -=- (c) 2007, Tim Burrell <tim.burrell@gmail.com>
-----------
Debug Mode Enabled
Registering Devices:
Standard - Directory [/dev/input]
Standard - Macintosh mouse button emulation [/dev/input/event0]
Keyboard - AT Translated Set 2 keyboard [/dev/input/event1]
Standard - PC Speaker [/dev/input/event2]
Mouse - Dell Dell USB Mouse [/dev/input/event3]
Standard - Power Button (FF) [/dev/input/event4]
Standard - Power Button (CM) [/dev/input/event5]
LIRC - LIRC [/dev/lircd]
--user scritps omitted--
Unable to Open X11 Display [Default] -- Per application mappings will not work!
Attached to Sound Card [hw:0] -- NVidia nForce2
onEvent: SoundCard -- SoundCardAttach [NVidia nForce2]
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Master Mono>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Master Mono> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Master Mono> Vol: 0.0
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Master Mono> Vol: 80.6451644897
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Master>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Master> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Master> Vol: 0.0
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Master> Vol: 70.9677429199
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <3D Control - Center>
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <3D Control - Depth>
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <3D Control - Switch>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <3D Control - Switch> Unmute
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <PCM>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <PCM> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <PCM> Vol: 0.0
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <PCM> Vol: 70.9677429199
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Surround Down Mix>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Surround Down Mix> Unmute
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Surround Jack Mode>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Surround Jack Mode>
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Surround>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Surround> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Surround> Vol: 0.0
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Center/LFE Down Mix>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Center/LFE Down Mix> Unmute
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Center>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Center> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Center> Vol: 0.0
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Center> Vol: 100.0
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <LFE>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <LFE> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <LFE> Vol: 0.0
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Line>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Line> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Line> Vol: 0.0
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <CD>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <CD> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <CD> Vol: 0.0
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <CD> Vol: 80.6451644897
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Mic Boost (+20dB)>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Mic Boost (+20dB)> Unmute
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Mic Select>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Mic Select>
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Mic>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Mic> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Mic> Vol: 0.0
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Phone>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Phone> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Phone> Vol: 0.0
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Video>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Video> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Video> Vol: 0.0
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <PC Speaker>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <PC Speaker> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <PC Speaker> Vol: 0.0
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Aux>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Aux> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Aux> Vol: 0.0
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Mono Output Select>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Mono Output Select>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Mic>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Mic>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <CD>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <CD>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Video>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Video>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Aux>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Aux>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Line>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Line>
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Mix>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Mix>
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Mix Mono>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Mix Mono>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Phone>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Phone>
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Capture>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Capture>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Capture>
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <IEC958 Playback AC97-SPSA>
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <IEC958>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <IEC958> Unmute
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <IEC958>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <IEC958>
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Analog to IEC958 Output>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Analog to IEC958 Output> Unmute
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Channel Mode>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Channel Mode>
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Duplicate Front>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Duplicate Front> Unmute
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Exchange Center/LFE>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Exchange Center/LFE> Unmute
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <External Amplifier>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <External Amplifier> Unmute
onEvent: SoundCard -- MixerElementAttach [NVidia nForce2] <Swap Surround Slot>
onEvent: SoundCard -- MixerElementChange [NVidia nForce2] <Swap Surround Slot> Unmute
Hmm... I see a few problems. First of all what application does the back button not work in?
Secondly... it says that it can't connect to X11 which means basically gizmod won't work. I can't imagine why this would be.
Are you running in X mode?
Got it working! I'm not exactly what combination of events I just did managed to make it work, but it works now. I still don't see the OSD for volume adjustments, but it works nonetheless. And somehow the Back/Exit button now works as well.
Something I did notice was that I had 3 different lircd.conf files stored into the 1 file (ie it listed 3 different sets of data), so I cleaned that up, changed the keyboard shortcut in Ubuntu and made the Gizmod script hit that shortcut and it works now. See below:
elif Event.Button == "Vol+":
Gizmod.Keyboards[0].createEvent(GizmoEventType.EV_KEY, GizmoKey.KEY_UP, [GizmoKey.KEY_LEFTCTRL])
return True
Everything *seems* to be working now. I will keep you posted as anything else arises.
Tim, thank you for your help and support through all of this, I couldn't have otherwise. You've got a nice little app going here and I will certainly recommend it to anyone I come across looking to install MythTV. Thanks again!
Great to hear, and thanks!
Keep me posted. If you run into any more issues, or come up with any sweet gizmod config hacks!
Tim.