16
Developers / Re: Final Release of 1.1?
« on: August 07, 2007, 04:15:40 pm »
Thanks, will grab it when I get home from work. Hopefully if not already the SVN is available as well. Sweet. Great job programmers!
News:
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
LinuxMCE sponsor
open.home.automation
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
17
Developers / Re: Final Release of 1.1?
« on: August 05, 2007, 10:53:46 pm »
You and me both! 
Not that I will know what to do with most of it heh, but I need it to make some changed to some stuff.
Not that I will know what to do with most of it heh, but I need it to make some changed to some stuff.
18
Installation issues / Re: Installation failed, running mythtv-setup
« on: August 05, 2007, 10:53:04 pm »
So clicking on Computing doesn't bring up the option to run Mythtv-Setup? That's how I have done it to setup my database?
19
Users / Re: Overwhelmed with error "Orbiter cannot register with the router"
« on: August 04, 2007, 05:44:36 am »
LMAO, I read Zaerc's message first and started to think, great we got another forum where people think they are all that. Then I read the original message, and my apologies to Zaerc for thinking that way heh. I can agree 100% that only a moron would come in and bitch about something because he doesn't understand it and blame it on everyone else!
If you don't find the answer in the Forums or FAQs or even if the answers are there and you are still a bit confused, then the least you could do is possibly ASK for help in a polite manner. Nobody is an expert. And I know you are just trying to get attention by letting us know that you aren't going to be using LinuxMCE, it really, not in the slightest way, bothers me that you are leaving. So why bother wasting your time posting that you are leaving?
Anyways, had to post, sorry, and very sorry to Zaerc for what I started to think heh.
If you don't find the answer in the Forums or FAQs or even if the answers are there and you are still a bit confused, then the least you could do is possibly ASK for help in a polite manner. Nobody is an expert. And I know you are just trying to get attention by letting us know that you aren't going to be using LinuxMCE, it really, not in the slightest way, bothers me that you are leaving. So why bother wasting your time posting that you are leaving?
Anyways, had to post, sorry, and very sorry to Zaerc for what I started to think heh.
20
Users / Re: Microsoft MCE Remote/IR Blaster
« on: August 03, 2007, 08:03:55 pm »
Do you remember those fancy little plugin wires that it came with! and the 4 jacks on the back of it heh! So ya it is a blaster, and the drivers are available in Lirc-0.8.2 I believe. I just don't know enough of how to implement it to do it.
http://www.mythtv.org/wiki/index.php/MCE_Remote
Please share if you figure something out, maybe this weekend I can start looking at it as well.
and the 4 jacks on the back of it heh! So ya it is a blaster, and the drivers are available in Lirc-0.8.2 I believe. I just don't know enough of how to implement it to do it. http://www.mythtv.org/wiki/index.php/MCE_Remote
Please share if you figure something out, maybe this weekend I can start looking at it as well.
21
Users / Re: Hauppauge Support
« on: August 03, 2007, 03:37:50 pm »
I am sure in time it will be supported, Hauppauge is pretty good about providing driver support for Linux.
I am looking into getting some PVR Cards to put in a few of my MD's to share the DirecTV Receivers onto LinuxMCE. I am guessing being as they aren't HD, etc, that probably the PVR-150's are what I need? Or is there a more recommended card? Would be sweet to get one that has the MPEG Decoder on it and output from the card, but not sure which models if any do that and if there is gonna be much benefit over just outputting from my NVIDIA. Any advice?
I am looking into getting some PVR Cards to put in a few of my MD's to share the DirecTV Receivers onto LinuxMCE. I am guessing being as they aren't HD, etc, that probably the PVR-150's are what I need? Or is there a more recommended card? Would be sweet to get one that has the MPEG Decoder on it and output from the card, but not sure which models if any do that and if there is gonna be much benefit over just outputting from my NVIDIA. Any advice?
22
Users / Microsoft MCE Remote/IR Blaster
« on: August 03, 2007, 06:05:22 am »
I know the IR rx works great and the remote, but that ir device is also a blaster, and there are drivers for it, was curious if anyone has or knows how to make it work with LMCE? Since I already have a few of these, would be great to make them control the components!
Thanks for any help.
Thanks for any help.
23
Users / Re: Logitech MX Air Mouse?
« on: August 02, 2007, 05:48:31 pm »
Heh, sorry to hear. I just think they make the better mice. Can't say I have ever had a problem with Linux support, but maybe cuz I hardly ever install the Setpoint stuff anyways, if that is what you are referring to! I just like the look of the Air Mouse more than the Gyration one, but it is pretty pricey.
24
Users / Logitech MX Air Mouse?
« on: August 02, 2007, 05:11:40 pm »
Anyone tried this mouse with LinuxMCE? I know the Gyration mouse is recommended. But this one looks pretty slick and looks like it is a similar concept. And I have always preferred Logitech Mice! They show a picture using it to control Winblows MCE. Sounds like a possibility!
25
Users / Re: Good remote for LinuxMCE?
« on: August 01, 2007, 10:50:36 pm »
Personally for ease, I like the Mickeysoft Winblows MCE Remote. The IR Blaster is supported, not sure bout the blaster part. That reminds me, has anyone gotten the blaster to work with LinuxMCE, would be nice to not have to add another device. I have drivers to make it work, just never have used them. Anyways, it is a nice little remote for what it is. I have a Wii, so thinking of trying the Wiimote thing just to see what it is like.
26
Users / Re: Things that are safe to do and not to do? Like compiling a kernel?
« on: August 01, 2007, 10:48:41 pm »
Thanks for the reply Zaerc. Ya, I have re-installed like 4 different times to test things to make sure that it all worked. So hopefully it didn't affect your system. I only tested against RC1. But anyways, let me know, am curious. Hopefully I can write better docs when the final comes out and I have access to the source.
As far as the MD's are concerned, ya I assumed I could chroot in and compile it or whatever, just didn't know how all that worked if it pulled the files from somewhere else. Will try that.
As far as the MD's are concerned, ya I assumed I could chroot in and compile it or whatever, just didn't know how all that worked if it pulled the files from somewhere else. Will try that.
27
Users / Re: Things that are safe to do and not to do? Like compiling a kernel?
« on: August 01, 2007, 03:49:01 pm »
Well did finally get time to try out a remote MD last night. I love it heh. But anyways, my hack definately as thought doesn't update the diskless boot stuff. Anyone know what the proper steps would be for doing that, so that the new libraries and such match?
Thanks
Thanks
29
Users / Re: Things that are safe to do and not to do? Like compiling a kernel?
« on: August 01, 2007, 05:59:31 am »
Here is the wanna be howto I made for how I got the latest MythTV SVN on the system. It is a very crude hack for now, but will get anyone going hopefully if there is a need to run the latest. Once 1.1 comes out, I will hopefully be able to get ahold of the sources and do this properly, and once done, will add a proper howto to the Wiki. Thanks for all that helped.
http://forum.linuxmce.com/index.php?topic=1981.0
Hooch
http://forum.linuxmce.com/index.php?topic=1981.0
Hooch
30
Users / Updating MythTV with the latest SVN Howto
« on: August 01, 2007, 05:58:10 am »
Until I can get the SVN Sources, once 1.1 comes out hopefully, I am not gonna waste time on a wiki, due to ideally it will all change and be PROPER. This is more of a crude hack to make it work. Mind you, it ideally should be safe, but it isn't proper. Proper would be to take the dependencies for the dummy packages I have you make below and remove them from the source requirement. Anywho, for those that might want it, here is how I upgraded Myth to the latest SVN. Allowing you to apply any patches that might be required in your area. Let me know any questions, or if you suggest anything that might work better till we can get sources.
Step 1
Temporary Package Removal
First we need to remove some conflicting packages so that we can build the dependencies for compiling our own. We later will re-install some of these dependencies, due to the fact they are the core of LinuxMCE! Keep in mind during this time, none of your MD's will function, being as we will be taking out the DCERouter package. Again, I repeat that we will be re-installing these later. And the way we remove them won't be taking away any config files, just the binaries themselves.
So either SSH into your system, or open up another terminal by hitting CTRL-ALT-F2 or another Function Key. Once in, we remove our packages.
This should remove all of those packages without complaining about other conflicts.
Step 2
Install Dependencies
Now we will install the base dependencies for MythTV and also a package creator that we will use later to trick the system. Mind you, this isn't ALL of the dependencies needed for Myth, this just covers the Core Backend/Frontend aspect. If you have plugins that you want to install, you would have to install the dependencies for them separately just like you would with Myth alone.
This should install the base dependencies along with our package creator.
Step 3
MythTV SVN Compilation
Now we are ready to grab our SVN of Myth. This is just how I do things, you can compile in your home directory if it suits you, but this is how I was brought up, whether it is proper, is to be determined! But I always try and compile in /usr/local/src. But to do so, we need to give our local user rights to compile there. Again, this can be done without all these steps, but I believe it is proper. Someone can correct me and teach me the right way if needed, I take learning too! So first let's add our local user to some groups and change the permissions of the directories.
Substitute <username> with your local user. And to be proper, you should log out and log back in, but it isn't absolutely required. Now we need to grab the latest SVN.
I personally like to keep record of the version of SVN I grabbed for reference in case I need to look up the TRACK and see of issues. So whatever # is shown at the end of grabbing your source, I rename my directory to that as such:
Replacing ##### with the TRACK #.
Now we are ready to apply any patches you might use, and configure Myth. I won't cover patches here, being as if you are doing this, then I would hope you know what patches you need, and everyone might have different ones. So I will just show you the configure line. I haven't had time to spend on it, to find out why, but having trouble with enabling XVMC. Normally on a regular system it finds the libraries, but here, I assume they aren't installed. I might come back and update this later or when we get the source and do the wiki, I will put the proper way in then. I think the nvidia-glx-dev package needs installed. I usually do the NVIDIA Drivers by Source, so that is a different topic. And this is assuming NVIDIA, not everyone runs it! So here is how I configure it. Which mind you, is more than is needed, but it is what the default libmyth-0.20 uses, so I stuck with it for being proper. And lots of these options are default. But again, just being proper!
Now we are ready to compile and install. This is assuming everything compiled ok, which it should unless you applied some patches that might not be compatible.
Step 4
Re-Installation of previous Packages
Now that we have our SVN Installed, we need to create some DUMMY packages to fill what our pluto packages have as dependencies required. Once I get my hands on the source, we can just remove the dependencies from the source and it won't need these dummy packages. Being as we manually compiled MythTV, it covers all of these packages mostly. Except for MythWeb and MythTV-Database. But the database is already installed, and MythWeb you can install yourself if you wish. That isn't covered here.
So here is where our package creator comes into play. We just need to make a dummy blank package that gets installed just so when the pluto packages are re-installed they think we have what they are looking for. To do this, we need to create an empty Makefile, with nothing to install, and then create the package like so.
In this file, all we need is a line like such:
That is it, now save the file by hitting CTRL-X and selecting Y to keep the filename.
Now to create our package, we just do this:
It will first ask you if you wish to create package documentation. This is a dummy package with no docs, so just answer N here. Next it will ask for a description of the package. I just put in what I am going to call the package with dummy-package at the end. Then after you hit ENTER twice it will show you what it is going to do. We need to change the actual name of the package so that it matches what we need. That is usually Option 2. And hopefully it appended todays date as the Version #, and you don't have to do anything, but if it didn't then enter Option 3 to put the date in as something for a Version. That is it, once all that is entered, it should look something like:
This package will be built according to these values:
0 - Maintainer: [ hooch@dcerouter ]
1 - Summary: [ libmyth-0.20-dummy-package ]
2 - Name: [ libmyth-0.20 ]
3 - Version: [ 20070731 ]
4 - Release: [ 1 ]
5 - License: [ GPL ]
6 - Group: [ checkinstall ]
7 - Architecture: [ i386 ]
8 - Source location: [ dummy ]
9 - Alternate source location: [ ]
10 - Requires: [ ]
Enter a number to change any of them or press ENTER to continue:
Once it looks like the above, just hit ENTER to create the package, and it will install it for you. We need to do that for all of the dependencies that the pluto packages will need:
libmyth-0.20
mythtv-backend
mythtv-frontend
mythtv-common
mythtv-database
mythweb
So in order to accomplish that, once one package is built, you can just get rid of the description-pak file and repeate the steps above, changing the name to the other package names.
Once all your packages have been built and installed. Then you are ready to re-install our pluto packages.
Step 5
Reboot and MythTVSetup
Whether it is absolutely required, I don't know but it is probably best, I would reboot the system now so that it boots back up with the new Myth and re-starts the DCERouter.
Once your system has come back up, and you start the Core Services, you now need to run mythtv-setup You will want to do this from the Orbiter. Once it is running, you will need to go into General and possibly change the Database Password to match what is in your /etc/mythtv/mysql.txt file. Once that is done, it will probably exit out of the setup. And you will have to re-run it if you need to make any changes that are necessary. Once you exit out, I also had to update the mysql.txt file for the mythtv user as well.
For the DBPassword, make sure it matches what is in your /etc/mythtv/mysql.txt file. Once done save the file and I believe it will restart the backend, and you should be back up and running. With your new SVN of Myth.
This didn't cover any Plugins or Themes, but there shouldn't be any issues installing them. Just configure and compile them like you normally would. And restart the backend. And I haven't gotten into LinuxMCE enough yet to know what might have to be done so that your remote MD's will reflect the new Myth. I think ideally it copies the files from your Core, so hopefully nothing, but maybe someone else can chime in there, till I get time to set one up.
Hopefully that helps someone. Like mentioned above, once 1.1 goes final, and they hopefully release the SVN Sources of all the modules, then maybe we can do this properly instead of basically hacking it to work. Let me know if there is anything you see that should be done better. I am not ashamed to say I sure as hell don't know everything. I can just usually hack at things to make them work! DANGEROUS!
Take care
Hooch
Step 1
Temporary Package Removal
First we need to remove some conflicting packages so that we can build the dependencies for compiling our own. We later will re-install some of these dependencies, due to the fact they are the core of LinuxMCE! Keep in mind during this time, none of your MD's will function, being as we will be taking out the DCERouter package. Again, I repeat that we will be re-installing these later. And the way we remove them won't be taking away any config files, just the binaries themselves.
So either SSH into your system, or open up another terminal by hitting CTRL-ALT-F2 or another Function Key. Once in, we remove our packages.
Code: [Select]
sudo apt-get remove libmyth-0.20 libmyth-0.20-dev mythtv-backend mythtv-frontend mythtv-common mythtv-database mythweb pluto-mythtv-player pluto-mythtv-plugin pluto-dcerouterThis should remove all of those packages without complaining about other conflicts.
Step 2
Install Dependencies
Now we will install the base dependencies for MythTV and also a package creator that we will use later to trick the system. Mind you, this isn't ALL of the dependencies needed for Myth, this just covers the Core Backend/Frontend aspect. If you have plugins that you want to install, you would have to install the dependencies for them separately just like you would with Myth alone.
Code: [Select]
sudo apt-get build-dep mythtv
sudo apt-get install checkinstallThis should install the base dependencies along with our package creator.
Step 3
MythTV SVN Compilation
Now we are ready to grab our SVN of Myth. This is just how I do things, you can compile in your home directory if it suits you, but this is how I was brought up, whether it is proper, is to be determined!
But I always try and compile in /usr/local/src. But to do so, we need to give our local user rights to compile there. Again, this can be done without all these steps, but I believe it is proper. Someone can correct me and teach me the right way if needed, I take learning too! So first let's add our local user to some groups and change the permissions of the directories.Code: [Select]
sudo adduser <username> src
sudo adduser <username> staff
sudo chown <username>:src /usr/src
sudo chown <username>:staff /usr/local/srcSubstitute <username> with your local user. And to be proper, you should log out and log back in, but it isn't absolutely required. Now we need to grab the latest SVN.
Code: [Select]
mkdir /usr/local/src/mythtv.cvs
cd /usr/local/src/mythtv.cvs
svn co http://svn.mythtv.org/svn/trunk/mythtv
svn co http://svn.mythtv.org/svn/trunk/mythplugins
svn co http://svn.mythtv.org/svn/trunk/myththemes
svn co http://svn.mythtv.org/svn/trunk/themesI personally like to keep record of the version of SVN I grabbed for reference in case I need to look up the TRACK and see of issues. So whatever # is shown at the end of grabbing your source, I rename my directory to that as such:
Code: [Select]
mv mythtv mythtv.#####Replacing ##### with the TRACK #.
Now we are ready to apply any patches you might use, and configure Myth. I won't cover patches here, being as if you are doing this, then I would hope you know what patches you need, and everyone might have different ones. So I will just show you the configure line. I haven't had time to spend on it, to find out why, but having trouble with enabling XVMC. Normally on a regular system it finds the libraries, but here, I assume they aren't installed. I might come back and update this later or when we get the source and do the wiki, I will put the proper way in then. I think the nvidia-glx-dev package needs installed. I usually do the NVIDIA Drivers by Source, so that is a different topic. And this is assuming NVIDIA, not everyone runs it! So here is how I configure it. Which mind you, is more than is needed, but it is what the default libmyth-0.20 uses, so I stuck with it for being proper. And lots of these options are default. But again, just being proper!
Code: [Select]
cd /usr/local/src/mythtv.cvs/mythtv.#####
./configure --prefix=/usr --enable-lirc --enable-audio-alsa --enable-audio-oss --enable-audio-jack --enable-audio-arts --enable-dvb --enable-ivtv --enable-firewire --enable-joystick-menu --disable-xvmc --enable-xvmc-vld --enable-xvmc-pro --enable-mmx --enable-proc-opt --enable-opengl-vsyncNow we are ready to compile and install. This is assuming everything compiled ok, which it should unless you applied some patches that might not be compatible.
Code: [Select]
make
sudo make installStep 4
Re-Installation of previous Packages
Now that we have our SVN Installed, we need to create some DUMMY packages to fill what our pluto packages have as dependencies required. Once I get my hands on the source, we can just remove the dependencies from the source and it won't need these dummy packages. Being as we manually compiled MythTV, it covers all of these packages mostly. Except for MythWeb and MythTV-Database. But the database is already installed, and MythWeb you can install yourself if you wish. That isn't covered here.
So here is where our package creator comes into play. We just need to make a dummy blank package that gets installed just so when the pluto packages are re-installed they think we have what they are looking for. To do this, we need to create an empty Makefile, with nothing to install, and then create the package like so.
Code: [Select]
mkdir /usr/local/src/mythtv.cvs/dummy
cd /usr/local/src/mythtv.cvs/dummy
nano -w MakefileIn this file, all we need is a line like such:
Code: [Select]
install:That is it, now save the file by hitting CTRL-X and selecting Y to keep the filename.
Now to create our package, we just do this:
Code: [Select]
sudo checkinstall make installIt will first ask you if you wish to create package documentation. This is a dummy package with no docs, so just answer N here. Next it will ask for a description of the package. I just put in what I am going to call the package with dummy-package at the end. Then after you hit ENTER twice it will show you what it is going to do. We need to change the actual name of the package so that it matches what we need. That is usually Option 2. And hopefully it appended todays date as the Version #, and you don't have to do anything, but if it didn't then enter Option 3 to put the date in as something for a Version. That is it, once all that is entered, it should look something like:
This package will be built according to these values:
0 - Maintainer: [ hooch@dcerouter ]
1 - Summary: [ libmyth-0.20-dummy-package ]
2 - Name: [ libmyth-0.20 ]
3 - Version: [ 20070731 ]
4 - Release: [ 1 ]
5 - License: [ GPL ]
6 - Group: [ checkinstall ]
7 - Architecture: [ i386 ]
8 - Source location: [ dummy ]
9 - Alternate source location: [ ]
10 - Requires: [ ]
Enter a number to change any of them or press ENTER to continue:
Once it looks like the above, just hit ENTER to create the package, and it will install it for you. We need to do that for all of the dependencies that the pluto packages will need:
libmyth-0.20
mythtv-backend
mythtv-frontend
mythtv-common
mythtv-database
mythweb
So in order to accomplish that, once one package is built, you can just get rid of the description-pak file and repeate the steps above, changing the name to the other package names.
Once all your packages have been built and installed. Then you are ready to re-install our pluto packages.
Code: [Select]
sudo apt-get install pluto-dcerouter pluto-mythtv-player pluto-mythtv-pluginStep 5
Reboot and MythTVSetup
Whether it is absolutely required, I don't know but it is probably best, I would reboot the system now so that it boots back up with the new Myth and re-starts the DCERouter.
Code: [Select]
sudo rebootOnce your system has come back up, and you start the Core Services, you now need to run mythtv-setup You will want to do this from the Orbiter. Once it is running, you will need to go into General and possibly change the Database Password to match what is in your /etc/mythtv/mysql.txt file. Once that is done, it will probably exit out of the setup. And you will have to re-run it if you need to make any changes that are necessary. Once you exit out, I also had to update the mysql.txt file for the mythtv user as well.
Code: [Select]
sudo nano -w /home/mythtv/.mythtv/mysql.txtFor the DBPassword, make sure it matches what is in your /etc/mythtv/mysql.txt file. Once done save the file and I believe it will restart the backend, and you should be back up and running. With your new SVN of Myth.
This didn't cover any Plugins or Themes, but there shouldn't be any issues installing them. Just configure and compile them like you normally would. And restart the backend. And I haven't gotten into LinuxMCE enough yet to know what might have to be done so that your remote MD's will reflect the new Myth. I think ideally it copies the files from your Core, so hopefully nothing, but maybe someone else can chime in there, till I get time to set one up.
Hopefully that helps someone. Like mentioned above, once 1.1 goes final, and they hopefully release the SVN Sources of all the modules, then maybe we can do this properly instead of basically hacking it to work. Let me know if there is anything you see that should be done better. I am not ashamed to say I sure as hell don't know everything. I can just usually hack at things to make them work!
DANGEROUS!Take care
Hooch