Kworld 115-No Analog Channels

Kworld 115-No Analog Channels

[Jason Pontious]

After getting upgraded to the latest v4l-dvb repository I am no longer able
to get any analog channels from my Kworld 115. (I finally broke down and
installed 2.6.25 kernel in Ubuntu).

Before I was getting analog channels via the top rf input.  Now I get no
channels regardless if i set atv_input tuner_simple module setting.  Digital
channels are not affected just analog in this.  I get no errors from dmesg.

Any Ideas?

Thanks!
Jason Pontious
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[David Engel]

On Thu, May 29, 2008 at 06:57:03PM -0400, Jason Pontious wrote:
> After getting upgraded to the latest v4l-dvb repository I am no longer able
> to get any analog channels from my Kworld 115. (I finally broke down and
> installed 2.6.25 kernel in Ubuntu).

Which drivers are you really using, 2.6.25 or latest v4l-dvb from
Mercurial?

> Before I was getting analog channels via the top rf input.  Now I get no
> channels regardless if i set atv_input tuner_simple module setting.  Digital
> channels are not affected just analog in this.  I get no errors from dmesg.
> 
> Any Ideas?

I ran into a similar (probably the same) problem last week.  My search
of the list archives revealed a known tuner detection regression in
2.6.25.  It's supposed to be fixed in Mercurial but I didn't test it
because it was simpler to just go back to 2.6.24.x.  I don't know why
the fix hasn't made it into 2.6.25.x yet.

David
-- 
David Engel
david@istwok.net

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[Jason Pontious]

On Fri, May 30, 2008 at 10:58 AM, David Engel <david@istwok.net> wrote:

> On Thu, May 29, 2008 at 06:57:03PM -0400, Jason Pontious wrote:
> > After getting upgraded to the latest v4l-dvb repository I am no longer
> able
> > to get any analog channels from my Kworld 115. (I finally broke down and
> > installed 2.6.25 kernel in Ubuntu).
>
> Which drivers are you really using, 2.6.25 or latest v4l-dvb from
> Mercurial?
>
> > Before I was getting analog channels via the top rf input.  Now I get no
> > channels regardless if i set atv_input tuner_simple module setting.
>  Digital
> > channels are not affected just analog in this.  I get no errors from
> dmesg.
> >
> > Any Ideas?
>
> I ran into a similar (probably the same) problem last week.  My search
> of the list archives revealed a known tuner detection regression in
> 2.6.25.  It's supposed to be fixed in Mercurial but I didn't test it
> because it was simpler to just go back to 2.6.24.x.  I don't know why
> the fix hasn't made it into 2.6.25.x yet.
>
> David
> --
> David Engel
> david@istwok.net



I am using the current v4l-dvb from mercurial as the latest there now has a
feature to allow you to select the rf input for analog channels which I
would like to have.  I upgraded to 2.6.25 in Ubuntu because of the way
Ubuntu is currenlty handling their kernel modules doesn't allow for an easy
compile of the drivers from mercurial.
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[David Engel]

On Fri, May 30, 2008 at 11:41:54AM -0400, Jason Pontious wrote:
> I am using the current v4l-dvb from mercurial as the latest there now has a
> feature to allow you to select the rf input for analog channels which I
> would like to have.  I upgraded to 2.6.25 in Ubuntu because of the way
> Ubuntu is currenlty handling their kernel modules doesn't allow for an easy
> compile of the drivers from mercurial.

I was not aware the input selection method had been changed again.
Thanks.  Now, I'll know to expect a conflict with my own hack when
this makes it into the mainline kernel.

Note to Michael Krufky.  I could be [probably am] missing something,
but to me it looks like there is no way to force the use of input 0
when QAM is used.

        case TUNER_PHILIPS_FCV1236D:
        {
                unsigned int new_rf;

                if (dtv_input[priv->nr])
                        new_rf = dtv_input[priv->nr];
                else
                        switch (params->u.vsb.modulation) {
                        case QAM_64:
                        case QAM_256:
                                new_rf = 1;
                                break;
                        case VSB_8:
                        default:
                                new_rf = 0;
                                break;
                        }
                simple_set_rf_input(fe, &buf[2], &buf[3], new_rf);
                break;
        }

If dtv_input is set to 0, it will be misinterpreted as autoselect and
then the use of QAM_64 or QAM_256 will make the code use input 1!

David
-- 
David Engel
david@istwok.net

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[Michael Krufky]

On Fri, May 30, 2008 at 1:18 PM, David Engel <david@istwok.net> wrote:
> On Fri, May 30, 2008 at 11:41:54AM -0400, Jason Pontious wrote:
>> I am using the current v4l-dvb from mercurial as the latest there now has a
>> feature to allow you to select the rf input for analog channels which I
>> would like to have.  I upgraded to 2.6.25 in Ubuntu because of the way
>> Ubuntu is currenlty handling their kernel modules doesn't allow for an easy
>> compile of the drivers from mercurial.
>
> I was not aware the input selection method had been changed again.
> Thanks.  Now, I'll know to expect a conflict with my own hack when
> this makes it into the mainline kernel.
>
> Note to Michael Krufky.  I could be [probably am] missing something,
> but to me it looks like there is no way to force the use of input 0
> when QAM is used.
>
>        case TUNER_PHILIPS_FCV1236D:
>        {
>                unsigned int new_rf;
>
>                if (dtv_input[priv->nr])
>                        new_rf = dtv_input[priv->nr];
>                else
>                        switch (params->u.vsb.modulation) {
>                        case QAM_64:
>                        case QAM_256:
>                                new_rf = 1;
>                                break;
>                        case VSB_8:
>                        default:
>                                new_rf = 0;
>                                break;
>                        }
>                simple_set_rf_input(fe, &buf[2], &buf[3], new_rf);
>                break;
>        }
>
> If dtv_input is set to 0, it will be misinterpreted as autoselect and
> then the use of QAM_64 or QAM_256 will make the code use input 1!


David,

"1" is tuner 1
"2" is tuner 2  (actually, "not one" is tuner "not one")
"0" is autoselect

-Mike

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[Michael Krufky]

On Fri, May 30, 2008 at 10:58 AM, David Engel <david@istwok.net> wrote:
> On Thu, May 29, 2008 at 06:57:03PM -0400, Jason Pontious wrote:
>> After getting upgraded to the latest v4l-dvb repository I am no longer able
>> to get any analog channels from my Kworld 115. (I finally broke down and
>> installed 2.6.25 kernel in Ubuntu).
>
> Which drivers are you really using, 2.6.25 or latest v4l-dvb from
> Mercurial?
>
>> Before I was getting analog channels via the top rf input.  Now I get no
>> channels regardless if i set atv_input tuner_simple module setting.  Digital
>> channels are not affected just analog in this.  I get no errors from dmesg.
>>
>> Any Ideas?
>
> I ran into a similar (probably the same) problem last week.  My search
> of the list archives revealed a known tuner detection regression in
> 2.6.25.  It's supposed to be fixed in Mercurial but I didn't test it
> because it was simpler to just go back to 2.6.24.x.  I don't know why
> the fix hasn't made it into 2.6.25.x yet.

Which fix?  What problem does it fix?  More details, please :-)

-Mike

P.S. ...  I respond quicker if you cc me.  ;-)  (I should have added
that to my last email, not this one)

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[Michael Krufky]

On Thu, May 29, 2008 at 6:57 PM, Jason Pontious <jpontious@gmail.com> wrote:
> After getting upgraded to the latest v4l-dvb repository I am no longer able
> to get any analog channels from my Kworld 115. (I finally broke down and
> installed 2.6.25 kernel in Ubuntu).
>
> Before I was getting analog channels via the top rf input.  Now I get no
> channels regardless if i set atv_input tuner_simple module setting.  Digital
> channels are not affected just analog in this.  I get no errors from dmesg.
>
> Any Ideas?

Set tuner-simple debug=1 -- this will cause the driver to tell you
which input is being used for what purpose at driver startup.  This
should help you to debug the issue on your end.

-Mike

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[David Engel]

On Sun, Jun 01, 2008 at 03:18:45AM -0400, Michael Krufky wrote:
> On Fri, May 30, 2008 at 10:58 AM, David Engel <david@istwok.net> wrote:
> > I ran into a similar (probably the same) problem last week.  My search
> > of the list archives revealed a known tuner detection regression in
> > 2.6.25.  It's supposed to be fixed in Mercurial but I didn't test it
> > because it was simpler to just go back to 2.6.24.x.  I don't know why
> > the fix hasn't made it into 2.6.25.x yet.
> 
> Which fix?  What problem does it fix?  More details, please :-)

When I ran into the problem last week, I went searching and ran across
this thread:

https://www.redhat.com/mailman/private/video4linux-list/2008-April/msg00221.html

I don't know if any of the posted patches or changes that eventually
went into mercurial fixed my problem or not.  Downgrading to 2.6.24.7
did fix the problem for me.  Since the above thread looked like the
same problem as mine, I figured I'd stick with 2.6.24.x until it got
fixed in 2.6.25.x or 2.6.26 comes out.

