The channel set for startup is a valid HD channel. Without making any DB changes, I can run version 7058 and it will work fine, then run a newer version and it will fail. I cannot change channels in mythfrontend, it just hangs with a black screen when I try to watch Live TV (much like when an incorrect channel is configured as the initial channel).
The channel it was set for was a cable-only HD channel, which didn't carry PSIP data. So, I changed it to another channel, an OTA channel that includes PSIP. But, the behavior of mythbackend didn't change. Here is the output from the working & failing versions of mythbackend: Working, 7058: 2005-08-18 22:06:24.763 DVB#0 Using DVB card 0, with frontend DViCO FusionHDTV 3 Gold-Q. 2005-08-18 22:06:24.765 New DB connection, total: 3 2005-08-18 22:06:24.766 DVB#0 WARNING - Symbol Rate setting (0) is out of range (min/max:10762000/10762000) 2005-08-18 22:06:24.851 DVB#0 Signal Lock 2005-08-18 22:06:24.912 DVB#1 Using DVB card 1, with frontend pcHDTV HD3000 HDTV. 2005-08-18 22:06:25.425 DVB#1 Signal Lock 2005-08-18 22:06:25.487 Channel(/dev/v4l/video0)::SwitchToInput(in 6): Error -1 while setting video mode (v2), "Invalid argument", trying v4l v1 2005-08-18 22:06:25.487 Channel(/dev/v4l/video0)::SwitchToInput(in 6): Setting video mode with v4l version 1 worked 2005-08-18 22:06:25.786 Channel(/dev/v4l/video1)::SwitchToInput(in 6): Error -1 while setting video mode (v2), "Invalid argument", trying v4l v1 2005-08-18 22:06:25.786 Channel(/dev/v4l/video1)::SwitchToInput(in 6): Setting video mode with v4l version 1 worked Failing, 7090: 2005-08-19 15:06:04.735 DVB#0 Using DVB card 0, with frontend DViCO FusionHDTV 3 Gold-Q. 2005-08-19 15:06:04.739 New DB connection, total: 3 2005-08-19 15:06:04.741 DVB#0 WARNING - Symbol Rate setting (0) is out of range (min/max:10762000/10762000) 2005-08-19 15:06:04.895 DVB#0 Signal Lock 2005-08-19 15:06:07.759 TVRec: Timed out waiting for lock -- aborting recording 2005-08-19 15:06:07.995 DVB#1 Using DVB card 1, with frontend pcHDTV HD3000 HDTV. 2005-08-19 15:06:08.447 DVB#1 Signal Lock 2005-08-19 15:06:08.518 Channel(/dev/v4l/video0)::SwitchToInput(in 6): Error -1 while setting video mode (v2), "Invalid argument", trying v4l v1 2005-08-19 15:06:08.518 Channel(/dev/v4l/video0)::SwitchToInput(in 6): Setting video mode with v4l version 1 worked 2005-08-19 15:06:08.832 Channel(/dev/v4l/video1)::SwitchToInput(in 6): Error -1 while setting video mode (v2), "Invalid argument", trying v4l v1 2005-08-19 15:06:08.832 Channel(/dev/v4l/video1)::SwitchToInput(in 6): Setting video mode with v4l version 1 worked On 8/19/05, Daniel Kristjansson <[EMAIL PROTECTED]> wrote: > On Fri, 2005-08-19 at 10:06 -0700, Todd Ignasiak wrote: > > I also ran into problems with an svn update yesterday. I backed off > > to 7058 and Live TV began working again. > > > > My hardware is: HD3000, FusionHDTV3, and a PVR-500. In a Gentoo > > x86-64 system running kernel 2.6.13-rc3-mm1. > > On mythbackend startup, when DVB0 is initialized, I see a message > > saying "signal locked", then about 3 seconds later, a message saying > > "timed out waiting for signal lock". > Can you send me the DB entries for one channel that causes problems? > i.e. the channel and dtv_multiplex entries. > > I'm thinking maybe this is not a true HDTV channel, but has some > entry in the DB that make MythTV think it is a HDTV channel with > a major and minor channel that it can not find... > > -- Daniel > > > > _______________________________________________ > mythtv-dev mailing list > [email protected] > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev > > > _______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
