| Author |
Message |
|
dothedog
|
 Posted: Sun Sep 30, 2007 6:42 am |
|
|
Joined: Wed Apr 19, 2006 7:58 pm
Posts: 33
|
Hi All,
I did an upgrade from r5E50 last night, I got pretty much everything working except that the tuner doeesn't seem to be working correctly. Here are the symptoms: When I try to "Watch TV" channel 2 is snow, channel 3 shows channel 2 clearly, really poor picture on channel 4 through about channel 48, Channels 50-55 are clear, the rest are bad.
I have a direct analog cable going into the hauppage pvr-250. Mobo is a nf3, video card is nvidia fx 5700.
This all worked great on r5e50.
Here is the output from dmesg:
Code: root@mythtv:/home/dothedog# cat /var/log/messages | grep ivtv
Sep 29 20:41:34 mythtv kernel: ivtv: Start initialization, version 1.1.0
Sep 29 20:41:34 mythtv kernel: ivtv0: Initializing card #0
Sep 29 20:41:34 mythtv kernel: ivtv0: Autodetected Hauppauge card (cx23416 based)
Sep 29 20:41:34 mythtv kernel: ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
Sep 29 20:41:34 mythtv kernel: tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0)
Sep 29 20:41:34 mythtv kernel: msp3400 2-0040: MSP3445G-B8 found @ 0x80 (ivtv i2c driver #0)
Sep 29 20:41:34 mythtv kernel: saa7115 2-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
Sep 29 20:41:34 mythtv kernel: ivtv0: Autodetected Hauppauge WinTV PVR-250
Sep 29 20:41:34 mythtv kernel: ivtv0: Registered device video0 for encoder MPG (4096 kB)
Sep 29 20:41:34 mythtv kernel: ivtv0: Registered device video32 for encoder YUV (2048 kB)
Sep 29 20:41:34 mythtv kernel: ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
Sep 29 20:41:34 mythtv kernel: ivtv0: Registered device video24 for encoder PCM (320 kB)
Sep 29 20:41:34 mythtv kernel: ivtv0: Initialized card #0: Hauppauge WinTV PVR-250
Sep 29 20:41:34 mythtv kernel: ivtv: End initialization
Sep 29 20:41:34 mythtv kernel: ir-kbd-i2c: i2c IR (Hauppauge) detected at i2c-2/2-0018/ir0 [ivtv i2c driver #0]
Sep 29 20:44:45 mythtv kernel: ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
Sep 29 20:44:45 mythtv kernel: ivtv0: Encoder revision: 0x02060039
Sep 29 20:57:17 mythtv kernel: ivtv0: All encoder MPG stream buffers are full. Dropping data.
Sep 29 20:57:17 mythtv kernel: ivtv0: Cause: the application is not reading fast enough.
I get a ton of the last two lines after that. I have never seen that before... But it does look like the card is picked up, the firmware is loading, etc. I have tried using different frequency tables, e.g. set the input to default and changed the tables from us-cable, us-cable-hrc, us-cable-irc in the General tab on mythtv-setup, but it doesn't seem to make any difference. Any help is appreciated. Rob[/code]
|
|
| Top |
|
 |
|
jzigmyth
|
Posted: Sun Sep 30, 2007 7:43 am |
|
|
Joined: Thu Mar 02, 2006 5:42 pm
Posts: 410
Location:
middleton wi usa atsc
|
|
Most likely this is the problem covered in tjc's R5F27hints. Which can be found in the "Hints and Tips" section under the "Knoppmyth" heading of this forum's index page, its a sticky so it should be easy to find. Pay particular attention to the "known issues" section. It refers to PVR-150 and PVR-500 cards but it is likely that the PVR-250 is included in the problem.
|
|
| Top |
|
|
|
tjc
|
Posted: Sun Sep 30, 2007 9:01 am |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
Link in my signature block. There are a whole list of issues for people with PVR cards using the ivtv drivers under "Known Changes", "Known Issues", and "Phase 3 - Post Install Setup". Please follow the links where indicated. (Using a tabbed browser is highly recommended.)
If none of those help, look for the notes in the follow on postings about ivtv buffer settings.
|
|
| Top |
|
|
|
dothedog
|
Posted: Sun Sep 30, 2007 9:42 pm |
|
|
Joined: Wed Apr 19, 2006 7:58 pm
Posts: 33
|
Guys, Thanks for the responses.
I went through the Hints and Tips post. Great stuff btw tjc!
I tried Code: update-rc.d set_ivtv_params defaults
but that didn't work... I got a "usage:" output.
I changed the resolution in WatchTV to 720x480. Set VBI to None.
Also, I went through all the stuff on BlackScreenWatchingTV as well. Dropped cards, inputs, and reloaded etc. Shut down computer, unplugged left it for 10 mins and rebooted.
I checked /etc/mythtv/modules/ivtv and it looks correct. http://mysettopbox.tv/phpBB2/viewtopic.php?t=4325
All cable connections are tight.
Still no workie. This worked great in r5e50.
Any help is greatly appreciated.
Rob
|
|
| Top |
|
|
|
tjc
|
Posted: Sun Sep 30, 2007 10:21 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
| Top |
|
|
|
dothedog
|
Posted: Mon Oct 01, 2007 6:56 am |
|
|
Joined: Wed Apr 19, 2006 7:58 pm
Posts: 33
|
tjc,
Yes, I changed the resolution on Default and LiveTV as well as High and Low, no change.
Not sure what you mean by "bumping up the buffers" are you referring to this:
Code: options enc_yuv_buffers=8 enc_mpg_buffers=32 enc_vbi_buffers=8 enc_pcm_buffers=8
I assume that is supposed to go in: Code: /etc/mythtv/modules/ivtv here it is: Code: root@mythtv:~# cat /etc/mythtv/modules/ivtv
alias char-major-81 videodev
alias char-major-61 lirc_i2c
#options ivtv debug=1
#options tuner type=2
options msp3400 once=1
install ivtv /sbin/modprobe tuner; /sbin/modprobe msp3400; /sbin/modprobe saa7115; /sbin/modprobe --ignore-install ivtv
remove ivtv /sbin/modprobe -r --ignore-remove ivtv && /sbin/modprobe -r saa7115 && /sbin/modprobe -r msp3400 && /sbin/modprobe -r tuner
That isn't in my file... help? Here are the log outputs: Code: dothedog@mythtv:~$ dmesg | grep "tuner model is TCL M2523_.*_E"
dothedog@mythtv:~$
Code: dothedog@mythtv:~$ dmesg | egrep 'tv|i2c|tuner|msp|saa|cx25|cx88|lirc'
Linux version 2.6.18-chw-13 (root@mythtv) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP PREEMPT Sat Jun 2 21:06:06 PDT 2007
i2c_adapter i2c-0: nForce2 SMBus adapter at 0x4c00
i2c_adapter i2c-1: nForce2 SMBus adapter at 0x4c40
ivtv: Start initialization, version 1.1.0
ivtv0: Initializing card #0
ivtv0: Autodetected Hauppauge card (cx23416 based)
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0)
msp3400 2-0040: MSP3445G-B8 found @ 0x80 (ivtv i2c driver #0)
msp3400 2-0040: MSP3445G-B8 supports radio, mode is autodetect and autoselect
saa7115 2-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
tveeprom 2-0050: Hauppauge model 32062, rev B185, serial# 7366722
tveeprom 2-0050: tuner model is TCL 2002N 6A (idx 85, type 50)
tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 2-0050: audio processor is MSP3445 (idx 12)
tveeprom 2-0050: decoder processor is SAA7115 (idx 19)
tveeprom 2-0050: has no radio, has IR receiver, has no IR transmitter
ivtv0: Autodetected Hauppauge WinTV PVR-250
tuner-simple 2-0061: type set to 50 (TCL 2002N)
tuner 2-0061: type set to TCL 2002N
ivtv0: Registered device video0 for encoder MPG (4096 kB)
ivtv0: Registered device video32 for encoder YUV (2048 kB)
ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
ivtv0: Registered device video24 for encoder PCM (320 kB)
ivtv0: Initialized card #0: Hauppauge WinTV PVR-250
ivtv: End initialization
bttv: driver version 0.9.17 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
input: i2c IR (Hauppauge) as /class/input/input2
ir-kbd-i2c: i2c IR (Hauppauge) detected at i2c-2/2-0018/ir0 [ivtv i2c driver #0]
i2c IR (Hauppauge): unknown key: key=0x45 raw=0x18c5 down=1
saa7130/34: v4l2 driver version 0.2.14 loaded
cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
cx88/2: cx2388x dvb driver version 0.0.6 loaded
cx88/2: registering cx8802 driver, type: dvb access: shared
i2c IR (Hauppauge): unknown key: key=0x45 raw=0x18c5 down=0
lirc_dev: IR Remote Control driver registered, at major 61
cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
lirc_i2c: chip found @ 0x18 (Hauppauge IR)
lirc_dev: lirc_register_plugin: sample_rate: 10
ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
ivtv0: Encoder revision: 0x02060039
ivtv0: All encoder MPG stream buffers are full. Dropping data.
ivtv0: Cause: the application is not reading fast enough.
Do you see anything in there that's wierd? I noticed that bttv is loading, I didn't think it was supposed to for this card? Again, THANK YOU for sticking with me. WAF and KAF are taking a bit of a hit  Rob[/code]
|
|
| Top |
|
|
|
tjc
|
Posted: Mon Oct 01, 2007 7:18 am |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
You won't find an existing options line in that file, you need to add it. See this page for details - http://www.knoppmythwiki.org/index.php?page=PerformanceOptimizeHowTo
You also have the ivtv remote problem where the ir_kbd_i2c module loaded by the dvb stuff is messing up your remote.
As for the quality problems, they really sound like a bad frequency set or a weak signal. Given that this hardware worked before (unless you moved it in the process and messed up the cables) I'm guessing its a config option like the frequency set. You need to make sure to restart the BE after making the change and make sure that everything other than the central one under general is set to "default" so that you can make the change and really have it take effect. After that I'd start fiddling with fine tuning or the like.
|
|
| Top |
|
|
|
dothedog
|
Posted: Mon Oct 01, 2007 8:28 pm |
|
|
Joined: Wed Apr 19, 2006 7:58 pm
Posts: 33
|
Ok, I did the following:
downloaded and cp the ir-kbd-i2c.ko.r5f27 to /lib/modules/2.6.18-chw-13/kernel/drivers/media/video/ir-kbd-i2c.ko
to fix the ir remote problem, I haven't tested yet, but I assume it will fix it if there is a problem.
I also added
Code: options enc_yuv_buffers=8 enc_mpg_buffers=32 enc_vbi_buffers=8
to /etc/mythtv/modules/ivtv However, I can't confirm that it took, Code: root@mythtv:/home/dothedog# cat /var/log/kern.log | egrep ivtv0
Oct 1 19:09:09 mythtv kernel: ivtv0: Initializing card #0
Oct 1 19:09:09 mythtv kernel: ivtv0: Autodetected Hauppauge card (cx23416 based)
Oct 1 19:09:09 mythtv kernel: ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
Oct 1 19:09:09 mythtv kernel: ivtv0: Autodetected Hauppauge WinTV PVR-250
Oct 1 19:09:09 mythtv kernel: ivtv0: Registered device video0 for encoder MPG (4096 kB)
Oct 1 19:09:09 mythtv kernel: ivtv0: Registered device video32 for encoder YUV (2048 kB)
Oct 1 19:09:09 mythtv kernel: ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
Oct 1 19:09:09 mythtv kernel: ivtv0: Registered device video24 for encoder PCM (320 kB)
Oct 1 19:09:09 mythtv kernel: ivtv0: Initialized card #0: Hauppauge WinTV PVR-250
Oct 1 19:09:19 mythtv kernel: ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
Oct 1 19:09:19 mythtv kernel: ivtv0: Encoder revision: 0x02060039
Oct 1 19:33:18 mythtv kernel: ivtv0: Initializing card #0
Oct 1 19:33:18 mythtv kernel: ivtv0: Autodetected Hauppauge card (cx23416 based)
Oct 1 19:33:18 mythtv kernel: ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
Oct 1 19:33:18 mythtv kernel: ivtv0: Autodetected Hauppauge WinTV PVR-250
Oct 1 19:33:18 mythtv kernel: ivtv0: Registered device video0 for encoder MPG (4096 kB)
Oct 1 19:33:18 mythtv kernel: ivtv0: Registered device video32 for encoder YUV (2048 kB)
Oct 1 19:33:18 mythtv kernel: ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
Oct 1 19:33:18 mythtv kernel: ivtv0: Registered device video24 for encoder PCM (320 kB)
Oct 1 19:33:18 mythtv kernel: ivtv0: Initialized card #0: Hauppauge WinTV PVR-250
Oct 1 19:33:28 mythtv kernel: ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
Oct 1 19:33:28 mythtv kernel: ivtv0: Encoder revision: 0x02060039
nc_pcm_buffers=8 There is no line: Code: ivtv0: Allocate DMA encoder MPEG stream: 1024 x 32768 buffers (32768KB total) This is the proceedure I used to try the us-cable, us-cable-irc, us-cable-hrc. Code: killall mythbackend
killall mythfrontend
mythtv-setup
change page three of general to us-cablexxx
escape out of mythtv-setup
mythfilldatabase
mythbackend
mythfrontend
select WatchTV
None of this seems to make a difference in the tuning though...
Any other ideas? Again, thanks for sticking with me on this.
Rob
|
|
| Top |
|
|
|
tjc
|
Posted: Mon Oct 01, 2007 10:14 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
No need for the mythfilldatabase step, the rest looks sane.
There are at least 2 places where you can (accidentally or intentionally) override the frequency set. 1) at the tuner input level 2) at the channel level.
|
|
| Top |
|
|
|
dothedog
|
Posted: Tue Oct 02, 2007 8:31 pm |
|
|
Joined: Wed Apr 19, 2006 7:58 pm
Posts: 33
|
Ok, I've tried a couple of things and am a bit confused...
I tried changing from us-cable us-cable-hrc.
Code: dothedog@mythtv:~$ v4l2-ctl -F
Frequency: 864 (54.000000 MHz)
Which according to this table is correct for us-cable-hrc according to this site: http://www.sencore.com/newsletter/Feb02 ... PartII.htmhowever, when I do Code: dothedog@mythtv:~$ ivtv-tune -l
Channels/Frequencies (MHz) for 'us-cable':
1 73.250
2 55.250
...
it says "us-cable" no matter what I do. The frequency of Channel 2 does change. However, I found that I could tune in Channel 2 if I added 6250 via MythWeb. Channel 2 then tunes correctly however: Code: dothedog@mythtv:~$ v4l2-ctl -F
Frequency: 964 (60.250000 MHz) That doesn't look like the correct frequency for Channel 2. According to the table in the website that I listed above Channel 2 should be: us-cable 55.25 us-cable-hrc 54.00 us-cable-irc 55.25 Something is clearly wrong, I don't think I want to try to find the "adjustments" for 100 channels one at a time. Can you think of anything else I can try? Rob EDIT: One more thing that may be unrelated however: Code: dothedog@mythtv:~$ uname -a
Linux mythtv 2.6.18-chw-13 #1 SMP PREEMPT Sat Jun 2 21:06:06 PDT 2007 i686 GNU/Linux
This is an AMD64 box single proc box, I'm wondering why the kernel is an SMP kernel? Could this cause problems?
|
|
| Top |
|
|
|
tjc
|
Posted: Tue Oct 02, 2007 9:08 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
dothedog wrote: This is an AMD64 box single proc box, I'm wondering why the kernel is an SMP kernel? Could this cause problems?
Nothing to worry about.
I've actually posted code before to tromp through all the channels in the DB and add some fixed offset, but I suspect you've got some other problem.
|
|
| Top |
|
|
|
dothedog
|
Posted: Mon Oct 08, 2007 8:45 am |
|
|
Joined: Wed Apr 19, 2006 7:58 pm
Posts: 33
|
Ok, This is pretty embarrassing however, I wanted to post a follow up. I hate finding a thread from someone that has the same problem as I have with no resolution
I actually went out and bought a PVR-150 to see if the PVR-250 card I had in was bad, but before I did, I did one more check of the connections. They were all tight, however, I realized that I had the coax from the wall going into an old vcr then to the PVR-250. I tried directly connecting the coax cable to the card and viola, the card picked up all the channels correctly. The vcr was off so it should have been a straight pass-through, however, for whatever reason, it was causing my PVR-250 to not pick up the channel frequencies correctly. I guess the PVR-150 is going back.
tjc, Thank you for your help, I'm sure you get a lot of dumb problems like this
|
|
| Top |
|
|
|
marc.aronson
|
Posted: Mon Oct 08, 2007 8:37 pm |
|
|
Joined: Tue Jan 18, 2005 2:07 am
Posts: 1532
Location:
California
|
Quote: I also added Code: options enc_yuv_buffers=8 enc_mpg_buffers=32 enc_vbi_buffers=8 to /etc/mythtv/modules/ivtv Heads-up -- there was a typo in the original wiki article that has been corrected. The line should read: Code: options ivtv enc_yuv_buffers=8 enc_mpg_buffers=32 enc_vbi_buffers=8 enc_pcm_buffers=8
Marc
|
|
| Top |
|
|
|
tjc
|
Posted: Mon Oct 08, 2007 11:02 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
dothedog wrote: I realized that I had the coax from the wall going into an old vcr then to the PVR-250. I tried directly connecting the coax cable to the card and viola, the card picked up all the channels correctly. The vcr was off so it should have been a straight pass-through, however, for whatever reason, it was causing my PVR-250 to not pick up the channel frequencies correctly.
Saw something very like that with a VCR myself. Same solution worked for me too. This is why the troubleshooting pages tell you try connecting "straight from the wall" to minimize potential external issues.
Glad to hear that you got it sorted out.
|
|
| Top |
|
|
View unanswered posts
View active topics
Linux 
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register