Here are the details concerning my problem.  When running 2.6.25.4,
analog capture on a Kworld ATSC 115 doesn't work with tvtime reporting
no signal.  Here is a snippet of my boot log with 2.6.25.4:

May 25 12:54:50 opus kernel: saa7130/34: v4l2 driver version 0.2.14 loaded
May 25 12:54:50 opus kernel: ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
May 25 12:54:50 opus kernel: ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 16
May 25 12:54:50 opus kernel: saa7133[0]: found at 0000:01:08.0, rev: 209, irq: 16, latency: 255, mmio: 0xfdeff000
May 25 12:54:50 opus kernel: saa7133[0]: subsystem: 17de:7352, board: Kworld ATSC110/115 [card=90,insmod option]
May 25 12:54:50 opus kernel: saa7133[0]: board init: gpio is 100
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 00: de 17 52 73 ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 12:54:50 opus kernel: usb 2-9: new low speed USB device using ohci_hcd and address 2
May 25 12:54:50 opus kernel: saa7133[0]: registered device video0 [v4l2]
May 25 12:54:50 opus kernel: saa7133[0]: registered device vbi0
May 25 12:54:50 opus kernel: ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
May 25 12:54:50 opus kernel: ACPI: PCI Interrupt 0000:00:06.1[B] -> Link [AAZA] -> GSI 22 (level, low) -> IRQ 22
May 25 12:54:50 opus kernel: PCI: Setting latency timer of device 0000:00:06.1 to 64
May 25 12:54:50 opus kernel: hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
May 25 12:54:50 opus kernel: usb 2-9: configuration #1 chosen from 1 choice
May 25 12:54:50 opus kernel: usbcore: registered new interface driver hiddev
May 25 12:54:50 opus kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:02.0/usb2/2-9/2-9:1.0/input/input5
May 25 12:54:50 opus kernel: input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:02.0-9
May 25 12:54:50 opus kernel: usbcore: registered new interface driver usbhid
May 25 12:54:50 opus kernel: drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
May 25 12:54:50 opus kernel: nxt200x: NXT2004 Detected
May 25 12:54:50 opus kernel: DVB: registering new adapter (saa7133[0])
May 25 12:54:50 opus kernel: DVB: registering frontend 0 (Nextwave NXT200X VSB/QAM frontend)...
May 25 12:54:50 opus kernel: nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
May 25 12:54:50 opus kernel: nxt2004: Waiting for firmware upload(2)...
May 25 12:54:50 opus kernel: Adding 2000084k swap on /dev/sda2.  Priority:-1 extents:1 across:2000084k
May 25 12:54:50 opus kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
May 25 12:54:50 opus kernel: EXT3 FS on sda1, internal journal
May 25 12:54:50 opus kernel: nxt2004: Firmware upload complete

Manually specifying the tuner type when loading the saa7134 module
makes no difference.

Booting with 2.6.24.7 fixes the problem.  Here is a snippet of the
boot log with 2.6.24.7:

May 25 14:01:27 opus kernel: saa7130/34: v4l2 driver version 0.2.14 loaded
May 25 14:01:27 opus kernel: forcedeth 0000:00:08.0: ifname eth0, PHY OUI 0x5043 @ 1, addr 00:e0:4d:1a:27:30
May 25 14:01:27 opus kernel: forcedeth 0000:00:08.0: highdma csum vlan pwrctl mgmt timirq gbit lnktim msi desc-v3
May 25 14:01:27 opus kernel: ACPI: PCI Interrupt Link [APCF] enabled at IRQ 20
May 25 14:01:27 opus kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 20 (level, low) -> IRQ 19
May 25 14:01:27 opus kernel: PCI: Setting latency timer of device 0000:00:02.0 to 64
May 25 14:01:27 opus kernel: ohci_hcd 0000:00:02.0: OHCI Host Controller
May 25 14:01:27 opus kernel: ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
May 25 14:01:27 opus kernel: ohci_hcd 0000:00:02.0: irq 19, io mem 0xfe02f000
May 25 14:01:27 opus kernel: usb usb1: configuration #1 chosen from 1 choice
May 25 14:01:27 opus kernel: hub 1-0:1.0: USB hub found
May 25 14:01:27 opus kernel: hub 1-0:1.0: 10 ports detected
May 25 14:01:27 opus kernel: ACPI: PCI Interrupt Link [APCL] enabled at IRQ 23
May 25 14:01:27 opus kernel: ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCL] -> GSI 23 (level, low) -> IRQ 16
May 25 14:01:27 opus kernel: PCI: Setting latency timer of device 0000:00:02.1 to 64
May 25 14:01:27 opus kernel: ehci_hcd 0000:00:02.1: EHCI Host Controller
May 25 14:01:27 opus kernel: ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2
May 25 14:01:27 opus kernel: ehci_hcd 0000:00:02.1: debug port 1
May 25 14:01:27 opus kernel: PCI: cache line size of 64 is not supported by device 0000:00:02.1
May 25 14:01:27 opus kernel: ehci_hcd 0000:00:02.1: irq 16, io mem 0xfe02e000
May 25 14:01:27 opus kernel: ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
May 25 14:01:27 opus kernel: usb usb2: configuration #1 chosen from 1 choice
May 25 14:01:27 opus kernel: hub 2-0:1.0: USB hub found
May 25 14:01:27 opus kernel: hub 2-0:1.0: 10 ports detected
May 25 14:01:27 opus kernel: ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
May 25 14:01:27 opus kernel: ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 20
May 25 14:01:27 opus kernel: saa7133[0]: found at 0000:01:08.0, rev: 209, irq: 20, latency: 255, mmio: 0xfdeff000
May 25 14:01:27 opus kernel: saa7133[0]: subsystem: 17de:7352, board: Kworld ATSC110/115 [card=90,autodetected]
May 25 14:01:27 opus kernel: saa7133[0]: board init: gpio is 100
May 25 14:01:27 opus kernel: saa7133[0]: i2c eeprom 00: de 17 52 73 ff ff ff ff ff ff ff ff ff ff ff ff
May 25 14:01:27 opus kernel: saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 14:01:27 opus kernel: saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 14:01:27 opus kernel: saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 14:01:27 opus kernel: saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 14:01:27 opus kernel: saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 14:01:27 opus kernel: saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 14:01:27 opus kernel: saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
May 25 14:01:27 opus kernel: tuner 2-0061: chip found @ 0xc2 (saa7133[0])
May 25 14:01:27 opus kernel: tuner-simple 2-0061: type set to 68 (Philips TUV1236D ATSC/NTSC dual in)
May 25 14:01:27 opus kernel: tuner 2-0061: type set to Philips TUV1236D AT
May 25 14:01:27 opus kernel: tuner-simple 2-0061: type set to 68 (Philips TUV1236D ATSC/NTSC dual in)
May 25 14:01:27 opus kernel: tuner 2-0061: type set to Philips TUV1236D AT
May 25 14:01:27 opus kernel: saa7133[0]: registered device video0 [v4l2]
May 25 14:01:27 opus kernel: saa7133[0]: registered device vbi0
May 25 14:01:27 opus kernel: ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
May 25 14:01:27 opus kernel: ACPI: PCI Interrupt 0000:00:06.1[B] -> Link [AAZA] -> GSI 22 (level, low) -> IRQ 17
May 25 14:01:27 opus kernel: PCI: Setting latency timer of device 0000:00:06.1 to 64
May 25 14:01:27 opus kernel: hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
May 25 14:01:27 opus kernel: nxt200x: NXT2004 Detected
May 25 14:01:27 opus kernel: DVB: registering new adapter (saa7133[0])
May 25 14:01:27 opus kernel: DVB: registering frontend 0 (Nextwave NXT200X VSB/QAM frontend)...
May 25 14:01:27 opus kernel: nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
May 25 14:01:27 opus kernel: nxt2004: Waiting for firmware upload(2)...
May 25 14:01:27 opus kernel: usb 1-9: new low speed USB device using ohci_hcd and address 2
May 25 14:01:27 opus kernel: usb 1-9: configuration #1 chosen from 1 choice
May 25 14:01:27 opus kernel: usbcore: registered new interface driver hiddev
May 25 14:01:27 opus kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:02.0/usb1/1-9/1-9:1.0/input/input5
May 25 14:01:27 opus kernel: input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:02.0-9
May 25 14:01:27 opus kernel: usbcore: registered new interface driver usbhid
May 25 14:01:27 opus kernel: drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
May 25 14:01:27 opus kernel: nxt2004: Firmware upload complete
May 25 14:01:27 opus kernel: nxt200x: Timeout waiting for nxt2004 to init.

Notice the additional log entries regarding the tuner detection.

FWIW, I have another system with 2 KWorld ATSC 115s.  That system has
always had issues with tuner detection no what kernel I use.
Depending on which PCI slots I place the cards in, I either get 0 or 1
tuners detected, but never 2.  I posted about that problem several
months ago, but never got a response from anyone.

