| Author |
Message |
|
detten
|
 Posted: Sat Jan 28, 2006 6:22 am |
|
|
Joined: Sun Jan 15, 2006 10:48 am
Posts: 15
|
I have R5A30.1, and a PVR 150.
After installation live TV worked fine, but whenever I try to record only static/noise is recorded, and for the rest of the session liveTV also only shows this static/noise. A cold reboot usually fixes the liveTV.
I upgraded ivtv drivers to 0.4.2. This fixed the remote issues, but the behaviour while trying to record something is still the same. Since I don't find any posts with simular problems, I assume I misconfigured somethinig. My guess would be the tuner. (I sometimes can restore image/sound when I use ptune-ui, but not always)
I tried to put the tuner to type 38 manually but this doesn't fix the problem either.
Any clues? Thanks.
this is my ivtv output :
Code: ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.2 (tagged release) loading
ivtv: Linux version: 2.6.13.2-chw-3 SMP preempt 586 gcc-3.3
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected WinTV PVR 150 card (cx23416 based)
ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI 18 (level, low) -> IRQ 18
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom: ivtv version
tveeprom: Hauppauge: model = 26039, rev = C1A5, serial# = 7948365
tveeprom: tuner = TCL MPE05-2 (idx = 105, type = 38)
tveeprom: tuner fmt = PAL(B/G) PAL(I) SECAM(L/L') PAL(D/K) (eeprom = 0x74, v4
= 0x00400e17)
tveeprom: audio processor = CX25842 (type = 24)
tveeprom: decoder processor = CX25842 (type = 1d)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
tuner: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3)) by insmod opti
tuner: The type=<n> insmod option will go away soon.
tuner: Please use the tuner=<n> option provided by
tuner: tv aard core driver (bttv, saa7134, ...) instead.
cx25840 0-0044: ivtv driver
cx25840 0-0044: cx25842-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 0-0044: loaded v4l-cx25840.fw firmware (14264 bytes)
ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
wm8775 0-001b: ivtv driver
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
tda9887 0-0043: (ivtv) chip found @ 0x86 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43]
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02050032
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB tota
ivtv0: Initialized WinTV PVR 150, card #0
ivtv: ==================== END INIT IVTV ====================
|
|
| Top |
|
 |
