[16:32] <tanjeff> Hi. I just installed mythbuntu 10.10 and have it basically running, except for the remote control.
[16:33] <tanjeff> I use the Nova-T card as remote, and when I press buttons, I get keystrokes, even without lircd running.
[16:34] <tanjeff> The problem is that 50% of the buttons don't generate keypresses (I look at it with xev) and that I don't get any lirc events (irw doesn't show any output)
[16:36] <tanjeff> I just don't understand how things works. I'm used to lircd and don't know why keyboard events are being generated...
[16:37] <tanjeff> ...and why no lirc events are being generated at all, not even for the "working" buttons.
[16:41] <mrand> tanjeff: remote support was pulled into the linux kernel, I believe including the kernel that comes with 10.10
[16:42] <mrand> there is a way to suspend the kernel remote support though, so you can revert to lirc if need be
[16:46] <tanjeff> I see.
[16:46] <tanjeff> Well, I would like to use the kernel support (in fact I would like to go go the easier way ;-)).
[16:47] <tanjeff> Is there a way to configure the remote somehow, so that the missing buttons start to work?
[16:47] <tanjeff> Or, can you give me a link to some documentation or something?
[16:48] <mrand> I'm trying to find something... not having much luck thus far.  If you can stay online for a while, superm1` might know.
[16:49] <mrand> One thing:  "echo -rc-6 > /sys/.../protocols" will turn off the in-kernel rc6 decoder
[16:49] <tanjeff> No, problem, I can wait for a while.
[16:53] <tanjeff> mrand: found ./devices/pci0000:00/0000:00:1e.0/0000:03:00.2/rc/rc0/protocols, but writing to it fails with "bash: echo: write error: Invalid argument"
[16:55] <mrand> tanjeff: I had hoped to play around with this on my test machine over the past several months, but work has preempted that - so unfortunately I'm still running 10.04
[16:58] <tanjeff> As far as I see, lirc was basically moved into the kernel. Seems not be rocket science, after all.
[17:04] <mrand> tanjeff: yeah, jarod is in charge of both, and they want the transition to be as seemless as possible.  lirc-mceusb to become mceusb, etc.
[17:11] <tanjeff> mrand: next problem, I'm sorry. My mythtvfrontend says "database has a newer TC schema (1264) than expected (1254)"
[17:11] <tanjeff> Is there an easy way to re-init the database or so?
[17:12] <tanjeff> I have no recordings to loose
[17:13] <tanjeff> And I touched nothing, of course ;-)
[17:20] <qwebirc81171> !help
[17:20] <Zinn> !help For a  complete list of my knowledge visit: http://www.baablogic.net/Zinn.cgi  Other available commands: !status, !about, !bug [bug_number].
[17:21] <Lachdanan> Hi Any/Everyone
[17:26] <mrand> tanjeff: hrm.  that shouldn't be necessarily.  I'd just make sure everything is updated to the latest 0.24-fixes from the PPA
[17:27] <tanjeff> Oh dear, I'm quite a newbie at mythbuntu. I just updated my system using synaptic. Do I need additional repositories?
[17:28] <tanjeff> BTW, my version is 0.23.1+fixes26437-0ubuntu1
[17:34] <Lachdanan> I'm running (or trying to run) a brand new installation (i've just reinstalled it for the 5th time) of Mythbuntu 10.10 with a Hauppauge 1300 tv tuner card.  And do I have some problems!  The most recent one is that when I try and click on WATCH TV to see if my channel setup actually worked this time, I get:  "Could not connect to the master backend server - is it running?"  The IP address under GENERAL in the Backend setup i
[17:36] <tanjeff> mrand: Found the mythbuntu-repos package. I didn't know about it before. Now upgrading to 0.24...
[17:37] <mrand> tanjeff: sorry - was away.  That's what you want - it's got numerous bug fixes
[17:38] <mrand> Lachdanan: Is message was too long and was cut off after GENERAL.  Is your backend running?  Also check your /var/log/mythtv/mythbackend.log for any warnings/error/messages.
[17:38] <mrand> Gotta run for now
[17:38] <tanjeff> The thing I mostly fear are updates - I have a wife sitting in front of the box and expecting things to work ;-)
[17:38] <Lachdanan> Further to that, when I try running "mythbackend" from terminal I get:  Failed to bind port 6543.  Exiting"
[17:39] <tanjeff> mrand:  thanx for the help
[17:39] <Lachdanan> mrand:  i am a TOTAL linux novice and got mythbuntu after a friend recommended it - and I'm slowly wanting to tear my hair out - but now I am intrigued :(
[17:40] <Lachdanan> If you'd be willing to assist, and you can give me a time when you'd be back I would really appreciate assistance
[17:41] <mrand> Lachdanan: others people on the channel should be able to help over the course of the day.  you don't normally launch mythbackend by yourself... instead, it is launched as a background "service"  If you don't already have it, make sure you try out mythbuntu-control-centre
[17:42] <Lachdanan> mrand, i know, i've killed it from terminal and tried starting it to see if it'd "go" - but it obviously doesnt
[17:42] <Lachdanan> i do have the control centre and when i try the TEST button on the SQL tab, it tests OK
[17:44] <tanjeff> Hm, updated to 0.24, now mythfrontend wants to update my database schema from 1032 to 1038. I didn't do it yet, and TV works now.
[17:44] <tanjeff> Is it a good Idea to update?
[17:45] <mrand> tanjeff: yes, that's normal.   Lachdanan: sudo service mythtv-backend start is how you launch it.
[17:45] <mrand> Ok, off like a prom dress.
[17:45]  * mrand away
[17:46] <Lachdanan> lemme try
[17:47] <Lachdanan> nope, same error when trying to WATCH TV
[17:47] <Lachdanan> I'm quickly going to put the mythbuntu pc online - will be back shortly
[18:32] <Lachdanan> Im back
[19:01] <Bennage> Hi all...
[19:01] <Bennage> Can Mythbuntu use a Blu-ray drive?
[23:25] <thunwind> hi all, I just upgraded from 0.23 -> 0.24, ran myth-setup on BE and am trying to connect my FE using MCC, but I can't get past mysql security pin (0000 check via BE/mysql and mythtv-setup)