Re: [linux-dvb] Tuner not detected on second Kworld card
On Sun, Oct 14, 2007 at 03:34:08PM -0400, CityK wrote: Yes, you can only use 32KHz from the tuner with the saa713x. This is a hardware limitation of the chip in regards to handling of SIF sources. For further information, search through the V4L achieves using various saa7134 or saa713x and 32KHz and alsa combinations. There should be plenty of good info. (Example: http://marc.info/?l=linux-videow=2r=1s=32KHz+saa7134q=b) Thanks for confirming and clarifying. David -- David Engel [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Tuner not detected on second Kworld card
On Thu, Oct 11, 2007 at 01:46:32PM -0500, David Engel wrote: Notice the absence of an equivalent tuner 1-0061: chip found line for saa7133[1]. This occurs with both the 2.6.21 and 2.6.22.* kernels. I briefly tested analog and digital capture on both cards in a separate system before installing them in the MythTV backend so I don't suspect a hardware problem. Not being able to tune could explain not being able to to an analog capture. Could this be another case of probing being done by the various drivers causing problems? If so, has any of it been fixed in the recently released 2.6.23 kernel? I've already had to go back to the 2.6.21 series on this system because the probing caused a minor problem with the Hauppauge cards. I tried moving the Kworld ATSC 115 cards around and also removing one at a time to see what would happen. I confirmed the tuner could be detected on each Kworld card in some configurations so I don't think it's a hardware problem with the Kworld cards themselves. I also found a case where the tuner on a Kworld card would only be detected if I blacklisted the ivtv driver to make the system ignore the Hauppauge cards. Both Kworld cards are now in slots where the tuner was detected individually in one form or another, but the driver still won't detect the tuner on both Kworld cards. It always only detects the first one. While I can't completely rule out a motherboard or BIOS problem, it does look like a probing/detection problem with the cx88 and/or ivtv drivers. Are any of the fixes for that in the 2.6.23 kernel yet? The minor problem I mentioned earlier has to do with using the saa7134-alsa module to capture sound directly from the card. A quick glance at the driver source code looks like it shold support 32 and 48 kHz sampling rates. I've only been able to get 32 kHz working well so far with MythTV. Trying 48 kHz results in some sort of rate mismatch. Is 48 kHz supposed to work? I tried using mplayer with 48 kHz audio and got the same results. Regardless of the requested audio rate, the cx88-alsa driver or hardware only supplies 32 kHz audio. The result is audio underruns and chipmunk audio because the samples that are received are being played too fast. Can anyone confirm the Kworld card can only do 32 kHz? David -- David Engel [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Tuner not detected on second Kworld card
Hi, I have a MythTV backend with two Kworld ATSC 115 and two Hauppage PVR x50 cards. I've been using the Kworld cards for digital capture for some time now without problem. I'd like to now use them for analog capture too and am having a problem. The first detected card seems to work fine except for one minor thing I'll address separately below. The second detected card doesn't work and only captures all black video or noise. In looking at my logs, I think there is a problem detecting the tuner on the second card. Oct 11 12:34:21 tux kernel: saa7130/34: v4l2 driver version 0.2.14 loaded Oct 11 12:34:21 tux kernel: saa7133[0]: found at :02:04.0, rev: 209, irq: 21, latency: 32, mmio: 0xf1009000 Oct 11 12:34:21 tux kernel: saa7133[0]: subsystem: 17de:7352, board: Kworld ATSC110 [card=90,insmod option] Oct 11 12:34:21 tux kernel: saa7133[0]: board init: gpio is 100 Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 00: de 17 52 73 ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: tuner 1-0061: chip found @ 0xc2 (saa7133[0]) Oct 11 12:34:21 tux kernel: saa7133[0]: registered device video2 [v4l2] Oct 11 12:34:21 tux kernel: saa7133[0]: registered device vbi2 Oct 11 12:34:21 tux kernel: saa7133[1]: found at :02:09.0, rev: 209, irq: 17, latency: 32, mmio: 0xf100a000 Oct 11 12:34:21 tux kernel: saa7133[1]: subsystem: 17de:7352, board: Kworld ATSC110 [card=90,insmod option] Oct 11 12:34:21 tux kernel: saa7133[1]: board init: gpio is 100 Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 00: de 17 52 73 ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[1]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Oct 11 12:34:21 tux kernel: saa7133[1]: registered device video3 [v4l2] Oct 11 12:34:21 tux kernel: saa7133[1]: registered device vbi3 Oct 11 12:34:21 tux kernel: DVB: registering new adapter (saa7133[0]). Oct 11 12:34:21 tux kernel: DVB: registering new adapter (saa7133[1]). Oct 11 12:34:21 tux kernel: saa7134 ALSA driver for DMA sound loaded Oct 11 12:34:21 tux kernel: saa7133[0]/alsa: saa7133[0] at 0xf1009000 irq 21 registered as card 2 Oct 11 12:34:21 tux kernel: saa7133[1]/alsa: saa7133[1] at 0xf100a000 irq 17 registered as card 3 Notice the absence of an equivalent tuner 1-0061: chip found line for saa7133[1]. This occurs with both the 2.6.21 and 2.6.22.* kernels. I briefly tested analog and digital capture on both cards in a separate system before installing them in the MythTV backend so I don't suspect a hardware problem. Not being able to tune could explain not being able to to an analog capture. Could this be another case of probing being done by the various drivers causing problems? If so, has any of it been fixed in the recently released 2.6.23 kernel? I've already had to go back to the 2.6.21 series on this system because the probing caused a minor problem with the Hauppauge cards. The minor problem I mentioned earlier has to do with using the saa7134-alsa module to capture sound directly from the card. A quick glance at the driver source code looks like it shold support 32 and 48 kHz sampling rates. I've only been able to get 32 kHz working well so far with MythTV. Trying 48 kHz results in some sort of rate mismatch. Is 48 kHz supposed to work? David -- David Engel [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [RFC] TUV1236d / dvb-pll: rf input switching via module option
On Mon, Sep 10, 2007 at 12:12:01PM -0500, David Engel wrote:
Unfortunately, this does not allow for REVERSING the input selection --
this will only force it to use one or the other in digital mode. If
anybody has some ideas as to how to reverse the default selection in a
clean way, I am open to suggestions.
The attached patch, is completely untested (I didn't even try
compiling it), but it should be close.
Take two, with the patch.
David
--
David Engel
[EMAIL PROTECTED]
diff -r b7fa7c4598ac linux/drivers/media/dvb/frontends/dvb-pll.c
--- a/linux/drivers/media/dvb/frontends/dvb-pll.c Sun Sep 09 12:00:45 2007 -0400
+++ b/linux/drivers/media/dvb/frontends/dvb-pll.c Mon Sep 10 11:58:50 2007 -0500
@@ -49,9 +49,9 @@ module_param(debug, int, 0644);
module_param(debug, int, 0644);
MODULE_PARM_DESC(debug, enable verbose debug messages);
-static unsigned int input[DVB_PLL_MAX] = { [ 0 ... (DVB_PLL_MAX-1) ] = 0 };
+static int input[DVB_PLL_MAX] = { [ 0 ... (DVB_PLL_MAX-1) ] = 0 };
module_param_array(input, int, NULL, 0644);
-MODULE_PARM_DESC(input,specify rf input choice, 0 for autoselect (default));
+MODULE_PARM_DESC(input,specify rf input choice, 0 for autoselect (default), -1 for autoselect reversed);
static unsigned int id[DVB_PLL_MAX] =
{ [ 0 ... (DVB_PLL_MAX-1) ] = DVB_PLL_UNDEFINED };
@@ -399,9 +399,10 @@ static void tuv1236d_rf(struct dvb_front
const struct dvb_frontend_parameters *params)
{
struct dvb_pll_priv *priv = fe-tuner_priv;
- unsigned int new_rf = input[priv-nr];
-
- if ((new_rf == 0) || (new_rf 2)) {
+ int new_rf = input[priv-nr];
+
+ if ((new_rf = 0) || (new_rf 2)) {
+ int reverse = (new_rf == -1);
switch (params-u.vsb.modulation) {
case QAM_64:
case QAM_256:
@@ -411,6 +412,8 @@ static void tuv1236d_rf(struct dvb_front
default:
new_rf = 2;
}
+ if (reverse)
+ new_rf = 3 - new_rf;
}
switch (new_rf) {
@@ -856,6 +859,9 @@ struct dvb_frontend *dvb_pll_attach(stru
printk( %d-%04x, i2c_adapter_id(i2c), pll_addr);
printk(: tuner rf input will be );
switch (input[priv-nr]) {
+ case -1:
+ printk(autoselected reversed\n);
+ break;
case 0:
printk(autoselected\n);
break;
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [RFC] TUV1236d / dvb-pll: rf input switching via module option
On Mon, Sep 10, 2007 at 03:04:32PM -0400, Michael Krufky wrote: This is the same thing I did in my tree, but just didn't push it to the repository. This would work, but it doesn't cover all possible cases. For instance, what if there was a tuner with three rf inputs? I don't think that such a device exists on any supported hardware, but you never know. Yes, devices with three or more inputs would be really troublesome this way. An alternative would be to have separate modules parameters per modulation type. Instead of dvb_pll taking an input parameter, it could, for example, take qam_input and vsb_input parameters. That could work as long as the number of modulation types doesn't grow much more. This solution is fine with me, for the meanwhile... if you could test it, would be nice :-) I will, but it take a few to serveral days. David -- David Engel [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Swapping inputs on Kworld ATSC 11x
Now that I've gotten the basics working on my Kworld ATSC 115, it's on to what initially intrigued me about this card. That's the dual RF inputs. The standard driver as of Linux v2.6.21 does analog and 8VSB on the top input and QAM on the bottom input. My desired behavior is analog and QAM on one input and 8VSB on the other. No problem. It was an easy enough driver hack to make it do what I wanted. Others might be interested in this change too, so is there any willingness from the core DVB maintainers to accept a patch to make this configurable via a module parameter? If so, would you like one global setting for all cards or one setting for each card? David -- David Engel [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Swapping inputs on Kworld ATSC 11x
On Tue, Jun 12, 2007 at 11:17:44AM -0400, Michael Krufky wrote: If you have already written a patch to do this, please feel free to post it -- just know that dvb-pll is a moving target right now -- This will be over in a week or two. All I've done so far is a quick, one-liner to unconditionally change things for me. I wasn't going to bother making a clean, conditional version for outside consumption unless there was interest in accepting it. If you've already got something in the works, I'll just wait for it. Thanks for the quick response. David -- David Engel [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Kworld ATSC 115/nxt2004 firmware problem
On Mon, Jun 11, 2007 at 11:12:55AM +0200, Markus Rechberger wrote: compile the i2c framework as modules, then the error will go away. I already discussed this bug with other developers, and I'll submit a bugfix soon (it's a bug in the firmware class code which tries to create duplicate sysfs entries which already got created by the i2c-dev code) Thanks, Markus. That indeed did the trick. David -- David Engel [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Kworld ATSC 115/nxt2004 firmware problem
Hi, I just got a Kworld ATSC 115 to play around with and maybe eventually use with MythTV. The analog support appears to work just fine, but I'm having a problem loading the nxt2004 firmware for the digital support. I downloaded the dvb-fe-nxt2004.fw firmware fileusing the get_dvb_firmware script and put it in /lib/firmware, so I don't think missing firmware is the cause. [EMAIL PROTECTED] ll /lib/firmware ~ total 12 -rw-r--r-- 1 root root 9584 Jun 9 11:26 dvb-fe-nxt2004.fw Is the 9584 size correct? It seems rather small. Here is a snippet from my kernel log when loading the saa7134-dvb module and trying to do an atscscan. The kobject_add failure looks awfully suspicious to me and is probably the major problem. Jun 9 13:42:08 opus kernel: nxt200x: NXT2004 Detected Jun 9 13:42:08 opus kernel: DVB: registering new adapter (saa7133[0]). Jun 9 13:42:08 opus kernel: DVB: registering frontend 0 (Nextwave NXT200X VSB/QAM frontend)... Jun 9 13:42:33 opus kernel: nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)... Jun 9 13:42:33 opus kernel: kobject_add failed for i2c-2 with -EEXIST, don't try to register things with the same name in the same directory. Jun 9 13:42:33 opus kernel: [c01fc204] kobject_shadow_add+0x114/0x190 Jun 9 13:42:33 opus kernel: [c024d88f] device_add+0xbf/0x670 Jun 9 13:42:33 opus kernel: [c01fc2ef] kobject_init+0x2f/0x50 Jun 9 13:42:33 opus kernel: [f88771cb] _request_firmware+0x11b/0x360 [firmware_class] Jun 9 13:42:33 opus kernel: [f88774af] request_firmware+0xf/0x20 [firmware_class] Jun 9 13:42:33 opus kernel: [f8a1ab23] nxt200x_init+0xa3/0xc70 [nxt200x] Jun 9 13:42:33 opus kernel: [c0383091] __sched_text_start+0x301/0x960 Jun 9 13:42:33 opus kernel: [c03830bd] __sched_text_start+0x32d/0x960 Jun 9 13:42:33 opus kernel: [f8a0d51d] dvb_frontend_init+0x1d/0x60 [dvb_core] Jun 9 13:42:33 opus kernel: [c0114cf9] __wake_up_common+0x39/0x60 Jun 9 13:42:33 opus kernel: [f8a0e825] dvb_frontend_thread+0x65/0x2f0 [dvb_core] Jun 9 13:42:33 opus kernel: [c0115acf] complete+0x3f/0x60 Jun 9 13:42:33 opus kernel: [f8a0e7c0] dvb_frontend_thread+0x0/0x2f0 [dvb_core] Jun 9 13:42:33 opus kernel: [c012ec4a] kthread+0xba/0xf0 Jun 9 13:42:33 opus kernel: [c012eb90] kthread+0x0/0xf0 Jun 9 13:42:33 opus kernel: [c0103773] kernel_thread_helper+0x7/0x14 Jun 9 13:42:33 opus kernel: === Jun 9 13:42:33 opus kernel: fw_register_device: device_register failed Jun 9 13:42:33 opus kernel: nxt2004: Waiting for firmware upload(2)... Jun 9 13:42:33 opus kernel: nxt2004: No firmware uploaded (timeout or file not found?) Jun 9 13:42:33 opus kernel: nxt200x: Timeout waiting for nxt2004 to init. I tried googling for similar problem reports, but couldn't find any. Does anyone know what might be wrong? This was all done with the v2.6.21.4 Linux kernel. I can easily try other kernel versions or DVB drivers to test. David -- David Engel [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