David
-- 
David Engel
david@istwok.net

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[David Engel]

On Sun, Jun 01, 2008 at 03:15:30AM -0400, Michael Krufky wrote:
> On Fri, May 30, 2008 at 1:18 PM, David Engel <david@istwok.net> wrote:
> > If dtv_input is set to 0, it will be misinterpreted as autoselect and
> > then the use of QAM_64 or QAM_256 will make the code use input 1!
> 
> "1" is tuner 1
> "2" is tuner 2  (actually, "not one" is tuner "not one")
> "0" is autoselect

Ah, OK.  Thanks for clarifying.

David
-- 
David Engel
david@istwok.net

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[Michael Krufky]

David,

On Sun, Jun 1, 2008 at 3:03 PM, David Engel <david@istwok.net> wrote:
> On Sun, Jun 01, 2008 at 03:18:45AM -0400, Michael Krufky wrote:
>> On Fri, May 30, 2008 at 10:58 AM, David Engel <david@istwok.net> wrote:
>> > I ran into a similar (probably the same) problem last week.  My search
>> > of the list archives revealed a known tuner detection regression in
>> > 2.6.25.  It's supposed to be fixed in Mercurial but I didn't test it
>> > because it was simpler to just go back to 2.6.24.x.  I don't know why
>> > the fix hasn't made it into 2.6.25.x yet.
>>
>> Which fix?  What problem does it fix?  More details, please :-)
>
> When I ran into the problem last week, I went searching and ran across
> this thread:
>
> https://www.redhat.com/mailman/private/video4linux-list/2008-April/msg00221.html

This is in the private archives...  Do you have a link from gmane or
some other public archive?

> I don't know if any of the posted patches or changes that eventually
> went into mercurial fixed my problem or not.  Downgrading to 2.6.24.7
> did fix the problem for me.  Since the above thread looked like the
> same problem as mine, I figured I'd stick with 2.6.24.x until it got
> fixed in 2.6.25.x or 2.6.26 comes out.
>
> Here are the details concerning my problem.  When running 2.6.25.4,
> analog capture on a Kworld ATSC 115 doesn't work with tvtime reporting
> no signal.  Here is a snippet of my boot log with 2.6.25.4:
>
> May 25 12:54:50 opus kernel: saa7130/34: v4l2 driver version 0.2.14 loaded
> May 25 12:54:50 opus kernel: ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
> May 25 12:54:50 opus kernel: ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 16
> May 25 12:54:50 opus kernel: saa7133[0]: found at 0000:01:08.0, rev: 209, irq: 16, latency: 255, mmio: 0xfdeff000
> May 25 12:54:50 opus kernel: saa7133[0]: subsystem: 17de:7352, board: Kworld ATSC110/115 [card=90,insmod option]
> May 25 12:54:50 opus kernel: saa7133[0]: board init: gpio is 100
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 00: de 17 52 73 ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> May 25 12:54:50 opus kernel: usb 2-9: new low speed USB device using ohci_hcd and address 2
> May 25 12:54:50 opus kernel: saa7133[0]: registered device video0 [v4l2]
> May 25 12:54:50 opus kernel: saa7133[0]: registered device vbi0
> May 25 12:54:50 opus kernel: ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
> May 25 12:54:50 opus kernel: ACPI: PCI Interrupt 0000:00:06.1[B] -> Link [AAZA] -> GSI 22 (level, low) -> IRQ 22
> May 25 12:54:50 opus kernel: PCI: Setting latency timer of device 0000:00:06.1 to 64
> May 25 12:54:50 opus kernel: hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
> May 25 12:54:50 opus kernel: usb 2-9: configuration #1 chosen from 1 choice
> May 25 12:54:50 opus kernel: usbcore: registered new interface driver hiddev
> May 25 12:54:50 opus kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:02.0/usb2/2-9/2-9:1.0/input/input5
> May 25 12:54:50 opus kernel: input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:02.0-9
> May 25 12:54:50 opus kernel: usbcore: registered new interface driver usbhid
> May 25 12:54:50 opus kernel: drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
> May 25 12:54:50 opus kernel: nxt200x: NXT2004 Detected
> May 25 12:54:50 opus kernel: DVB: registering new adapter (saa7133[0])
> May 25 12:54:50 opus kernel: DVB: registering frontend 0 (Nextwave NXT200X VSB/QAM frontend)...
> May 25 12:54:50 opus kernel: nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
> May 25 12:54:50 opus kernel: nxt2004: Waiting for firmware upload(2)...
> May 25 12:54:50 opus kernel: Adding 2000084k swap on /dev/sda2.  Priority:-1 extents:1 across:2000084k
> May 25 12:54:50 opus kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
> May 25 12:54:50 opus kernel: EXT3 FS on sda1, internal journal
> May 25 12:54:50 opus kernel: nxt2004: Firmware upload complete
>
> Manually specifying the tuner type when loading the saa7134 module
> makes no difference.

Under 2.6.25, can you confirm whether or not the "tuner" module is
actually loaded?  If it is loaded, can you do:

modprobe -r tuner
modprobe -r tuner-simple
modprobe tuner-simple debug=1
modprobe tuner debug=1

...then test again and show the dmesg logs.

Regards,

Mike

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[hermann pitton]

Mike,

Am Sonntag, den 01.06.2008, 15:10 -0400 schrieb Michael Krufky:
> David,
> 
> On Sun, Jun 1, 2008 at 3:03 PM, David Engel <david@istwok.net> wrote:
> > On Sun, Jun 01, 2008 at 03:18:45AM -0400, Michael Krufky wrote:
> >> On Fri, May 30, 2008 at 10:58 AM, David Engel <david@istwok.net> wrote:
> >> > I ran into a similar (probably the same) problem last week.  My search
> >> > of the list archives revealed a known tuner detection regression in
> >> > 2.6.25.  It's supposed to be fixed in Mercurial but I didn't test it
> >> > because it was simpler to just go back to 2.6.24.x.  I don't know why
> >> > the fix hasn't made it into 2.6.25.x yet.
> >>
> >> Which fix?  What problem does it fix?  More details, please :-)
> >
> > When I ran into the problem last week, I went searching and ran across
> > this thread:
> >
> > https://www.redhat.com/mailman/private/video4linux-list/2008-April/msg00221.html
> 
> This is in the private archives...  Do you have a link from gmane or
> some other public archive?

it is the first posting from Ian Pickworth there, followed by an reply
by me, since Ian helped on several cx88 norm setting issues and also
with the tda9887 radio support, you might not remember anymore, but to
leave him without reply is beyond my scope.

The bug was confirmed then by Gert, who did the initial empress encoder
support.

However, Mauro fixed the eeprom detection then within all that immense
traffic and work during the last merge window open.

Remaining serious issues are, since 2.6.25 the users can't select the
PAL/SECAM subnorms anymore after the ioctl2 conversion, which is an
extremely bad idea on saa713x, and further it is more improved on 2.6.26
now, that they are not even to set the tuner type anymore, without to
change it in the source, which is another extremely bad idea, as I
posted several times.

I don't blame anyone, Hartmut and me were also too much focused on the
outstanding DVB-S stuff that time and did not care much about analog,
but the driver is in serious troubles now and I'm a little bit grumpy,
or at least not in the mood to explain again and again were we are ...

Cheers,
Hermann

