I'm starting a project to build a MythTV box for my living room. Anyone else currently working with MythTV on CentOS 4?
Here are some of the gotcha's I've worked through so far:
- I was originally planning on using KnoppMyth. But their CD appears to be only for i386. Without realizing it, the P4 CPU I picked is one of the newer ones with the x86_64 extensions. It won't boot i386. Thus, my plan B is going with CentOS4 x86_64 and installing from the ATrpms collection. Here's someone who's already doing this:
http://umich2.com/archives/category/linux/mythtv/
- I picked up a cheap Radeon 7000 with TV out. Wrong! Various posts seem to say that the TV Out functionality is not supported by the X.org radeon driver. It *does* work with the vesa driver though. I just don't know if video and DVD playback will work with the vesa driver. Does anyone know?
- The stock RedHat kernel does *not* have irda support enabled. I downloaded 2.6.13.2, enabled irda, and my motherboard's irda port is found and configured. We'll see if I can get it to work with the IR adapter in the nMediaPC case I bought.
Kirk Bocek
Kirk Bocek wrote:
I'm starting a project to build a MythTV box for my living room. Anyone else currently working with MythTV on CentOS 4?
Here are some of the gotcha's I've worked through so far:
- I was originally planning on using KnoppMyth. But their CD appears
to be only for i386. Without realizing it, the P4 CPU I picked is one of the newer ones with the x86_64 extensions. It won't boot i386. Thus, my plan B is going with CentOS4 x86_64 and installing from the ATrpms collection. Here's someone who's already doing this:
http://umich2.com/archives/category/linux/mythtv/
- I picked up a cheap Radeon 7000 with TV out. Wrong! Various posts
seem to say that the TV Out functionality is not supported by the X.org radeon driver. It *does* work with the vesa driver though. I just don't know if video and DVD playback will work with the vesa driver. Does anyone know?
- The stock RedHat kernel does *not* have irda support enabled. I
downloaded 2.6.13.2, enabled irda, and my motherboard's irda port is found and configured. We'll see if I can get it to work with the IR adapter in the nMediaPC case I bought.
Kirk Bocek
Kirk,
I've got an X600 ATI board, and the ATI driver *does* support the TV out function as well as dual monitors in either horizontal or vertical splits. I don't use the TV-out function. I believe I recall seeing the 7000 series being supported. Might check the ATI website.
Good luck..
Sam
Unfortunately the proprietary ATI driver is only for the Radeon 8500 and up. There's another ATI driver project called Gatos. They seem to be in the process of transitioning from XFree86 to X.org. I have no idea where they are regarding CentOS.
Kirk Bocek
Sam Drinkard wrote:
Kirk,
I've got an X600 ATI board, and the ATI driver *does* support the TV out function as well as dual monitors in either horizontal or vertical splits. I don't use the TV-out function. I believe I recall seeing the 7000 series being supported. Might check the ATI website.
Good luck..
Sam
On Mon, 2005-09-26 at 14:11, Kirk Bocek wrote:
I'm starting a project to build a MythTV box for my living room. Anyone else currently working with MythTV on CentOS 4?
Have not used Centos but I do have a master backend/frontend running on FC3 and a slave backend/frontend running on FC4.
I would think the easiest way to do this with Centos would be to use the ATRPMS as a base and work from there. The other alternative is to build it from source which should not be to bad. Just use the various how to's and guides put out for FC3 as a starting point.
Jarod's guide is pretty good. Just remember to expand and read all the sections. http://wilsonet.com/mythtv/
- I picked up a cheap Radeon 7000 with TV out. Wrong! Various posts seem to say that
the TV Out functionality is not supported by the X.org radeon driver. It *does* work with the vesa driver though. I just don't know if video and DVD playback will work with the vesa driver. Does anyone know?
Been using the TV out on the PVR-350. Have been using this primarily for recording TV and playing it back. The output is spectacular. I can not tell the difference between the original broadcast show and the mythtv recording. (except that is skips over most commercials automatically of course. )
- The stock RedHat kernel does *not* have irda support enabled. I downloaded
2.6.13.2, enabled irda, and my motherboard's irda port is found and configured. We'll see if I can get it to work with the IR adapter in the nMediaPC case I bought.
Kirk Bocek
I use the remote provided by the PVR-350 which does a good job. The second system I installed this on took all of about 15 minutes to get the remote working if that much time.
If/when you get to the point of setting up a slave backend let me know, there were a couple of gotcha's that I had to work through to get that working as expected. And as far as I am concerned none of the how to's or guides really explain setting up a slave backend clearly. (I think by the time they got to setting up a slave backend they assumed a lot and knew how it all worked, those of us new to mythtv don't have that background, yet.)
Depending on the type of inputs you will be recording you will want to have at least two capture cards if not three or four. This makes conflicts less likely to occur.
Scot L. Harris wrote:
I would think the easiest way to do this with Centos would be to use the ATRPMS as a base and work from there. The other alternative is to build it from source which should not be to bad. Just use the various how to's and guides put out for FC3 as a starting point.
That's my plan. :)
Jarod's guide is pretty good. Just remember to expand and read all the sections. http://wilsonet.com/mythtv/
Yep, I've had him bookmarked for awhile.
Been using the TV out on the PVR-350. Have been using this primarily for recording TV and playing it back. The output is spectacular. I can not tell the difference between the original broadcast show and the mythtv recording. (except that is skips over most commercials automatically of course. )
My PVR-350 is coming. Are you able to run the Myth frontend on the PVR-350? I see various notes about putting DVD output and such on the 350 but what about the cosole output?
If/when you get to the point of setting up a slave backend let me know, there were a couple of gotcha's that I had to work through to get that working as expected.
When MythTV talks about the 'back end' is that simply the MySQL database or is there some other software involved?
Depending on the type of inputs you will be recording you will want to have at least two capture cards if not three or four. This makes conflicts less likely to occur.
Why two? I was planning on just one PVR-350 to begin with and maybe adding a second later. Do you know anything about the version with two tuners? I think it's the 550.
Kirk
On Mon, 2005-09-26 at 14:51, Kirk Bocek wrote:
Scot L. Harris wrote:
Been using the TV out on the PVR-350. Have been using this primarily for recording TV and playing it back. The output is spectacular. I can not tell the difference between the original broadcast show and the mythtv recording. (except that is skips over most commercials automatically of course. )
My PVR-350 is coming. Are you able to run the Myth frontend on the PVR-350? I see various notes about putting DVD output and such on the 350 but what about the cosole output?
Yes, Jarod's guide has some good info for getting X to run out the PVR-350. I run the master backend on my main TV with just the connection to the TV. As part of that setup you create a new initrd file so it switches all output to the PVR-350 early on in the boot up.
When I upgraded from .17 to .18.1 I did hookup a mouse and keyboard. But normal operation is via the remote control or via mythweb. You still have the ability to ssh into the system and you can always use vncserver on the box. BTW: I found the upgrade process to be very easy just yum install the new mythtv-suite and it takes care of all the other packages for you. Very nicely done.
I have not worked with the DVD much yet. On my todo list. :) I have read where it should be possible to run xine out the PVR-350 but it is not clear to me if the quality is going to be acceptable. Until then I use the old Apex DVD player.
My initial attempt at using the DVD was a problem as I had difficulty getting DMA enabled for the DVD drive. I think I have that resolved now but have not retried using a DVD on that system. The slave backend that I turned up last week has not been tested with a DVD yet. Possibly by next week I will get to that testing.
If/when you get to the point of setting up a slave backend let me know, there were a couple of gotcha's that I had to work through to get that working as expected.
When MythTV talks about the 'back end' is that simply the MySQL database or is there some other software involved?
There are three main parts to a mythtv system, the mysql database, mythbackend, and mythfrontend. You need ONE mysql database, it can be on any system you want but is typically on the first mythbackend system you setup. The mythbackend process runs on any system you have capture cards in. The master backend is the one with the mysql database.
Any system you want to watch recordings on you will run mythfrontend.
In most cases the first box will run all three.
The slave backends will run a mythbackend process and can run a mythfrontend process if you are using them to view recordings.
I eventually want to setup diskless frontend systems that boot from the network and only run the mythfrontend process.
Depending on the type of inputs you will be recording you will want to have at least two capture cards if not three or four. This makes conflicts less likely to occur.
Why two? I was planning on just one PVR-350 to begin with and maybe adding a second later. Do you know anything about the version with two tuners? I think it's the 550.
You want at least two so you can record two shows at once or watch live TV through the mythtv box and record a show at the same time. You don't have to have a capture card available to watch recordings.
I found that two capture cards resolved all but a few conflicts. Three gets that down to almost none and four seems to clear all conflicts so far. But then I have only had four capture cards going less than a week.
Once you get the box setup you will find that you stop watching live tv that much if at all. Virtually everything I watch is recorded any more. (just love that commercial skip capability)
Start with one capture card to get it working. Then you can easily add a second card. I installed a PVR-250 in the first box as a second card. Takes just a minute or two to add it. You just run mythtv-setup again and add the card and video source. The system then starts using it.
If you plan to use different video out such as through regular video card then the PVR-350 is probably not the card you want. The only other thing it provides is the remote control and IR receiver.
I tried a PVR-500 card in the second box. I currently have it pulled out and have a PVR-350 and PVR-250 in that box as well. I had trouble getting the drivers to work correctly with the PVR-500. Have been trying to figure out if it is a hardware problem or a driver problem. At some point I need to try it again with the 0.3.8 ivtv drivers. Currently running 0.3.7k drivers from ATRPMS. I would have left the card in the system however I found that the third PCI slot on this ECS motherboard has a capacitor that sticks up to far for the card to seat properly in that third slot. I might get all the cards in the system if I move the PVR-350 down to that slot since it does not have the red audio connector on the bottom edge of the card. Again this is something I plan to try but won't get to it until next week or the week after.
I over built the first mythtv box. Hindsight I would build a tower system with the TB of disk and run several capture cards and mythbackend on that system. Would tuck that one back in the office. I would then build diskless frontend systems for each TV. An additional backend system might be needed to get four capture cards running. But if the PVR-500 can work I would use a couple of those.
At some point I need to look at a hotswap raid system but that is way down the road. :)
Scot L. Harris wrote:
Yes, Jarod's guide has some good info for getting X to run out the PVR-350. I run the master backend on my main TV with just the connection to the TV. As part of that setup you create a new initrd file so it switches all output to the PVR-350 early on in the boot up.
Groovy! I also found several detailed instructions on getting X running on the 350. Now I can say bye-bye to the Radeon 7000 and just use the VGA that's onboard the motherboard during setup. That'll leave another slot for capture cards. UPS just showed up with my PVR-350...
I have not worked with the DVD much yet. On my todo list. :) I have read where it should be possible to run xine out the PVR-350 but it is not clear to me if the quality is going to be acceptable. Until then I use the old Apex DVD player.
I hope this works. Replacing the DVD player in the AV shelving is a primary goal for me.
There are three main parts to a mythtv system, the mysql database, mythbackend, and mythfrontend. You need ONE mysql database, it can be on any system you want but is typically on the first mythbackend system you setup. The mythbackend process runs on any system you have capture cards in. The master backend is the one with the mysql database.
Any system you want to watch recordings on you will run mythfrontend.
In most cases the first box will run all three.
The slave backends will run a mythbackend process and can run a mythfrontend process if you are using them to view recordings.
I eventually want to setup diskless frontend systems that boot from the network and only run the mythfrontend process.
Ooh, good idea! Added to Future Project list.
You want at least two so you can record two shows at once or watch live TV through the mythtv box and record a show at the same time. You don't have to have a capture card available to watch recordings.
Duh! I forgot about that scenario. Note to self - plan to get another tuner.
Start with one capture card to get it working. Then you can easily add a second card. I installed a PVR-250 in the first box as a second card. Takes just a minute or two to add it. You just run mythtv-setup again and add the card and video source. The system then starts using it.
I'm glad it's that easy.
I tried a PVR-500 card in the second box...
Too bad that's not working. But since it's easy to add cards, it sounds like I can afford to wait until support for that card settles out.
I over built the first mythtv box. Hindsight I would build a tower system with the TB of disk and run several capture cards and mythbackend on that system. Would tuck that one back in the office. I would then build diskless frontend systems for each TV. An additional backend system might be needed to get four capture cards running. But if the PVR-500 can work I would use a couple of those.
Right now I'm going to go with just the scenario you describe: everything on this one box. Already have a 'house server' in the garage providing net connection, etc. I hope to upgrade it at some point and make it the backend with a bunch of raided, hot-swap storage. Maybe do video capture too on it. Your idea to do diskless workstations is a good one. Might even be able to do something fanless!
Just did the ATrpms install of mythtv-suite. That's a lot of packages! But no errors, thankfully. We'll see how the PVR-350 works now.
Kirk Bocek
On Mon, 2005-09-26 at 16:29, Kirk Bocek wrote:
Scot L. Harris wrote:
Groovy! I also found several detailed instructions on getting X running on the 350. Now I can say bye-bye to the Radeon 7000 and just use the VGA that's onboard the motherboard during setup. That'll leave another slot for capture cards. UPS just showed up with my PVR-350...
This is exactly what I am doing with the new slave backend system. The ECS board has built in VGA which is what I am using during setup. By next week this box will be using the PVR-350 for all output. But I wanted to try and test the DVD first. :)
I have not worked with the DVD much yet. On my todo list. :) I have read where it should be possible to run xine out the PVR-350 but it is not clear to me if the quality is going to be acceptable. Until then I use the old Apex DVD player.
I hope this works. Replacing the DVD player in the AV shelving is a primary goal for me.
Me too! The Apex player I have does not like DVD-R or +R for that matter.
You want at least two so you can record two shows at once or watch live TV through the mythtv box and record a show at the same time. You don't have to have a capture card available to watch recordings.
Duh! I forgot about that scenario. Note to self - plan to get another tuner.
I assume you are just connecting the cable straight from the wall to the capture card? I find this works very well.
Start with one capture card to get it working. Then you can easily add a second card. I installed a PVR-250 in the first box as a second card. Takes just a minute or two to add it. You just run mythtv-setup again and add the card and video source. The system then starts using it.
I'm glad it's that easy.
Where it got confusing was getting the capture cards in slave backends working.
I tried a PVR-500 card in the second box...
Too bad that's not working. But since it's easy to add cards, it sounds like I can afford to wait until support for that card settles out.
I kept watching the list and it seemed that lots of people have it working. It could be a hardware problem in the card I received. Have not figured out how to test for that yet. I was able to get video and sound going on the first tuner but the second tuner just did not work. The system recognized both tuners but I was unable to adjust the various settings on the second tuner using the tools provided. I found a few people on the list reporting the same exact problem. So it may be a driver issue which why I need to eventually try the 0.3.8 ivtv drivers.
Right now I'm going to go with just the scenario you describe: everything on this one box. Already have a 'house server' in the garage providing net connection, etc. I hope to upgrade it at some point and make it the backend with a bunch of raided, hot-swap storage. Maybe do video capture too on it. Your idea to do diskless workstations is a good one. Might even be able to do something fanless!
That is exactly where I want to go with the frontend systems, fanless, silent, cool. No moving parts.
Right now the big box with the four 300GB drives in it is not to bad. I only really notice it once it finishes recording a show and runs the commercial flagging job. The processors kick in high gear and the power supply fan revs up. Almost sounds like it is rewinding the show. :)
Just did the ATrpms install of mythtv-suite. That's a lot of packages! But no errors, thankfully. We'll see how the PVR-350 works now.
Good luck, the mythtv project has got to be one of the most useful projects that have come out for a linux type system.
Scot L. Harris wrote:
I assume you are just connecting the cable straight from the wall to the capture card? I find this works very well.
Yes, I'm going to use the analog service from the cable company. We also have a digital box but I hope to get this working well enough to do away with it.
Speaking of which, is there any such beast as a *digital* cable tuner card?
Where it got confusing was getting the capture cards in slave backends working.
I believe you were going to share your gotchas in setting up the backend...
That is exactly where I want to go with the frontend systems, fanless, silent, cool. No moving parts.
<HomerVoice>Uhhhh, Fanless...</HomerVoice>
Good luck, the mythtv project has got to be one of the most useful projects that have come out for a linux type system.
Thanks.
On Mon, 2005-09-26 at 19:36, Kirk Bocek wrote:
Scot L. Harris wrote:
I assume you are just connecting the cable straight from the wall to the capture card? I find this works very well.
Yes, I'm going to use the analog service from the cable company. We also have a digital box but I hope to get this working well enough to do away with it.
That is all I am using. I dropped all pay channels a long time ago and don't really need the digital service.
Speaking of which, is there any such beast as a *digital* cable tuner card?
Not that I am aware of. The problem is that different cable companies use different equipment, no real wide used standard. The best you are going to do is to setup mythtv to use an IR blaster to change channels on the digital cable box. Have not done that here but understand that many people have set this up. Only problem is that you need a cable box for each capture card you setup for digital cable.
Actually there is another option to the IR blaster. I understand that some cable boxes come with firewire outputs that you can connect to the system. In some cases it sounds like this can be used to control channel changing. I think this is used primarily for HD recording. You would need to check the mailing list for the details. I don't expect to get into HDTV anytime soon.
Where it got confusing was getting the capture cards in slave backends working.
I believe you were going to share your gotchas in setting up the backend...
The main gotcha I ran into is that during install you end up with multiple copies of mysql.txt files on the system. You must make sure that they all are configure consistently and point to the master backend system where the actual mysql database lives.
You run mythtv-setup on the slave backend and configure things but don't setup channel lists. That is only done on the master backend system. If everything is communicating correctly you will have video listings available from the master backend.
Also when you setup the masterbackend make sure to use the actual IP address or name of the masterbackend instead of using localhost.
And if you do delete capture cards or channel listings you will need to reconfigure those on the master backend then the slave backend.
If you forget to do that you will loose scheduled recordings since there won't be any capture cards available.
Also after running mythtv-setup remember to restart mythbackend on the master and slave. You can verify things have been setup correctly by looking at mythweb's status page. It will list all of the capture cards available for use.
I also found in Jarod's guide a good trick to fix some ghosting I was getting on the slave backend. Not sure why but I had to modify the dnr_temporal options on the PVR-350 and PVR-250. Did not have to do this on the master backend just the capture cards on the slave backend. For some reason they would default to a value of 8. Setting them to 0 fixed the ghosting I was seeing.
Scot, I believe you said you were using the IR receiver on the PVR-350, right? Do you have any notes or gotcha's on getting it to work. So far, I'm having no luck.
I've got ivtv installed and have got my X session running on the PVR-350's frame buffer. Now I'm trying to get the IR receiver working but am getting no output out of irw.
I've got lirc 0.7.2 installed. I've got:
alias char-major-61 lirc_i2c
in modprobe.conf. When I modprobe lirc_i2c it whines about bttv and cx8800 (which aren't installed) then says:
lirc_i2c: chip found @ 0x18 (Hauppauge IR) ivtv: i2c attach to card #0 ok [client=Hauppauge IR, addr=18] lirc_dev: lirc_register_plugin: sample_rate: 10
So it looks like the two pieces are talking. the /dev entries seem to be correct. But I get no output at all from irw. No errors either. I even tried plugging in a second Hauppauge IR receiver into the card that I had laying around.
Do you have any ideas?
Thanks, Kirk
Scot L. Harris wrote:
Good luck, the mythtv project has got to be one of the most useful projects that have come out for a linux type system.
Kirk Bocek wrote:
Scot, I believe you said you were using the IR receiver on the PVR-350, right? Do you have any notes or gotcha's on getting it to work. So far, I'm having no luck.
I've got ivtv installed and have got my X session running on the PVR-350's frame buffer. Now I'm trying to get the IR receiver working but am getting no output out of irw.
I've got lirc 0.7.2 installed. I've got:
alias char-major-61 lirc_i2cin modprobe.conf. When I modprobe lirc_i2c it whines about bttv and cx8800 (which aren't installed) then says:
lirc_i2c: chip found @ 0x18 (Hauppauge IR) ivtv: i2c attach to card #0 ok [client=Hauppauge IR, addr=18] lirc_dev: lirc_register_plugin: sample_rate: 10
So it looks like the two pieces are talking. the /dev entries seem to be correct. But I get no output at all from irw. No errors either. I even tried plugging in a second Hauppauge IR receiver into the card that I had laying around.
Do you have any ideas?
Thanks, Kirk
Scot L. Harris wrote:
Good luck, the mythtv project has got to be one of the most useful projects that have come out for a linux type system.
Sorry, this may already have come up, but have you looked through Jarod Wilson's guide (recently updated for FC4. That may provide some additional insight...
http://wilsonet.com/mythtv/fcmyth.php
-Pete
Oh yea! I've been living by it! :)
I'm just now looking at his 'update' notes about getting the modules loaded early in the boot process. Maybe that'll help.
Kirk
Peter Loron wrote:
Sorry, this may already have come up, but have you looked through Jarod Wilson's guide (recently updated for FC4. That may provide some additional insight...
I already installed a Centos 4.0 on Server.
But when I restart the server stop and never get up again.
The last messages are this.
Md: stopping all md devices Md: md0 switched to read only mode
Any help..
Thank you
Este correo se encuentra libre de VIRUS, Gobchih
Este correo se encuentra libre de VIRUS, Gobchih
Hi, it worked for me adding acpi=off apm=on to the kernel parameters in grub.conf:
kernel /vmlinuz-2.6.9-11.EL ro root=LABEL=/ rhgb quiet acpi=off apm=on
You can also check this http://lists.centos.org/pipermail/centos/2005-August/009659.html or this http://lists.centos.org/pipermail/centos/2005-June/007465.html
Have a nice day
Carlos Arellano wrote:
I already installed a Centos 4.0 on Server.
But when I restart the server stop and never get up again.
The last messages are this.
Md: stopping all md devices Md: md0 switched to read only mode
Any help..
Thank you
Este correo se encuentra libre de VIRUS, Gobchih
Este correo se encuentra libre de VIRUS, Gobchih _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I still have this problem any help please.
I have tried many things but any works.
I already installed a Centos 4.0 on Server.
But when I restart the server stop and never get up again.
The last messages are this.
Md: stopping all md devices Md: md0 switched to read only mode
Any help..
Thank you
Este correo se encuentra libre de VIRUS, Gobchih
Este correo se encuentra libre de VIRUS, Gobchih _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Este correo se encuentra libre de VIRUS, Gobchih
Este correo se encuentra libre de virus
Este correo se encuentra libre de virus
Carlos Arellano spake the following on 2/7/2006 2:24 PM:
I still have this problem any help please.
I have tried many things but any works.
I already installed a Centos 4.0 on Server.
But when I restart the server stop and never get up again.
The last messages are this.
Md: stopping all md devices Md: md0 switched to read only mode
Do you have any details on the hardware? Is CentOS patched current? Is there a md0 device? Is it in use?
On Tuesday 07 Feb 2006 22:24, Carlos Arellano wrote:
I still have this problem any help please.
I have tried many things but any works.
I already installed a Centos 4.0 on Server.
But when I restart the server stop and never get up again.
The last messages are this.
Md: stopping all md devices Md: md0 switched to read only mode
Any help..
Thank you
Have you got a keyboard plugged in? I had the same problem - it would stop OK but only restart with a keyboard. Never could find out why.
Dave F
On 07/02/06, David Fletcher centos@fletchersweb.net wrote:
Have you got a keyboard plugged in? I had the same problem - it would stop OK but only restart with a keyboard. Never could find out why.
That would probably be a BIOS thing. Most BIOSes have a Halt On... section which can include keyboard/mouse errors. Some Supermicro board's BIOSes need to be set to Fast Boot to bypass keyboard errors.
Will.
On Tue, 7 Feb 2006, David Fletcher wrote:
On Tuesday 07 Feb 2006 22:24, Carlos Arellano wrote:
I already installed a Centos 4.0 on Server.
But when I restart the server stop and never get up again.
The last messages are this.
Md: stopping all md devices Md: md0 switched to read only mode
Have you got a keyboard plugged in? I had the same problem - it would stop OK but only restart with a keyboard. Never could find out why.
I have a couple systems that behave that way. The fix that worked here was to append 'apm=off' to the kernel parameters. E.g.,
title CentOS (2.6.9-22.0.2.EL) root (hd0,0) kernel /boot/vmlinuz-2.6.9-22.0.2.EL ro root=/dev/md1 apm=off initrd /boot/initrd-2.6.9-22.0.2.EL.img
To my chagrin, I've never investigated what it works...
I have a keyboard and mouse on the server, already modify apm=off on Kernel parameters, and the problem is there.
Any other thing to do?
Thanks.
And about the md0 devices I don't have a array only have a scssi disk.
Thanks.
Carlos Arellano Redes y Telecomunicaciones Gobierno del Estado Tel: 4299-33-00 Ext: 13767 http://chihuahua.gob.mx.
-----Mensaje original----- De: centos-bounces@centos.org [mailto:centos-bounces@centos.org] En nombre de Paul Heinlein Enviado el: Tuesday, February 07, 2006 3:58 PM Para: CentOS mailing list Asunto: Re: [CentOS] Restart Linux
On Tue, 7 Feb 2006, David Fletcher wrote:
On Tuesday 07 Feb 2006 22:24, Carlos Arellano wrote:
I already installed a Centos 4.0 on Server.
But when I restart the server stop and never get up again.
The last messages are this.
Md: stopping all md devices Md: md0 switched to read only mode
Have you got a keyboard plugged in? I had the same problem - it would stop OK but only restart with a keyboard. Never could find out why.
I have a couple systems that behave that way. The fix that worked here was to append 'apm=off' to the kernel parameters. E.g.,
title CentOS (2.6.9-22.0.2.EL) root (hd0,0) kernel /boot/vmlinuz-2.6.9-22.0.2.EL ro root=/dev/md1 apm=off initrd /boot/initrd-2.6.9-22.0.2.EL.img
To my chagrin, I've never investigated what it works...
On Feb 7, 2006, at 6:59 PM, Carlos Arellano wrote:
I have a keyboard and mouse on the server, already modify apm=off on Kernel parameters, and the problem is there.
Any other thing to do?
perhaps add "noacpi" to your kernel parameters as well?
what hardware (especially what motherboard) does this machine have?
-steve
--- If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
I have already add acpi=off on kernel parameters, And my server is a Compaq proliant, I have the same problem with other distributions.
Any help ?
Carlos Arellano Redes y Telecomunicaciones Gobierno del Estado Tel: 4299-33-00 Ext: 13767 http://chihuahua.gob.mx.
-----Mensaje original----- De: Steve Huff [mailto:shuff@vecna.org] Enviado el: Tuesday, February 07, 2006 5:30 PM Para: CentOS mailing list Asunto: Re: [CentOS] Restart Linux
X-Sp5.0 tests=ALL_TRUSTED autolearn=ham version=3.0.4 X-BeenThere: centos@centos.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: CentOS mailing list centos@centos.org List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: http://lists.centos.org/mailman/listinfo/centos, mailto:centos-request@centos.org?subject=unsubscribe List-Archive: http://lists.centos.org/pipermail/centos List-Post: mailto:centos@centos.org List-Help: mailto:centos-request@centos.org?subject=help List-Subscribe: http://lists.centos.org/mailman/listinfo/centos, mailto:centos-request@centos.org?subject=subscribe Sender: centos-bounces@centos.org Errors-To: centos-bounces@centos.org
------=neXtPaRt_1139358632 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit
On Feb 7, 2006, at 6:59 PM, Carlos Arellano wrote:
I have a keyboard and mouse on the server, already modify apm=off on Kernel parameters, and the problem is there.
Any other thing to do?
perhaps add "noacpi" to your kernel parameters as well?
what hardware (especially what motherboard) does this machine have?
-steve
--- If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
------=neXtPaRt_1139358632 Content-Type: text/plain;
Este correo se encuentra libre de virus
------=neXtPaRt_1139358632--
Este correo se encuentra libre de virus
Este correo se encuentra libre de virus
Carlos Arellano spake the following on 2/8/2006 9:32 AM:
I have already add acpi=off on kernel parameters, And my server is a Compaq proliant, I have the same problem with other distributions.
http://h18004.www1.hp.com/products/servers/linux/documentation.html
Carlos Arellano wrote:
I have a keyboard and mouse on the server, already modify apm=off on Kernel parameters, and the problem is there.
Any other thing to do?
Thanks.
And about the md0 devices I don't have a array only have a scssi disk.
Thanks.
What command are you using to restart the server? I have one machine that doesn't like
shutdown -r now
but works fine with
reboot
John Hinton
Carlos Arellano Redes y Telecomunicaciones Gobierno del Estado Tel: 4299-33-00 Ext: 13767 http://chihuahua.gob.mx.
-----Mensaje original----- De: centos-bounces@centos.org [mailto:centos-bounces@centos.org] En nombre de Paul Heinlein Enviado el: Tuesday, February 07, 2006 3:58 PM Para: CentOS mailing list Asunto: Re: [CentOS] Restart Linux
On Tue, 7 Feb 2006, David Fletcher wrote:
On Tuesday 07 Feb 2006 22:24, Carlos Arellano wrote:
I already installed a Centos 4.0 on Server.
But when I restart the server stop and never get up again.
The last messages are this.
Md: stopping all md devices Md: md0 switched to read only mode
Have you got a keyboard plugged in? I had the same problem - it would stop OK but only restart with a keyboard. Never could find out why.
I have a couple systems that behave that way. The fix that worked here was to append 'apm=off' to the kernel parameters. E.g.,
title CentOS (2.6.9-22.0.2.EL) root (hd0,0) kernel /boot/vmlinuz-2.6.9-22.0.2.EL ro root=/dev/md1 apm=off initrd /boot/initrd-2.6.9-22.0.2.EL.img
To my chagrin, I've never investigated what it works...
Este correo se encuentra libre de virus
!DSPAM:43e93420218498152433266!
Este correo se encuentra libre de virus
!DSPAM:43e93420218498152433266!
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
!DSPAM:43e93420218498152433266!
Well, Jarod's rc.sysinit patch hasn't helped. Both ivtv and lirc_i2c say they see each other but I'm still not getting any output from irw. :(
Peter Loron wrote:
Sorry, this may already have come up, but have you looked through Jarod Wilson's guide (recently updated for FC4. That may provide some additional insight...
On Thu, 2005-09-29 at 12:40, Kirk Bocek wrote:
Scot, I believe you said you were using the IR receiver on the PVR-350, right? Do you have any notes or gotcha's on getting it to work. So far, I'm having no luck.
I've got ivtv installed and have got my X session running on the PVR-350's frame buffer. Now I'm trying to get the IR receiver working but am getting no output out of irw.
I've got lirc 0.7.2 installed. I've got:
alias char-major-61 lirc_i2c
in modprobe.conf. When I modprobe lirc_i2c it whines about bttv and cx8800 (which aren't installed) then says:
lirc_i2c: chip found @ 0x18 (Hauppauge IR) ivtv: i2c attach to card #0 ok [client=Hauppauge IR, addr=18] lirc_dev: lirc_register_plugin: sample_rate: 10
So it looks like the two pieces are talking. the /dev entries seem to be correct. But I get no output at all from irw. No errors either. I even tried plugging in a second Hauppauge IR receiver into the card that I had laying around.
Do you have any ideas?
Thanks, Kirk
On my masterbackend/frontend system it uses FC3 which is probably closer to Centos 4.1 (assume that is the version you are using).
I have the following entries in /etc/modprobe.conf:
alias char-major-61 lirc_i2c # --- BEGIN: lirc setup --- install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install lirc_i2c # --- END: lirc setup ---
I believe I found that in Jarod's guide for FC3. The FC4 install used these same lines. When I set this up on the slave backend/frontend system lirc worked first time with irw and then with mythtv.
I just followed the section in Jarod's guide for setting this up. Check for typos and walk through each step carefully. Make sure 61 is the right number for the device. Look for the major number 61 in the /dev directory. Should be lirc device or grep for 61.
And just to make sure the simple things are taken care of, check that you put the batteries in the remote. And that they are installed correctly. :)
Finally got my PVR-350 IR problem solved. Turns out the error was between the keyboard and chair...
I was using a One-For-All UNC-8910 remote for testing instead of the gray Hauppauge remote that came with the PVR-350. I *assumed* (always a bad thing) that IR receiver would accept any signals and that they would show up under the 'raw output' utilities like irrecord and mode2... not so.
Most of the default modes on the 8910 are *not* recognized by the PVR-350 IR whatsoever. Once I started using the gray Hauppauge remote, everything worked. It also works with the 8910 once I use the 'learning mode' of the 8910 to program the Hauppauge codes.
<sigh> One of these days I'll get that 'Do What I Want' button installed...
Kirk
Scot L. Harris wrote:
On Thu, 2005-09-29 at 12:40, Kirk Bocek wrote:
Scot, I believe you said you were using the IR receiver on the PVR-350, right? Do you have any notes or gotcha's on getting it to work. So far, I'm having no luck.
I've got ivtv installed and have got my X session running on the PVR-350's frame buffer. Now I'm trying to get the IR receiver working but am getting no output out of irw.
I've got lirc 0.7.2 installed. I've got:
alias char-major-61 lirc_i2c
in modprobe.conf. When I modprobe lirc_i2c it whines about bttv and cx8800 (which aren't installed) then says:
lirc_i2c: chip found @ 0x18 (Hauppauge IR) ivtv: i2c attach to card #0 ok [client=Hauppauge IR, addr=18] lirc_dev: lirc_register_plugin: sample_rate: 10
So it looks like the two pieces are talking. the /dev entries seem to be correct. But I get no output at all from irw. No errors either. I even tried plugging in a second Hauppauge IR receiver into the card that I had laying around.
Do you have any ideas?
Thanks, Kirk
On my masterbackend/frontend system it uses FC3 which is probably closer to Centos 4.1 (assume that is the version you are using).
I have the following entries in /etc/modprobe.conf:
alias char-major-61 lirc_i2c # --- BEGIN: lirc setup --- install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install lirc_i2c # --- END: lirc setup ---
I believe I found that in Jarod's guide for FC3. The FC4 install used these same lines. When I set this up on the slave backend/frontend system lirc worked first time with irw and then with mythtv.
I just followed the section in Jarod's guide for setting this up. Check for typos and walk through each step carefully. Make sure 61 is the right number for the device. Look for the major number 61 in the /dev directory. Should be lirc device or grep for 61.
And just to make sure the simple things are taken care of, check that you put the batteries in the remote. And that they are installed correctly. :)
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Kirk Bocek wrote:
Finally got my PVR-350 IR problem solved. Turns out the error was between the keyboard and chair...
I was using a One-For-All UNC-8910 remote for testing instead of the gray Hauppauge remote that came with the PVR-350. I *assumed* (always a bad thing) that IR receiver would accept any signals and that they would show up under the 'raw output' utilities like irrecord and mode2... not so.
Most of the default modes on the 8910 are *not* recognized by the PVR-350 IR whatsoever. Once I started using the gray Hauppauge remote, everything worked. It also works with the 8910 once I use the 'learning mode' of the 8910 to program the Hauppauge codes.
<sigh> One of these days I'll get that 'Do What I Want' button installed...
Kirk
Got some side questions.... Does this system have the ability to record HDTV? Does this system 'autoskip' commercials? This sounds like a great alternative to the $800 dvr/hdtv receivers which seems to now come with a $5 per month 'dvr fee'? Where does the $5 go? Why does it exist? Is this a way to appease the skipping of commercials or just another way to make money for the use of a signal you're already paying for? Anyway, I'm feeling like I'm being taken for a ride... HDTV is the future... why can they charge more for HDTV service at all? It is a federal 'standard'. All broadcast some day will be in HDTV. Sorry... an off topic rant... but I'm looking for a cure to the dvr issue at the moment.
Thanks for any help.
John Hinton
John, I'm just getting started with MythTV, so I'm probably not the right person to ask. I've seen postings on the various lists about HDTV so I assume the answer is yes, it can handle it with the right hardware. No, there are no fees. MythTV uses some freely available scheduling information to do its thing. I haven't gotten that far yet, so I can't say too much. Yes, I've read that MythTV and do commercial skipping.
Some links to get you started:
http://mysettopbox.tv/ http://wilsonet.com/mythtv/fcmyth.php http://www.linuxis.us/linux/media/howto/linux-htpc/
There's lots, lots more out there.
Kirk
John Hinton wrote:
Kirk Bocek wrote:
Finally got my PVR-350 IR problem solved. Turns out the error was between the keyboard and chair...
I was using a One-For-All UNC-8910 remote for testing instead of the gray Hauppauge remote that came with the PVR-350. I *assumed* (always a bad thing) that IR receiver would accept any signals and that they would show up under the 'raw output' utilities like irrecord and mode2... not so.
Most of the default modes on the 8910 are *not* recognized by the PVR-350 IR whatsoever. Once I started using the gray Hauppauge remote, everything worked. It also works with the 8910 once I use the 'learning mode' of the 8910 to program the Hauppauge codes.
<sigh> One of these days I'll get that 'Do What I Want' button installed...
Kirk
Got some side questions.... Does this system have the ability to record HDTV? Does this system 'autoskip' commercials? This sounds like a great alternative to the $800 dvr/hdtv receivers which seems to now come with a $5 per month 'dvr fee'? Where does the $5 go? Why does it exist? Is this a way to appease the skipping of commercials or just another way to make money for the use of a signal you're already paying for? Anyway, I'm feeling like I'm being taken for a ride... HDTV is the future... why can they charge more for HDTV service at all? It is a federal 'standard'. All broadcast some day will be in HDTV. Sorry... an off topic rant... but I'm looking for a cure to the dvr issue at the moment.
Thanks for any help.
John Hinton _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, 2005-10-06 at 12:30, Kirk Bocek wrote:
John, I'm just getting started with MythTV, so I'm probably not the right person to ask. I've seen postings on the various lists about HDTV so I assume the answer is yes, it can handle it with the right hardware. No, there are no fees. MythTV uses some freely available scheduling information to do its thing. I haven't gotten that far yet, so I can't say too much. Yes, I've read that MythTV and do commercial skipping.
Some links to get you started:
http://mysettopbox.tv/ http://wilsonet.com/mythtv/fcmyth.php http://www.linuxis.us/linux/media/howto/linux-htpc/
There's lots, lots more out there.
Kirk
John Hinton wrote:
Got some side questions.... Does this system have the ability to record HDTV? Does this system 'autoskip' commercials? This sounds like a great alternative to the $800 dvr/hdtv receivers which seems to now come with a $5 per month 'dvr fee'? Where does the $5 go? Why does it exist? Is this a way to appease the skipping of commercials or just another way to make money for the use of a signal you're already paying for? Anyway, I'm feeling like I'm being taken for a ride... HDTV is the future... why can they charge more for HDTV service at all? It is a federal 'standard'. All broadcast some day will be in HDTV. Sorry... an off topic rant... but I'm looking for a cure to the dvr issue at the moment.
Thanks for any help.
Yes you can setup mythtv to handle HDTV. Have not done that myself yet but many people on the list have. You need to install one of the HD capable capture cards. I believe there is also an option to use a firewire connection from HDTV converter boxes that cable companies provide. Actually been some discussion that cable companies are required to provide the firewire connections.
The auto commercial skip feature is one of my favorite features. It is not 100% but does auto skip about 90% or better of the commercials. It depends a lot on the particular show. Some shows the skips are perfect all the time. Other shows will miss some skips. But for the most part it works much better than I expected.
I think the monthly fees on some of the other dvr options is to cover channel listings costs and to make money. mythtv has worked out a deal with http://labs.zap2it.com to provide free channel listings. You just have to fill out a survey about every 3 months.
Personally I just use the analog cable channels provided by my cable company. Canceled the pay channels a long time ago, rarely found anything worth watching on those channels.
Whats really nice is that you can setup a backend system (or more than one backend system) and lots of frontend systems. The frontend systems can view any of the content on the backend systems.
My next project is to build a diskless netboot frontend system.
On Thu, 2005-10-06 at 10:56, John Hinton wrote:
Got some side questions.... Does this system have the ability to record HDTV?
I don't think anything you can buy for a PC will record HDTV from cable systems - at least in the US.
This sounds like a great alternative to the $800 dvr/hdtv receivers which seems to now come with a $5 per month 'dvr fee'? Where does the $5 go? Why does it exist?
In the cable company case, the fee is usually a rental instead of having to buy the $800 box yourself. Over the air/satellite systems are different and you might have to buy the box up front.
Anyway, I'm feeling like I'm being taken for a ride... HDTV is the future... why can they charge more for HDTV service at all?
Bandwidth is much higher for HD.
It is a federal 'standard'. All broadcast some day will be in HDTV.
Digital is a standard and planned requirement considered necessary for bandwidth reduction. HD resolution is not.
-- Les Mikesell lesmikesell@gmail.com
On Thu, 2005-10-06 at 18:15, Les Mikesell wrote:
On Thu, 2005-10-06 at 10:56, John Hinton wrote:
Got some side questions.... Does this system have the ability to record HDTV?
I don't think anything you can buy for a PC will record HDTV from cable systems - at least in the US.\
There are HDTV cards available but as you imply I believe these are for over the air broadcasts. I would think that would include at least some of the channels sent out over a cable system.
http://pchdtv.com/hd_3000.html http://wendy.seltzer.org/mythtv/
As I mentioned in another message I believe I read that cable companies must provide a firewire interface for digital content. Not sure that includes the HDTV content or not but would suspect that it would.
Of course I also read that as of July 2005 they have passed laws making it illegal to make HDTV cards that don't support broadcast flags.
Suspect there will be a big battle over this in the next year or two as HDTV becomes more common and people find that they are unable to record and time shift shows.
On Thu, 2005-10-06 at 19:17, Scot L. Harris wrote:
Got some side questions.... Does this system have the ability to record HDTV?
I don't think anything you can buy for a PC will record HDTV from cable systems - at least in the US.\
There are HDTV cards available but as you imply I believe these are for over the air broadcasts. I would think that would include at least some of the channels sent out over a cable system.
http://pchdtv.com/hd_3000.html http://wendy.seltzer.org/mythtv/
No, in fact the mandated digital tuner that will eventually be required in all US TV's won't work with the digital encoding on the cable systems where nearly all of them will be connected either.
As I mentioned in another message I believe I read that cable companies must provide a firewire interface for digital content. Not sure that includes the HDTV content or not but would suspect that it would.
Yes, it does. I have Comcast and the Motorola DVR and have been able to get HD out the firewire and view it with videolan client but it is very inconvenient since it only plays in real time as the same thing shows on the video outputs.
Of course I also read that as of July 2005 they have passed laws making it illegal to make HDTV cards that don't support broadcast flags.
Suspect there will be a big battle over this in the next year or two as HDTV becomes more common and people find that they are unable to record and time shift shows.
Oh, it isn't that you are unable to record - you are only allowed to use certain equipment to do it. The DVR itself does basic timeshifting, and the firewire output is usable even with protected content with D-VHS tape drives - just not generic computer equipment...
On Thu, 2005-10-06 at 22:38, Les Mikesell wrote:
No, in fact the mandated digital tuner that will eventually be required in all US TV's won't work with the digital encoding on the cable systems where nearly all of them will be connected either.
I never liked having to use cable boxes. The tuners in the TVs, VCRs, DVRs, etc should by default be able to accept and use all the signals sent by the cable company. It gets to be a mess trying to split and route connections to all the different devices and forget viewing multiple channels that are digital or pay channels if you don't have multiple cable boxes.
As I mentioned in another message I believe I read that cable companies must provide a firewire interface for digital content. Not sure that includes the HDTV content or not but would suspect that it would.
Yes, it does. I have Comcast and the Motorola DVR and have been able to get HD out the firewire and view it with videolan client but it is very inconvenient since it only plays in real time as the same thing shows on the video outputs.
I don't understand that, you want to pull in a show faster than it plays?
Of course I also read that as of July 2005 they have passed laws making it illegal to make HDTV cards that don't support broadcast flags.
Suspect there will be a big battle over this in the next year or two as HDTV becomes more common and people find that they are unable to record and time shift shows.
Oh, it isn't that you are unable to record - you are only allowed to use certain equipment to do it. The DVR itself does basic timeshifting, and the firewire output is usable even with protected content with D-VHS tape drives - just not generic computer equipment...
Wonder how long that will last? Such things normally present a challenge to those that develop things like mythtv. :)
On Thu, 2005-10-06 at 22:17, Scot L. Harris wrote:
No, in fact the mandated digital tuner that will eventually be required in all US TV's won't work with the digital encoding on the cable systems where nearly all of them will be connected either.
I never liked having to use cable boxes.
Nobody likes cable boxes except the people selling them and renting them to you.
The tuners in the TVs, VCRs, DVRs, etc should by default be able to accept and use all the signals sent by the cable company.
Actually I'd rather have a device able to deliver to any networked computer instead of having to deal with tuners at every display.
Yes, it does. I have Comcast and the Motorola DVR and have been able to get HD out the firewire and view it with videolan client but it is very inconvenient since it only plays in real time as the same thing shows on the video outputs.
I don't understand that, you want to pull in a show faster than it plays?
Yes, when it is already recorded. The equivalent would be copying a file from one mythtv server to another for later viewing. It would be better to allow access to arbitrary files, not just what comes out the video jacks and to do it at full media speed, not real display time.
Oh, it isn't that you are unable to record - you are only allowed to use certain equipment to do it. The DVR itself does basic timeshifting, and the firewire output is usable even with protected content with D-VHS tape drives - just not generic computer equipment...
Wonder how long that will last? Such things normally present a challenge to those that develop things like mythtv. :)
I think it will last until the voters wake up and realize that their interests have been sold out by the legislators mandating this crap.
First... sorry for breaking this thread so badly.. but... I guess it's not exactly CentOS related anyway. Then again, it is a 'fantastic' new use for Linux in general, which could have a positive effect for us all!
I don't understand that, you want to pull in a show faster than it plays?
Yes, when it is already recorded. The equivalent would be copying a file from one mythtv server to another for later viewing. It would be better to allow access to arbitrary files, not just what comes out the video jacks and to do it at full media speed, not real display time.
Fat chance of that. Remember.. "Who shot J.R.?" I don't think they'll ever allow you to see the outcome faster than the rest of the world by having such a device. Commercials will gain from this, as those wanting to know who shot JR at the earliest possible moment will sit through the commercials. Otherwise, advertising on TV could completely go away and the cost of TV programming would have to rise substantially. Likely, this is already being factored in.. first it was VCRs... clunky but effective... but with DVR, whew.. commercial skip is so very easy.
I think it will last until the voters wake up and realize that their interests have been sold out by the legislators mandating this crap.
I am on Dish Network. So, I buy my equipment 'each' time. I now have a couple of receivers one a STV Dishplayer. I've purchased a LCD TV and am looking at the HDTV options. I should have said this in my first post.
So, looking at Direct and Dish for a best upgrade alternative... I find there really isn't one that's reasonable. Maybe I'm just looking too early and should wait a year... but.. with MythTV, gee, that changes everything. With Dish, I'd need to buy yet another new receiver and to get DVR and HDTV in one receiver it's $799 (which actually contains two receivers.. one HDTV and one STV). I saw on one of the satelite websites, that having a DVR will cost an extra $4.99/month. That rubs me the wrong way. I'm already paying for programming, why do I have to pay more to watch when I want? They didn't charge me the 5 bucks for having a VCR... what's the difference? And, as 'standards' seem to change so quickly, this seems to be an ongoing process of equipment purchases... something I don't want to spend money on for TV.. it's just not that high of a priority. So, Myth looks very very interesting.
So, I'm looking now at a MythTV system and possibly a HDTV satelite receiver, however the quantity of programming and the additional HDTV fees... another 11 bucks a month for 4 to 6 channels... just goes beyond what I really want to pay. Network television is doing simulcast. Now realalistically, how long can we expect that to continue? Something like a football game. If I understand this right they have two crews with two sets of cameras shooting the same game at the same time. Or maybe this is bad information now and that might have just been done at the start? But, I am thinking this redundant signal broadcasting will go away as quickly as it can be done without losing viewers. Maybe in the next 5 to 10 years. Yes, the satelite companies both seem to have put up additional satelites, but this was done to "add local stations", with at the same time the forethought that HDTV was coming, so it was included on the new equipment. I guess I'm just fussing because I want HDTV on my local stations, which is not available via antenna in my remote area, nor via satelite yet... and I want it at the price I'm already paying... which is PLENTY! This is supposed to be a 'free TV' signal. I don't get to charge more for clients visiting our webservers on broadband versus those on dialup!
So, for about the same equipment cost, I could buy myself a nice fast new computer for my workstation, relagate my 2.4GHtz to the Myth system and if the harddrive dies, something that happened to my first dishplayer just weeks before the one year warrenty ran out (whew!!), I'll be able to easily fix it instead of finding a way to replace a bad drive in a dishplayer at perhaps 13 months and going through the hassles of finding information on how to do it. I like this direction much better! It also has the potential of 'extending' the life of my old computer equipment as I upgrade/replace systems.
Thanks for all the links and info.. I'll spend some time figuring out the technobabble in this field and come to a conclusion and direction.
To the list, sorry if this went too far off topic.. I'm hoping it will be considered as good general information to all and yet another great reason for using Linux!
Best Regards, John Hinton
On Thu, 2005-10-06 at 23:31, Les Mikesell wrote:
On Thu, 2005-10-06 at 22:17, Scot L. Harris wrote:
Actually I'd rather have a device able to deliver to any networked computer instead of having to deal with tuners at every display.
Actually mythtv almost gets you there. If you have a sufficient number of capture cards you could have a box that accepts cable from the wall. All your displays would run mythfrontend. This keeps all the tuners on the backend system.
Yes, it does. I have Comcast and the Motorola DVR and have been able to get HD out the firewire and view it with videolan client but it is very inconvenient since it only plays in real time as the same thing shows on the video outputs.
I don't understand that, you want to pull in a show faster than it plays?
Yes, when it is already recorded. The equivalent would be copying a file from one mythtv server to another for later viewing. It would be better to allow access to arbitrary files, not just what comes out the video jacks and to do it at full media speed, not real display time.
OK, I understand now. You are talking about the bundled DVR the cable company provides. Could you feed the firewire into a mythtv box? Then you be able to do those things with the content from the myth box. Would mean not using the Comcast DVR.
Wonder how long that will last? Such things normally present a challenge to those that develop things like mythtv. :)
I think it will last until the voters wake up and realize that their interests have been sold out by the legislators mandating this crap.
Like that will happen in my life time. I have a better chance of winning the lotto.
On Fri, 2005-10-07 at 11:07, Scot L. Harris wrote:
Yes, it does. I have Comcast and the Motorola DVR and have been able to get HD out the firewire and view it with videolan client but it is very inconvenient since it only plays in real time as the same thing shows on the video outputs.
I don't understand that, you want to pull in a show faster than it plays?
Yes, when it is already recorded. The equivalent would be copying a file from one mythtv server to another for later viewing. It would be better to allow access to arbitrary files, not just what comes out the video jacks and to do it at full media speed, not real display time.
OK, I understand now. You are talking about the bundled DVR the cable company provides. Could you feed the firewire into a mythtv box? Then you be able to do those things with the content from the myth box. Would mean not using the Comcast DVR.
For the moment, the DVR/cable box is the only device I have with HD component output so it isn't all that useful to do anything with the firewire output. Eventually I may get something like the roku HD1000 which would make it worthwhile. I've only played with reading firewire the with a Mac program, but it is possible to change the channel and capture the video unless it is encrypted. You can't play back through it.
Wonder how long that will last? Such things normally present a challenge to those that develop things like mythtv. :)
I think it will last until the voters wake up and realize that their interests have been sold out by the legislators mandating this crap.
Like that will happen in my life time. I have a better chance of winning the lotto.
Agreed - and using the DVR isn't that bad... Comcast makes a lot of content available 'on demand', including movies from the premium channels so you don't have to record them yourself to timeshift although they don't have everything in HD and charge extra for the on-demand HD if they do have it.
Scot L. Harris wrote:
I found that two capture cards resolved all but a few conflicts. Three gets that down to almost none and four seems to clear all conflicts so far. But then I have only had four capture cards going less than a week.
I have three, a PVR-500 and PVR-250 and rarely see a conflict. It's wonderful.
I tried a PVR-500 card in the second box. I currently have it pulled out and have a PVR-350 and PVR-250 in that box as well. I had trouble getting the drivers to work correctly with the PVR-500. Have been
ivtv 0.3.8 is pretty good. I'm using the latest SVN build of 0.3.9 since that fixes the problems where one tuner on the PVR-500 would lose audio. At first I thought it was a hardware problem but it turned out to be an issue with the driver. 0.3.9, when release, should be a pretty solid release.
--Ajay
On Wed, 2005-09-28 at 18:12, Ajay Sharma wrote:
Scot L. Harris wrote:
I found that two capture cards resolved all but a few conflicts. Three gets that down to almost none and four seems to clear all conflicts so far. But then I have only had four capture cards going less than a week.
I have three, a PVR-500 and PVR-250 and rarely see a conflict. It's wonderful.
I tried a PVR-500 card in the second box. I currently have it pulled out and have a PVR-350 and PVR-250 in that box as well. I had trouble getting the drivers to work correctly with the PVR-500. Have been
ivtv 0.3.8 is pretty good. I'm using the latest SVN build of 0.3.9 since that fixes the problems where one tuner on the PVR-500 would lose audio. At first I thought it was a hardware problem but it turned out to be an issue with the driver. 0.3.9, when release, should be a pretty solid release.
I was kind of hoping this was a driver issue that would be resolved shortly. I will have to swap around the cards in that box since the motherboard I have seems to have a capacitor placed such that the PVR-500 won't seat correctly. I think the PVR-350 will fit there, it has the IR connector on the bottom edge and it is smaller than the audio connector on the PVR-500 which is on the bottom edge.
On Monday 26 September 2005 20.11, Kirk Bocek wrote:
I'm starting a project to build a MythTV box for my living room. Anyone else currently working with MythTV on CentOS 4?
Here are some of the gotcha's I've worked through so far:
- I was originally planning on using KnoppMyth. But their CD appears to be
only for i386. Without realizing it, the P4 CPU I picked is one of the newer ones with the x86_64 extensions. It won't boot i386.
Intel CPUs with EM64T _will_ work fine with i386 dists. Lots of people pick a i386 dist (even when there is a similar x86_64 dist available) for software and hardware compatibility reasons.
/Peter
Thus, my plan B is going with CentOS4 x86_64 and installing from the ATrpms collection. Here's someone who's already doing this:
http://umich2.com/archives/category/linux/mythtv/
- I picked up a cheap Radeon 7000 with TV out. Wrong! Various posts seem to
say that the TV Out functionality is not supported by the X.org radeon driver. It *does* work with the vesa driver though. I just don't know if video and DVD playback will work with the vesa driver. Does anyone know?
- The stock RedHat kernel does *not* have irda support enabled. I
downloaded 2.6.13.2, enabled irda, and my motherboard's irda port is found and configured. We'll see if I can get it to work with the IR adapter in the nMediaPC case I bought.
Kirk Bocek
Peter Kjellström wrote:
Intel CPUs with EM64T _will_ work fine with i386 dists. Lots of people pick a i386 dist (even when there is a similar x86_64 dist available) for software and hardware compatibility reasons.
/Peter
That's what I thought too. I had wanted to run i386 for compatibility. But as I mentioned to Brian J. Smith off-list, both KnoppMyth and CentoOS4.1 i386 hung when booting off of the install disk. Whereas CentoOS4.1 x86_64 installed without complaint.
Can anyone come up with a reason x86_64 would boot but i386 wouldn't?
On the other side of the compatibility coin, ATrpms has a *full* set of el4.x86_64 RPMs for MythTV, Lirc, etc. So far, compatibility has not been and issue. I mentioned in my first post that I installed the lastest kernel. Turns out that that really wasn't needed. ATrpms has all the needed kernel modules pre-compiled for the currently released kernel. By going with the latest kernel I've had to compile and install all those modules myself.
Kirk Bocek
Quoting Kirk Bocek t004@kbocek.com:
That's what I thought too. I had wanted to run i386 for compatibility. But as I mentioned to Brian J. Smith off-list, both KnoppMyth and CentoOS4.1 i386 hung when booting off of the install disk. Whereas CentoOS4.1 x86_64 installed without complaint.
Can anyone come up with a reason x86_64 would boot but i386 wouldn't?
Could be hole lot of things. Most likely something is weird with your BIOS or motherboard. The CPU as such shouldn't be a problem. When you say "hung", does it load the kernel and initrd images at all? Does the kernel starts? Are you getting kernel panic? Is initrd stuff freaking out? Installer hungs? They are all on different levels, and might point to different things going wrong.
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Aleksandar Milivojevic wrote:
Quoting Kirk Bocek t004@kbocek.com:
That's what I thought too. I had wanted to run i386 for compatibility. But as I mentioned to Brian J. Smith off-list, both KnoppMyth and CentoOS4.1 i386 hung when booting off of the install disk. Whereas CentoOS4.1 x86_64 installed without complaint.
Can anyone come up with a reason x86_64 would boot but i386 wouldn't?
Could be hole lot of things. Most likely something is weird with your BIOS or motherboard. The CPU as such shouldn't be a problem. When you say "hung", does it load the kernel and initrd images at all? Does the kernel starts? Are you getting kernel panic? Is initrd stuff freaking out? Installer hungs? They are all on different levels, and might point to different things going wrong.
It always happened fairly far into the boot process. KnoppMyth would hang just after "Detecting Hardware". Sometimes (but not always) it would give a kernel panic. I tried the 'failsafe' boot with the same result. I'd have to reboot CentOS to see exactly where it was happening but CentOS would always panic with a whole bunch of register dumps and so forth that would scroll off the screen.
x86_64 had been rock-solid for almost a week now.
Kirk
Quoting Kirk Bocek t004@kbocek.com:
It always happened fairly far into the boot process. KnoppMyth would hang just after "Detecting Hardware". Sometimes (but not always) it would give a kernel panic. I tried the 'failsafe' boot with the same result. I'd have to reboot CentOS to see exactly where it was happening but CentOS would always panic with a whole bunch of register dumps and so forth that would scroll off the screen.
x86_64 had been rock-solid for almost a week now.
Then its probably a kernel bug, funky motherboard, or the combo of the two. If you want, you might search Google, kernel list archives, and/or bugzilla to see if there were more folks with your problem (and possibly if there's solution).
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
-
Ajay Sharma -
Aleksandar Milivojevic -
Carlos Arellano -
David Fletcher -
John Hinton -
Kirk Bocek -
Les Mikesell -
Paul Heinlein -
Peter Kjellström -
Peter Loron -
Sam Drinkard -
Scot L. Harris -
Scott Silva -
Simone -
Steve Huff -
Will McDonald