=== zcutlip_ is now known as zcutlip
=== zcutlip_ is now known as zcutlip
=== zcutlip_ is now known as zcutlip
[17:10] <qwebirc97605> Is there a way to add mythbuntu repos / mythbuntu-control-centre to a headless ubuntu server install?
[17:10] <tgm4883> qwebirc97605, yes, which version are you looking for?
[17:11] <qwebirc97605> I'm using 12.04 and I'd like to update my mythtv to 0.26
[17:11] <tgm4883> apt-add-repository ppa:mythbuntu/0.26
[17:11] <qwebirc97605> that's quick and easy.  THANKS!
[17:11] <tgm4883> yw
[18:50] <KjetilK> Hmmm, seems like the kernel-based lirc isn't using the  ~/.lirc/mythtv config, as most of the keys of the remote isn't working
[18:50] <KjetilK> can anyone shed any light?
[19:01] <rhpot1991> KjetilK: it doesn't use the lirc configs
[19:01] <KjetilK> rhpot1991, right, so where do I set the keymaps?
[19:04] <rhpot1991> http://askubuntu.com/questions/133513/tweaking-remote-control-in-kernel-lirc
[19:04] <Zinn> [askubuntu.com] 12.04 - Tweaking Remote Control (In-Kernel LIRC) - Ask Ubuntu
[19:04] <rhpot1991> that might help
[19:04] <KjetilK> rhpot1991, thanks, I'll lok
[19:05] <rhpot1991> you can force lirc to use the dev/input devices as well
[19:05] <KjetilK> ok
[19:48] <stevew> Installed Mythbuntu 12.04, upgraded to 12.04.1, tried to use MCC to upgrade MythTV from 0.25 to 0.26.  The Update Manager sees the new repository changes, downloads the changes, but then gets stuck trying to apply the changes.   It hangs (or appears to) with the spinning black ball thing.   Should this process take a long time?
[19:49] <tgm4883> stevew, so you did the refresh, changed to 0.26, then did apply and that is where it's hanging?
[20:10] <stevew> yes, exactly
[20:15] <tgm4883> stevew, did you get a password prompt popup?
[20:15] <stevew> yes, authenticated, and then the progress bar gets about 2/3 across before it hangs.
[20:15] <tgm4883> hmm, interesting
[20:17] <tgm4883> stevew, so that shouldn't take too long
[20:17] <tgm4883> you can try running this in the terminal
[20:17] <stevew> ok.
[20:17] <tgm4883> apt-add-repository -y ppa:mythbuntu/0.26
[20:17] <tgm4883> see if that throws any errors
[20:17] <stevew> I'll need to kill the update manager.
[20:18] <tgm4883> update manager is running now?
[20:19] <stevew> Yes, it was still hanged (hung,hanging,etc...)
[20:19] <stevew> Just killed it.
[20:20] <stevew> ran apt-add-repository, that seems to have worked.
[20:20] <tgm4883> stevew, weird, as that is exactly what mythbuntu-repos is doing in the background
[20:20] <stevew> hmm.
[20:26] <stevew> I'm not a package wizard.   How do you tell with version of mythtv is installed?
[20:26] <stevew> *which version*
[20:27] <tgm4883> dpkg -l mythtv*
[20:32] <stevew> So it says I now have mythtv 2:0.26.0+fixes installed.
[20:51] <tgm4883> stevew, sweet
[20:54] <stevew> Not sure how that worked exactly.
[20:56] <Bummed>  anyone have any data on how much horse power is needed to suppport  HDHome Duals on a network ?
[20:56] <tgm4883> Bummed, what do you mean by horsepower?
[20:58] <Bummed> looking around the house at the machines that are not currently dedicated to someing
[20:58] <Bummed> I have a 2 thinkpads and a sony viao desktop
[20:59] <tgm4883> Bummed, well the HDHR's are digital tuners, meaning that the stream already comes in compressed. So for recording, you're looking at disk write speed and network bandwidth
[20:59] <Bummed> thinkpads are dual core with 4 GB of memory .. desktop is P4 with hyperthreading and 1 GB of memory
[20:59] <Bummed> think any of those would work or should I go buy a new toy :-)
[21:00] <tgm4883> those would work for recording
[21:00] <tgm4883> you could probably record with a P3
[21:00] <rhpot1991> video playback will be the most intensive operation
[21:00] <Bummed> and I do have a couple of more powerful machines that I can off hours off load commercial cutting and transcoding to
[21:01] <rhpot1991> and most people normally use an nvidia graphics card and offload that work via vdpau
[21:02] <Bummed> so for play back and intel GMA HD is a bad idea ?
[21:45] <KjetilK> so, I uninstalled lirc to rely on the kernel drivers and went through http://forum.xbmc.org/showthread.php?tid=104541
[21:46] <KjetilK> that seemed to work very nicely, but then I decided to see if I could get it up on boottime
[21:46] <KjetilK> now, I realize that something actually does come up at bootime, because some keys work in Myth
[21:47] <KjetilK> but putting the keymap in has no apparent effect on which keys work in Myth...
[21:49] <KjetilK> I have an imon and a mceusb
[21:50] <KjetilK> if I can get the latter to work, that'd be all I need
[21:51] <KjetilK> hmmm, I'm not getting any test events, but I guess the imon now tries to catch it all...
[21:56]  * KjetilK tries to blacklist imon stuff
[21:59] <KjetilK> oh, it looks like ir-keytable crashes shortly after startup
[22:20]  * KjetilK has the feeling it is just mappings from e.g. KEY_OK to keys that are missing, where do I set that in a kernel-only case?