Pretty much what's in the subject line. Its not hardware, since Ive got a second PVR-150, and I can't find anything obvious in the log files, except the mythbackend logfile doesn't seem to be getting updated much.

So here's what happens: watching liveTV. Switch channels. "ERROR While Wathicng LiveTV" main menu. Going to 'Watch TV' gives you a 5 second blank screen and drops you at the menu again, unless you can slip a 'y' in there and switch tuners before it does.

Reboots don't help, you have to run mythtv-setup, where everything looks like it did before, and delete and re-add the tuner cards.

Any ideas?

My HW: AMDx2 3600+, nvidia 6200, PVR150, HD5500

Thanks in advance.

Quick clarification- the second PVR150 is not in the box- I just happen to have a spare which I swapped out to test the hardware.

Also- this doesn't happen every time- only on occasion. More often if you do it with a remote frontend, but that may just be coincidence.

This could happen if you had udev rules set up before an upgrade that need to be reapplied. If this was the case you might have something like the pvr-150 set up on /dev/pvr150 or /dev/video01 and the pvr150 is now /dev/video1. Details of the udev rules are at http://www.knoppmythwiki.org/index.php?page=Udev

Thanks, silentmic. This definitely COULD be it- I didn't have udev rules set up previously, but it wasn't necessary. With R5.5, the cx88 modules necessary for the analog tuner portion of the HD5500 have been re-enabled, allowing the establishment of video0 for the analog hd5500, and then the pvr150 shows up as video1 (even though it is ivtv0).

I'll try this tonight, and report back with results.

Well, after some more testing, that's not it.

For informational purposes, I established a udev local.rules (symlinked by /etc/udev/rules.d/z99_local_rules) and it looke dlike this:


It works. After a reboot, there's a /dev/pvr151 which I can refer to in mythtv-setup as the pvr150. Unfortunately, my problem still exists, so I went back to the old way of doing things.

Here's some more things I noticed (I apologize for the lack of better continuous scientific data, I work in blocks of 40 minutes which is all the time my 3 week old son will sleep)

1. Channel changing- if I change channels too fast after changing the previous one, it seems as if the channel_change script isn't finished yet, and it gets tuned to the wrong channel (my channel_change script runs an irblaster script to a dish301)

2. Yesterday, it remembered the tuner, but forgot that I had a channel_change script established under that tuner, and the backend log actually noted 'hey your channel change script is missing, so changing channels won't do anything'. The frontend was working properly, but the channel wouldn't actually change although the OSD stated the correct info. So the channel_change script was working fine, then suddenly didn't- almost like its forgetting the setup info for that card.

3. When this problem occurs, I can restart the frontend, and the backend without fixing it. I have to quit the backend, run mythtv-setup, delete all tuners, re-add them and reassign channels to inputs. The pvr150 is always /dev/video1, but simply running mythtv-setup and quitting will not fix the problem. I do not have to reboot- it works OK when I restart the backend and frontend until it happens again.

4. I've decided that it was a coincidence that it happened more with a remote frontend. I tried both remote and local frontend and got roughly equal occurrences with both)

Any ideas? The HD tuner card (DVB0, HD5500) has never had a problem.

Are you using DHCP and if so does the machine have a consistent host name?

I was, and although the IP address was consistent I wasn't sure about the host name.

I reinstalled from scratch to make sure I wasn't missing something obvious, but also changed over to a static IP.

No change.

I Do, however, have some new and interesting information:

I only get the TV error when I switch to a 3 digit channel. 2 digit channels work consistently perfect, 3 digit channels cause consistent failures.

Here's my channel_change.sh script:



Here's what mythbackend says from a terminal when the failure occurs:


It should be on channel 122, not 1122. Hm.

I can try shortening the delay between numbers, I guess, but why would this happen? I also tried eliminating the cancel at the end without results.

Well, I think I've got a workaraound:

I put the contents of /etc/irblaster/channel_change.sh in a file called /etc/irblaster/channel.sh and just made channel_change.sh say this:


It looks to me like things get irritated when the channel_change.sh script takes longer (like 3 channels instead of 2) to return. This seems to be practical workaround and returns instantly. After some channel changing abuse, it seems to be holding pretty steady.

Since I don't know _why_ this happens, I'm not changing the subject line to resolved.

I have the same problem. I'm trying your workaround tonight, will report back.

I started a new thread here: http://mysettopbox.tv/phpBB2/viewtopic.php?p=116582

_________________
Douw Steyn
LinHES 6.03
AMD Athlon 64 X2 Dual Core 5400+ , PVR-150, GeForce 8100, 2GB RAM,
600GB in Storage Groups