> > I don't know if any of the posted patches or changes that eventually
> > went into mercurial fixed my problem or not.  Downgrading to 2.6.24.7
> > did fix the problem for me.  Since the above thread looked like the
> > same problem as mine, I figured I'd stick with 2.6.24.x until it got
> > fixed in 2.6.25.x or 2.6.26 comes out.
> >
> > Here are the details concerning my problem.  When running 2.6.25.4,
> > analog capture on a Kworld ATSC 115 doesn't work with tvtime reporting
> > no signal.  Here is a snippet of my boot log with 2.6.25.4:
> >
> > May 25 12:54:50 opus kernel: saa7130/34: v4l2 driver version 0.2.14 loaded
> > May 25 12:54:50 opus kernel: ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
> > May 25 12:54:50 opus kernel: ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 16
> > May 25 12:54:50 opus kernel: saa7133[0]: found at 0000:01:08.0, rev: 209, irq: 16, latency: 255, mmio: 0xfdeff000
> > May 25 12:54:50 opus kernel: saa7133[0]: subsystem: 17de:7352, board: Kworld ATSC110/115 [card=90,insmod option]
> > May 25 12:54:50 opus kernel: saa7133[0]: board init: gpio is 100
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 00: de 17 52 73 ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > May 25 12:54:50 opus kernel: usb 2-9: new low speed USB device using ohci_hcd and address 2
> > May 25 12:54:50 opus kernel: saa7133[0]: registered device video0 [v4l2]
> > May 25 12:54:50 opus kernel: saa7133[0]: registered device vbi0
> > May 25 12:54:50 opus kernel: ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
> > May 25 12:54:50 opus kernel: ACPI: PCI Interrupt 0000:00:06.1[B] -> Link [AAZA] -> GSI 22 (level, low) -> IRQ 22
> > May 25 12:54:50 opus kernel: PCI: Setting latency timer of device 0000:00:06.1 to 64
> > May 25 12:54:50 opus kernel: hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
> > May 25 12:54:50 opus kernel: usb 2-9: configuration #1 chosen from 1 choice
> > May 25 12:54:50 opus kernel: usbcore: registered new interface driver hiddev
> > May 25 12:54:50 opus kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:02.0/usb2/2-9/2-9:1.0/input/input5
> > May 25 12:54:50 opus kernel: input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:02.0-9
> > May 25 12:54:50 opus kernel: usbcore: registered new interface driver usbhid
> > May 25 12:54:50 opus kernel: drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
> > May 25 12:54:50 opus kernel: nxt200x: NXT2004 Detected
> > May 25 12:54:50 opus kernel: DVB: registering new adapter (saa7133[0])
> > May 25 12:54:50 opus kernel: DVB: registering frontend 0 (Nextwave NXT200X VSB/QAM frontend)...
> > May 25 12:54:50 opus kernel: nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
> > May 25 12:54:50 opus kernel: nxt2004: Waiting for firmware upload(2)...
> > May 25 12:54:50 opus kernel: Adding 2000084k swap on /dev/sda2.  Priority:-1 extents:1 across:2000084k
> > May 25 12:54:50 opus kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
> > May 25 12:54:50 opus kernel: EXT3 FS on sda1, internal journal
> > May 25 12:54:50 opus kernel: nxt2004: Firmware upload complete
> >
> > Manually specifying the tuner type when loading the saa7134 module
> > makes no difference.
> 
> Under 2.6.25, can you confirm whether or not the "tuner" module is
> actually loaded?  If it is loaded, can you do:
> 
> modprobe -r tuner
> modprobe -r tuner-simple
> modprobe tuner-simple debug=1
> modprobe tuner debug=1
> 
> ...then test again and show the dmesg logs.
> 
> Regards,
> 
> Mike
> 


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[David Engel]

On Sun, Jun 01, 2008 at 03:10:21PM -0400, Michael Krufky wrote:
> On Sun, Jun 1, 2008 at 3:03 PM, David Engel <david@istwok.net> wrote:
> > https://www.redhat.com/mailman/private/video4linux-list/2008-April/msg00221.html
> 
> This is in the private archives...  Do you have a link from gmane or
> some other public archive?

http://lists-archives.org/video4linux/22351-hauppauge-wintv-regreession-from-2-6-24-to-2-6-25.html

> Under 2.6.25, can you confirm whether or not the "tuner" module is
> actually loaded?  If it is loaded, can you do:

Yes, the tuner module is loaded with a clean boot of 2.6.25.  The
output from "lsmod | grep tuner" is:

tuner                  34656  0 
tea5767                 6020  1 tuner
tda8290                12292  1 tuner
tuner_xc2028           18960  1 tuner
firmware_class          7040  3 nxt200x,saa7134_dvb,tuner_xc2028
tda9887                 9092  1 tuner
tuner_simple            8584  1 tuner
mt20xx                 11784  1 tuner
tea5761                 4612  1 tuner
videodev               30976  2 tuner,saa7134
v4l2_common             9856  2 tuner,saa7134
i2c_core               18836  18 nvidia,dvb_pll,nxt200x,saa7134_dvb,tuner,tea5767,tda8290,tda827x,tuner_xc2028,tda9887,tuner_simple,mt20xx,tea5761,saa7134,v4l2_common,ir_kbd_i2c,tveeprom,i2c_nforce2

> modprobe -r tuner
> modprobe -r tuner-simple
> modprobe tuner-simple debug=1
> modprobe tuner debug=1
> 
> ...then test again and show the dmesg logs.

Here are the logs:

Jun  1 15:52:36 opus kernel: tuner' 2-0043: chip found @ 0x86 (saa7133[0])
Jun  1 15:52:36 opus kernel: tda9887 2-0043: tda988[5/6/7] found
Jun  1 15:52:36 opus kernel: tuner' 2-0043: type set to tda9887
Jun  1 15:52:36 opus kernel: tuner' 2-0043: tv freq set to 0.00
Jun  1 15:52:36 opus kernel: tuner' 2-0043: TV freq (0.00) out of range (44-958)
Jun  1 15:52:36 opus kernel: tuner' 2-0043: saa7133[0] tuner' I2C addr 0x86 with type 74 used for 0x0e
Jun  1 15:52:36 opus kernel: tuner' 2-0043: Calling set_type_addr for type=68, addr=0xff, mode=0x04, config=0x00
Jun  1 15:52:36 opus kernel: tuner' 2-0043: set addr for type 74
Jun  1 15:52:36 opus kernel: tuner' 2-0061: Setting mode_mask to 0x0e
Jun  1 15:52:36 opus kernel: tuner' 2-0061: chip found @ 0xc2 (saa7133[0])
Jun  1 15:52:36 opus kernel: tuner' 2-0061: tuner 0x61: Tuner type absent
Jun  1 15:52:36 opus kernel: tuner' 2-0061: Calling set_type_addr for type=68, addr=0xff, mode=0x04, config=0x00
Jun  1 15:52:36 opus kernel: tuner' 2-0061: set addr for type -1
Jun  1 15:52:36 opus kernel: tuner' 2-0061: defining GPIO callback
Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: type set to 68 (Philips TUV1236D ATSC/NTSC dual in)
Jun  1 15:52:36 opus kernel: tuner' 2-0061: type set to Philips TUV1236D AT
Jun  1 15:52:36 opus kernel: tuner' 2-0061: tv freq set to 400.00
Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: IFPCoff = 623: tuner_t_params undefined for tuner 68
Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: tv: param 0, range 1
Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: Freq= 400.00 MHz, V_IF=38.93 MHz, Offset=0.00 MHz, div=7023
Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: tv 0x1b 0x6f 0xce 0x02
Jun  1 15:52:36 opus kernel: tuner' 2-0061: saa7133[0] tuner' I2C addr 0xc2 with type 68 used for 0x0e

The tuner is detected this time and analog capture works.

David
-- 
David Engel
david@istwok.net

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[Michael Krufky]

On Sun, Jun 1, 2008 at 4:46 PM, hermann pitton <hermann-pitton@arcor.de> wrote:
> Am Sonntag, den 01.06.2008, 15:10 -0400 schrieb Michael Krufky:
>> On Sun, Jun 1, 2008 at 3:03 PM, David Engel <david@istwok.net> wrote:
>> > On Sun, Jun 01, 2008 at 03:18:45AM -0400, Michael Krufky wrote:
>> >> On Fri, May 30, 2008 at 10:58 AM, David Engel <david@istwok.net> wrote:
>> >> > I ran into a similar (probably the same) problem last week.  My search
>> >> > of the list archives revealed a known tuner detection regression in
>> >> > 2.6.25.  It's supposed to be fixed in Mercurial but I didn't test it
>> >> > because it was simpler to just go back to 2.6.24.x.  I don't know why
>> >> > the fix hasn't made it into 2.6.25.x yet.
>> >>
>> >> Which fix?  What problem does it fix?  More details, please :-)
>> >
>> > When I ran into the problem last week, I went searching and ran across
>> > this thread:
>> >
>> > https://www.redhat.com/mailman/private/video4linux-list/2008-April/msg00221.html
>>
>> This is in the private archives...  Do you have a link from gmane or
>> some other public archive?
>
> it is the first posting from Ian Pickworth there, followed by an reply
> by me, since Ian helped on several cx88 norm setting issues and also
> with the tda9887 radio support, you might not remember anymore, but to
> leave him without reply is beyond my scope.
>
> The bug was confirmed then by Gert, who did the initial empress encoder
> support.
>
> However, Mauro fixed the eeprom detection then within all that immense
> traffic and work during the last merge window open.
>
> Remaining serious issues are, since 2.6.25 the users can't select the
> PAL/SECAM subnorms anymore after the ioctl2 conversion, which is an
> extremely bad idea on saa713x, and further it is more improved on 2.6.26
> now, that they are not even to set the tuner type anymore, without to
> change it in the source, which is another extremely bad idea, as I
> posted several times.
>
> I don't blame anyone, Hartmut and me were also too much focused on the
> outstanding DVB-S stuff that time and did not care much about analog,
> but the driver is in serious troubles now and I'm a little bit grumpy,
> or at least not in the mood to explain again and again were we are ...

Hermann,

Please don't top-post.

David Engel's problem is unrelated to the issue that you describe -- I
will address his issue in a separate email.

The issue that you are describing is due to the change in load order
during initialization.  Mauro made this change very late in the
2.6.25-rc stages, against my recommendation.

I am staying away from this issue, since I advised against that
change.  So, I defer to Mauro (cc added).

Mauro, are you aware that this is still an issue?

...some helpful hints:

this will not work unless we do the following, in this order:

#1 bring up the i2c bus
#2 allow tveeprom.ko client module to attach, so that
(bridgedriver)_card_setup can read tuner info from tveeprom
#3 allow tuner.ko client to attach

