Pinnacle Systems PCTV 330e and Hauppauge WinTV HVR 900 (R2) not working under Debian 2.6.30-1

Pinnacle Systems PCTV 330e and Hauppauge WinTV HVR 900 (R2) not working under Debian 2.6.30-1

[Jelle de Jong]

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

Hi all,

This is sort of an updated report, I tested my em28xx based hybrid
devices again and the dvb-t still does not work under the 2.6.30 kernel.
I am not interested in the analog parts. So how is the process going on
getting support for dvb-t in the kernel. I am also not interested in any
non free non mainstream maintained code bases.

I believe I sent some em28xx devices to Devin, so how is the process
going, any luck?

Question for Antti if he had any luck with the devices (rtl2831-r2) I send?

Best regards,

Jelle de Jong

[-- Attachment #2: not-working-dvb-t-devices.txt --]
[-- Type: text/plain, Size: 8485 bytes --]

$ cat /proc/version
Linux version 2.6.30-1-686 (Debian 2.6.30-1) (waldi@debian.org) (gcc version 4.3.3 (Debian 4.3.3-11) ) #1 SMP Sun Jun 14 16:11:32 UTC 2009

[ 2629.292634] usb 1-2: New USB device found, idVendor=2304, idProduct=0226
[ 2629.292648] usb 1-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 2629.292660] usb 1-2: Product: PCTV 330e
[ 2629.292669] usb 1-2: Manufacturer: Pinnacle Systems
[ 2629.292678] usb 1-2: SerialNumber: 070901090280
[ 2629.293003] usb 1-2: configuration #1 chosen from 1 choice
[ 2629.380840] Linux video capture interface: v2.00
[ 2629.458285] em28xx: New device Pinnacle Systems PCTV 330e @ 480 Mbps (2304:0226, interface 0, class 0)
[ 2629.458319] em28xx #0: Identified as Pinnacle Hybrid Pro (2) (card=56)
[ 2629.458684] em28xx #0: chip ID is em2882/em2883
[ 2629.632618] em28xx #0: i2c eeprom 00: 1a eb 67 95 04 23 26 02 d0 12 5c 03 8e 16 a4 1c
[ 2629.632666] em28xx #0: i2c eeprom 10: 6a 24 27 57 46 07 01 00 00 00 00 00 00 00 00 00
[ 2629.632707] em28xx #0: i2c eeprom 20: 46 00 01 00 f0 10 02 00 b8 00 00 00 5b e0 00 00
[ 2629.632747] em28xx #0: i2c eeprom 30: 00 00 20 40 20 6e 02 20 10 01 00 00 00 00 00 00
[ 2629.632787] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 2629.632826] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 2629.632865] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 24 03 50 00 69 00
[ 2629.632905] em28xx #0: i2c eeprom 70: 6e 00 6e 00 61 00 63 00 6c 00 65 00 20 00 53 00
[ 2629.632945] em28xx #0: i2c eeprom 80: 79 00 73 00 74 00 65 00 6d 00 73 00 00 00 16 03
[ 2629.632985] em28xx #0: i2c eeprom 90: 50 00 43 00 54 00 56 00 20 00 33 00 33 00 30 00
[ 2629.633039] em28xx #0: i2c eeprom a0: 65 00 00 00 1c 03 30 00 37 00 30 00 39 00 30 00
[ 2629.633084] em28xx #0: i2c eeprom b0: 31 00 30 00 39 00 30 00 32 00 38 00 30 00 00 00
[ 2629.633124] em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 2629.633163] em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 2629.633203] em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 2629.633242] em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 2629.633287] em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0x87b3a5bf
[ 2629.633295] em28xx #0: EEPROM info:
[ 2629.633303] em28xx #0:   AC97 audio (5 sample rates)
[ 2629.633310] em28xx #0:   500mA max power
[ 2629.633321] em28xx #0:   Table at 0x27, strings=0x168e, 0x1ca4, 0x246a
[ 2629.633331] em28xx #0:
[ 2629.633335]
[ 2629.633345] em28xx #0: The support for this board weren't valid yet.
[ 2629.633354] em28xx #0: Please send a report of having this working
[ 2629.633363] em28xx #0: not to V4L mailing list (and/or to other addresses)
[ 2629.633369]
[ 2629.646677] tvp5150 1-005c: chip found @ 0xb8 (em28xx #0)
[ 2629.668207] tuner 1-0061: chip found @ 0xc2 (em28xx #0)
[ 2629.707303] xc2028 1-0061: creating new instance
[ 2629.707318] xc2028 1-0061: type set to XCeive xc2028/xc3028 tuner
[ 2629.707346] i2c-adapter i2c-1: firmware: requesting xc3028-v27.fw
[ 2629.725562] xc2028 1-0061: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7
[ 2629.776067] xc2028 1-0061: Loading firmware for type=BASE MTS (5), id 0000000000000000.
[ 2630.787641] xc2028 1-0061: Loading firmware for type=MTS (4), id 000000000000b700.
[ 2630.804877] xc2028 1-0061: Loading SCODE for type=MTS LCD NOGD MONO IF SCODE HAS_IF_4500 (6002b004), id 000000000000b700.
[ 2630.988331] em28xx #0: Config register raw data: 0xd0
[ 2630.989121] em28xx #0: AC97 vendor ID = 0xffffffff
[ 2630.989496] em28xx #0: AC97 features = 0x6a90
[ 2630.989506] em28xx #0: Empia 202 AC97 audio processor detected
[ 2631.116623] tvp5150 1-005c: tvp5150am1 detected.
[ 2631.237132] em28xx #0: v4l2 driver version 0.1.2
[ 2631.319217] em28xx #0: V4L2 device registered as /dev/video0 and /dev/vbi0
[ 2631.332140] usbcore: registered new interface driver em28xx
[ 2631.332159] em28xx driver loaded
[ 2631.385655] em28xx-audio.c: probing for em28x1 non standard usbaudio
[ 2631.385671] em28xx-audio.c: Copyright (C) 2006 Markus Rechberger
[ 2631.387359] Em28xx: Initialized (Em28xx Audio Extension) extension
[ 2631.656608] tvp5150 1-005c: tvp5150am1 detected.

------------------------------------------------------------------------

[ 2749.140095] usb 1-2: new high speed USB device using ehci_hcd and address 9
[ 2749.277649] usb 1-2: New USB device found, idVendor=2040, idProduct=6502
[ 2749.277664] usb 1-2: New USB device strings: Mfr=0, Product=1, SerialNumber=2
[ 2749.277676] usb 1-2: Product: WinTV HVR-900
[ 2749.277685] usb 1-2: SerialNumber: 4030600678
[ 2749.278014] usb 1-2: configuration #1 chosen from 1 choice
[ 2749.278346] em28xx: New device WinTV HVR-900 @ 480 Mbps (2040:6502, interface 0, class 0)
[ 2749.278373] em28xx #0: Identified as Hauppauge WinTV HVR 900 (R2) (card=18)
[ 2749.278522] em28xx #0: chip ID is em2882/em2883
[ 2749.451506] em28xx #0: i2c eeprom 00: 1a eb 67 95 40 20 02 65 d0 12 5c 03 82 1e 6a 18
[ 2749.451553] em28xx #0: i2c eeprom 10: 00 00 24 57 66 07 01 00 00 00 00 00 00 00 00 00
[ 2749.451594] em28xx #0: i2c eeprom 20: 46 00 01 00 f0 10 02 00 b8 00 00 00 5b e0 00 00
[ 2749.451634] em28xx #0: i2c eeprom 30: 00 00 20 40 20 6e 02 20 10 01 01 01 00 00 00 00
[ 2749.451674] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 2749.451714] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 2749.451753] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 18 03 34 00 30 00
[ 2749.451793] em28xx #0: i2c eeprom 70: 33 00 30 00 36 00 30 00 30 00 36 00 37 00 38 00
[ 2749.451833] em28xx #0: i2c eeprom 80: 00 00 1e 03 57 00 69 00 6e 00 54 00 56 00 20 00
[ 2749.451873] em28xx #0: i2c eeprom 90: 48 00 56 00 52 00 2d 00 39 00 30 00 30 00 00 00
[ 2749.451913] em28xx #0: i2c eeprom a0: 84 12 00 00 05 50 1a 7f d4 78 23 fa fd d0 38 89
[ 2749.451953] em28xx #0: i2c eeprom b0: ff 00 00 00 04 84 0a 00 01 01 20 77 00 40 e6 15
[ 2749.451993] em28xx #0: i2c eeprom c0: 3e f0 74 02 01 00 01 79 01 00 00 00 00 00 00 00
[ 2749.452065] em28xx #0: i2c eeprom d0: 84 12 00 00 05 50 1a 7f d4 78 23 fa fd d0 38 89
[ 2749.452106] em28xx #0: i2c eeprom e0: ff 00 00 00 04 84 0a 00 01 01 20 77 00 40 e6 15
[ 2749.452146] em28xx #0: i2c eeprom f0: 3e f0 74 02 01 00 01 79 01 00 00 00 00 00 00 00
[ 2749.452191] em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0xa9c738dd
[ 2749.452199] em28xx #0: EEPROM info:
[ 2749.452207] em28xx #0:   AC97 audio (5 sample rates)
[ 2749.452214] em28xx #0:   500mA max power
[ 2749.452225] em28xx #0:   Table at 0x24, strings=0x1e82, 0x186a, 0x0000
[ 2749.457873] tveeprom 1-0050: Hauppauge model 65018, rev B3C0, serial# 4068838
[ 2749.457892] tveeprom 1-0050: tuner model is Xceive XC3028 (idx 120, type 71)
[ 2749.457908] tveeprom 1-0050: TV standards PAL(B/G) PAL(I) PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xd4)
[ 2749.457921] tveeprom 1-0050: audio processor is None (idx 0)
[ 2749.457932] tveeprom 1-0050: has radio
[ 2749.464515] tvp5150 1-005c: chip found @ 0xb8 (em28xx #0)
[ 2749.476442] tuner 1-0061: chip found @ 0xc2 (em28xx #0)
[ 2749.476916] xc2028 1-0061: creating new instance
[ 2749.476932] xc2028 1-0061: type set to XCeive xc2028/xc3028 tuner
[ 2749.476963] i2c-adapter i2c-1: firmware: requesting xc3028-v27.fw
[ 2749.499788] xc2028 1-0061: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7
[ 2749.548065] xc2028 1-0061: Loading firmware for type=BASE MTS (5), id 0000000000000000.
[ 2750.555404] xc2028 1-0061: Loading firmware for type=MTS (4), id 000000000000b700.
[ 2750.572765] xc2028 1-0061: Loading SCODE for type=MTS LCD NOGD MONO IF SCODE HAS_IF_4500 (6002b004), id 000000000000b700.
[ 2750.756462] input: em28xx IR (em28xx #0) as /devices/pci0000:00/0000:00:1d.7/usb1/1-2/input/input12
[ 2750.756939] em28xx #0: Config register raw data: 0xd0
[ 2750.757776] em28xx #0: AC97 vendor ID = 0xffffffff
[ 2750.758150] em28xx #0: AC97 features = 0x6a90
[ 2750.758164] em28xx #0: Empia 202 AC97 audio processor detected
[ 2750.900626] tvp5150 1-005c: tvp5150am1 detected.
[ 2751.038142] em28xx #0: v4l2 driver version 0.1.2
[ 2751.123980] em28xx #0: V4L2 device registered as /dev/video0 and /dev/vbi0
[ 2751.123991] em28xx-audio.c: probing for em28x1 non standard usbaudio
[ 2751.123997] em28xx-audio.c: Copyright (C) 2006 Markus Rechberger
[ 2751.440613] tvp5150 1-005c: tvp5150am1 detected.

Re: Pinnacle Systems PCTV 330e and Hauppauge WinTV HVR 900 (R2) not working under Debian 2.6.30-1

[Devin Heitmueller]

On Fri, Jun 26, 2009 at 4:26 AM, Jelle de Jong<jelledejong@powercraft.nl> wrote:
> Hi all,
>
> This is sort of an updated report, I tested my em28xx based hybrid
> devices again and the dvb-t still does not work under the 2.6.30 kernel.
> I am not interested in the analog parts. So how is the process going on
> getting support for dvb-t in the kernel. I am also not interested in any
> non free non mainstream maintained code bases.
>
> I believe I sent some em28xx devices to Devin, so how is the process
> going, any luck?
>
> Question for Antti if he had any luck with the devices (rtl2831-r2) I send?
>
> Best regards,
>
> Jelle de Jong

Hello Jelle,

Unfortunately, I could have told you without your having done any
testing that the 330e and HVR-900 R2 are not any closer to working -
nobody is working on them.  They both use the Micronas drx-d, for
which we have a reverse engineered driver that is not currently used
in any devices and it is unknown whether it actually works.  Devices
attempting to use the driver require a config structure which has
something like 27 inputs, so while I do have the HVR-900 R2 hardware I
didn't feel comfortable attempting to get it to work without a signal
generator.

Regarding the Terratec Cinergy T XS USB you sent me...  there are two
variants of the same device with the same USB ID.  One has the zl10353
and the other has the mt352.  I found one bug that was common to both,
one bug in the zl10353 version, and one bug in the mt352.  I issued a
PULL request for the zl10353 version last Tuesday.

So, I've fixed three bugs and gotten the zl10353 version working.  The
mt352 version (which is the one you sent me) has the fixes above, but
according to the one user who has been willing to test the changes,
the device still does not work.  I do not know whether this is really
a bug in the driver or a problem in the user's environment (since he
doesn't own any other tuners to verify his signal and antenna with).
Contrary to my expectations, I haven't been been able to get access to
the signal generator, so I haven't been able to fully test/debug the
device myself.

If there are any other users out there with the mt352 version of the
Terratec Cinergy T XS who can do testing, I would definitely be
willing to work with them.

I am continuing to try to get access to a generator, and looking for
other testers who can try the changes.  I'm at a point now where I was
debating just sending it back to you and having you see if it works
(given the fixes I've already made), and attempting to debug any
issues remotely.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Re: Pinnacle Systems PCTV 330e and Hauppauge WinTV HVR 900 (R2) not working under Debian 2.6.30-1

[Simon Kenyon]

Devin Heitmueller wrote:
> Regarding the Terratec Cinergy T XS USB you sent me...  there are two
> variants of the same device with the same USB ID.  One has the zl10353
> and the other has the mt352.  I found one bug that was common to both,
> one bug in the zl10353 version, and one bug in the mt352.  I issued a
> PULL request for the zl10353 version last Tuesday.
>   
as you know i have the xl10353 variant. and you got it to work on my 
machine.

now i know you don't want to hear this but the same code will not work 
on another machine.
both are running 2.6.28-gentoo-r5, however i'm pretty sure the 
configurations are different.
the working machine has an MSI KA780G MS-7551 [SB700 chipset] 
motherboard and
the non-working machine has an ASUSTeK M3N78-EM [GeForce 8200 chipset] 
motherboard

in fact, i've seen reference on this list to the fact that there are 
problems with the SB700. that seems to be the opposite to me.
i will check it out on an Atom based netbook and an old Intel Centrino 
laptop to see if the code works there.
i suspect it will - but need to confirm it.

i'm afriad it is two steps forward and one step backwards
--
simon

Re: Pinnacle Systems PCTV 330e and Hauppauge WinTV HVR 900 (R2) not working under Debian 2.6.30-1

[Devin Heitmueller]

On Fri, Jun 26, 2009 at 10:36 AM, Simon Kenyon<simon@koala.ie> wrote:
> as you know i have the xl10353 variant. and you got it to work on my
> machine.
>
> now i know you don't want to hear this but the same code will not work on
> another machine.
> both are running 2.6.28-gentoo-r5, however i'm pretty sure the
> configurations are different.
> the working machine has an MSI KA780G MS-7551 [SB700 chipset] motherboard
> and
> the non-working machine has an ASUSTeK M3N78-EM [GeForce 8200 chipset]
> motherboard
>
> in fact, i've seen reference on this list to the fact that there are
> problems with the SB700. that seems to be the opposite to me.
> i will check it out on an Atom based netbook and an old Intel Centrino
> laptop to see if the code works there.
> i suspect it will - but need to confirm it.
>
> i'm afriad it is two steps forward and one step backwards
> --
> simon

Well, that's better than one step forward and two steps backward.  :-)

Send me the dmesg offline and I will work with you to try to debug the
issue.  I have some significant doubts this is an em28xx issue though.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Ralink RTL2831U

[Antti Palosaari]

Moi Jelle,

On 06/26/2009 11:26 AM, Jelle de Jong wrote:
> Question for Antti if he had any luck with the devices (rtl2831-r2) I send?

I have been busy with other drivers, but now I have time for this.

It was a little bit tricky to take sniffs from Windows because sniffer 
crashed very easily with this device :o But after testing about all 
drivers I found and after countless blue-screens I finally got one good 
sniff. From sniff I see this device is rather simple to program. And 
device you send have MT2060 tuner.

With a any luck and without other summer activities (I am still hoping 
warm weather and beach activities :) it will not take many days to get 
picture. After that I will move relevant parts from the current Ralink 
driver to the new driver... I will keep informed about driver status.

regards
Antti
-- 
http://palosaari.fi/

Re: Ralink RTL2831U

[Jan Hoogenraad]

Please note that the current (not split-up) driver was developed by the 
maker of the hardware.
It is the same code that is used in the Windows driver.

As far as I have seen, there is only ONE callback from the tuner code to 
the demodulator.
I forgot the name of the routine.

Cheers,
		Jan

Antti Palosaari wrote:
> Moi Jelle,
> 
> On 06/26/2009 11:26 AM, Jelle de Jong wrote:
>> Question for Antti if he had any luck with the devices (rtl2831-r2) I 
>> send?
> 
> I have been busy with other drivers, but now I have time for this.
> 
> It was a little bit tricky to take sniffs from Windows because sniffer 
> crashed very easily with this device :o But after testing about all 
> drivers I found and after countless blue-screens I finally got one good 
> sniff. From sniff I see this device is rather simple to program. And 
> device you send have MT2060 tuner.
> 
> With a any luck and without other summer activities (I am still hoping 
> warm weather and beach activities :) it will not take many days to get 
> picture. After that I will move relevant parts from the current Ralink 
> driver to the new driver... I will keep informed about driver status.
> 
> regards
> Antti


-- 
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht