[01:35] i can send you my lircrc, i have modified it a little [01:35] tazgodx, no use sending it to me. file a bug against mythbuntu lirc generator === directhex has lost all his recordings, suggests completely removing JFS support from mythbuntu to save other poor unfortunates [01:35] i will lose these kidns of things otherwise [01:36] ruh oh? [01:36] directhex, what happened? [01:36] directhex: JFS or XFS are the recommended types.. [01:36] Daviey, well, unrecommend JFS! [01:36] What happend? [01:36] superm1, random glitch caused my /data/MythTV folder to become eaten by a grue [01:37] yikes. [01:37] freaking grue's. :( [01:37] where do i file bug reports again? [01:38] either launchpad.net/mythbuntu or launchpad.net/ubuntu/+source/mythbuntu-lirc-generator [01:38] unfortunately, retard that i am, i forgot to check /lost+found before doing some database spring cleaning [01:39] so i have 210 files without proper filenames, about 50% of those have "target" filenames i'm trying to determine from file creation/modify dates. the rest i need to rebuild DB entries [01:39] it's only 210 things to do by hand \o/ [01:41] so lesson of the day is that we stay away from jfs and reiserfs then eh? [01:41] reiserfs is just bad, period [01:41] XFS is what i recommend [01:44] hi ho, hi ho, renamin' rcn's we go [01:44] doode doode dooo doode doodeedee [01:44] hi ho, hi ho hi ho hi ho! [01:44] i'll stick with XFS from now on. format speed be damned [01:44] should've trusted sgi before ibm [01:45] Oct 15 07:36:04 localhost kernel: [1059800.146483] ERROR: (device sda3): DT_GETPAGE: dtree page corrupt [01:45] that was if. after that, all downhill [01:51] anyone know how i can change which input i am watching? i have 3 inputs now, and just curious how i can switch from my analog to my digital cable input [01:54] tazgodx, that would be the Y key. You can also select which channel your watching (and depending on the setup, the tuner) from the guide [01:55] from the guide you say huh? [01:59] yep [01:59] depending on the setup === frank_ [n=frank@CPE000d88f1925d-CM000a73668bc0.cpe.net.cable.rogers.com] has joined #ubuntu-mythtv === MythbuntuGuest96 [n=Mythbunt@24-155-14-187.dyn.grandenetworks.net] has joined #ubuntu-mythtv [02:09] hmmmm, how to map that to a key on my remote...just which one... === MythbuntuGuest96 is now known as superNoob [02:10] hello [02:10] *now [02:11] ok someone showed me how to edit a file but when i rebooted it came back. it was sudu nano x11/xconfig?? or something i edited the file and and it works..how do imake it prermanant [02:12] hellO? [02:13] superNoob, you need to remember were not paid to be in this channel [02:13] so we don't sit here eagerly waiting for a question [02:13] oho [02:13] ohh sorry. [02:14] it would have been [02:14] /etc/X11/xorg.conf [02:14] and you should have used sudo to edit it right [02:14] right. [02:15] Do you know why the line came back? after rebooting? [02:15] so what exactly do you mean it came back? [02:15] what line? [02:15] i deleted line virual 1400 .. because my monitor screen moves with mouse [02:16] hmm [02:16] well it came back because something else put it back there [02:16] or because you didn't sudo [02:17] it started when i changed my video driver. [02:18] do you think it is set wrong? [02:18] well i dont' know what virual 1400 does [02:18] me either [02:23] okay, 97 recordings fully recovered [02:23] 111 recordings partially recovered [02:24] dealing with the partials is a job for another day [02:26] anyone have any bright ideas for how to find out why a box is randomly locking up lately? [02:26] check syslog maybe [02:26] what has changed [02:27] well it was doing it randomly before I upgraded to gutsy [02:27] I thought it was from installing kismet, so I removed that and thought it was ok [02:27] but I came home just now to find it locked up and not recording how I met your mother [02:27] :( [02:28] I am currently upgrading the slave backend to gutsy, not that I would think that would do it [02:28] I suspect it might be a hard drive issue, the one drive makes noise sometimes [02:29] could very well be [02:29] its the drive that the OS is on too none the less [02:29] well just make sure your database is ok [02:29] and backed up [02:30] ya [02:30] I have a backup (on the same drive), I should move it somewhere else [02:30] any ideas how you would go about checking a drive for errors? [02:30] yes if the drive fails your screwed [02:30] SMART? [02:31] I'll have to reboot and see if it is enabled [02:31] that or maybe a filesystem check [02:32] but i dont know how deep that check would go [02:33] hmmm, gonna have to boot with a live cd to check it [02:34] that is gonna be a pain in the ass with it only hooked up to a tv [02:34] why do you need live cd? [02:34] WARNING!!! Running e2fsck on a mounted filesystem may cause [02:34] SEVERE filesystem damage. [02:34] that [02:34] ah [02:34] that is true [02:34] damn, db backup is almost 60 megs [02:35] That is one thing that usually doesn't get checked often on mythtv systems [02:35] since it's set to do it like every 30 times [02:35] ya [02:35] and it only reboots when something gets busted [02:35] or there is a kernel update [02:38] I wonder if it might have to do with deleting not happening soon enough for recordings to save === frank__ [n=frank@CPE000d88f1925d-CM000a73668bc0.cpe.net.cable.rogers.com] has joined #ubuntu-mythtv [02:44] Im trying to folow some directions written for Fedora.. what is Sysconfig called on Ubuntu? [02:45] what does sysconfig do on fedora [02:45] if it opens the terminal in gnome, then the command is gnome-terminal [02:45] here's the refrence [02:46] In /etc/init.d/irblaster, replace every instance of "lircd" by "irblaster". Then put this into /etc/sysconfig/irblaster: === tgm4883 shrugs [02:48] tgm4883: I have an annoyance for you that you just might know the answer too [02:48] k [02:48] 42 [02:48] nopoe [02:48] *nope [02:48] wrong answer [02:48] can we try again? [02:48] 42 is never wrong [02:48] this time with me asking first? [02:48] :) [02:48] 28 [02:48] it's the i ching [02:48] ok shoot [02:49] I have my mythtv keeping it's recordings on a network storage [02:49] it's done it before without problems [02:49] this time though, and every time with mythbuntu that is, the lockfile is never removed [02:49] I manually make sure that there is no lockfile, startup myth-backend, and everything works === rhpot1991 runs memtest to be sure [02:50] I close/stop mythbacked and the lockfile doesn't get deleted [02:50] this makes it so that the next time mythbackend is started, it crashes out because there is already a lockfile, thus it thinks it's already running. [02:51] I've already checked and made sure that the network storage is being mounted read/write, and it is, because from the backend server I can remove the file without problems [02:51] when you stop it, do you verify that it actually stopped? [02:51] so I thought maybe that user couldn't delete it... [02:51] well... when I tell it to stop a 2nd time it says that no pid found [02:52] ok [02:52] how about a restart when running, does that work? [02:52] ok, so my next thought [02:52] was that the mythtv user couldn't delete the file [02:52] so I su'd to the mythtv user and removed the file without problems [02:52] so now I'm lost :) [02:52] restart does the same thing [02:52] same thing as in doesn't work? [02:52] it stops it, doesn't delete the lockfile, and then it says it starts, but it doesn't [02:53] ok [02:53] (it starts, but then crashes due to lockfile) [02:53] what are the permissions on that lock file? [02:53] and what kind of share is this? [02:53] -rw-r--r-- 1 1003 nogroup 0 2007-10-15 18:20 nfslockfile.lock [02:53] samba share [02:53] mounted via fstab [02:53] using the cifs protocol [02:54] here's the mount line for that mount: //192.168.200.15/risk /data/nas-mounts/risk cifs username=tvmyth,password=mythtv 0 0 [02:54] is tvmyth the default user on the main system [02:55] tvmyth is a user I made up for the share [02:55] it's not used anywhere else except for this share [02:55] nas is debian [02:55] backend is mythbuntu rc [02:55] k [02:56] so on the backend, you have it mounted at /data/nas-mounts/risk [02:56] right [02:57] and you are able to (on the backend) go into /data/nas-mounts/risk and remove the file? [02:58] and it worked, but then you reinstalled and now it doesn't? [02:59] is all this correct? [03:00] sorry, was registering a blueprint [03:01] yes and no [03:01] yes it's mounted there [03:01] yes, by going there, I can remove the file [03:01] but I never reinstalled... [03:01] hmm [03:01] what changed? [03:01] it's always been like this [03:01] mythbuntu has always been like this [03:02] previously I was running fedora as my backend, and it worked then [03:02] between the two I ran feisty as a backend, but I never really got that functional, so I don't know [03:02] (wasn't functional due to my tuner problems, nothing to do with this) [03:03] but this has worked on before on the current installations on both the backend and NAS? [03:03] same installation of the NAS [03:03] it has never worked with this installation of the backend [03:03] thus the problem [03:03] but [03:03] but I never reinstalled... [03:04] ^^ your quote [03:04] yes [03:04] exactly [03:04] I was working when fedora was my backend [03:04] now that machine has been molested, and is now mythbuntu [03:04] and while mythbuntu, it has never worked [03:04] how do you go from fedora to mythbuntu without reinstalling? [03:04] ugh [03:04] im so confused [03:04] by formatting :) [03:04] lol [03:05] I've never reinstalled.. [03:05] reinstall means that I install the same as before [03:05] I didn't... [03:05] ohhh [03:05] I formatted and installed mythbuntu [03:05] I get it now [03:05] ok [03:06] now, mythbuntu works great when setup to use a local dir as the recording source [03:06] but when it's using the nas, I have this problem [03:06] ok [03:06] oh, one other thing [03:06] the recording dir is actually in /data/nas-mounts/risk/mythtv/recordings [03:07] ok i figured as much [03:07] but that's long... and only the recordings are there, the videos are somewhere else on the nas, the music is somewhere else, etc [03:07] did it work with the feisty backend? [03:07] so I have each symlinked [03:07] /data/mythtv/recordings [03:07] that's where I actually have my recordings set to [03:08] with a symlink for music, videos, pictures, etc all in that mythtv dir too [03:08] just to have them all together [03:08] shouldn't matter, but just wanted to say it [03:08] ok makes sense [03:08] did the feisty backend work or did you even try? [03:08] I never got my tuner working in feisty, so the backend wouldn't start because of that [03:08] ok [03:10] so I'm quite confused... [03:10] is the backend running as the same user as you are logged in? [03:10] the path for the backend lockfile is /data/mythtv/recordings/nfslockfile.lock [03:10] I can delete that no problems manually, but the backend closing can't...... that just doesn't make sense to me... [03:10] I start it via the init.d script [03:11] im not sure [03:11] see my problem? :) [03:11] the first thing that jumped out at me was user-id's [03:12] making sure those matched up properly, but you can delete the file manually so i dont know [03:13] yeah, well, the user-id gets screwed up because it's a samba share... [03:13] it automatically gets changed to being owned by nobody === Tari__ [n=Tari@CPE-72-133-204-1.wi.res.rr.com] has joined #ubuntu-mythtv [03:21] Im going to have to give up on making Lirc work correctly with UbuntuMyth unless I can get some good help with it.. [03:22] which means I need to give up on UbuntuMyth since I can't record anything correctly with out Lirc [03:23] are you blasting or receiving? [03:24] I am trying to send a single with the USB Uirt to the Dish Satalite [03:24] ah [03:24] I've probably changed my configs so much around I'd need to reinstall Lirc at this point [03:24] because im desperate after so many days of dicking with it.. I even tried a Fedora howto.. but it doesn't work either [03:25] next step is move to fedora and try it [03:25] the last thing I wanted to do was abandone UbuntuMyth cause I really dig it [03:26] Im just thinking after a week if it dont work.. drop it type thing.. [03:26] perhaps superm1 could shed a little light on sysconf [03:26] Im hoping in future versions things like this will be supported either in documents or even better [03:26] solarbaby: have you tried totally removing the lirc config and starting over with a Uirt howto? [03:27] wait [03:27] is that from home-electro ? [03:27] MitoTranin: is what? [03:27] nm [03:28] MitoTranin: I followed this manual http://guillaume.filion.org/blog/archives/howto/ [03:28] I thought you were talking about a device I had [03:28] didn't help me at all [03:28] but it's a different device [03:28] ah [03:28] solarbaby: does your uirt get detected properly even? [03:28] is it listed in lsusb ? [03:29] I think it does [03:30] think? [03:30] whats the command? [03:30] if it doesn't get listed there, you have no hope of it working until it does [03:30] ..... lsusb [03:31] Bus 002 Device 002: ID 0403:f850 Future Technology Devices International, Ltd [03:31] that lists (thus ls) all the usb devices detected on the system (thus usb) [03:31] Bus 002 Device 001: ID 0000:0000 [03:31] Bus 001 Device 002: ID 046d:c508 Logitech, Inc. [03:31] Bus 001 Device 001: ID 0000:0000 [03:31] I dont see it [03:31] but I have seen it before [03:31] yeah, it's the first one [03:32] 0403:f850: [FTDI] [USB-UIRT] [03:32] same ID [03:32] different description [03:32] mine might be an older device [03:33] its not the USB UIRT 2 I think its just the USB UIRT [03:33] that might be your problem [03:33] are the drivers you're using for your version? [03:33] it does fine with sending when using GBPVR but I want myth [03:33] Yeah.. they are [03:34] gbpvr is windows though, so totally different [03:34] that just proves that the device itself works :) [03:34] true.. and like I said i want myth [03:34] yup [03:34] though this is always a good thing to know :0 [03:35] I've been wanting to run myth forever.. and I thought I and Myth were both ready for eachother [03:35] hehe [03:36] did you check this out: https://help.ubuntu.com/community/Lirc_USB-UIRT [03:38] solarbaby: gotta run for a bit... good luck, and I'll be back in a while! [03:41] thanks === Wy|laptop [n=wy@c-24-21-162-35.hsd1.or.comcast.net] has joined #ubuntu-mythtv [03:53] superm1: I am failing [03:53] with what? [03:53] superm1: lirc [03:53] what's wrong with lirc? [03:54] superm1: I've tried for days now to make it work.. cause with out it mythtv doesn'tt function [03:54] solarbaby, what lirc device? [03:54] superm1: usb uirt.. [03:54] have you seen https://help.ubuntu.com/community/Lirc_USB-UIRT [03:54] yup.. it doesn't give enough info [03:55] well is lircd not running when your done? [03:55] or what's happeneing [03:55] are you seeing the ttyUSB0 made? [03:55] it starts [03:55] yup [03:55] now what? [03:55] okay and so you have the right lircd.conf in /etc/lirc? [03:55] I found one for dish network and I put it in [03:55] it loads with out error [03:56] okay [03:56] so you are trying to do ir transmitting right? [03:56] yup! [03:56] okay so the syntax to send a button should just be like this [03:56] irsend -d /dev/ttyUSB0 SEND_ONCE BUTTON [03:56] does that work for you? [03:57] er [03:57] no that's wrong [03:57] irsend: Connection refused [03:57] i just checkjed the man page [03:57] it should be [03:57] irsend -d /dev/lircd SEND_ONCE BUTTON [03:57] where BUTTON is the button you're trying to send [03:57] my mistake [03:57] ok so I'll replace button with power [03:59] superm1: root@mythpvr:/usr/local/bin# irsend -d /dev/lircd SEND_ONCE power_on [03:59] irsend: not enough arguments [03:59] solarbaby, oh it appears irsend wants the remote name too [03:59] try it like this [03:59] irsend -d /dev/lircd SEND_ONCE REMOTE BUTTON [04:00] superm1: root@mythpvr:/usr/local/bin# irsend -d /dev/lircd SEND_ONCE dish info [04:00] irsend: command failed: SEND_ONCE dish info [04:00] irsend: transmission failed [04:02] hm. [04:03] have you tried to siwtch it over between uirt2_raw and uirt_raw? [04:04] *usb_uirt_raw [04:04] superm1: nope [04:04] solarbaby, you might consider modifying your lircd.conf for that to see [04:04] *hardware.conf [04:04] man i cant type today [04:04] superm1: ok === Wy_ [n=wy@c-24-21-162-35.hsd1.mn.comcast.net] has joined #ubuntu-mythtv [04:09] I changed it but I still get connection refused [04:09] well if you get a connection refused, it sounds like the other driver was the right one [04:09] can you test receiving buttons with this receiver too? [04:09] with IRW? I'll try [04:11] irw loads and takes control of the screen, but it does not report any button presses from any of my 4 remotes sitting next to me [04:12] and the dish network remote doesn't even make the usb uirt led glow like most of the other remotes do [04:12] do you have the other remote's lircd.conf's listed? [04:12] no.. just the dish network [04:13] well if the red led doesnt light up, i'd say you need to make sure that your dish remote is even working in the first place [04:13] in all interest of fairness.. in another life time I installed UbuntuMyth with Lirc Hauppauge 350 Remote turned on, and it worked.. but this time I left it off at install because I am only interested in being able to access dish network and turn channels [04:14] it works [04:14] my xbox remote also doesn't make the led flash [04:14] i see [04:14] so its only sensitive to certain frequencies [04:15] what you want to do is make sure that you have the uirt working [04:15] with any remote then [04:15] yeah.. but the device is totally capable of doing this freq, its just the software isn't doing it [04:15] add a lircd.conf for another one in [04:15] and get it to receive [04:15] then worry about transmitting [04:15] i say [04:15] sounds most logical [04:16] I've made it work with the Hauppage before, well default install of Myth made it work before [04:16] course that was never going through the usb uirt, that was going through the hauppage tuner card [04:16] yeah [04:16] Hmm [04:16] this usbuirt is a different beast [04:16] i haven't used one myself [04:16] it was nearly $60 [04:17] well for that much $ you'd hope it'd work :) [04:17] and it worked great when I was using SageTV and GBPVR, but like I said before I want myth [04:18] solarbaby: did you try uninstalling lirc and following that ubuntu guide for it? [04:19] yeah.. I think I followed it right [04:19] wait a minute [04:19] you aren't using a compiled lirc package?? [04:19] apt-get install lirc [04:19] okay good [04:19] ;) [04:20] yeah there wasn't hardly anything to that guide.. [04:22] yeah... which is why it sounds pretty simple to me... [04:23] superm1: good news.. Hauppage remote works great using IRW when connected through the UIRT [04:23] solarbaby, okay that's a good sign then [04:23] solarbaby, try sending a hauppauge key through irsend [04:23] to rule out troubles in your dish lircd.conf [04:24] sorry.. I dont know how? [04:24] grab a digital camera [04:24] and point it at your ir transmitter [04:24] and then issue a similar command as before [04:24] that you used to send a dish info key [04:24] but send a hauppauge key instead [04:24] Oh [04:25] i've gotta run [04:25] i'll be back later on [04:25] superm1: thanks buddy [04:26] superm1: it sends with hauppage === Alowishus [n=jpenix@fwsdo.projectdesign.com] has left #ubuntu-mythtv [] [05:01] solarbaby, okay back from my meeting [05:01] solarbaby, so that means something is wrong with that lircd.conf you have for dish [05:03] superm1: it sends now with dish too but it doesn't control my box [05:03] what was wrong with the sending before? [05:03] superm1: and when i use irw it doesn't respond to my dish remote.. [05:04] solarbaby, you need to try a different (but similar) dish remote lircd.conf it sounds like then [05:04] superm1: maybe it was the script I was use lircd.conf [05:04] superm1: i agree.. I've used every single one I could find [05:05] solarbaby, have you come across anyone who claims this to work (dish) with usb uirt on linux in your searches? [05:05] superm1: no actual people.. jsut some forums [05:05] superm1: i'll restart the search [05:06] well the forums are authored by people [05:06] so i mean you've come across evidence that it should work at least === MythbuntuGuest35 [n=Mythbunt@24-155-14-187.dyn.grandenetworks.net] has joined #ubuntu-mythtv [05:08] hello [05:08] $hello [05:09] when i rip a dvd where do i go to see it [05:10] in your videos directory [05:10] for mythvideo [05:10] the size of the file? [05:11] what do you mean the size? [05:12] the size of the ripped dvd [05:13] oh that depends on the options you chose [05:14] hmm [05:14] why? [05:14]