We must not call SET_TYPE until after all of the above have completed.

-Mike

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[Michael Krufky]

On Sun, Jun 1, 2008 at 4:55 PM, David Engel <david@istwok.net> wrote:
> On Sun, Jun 01, 2008 at 03:10:21PM -0400, Michael Krufky wrote:
>> On Sun, Jun 1, 2008 at 3:03 PM, David Engel <david@istwok.net> wrote:
>> > https://www.redhat.com/mailman/private/video4linux-list/2008-April/msg00221.html
>>
>> This is in the private archives...  Do you have a link from gmane or
>> some other public archive?
>
> http://lists-archives.org/video4linux/22351-hauppauge-wintv-regreession-from-2-6-24-to-2-6-25.html
>
>> Under 2.6.25, can you confirm whether or not the "tuner" module is
>> actually loaded?  If it is loaded, can you do:
>
> Yes, the tuner module is loaded with a clean boot of 2.6.25.  The
> output from "lsmod | grep tuner" is:
>
> tuner                  34656  0
> tea5767                 6020  1 tuner
> tda8290                12292  1 tuner
> tuner_xc2028           18960  1 tuner
> firmware_class          7040  3 nxt200x,saa7134_dvb,tuner_xc2028
> tda9887                 9092  1 tuner
> tuner_simple            8584  1 tuner
> mt20xx                 11784  1 tuner
> tea5761                 4612  1 tuner
> videodev               30976  2 tuner,saa7134
> v4l2_common             9856  2 tuner,saa7134
> i2c_core               18836  18 nvidia,dvb_pll,nxt200x,saa7134_dvb,tuner,tea5767,tda8290,tda827x,tuner_xc2028,tda9887,tuner_simple,mt20xx,tea5761,saa7134,v4l2_common,ir_kbd_i2c,tveeprom,i2c_nforce2
>
>> modprobe -r tuner
>> modprobe -r tuner-simple
>> modprobe tuner-simple debug=1
>> modprobe tuner debug=1
>>
>> ...then test again and show the dmesg logs.
>
> Here are the logs:
>
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: chip found @ 0x86 (saa7133[0])
> Jun  1 15:52:36 opus kernel: tda9887 2-0043: tda988[5/6/7] found
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: type set to tda9887
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: tv freq set to 0.00
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: TV freq (0.00) out of range (44-958)
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: saa7133[0] tuner' I2C addr 0x86 with type 74 used for 0x0e
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: Calling set_type_addr for type=68, addr=0xff, mode=0x04, config=0x00
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: set addr for type 74
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: Setting mode_mask to 0x0e
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: chip found @ 0xc2 (saa7133[0])
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: tuner 0x61: Tuner type absent
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: Calling set_type_addr for type=68, addr=0xff, mode=0x04, config=0x00
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: set addr for type -1
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: defining GPIO callback
> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: type set to 68 (Philips TUV1236D ATSC/NTSC dual in)
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: type set to Philips TUV1236D AT
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: tv freq set to 400.00
> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: IFPCoff = 623: tuner_t_params undefined for tuner 68
> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: tv: param 0, range 1
> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: Freq= 400.00 MHz, V_IF=38.93 MHz, Offset=0.00 MHz, div=7023
> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: tv 0x1b 0x6f 0xce 0x02
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: saa7133[0] tuner' I2C addr 0xc2 with type 68 used for 0x0e
>
> The tuner is detected this time and analog capture works.

David,

The fact that reloading tuner.ko confirms my suspicion --

In the case of the ATSC110 / ATSC115, we can't attach the tuner client
module until after the NXT2004 has been initialized with its i2c gate
left in open state.

If you unload all v4l/dvb drivers and modprobe saa7134, I believe this
will work properly, since the demod has already been initialized once,
with the gate left open by default.

So, that's a workaround to your problem.  When I find some spare time,
I'll investigate into what changed in 2.6.25 that led to this issue.
This is *not* the same issue that Hermann described in his mail.

-Mike

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[Mauro Carvalho Chehab]

On Mon, 2 Jun 2008 16:04:49 -0400
"Michael Krufky" <mkrufky@linuxtv.org> wrote:

> On Sun, Jun 1, 2008 at 4:46 PM, hermann pitton <hermann-pitton@arcor.de> wrote:
> > Am Sonntag, den 01.06.2008, 15:10 -0400 schrieb Michael Krufky:
> >> On Sun, Jun 1, 2008 at 3:03 PM, David Engel <david@istwok.net> wrote:
> >> > On Sun, Jun 01, 2008 at 03:18:45AM -0400, Michael Krufky wrote:
> >> >> On Fri, May 30, 2008 at 10:58 AM, David Engel <david@istwok.net> wrote:
> >> >> > I ran into a similar (probably the same) problem last week.  My search
> >> >> > of the list archives revealed a known tuner detection regression in
> >> >> > 2.6.25.  It's supposed to be fixed in Mercurial but I didn't test it
> >> >> > because it was simpler to just go back to 2.6.24.x.  I don't know why
> >> >> > the fix hasn't made it into 2.6.25.x yet.
> >> >>
> >> >> Which fix?  What problem does it fix?  More details, please :-)
> >> >
> >> > When I ran into the problem last week, I went searching and ran across
> >> > this thread:
> >> >
> >> > https://www.redhat.com/mailman/private/video4linux-list/2008-April/msg00221.html
> >>
> >> This is in the private archives...  Do you have a link from gmane or
> >> some other public archive?
> >
> > it is the first posting from Ian Pickworth there, followed by an reply
> > by me, since Ian helped on several cx88 norm setting issues and also
> > with the tda9887 radio support, you might not remember anymore, but to
> > leave him without reply is beyond my scope.
> >
> > The bug was confirmed then by Gert, who did the initial empress encoder
> > support.
> >
> > However, Mauro fixed the eeprom detection then within all that immense
> > traffic and work during the last merge window open.
> >
> > Remaining serious issues are, since 2.6.25 the users can't select the
> > PAL/SECAM subnorms anymore after the ioctl2 conversion, which is an
> > extremely bad idea on saa713x, and further it is more improved on 2.6.26
> > now, that they are not even to set the tuner type anymore, without to
> > change it in the source, which is another extremely bad idea, as I
> > posted several times.
> >
> > I don't blame anyone, Hartmut and me were also too much focused on the
> > outstanding DVB-S stuff that time and did not care much about analog,
> > but the driver is in serious troubles now and I'm a little bit grumpy,
> > or at least not in the mood to explain again and again were we are ...
> 
> Hermann,
> 
> Please don't top-post.
> 
> David Engel's problem is unrelated to the issue that you describe -- I
> will address his issue in a separate email.
> 
> The issue that you are describing is due to the change in load order
> during initialization.  Mauro made this change very late in the
> 2.6.25-rc stages, against my recommendation.
> 
> I am staying away from this issue, since I advised against that
> change.  So, I defer to Mauro (cc added).
> 
> Mauro, are you aware that this is still an issue?
> 
> ...some helpful hints:
> 
> this will not work unless we do the following, in this order:
> 
> #1 bring up the i2c bus
> #2 allow tveeprom.ko client module to attach, so that
> (bridgedriver)_card_setup can read tuner info from tveeprom
> #3 allow tuner.ko client to attach
> 
> We must not call SET_TYPE until after all of the above have completed.

This won't work, since tveeprom and tuner can be compiled in kernel or they may
already be loaded (for example, if you have two boards on your machine with
different bridges, the second bridge setup will run after the load of those
modules). 

We can postpone the call of SET_TYPE, or allow that a second SET_TYPE to be
accepted, but we can't make any assumption about the module load order.

If, previously, the driver were assuming a that I2C drivers were compiled
as module, and a certain load order, the driver were already broken.

The problem is not related to when a driver is loaded, but when I2C binding
happens.

Since we are using the old probe methods on most boards, after I2C is
initialized by the bridge, any existing i2c driver will try to bind on it.
Also, there's no control on the order that each i2c driver will be attached to
the i2c bus.

The proper fix is to migrate all drivers to the way that ivtv and cx18 are
probing i2c devices. This way, we can control when I2C bind for tveeprom and
for tuner will happen. So, we can do what you are meaning: bind first tveeprom,
then do the proper card setup and bind the tuner.

Cheers,
Mauro

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[hermann pitton]

