Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
On Tue, 29 Nov 2005 18:28:49 -0800, Brad Fuller wrote:
>I've had some success... I'm not even limping yet, but at least I'm
>crawling...
>
>I've been able to scan the channels on the HD3000 once I set it to "DVB"
>card instead of "HD3000".
>I still have to manually /sbin/modprobe cx88-dvb to get the dvb drivers
>to load
***
See below, in modprobe. conf Uncomment the commented cx88-dvb line!!!
***
>I've been able to keep my PVR-250 recording.
Glad to see that you are making progress. It appears that all of us
attempting to help you were talking at cross purposes for quite some time,
as you were actually using the wrong original setup. You could *not* get
to where you wanted to be, from where you were starting... which none of
*us* noticed in a general sense although we noted it specifically, as you
were loading the wrong modules. The light dawned with Daniel's message, it
appears.
(BTW: Thank you Daniel and the other developers for your efforts.)
I suspect that there is a lot of confusion floating around about the names
of things and what they do:
v4L = cx88000 = NTSC (may be referred to as 'something version 4)
dvb =cx88-dvb = ATSC (referred to as 'something version 3x')
It is very easy to select the wrong type of card, not understanding the
differences.
Now that you know, I strongly suggest that you go into mythtv-setup now,
make note of what you have set for the PVR250 and the HD3000 and then
re-start mythtv-setup and agree to delete everything, that is: START FROM
A CLEAN SLATE.
You now know how to select the correct type of card (module) for what you
want to do. It will only take a few minutes to re-enter the two cards.
Your tuning tables are the problem at the moment. It appears that you have
changed your lineup and added that to the existing (NTSC=wrong) lineup. To
get rid of those channels you will have to delete them individually and
manually.
Far easier to adjust your lineups at labs.zap2it.com, and
re-'mythdatabasefill' (which is what happens when you select 'download
from source' or whatever its called (the box beside the 'scan channels'
box).
That should (ok, might!) fix your channel lineup problem.
Re: modprobe.conf, see below.
>I just now have been able to tune to HD3000. I think some of my tuning
>table is off because when I select 2_1 as the starting channel myth
>times out. But, when I set it to 93 (for some reason, there were more
>channels above my cable (top channel 82 on comcast SF-Bay Area) it
>worked. So, I think there is something amiss with the tuning. Don't know
>what yet. I'm don't know how the scanning on mythtv-setup and
>mythfilldatabase from Zap2It works together. Any pointers appreciated.
>I'll have to go back thru the links that geoff, blastzone and Mercury
>have provided (THANKS!)
Myth tunes using *only* the information in its tables. The 'clean' setup
is to use only your zap2it lineups to populate your tables. You can
(should?) have 2 distinct lineups if there is no overlap between the
channels your cards can 'see'. The 'messy' setup is to run a channel scan.
If you do only the latter, its difficult to get the guide to agree with
your channel lineup... If you do both, you end up with duplicate entries
for the channels relating to that card.
In mythtv-setup, selecting 'Video Sources' or 'Fetch from source' in the
'Channel Editor' will end up running mythfilldatabase. You might as well
make sure that your tables are clean.
>My current modprobe.conf for those interested:
>---
>alias eth0 via-rhine
>alias scsi_hostadapter sata_via
>alias snd-card-0 snd-via82xx
>options snd-card-0 index=0
>options snd-via82xx index=0
>remove snd-via82xx { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; };
>/sbin/modprobe -r --ignore-remove snd-via82xx
>alias usb-controller ehci-hcd
>alias usb-controller1 uhci-hcd
>alias ieee1394-controller ohci1394
>#
># ivtv modules setup
>alias char-major-81 videodev
>alias char-major-81-0 ivtv
># alias tveeprom tveeprom-ivtv
Ah HAH! So this worked for you too!
>alias msp3400 msp3400-ivtv
>#
># nvidia kernel module
>alias char-major-195 nvidia-1_0-7676
>alias nvidia nvidia-1_0-7676
>#
># cx88 DVB driver
>alias char-major-81 cx88-blackbird
>#install cx88-dvb
If you take the comment marker '#' off this line, you will no longer have
to load this module manually
**
Geoff
>#install btcx-risc
>#install cx88-dvb /sbin/modprobe cx8800;/sbin/modprobe --ignore-install
>cx88-dvb
>#
># lirc - at bottom to ensure ivtv is loaded before lirc_i2c
>alias char-major-61 lirc_i2c
>install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install
>lirc_i2c
>___
>mythtv-users mailing list
>mythtv-users@mythtv.org
>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
R. Geoffrey Newbury [EMAIL PROTECTED]
Barrister and Solicitor
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
Daniel Kristjansson wrote: On Tue, 2005-11-29 at 13:22 -0800, Brad Fuller wrote: Mercury Morris wrote: So, here's a question: Did you complete a successful scan of available channels during mythtv-setup? It's greyed out. Is it grayed out because I chose "no" at the beginning of mythtv. I just didn't want it to change anything since I didn't want what I had corrupted. Would it? If you are using 0.18.1, it is greyed out because that version didn't support scanning for V4L sources of any kind. SVN supports scanning Analog and Digital V4L sources, as well as DVB sources. And another question: Did you choose to define the HD3000 card as a DVB card (part of Input Connections)? There is no "DVB" setting in Input Connections. My Input Connections assigns the Capture Device (card) and Input to the Video Source (which is "terrestrial" as cited above) What he means is, did you define the card as a "pcHDTV HD-2000/3000" card or "DVB" card. The former only works with the Digial V4L pcHDTV drivers, and the latter only works with the DVB DTV drivers. In SVN the former has been renamed to specify that it only applies with the V4L drivers. When 0.18 was being developed the HD-3000 DVB drivers were new and still a bit broken. Also the digital V4L pcHDTV support in 0.18.1 does not support the pcHDTV 2.0 drivers during setup, only 1.4 and earlier; you need SVN to setup using the digital pcHDTV 2.0 V4L drivers. Under Channel Editor (part of mythtv-setup) you can scan for channels, actually you must scan for them or else MythTV won't work. hmmm... I guess I have to say YES to the question: "Would you like to clear all program data and channel settings..." at the beginning. Shessh.. I don't want to mess up what is alread there. Will it? This will clear all the channels. In SVN, you can delete the channels on one source as part of the scan. But in 0.18 you must either delete each channel individually (hi-light the channel in the Channel Editor, then press M, then select "Delete" from the menu), or you can delete the channels using the mysql command line tool if you have a basic command of SQL, or delete all channels on all sources during startup. If you are using a pcHDTV card I recommend you upgrade to SVN revision 7674. It will make the setup considerably easier, while avoiding the LiveTV problems in current SVN. If you have the DVB drivers installed create a DVB card, and make sure you click all the buttons in the card setup so everything is initialized properly. Also make sure that you do not assign a source that you have ever added V4L channels to, to a DVB card input. That is just asking for trouble as V4L drivers tune to the visual carrier of a channel and DVB drivers tune to the center frequency of a channel. Also if you change the frequency table used by a digital source, make sure you delete all the channels on that card using the "treatment of existing channels" tab in the scanner. A sizable part of the 0.19 release will be improvements in the setup of and usability of digital cards like the pcHDTV HD-3000. The other part of the release is improved LiveTV functionality which we are working the kinks out of at the moment. Much obliged Daniel! As I mentioned in a very recent msg, HD3000 card is limping a bit in the LiveTV on some channels. I still don't know why I have channels above 82 in my listing. I understand all of the ones that have a "_#" appended because that is from the Zap2It download. The channels above 82 don't show up in the Zap2It list, so I don' t know how Myth got those. I suppose from physically scanning the card for channels. I got to figure out how to resolve to two so it is useful. Thanks for the tips on deleting, that might come in handy with this. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
On Tue, 2005-11-29 at 13:22 -0800, Brad Fuller wrote: > Mercury Morris wrote: > > So, here's a question: Did you complete a successful scan of > > available channels during mythtv-setup? > It's greyed out. Is it grayed out because I chose "no" at the beginning > of mythtv. I just didn't want it to change anything since I didn't want > what I had corrupted. Would it? If you are using 0.18.1, it is greyed out because that version didn't support scanning for V4L sources of any kind. SVN supports scanning Analog and Digital V4L sources, as well as DVB sources. > > And another question: Did you choose to define the HD3000 card as a > > DVB card (part of Input Connections)? > There is no "DVB" setting in Input Connections. My Input Connections > assigns the Capture Device (card) and Input to the Video Source (which > is "terrestrial" as cited above) What he means is, did you define the card as a "pcHDTV HD-2000/3000" card or "DVB" card. The former only works with the Digial V4L pcHDTV drivers, and the latter only works with the DVB DTV drivers. In SVN the former has been renamed to specify that it only applies with the V4L drivers. When 0.18 was being developed the HD-3000 DVB drivers were new and still a bit broken. Also the digital V4L pcHDTV support in 0.18.1 does not support the pcHDTV 2.0 drivers during setup, only 1.4 and earlier; you need SVN to setup using the digital pcHDTV 2.0 V4L drivers. > > Under Channel Editor (part of mythtv-setup) you can scan for channels, > > actually you must scan for them or else MythTV won't work. > hmmm... I guess I have to say YES to the question: > "Would you like to clear all program data and channel settings..." > at the beginning. Shessh.. I don't want to mess up what is alread there. > Will it? This will clear all the channels. In SVN, you can delete the channels on one source as part of the scan. But in 0.18 you must either delete each channel individually (hi-light the channel in the Channel Editor, then press M, then select "Delete" from the menu), or you can delete the channels using the mysql command line tool if you have a basic command of SQL, or delete all channels on all sources during startup. If you are using a pcHDTV card I recommend you upgrade to SVN revision 7674. It will make the setup considerably easier, while avoiding the LiveTV problems in current SVN. If you have the DVB drivers installed create a DVB card, and make sure you click all the buttons in the card setup so everything is initialized properly. Also make sure that you do not assign a source that you have ever added V4L channels to, to a DVB card input. That is just asking for trouble as V4L drivers tune to the visual carrier of a channel and DVB drivers tune to the center frequency of a channel. Also if you change the frequency table used by a digital source, make sure you delete all the channels on that card using the "treatment of existing channels" tab in the scanner. A sizable part of the 0.19 release will be improvements in the setup of and usability of digital cards like the pcHDTV HD-3000. The other part of the release is improved LiveTV functionality which we are working the kinks out of at the moment. -- Daniel ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
I've had some success... I'm not even limping yet, but at least I'm
crawling...
I've been able to scan the channels on the HD3000 once I set it to "DVB"
card instead of "HD3000".
I still have to manually /sbin/modprobe cx88-dvb to get the dvb drivers
to load
I've been able to keep my PVR-250 recording.
I just now have been able to tune to HD3000. I think some of my tuning
table is off because when I select 2_1 as the starting channel myth
times out. But, when I set it to 93 (for some reason, there were more
channels above my cable (top channel 82 on comcast SF-Bay Area) it
worked. So, I think there is something amiss with the tuning. Don't know
what yet. I'm don't know how the scanning on mythtv-setup and
mythfilldatabase from Zap2It works together. Any pointers appreciated.
I'll have to go back thru the links that geoff, blastzone and Mercury
have provided (THANKS!)
BTW, when I select the card in mythtv-setup>Input the number that I
place in:
"Starting Channel" didn't stick for a long time. It doesn't matter if I
had mythbackend running or not. (BTW, when it's running, there are more
options (LNB, Stat location... something that is not relevent to my
situation).
Now, the problems I have are:
* audio echoing on most of the HD channels.
* intermittent sound on a few HD channels
* some video stuttering on HD Channels.
* As I mentioned, some channels tuning incorrect (I assume that's the
problem)
CPU pegs out on HD channel (I have a AMD64/3000 running FC4-32bit.
Plenty of power.)
My current modprobe.conf for those interested:
---
alias eth0 via-rhine
alias scsi_hostadapter sata_via
alias snd-card-0 snd-via82xx
options snd-card-0 index=0
options snd-via82xx index=0
remove snd-via82xx { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-via82xx
alias usb-controller ehci-hcd
alias usb-controller1 uhci-hcd
alias ieee1394-controller ohci1394
#
# ivtv modules setup
alias char-major-81 videodev
alias char-major-81-0 ivtv
# alias tveeprom tveeprom-ivtv
alias msp3400 msp3400-ivtv
#
# nvidia kernel module
alias char-major-195 nvidia-1_0-7676
alias nvidia nvidia-1_0-7676
#
# cx88 DVB driver
alias char-major-81 cx88-blackbird
#install cx88-dvb
#install btcx-risc
#install cx88-dvb /sbin/modprobe cx8800;/sbin/modprobe --ignore-install
cx88-dvb
#
# lirc - at bottom to ensure ivtv is loaded before lirc_i2c
alias char-major-61 lirc_i2c
install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install
lirc_i2c
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
R. Geoffrey Newbury wrote: On Tue, 29 Nov 2005 10:56:25 -0800, Brad Fuller wrote: R. Geoffrey Newbury wrote: If you want to watch HD, you need the cx-dvb module. It should be loaded after the ivtv modules and not as part of them. What do mean "not as part of them"? You mean not in modprobe? The pcHDTV card has 2 modes: ATSC and NTSC. If you want NTSC, you can load the cx8800 module as one of the 'alias char-major-81-x' group of lines and it will appear as /dev/videox. In this mode, you can apparently get away with using the tveeprom-ivtv module (not sure of this). If you want ATSC, you must use the tveeprom module (not tveeprom-ivtv) and the cx88-dvb and cx88-blackbird (for the mpeg encoder). These apparently must be loaded after the ivtv stuff and the hardware appears at /dev/dvb/adapter0. Amended below, to match mine.. My modprobe.conf: # ivtv modules setup alias char-major-81-0 ivtv #alias tveeprom tveeprom-ivtv alias msp3400 msp3400-ivtv # # nvidia kernel module alias char-major-195 nvidia-1_0-7676 alias nvidia nvidia-1_0-7676 # lirc - at bottom to ensure ivtv is loaded before lirc_i2c install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install lirc_i2c install cx88-dvb #needs a little more: add: install cx88-blackbird install btcx-risc # I have no idea what this module does! me either. When I used the dvb-tools (I think that's what they were called... I'm getting forgetful with all this!) It installed the following in modprobe.conf: (note that these are only 3 lines. 2nd line is long) alias char-major-81 cx88-blackbird install cx88-atsc /sbin/modprobe cx8800;/sbin/modprobe --ignore-install install cx88-dvb /sbin/modprobe cx8800;/sbin/modprobe --ignore-install cx88-dvb install btcx-risc /sbin/modprobe tuner;/sbin/modprobe --ignore-install btcx-risc I'm lost as to whether I need to have the alias char-major81 in there or not. Very confusing. cx88-dvb is the last loaded. But, the PC still just loads the V4L drivers. I still have to manually: /sbin/modprobe cx-88 If you have to do this again, try cx88-dvb instead. I think that you get this result because of the wrong tveeprom... just a guess opps.. that's a typo. I DO use: /sbin/modprobe cx88-dvb ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
On Tue, 29 Nov 2005 10:56:25 -0800, Brad Fuller wrote: >R. Geoffrey Newbury wrote: > >>If you want to watch HD, you need the cx-dvb module. It should be loaded >>after the ivtv modules and not as part of them. >> >What do mean "not as part of them"? You mean not in modprobe? The pcHDTV card has 2 modes: ATSC and NTSC. If you want NTSC, you can load the cx8800 module as one of the 'alias char-major-81-x' group of lines and it will appear as /dev/videox. In this mode, you can apparently get away with using the tveeprom-ivtv module (not sure of this). If you want ATSC, you must use the tveeprom module (not tveeprom-ivtv) and the cx88-dvb and cx88-blackbird (for the mpeg encoder). These apparently must be loaded after the ivtv stuff and the hardware appears at /dev/dvb/adapter0. Amended below, to match mine.. >My modprobe.conf: > ># ivtv modules setup >alias char-major-81-0 ivtv #alias tveeprom tveeprom-ivtv >alias msp3400 msp3400-ivtv ># ># nvidia kernel module >alias char-major-195 nvidia-1_0-7676 >alias nvidia nvidia-1_0-7676 ># lirc - at bottom to ensure ivtv is loaded before lirc_i2c >install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install >lirc_i2c >install cx88-dvb #needs a little more: add: install cx88-blackbird install btcx-risc # I have no idea what this module does! >cx88-dvb is the last loaded. But, the PC still just loads the V4L >drivers. I still have to manually: > >/sbin/modprobe cx-88 If you have to do this again, try cx88-dvb instead. I think that you get this result because of the wrong tveeprom... just a guess > > >>Your card should show up >>at /dev/dvb/adapter0 with subfolders. >> >Yeah.. it does when I manually "modprobe cx88-dvb" > >>If your card does not want to show up, try adding 'card=22' to the >>modprobe line. >> >> >It seems to be recognized as card=22. Here's the dmesg: > > >Linux video capture interface: v1.00 >cx2388x blackbird driver version 0.0.5 loaded >cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV >[card=22,autodetected] >TV tuner 52 at 0x1fe, Radio tuner -1 at 0x1fe >cx2388x v4l2 driver version 0.0.5 loaded >ACPI: PCI Interrupt :00:0b.0[A] -> Link [LNKC] -> GSI 11 (level, >low) -> IRQ 11 >cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV >[card=22,autodetected] >TV tuner 52 at 0x1fe, Radio tuner -1 at 0x1fe >cx88[0]/0: found at :00:0b.0, rev: 5, irq: 11, latency: 32, mmio: >0xea00 > : chip found @ 0xc2 (cx88[0]) >tuner 1-0061: type set to 52 (Thomson DDT 7610 (ATSC/NTSC)) >cx88[0]/0: registered device video0 [v4l2] >cx88[0]/0: registered device vbi0 >cx88[0]/0: registered device radio0 > > >>It is clear that you are loading the card against the ivtv driver (version >>.5which is why it almost works...). >> >> >What do you mean "against the ivtv driver"? Because, you only get the dmesg result above after doing a manual modprobe of the cx88-dvb module >I guess I'm not understanding the integration of tveeprom for dvb and >ivtv that you explained before. Is that my problem? I'm not sure.. .Maybe not enough coffee. or rum... that's it! not enough rum. Especially at lunch. tveeprom is a module which queries the hardware on your cards, using the eeprom module. I think that the addresses on the cards are fixed but not the information nor the manner in which it is called. There used to be 2 versions of tveeprom: one from the pchdtv side of things and one from ivtv... The pchdtv stuff got added to the kernel tree. ivtv changed the name of the module so you could use tveeprom-ivtv but along the way the 2 versions were merging. I now understand (although I may be wrong) that ivtv was re-written to match the calls and structure used by the kernel versions...At any rate, we can now use the kernel tveeprom to call both the pvr card and the hdtv cards... thus avoiding what is quite properly called 'dll hell' on another OS which shall remain tasteless and insecure... Geoff R. Geoffrey Newbury [EMAIL PROTECTED] Barrister and Solicitor Telephone: 905-271-9600 Mississauga,Ontario, Canada Facsimile: 905-271-1638 ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
On 11/29/05, Brad Fuller <[EMAIL PROTECTED]> wrote: Mercury Morris wrote:> As I re-read this thread, there is something missing:>> Brad, you say you "created a HD3000 card in mythtv-setup and assigned> it to bcast." I asked about that before, but didn't see any answer. Oh.. I merely meant that I created a a Video Source called "terrestrial"using the Channel Freq Table of; us-bcast.>> So, here's a question: Did you complete a successful scan of > available channels during mythtv-setup?It's greyed out. Is it grayed out because I chose "no" at the beginningof mythtv. I just didn't want it to change anything since I didn't wantwhat I had corrupted. Would it? > And another question: Did you choose to define the HD3000 card as a> DVB card (part of Input Connections)?There is no "DVB" setting in Input Connections. My Input Connectionsassigns the Capture Device (card) and Input to the Video Source (which is "terrestrial" as cited above)>> Under Channel Editor (part of mythtv-setup) you can scan for channels,> actually you must scan for them or else MythTV won't work.hmmm... I guess I have to say YES to the question: "Would you like to clear all program data and channel settings..."at the beginning. Shessh.. I don't want to mess up what is alread there.Will it?>> So, I apologize for the questions, but I just wanted to be sure that > the setup steps have all been completed. Otherwise, we aren't all on> the same page trying to figure out what's going wrong. Well, I think you might have a bit of work ahead of you. "Greyed out" scan for channels is not good. This could mean that the MythTV binaries you are using were not compiled with DVB support included. I'm not sure of that, but it's almost exactly like what happened to my system when I added 2.6.13 kernel with DVB support. The difference is "greyed out" (your system) versus missing scan button (my system). >From earlier posts, I got the feeling that you installed MythTV from RPMs - that is from packages built by someone other than yourself. And that's OK, but if the packages do not include DVB support in MythTV, then you have to install a version that DOES include DVB support. Long ago, I gave up on the RPMs, preferring to download all the software in source form and compile it. Then there is little doubt about what is supported and what isn't. This is my subtle way of recommending that you take a deep breath and install from source. I know that if I were to receive news like the three paragraphs above, I wouldn't be too happy, especially if I had never installed from source before. But I can tell you from my experience of November 2004, when I made the decision to give up on RPMs, it was the right thing to do (for me). The quality of the software packages, IVTV, LIRC, and MythTV too, of course, is so good that I don't worry about it at all. After installing from source several times, I have complete confidence in all the packages. As for the question you asked about clearing all program data and channel settings, you don't have to say Yes - at least not yet. But that's not good news, because it seems very likely to me that you have some re-building to do. At the very least, you have some re-installing to do - specifically a version of MythTV that includes DVB support. I hate to add the following (also not good news), but there is a conflict between the IVTV version of tveeprom.ko and the kernel version of that module. I add this point as a heads-up for after the DVB problems are solved. My system has the conflict, now solved in kind of a temporary way. I just wanted to give you as complete a picture of what steps are needed to get your system working with both PVR250 and HD3000 tuners. -- MM ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
Blastzone wrote: Brad - If you say 'yes' to the question at the start about clearing your capture cards, then you'll lose everything you have set up so far. So, step 1 - back up your mysql table! (if you haven't done this already). I haven't read back in the log, but back up your tables!! step 2 - Using mythtv-setup, go to menu option 2 - capture cards. Is your HD3000 listed as a DVB device, v4l device, or hd3000 device? I didn't have any luck with hd3000, and v4l will give you NTSC. Try removing it (highlight and press d) and re-adding as a DVB card. You may need to stop mythbackend. By default, mythbackend will lock DVB cards open. It is listed as an HD3000 device. That was my problem. Heck, that sounded like a reasonable selection to me! I just changed it to DVB and was able to recognize the device. Yeah! Now, I'm doing a channel scan. I did not elect to clear the channels when mythtv-setup started. Once I deleted and added the device as a DVB it allowed me to scan for channels. That's what it is doing right now. Ok, its finished. I now have ATSC channels scanned as well as NTSC channels in my "terrestrial" Video Source. That's not what I wanted and I remember reading that other people had this problem. How do I delete the NTSC channels and leave the ATSC. I'll search the archives for this. If you have any wisdom regarding this I would be very obliged. Thank you ALL for your HELP! I much appreciate it! I'm halfway there... (I hope) brad -- Brad Fuller (408) 799-6124 ** Sonaural Audio Studios ** (408) 799-6123 West San Jose (408) 799-6124 Cambrian Hear us online: www.Sonaural.com See me on O'Reilly: http://www.oreillynet.com/pub/au/2184 ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
Brad - If you say 'yes' to the question at the start about clearing your capture cards, then you'll lose everything you have set up so far. So, step 1 - back up your mysql table! (if you haven't done this already). I haven't read back in the log, but back up your tables!! step 2 - Using mythtv-setup, go to menu option 2 - capture cards. Is your HD3000 listed as a DVB device, v4l device, or hd3000 device? I didn't have any luck with hd3000, and v4l will give you NTSC. Try removing it (highlight and press d) and re-adding as a DVB card. You may need to stop mythbackend. By default, mythbackend will lock DVB cards open. once you've done that, you should be able to go into the channel editor & do a scan.On 11/29/05, Brad Fuller < [EMAIL PROTECTED]> wrote:Mercury Morris wrote:> As I re-read this thread, there is something missing: >> Brad, you say you "created a HD3000 card in mythtv-setup and assigned> it to bcast." I asked about that before, but didn't see any answer.Oh.. I merely meant that I created a a Video Source called "terrestrial" using the Channel Freq Table of; us-bcast.>> So, here's a question: Did you complete a successful scan of> available channels during mythtv-setup?It's greyed out. Is it grayed out because I chose "no" at the beginning of mythtv. I just didn't want it to change anything since I didn't wantwhat I had corrupted. Would it?> And another question: Did you choose to define the HD3000 card as a> DVB card (part of Input Connections)? There is no "DVB" setting in Input Connections. My Input Connectionsassigns the Capture Device (card) and Input to the Video Source (whichis "terrestrial" as cited above)> > Under Channel Editor (part of mythtv-setup) you can scan for channels,> actually you must scan for them or else MythTV won't work.hmmm... I guess I have to say YES to the question:"Would you like to clear all program data and channel settings..." at the beginning. Shessh.. I don't want to mess up what is alread there.Will it?>> So, I apologize for the questions, but I just wanted to be sure that> the setup steps have all been completed. Otherwise, we aren't all on > the same page trying to figure out what's going wrong.>> --> MM>___mythtv-users mailing list mythtv-users@mythtv.orghttp://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
Mercury Morris wrote: As I re-read this thread, there is something missing: Brad, you say you "created a HD3000 card in mythtv-setup and assigned it to bcast." I asked about that before, but didn't see any answer. Oh.. I merely meant that I created a a Video Source called "terrestrial" using the Channel Freq Table of; us-bcast. So, here's a question: Did you complete a successful scan of available channels during mythtv-setup? It's greyed out. Is it grayed out because I chose "no" at the beginning of mythtv. I just didn't want it to change anything since I didn't want what I had corrupted. Would it? And another question: Did you choose to define the HD3000 card as a DVB card (part of Input Connections)? There is no "DVB" setting in Input Connections. My Input Connections assigns the Capture Device (card) and Input to the Video Source (which is "terrestrial" as cited above) Under Channel Editor (part of mythtv-setup) you can scan for channels, actually you must scan for them or else MythTV won't work. hmmm... I guess I have to say YES to the question: "Would you like to clear all program data and channel settings..." at the beginning. Shessh.. I don't want to mess up what is alread there. Will it? So, I apologize for the questions, but I just wanted to be sure that the setup steps have all been completed. Otherwise, we aren't all on the same page trying to figure out what's going wrong. -- MM ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
R. Geoffrey Newbury wrote:
On Mon, 28 Nov 2005 15:58:00 -0800, Brad Fuller wrote:
We need more information about your system: Which kernel are you
using? If you are not using the DVB driver for the HD3000, well...,
you should be!
BRAD, there is a problem with your modprobe.conf
Here's modprobe.conf:
alias char-major-61 lirc_i2c
alias eth0 via-rhine
alias scsi_hostadapter sata_via
alias snd-card-0 snd-via82xx
options snd-card-0 index=0
options snd-via82xx index=0
remove snd-via82xx { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-via82xx
alias usb-controller ehci-hcd
alias usb-controller1 uhci-hcd
alias ieee1394-controller ohci1394
#
# ivtv modules setup
*
should have:
alias char-major 81 videodev
then
alias char-major-81-0 ivtv
I added this. Didn't seem to change anything.
THIS LINE IS THE PROBLEM >>>alias tveeprom tveeprom-ivtv
Comment out that line and try rebooting so that the 'real' tveeprom is
loaded instead of the ivtv version.
How can you tell if it works or not. In the dmesg tveeprom is shown the
same - in the ivtv section, and neither time did it mentiion the
"tveeprom-ivtv" module.
in lsmod, tveeprom module is used by cx88xx.
I think that my main problem is that the cx8800 gets loaded and stops
cx88-dvb from loading. But, I don't know how to get cx8800 to not load.
I assume that Mercury Morris has the same problem as he comments out
all
references to ivtv and cv88 in modprobe and uses rc.local to load the
video drivers -- with waits in between the loads. I may have to resort
to that. Doesn't seem right, though.
If it does not work straight away, copy the kernel tveeprom over to the
ivtv tree, making sure that the ivtv version has a different name.
alias msp3400 msp3400-ivtv
#
# nvidia kernel module
alias char-major-195 nvidia-1_0-7676
alias nvidia nvidia-1_0-7676
# lirc - at bottom to ensure ivtv is loaded before lirc_i2c
Why don't you just remove the lirc_i2c line from the top of the
file, and move it here?
install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install
lirc_i2c
install cx88-dvb /sbin/modprobe cx8800;/sbin/modprobe --ignore-install
cx88-dvb
here is (relevant) dmesg at bootup (too long to include all):
* NOTE that this shows the cx88-dvb stuff is seeing the HD3000
card, BEFORE the ivtv stuff sees the PVR250... This is backwards so try
re-ordering your modprobe.conf file.
But everything appears to be fine
Just like mine!
So the problem is not that the drivers cannot load, but that together they
do not return understandable stuff!
Geoff
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Linux video capture interface: v1.00
cx2388x blackbird driver version 0.0.5 loaded
cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV
[card=22,autodetected]
TV tuner 52 at 0x1fe, Radio tuner -1 at 0x1fe
cx2388x v4l2 driver version 0.0.5 loaded
ACPI: PCI Interrupt :00:0b.0[A] -> Link [LNKC] -> GSI 11 (level,
low) -> IRQ 11
cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV
[card=22,autodetected]
TV tuner 52 at 0x1fe, Radio tuner -1 at 0x1fe
cx88[0]/0: found at :00:0b.0, rev: 5, irq: 11, latency: 32, mmio:
0xea00
: chip found @ 0xc2 (cx88[0])
tuner 1-0061: type set to 52 (Thomson DDT 7610 (ATSC/NTSC))
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/0: registered device radio0
ivtv: START INIT IVTV
ivtv: version 0.4.0 (tagged release) loading
ivtv: Linux version: 2.6.13-1.1532_FC4 686 REGPARM 4KSTACKS gcc-4.0
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv0: Autodetected WinTV PVR 250 card (iTVC16 based)
ACPI: PCI Interrupt :00:0a.0[A] -> Link [LNKB] -> GSI 11 (level,
low) -> IRQ 11
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
: chip found @ 0xc2 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
tveeprom: Hauppauge: model = 32062, rev = B185, serial# = 7366797
tveeprom: tuner = TCL 2002N 6A (idx = 85, type = 50)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x1000)
tveeprom: audio_processor = MSP3445 (type = 12)
saa7115 2-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21]
msp34xx: ivtv version
msp34xx: init: chip=MSP3445G-B8, has NICAM support, simple (D) mode,
simpler (G) no-thread mode
msp34xx: $Id$ compiled on: Oct 21 2005 02:12:13
ivtv0: i2c attach to card #0 ok [client=MSP3445G-B8, addr=40]
tda9885/6/7: chip found @ 0x86
ivtv0: loading /lib/modules/ivtv-fw-enc.bin
ivtv0: Encoder revision: 0x02040024
ivtv0 warning: Encoder Firmware can be buggy, use version 0x02040011 or
0x02050032.
ivtv0: Allocate DMA enco
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
As I re-read this thread, there is something missing: Brad, you say you "created a HD3000 card in mythtv-setup and assigned it to bcast." I asked about that before, but didn't see any answer. So, here's a question: Did you complete a successful scan of available channels during mythtv-setup? And another question: Did you choose to define the HD3000 card as a DVB card (part of Input Connections)? Under Channel Editor (part of mythtv-setup) you can scan for channels, actually you must scan for them or else MythTV won't work. So, I apologize for the questions, but I just wanted to be sure that the setup steps have all been completed. Otherwise, we aren't all on the same page trying to figure out what's going wrong. -- MM ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
R. Geoffrey Newbury wrote:
On Tue, 29 Nov 2005 08:45:08 -0800, Brad Fuller wrote:
I wish I could tell you 1, 2, 3 simple steps that would help your
system work, but it may take a bit of trial-and-error on your part to
find the right combination of commands. It took me a few days of
experimenting to come up with the two files that I use now.
Much obliged. I'll check them out.
I do think there is something with bootup because I have to modprobe to
get cx88 successfully loaded. But, it IS loaded and I can use mplayer to
view HD channels. And, when going into Mythtv, PVR250 works. That's why
I thought it was a configuration problem inside Mythtv, not a driver issue.
If you want to watch HD, you need the cx-dvb module. It should be loaded
after the ivtv modules and not as part of them.
What do mean "not as part of them"? You mean not in modprobe?
My modprobe.conf:
alias char-major-61 lirc_i2c
alias eth0 via-rhine
alias scsi_hostadapter sata_via
alias snd-card-0 snd-via82xx
options snd-card-0 index=0
options snd-via82xx index=0
remove snd-via82xx { /usr/sbin/alsactl store 0 >/dev/null
2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-via82xx
alias usb-controller ehci-hcd
alias usb-controller1 uhci-hcd
alias ieee1394-controller ohci1394
#
# ivtv modules setup
alias char-major-81-0 ivtv
alias tveeprom tveeprom-ivtv
alias msp3400 msp3400-ivtv
#
# nvidia kernel module
alias char-major-195 nvidia-1_0-7676
alias nvidia nvidia-1_0-7676
# lirc - at bottom to ensure ivtv is loaded before lirc_i2c
install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install
lirc_i2c
install cx88-dvb
cx88-dvb is the last loaded. But, the PC still just loads the V4L
drivers. I still have to manually:
/sbin/modprobe cx-88
Your card should show up
at /dev/dvb/adapter0 with subfolders.
Yeah.. it does when I manually "modprobe cx88-dvb"
If your card does not want to show up, try adding 'card=22' to the
modprobe line.
It seems to be recognized as card=22. Here's the dmesg:
Linux video capture interface: v1.00
cx2388x blackbird driver version 0.0.5 loaded
cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV
[card=22,autodetected]
TV tuner 52 at 0x1fe, Radio tuner -1 at 0x1fe
cx2388x v4l2 driver version 0.0.5 loaded
ACPI: PCI Interrupt :00:0b.0[A] -> Link [LNKC] -> GSI 11
(level, low) -> IRQ 11
cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV
[card=22,autodetected]
TV tuner 52 at 0x1fe, Radio tuner -1 at 0x1fe
cx88[0]/0: found at :00:0b.0, rev: 5, irq: 11, latency: 32, mmio:
0xea00
: chip found @ 0xc2 (cx88[0])
tuner 1-0061: type set to 52 (Thomson DDT 7610 (ATSC/NTSC))
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/0: registered device radio0
It is clear that you are loading the card against the ivtv driver (version
.5which is why it almost works...).
What do you mean "against the ivtv driver"?
I guess I'm not understanding the integration of tveeprom for dvb and
ivtv that you explained before. Is that my problem?
thanks for your help!
brad
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
Mercury Morris wrote: Thanks for gathering all the information and posting it. Others may not agree with me after reading the bootup messages from the system log, but I do not believe that you are using the DVB drivers. I base this on the line that says: cx2388x v4l2 driver version 0.0.5 loaded And then there are the lines that refer to "registered device(s)" video0 [v4l2], vbi0, and radio0. These are not the devices you want to be created when using the DVB drivers to control the HD3000 card. There should be a line like DVB: registering frontend 0 (pcHDTV HD3000 HDTV)... I cannot tell you what specific steps are needed to correct this, mainly because I cannot sit down in front of your system and have a look at all the files that control the start-up. But it looks like there is a conflict somewhere that causes the V4L driver to be loaded, and the DVB driver to be shoved aside, ignored, whatever. What I can do is attach two files, modprobe.conf and rc.local. These are the two files that I use to control how the tuner cards are recognized, registered, and initialized. But I do this quite reluctantly because your system and my system are different. And I caution that if you DO read through these two files, note the sections that are COMMENTED-OUT. I found that modprobe.conf was not reliable, and moved the start-up commands to rc.local so I could control the order and timing of loading the software. I wish I could tell you 1, 2, 3 simple steps that would help your system work, but it may take a bit of trial-and-error on your part to find the right combination of commands. It took me a few days of experimenting to come up with the two files that I use now. Much obliged. I'll check them out. I do think there is something with bootup because I have to modprobe to get cx88 successfully loaded. But, it IS loaded and I can use mplayer to view HD channels. And, when going into Mythtv, PVR250 works. That's why I thought it was a configuration problem inside Mythtv, not a driver issue. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
Thanks for gathering all the information and posting it. Others may not agree with me after reading the bootup messages from the system log, but I do not believe that you are using the DVB drivers. I base this on the line that says: cx2388x v4l2 driver version 0.0.5 loaded And then there are the lines that refer to "registered device(s)" video0 [v4l2], vbi0, and radio0. These are not the devices you want to be created when using the DVB drivers to control the HD3000 card. There should be a line like DVB: registering frontend 0 (pcHDTV HD3000 HDTV)... I cannot tell you what specific steps are needed to correct this, mainly because I cannot sit down in front of your system and have a look at all the files that control the start-up. But it looks like there is a conflict somewhere that causes the V4L driver to be loaded, and the DVB driver to be shoved aside, ignored, whatever. What I can do is attach two files, modprobe.conf and rc.local. These are the two files that I use to control how the tuner cards are recognized, registered, and initialized. But I do this quite reluctantly because your system and my system are different. And I caution that if you DO read through these two files, note the sections that are COMMENTED-OUT. I found that modprobe.conf was not reliable, and moved the start-up commands to rc.local so I could control the order and timing of loading the software. I wish I could tell you 1, 2, 3 simple steps that would help your system work, but it may take a bit of trial-and-error on your part to find the right combination of commands. It took me a few days of experimenting to come up with the two files that I use now. -- MM mm.rc.local Description: Binary data mm.modprobe.conf Description: Binary data ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
Steve Adeff wrote: On Monday 28 November 2005 17:36, Brad Fuller wrote: Steve Adeff wrote: I had similar problems once, you need to recompile MythTV and make sure to enable DVB support. It could also be improper DVB header files for the drivers which Myth uses. I've tried the ones that come with the 2.6.13 kernel with no luck so I just grabbed the drivers from the pchdtv.com downloads area and installed *just* the header files. You installed just the header files with no rebuild? Is that what you are saying? Do you know which file to download to get the header files? I didn't see anything at the site that addressed this. for some reason the headers that came with my kernel wouldn't allow Myth or Mplayer to access the card (azap worked fine). So I downloaded the driver from pchdtv.com. I figured, well, I know the card and driver works, its just programs I'm compiling so maybe the header files with this kernel are fubar. I checked and the header files were different so I copied the newer driver headers over the ones that came with the kernel, recompiled mplayer and it worked, so I recompiled mythtv and it worked. problem solved! Thanks for the tip, Steve. Mplayer works fine for me. I just can't get MythTV to work. What do you have for your HD3000 card in your mythtv-setup >>Capture Card Setup>>Video Device ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
On Monday 28 November 2005 17:36, Brad Fuller wrote: > Steve Adeff wrote: > >I had similar problems once, you need to recompile MythTV and make sure to > >enable DVB support. It could also be improper DVB header files for the > >drivers which Myth uses. I've tried the ones that come with the 2.6.13 > > kernel with no luck so I just grabbed the drivers from the pchdtv.com > > downloads area and installed *just* the header files. > > You installed just the header files with no rebuild? Is that what you > are saying? > > Do you know which file to download to get the header files? I didn't see > anything at the site that addressed this. for some reason the headers that came with my kernel wouldn't allow Myth or Mplayer to access the card (azap worked fine). So I downloaded the driver from pchdtv.com. I figured, well, I know the card and driver works, its just programs I'm compiling so maybe the header files with this kernel are fubar. I checked and the header files were different so I copied the newer driver headers over the ones that came with the kernel, recompiled mplayer and it worked, so I recompiled mythtv and it worked. problem solved! Steve ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
-- Forwarded message --
From: Mercury
Morris <[EMAIL PROTECTED]>
Date: Nov 28, 2005 3:55 PM
Subject: Re: [mythtv-users] HD3000 recording problem in Mythtv-
signalStrengthATSC_v4l2(), error: Invalid argument
To: Discussion about mythtv <mythtv-users@mythtv.org
>
I
created a HD3000 card in mythtv-setup and assigned it to bcast. I
created a new Zap2It entry for broadcast TV and assigned this to the
HD3000 card. It seemed to dnl the program data fine as the program guide
has terrestrial channels like 3_1, 4_1 intermingled with the regular
cable channels.
What exactly does "...assigned it to bcast." mean?
We need more
information about your system: Which kernel are you using?
If you are not using the DVB driver for the HD3000, well..., you should
be!
2.6.13-1.1532_FC4
Note that I haven't rebooted when working on this. I just:
/sbin/modprobe cx88-dvb
and the modules load.
However, I just rebooted and I had to manually:
/sbin/modprobe cx88-dvb
to get the modules to load (so that /dev/dvb/adapter0 would be
created.) Don't know why. But, that should be a separate problem,right.
Here's modprobe.conf:
alias char-major-61 lirc_i2c
alias eth0 via-rhine
alias scsi_hostadapter sata_via
alias snd-card-0 snd-via82xx
options snd-card-0 index=0
options snd-via82xx index=0
remove snd-via82xx { /usr/sbin/alsactl store 0 >/dev/null
2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-via82xx
alias usb-controller ehci-hcd
alias usb-controller1 uhci-hcd
alias ieee1394-controller ohci1394
#
# ivtv modules setup
alias char-major-81-0 ivtv
alias tveeprom tveeprom-ivtv
alias msp3400 msp3400-ivtv
#
# nvidia kernel module
alias char-major-195 nvidia-1_0-7676
alias nvidia nvidia-1_0-7676
# lirc - at bottom to ensure ivtv is loaded before lirc_i2c
install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install
lirc_i2c
install cx88-dvb /sbin/modprobe cx8800;/sbin/modprobe --ignore-install
cx88-dvb
But,
when I try record something on a ATSC channel even though the hard
disk grinds away and MythTV thinks it's recording nothing shows up and
the .nuv file is empty. This is the relevent mythbackend log:
---
2005-11-28 10:34:31.111 Started recording "The View" on channel: 2020 on
2005-11-28 10:34:
36.685 Channel(14)::signalStrengthATSC_v4l2(), error: Invalid argument
2005-11-28 10:34:36.771 Changing from None to RecordingOnly
2005-11-28 10:34:36.845 Channel(15)::signalStrengthATSC_v4l2(), error:
Invalid argument
2005-11-28 10:34:
42.633 HD5 Error: could not obtain sync
2005-11-28 11:00:00.006 Finished recording The View on channel: 2020
---
I
would also be interested in the messages from the system log during the
boot-up of your system. Specifically, the messages that show the
HD3000 card being detected are of great interest.
Another possible area of interest is how the PVR250 is detected and
initialized, but I'm assuming that it continues to work, even with the
HD3000's difficulties.
Yes.
Why is this of interest...well there could
be some conflict between the two cards and/or between the IVTV software
and the kernel modules. There just isn't enough information in
your post to be sure.
here is (relevant) dmesg at bootup (too long to include all):
Linux version 2.6.13-1.1532_FC4 ([EMAIL PROTECTED])
(gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 Thu Oct 20 01:30:08
EDT 2005
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Linux video capture interface: v1.00
cx2388x blackbird driver version 0.0.5 loaded
cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV
[card=22,autodetected]
TV tuner 52 at 0x1fe, Radio tuner -1 at 0x1fe
cx2388x v4l2 driver version 0.0.5 loaded
ACPI: PCI Interrupt :00:0b.0[A] -> Link [LNKC] -> GSI 11
(level, low) -> IRQ 11
cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV
[card=22,autodetected]
TV tuner 52 at 0x1fe, Radio tuner -1 at 0x1fe
cx88[0]/0: found at :00:0b.0, rev: 5, irq: 11, latency: 32, mmio:
0xea00
: chip found @ 0xc2 (cx88[0])
tuner 1-0061: type set to 52 (Thomson DDT 7610 (ATSC/NTSC))
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/0: registered device radio0
ivtv: START INIT IVTV
ivtv: version 0.4.0 (tagged release) loading
ivtv: Linux version: 2.6.13-1.1532_FC4 686 REGPARM 4KSTACKS gcc-4.0
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv0: Autodetected WinTV PVR 250 card (iTVC16 based)
ACPI: PCI Interrupt :00:0a.0[A] -> Link [LNKB] -> GSI 11
(level, low) -> IRQ 11
ivtv0: Unreasonably low latency timer, setting to 64 (wa
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
Steve Adeff wrote: I had similar problems once, you need to recompile MythTV and make sure to enable DVB support. It could also be improper DVB header files for the drivers which Myth uses. I've tried the ones that come with the 2.6.13 kernel with no luck so I just grabbed the drivers from the pchdtv.com downloads area and installed *just* the header files. You installed just the header files with no rebuild? Is that what you are saying? Do you know which file to download to get the header files? I didn't see anything at the site that addressed this. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
On Monday 28 November 2005 15:47, Brad Fuller wrote: > Howdy all, > > I can now view HD3000 signals outside of mythtv (YEAH) but I cannot > record HD3000 signals inside of myth. > I'm using OTA for HD3000 and cable for PVR250 - both in the same box. > PVR250 records fine (although it's labeled as Encoder 2 on mythweb and > the HD3000 is labeled Encoder 4. Strange.) > > I'm wondering if it is something to do with the tuning or the device > assignment or both > > Potential Assignment problem: > > When playing outside of myth (with mplayer) the HD3000 device is: > /dev/dvb/adapter0/dvr0 > > But, mythtv-setup indicates an error about not being able to probe the > inputs. The permissions on the directory and the devices are the same as > my PVR-250 (video1). I also tried it as "root" with no change. > It does let me assign it to video32 which seems to be a device that > others have used. I don't understand this. > > The HD3000 is assigned to a Video Source Setup (called "terrestrial") > that connects to Zap2It programs of Local broadcast. The tuning table is > us-bcast. > > I think this is my main problem. > > > Potential Tuning Problem: > > I have a list of azap channels in my ~/.azap directory. Can someone tell > me if MythTV uses this table? > > I created a HD3000 card in mythtv-setup and assigned it to bcast. I > created a new Zap2It entry for broadcast TV and assigned this to the > HD3000 card. It seemed to dnl the program data fine as the program guide > has terrestrial channels like 3_1, 4_1 intermingled with the regular > cable channels. > > But, when I try record something on a ATSC channel even though the hard > disk grinds away and MythTV thinks it's recording nothing shows up and > the .nuv file is empty. This is the relevent mythbackend log: > > --- > 2005-11-28 10:34:31.111 Started recording "The View" on channel: 2020 on > cardid: 4, sourceid 2 > 2005-11-28 10:34:31.608 Channel(14)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:32.114 Channel(14)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:32.622 Channel(14)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:33.130 Channel(14)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:33.638 Channel(14)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:34.146 Channel(14)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:34.653 Channel(14)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:35.161 Channel(14)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:35.669 Channel(14)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:36.177 Channel(14)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:36.685 Channel(14)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:36.771 Changing from None to RecordingOnly > 2005-11-28 10:34:36.845 Channel(15)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:37.349 Channel(15)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:37.857 Channel(15)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:38.365 Channel(15)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:38.873 Channel(15)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:39.381 Channel(15)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:39.889 Channel(15)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:40.397 Channel(15)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:40.905 Channel(15)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:41.413 Channel(15)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:41.921 Channel(15)::signalStrengthATSC_v4l2(), error: > Invalid argument > 2005-11-28 10:34:42.633 HD5 Error: could not obtain sync > 2005-11-28 11:00:00.006 Finished recording The View on channel: 2020 > --- > > The program that was suppose to record is on channel 7-1 which is KPIXDT > in Zap2It listing, and "KPIX DT" in azap (if that makes a difference). > Here's my channels from azap: > > $ cat ~/.azap/channels.conf > KNTV-HD:20700:8VSB:65:68:4 > NBC Wea:20700:8VSB:81:84:5 > KBWB-HD:50300:8VSB:49:52:3 > KBWB-SD:50300:8VSB:65:68:4 > KGO-DT :53300:8VSB:49:52:3 > KGO-DT :53300:8VSB:65:68:4 > KTSF-D2:55100:8VSB:49:68:4 > KTSF-D1:55100:8VSB:49:52:3 > KPIX DT:56300:8VSB:49:52:1 > KQED-HD:56900:8VSB:49:52:3 > ENCORE:56900:8VSB:65:68:4 > WORLD:56900:8VSB:81:84:5 > LIFE:56900:8VSB:97:100:6 > KIDS:56900:8VSB:113:116:7 > KMTP Digital Television:58700:8VSB:49:52:3 > KFSF DT:59300:8VSB:49:52:3 > [0004]:59300:8VSB:65:68:4 > KCNS-DT:62300:8VSB:49:52:3 > KKPX FaithTV:63500:8V
[mythtv-users] HD3000 recording problem in Mythtv- signalStrengthATSC_v4l2(), error: Invalid argument
Howdy all, I can now view HD3000 signals outside of mythtv (YEAH) but I cannot record HD3000 signals inside of myth. I'm using OTA for HD3000 and cable for PVR250 - both in the same box. PVR250 records fine (although it's labeled as Encoder 2 on mythweb and the HD3000 is labeled Encoder 4. Strange.) I'm wondering if it is something to do with the tuning or the device assignment or both Potential Assignment problem: When playing outside of myth (with mplayer) the HD3000 device is: /dev/dvb/adapter0/dvr0 But, mythtv-setup indicates an error about not being able to probe the inputs. The permissions on the directory and the devices are the same as my PVR-250 (video1). I also tried it as "root" with no change. It does let me assign it to video32 which seems to be a device that others have used. I don't understand this. The HD3000 is assigned to a Video Source Setup (called "terrestrial") that connects to Zap2It programs of Local broadcast. The tuning table is us-bcast. I think this is my main problem. Potential Tuning Problem: I have a list of azap channels in my ~/.azap directory. Can someone tell me if MythTV uses this table? I created a HD3000 card in mythtv-setup and assigned it to bcast. I created a new Zap2It entry for broadcast TV and assigned this to the HD3000 card. It seemed to dnl the program data fine as the program guide has terrestrial channels like 3_1, 4_1 intermingled with the regular cable channels. But, when I try record something on a ATSC channel even though the hard disk grinds away and MythTV thinks it's recording nothing shows up and the .nuv file is empty. This is the relevent mythbackend log: --- 2005-11-28 10:34:31.111 Started recording "The View" on channel: 2020 on cardid: 4, sourceid 2 2005-11-28 10:34:31.608 Channel(14)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:32.114 Channel(14)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:32.622 Channel(14)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:33.130 Channel(14)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:33.638 Channel(14)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:34.146 Channel(14)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:34.653 Channel(14)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:35.161 Channel(14)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:35.669 Channel(14)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:36.177 Channel(14)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:36.685 Channel(14)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:36.771 Changing from None to RecordingOnly 2005-11-28 10:34:36.845 Channel(15)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:37.349 Channel(15)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:37.857 Channel(15)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:38.365 Channel(15)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:38.873 Channel(15)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:39.381 Channel(15)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:39.889 Channel(15)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:40.397 Channel(15)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:40.905 Channel(15)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:41.413 Channel(15)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:41.921 Channel(15)::signalStrengthATSC_v4l2(), error: Invalid argument 2005-11-28 10:34:42.633 HD5 Error: could not obtain sync 2005-11-28 11:00:00.006 Finished recording The View on channel: 2020 --- The program that was suppose to record is on channel 7-1 which is KPIXDT in Zap2It listing, and "KPIX DT" in azap (if that makes a difference). Here's my channels from azap: $ cat ~/.azap/channels.conf KNTV-HD:20700:8VSB:65:68:4 NBC Wea:20700:8VSB:81:84:5 KBWB-HD:50300:8VSB:49:52:3 KBWB-SD:50300:8VSB:65:68:4 KGO-DT :53300:8VSB:49:52:3 KGO-DT :53300:8VSB:65:68:4 KTSF-D2:55100:8VSB:49:68:4 KTSF-D1:55100:8VSB:49:52:3 KPIX DT:56300:8VSB:49:52:1 KQED-HD:56900:8VSB:49:52:3 ENCORE:56900:8VSB:65:68:4 WORLD:56900:8VSB:81:84:5 LIFE:56900:8VSB:97:100:6 KIDS:56900:8VSB:113:116:7 KMTP Digital Television:58700:8VSB:49:52:3 KFSF DT:59300:8VSB:49:52:3 [0004]:59300:8VSB:65:68:4 KCNS-DT:62300:8VSB:49:52:3 KKPX FaithTV:63500:8VSB:97:100:6 KKPX Worship:63500:8VSB:81:84:5 KKPX Pax:63500:8VSB:65:68:4 KKPX Digital Television:63500:8VSB:49:52:3 KCSM-TV:64700:8VSB:33:36:2 Jazz-TV:64700:8VSB:49:52:3 Jazz-TV:64700:8VSB:65:68:4 KBHK-DT