|
tjc
|
Posted: Sat Jan 28, 2006 10:31 am |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
OK, we're going to have to work throught this one step by step. First some clean up and long shot checks to make sure we haven't overlooked anything. The bizarre thing is that watching live TV uses most of the same mechanisms as a scheduled recording.
- Since the tuner type is being detected correctly you shouldn't need to set that in the module options. This will just confuse the issue so lets get rid of it.
- Double check the md5sums of your firmware files. I suspect they're fine but lets cover all the bases.
- Next time you get the static/snow use ivtvctl -Va to see what it's settings are. After that try ivtvctl --reload to see if it recovers.
- Are you using different recording profiles between live and recordings? The PVR-150 doesn't support all the resolutions that the PVR-250 does. I find that the default ones "just work" but I'm NTSC rather than PAL.
- Are you sure you've got the right frequency set and so on selected in mythtv-setup? Rerun it and check all the settings, both under the general page and the input connections. In the later make sure you don't have an external channel change command or preset channel defined.
- You did purge the card definitions and recreate them and the input connections after the driver upgrade right?
That ought to get you started...
|
|
| Top |
|
|
|
detten
|
Posted: Sat Jan 28, 2006 11:38 am |
|
|
Joined: Sun Jan 15, 2006 10:48 am
Posts: 15
|
First of all, thank you for the help.
I booted up knoppmyth to try the steps you proposed. Very supprisingly, I was able to record fine now...
I started and stopped recording a couple of times, and after 3 attempts the static was back.
I did the ivtvctl -Va before and after, this is the diff between both :
Code: sh-3.00$ diff b4.txt after.txt
95c95
< Frequency = 3028
---
> Frequency = 3924
115c115
< Video standard = 0x000000ff
---
> Video standard = 0x00003000
122c122
< Mute = 0
---
> Mute = 1
ivtvctl --reload did not fix the issue however this(obviously) did :
ivtvctl --set-freq 3028
ivtvctl -u 0x00000ff
You know what can cause the 2 settings to change upon start of recording?
md5sums are OK.
I don't think there is a problem with settings between live/recordings since both stop working once the issue kicks in.
frequency is correct too.
I did purge and recreate the card definition, as stated in the wiki.
|
|
| Top |
|
|
|
tjc
|
Posted: Sat Jan 28, 2006 12:18 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
Frequncy is probabaly normal that will change with the channel you're trying record/watch. The video standard however is most likely your problem. You'll have to look up what that one corresponds to and track down where to fix it.
Worst comes to worse you can pretend that you have an external tuner and use a script that calls the ivtvctl and ivtv-tune utilities to do the right thing... Take another look through mythtv-setup and make sure you're not picking NTSC or the wrong version of PAL somewhere...
|
|
| Top |
|
|
|
detten
|
Posted: Sun Jan 29, 2006 6:27 am |
|
|
Joined: Sun Jan 15, 2006 10:48 am
Posts: 15
|
I still haven't found the root of my problem, I guess that for some reason mythtv sets the ivtv driver back to NTSC.
0x3000 seems to be the value for NTSC, and 0xFF for PAL according to /etc/init.d/set_ivtv_param :
Code: ("") IVTV_TYPE=0x3000 ;;
(NTSC) IVTV_TYPE=0x3000 ;;
(PAL) IVTV_TYPE=0xff ;;
To be sure the problem wasn't here I changed all 3 values to 0xff. The problem remained though. And threw me back to 0x3000 after 2 recordings. I also noticed that /etc/sysconfig/ivtv/cfg-0 (config file for the above) wasn't having any IVTV_TYPE defined. So I set it to : Code: IVTV_TYPE='PAL'
alas that didn'tf fix the issue either. (because it was set to PAL at the top of set_ivtv_param anyway)
I think I can be sure I didn't misconfigure in mythtv-setup, since it occasionally works fine. (I even tried to override the default with PAL on all channels seperatly, but that didn't help either)
Besides the Video Standard, also the mute is turned on every time.
Are there more config files I can check?
|
|
| Top |
|
|
|
tjc
|
Posted: Sun Jan 29, 2006 10:24 am |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
I was thinking of your problem last night while while playing with an experimental install. I noticed that the channel editor allows you to set a different "TV Format", but you it looks like you've already found that and didn't have any luck.  I have to agree with your assessment that's it's mistakenly getting set to NTSC by something, since it was the top item on my list.
The next step is to try to narrow down exactly when it happens, for particular channels, particular times, ... Then we can backtrack and look for common factors. It might also help to use ivtvctl to turn on logging for the kernel module. This actually sounds vaguely familiar, and I'm trying to remember where I've seen a posting about someone having the driver get the wrong one of PAL/NTSC... Try hitting the IVTV mailing lists and forums, and possibly the MythTV bug tracking system.
The tuning script notion is still a possibility. Granted it's an ugly hack, but if this turns out ot be a driver or MythTV bug it might be the easiest work around.
|
|
| Top |
|
|
|
detten
|
Posted: Mon Jan 30, 2006 11:48 am |
|
|
Joined: Sun Jan 15, 2006 10:48 am
Posts: 15
|
I'm about to try a fresh knoppmyth install of my machine if I don't find a solution soon I think
Thanks again for the hints. I tried to get maximum debug info from the ivtv module, and I think this might be a cause :
Code: cx25840 0-0044: 720x576 is not a valid size!
cx25840 0-0044: 720x576 is not a valid size!
cx25840 0-0044: 720x576 is not a valid size!
cx25840 0-0044: 720x576 is not a valid size!
Though I thought this was the standard setting for PAL??
Other than that I don't notice anything special in the logging.
I can't find any exactly the same issues on ivtv mailinglists, though this one comes very close (alas without answer) :
http://www.gossamer-threads.com/lists/ivtv/users/27751
Though I actually have noise on the upper 480 lines, he just has his image on wrong resolution. I have had this same issue too, but only 2% of all tries. (the rest is the noise issue)
Further than that, the issue arises on all channels, and mostly on 2nd or 3rd time I start recording. Time isn't a factor.
Maybe I will have to have a look into such tuning script, though its not yet clear to me how that would fix the issue. (I cannot ivtvctl -u 0x00000ff when the card is displaying)
|
|
| Top |
|
|
|
tjc
|
Posted: Mon Jan 30, 2006 8:12 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
detten wrote: Code: cx25840 0-0044: 720x576 is not a valid size! Though I thought this was the standard setting for PAL?? Thats one of those theory and practice things. In theory NTSC is something like 720x525, but in practice even at 640x480 the edges are off the screen. detten wrote: Maybe I will have to have a look into such tuning scrip, though its not yet clear to me how that would fix the issue. (I cannot ivtvctl -u 0x00000ff when the card is displaying) A tuning script gets run when you change the channel, so you can jam the right format and muting in there with ivtvctl, then pick the right channel with ivtv-tune, and it should be right. I'm on the verge of using one myself to deal with the different volume levels between my PVR-250 and my PVR-150. There are things that the MythTV software should let you adjust for each tuner card which it doesn't short of using a brute force solution like this. BTW - I'm not talking about anything hard or scary here. You've probably already used all the commands you would need. Somtheing like this should be about 90% of the solution: Code: #!/bin/bash
DEVICE="/dev/video0"
CTL_OPTS="-d $DEVICE -u 0x00000ff"
TUNE_OPTS="-d $DEVICE -c $1"
/usr/local/bin/ivtvctl $CTL_OPTS
/usr/local/bin/ivtv-tune $TUNE_OPTS Notice that I broke things out to make tweaking them easier. Since only the channel number is passed, you would need a seperate script for each tuner, and each would need the device variable set appropriately. If you wanted to tweak more parameters add them to CTL_OPTS... Stick that in a file called /usr/local/bin/tune_video0.sh and Code: chmod +x /usr/local/bin/tune_video0.sh
should render it executable.
|
|
| Top |
|
|
|
detten
|
Posted: Tue Jan 31, 2006 1:36 am |
|
|
Joined: Sun Jan 15, 2006 10:48 am
Posts: 15
|
thanks again for the explication.
I probably wasn't clear in explaining in what I don't understand 
I don't see 'when'/'how' to call such script. Since for example I'm watching LiveTV, and I start recording it, then I didn't change channel (right?). And as long as I don't switch channel I cannot change back to PAL? So when do you call that script then from mythtv? (Probably a silly question  )
Anyway I'll try to investigate the illegal size thing some further first, and maybe post this issue on the ivtv mailinglist. (though I'm still not sure its an ivtv module issue) Since as long as I watch liveTV only, nothing goes wrong.
|
|
| Top |
|
|
|
tjc
|
Posted: Tue Jan 31, 2006 9:36 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
Well, I don't know if the MythTV software bothers to check if it's already on the channel before calling the tuner script, and I don't know of any other "hooks" that give you a chance to correct settings. Trying it will cost you all of about ten minutes work, and it might solve your problem. We've already wasted more time than that talking about it... The "economics" of the situation seem pretty obvious.
This type of thing always reminds me of puzzling through the old Fortran IV manuals back in my student days. You could spend HOURS reading, rereading, discussing, arguing, looking for other references, discussing those, trying to find examples, ... Or you could spend ten minutes to write a couple simple examples of your own and test them.
It's a rather empowering revelation if you think about it...
|
|
| Top |
|
|
|
detten
|
Posted: Wed Feb 01, 2006 3:21 pm |
|
|
Joined: Sun Jan 15, 2006 10:48 am
Posts: 15
|
I downsized the resolution to 640x480, this eliminates the debug messages, though the behaviour is still the same.
Your post convinced me to create a script  I tried first with the one you pasted earlier, as it looks ok to start with.
I assume I have to call the script in mythtv-setup step 4 "external command..." ?
Anyway I have put it there, and that breaks switching channels completely. (changing channels switches to the same channel all the time)
I guess that isn't the way the script is supposed to be called by mythtv.
How am I supposed to call such script? (Sorry if the answer is trivial, I didn't find any solution right away)
edit : it seems that I can't change channel because my channel frequencies are alphanumeric (europe-west). Adding -t europe-west to the ivtv-tune command fixes that.
I didn't have time to test extensively, but so far the hack seems to work fine
Thanks a lot for the help!
|
|
| Top |
|
|
|
tjc
|
Posted: Wed Feb 01, 2006 10:50 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Like I said, about 90% of the solution. You are now the ultra-cool dude who knows all about this, and gets to answer the next ten newbies questions about it. My answer from now on is "Oh, detten is the one to ask. He's our resident expert on that."
BTW - I suspect that your "invalid size" error might have been related to it being set to the wrong TV format, since that's certainly not a valid NTSC size... Thats just a wild guess however...
|
|
| Top |
|
|
|
detten
|
Posted: Thu Feb 02, 2006 3:24 pm |
|
|
Joined: Sun Jan 15, 2006 10:48 am
Posts: 15
|
seems I'm not that ultra-cool yet 
After a reboot I notice the script doesn't work till I stop/start the mythbackend. Executing the script from an xterm does work though :/
It seems like a mythtv bug?
All I need to do is find where mythfrontend is started and do the start/stop of the backend, a hack on a hack. Doesn't that make me ultra-cool or what?  Is 'KnoppMyth-run' the script were the frontend is started? I tried to tweak that but it didn't work.
|
|
| Top |
|
|
|
tjc
|
Posted: Thu Feb 02, 2006 7:10 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
Did you set the right permissons and ownership on it? It should be something like rwxr-xr-x root:root.
|
|
| Top |
|
|
|
detten
|
Posted: Fri Feb 03, 2006 4:07 am |
|
|
Joined: Sun Jan 15, 2006 10:48 am
Posts: 15
|
|
yes I'm sure I did that.
I can run the script as mythtv user perfectly from an xterm while the frontend is running, and it switches channel.
Once the backend is stopped/started again, it also works perfectly
|
|
| Top |
|
|
View unanswered posts
View active topics
KnoppMyth 
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register