Am Montag, den 02.06.2008, 17:51 -0300 schrieb Mauro Carvalho Chehab:
> On Mon, 2 Jun 2008 16:04:49 -0400
> "Michael Krufky" <mkrufky@linuxtv.org> wrote:
> 
> > On Sun, Jun 1, 2008 at 4:46 PM, hermann pitton <hermann-pitton@arcor.de> wrote:
> > > Am Sonntag, den 01.06.2008, 15:10 -0400 schrieb Michael Krufky:
> > >> On Sun, Jun 1, 2008 at 3:03 PM, David Engel <david@istwok.net> wrote:
> > >> > On Sun, Jun 01, 2008 at 03:18:45AM -0400, Michael Krufky wrote:
> > >> >> On Fri, May 30, 2008 at 10:58 AM, David Engel <david@istwok.net> wrote:
> > >> >> > I ran into a similar (probably the same) problem last week.  My search
> > >> >> > of the list archives revealed a known tuner detection regression in
> > >> >> > 2.6.25.  It's supposed to be fixed in Mercurial but I didn't test it
> > >> >> > because it was simpler to just go back to 2.6.24.x.  I don't know why
> > >> >> > the fix hasn't made it into 2.6.25.x yet.
> > >> >>
> > >> >> Which fix?  What problem does it fix?  More details, please :-)
> > >> >
> > >> > When I ran into the problem last week, I went searching and ran across
> > >> > this thread:
> > >> >
> > >> > https://www.redhat.com/mailman/private/video4linux-list/2008-April/msg00221.html
> > >>
> > >> This is in the private archives...  Do you have a link from gmane or
> > >> some other public archive?
> > >
> > > it is the first posting from Ian Pickworth there, followed by an reply
> > > by me, since Ian helped on several cx88 norm setting issues and also
> > > with the tda9887 radio support, you might not remember anymore, but to
> > > leave him without reply is beyond my scope.
> > >
> > > The bug was confirmed then by Gert, who did the initial empress encoder
> > > support.
> > >
> > > However, Mauro fixed the eeprom detection then within all that immense
> > > traffic and work during the last merge window open.
> > >
> > > Remaining serious issues are, since 2.6.25 the users can't select the
> > > PAL/SECAM subnorms anymore after the ioctl2 conversion, which is an
> > > extremely bad idea on saa713x, and further it is more improved on 2.6.26
> > > now, that they are not even to set the tuner type anymore, without to
> > > change it in the source, which is another extremely bad idea, as I
> > > posted several times.
> > >
> > > I don't blame anyone, Hartmut and me were also too much focused on the
> > > outstanding DVB-S stuff that time and did not care much about analog,
> > > but the driver is in serious troubles now and I'm a little bit grumpy,
> > > or at least not in the mood to explain again and again were we are ...
> > 
> > Hermann,
> > 
> > Please don't top-post.

No, I didn't.

I only used/abused exactly this to point at the outstanding issues
again, or do you seriously assume that I don't know that the Kworld ATSC
stuff is not within eeprom tuner detection issues on saa7134?

> > 
> > David Engel's problem is unrelated to the issue that you describe -- I
> > will address his issue in a separate email.
> > 
> > The issue that you are describing is due to the change in load order
> > during initialization.  Mauro made this change very late in the
> > 2.6.25-rc stages, against my recommendation.
> > 
> > I am staying away from this issue, since I advised against that
> > change.  So, I defer to Mauro (cc added).
> > 
> > Mauro, are you aware that this is still an issue?
> > 
> > ...some helpful hints:
> > 
> > this will not work unless we do the following, in this order:
> > 
> > #1 bring up the i2c bus
> > #2 allow tveeprom.ko client module to attach, so that
> > (bridgedriver)_card_setup can read tuner info from tveeprom
> > #3 allow tuner.ko client to attach
> > 
> > We must not call SET_TYPE until after all of the above have completed.
> 
> This won't work, since tveeprom and tuner can be compiled in kernel or they may
> already be loaded (for example, if you have two boards on your machine with
> different bridges, the second bridge setup will run after the load of those
> modules). 
> 
> We can postpone the call of SET_TYPE, or allow that a second SET_TYPE to be
> accepted, but we can't make any assumption about the module load order.
> 
> If, previously, the driver were assuming a that I2C drivers were compiled
> as module, and a certain load order, the driver were already broken.

Yes, this was tested by me and confirmed and posted.

Unluckily I don't have enough free PCI slots currently anymore to trace
the two analog only cards I have with tuner eeprom detection 24/7.

> The problem is not related to when a driver is loaded, but when I2C binding
> happens.
> 
> Since we are using the old probe methods on most boards, after I2C is
> initialized by the bridge, any existing i2c driver will try to bind on it.
> Also, there's no control on the order that each i2c driver will be attached to
> the i2c bus.
> 
> The proper fix is to migrate all drivers to the way that ivtv and cx18 are
> probing i2c devices. This way, we can control when I2C bind for tveeprom and
> for tuner will happen. So, we can do what you are meaning: bind first tveeprom,
> then do the proper card setup and bind the tuner.

Mike, Mauro, thanks for confirming that it is not unnoticed and
forgotten.

Cheers,
Hermann


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[David Engel]

On Mon, Jun 02, 2008 at 04:09:12PM -0400, Michael Krufky wrote:
> On Sun, Jun 1, 2008 at 4:55 PM, David Engel <david@istwok.net> wrote:
> > The tuner is detected this time and analog capture works.
> 
> The fact that reloading tuner.ko confirms my suspicion --
> 
> In the case of the ATSC110 / ATSC115, we can't attach the tuner client
> module until after the NXT2004 has been initialized with its i2c gate
> left in open state.
> 
> If you unload all v4l/dvb drivers and modprobe saa7134, I believe this
> will work properly, since the demod has already been initialized once,
> with the gate left open by default.

This jives with what I saw in further testing.  After it worked once,
it would continue to work across all sorts of module reloads.  I
thought there was one time it didn't continue to work, though, but I
could never reproduce it.

> So, that's a workaround to your problem.  When I find some spare time,
> I'll investigate into what changed in 2.6.25 that led to this issue.
> This is *not* the same issue that Hermann described in his mail.

Thanks.  It would be very nice to get this fixed.  FWIW, I just tried
unloading and reloading tuner/tuner-simple on my system with 2 ATSC
115s and 2 PVR x50s.  All tuners were detected for the first time I
can remember.  The PVR x50 tuners were always detected but no more
than one of the ATSC 115 tuners was ever detected before.

David
-- 
David Engel
david@istwok.net

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[Jason Pontious]

On Sun, Jun 1, 2008 at 4:55 PM, David Engel <david@istwok.net> wrote:

> On Sun, Jun 01, 2008 at 03:10:21PM -0400, Michael Krufky wrote:
> > On Sun, Jun 1, 2008 at 3:03 PM, David Engel <david@istwok.net> wrote:
> > >
> https://www.redhat.com/mailman/private/video4linux-list/2008-April/msg00221.html
> >
> > This is in the private archives...  Do you have a link from gmane or
> > some other public archive?
>
>
> http://lists-archives.org/video4linux/22351-hauppauge-wintv-regreession-from-2-6-24-to-2-6-25.html
>
> > Under 2.6.25, can you confirm whether or not the "tuner" module is
> > actually loaded?  If it is loaded, can you do:
>
> Yes, the tuner module is loaded with a clean boot of 2.6.25.  The
> output from "lsmod | grep tuner" is:
>
> tuner                  34656  0
> tea5767                 6020  1 tuner
> tda8290                12292  1 tuner
> tuner_xc2028           18960  1 tuner
> firmware_class          7040  3 nxt200x,saa7134_dvb,tuner_xc2028
> tda9887                 9092  1 tuner
> tuner_simple            8584  1 tuner
> mt20xx                 11784  1 tuner
> tea5761                 4612  1 tuner
> videodev               30976  2 tuner,saa7134
> v4l2_common             9856  2 tuner,saa7134
> i2c_core               18836  18
> nvidia,dvb_pll,nxt200x,saa7134_dvb,tuner,tea5767,tda8290,tda827x,tuner_xc2028,tda9887,tuner_simple,mt20xx,tea5761,saa7134,v4l2_common,ir_kbd_i2c,tveeprom,i2c_nforce2
>
> > modprobe -r tuner
> > modprobe -r tuner-simple
> > modprobe tuner-simple debug=1
> > modprobe tuner debug=1
> >
> > ...then test again and show the dmesg logs.
>
> Here are the logs:
>
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: chip found @ 0x86 (saa7133[0])
> Jun  1 15:52:36 opus kernel: tda9887 2-0043: tda988[5/6/7] found
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: type set to tda9887
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: tv freq set to 0.00
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: TV freq (0.00) out of range
> (44-958)
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: saa7133[0] tuner' I2C addr 0x86
> with type 74 used for 0x0e
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: Calling set_type_addr for
> type=68, addr=0xff, mode=0x04, config=0x00
> Jun  1 15:52:36 opus kernel: tuner' 2-0043: set addr for type 74
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: Setting mode_mask to 0x0e
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: chip found @ 0xc2 (saa7133[0])
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: tuner 0x61: Tuner type absent
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: Calling set_type_addr for
> type=68, addr=0xff, mode=0x04, config=0x00
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: set addr for type -1
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: defining GPIO callback
> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: type set to 68 (Philips
> TUV1236D ATSC/NTSC dual in)
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: type set to Philips TUV1236D AT
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: tv freq set to 400.00
> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: IFPCoff = 623:
> tuner_t_params undefined for tuner 68
> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: tv: param 0, range 1
> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: Freq= 400.00 MHz,
> V_IF=38.93 MHz, Offset=0.00 MHz, div=7023
> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: tv 0x1b 0x6f 0xce 0x02
> Jun  1 15:52:36 opus kernel: tuner' 2-0061: saa7133[0] tuner' I2C addr 0xc2
> with type 68 used for 0x0e
>
> The tuner is detected this time and analog capture works.
>
> David
> --
> David Engel
> david@istwok.net
>


I've been following this discussion closely and will give you my input from
what I have seen.  Here is my output from a 2.6.24-rc4 kernel with the
v4l-dvb drivers included in that kernel.

My output from lsmod | grep tuner is :

tuner                  28364  0
tea5767                 8324  1 tuner
tda8290                15108  1 tuner
tuner_xc2028           22320  2 saa7134_dvb,tuner
xc5000                 12292  1 tuner
tda9887                12292  1 tuner
mt20xx                 14216  1 tuner
tea5761                 6532  1 tuner
tuner_simple           16148  2 saa7134_dvb,tuner
tuner_types            18688  1 tuner_simple
videodev               34944  3 tuner,saa7134,compat_ioctl32
v4l2_common            13952  2 tuner,saa7134
i2c_core               26528  28
saa7134_dvb,lnbp21,tda826x,mt352,tda10086,dvb_pll,nxt200x,isl6421,tda1004x,tuner,tea5767,tda8290,tda18271,tda827x,tuner_xc2028,xc5000,tda9887,mt20xx,tea5761,tuner_simple,saa7134,ir_kbd_i2c,tveeprom,v4l2_common,i2c_ali15x3,i2c_ali1535,nvidia,i2c_ali1563

After modprobe -r tuner; modprobe -r saa7134-dvb; modprobe -r tuner-simple;
then modprobe tuner debug=1; modprobe saa7134-dvb; modprobe tuner-simple
debug=1

[17205274.727019] tda9887 1-0043: destroying instance
[17205281.126932] tuner-simple 1-0061: destroying instance
[17205295.203526] tuner' 1-0043: chip found @ 0x86 (saa7133[0])
[17205295.203535] tda9887 1-0043: creating new instance
[17205295.203538] tda9887 1-0043: tda988[5/6/7] found
[17205295.203540] tuner' 1-0043: type set to tda9887
[17205295.203543] tuner' 1-0043: tv freq set to 0.00
[17205295.203546] tuner' 1-0043: TV freq (0.00) out of range (44-958)
[17205295.211552] tuner' 1-0043: saa7133[0] tuner' I2C addr 0x86 with type
74 used for 0x0e
[17205295.219525] tuner' 1-0061: Setting mode_mask to 0x0e
[17205295.219530] tuner' 1-0061: chip found @ 0xc2 (saa7133[0])
[17205295.219532] tuner' 1-0061: tuner 0x61: Tuner type absent
[17205319.208573] nxt200x: NXT2004 Detected
[17205319.216610] tuner-simple 1-0061: creating new instance
[17205319.216615] tuner-simple 1-0061: type set to 68 (Philips TUV1236D
ATSC/NTSC dual in)
[17205319.216619] tuner-simple 1-0061: tuner 0 atv rf input will be
autoselected
[17205319.216621] tuner-simple 1-0061: tuner 0 dtv rf input will be
autoselected
[17205319.216625] DVB: registering new adapter (saa7133[0])
[17205319.216628] DVB: registering frontend 0 (Nextwave NXT200X VSB/QAM
frontend)...
[17205319.232698] nxt2004: Waiting for firmware upload
(dvb-fe-nxt2004.fw)...
[17205319.232706] firmware: requesting dvb-fe-nxt2004.fw
[17205319.256572] nxt2004: Waiting for firmware upload(2)...
[17205320.877005] nxt2004: Firmware upload complete

I dont have analog channels before or after this.  I should have some set of
analog channels on either input.  Before with the ubuntu 2.6.24 I would
receive analog from the top input.  With 2.6.26-rc4 I can't seem to get
analog no matter what.  I'm not sure how my problem applies to the rest of
this conversation or if its completely different.

Let me know if you would like me to test anything else.

Thanks!
Jason Pontious
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[Michael Krufky]

Jason Pontious wrote:
> On Sun, Jun 1, 2008 at 4:55 PM, David Engel <david@istwok.net> wrote:
> 
>> On Sun, Jun 01, 2008 at 03:10:21PM -0400, Michael Krufky wrote:
>>> modprobe -r tuner
>>> modprobe -r tuner-simple
>>> modprobe tuner-simple debug=1
>>> modprobe tuner debug=1
>>>
>>> ...then test again and show the dmesg logs.
>> Here are the logs:
>>
>> Jun  1 15:52:36 opus kernel: tuner' 2-0043: chip found @ 0x86 (saa7133[0])
>> Jun  1 15:52:36 opus kernel: tda9887 2-0043: tda988[5/6/7] found
>> Jun  1 15:52:36 opus kernel: tuner' 2-0043: type set to tda9887
>> Jun  1 15:52:36 opus kernel: tuner' 2-0043: tv freq set to 0.00
>> Jun  1 15:52:36 opus kernel: tuner' 2-0043: TV freq (0.00) out of range
>> (44-958)
>> Jun  1 15:52:36 opus kernel: tuner' 2-0043: saa7133[0] tuner' I2C addr 0x86
>> with type 74 used for 0x0e
>> Jun  1 15:52:36 opus kernel: tuner' 2-0043: Calling set_type_addr for
>> type=68, addr=0xff, mode=0x04, config=0x00
>> Jun  1 15:52:36 opus kernel: tuner' 2-0043: set addr for type 74
>> Jun  1 15:52:36 opus kernel: tuner' 2-0061: Setting mode_mask to 0x0e
>> Jun  1 15:52:36 opus kernel: tuner' 2-0061: chip found @ 0xc2 (saa7133[0])
>> Jun  1 15:52:36 opus kernel: tuner' 2-0061: tuner 0x61: Tuner type absent
>> Jun  1 15:52:36 opus kernel: tuner' 2-0061: Calling set_type_addr for
>> type=68, addr=0xff, mode=0x04, config=0x00
>> Jun  1 15:52:36 opus kernel: tuner' 2-0061: set addr for type -1
>> Jun  1 15:52:36 opus kernel: tuner' 2-0061: defining GPIO callback
>> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: type set to 68 (Philips
>> TUV1236D ATSC/NTSC dual in)
>> Jun  1 15:52:36 opus kernel: tuner' 2-0061: type set to Philips TUV1236D AT
>> Jun  1 15:52:36 opus kernel: tuner' 2-0061: tv freq set to 400.00
>> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: IFPCoff = 623:
>> tuner_t_params undefined for tuner 68
>> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: tv: param 0, range 1
>> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: Freq= 400.00 MHz,
>> V_IF=38.93 MHz, Offset=0.00 MHz, div=7023
>> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: tv 0x1b 0x6f 0xce 0x02
>> Jun  1 15:52:36 opus kernel: tuner' 2-0061: saa7133[0] tuner' I2C addr 0xc2
>> with type 68 used for 0x0e
>>
>> The tuner is detected this time and analog capture works.
>>
>> David
>> --
>> David Engel
>> david@istwok.net
>>
> 
> 
> I've been following this discussion closely and will give you my input from
> what I have seen.  Here is my output from a 2.6.24-rc4 kernel with the
> v4l-dvb drivers included in that kernel.
> 
> My output from lsmod | grep tuner is :
> 
> [snip]
> 
> After modprobe -r tuner; modprobe -r saa7134-dvb; modprobe -r tuner-simple;
> then modprobe tuner debug=1; modprobe saa7134-dvb; modprobe tuner-simple
> debug=1

module load order matters.  to explain how and why is beyond the scope of this conversation.  To make things easy, use "make unload" inside the v4l-dvb tree to unload all the media drivers.  (do NOT ever use make load)

The order that you loaded above will not propogate the debug=1 module option to tuner-simple, since you already loaded 'tuner' and saa7134 is already running -- the combination of saa7134 and tuner will automatically load tuner-simple without any regard to your command line module options.

try this:

make unload
modprobe tuner-simple debug=1
modprobe tuner debug=1
modprobe saa7134
modprobe saa7134-dvb

> [17205274.727019] tda9887 1-0043: destroying instance
> [17205281.126932] tuner-simple 1-0061: destroying instance
> [17205295.203526] tuner' 1-0043: chip found @ 0x86 (saa7133[0])
> [17205295.203535] tda9887 1-0043: creating new instance
> [17205295.203538] tda9887 1-0043: tda988[5/6/7] found
> [17205295.203540] tuner' 1-0043: type set to tda9887
> [17205295.203543] tuner' 1-0043: tv freq set to 0.00
> [17205295.203546] tuner' 1-0043: TV freq (0.00) out of range (44-958)
> [17205295.211552] tuner' 1-0043: saa7133[0] tuner' I2C addr 0x86 with type
> 74 used for 0x0e
> [17205295.219525] tuner' 1-0061: Setting mode_mask to 0x0e
> [17205295.219530] tuner' 1-0061: chip found @ 0xc2 (saa7133[0])
> [17205295.219532] tuner' 1-0061: tuner 0x61: Tuner type absent
> [17205319.208573] nxt200x: NXT2004 Detected
> [17205319.216610] tuner-simple 1-0061: creating new instance
> [17205319.216615] tuner-simple 1-0061: type set to 68 (Philips TUV1236D
> ATSC/NTSC dual in)
> [17205319.216619] tuner-simple 1-0061: tuner 0 atv rf input will be
> autoselected
> [17205319.216621] tuner-simple 1-0061: tuner 0 dtv rf input will be
> autoselected
> [17205319.216625] DVB: registering new adapter (saa7133[0])
> [17205319.216628] DVB: registering frontend 0 (Nextwave NXT200X VSB/QAM
> frontend)...
> [17205319.232698] nxt2004: Waiting for firmware upload
> (dvb-fe-nxt2004.fw)...
> [17205319.232706] firmware: requesting dvb-fe-nxt2004.fw
> [17205319.256572] nxt2004: Waiting for firmware upload(2)...
> [17205320.877005] nxt2004: Firmware upload complete
> 
> I dont have analog channels before or after this.  I should have some set of
> analog channels on either input.  Before with the ubuntu 2.6.24 I would
> receive analog from the top input.  With 2.6.26-rc4 I can't seem to get
> analog no matter what.  I'm not sure how my problem applies to the rest of
> this conversation or if its completely different.
> 
> Let me know if you would like me to test anything else.

If the top input doesn't work, then try the bottom one.  Use the module options to change them if you like.

If things still dont work, then try the following:

make unload
modprobe saa7134-dvb
modprobe -r tuner
modprobe tuner

...that should do it.  Try both inputs.

-Mike

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Kworld 115-No Analog Channels

[Jason Pontious]

On Tue, Jun 3, 2008 at 9:38 PM, Michael Krufky <mkrufky@linuxtv.org> wrote:

> Jason Pontious wrote:
> > On Sun, Jun 1, 2008 at 4:55 PM, David Engel <david@istwok.net> wrote:
> >
> >> On Sun, Jun 01, 2008 at 03:10:21PM -0400, Michael Krufky wrote:
> >>> modprobe -r tuner
> >>> modprobe -r tuner-simple
> >>> modprobe tuner-simple debug=1
> >>> modprobe tuner debug=1
> >>>
> >>> ...then test again and show the dmesg logs.
> >> Here are the logs:
> >>
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0043: chip found @ 0x86
> (saa7133[0])
> >> Jun  1 15:52:36 opus kernel: tda9887 2-0043: tda988[5/6/7] found
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0043: type set to tda9887
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0043: tv freq set to 0.00
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0043: TV freq (0.00) out of range
> >> (44-958)
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0043: saa7133[0] tuner' I2C addr
> 0x86
> >> with type 74 used for 0x0e
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0043: Calling set_type_addr for
> >> type=68, addr=0xff, mode=0x04, config=0x00
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0043: set addr for type 74
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0061: Setting mode_mask to 0x0e
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0061: chip found @ 0xc2
> (saa7133[0])
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0061: tuner 0x61: Tuner type
> absent
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0061: Calling set_type_addr for
> >> type=68, addr=0xff, mode=0x04, config=0x00
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0061: set addr for type -1
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0061: defining GPIO callback
> >> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: type set to 68
> (Philips
> >> TUV1236D ATSC/NTSC dual in)
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0061: type set to Philips TUV1236D
> AT
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0061: tv freq set to 400.00
> >> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: IFPCoff = 623:
> >> tuner_t_params undefined for tuner 68
> >> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: tv: param 0, range 1
> >> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: Freq= 400.00 MHz,
> >> V_IF=38.93 MHz, Offset=0.00 MHz, div=7023
> >> Jun  1 15:52:36 opus kernel: tuner-simple 2-0061: tv 0x1b 0x6f 0xce 0x02
> >> Jun  1 15:52:36 opus kernel: tuner' 2-0061: saa7133[0] tuner' I2C addr
> 0xc2
> >> with type 68 used for 0x0e
> >>
> >> The tuner is detected this time and analog capture works.
> >>
> >> David
> >> --
> >> David Engel
> >> david@istwok.net
> >>
> >
> >
> > I've been following this discussion closely and will give you my input
> from
> > what I have seen.  Here is my output from a 2.6.24-rc4 kernel with the
> > v4l-dvb drivers included in that kernel.
> >
> > My output from lsmod | grep tuner is :
> >
> > [snip]
> >
> > After modprobe -r tuner; modprobe -r saa7134-dvb; modprobe -r
> tuner-simple;
> > then modprobe tuner debug=1; modprobe saa7134-dvb; modprobe tuner-simple
> > debug=1
>
> module load order matters.  to explain how and why is beyond the scope of
> this conversation.  To make things easy, use "make unload" inside the
> v4l-dvb tree to unload all the media drivers.  (do NOT ever use make load)
>
> The order that you loaded above will not propogate the debug=1 module
> option to tuner-simple, since you already loaded 'tuner' and saa7134 is
> already running -- the combination of saa7134 and tuner will automatically
> load tuner-simple without any regard to your command line module options.
>
> try this:
>
> make unload
> modprobe tuner-simple debug=1
> modprobe tuner debug=1
> modprobe saa7134
> modprobe saa7134-dvb
>
> > [17205274.727019] tda9887 1-0043: destroying instance
> > [17205281.126932] tuner-simple 1-0061: destroying instance
> > [17205295.203526] tuner' 1-0043: chip found @ 0x86 (saa7133[0])
> > [17205295.203535] tda9887 1-0043: creating new instance
> > [17205295.203538] tda9887 1-0043: tda988[5/6/7] found
> > [17205295.203540] tuner' 1-0043: type set to tda9887
> > [17205295.203543] tuner' 1-0043: tv freq set to 0.00
> > [17205295.203546] tuner' 1-0043: TV freq (0.00) out of range (44-958)
> > [17205295.211552] tuner' 1-0043: saa7133[0] tuner' I2C addr 0x86 with
> type
> > 74 used for 0x0e
> > [17205295.219525] tuner' 1-0061: Setting mode_mask to 0x0e
> > [17205295.219530] tuner' 1-0061: chip found @ 0xc2 (saa7133[0])
> > [17205295.219532] tuner' 1-0061: tuner 0x61: Tuner type absent
> > [17205319.208573] nxt200x: NXT2004 Detected
> > [17205319.216610] tuner-simple 1-0061: creating new instance
> > [17205319.216615] tuner-simple 1-0061: type set to 68 (Philips TUV1236D
> > ATSC/NTSC dual in)
> > [17205319.216619] tuner-simple 1-0061: tuner 0 atv rf input will be
> > autoselected
> > [17205319.216621] tuner-simple 1-0061: tuner 0 dtv rf input will be
> > autoselected
> > [17205319.216625] DVB: registering new adapter (saa7133[0])
> > [17205319.216628] DVB: registering frontend 0 (Nextwave NXT200X VSB/QAM
> > frontend)...
> > [17205319.232698] nxt2004: Waiting for firmware upload
> > (dvb-fe-nxt2004.fw)...
> > [17205319.232706] firmware: requesting dvb-fe-nxt2004.fw
> > [17205319.256572] nxt2004: Waiting for firmware upload(2)...
> > [17205320.877005] nxt2004: Firmware upload complete
> >
> > I dont have analog channels before or after this.  I should have some set
> of
> > analog channels on either input.  Before with the ubuntu 2.6.24 I would
> > receive analog from the top input.  With 2.6.26-rc4 I can't seem to get
> > analog no matter what.  I'm not sure how my problem applies to the rest
> of
> > this conversation or if its completely different.
> >
> > Let me know if you would like me to test anything else.
>
> If the top input doesn't work, then try the bottom one.  Use the module
> options to change them if you like.
>
> If things still dont work, then try the following:
>
> make unload
> modprobe saa7134-dvb
> modprobe -r tuner
> modprobe tuner
>
> ...that should do it.  Try both inputs.
>
> -Mike


Well after trying everything I could think of I could never get analog
channels to work with the drivers that came with 2.6.26-rc4.  I finally gave
up and went back to the 2.6.24 ubuntu kernel and modified tuner-simple.c
file and recompiled the module.  Hopefully you guys understand the problem
and have a fix in mind.  I wish I had time to debug all of this.  I had
analog channels on 2.6.24 it was just using the wrong input for my setup.
With 2.6.26 I got no analog channels (with the exact same options used in
2.6.24 setup).  Which is strange since I should have some analog channels
either way since I have both inputs connected.  With 2.6.24 I got the
"wrong" analog channels.  With 2.6.26 I got NO analog channels period.  I am
running amd64 but I doubt this is causing any issues.

Well just thought I would update you guys on where I ended up.  Thanks again
for all the help you provided!  I learned more about the v4l kernel modules
than I ever imagined during this.
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list