[linux-dvb] Re: nova-t 500 progress?

[Eduard Huguet]

-- Missatge reenviat --
From: Robin Hill <[EMAIL PROTECTED]>
To: linux-dvb@linuxtv.org
Date: Thu, 17 May 2007 23:15:22 +0100
Subject: [linux-dvb] Re: nova-t 500 progress?
On Thu May 17, 2007 at 11:55:28AM +0100, Richard Morris wrote:

> I use 2 of the Nova-T 500's with MythTV, I get about 4 disconnects a day
> that either fill up the event log with messages like:
>
> May 17 10:01:00 athlon mt2060 I2C read failed
>
> and/or crash MythTV.
>
I guess you're running with EIT scanning enabled?  Disabling this will
dramatically reduce the number of resets (I get about one a month with
my two cards).

Cheers,
Robin
--
 ___
( ' } |   Robin Hill <[EMAIL PROTECTED]>  |
   / / )  | Little Jim says |
  // !!   |  "He fallen in de water !!" |




What kernel are you using? I'm using 2.6.21 and HG drivers and the
disconnects are way less frequent than before, even with EIT scanning
activated in MythTV. Currently most days the system doesn't experience any,
it's just about one per week now.

These are my machine specs:
 · Asus Pundit P1-AH2 (AMD 3800 - 64 bit)
 · 1GB RAM
 · 1 PCI slot filled with Nova-T 500 (the other one is free)
 · Sabayon 3.3 x86 (32 bit edition), with kernel upgraded to 2.6.21

The system is now rock stable, with only a (very) few disconnects, as said
before. It's not a 24/24 server, but it's mostly on during the day, and EIT
scanning is on and working fine.

BTW, someone posted some days ago that he had a script that monitorizes
'dmesg' and restarts automatically MythTV backend what it detects the mt2060
read/write error. It would be great if he could share it, I'd really be
interested :D.

Cheers
 Eduard Huguet
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Uwe

[Simon Arlott]

On 18/05/07 01:40, Allan Stirling wrote:

Uwe Bugla wrote:


Is there any way to disallow someone from posting to the mailing list, 
or does everyone have to add Uwe to their own killfile?


It's possible, whether it happens or not is up to the list maintainer. 
Other mailing lists have no problem banning him after the first incident 
(e.g. MPlayer).



--
Simon Arlott

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Incorrect tuning parameters for Perth Western Australia

[Jim Barber]

Peter D. wrote:
The way it seems to work is that nothing happens until someone in Perth 
(that means YOU) posts a corrected configuration file to this list.  
There have been a couple of similar posts for other places in the last 
few days.  

First step; download the current code from linuxtv.org and make sure that 
the changes have not already been included.  It is only a couple of Meg.  


Okay I've used the following link to access details about the latest file via 
CVS web:

http://www.linuxtv.org/cgi-bin/viewcvs.cgi/dvb-apps/util/scan/dvb-t/au-Perth?rev=1.2&view=log

It is at revision 1.2 and was last modified Dec 19th 2005 01:31:20 (16 months, 
4 weeks ago).
I downloaded it using the following link:

http://www.linuxtv.org/cgi-bin/viewcvs.cgi/*checkout*/dvb-apps/util/scan/dvb-t/au-Perth?rev=1.2

The data is out of date, so I've corrected it.
Only with the correction will my "Hauppauge Nova-T 500" correctly lock on to 
channel 7.

Most other people send the new/corrected file as an attachment, which I 
assume is the easiest way for the recipient to handle it.  

I suggest posting a reply with the file attached as a file (assuming 
that the change has not already made it to linuxtv.org).  Don't be too 
disheartened if you don't see an immediate response.  They seem to be 
collected and acknowledged in bulk irregularly.  


The modified file is attached.
Thanks for your help.

Regards,

--
--
Jim Barber
# Australia / Perth
# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
# ABC
T 22650 7MHz 3/4 NONE QAM64 8k 1/16 NONE
# Seven Network
T 17750 7MHz 2/3 NONE QAM64 8k 1/16 NONE
# Nine Network
T 191625000 7MHz 3/4 NONE QAM64 8k 1/16 NONE
# Network TEN
T 21950 7MHz 3/4 NONE QAM64 8k 1/16 NONE
# SBS
T 53650 7MHz 2/3 NONE QAM64 8k 1/8 NONE
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Incorrect tuning parameters for Perth Western Australia

[Peter D.]

On Monday 14 May 2007 19:50, Jim Barber wrote:
> Hi all.
>
> I hope this is the right mailing list to send to.

Yes I think so.  

> It's a request to fix an incorrect setting in the configuration file
> supplied for the scan utility of the dvb-utils software, the the au-Perth
> region.

The way it seems to work is that nothing happens until someone in Perth 
(that means YOU) posts a corrected configuration file to this list.  
There have been a couple of similar posts for other places in the last 
few days.  

First step; download the current code from linuxtv.org and make sure that 
the changes have not already been included.  It is only a couple of Meg.  

I'm not brave enough to submit changes for other cities even bases on 
data from an official web site.  Maybe we should?  There are other 
Australian cities.  

> I have a Hauppauge Nova-T tuner card and for ages I've been able to get
> all of the five TV stations except for Channel 7. I had looked all over
> the Internet and the settings reoprted on various wiki's, mailing lists,
> etc all agreed with the ones I was trying, but failing with.

I think that the problem is that channel 7 has changed one of its parameters 
recently AND some hardware is capable of ignoring some of the now wrong 
configuration while other hardware is stumped by the new mis-configuration.  

> Finally I stumbled across the correct settings on the Digital
> Broadcasting Australia's website at the following link:
>
>   http://www.dba.org.au/index.asp?sectionID=120
>
> The problem is that everywhere, the guard interval for channel 7 has been
> reported as being 1/8. This is incorrect. It is actually 1/16.
> It was enough to stop me from being able to tune to it, even when doing
> auto scans. I was just about to return the DVB-T capture card as faulty
> because of this setting reported incorrectly everywhere.
>
> I'm using Debian, and they have a dvb-utils package that is at version
> 1.1.1 that seems to be the latest version. In this package is a file
> called: /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-Perth The current
> contents of this file are as follows:
>
>   # Australia / Perth (Carmel/Bickley transmitters)
>   # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
>   # ABC
>   T 22650 7MHz 3/4 NONE QAM64 8k 1/16 NONE
>   # Seven
>   T 17750 7MHz 2/3 NONE QAM64 8k 1/8 NONE
>   # Nine
>   T 191625000 7MHz 3/4 NONE QAM64 8k 1/16 NONE
>   # Ten
>   T 21950 7MHz 3/4 NONE QAM64 8k 1/16 NONE
>   # SBS
>   T 536625000 7MHz 2/3 NONE QAM64 8k 1/8 NONE
>
> However the entry for "Seven" should be:
>
>   T 17750 7MHz 2/3 NONE QAM64 8k 1/16 NONE
>
> Is this the correct list to report this problem to so that the file is
> corrected in future versions of the utils?
>
> I hope this helps anyone else from Perth who has had the same problem as
> me and kept finding the same mis-information that I did.

It looks like you have already done all of the hard work.  Congratulations.  

Most other people send the new/corrected file as an attachment, which I 
assume is the easiest way for the recipient to handle it.  

I suggest posting a reply with the file attached as a file (assuming 
that the change has not already made it to linuxtv.org).  Don't be too 
disheartened if you don't see an immediate response.  They seem to be 
collected and acknowledged in bulk irregularly.  


-- 
sig goes here...
Peter D.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Re: New Devices (Testers wanted)

[Markus Rechberger]

On 5/18/07, James Klaas <[EMAIL PROTECTED]> wrote:

I have a KWorld PVRTV 300U that I would love to have working.  I went
to mcentral.de and pulled the hg from there as spelled out on one of
the pages:

hg clone http://mcentral.de/hg/~mrec/v4l-dvb-kernel


sorry, this tree is limited to kernel <2.6.20, there's another one
which works with newer ones:
$ hg clone http://mcentral.de/hg/~mrec/v4l-dvb

cheers,
Markus



I'm running the Ubuntu 2.6.20.3-ubuntu1 kernel source.  Is there a set
of patches on this?  It didn't compile for me, complaining about a
macro that was given 3 arguments, but it only takes 2.  I also waded
through some of the sources, but didn't see any references to the
KWorld PVRTV 300U.  That being said, I would love to do some testing
on that USB tuner stick.

James

On 5/17/07, Markus Rechberger <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I put together a list of devices which are managed on mcentral.de, I'm
> looking for a list of outstanding bugs and people who are willing to
> work on getting them resolved.
>
> The list counts 56 (dvb-t/analogue/hybrid) devices at the moment, I
> will add a few more during the next few days.
>
>  Compro VideoMate T750
>  Pinnacle PCTV Hybrid (PCMCIA)
>  Winfast TV 2000 XP Global
>  Powercolor Real Angel
>  Avermedia A16D
>  Avermedia M115
>  Avermedia Cardbus 506
>  Terratec Cinergy 250 USB
>  Pinnacle PCTV USB 2
>  Hauppauge WinTV USB 2
>  MSI VOX USB 2.0
>  Terratec Cinergy 200 USB
>  Leadtek Winfast USB II
>  Kworld USB2800
>  Pinnacle Dazzle DVC 90
>  Hauppauge WinTV HVR 900
>  Terratec Hybrid XS
>  Terratec Hybrid XS Secam
>  Kworld PVR TV 2800 RF
>  Terratec Prodigy XS
>  Videology 20K14XUSB USB2.0
>  Usbgear VD204v9
>  Terratec Cinergy T XS
>  Pinnacle PCTV DVB-T
>  DNT DA2 Hybrid
>  Pinnacle Hybrid Pro
>  Hercules Smart TV USB 2.0
>  Compro, VideoMate U3
>  KWorld DVB-T 310U
>  SIIG AVTuner-PVR/Prolink PlayTV USB 2.0
>  Terratec Cinergy T XS (MT2060)
>  MSI DigiVox A/D
>  D-Link DUB-T210 TV Tuner
>  Gadmei UTV310
>  Kworld 355 U DVB-T
>  Supercomp USB 2.0 TV
>  Hauppauge WinTV HVR Rev. 1.2
>  Gadmei UTV330
>  V-Gear PocketTV
>  Kworld 350 U DVB-T
>  Terratec Hybrid XS (em2882)
>  Pinnacle Dazzle DVC 100
>  Yakumo MovieMixer
>  Huaqi DLCW-130
>  Generic EM2883 video grabber
>  Hauppauge WinTV HVR 950
>  Pinnacle PCTV HD Pro
>  Pinnacle Hybrid Pro (2)
>  Hauppauge WinTV USB 2 (R2)
>  NetGMBH Cam
>  Leadtek Winfast USB II Deluxe
>  MSI DigiVox A/D II
>  Typhoon DVD Maker
>  Pinnacle PCTV USB 2 (Philips FM1216ME)
>  KWorld DVB-T 305U
>  KWorld PVRTV 300U
>
> http://mcentral.de/wiki/index.php/Linuxtv
>
> thanks,
> Markus
>
> --
> video4linux-list mailing list
> Unsubscribe mailto:[EMAIL PROTECTED]
> https://www.redhat.com/mailman/listinfo/video4linux-list
>




--
Markus Rechberger

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Uwe

[timecop]

Yes, it has Reply-To-All, which is what I use.
Then I proceed cutting "linux-dvb@linuxtv.org" 
out of the CC: field, selecting all text in To: field, and pasting it
there. Which is quite annoying. And if the previous email had multiple
CC's, then I need to clear the rest of them out of CC field.

I don't need to CC another copy to YOU since clearly you've already
subscribed to the list.

-tc

On 5/18/07, Shannon Wynter <[EMAIL PROTECTED]> wrote:

G'day.

I'm not going to get into any of the other argument (arguing on the
internet is like... well you know) however. With regards to the reply-to
address: Most mail clients have a 'Reply-All' button.

I noticed you are using gmail, when viewing an email in gmail,
right-besides the reply button is a little arrow, clicking this should
display the 'Reply to all' option.

I hope this makes your life a litle more convenient.

timecop wrote:
> Before that, I think a more productive change would be to make this
> list's Reply-To header go back to [EMAIL PROTECTED] instead of
> replying to the original user, and having to copy/paste + CC the rest
> of the addresses, which is more annoying than Uwe's thesaurus.
>
> -tc




___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Uwe

[Shannon Wynter]

G'day.

I'm not going to get into any of the other argument (arguing on the 
internet is like... well you know) however. With regards to the reply-to 
address: Most mail clients have a 'Reply-All' button.


I noticed you are using gmail, when viewing an email in gmail, 
right-besides the reply button is a little arrow, clicking this should 
display the 'Reply to all' option.


I hope this makes your life a litle more convenient.

timecop wrote:

Before that, I think a more productive change would be to make this
list's Reply-To header go back to [EMAIL PROTECTED] instead of
replying to the original user, and having to copy/paste + CC the rest
of the addresses, which is more annoying than Uwe's thesaurus.

-tc



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Uwe

[timecop]

Before that, I think a more productive change would be to make this
list's Reply-To header go back to [EMAIL PROTECTED] instead of
replying to the original user, and having to copy/paste + CC the rest
of the addresses, which is more annoying than Uwe's thesaurus.

-tc

On 5/18/07, Allan Stirling <[EMAIL PROTECTED]> wrote:

Uwe Bugla wrote:


Is there any way to disallow someone from posting to the
mailing list, or does everyone have to add Uwe to their own
killfile?

Cheers,

Allan.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Uwe

[Allan Stirling]

Uwe Bugla wrote:


Is there any way to disallow someone from posting to the 
mailing list, or does everyone have to add Uwe to their own 
killfile?


Cheers,

Allan.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: [RFC/PATCHES] xc3028 hybrid tuner, em28xx/em2880-dvb, saa7134, cx88

[Uwe Bugla]

Am Donnerstag, 17. Mai 2007 20:30 schrieb Oliver Endriss:
> Markus Rechberger wrote:
> > On 5/15/07, Oliver Endriss <[EMAIL PROTECTED]> wrote:
> > > Markus Rechberger wrote:
> > > > to be more accurate where all the changes happened:
> > > >  b/linux/drivers/media/tuners/Kconfig|   14
> > > >  b/linux/drivers/media/tuners/Makefile   |7
> > > >  b/linux/drivers/media/tuners/xc3028-tuner.c |  601 
> > > >  b/linux/drivers/media/tuners/xc3028-tuner.h |   20
> > > >  b/linux/drivers/media/video/em28xx/em2880-dvb.c |  748 
> > > >  b/linux/drivers/media/video/em28xx/em28xx-audio.c   |  439 ++
> > > >  b/linux/drivers/media/video/em28xx/em28xx-webcam.c  |  365 ++
> > > >  b/linux/include/media/v4l_dvb_tuner.h   |  131
> > > >  linux/Documentation/video4linux/CARDLIST.cx88   |3
> > > >  linux/Documentation/video4linux/CARDLIST.em28xx |   69
> > > >  linux/Documentation/video4linux/CARDLIST.tuner  |1
> > > >  linux/drivers/media/Kconfig |2
> > > >  linux/drivers/media/Makefile|1
> > > >  linux/drivers/media/common/ir-keymaps.c |  221 +
> > > >  linux/drivers/media/dvb/b2c2/flexcop-fe-tuner.c |   21
> > > >  linux/drivers/media/dvb/bt8xx/dvb-bt8xx.c   |   34
> > > >  linux/drivers/media/dvb/dvb-core/dmxdev.c   |6
> > > >  linux/drivers/media/dvb/dvb-core/dmxdev.h   |1
> > > >  linux/drivers/media/dvb/dvb-core/dvb_demux.c|3
> > > >  linux/drivers/media/dvb/dvb-core/dvb_demux.h|3
> > > >  linux/drivers/media/dvb/dvb-core/dvb_frontend.c |   29
> > > >  linux/drivers/media/dvb/dvb-core/dvb_frontend.h |   64
> > > >  linux/drivers/media/dvb/dvb-core/dvb_net.c  |   29
> > > >  linux/drivers/media/dvb/dvb-core/dvb_net.h  |1
> > > >  linux/drivers/media/dvb/dvb-usb/af9005-fe.c |   12
> > > >  linux/drivers/media/dvb/dvb-usb/au6610.c|3
> > > >  linux/drivers/media/dvb/dvb-usb/cxusb.c |  150
> > > >  linux/drivers/media/dvb/dvb-usb/cxusb.h |2
> > > >  linux/drivers/media/dvb/dvb-usb/dib0700_devices.c   |7
> > > >  linux/drivers/media/dvb/dvb-usb/dibusb-common.c |6
> > > >  linux/drivers/media/dvb/dvb-usb/dibusb-mb.c |   17
> > > >  linux/drivers/media/dvb/dvb-usb/digitv.c|7
> > > >  linux/drivers/media/dvb/dvb-usb/dvb-usb-i2c.c   |   11
> > > >  linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h   |2
> > > >  linux/drivers/media/dvb/dvb-usb/dvb-usb.h   |8
> > > >  linux/drivers/media/dvb/dvb-usb/gl861.c |3
> > > >  linux/drivers/media/dvb/dvb-usb/m920x.c |   14
> > > >  linux/drivers/media/dvb/dvb-usb/opera1.c|3
> > > >  linux/drivers/media/dvb/dvb-usb/ttusb2.c|3
> > > >  linux/drivers/media/dvb/dvb-usb/umt-010.c   |3
> > > >  linux/drivers/media/dvb/frontends/at76c651.c|2
> > > >  linux/drivers/media/dvb/frontends/bsbe1.h   |3
> > > >  linux/drivers/media/dvb/frontends/bsru6.h   |3
> > > >  linux/drivers/media/dvb/frontends/cx22700.c |2
> > > >  linux/drivers/media/dvb/frontends/cx22702.c |2
> > > >  linux/drivers/media/dvb/frontends/cx24110.c |2
> > > >  linux/drivers/media/dvb/frontends/dib3000mb.c   |2
> > > >  linux/drivers/media/dvb/frontends/dib3000mc.c   |2
> > > >  linux/drivers/media/dvb/frontends/dib7000m.c|2
> > > >  linux/drivers/media/dvb/frontends/dib7000p.c|2
> > > >  linux/drivers/media/dvb/frontends/dvb-pll.c |   65
> > > >  linux/drivers/media/dvb/frontends/dvb-pll.h |   19
> > > >  linux/drivers/media/dvb/frontends/dvb_dummy_fe.c|2
> > > >  linux/drivers/media/dvb/frontends/l64781.c  |2
> > > >  linux/drivers/media/dvb/frontends/lgdt330x.c|6
> > > >  linux/drivers/media/dvb/frontends/mt2060.c  |   43
> > > >  linux/drivers/media/dvb/frontends/mt2060.h  |6
> > > >  linux/drivers/media/dvb/frontends/mt312.c   |2
> > > >  linux/drivers/media/dvb/frontends/mt352.c   |   15
> > > >  linux/drivers/media/dvb/frontends/mt352.h   |3
> > > >  linux/drivers/media/dvb/frontends/nxt200x.c |2
> > > >  linux/drivers/media/dvb/frontends/nxt6000.c |2
> > > >  linux/drivers/media/dvb/frontends/or51132.c |2
> > > >  linux/drivers/media/dvb/frontends/qt1010.c  |   59
> > > >  linux/drivers/media/dvb/frontends/qt1010.h  |4
> > > >  linux/drivers/media/dvb/frontends/s5h1420.c | 

[linux-dvb] Re: nova-t 500 progress?

[Robin Hill]

On Thu May 17, 2007 at 11:55:28AM +0100, Richard Morris wrote:

> I use 2 of the Nova-T 500's with MythTV, I get about 4 disconnects a day
> that either fill up the event log with messages like:
> 
> May 17 10:01:00 athlon mt2060 I2C read failed
> 
> and/or crash MythTV.
> 
I guess you're running with EIT scanning enabled?  Disabling this will
dramatically reduce the number of resets (I get about one a month with
my two cards).

Cheers,
Robin
-- 
 ___
( ' } |   Robin Hill <[EMAIL PROTECTED]>  |
   / / )  | Little Jim says |
  // !!   |  "He fallen in de water !!" |


pgpvaJOLmXRye.pgp
Description: PGP signature
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] HVR3000 DVB-T problems

[Simon Santoro]

On Thursday 17 May 2007 11:21:46 Simon Santoro wrote:
> Simon Santoro wrote:
> [CUT no DVB-T channels found]
>
[CUT analog channels not found]

I just made some more test, and it looks like that when kaffeine is scanning a 
frequecy where indeed a mux is present in my location, it prints out:

---
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 65800 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
 LOCKED.
Transponders: 33/63

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
---

At the same time dmesg says:
cx88[1]/2-mpeg: cx8802_timeout
I know that on 65800 Hz i have transponder, because the TV has a channel 
on that frequency.
It looks like I can get a lock, but the driver is somehow unable to get the 
mpeg stream?

Please help! :)

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] DVB-S streams with TT3200

[laasa]

laasa schrieb:


Christian Schuld schrieb:


Hello Laasa,

On Mittwoch, 9. Mai 2007, laasa wrote:

[ ... ]

 

When I read this dump correct and it is my second linux dump I ever 
seen, then in the function stb6100_set_frequency occures a divide by 
zero exception.
There are only 2 lines in the function stb6100_set_frequency where a 
division was made. In both lines the a divison by state->reference 
was made.
So I think that state->reference is zero, but normaly it was 
initialized before in stb6100_init.


3 ideas:
1) a printk in stb6100_init to see, if the function was called (and 
leave) before stb6100_set_frequency (or exception happens).
  



stb6100_init never gets called.

 

2) there is the possibility to give state->reference via 
stb6100_attach via the config-parameter refclock in budget-ci.c:

   struct stb6100_config tt3200_stb6100_config = {
   .tuner_address = 0x60,
   .refclock = 2700,
   };
  



That does the trick. Thanks :-)
But now szap2 doesn't work :-(
It produces an output like that on every transponder it try to tune to:

$ szap2 -a 1 "Prosieben"
zapping to 148 'ProSieben':
sat 0, frequency = 12480 MHz V, symbolrate 2750, vpid = 0x00ff, 
apid = 0x0100 sid = 0x0382 (fec = -2147483648, mod = 2)

Querying info .. Delivery system=DVB-S
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
--> Using 'STB0899 DVB-S' DVB-S
diseqc: sat_no:0 pol_vert:1 hi_band:1 cmd:e0 10 38 f1 wait:0

do_tune: API version=2, delivery system = 0
do_tune: Frequency = 188, Srate = 2750 (DVB-S)
do_tune: Frequency = 188, Srate = 2750 (SET_PARAMS)


status 00 | signal  | snr 0004 | ber  | unc fffe |
status 00 | signal  | snr 0004 | ber  | unc fffe |
[...]

Christian

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


 


Christian,
sorry for the delay.

two things:
- For me it is not clear that stb6100_init never gets called. Normally 
it is called in dvb_frontend_init (fe->ops.tuner_ops.init).

   => Can you check (e.g. with additional printk)?
   => May be it helps to call stb6100_init in stb6100_attach.
- Second is the hint in 
http://www.linuxtv.org/pipermail/linux-dvb/2007-May/017921.html to 
setup gpio:


   case 0x1019:// TT S2-3200 PCI
   // gpio2 is connected to CLB - reset it + leave it high
   saa7146_setgpio(budget_ci->budget.dev, 2, SAA7146_GPIO_OUTLO);
   msleep(1);
   saa7146_setgpio(budget_ci->budget.dev, 2, SAA7146_GPIO_OUTHI);
   msleep(1);

   budget_ci->budget.dvb_frontend = dvb_attach(stb0899_attach, 
...



Hope it helps.






___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Another thing to get better tuning is this code patch. But this is only 
a speed hack and no end solution.

I get now all DVB-S-channels :-) For DVB-S2-channels it does not help :-(

function stb0899_dvbs_algo in modul stb0899_algo.c
  ...
  /* release stream merger RESET*/
  reg = stb0899_read_reg(state, STB0899_TSTRES);
  STB0899_SETFIELD_VAL(FRESRS, reg, 0);
  stb0899_write_reg(state, STB0899_TSTRES, reg);

  /* TODO: */
  if (   ((internal->freq > 187) && (internal->freq < 189))
  || ((internal->freq > 157) && (internal->freq < 159))
  || ((internal->freq > 150) && (internal->freq < 152))
 )
  {/* special for ProSieben, RTL ... */
  printk("%s: special for 
frequency=%d\n",__func__,internal->freq);

  }
  else
  {
/* disable carrier detector*/
  reg = stb0899_read_reg(state, STB0899_CFD);
  STB0899_SETFIELD_VAL(CFD_ON, reg, 0);
  stb0899_write_reg(state, STB0899_RTF, reg);
  }

  stb0899_read_regs(state, STB0899_EQUAI1, eq_const, 10);
...

--

To get tuning more stable, it helps to have an retry in 
STB6100_set_frequency:


enum stb0899_status stb0899_dvbs_algo(struct stb0899_state *state)
{
   ...
   s32 retry = 0;
   ..
   stb0899_first_subrange(state);
   do {
   retry = 0;
   do
   {
 ...
   }
   while ( ++retry < 5 && (internal->status != RANGEOK) );
  
   if (internal->status != RANGEOK)

   next_sub_range(state);

   } while (internal->sub_range && internal->status != RANGEOK);
   ...

Hope it helps.



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] JTVOS: a "wannabe" java interactive DTV ..

[Andrea Venturi]

hi,

i think this post could be slightly relevant. it's about DVB and linux,
actually on the dreambox, but, tomorrow, maybe also on a generic linux
box. if you like it please help us!

today Cineca is _starting_ yet another project with regard interactive
digital television: a free java based middleware for STB.

actually this is a long term roadmap. we are in the first stage: the
bootstrap one.

since many years, Cineca created and gave away (as free tools) some
building blocks on the infrastructure side on the interactive digital tv
chain:

- some java interactive applications (let's call them in a more broad
sense then MHP xlets), i.e. we gave away Yambo an XML browser
(ASAP it's coming a next release with stream event and other interesting
features), and T-islessia a fairly advanced game engine for the tv set.

(BTW these MHP apps are going to be stripped down to run easily on a
subset of the "bloated" MHP environment. the subset supported by JTVOS
of course!)

- a DVB and DSM-CC carousel server for the DVB signaling and
broadcasting of these java applications: JustDvb-It:  BTW we are soon
releasing the 2.0 version with advanced features like: compressed
modules, NIT LCN support, MHP stored applications (where it applies like
MHP 1.1), MHEG5 support and so on..

now it's the time to tackle the STB middleware too. the market is not
going to offer too many choices and control on this piece of the value
chain, so we'd like to push (a very little) pressure with a little niche
free open source project: JTVOS

actually it's not a fully blown package. it's just an exciting starting
point.

JTVOS is a fairly compact package with the porting of the GPL licensed
Java VM (PBP 1.1) from Sun on a Dreambox 7000 environment (stripped down
from their enigma engine..), and the first (and only) Java Application
working on the tv is the traditional "hello world" with the IP address
of the box on which is running!

that's all. there's a lot of things to be done to come to a useful firmware.

we need STB designers (for the GUI and the navigation of the features),
java programmers, graphic artists, documentation, people for the
testing, system programmer to drive the other hardware pieces and so on..

lot of entertainment is forecasted! :-)

maybe it can be ported to many different HW platforms. actually it just
run on the Dreambox 7000. a natively linux platform.

please read carefully the few informations you can find in the package
and here:

  http://www.cineca.tv/labs/jtv/

BTW register yourself to grab a copy of the build environment (only 70MB
but 300MB untarred, and 1.7GB after a succesfully complete compilation)
or just the dreambox image to try it (no warranty!!) on your box.

hope you'll enjoy and keep us informed.

bye

andrea venturi



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: [RFC/PATCHES] xc3028 hybrid tuner, em28xx/em2880-dvb, saa7134, cx88

[Oliver Endriss]

Markus Rechberger wrote:
> On 5/15/07, Oliver Endriss <[EMAIL PROTECTED]> wrote:
> > Markus Rechberger wrote:
> > > to be more accurate where all the changes happened:
> > >  b/linux/drivers/media/tuners/Kconfig|   14
> > >  b/linux/drivers/media/tuners/Makefile   |7
> > >  b/linux/drivers/media/tuners/xc3028-tuner.c |  601 
> > >  b/linux/drivers/media/tuners/xc3028-tuner.h |   20
> > >  b/linux/drivers/media/video/em28xx/em2880-dvb.c |  748 
> > >  b/linux/drivers/media/video/em28xx/em28xx-audio.c   |  439 ++
> > >  b/linux/drivers/media/video/em28xx/em28xx-webcam.c  |  365 ++
> > >  b/linux/include/media/v4l_dvb_tuner.h   |  131
> > >  linux/Documentation/video4linux/CARDLIST.cx88   |3
> > >  linux/Documentation/video4linux/CARDLIST.em28xx |   69
> > >  linux/Documentation/video4linux/CARDLIST.tuner  |1
> > >  linux/drivers/media/Kconfig |2
> > >  linux/drivers/media/Makefile|1
> > >  linux/drivers/media/common/ir-keymaps.c |  221 +
> > >  linux/drivers/media/dvb/b2c2/flexcop-fe-tuner.c |   21
> > >  linux/drivers/media/dvb/bt8xx/dvb-bt8xx.c   |   34
> > >  linux/drivers/media/dvb/dvb-core/dmxdev.c   |6
> > >  linux/drivers/media/dvb/dvb-core/dmxdev.h   |1
> > >  linux/drivers/media/dvb/dvb-core/dvb_demux.c|3
> > >  linux/drivers/media/dvb/dvb-core/dvb_demux.h|3
> > >  linux/drivers/media/dvb/dvb-core/dvb_frontend.c |   29
> > >  linux/drivers/media/dvb/dvb-core/dvb_frontend.h |   64
> > >  linux/drivers/media/dvb/dvb-core/dvb_net.c  |   29
> > >  linux/drivers/media/dvb/dvb-core/dvb_net.h  |1
> > >  linux/drivers/media/dvb/dvb-usb/af9005-fe.c |   12
> > >  linux/drivers/media/dvb/dvb-usb/au6610.c|3
> > >  linux/drivers/media/dvb/dvb-usb/cxusb.c |  150
> > >  linux/drivers/media/dvb/dvb-usb/cxusb.h |2
> > >  linux/drivers/media/dvb/dvb-usb/dib0700_devices.c   |7
> > >  linux/drivers/media/dvb/dvb-usb/dibusb-common.c |6
> > >  linux/drivers/media/dvb/dvb-usb/dibusb-mb.c |   17
> > >  linux/drivers/media/dvb/dvb-usb/digitv.c|7
> > >  linux/drivers/media/dvb/dvb-usb/dvb-usb-i2c.c   |   11
> > >  linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h   |2
> > >  linux/drivers/media/dvb/dvb-usb/dvb-usb.h   |8
> > >  linux/drivers/media/dvb/dvb-usb/gl861.c |3
> > >  linux/drivers/media/dvb/dvb-usb/m920x.c |   14
> > >  linux/drivers/media/dvb/dvb-usb/opera1.c|3
> > >  linux/drivers/media/dvb/dvb-usb/ttusb2.c|3
> > >  linux/drivers/media/dvb/dvb-usb/umt-010.c   |3
> > >  linux/drivers/media/dvb/frontends/at76c651.c|2
> > >  linux/drivers/media/dvb/frontends/bsbe1.h   |3
> > >  linux/drivers/media/dvb/frontends/bsru6.h   |3
> > >  linux/drivers/media/dvb/frontends/cx22700.c |2
> > >  linux/drivers/media/dvb/frontends/cx22702.c |2
> > >  linux/drivers/media/dvb/frontends/cx24110.c |2
> > >  linux/drivers/media/dvb/frontends/dib3000mb.c   |2
> > >  linux/drivers/media/dvb/frontends/dib3000mc.c   |2
> > >  linux/drivers/media/dvb/frontends/dib7000m.c|2
> > >  linux/drivers/media/dvb/frontends/dib7000p.c|2
> > >  linux/drivers/media/dvb/frontends/dvb-pll.c |   65
> > >  linux/drivers/media/dvb/frontends/dvb-pll.h |   19
> > >  linux/drivers/media/dvb/frontends/dvb_dummy_fe.c|2
> > >  linux/drivers/media/dvb/frontends/l64781.c  |2
> > >  linux/drivers/media/dvb/frontends/lgdt330x.c|6
> > >  linux/drivers/media/dvb/frontends/mt2060.c  |   43
> > >  linux/drivers/media/dvb/frontends/mt2060.h  |6
> > >  linux/drivers/media/dvb/frontends/mt312.c   |2
> > >  linux/drivers/media/dvb/frontends/mt352.c   |   15
> > >  linux/drivers/media/dvb/frontends/mt352.h   |3
> > >  linux/drivers/media/dvb/frontends/nxt200x.c |2
> > >  linux/drivers/media/dvb/frontends/nxt6000.c |2
> > >  linux/drivers/media/dvb/frontends/or51132.c |2
> > >  linux/drivers/media/dvb/frontends/qt1010.c  |   59
> > >  linux/drivers/media/dvb/frontends/qt1010.h  |4
> > >  linux/drivers/media/dvb/frontends/s5h1420.c |6
> > >  linux/drivers/media/dvb/frontends/sp8870.c  |2
> > >  linux/drivers/media/dvb/frontends/sp887x.c  |4
> > >  linux/drivers/media/dvb/frontends/stv0297.c   

[linux-dvb] Re: New Devices (Testers wanted)

[Markus Rechberger]

On 5/17/07, Daniel Gimpelevich <[EMAIL PROTECTED]> wrote:

On Thu, 17 May 2007 17:40:04 +0200, Markus Rechberger wrote:

> Hi,
>
> I put together a list of devices which are managed on mcentral.de, I'm
> looking for a list of outstanding bugs and people who are willing to
> work on getting them resolved.
>
> The list counts 56 (dvb-t/analogue/hybrid) devices at the moment, I
> will add a few more during the next few days.
[snip]
> http://mcentral.de/wiki/index.php/Linuxtv
>
> thanks,
> Markus

I can test the PowerColor Real Angel 330, but not immediately. It was
apparently marketed as an analog-only device, but if I can coax it to tune
ATSC as well, all the better.


ATSC does not work yet but I'll add it very soon! :-)

Markus

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] DVB-S streams with TT3200

[laasa]

Christian Schuld schrieb:


Hello Laasa,

On Mittwoch, 9. Mai 2007, laasa wrote:

[ ... ]

 

When I read this dump correct and it is my second linux dump I ever 
seen, then in the function stb6100_set_frequency occures a divide by 
zero exception.
There are only 2 lines in the function stb6100_set_frequency where a 
division was made. In both lines the a divison by state->reference was made.
So I think that state->reference is zero, but normaly it was initialized 
before in stb6100_init.


3 ideas:
1) a printk in stb6100_init to see, if the function was called (and 
leave) before stb6100_set_frequency (or exception happens).
   



stb6100_init never gets called.

 

2) there is the possibility to give state->reference via stb6100_attach 
via the config-parameter refclock in budget-ci.c:

   struct stb6100_config tt3200_stb6100_config = {
   .tuner_address = 0x60,
   .refclock = 2700,
   };
   



That does the trick. Thanks :-) 


But now szap2 doesn't work :-(
It produces an output like that on every transponder it try to tune to:

$ szap2 -a 1 "Prosieben"
zapping to 148 'ProSieben':
sat 0, frequency = 12480 MHz V, symbolrate 2750, vpid = 0x00ff, apid = 
0x0100 sid = 0x0382 (fec = -2147483648, mod = 2)
Querying info .. Delivery system=DVB-S
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
--> Using 'STB0899 DVB-S' DVB-S
diseqc: sat_no:0 pol_vert:1 hi_band:1 cmd:e0 10 38 f1 wait:0

do_tune: API version=2, delivery system = 0
do_tune: Frequency = 188, Srate = 2750 (DVB-S)
do_tune: Frequency = 188, Srate = 2750 (SET_PARAMS)


status 00 | signal  | snr 0004 | ber  | unc fffe |
status 00 | signal  | snr 0004 | ber  | unc fffe |
[...]

Christian

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


 


Christian,
sorry for the delay.

two things:
- For me it is not clear that stb6100_init never gets called. Normally 
it is called in dvb_frontend_init (fe->ops.tuner_ops.init).

   => Can you check (e.g. with additional printk)?
   => May be it helps to call stb6100_init in stb6100_attach.
- Second is the hint in 
http://www.linuxtv.org/pipermail/linux-dvb/2007-May/017921.html to setup 
gpio:


   case 0x1019:// TT S2-3200 PCI
   // gpio2 is connected to CLB - reset it + leave it high
   saa7146_setgpio(budget_ci->budget.dev, 2, SAA7146_GPIO_OUTLO);
   msleep(1);
   saa7146_setgpio(budget_ci->budget.dev, 2, SAA7146_GPIO_OUTHI);
   msleep(1);

   budget_ci->budget.dvb_frontend = dvb_attach(stb0899_attach, 
	...



Hope it helps.






___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: [RFC/PATCHES] xc3028 hybrid tuner, em28xx/em2880-dvb, saa7134, cx88

[Mauro Carvalho Chehab]

Michael,

On Wed, 16 May 2007, Michael Krufky wrote:


Mauro Carvalho Chehab wrote:



The proposed changes are simply too large and span too many source files
to achieve a proper review by enough developers, especially in their
"spare time," not to mention all the regression testing that needs to be
done.

As much as we try to come to an agreement about this right now, I fear
that it will be very difficult -- this debate has gone on for over a
year and reaching an agreement will not be easy.

Please take note, that if we proceed in the order above, this will allow
us to merge the majority of Markus' changes, leaving only the api
changes behind.  At this point, the remainder of the changesets will be
MUCH smaller, and much easier to review.

If you simply shoot me down for the idea of temporarily having a
separate dvb module for the dvb subsystem to interface with the xc3028
tuner,  then you are not seeing the big picture.


I think you have only a partial view of the big picture.

We should remind that we've started discussing a common code for tuners 
even before Markus iniciative, when we've re-designed tuner-simple to look 
like dvb-pll in a way that the same code could handle both functions.


Every time someone tries to work on this direction, people run away, 
opting to the path of duplicating the code. Until now, the argues in favor 
of the duplication relies in the fact that the duplicated code on dvb-pll 
and tuner-simple is not big. For xc3028, however, it is a big code 
duplication. Also, I can't foresee any hope on a common code in the near 
future if we go to the duplication path.


To make things worse, duplicating xc3028 code means a complete rework on 
em28xx code. This doesn't seem to be good and won't solve the issue.


IMO, we should really focus on some code proposition and work on it, until 
have most of us happy, not risking break any driver.


That's said, we should really try to cope together for having a solution.

From my side, I've actively reviewed all Markus patch series. The changes 
are not so big, but, since he replaced the usage of the main dvb frontend 
struct to a newer one, all drivers needed to be changed. His series looks 
ok, but, as touches on all frontends, the internal API should be tested 
for all drivers.


The proposed an alternative patch series I've worked were just adding the 
newer fields needed from his approach into dvb_frontend struct.


My suggestion is to you all to take a look on those changes. If the 
direction (on Marcus original series or on my series) is ok, we can 
improve the corresponding patch series as needed, with contributions from 
the developers.


The API changes(*) on my proposed series are all at:

http://linuxtv.org/~mchehab/mrec2/hg_mrec_01.patch

(*) Please ignore the "removal" of xc3028.c from the patch above - The 
driver were renamed on Markus tree and moved to another directory. If all 
accept this approach, I will move that part to the patch that creates 
tuner-xc3028.c.


Cheers,
Mauro.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] [PATCH] Improved support for Dual Digital 4 in v4l-dvb-experimental

[Markus Rechberger]

Hi John,

On 5/12/07, John Newbigin <[EMAIL PROTECTED]> wrote:

Markus Rechberger wrote:
>
>
> Anyway do you know the exact difference between DVB-T in Australia and
> other countries?
I can answer that.  AS4599 and AS4933 are the standards for DVB-T in
Australia.  It is basically ETSI standard DVB-T.  It defines the
meanings of content descriptors and ratings and introduces descriptor
0x83 for the recommended channel (which I think is a UK standard), none
of which should impact on the driver.  It also defines which streams
should be used for various formats.  There is a lot to do with PAL
compatibility (for set top boxes etc)

The actual frequencies for broadcast are the same channels as used for
analog.  All channels are 7Mhz (except UHF27 which is only 6MHz and not
used although it /might/ get used in the future for radio).  Long term
the ACMA want to use SFN but I don't know if anyone does yet.  Channels
may use (with the permission of the ACMA) a +/-125kHz offset to prevent
interference with other services etc. The channels suitable for DVB-T
range from 17750 through to 81650 (center frequency)

Transmission may use 2k or 8k COFDM carrier. Transmitters may use
hierarchical modes but I don't think any currently do.

Basically, the major difference is 7Mhz channels.

I have done a lot of research on DVB-T in AUS if anyone whats more details.



can you give us more information about that? The Xceive
firmwarepackage contains extra firmwares for Australia, it would be
good to directly focus on the specific difference instead of passing
eg. a countrycode to a dvb driver (this shouldn't be an option)

thanks,
Markus

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Integration of HVR4000

[Uwe Schmeling]

Hi,

when is it planned to merge the HVR4000 drivers into kernel? It is
running stable for me since several weeks
and other people had also success with this card, so why not integrating?

regards Uwe

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Re: [RFC/PATCHES] xc3028 hybrid tuner, em28xx/em2880-dvb, saa7134, cx88

[hermann pitton]

Am Montag, den 14.05.2007, 13:39 -0700 schrieb Trent Piepho:
> On Mon, 14 May 2007, Markus Rechberger wrote:
> > Hi all,
> >
> > I exported the patches of my v4l-dvb-experimental repository against
> > the current v4l-dvb repository on linuxtv.org.
> >
> > The single patchfiles are available on mcentral.de
> > http://mcentral.de/~mrec/patches/v4l-dvb/
> [93 patches]

actually 78 and on missing 16 i stopped, seeing your clashes already.

> It's really hard for anyone to make sense of a patch bomb like this.
> There's just too many changes, and none of the patches even have comments
> longer than one line.
> 
> The organization of the patches is really hard to follow too.  For example,
> patch 19 adds a NULL pointer check to tuner-core (why is this necessary?)
> and then also adds two register names names to the dvb zl10353 driver.
> Those changes have nothing to do with each other.  It's patch 20 that
> actually adds the code to zl10353 that uses the new registers, and it even
> changes the names used in patch 19.
> 

Trent, any chance to get it up to current level for testing and to make
next time less hard? I'm willing to waste time (and devices) on it.

Greetings,
Hermann






___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Please help, best support USB DVB-S?

[Mark Buechler]

I'm looking to upgrade my system and it seems all the newer rackmount
systems from Dell, IBM, HP and the like all have 3.3v PCI slots only and the
majority of my DVB-S cards are 5v. So, I'm wondering if someone can tell me
the most stable best supported USB DVB-S module available.

Thanks, Mark.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] New Devices (Testers wanted)

[Markus Rechberger]

Hi,

I put together a list of devices which are managed on mcentral.de, I'm
looking for a list of outstanding bugs and people who are willing to
work on getting them resolved.

The list counts 56 (dvb-t/analogue/hybrid) devices at the moment, I
will add a few more during the next few days.

Compro VideoMate T750
Pinnacle PCTV Hybrid (PCMCIA)
Winfast TV 2000 XP Global
Powercolor Real Angel
Avermedia A16D
Avermedia M115
Avermedia Cardbus 506
Terratec Cinergy 250 USB
Pinnacle PCTV USB 2
Hauppauge WinTV USB 2
MSI VOX USB 2.0
Terratec Cinergy 200 USB
Leadtek Winfast USB II
Kworld USB2800
Pinnacle Dazzle DVC 90
Hauppauge WinTV HVR 900
Terratec Hybrid XS
Terratec Hybrid XS Secam
Kworld PVR TV 2800 RF
Terratec Prodigy XS
Videology 20K14XUSB USB2.0
Usbgear VD204v9
Terratec Cinergy T XS
Pinnacle PCTV DVB-T
DNT DA2 Hybrid
Pinnacle Hybrid Pro
Hercules Smart TV USB 2.0
Compro, VideoMate U3
KWorld DVB-T 310U
SIIG AVTuner-PVR/Prolink PlayTV USB 2.0
Terratec Cinergy T XS (MT2060)
MSI DigiVox A/D
D-Link DUB-T210 TV Tuner
Gadmei UTV310
Kworld 355 U DVB-T
Supercomp USB 2.0 TV
Hauppauge WinTV HVR Rev. 1.2
Gadmei UTV330
V-Gear PocketTV
Kworld 350 U DVB-T
Terratec Hybrid XS (em2882)
Pinnacle Dazzle DVC 100
Yakumo MovieMixer
Huaqi DLCW-130
Generic EM2883 video grabber
Hauppauge WinTV HVR 950
Pinnacle PCTV HD Pro
Pinnacle Hybrid Pro (2)
Hauppauge WinTV USB 2 (R2)
NetGMBH Cam
Leadtek Winfast USB II Deluxe
MSI DigiVox A/D II
Typhoon DVD Maker
Pinnacle PCTV USB 2 (Philips FM1216ME)
KWorld DVB-T 305U
KWorld PVRTV 300U

http://mcentral.de/wiki/index.php/Linuxtv

thanks,
Markus

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

RE: [linux-dvb] Divco Fusion HDTVDVB-T PlusNoAudio for composite/s-video input

[Anthony Giggins]

Well I finally tried with arecord but still no good with the internal cable
connected to the AUX on the soundcard. I don't have the right cable too test
direct too the line in jack on the sound card (I know this works for
pass-through playback I tested with a mp3 player but not under mythtv), I'll
try and borrow the right cable so I can test further.

Michael any luck with the GPIO information I provided?

Would this be best posted on the video4linux mailing list?

Thanks Anthony

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Anthony Giggins
Sent: Monday, 7 May 2007 7:39 AM
To: linux-dvb@linuxtv.org
Subject: RE: [linux-dvb] Divco Fusion HDTVDVB-T PlusNoAudio for
composite/s-video input

I've tried using the line in on the soundcard, in mythtv for the audio but
it caused issues with normal audio play back, it might work better with
arecord/aplay, I'll give this a go when I get some spare time, it would be
great if the GPIO gets it working through the internal cable.

Yeah it works fine under windows with the audio cable connected too the AUX
connector.

Thanks Anthony

-Original Message-
From: John Newbigin [mailto:[EMAIL PROTECTED] 
Sent: Sunday, 6 May 2007 3:06 PM
To: Anthony Giggins
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Divco Fusion HDTV DVB-T PlusNoAudio for
composite/s-video input

I just checked my setup.  I actually just have the audio connected 
directly to the motherboard line in jack.

Alsa 'capture' settings are
Line = Capture
Capture = Capture
Capture volume = 0.  You can bump this up but I get clipping.

You can get a VU meter by running
arecord -f dat -D plug:dsnoop -v -v -v /dev/null

If that works and you already have aplay working, you can use
arecord -f dat -D plug:dsnoop | aplay

Perhaps some GPIO might enable the sound cable on the dvico card, I 
don't know.  Does it work under windows if you use the audio cable?

John.

Anthony Giggins wrote:
> Yes I have the same card as you John 
>
>
> Vendor ID:   0x14f1
> Device ID:   0x8800
> Subsystem ID:0xdb1018ac
>
> Please let me know your alsa setting I have tried everything :(
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> On Behalf Of Anthony Giggins
> Sent: Saturday, 5 May 2007 11:35 PM
> To: linux-dvb@linuxtv.org
> Subject: RE: [linux-dvb] Divco Fusion HDTV DVB-T PlusNoAudio for
> composite/s-video input
>
> The card I have is subsystem: 18ac:db10 not sure where your getting the
> 14f1:8802 from.
>
> Can you please tell me how you have configured your alsa I have tried
> connecting the supplied cable too both the AUX and the CDROM inputs on the
> SBlive sound card I am using.
>
> I'll hopefully be attempting the regspy GPIO stuff tomorrow if all goes
too
> plan.
>
> Thanks for the idea, keep them coming :)
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> On Behalf Of John Newbigin
> Sent: Saturday, 5 May 2007 4:47 PM
> To: linux-dvb@linuxtv.org
> Subject: Re: [linux-dvb] Divco Fusion HDTV DVB-T Plus NoAudio for
> composite/s-video input
>
> Is this the 14f1:8802 Subsystem: 18ac:db10
>
> If so, I have the same card.  It does not support audio capture.  You
> must you the supplied cable to connect to you sound card aux/line in.
>
> You then must configure alsa correctly to allow recording from the input
> you are using (test with arecord | aplay)
>
> I also found the analog capture on this card is rubbish and I would
> recommend people avoid it.  The digital works fine.
>
> John.
>
> Michael Krufky wrote:
>   
>> Anthony Giggins wrote:
>>   
>> 
>>> Hello Everyone,
>>>
>>> I am using this card with Mythtv under mythdora distro
(www.mythdora.com)
>>> for DVB with minimal problems but I am unable too get any audio via
>>> composite/s-video input, video works fine.
>>> This is pretty much my last remaining problem, I've searched every
>>>   
> mailing
>   
>>> list I can think of and have several other people in the same boat in
>>> varying distro's can anyone give me anything I can try, the passthrough
>>> audio cable is plugged into my SB Live value card and I believe I have
>>> alsa configured correctly but I could be wrong.
>>>
>>> Please Help!
>>> 
>>>   
>> We may need to program the GPIO for those input muxes... Please see the
>> 
> GPIO pins section, cx2388x subsection of the v4lwiki, located at
> http://linuxtv.org/v4lwiki ... You'll need to use regspy, which is part of
> the dscaler project, in conjunction with the DViCO windows drivers and
> FusionHDTV application, in order to sniff the GPIO settings of the windows
> driver.  With that data, we should be able to resolve this problem for
you.
>   
>> I am looking at the current code, which sets gpio0 to 0x27df ...
>> 
> Perhaps this is inaccurate, or you have an alternate revision of this
model.
> Let me know what you find from regspy.
>   
>> Good Luck,
>>
>> Mike Krufky


__

Re: [linux-dvb] Re: [RFC/PATCHES] xc3028 hybrid tuner, em28xx/em2880-dvb, saa7134, cx88

[Markus Rechberger]

On 5/17/07, Johannes Stezenbach <[EMAIL PROTECTED]> wrote:

On Thu, May 17, 2007, Markus Rechberger wrote:
> On 5/17/07, Johannes Stezenbach <[EMAIL PROTECTED]> wrote:
> >On Thu, May 17, 2007, Markus Rechberger wrote:
> >>
> >> I will not go back anymore, instead a fork off seems to be a good
> >> solution if the linuxtv project wants to stay stuck where it is at the
> >> moment it should do so.
> >
> >Yep, we all know by know the linux-dvb crowd is not an easy one.
> >
> >So what? If your goal is to get your drivers merged, it
> >seems the _fastest_ way is to take the detour,
> >even if it means additional work for you.
>
> Ok, so it only keeps one possibility open to start another official
> linuxtv project.
>
> The current approach is quite mature already, the other approaches are
> incomplete or will just kick everything back where it was already a
> long time ago.
>
> I redid the code 3 times already so I don't see another option, this
> all seems very rude to me since there hasn't been any review on the
> code either.
>
> Any last comments on all that?

Well, I see the option of redoing the code a fourth time.
I'm glad you asked. ;-)

I'm sorry but I currently see no other way to get your code merged.

But it's _your_ choice.



It's ok I won't write another further replies about it and I do not
share this opinion since during the history there have been enough
offers from my side to include the code.

bye,
Markus

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] [PATCH] Compro VideoMate T750

[Markus Rechberger]

Hi,

I added this patch to the repository, can you please retry?
There has been some work going on with the qt1010, we might see some
changes from that part too soon.

thanks,
Markus

On 4/26/07, Chris Johns <[EMAIL PROTECTED]> wrote:

John Newbigin wrote:
> This patch add support for Compro VideoMate T750 to the saa7134 driver
> in v4l-dvb-experimental
> Analog TV is working
> Digital is detected but not yet working

I applied the patch (did not apply cleanly but I suspect this is me and hg)
and it built. I do not get any analog TV. The dmesg gives:

saa7130/34: v4l2 driver version 0.2.14 loaded
ACPI: PCI Interrupt :02:03.0[A] -> GSI 16 (level, low) -> IRQ 18
saa7133[0]: found at :02:03.0, rev: 209, irq: 18, latency: 32, mmio:
0xfb005000
saa7133[0]: subsystem: 185b:c900, board: Compro VideoMate T750
[card=116,autodetected]
saa7133[0]: board init: gpio is 84bf00
saa7133[0]: Oops: IR config error [card=116]
saa7133[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: 01 40 01 03 03 01 03 01 08 ff 00 89 ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff d7 00 c4 86 1e 05 ff 02 c2 ff 01 ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb
saa7133[0]: i2c eeprom 60: 30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
tuner 1-0062: chip found @ 0xc4 (saa7133[0])
tuner 1-0063: chip found @ 0xc6 (saa7133[0])
tuner 1-0068: chip found @ 0xd0 (saa7133[0])
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[0]: registered device radio0
Quantek QT1010 successfully identified.
DVB: registering new adapter (saa7133[0]).
DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)...

When I run tvtime and scan I get this message repeating:

tuner 1-0062: tuner type not set

Regards
Chris

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb




--
Markus Rechberger

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] (AN2235) tuning failed using latest v4l-dvb

[Mr SOUISSI]

hi,
My artec dvb-t usb work fine with some "old (cvs) dvb driver" using dvb-pll
patch.
i try with latest (hg) v4l-dvb and Debian (etch) offciel kernel (2.6.18-4-k7),
nothing... :/

my syslog
May 17 15:39:57 john kernel: usb 1-1: new full speed USB device using
uhci_hcd and address 9
May 17 15:39:57 john kernel: usb 1-1: configuration #1 chosen from 1 choice
May 17 15:39:58 john kernel: dvb-usb: found a 'Artec T1 USB1.1 TVBOX with
AN2235 (faulty USB IDs)' in cold state, will try to load a firmware
May 17 15:39:58 john kernel: dvb-usb: downloading firmware from file '
dvb-usb-dibusb-an2235-01.fw'
May 17 15:39:58 john kernel: usbcore: registered new driver
dvb_usb_dibusb_mb
May 17 15:39:58 john kernel: usb 1-1: USB disconnect, address 9
May 17 15:39:58 john kernel: dvb-usb: generic DVB-USB module successfully
deinitialized and disconnected.
May 17 15:40:00 john kernel: usb 1-1: new full speed USB device using
uhci_hcd and address 10
May 17 15:40:00 john kernel: usb 1-1: configuration #1 chosen from 1 choice
May 17 15:40:00 john kernel: dvb-usb: found a 'DiBcom USB1.1 DVB-T reference
design (MOD3000)' in warm state.
May 17 15:40:00 john kernel: i2c_adapter i2c-6: SMBus Quick command not
supported, can't probe for chips
May 17 15:40:00 john kernel: i2c_adapter i2c-6: SMBus Quick command not
supported, can't probe for chips
May 17 15:40:00 john kernel: dvb-usb: will use the device's hardware PID
filter (table count: 16).
May 17 15:40:00 john kernel: DVB: registering new adapter (DiBcom
USB1.1DVB-T reference design (MOD3000))
May 17 15:40:00 john kernel: DVB: registering frontend 1 (DiBcom 3000M-B
DVB-T)...
May 17 15:40:00 john kernel: dibusb: This device has the Panasonic
ENV77H11D5 onboard.
May 17 15:40:00 john kernel: input: IR-receiver inside an USB DVB receiver
as /class/input/input8
May 17 15:40:00 john kernel: dvb-usb: schedule remote query interval to 150
msecs.
May 17 15:40:00 john kernel: dvb-usb: DiBcom USB1.1 DVB-T reference design
(MOD3000) successfully initialized and connected.

dvbscan -a 1 .kde/share/apps/kaffeine/dvb-t/fr-Albi > channels.conf

scanning .kde/share/apps/kaffeine/dvb-t/fr-Albi
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder 73000 0 9 0 3 1 4 0
initial transponder 75400 0 9 0 3 1 4 0
initial transponder 69800 0 9 0 3 1 4 0
initial transponder 60200 0 9 0 3 1 4 0
initial transponder 74600 0 9 0 3 1 4 0
initial transponder 81800 0 9 0 3 1 4 0

tune to:

73000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_AUTO:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
 and all failed

same problem using kaffeine (no signal)

modinfo /lib/modules/2.6.18-4-k7/kernel/drivers/media/dvb/dvb-usb/dvb-
usb-dibusb-mb.ko
filename:
/lib/modules/2.6.18-4-k7/kernel/drivers/media/dvb/dvb-usb/dvb-
usb-dibusb-mb.ko
author: Patrick Boettcher <[EMAIL PROTECTED]>
description:Driver for DiBcom USB DVB-T devices (DiB3000M-B based)
version:1.0
license:GPL
vermagic:   2.6.18-4-k7 SMP mod_unload K7 REGPARM gcc-4.1
depends:dvb-usb,dvb-usb-dibusb-common,i2c-core,usbcore,dvb-pll
alias:  usb:v14AAp0001d*dc*dsc*dp*ic*isc*ip*


Thanks.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: [RFC/PATCHES] xc3028 hybrid tuner, em28xx/em2880-dvb, saa7134, cx88

[Johannes Stezenbach]

On Thu, May 17, 2007, Markus Rechberger wrote:
> On 5/17/07, Johannes Stezenbach <[EMAIL PROTECTED]> wrote:
> >On Thu, May 17, 2007, Markus Rechberger wrote:
> >>
> >> I will not go back anymore, instead a fork off seems to be a good
> >> solution if the linuxtv project wants to stay stuck where it is at the
> >> moment it should do so.
> >
> >Yep, we all know by know the linux-dvb crowd is not an easy one.
> >
> >So what? If your goal is to get your drivers merged, it
> >seems the _fastest_ way is to take the detour,
> >even if it means additional work for you.
> 
> Ok, so it only keeps one possibility open to start another official
> linuxtv project.
> 
> The current approach is quite mature already, the other approaches are
> incomplete or will just kick everything back where it was already a
> long time ago.
> 
> I redid the code 3 times already so I don't see another option, this
> all seems very rude to me since there hasn't been any review on the
> code either.
> 
> Any last comments on all that?

Well, I see the option of redoing the code a fourth time.
I'm glad you asked. ;-)

I'm sorry but I currently see no other way to get your code merged.

But it's _your_ choice.


Johannes

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: [RFC/PATCHES] xc3028 hybrid tuner, em28xx/em2880-dvb, saa7134, cx88

[Markus Rechberger]

On 5/17/07, Johannes Stezenbach <[EMAIL PROTECTED]> wrote:

On Thu, May 17, 2007, Markus Rechberger wrote:
>
> I will not go back anymore, instead a fork off seems to be a good
> solution if the linuxtv project wants to stay stuck where it is at the
> moment it should do so.

Yep, we all know by know the linux-dvb crowd is not an easy one.

So what? If your goal is to get your drivers merged, it
seems the _fastest_ way is to take the detour,
even if it means additional work for you.



Ok, so it only keeps one possibility open to start another official
linuxtv project.

The current approach is quite mature already, the other approaches are
incomplete or will just kick everything back where it was already a
long time ago.

I redid the code 3 times already so I don't see another option, this
all seems very rude to me since there hasn't been any review on the
code either.

Any last comments on all that?

Markus


Sorry if that is a bitter pill to swallow, but I
see little other chances to get going forward.


Johannes




--
Markus Rechberger

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] RE: Hauppauge WinTV Nova-T USB Stick

[Pierre]

>> But as soon as I have run tzap I get the following errors repeated in the
logs:
>> May 13 20:08:38 toshiba kernel: mt2060 I2C read failed May 13 20:09:09 
>> toshiba last message repeated 227 times
 
> I wonder if that's related to the above I2C warning...
Perhaps, but I installed it on another machine I didn't get this warning,
but still had the same error in the logs.
 
>> I tried getting the latest dvb modules:
>> hg clone http://linuxtv.org/hg/v4l-dvbcd v4l-dvb make make install
[snip]
>> But still no difference, has anyone got a solution?
 
> You *did* reload the modules...? :-) 
Yep
 
Is it a question of just waiting for an update to the modules?


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] [PATCH] Correct an error in uk-PontopPike (tuning failure)

[Darren Salt]

Tuning fails when I run 'scan uk-PontopPike' with my Nova-T USB sticks.
However, it succeeds when I instead point it at one of my Nova-T PCI cards
(cx88).

Setting FEC_HI to 3/4 works with both, as does setting it to NONE; also,
setting FEC_LO to 3/4 works. This is expected, since previously-generated
channels.conf files say 3/4 for both (for channels on the same frequency) and
otherwise agree with the scan file.

I have therefore chosen to set both to 3/4.

diff -r 9461233ee3df util/scan/dvb-t/uk-PontopPike
--- a/util/scan/dvb-t/uk-PontopPike Wed May 16 21:20:16 2007 +0200
+++ b/util/scan/dvb-t/uk-PontopPike Thu May 17 14:06:50 2007 +0100
@@ -1,3 +1,3 @@
 # Pontop Pike, UK
 # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
-T 69000 8MHz 1/2 NONE QAM16 2k 1/32 NONE
+T 69000 8MHz 3/4 3/4 QAM16 2k 1/32 NONE

-- 
| Darren Salt| linux or ds at  | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Lobby friends, family, business, government.WE'RE KILLING THE PLANET.

If a bus stops at a bus station, does work stop at a workstation?

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: [RFC/PATCHES] xc3028 hybrid tuner, em28xx/em2880-dvb, saa7134, cx88

[Johannes Stezenbach]

On Thu, May 17, 2007, Markus Rechberger wrote:
> 
> I will not go back anymore, instead a fork off seems to be a good
> solution if the linuxtv project wants to stay stuck where it is at the
> moment it should do so.

Yep, we all know by know the linux-dvb crowd is not an easy one.

So what? If your goal is to get your drivers merged, it
seems the _fastest_ way is to take the detour,
even if it means additional work for you.

Sorry if that is a bitter pill to swallow, but I
see little other chances to get going forward.


Johannes

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: [RFC/PATCHES] xc3028 hybrid tuner, em28xx/em2880-dvb, saa7134, cx88

[Markus Rechberger]

On 5/17/07, Johannes Stezenbach <[EMAIL PROTECTED]> wrote:

Hi Markus,

On Thu, May 17, 2007, Markus Rechberger wrote:
> On 5/17/07, Michael Krufky <[EMAIL PROTECTED]> wrote:
> >
> >Don't get me wrong -- I am not suggesting that we duplicate this code
> >and leave it in that state forever.  What I am suggesting is that we go
> >about this change in small steps.
> >
> >The proposed changes are simply too large and span too many source files
> >to achieve a proper review by enough developers, especially in their
> >"spare time," not to mention all the regression testing that needs to be
> >done.
>
> In that case I'm willing to fork the linuxtv project if I did too much
> to review.
> I just spent too much time on it to throw it away without a serious
> discussion.
>
> The tuner refactoring code has around 600-700 lines of code I think,
> the rest are the additional drivers and other things.

After the recent flamewar there was the opportunity for you
to get the whole thing merged, if you had only pushed
it out in time. IMHO em28xx even could have made it into 2.6.22...

Life is full of compromises, some of them ugly.
Don't you think it would be better to scarifice those 700 lines
of code in order to get the thousands of lines of em28xx and xc3028
code merged _now_?

(And, BTW, you should not take this personal. The amount of
code written for the kernel, posted to lkml and then mercilessly
pulled to pieces, and finally thrown away is HUGE.)

While certainly not ideal, Mike's plan is at least a way
to make progress, even if there's a little detour involved.




I have some other work pending which relies on this too since I don't
want to get stuck I want to get forward asap.
The reason why I redid it back than was I tried to find a better
solution and in case of that I'm fine with that solution now since it
works flawlessly with the saa7134 and cx88 too.
The last discussion before this one was to get the patches ready for
merging with the upstream code, I exported it again and now again it's
having a hard time. I just one more time spent another full day with
doing and testing all that.

This is not acceptable for me anymore, and I'm very sure that this
time wasting mentality will go on with other projects too which join
the current linuxtv project.

I seriously discussed this way in private with some developers,
surprisingly some of them had nearly the same idea as I wrote already.
There are many ways devices can be built, there will never be one way
which will cover all board designs, Manu listed some possibilities,
maybe he should also have written what about devices which do not have
a tuner either and are directly fed with input data. My current work
is based on what is available now on the market.
All the tuners which are written as dvb tuner modules at the moment
are i2c tuners, using dvb_attach it's still possible to override the
structs with completly different callbacks.

I will not go back anymore, instead a fork off seems to be a good
solution if the linuxtv project wants to stay stuck where it is at the
moment it should do so.

I'm very sure almost noone even had a look at the code. Since around 1
1/2 years there hasn't been any solution, linuxtv can go for another
10 years I don't mind but then without em28xx(analogue/digital)
support which is very popular at the moment, and also lacking support
for the xc3028 hybrid devices.

Markus

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: [RFC/PATCHES] xc3028 hybrid tuner, em28xx/em2880-dvb, saa7134, cx88

[Johannes Stezenbach]

Hi Markus,

On Thu, May 17, 2007, Markus Rechberger wrote:
> On 5/17/07, Michael Krufky <[EMAIL PROTECTED]> wrote:
> >
> >Don't get me wrong -- I am not suggesting that we duplicate this code
> >and leave it in that state forever.  What I am suggesting is that we go
> >about this change in small steps.
> >
> >The proposed changes are simply too large and span too many source files
> >to achieve a proper review by enough developers, especially in their
> >"spare time," not to mention all the regression testing that needs to be
> >done.
> 
> In that case I'm willing to fork the linuxtv project if I did too much
> to review.
> I just spent too much time on it to throw it away without a serious 
> discussion.
> 
> The tuner refactoring code has around 600-700 lines of code I think,
> the rest are the additional drivers and other things.

After the recent flamewar there was the opportunity for you
to get the whole thing merged, if you had only pushed
it out in time. IMHO em28xx even could have made it into 2.6.22...

Life is full of compromises, some of them ugly.
Don't you think it would be better to scarifice those 700 lines
of code in order to get the thousands of lines of em28xx and xc3028
code merged _now_?

(And, BTW, you should not take this personal. The amount of
code written for the kernel, posted to lkml and then mercilessly
pulled to pieces, and finally thrown away is HUGE.)

While certainly not ideal, Mike's plan is at least a way
to make progress, even if there's a little detour involved.


Johannes

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] pctv MSI Digivox A/V II...sound doesn't work

[Markus Rechberger]

Hi,

what repository did you use?
Did you read through the em28xx wiki/discussions there?
You might also test v4lctl volume mute off, I'm not sure if it works.
The em28xx ML includes many more people who own such devices, some of
them might have some experience with that device.

Markus


On 5/17/07, Claudio Ghirlanda <[EMAIL PROTECTED]> wrote:

Hi everybody, this card is making me crazy...so following a few guide I
right install this USB2.0 MSI Digivox A/V II with v4l-dvb-kernel driver and
firmware2. I can see correctly cable tv but problem is that I can't hear
anything!

I also used the v4l-scripts-usbaudio_setup.sh to be sure that the input and
output audio device were correct: "mixer10 Empia Em28xx Au" as TV Audio
source (if I remove the card this choice disappear...so at least it is
recognizes!) and "Realtek ALC883 HDA-Intel" as output device.

Apparently no error...but steel no sound
I told myself maybe this is from the not correct setup of "mixer10 Empia
Em28xx Au" but I can't see how am I suppose to configure it!
Did someone use this card? How can I configure the input sound device?


I'm using Debian Etch kernel 2.6.18-4-686 on a acer aspire 5610
thank you
ciao




--
Markus Rechberger

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] pctv MSI Digivox A/V II...sound doesn't work

[Claudio Ghirlanda]

Hi everybody, this card is making me crazy...so following a few guide I
right install this USB2.0 MSI Digivox A/V II with v4l-dvb-kernel driver and
firmware2. I can see correctly cable tv but problem is that I can't hear
anything!

I also used the v4l-scripts-usbaudio_setup.sh to be sure that the input and
output audio device were correct: "mixer10 Empia Em28xx Au" as TV Audio
source (if I remove the card this choice disappear...so at least it is
recognizes!) and "Realtek ALC883 HDA-Intel" as output device.

Apparently no error...but steel no sound
I told myself maybe this is from the not correct setup of "mixer10 Empia
Em28xx Au" but I can't see how am I suppose to configure it!
Did someone use this card? How can I configure the input sound device?


I'm using Debian Etch kernel 2.6.18-4-686 on a acer aspire 5610
thank you
ciao
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] nova-t 500 progress?

[Markus Rechberger]

Hi,

can someone list what has been tried to avoid this disconnection behaviour?
I don't think that relying on hacks would be the right way, maybe
document what has been done to debug that issue on the wiki, so that
if someone wants to join debugging knows where he has to start.

I'd have a few ideas about debugging but I'm not sure if someone else
already tried it.
* it works in windows? if yes -> get a protocol dump with usbsnoop,
add some debug which makes it easily to compare what the linux driver
does and compare the difference. This is the easiest way if someone
wants to work on it and if the specs aren't available, although
windows should nearly use a similar approach.

Markus

On 5/17/07, Richard Morris <[EMAIL PROTECTED]> wrote:

>
>Hi,
>   It seems a great idea to me! Would you mind to share it? I'm quite a
noob in Linux and I'd be interested in having such a tool to perform
automatic >restarts of mythtv :D.

Eduard,

I use 2 of the Nova-T 500's with MythTV, I get about 4 disconnects a day
that either fill up the event log with messages like:

May 17 10:01:00 athlon mt2060 I2C read failed

and/or crash MythTV.

I run the following as a cron job every minute to restart MythTV which also
causes the card to reconnect again; presumably when MythTV is restarted it
closes whatever streams it was trying to read from the device.

if tail /var/log/messages | grep  -E '^[A-Z][a-z]{2}[ ]{1,2}[0-9]{1,2}[
][0-9]{2}:[0-9]{2}:[0-9]{2}[ ][a-z]+[ ]mt2060 I2C read failed'  ; then
/etc/init.d/mythbackend restart ; fi ; if ! ps -A | grep mythbackend >>
/dev/null ; then /etc/init.d/mythbackend restart ; fi

Regards

Richard Morris



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb




--
Markus Rechberger

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

RE: [linux-dvb] nova-t 500 progress?

[Richard Morris]

>
>Hi, 
>   It seems a great idea to me! Would you mind to share it? I'm quite a
noob in Linux and I'd be interested in having such a tool to perform
automatic >restarts of mythtv :D.

Eduard,

I use 2 of the Nova-T 500's with MythTV, I get about 4 disconnects a day
that either fill up the event log with messages like:

May 17 10:01:00 athlon mt2060 I2C read failed

and/or crash MythTV.

I run the following as a cron job every minute to restart MythTV which also
causes the card to reconnect again; presumably when MythTV is restarted it
closes whatever streams it was trying to read from the device.

if tail /var/log/messages | grep  -E '^[A-Z][a-z]{2}[ ]{1,2}[0-9]{1,2}[
][0-9]{2}:[0-9]{2}:[0-9]{2}[ ][a-z]+[ ]mt2060 I2C read failed'  ; then
/etc/init.d/mythbackend restart ; fi ; if ! ps -A | grep mythbackend >>
/dev/null ; then /etc/init.d/mythbackend restart ; fi

Regards

Richard Morris



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: [RFC/PATCHES] xc3028 hybrid tuner, em28xx/em2880-dvb, saa7134, cx88

[Markus Rechberger]

On 5/17/07, Michael Krufky <[EMAIL PROTECTED]> wrote:

Mauro Carvalho Chehab wrote:
>
>> I do frown upon code duplication, however, in this case it is a safer
>> alternative to the one currently on the table.  Earlier versions of
>> the xc3028 tuner driver were bound to the video4linux tuner.ko
>> module, for the sake of tuning analog television stations.  There was
>> a wrapper present inside the em2880-dvb driver that allowed the dvb
>> subsystem to access the xc3028 via tuner.ko.  I am not a big fan of
>> this solution, however, it does not touch any core subsystem code.
>> DVB-only devices can use a separate module in order to access the
>> xc3028 without imposing dependencies on the v4l core.
>
> Duplicating a driver is not a solution, just a terrible hack. We
> should focus on a way to use the same tuner driver for both Analog and
> Digital TV.
>
Mauro,

Don't get me wrong -- I am not suggesting that we duplicate this code
and leave it in that state forever.  What I am suggesting is that we go
about this change in small steps.

The proposed changes are simply too large and span too many source files
to achieve a proper review by enough developers, especially in their
"spare time," not to mention all the regression testing that needs to be
done.



In that case I'm willing to fork the linuxtv project if I did too much
to review.
I just spent too much time on it to throw it away without a serious discussion.

The tuner refactoring code has around 600-700 lines of code I think,
the rest are the additional drivers and other things.



As much as we try to come to an agreement about this right now, I fear
that it will be very difficult -- this debate has gone on for over a
year and reaching an agreement will not be easy.

I think that the only way to move forward while keeping everybody happy
would be to proceed in the following order:

1) merge xc3028 support into tuner.ko for analog support*

2) break apart tuner.ko into modularized sub-modules*

3) add xc3028-fe.ko module for dvb-only support**

4) merge in updates to the em28xx driver***

5) add xc3028 support to other card drivers***

6) restart discussions about hybrid / tuner inter-subsystem API

7) apply changes agreed upon in step 6, to migrate the tuner modules to
the new tuner internal api, while removing the duplicated xc3028 module.


*(1) and (2) may be reversed

** http://linuxtv.org/~mkrufky/xc-bluebird.patch

*** analog functionality should use tuner.ko only
*** digital functionality should use xc3028-fe.ko only

---

Please take note, that if we proceed in the order above, this will allow
us to merge the majority of Markus' changes, leaving only the api
changes behind.  At this point, the remainder of the changesets will be
MUCH smaller, and much easier to review.

Under the conditions that we'll be under after step 5, it will be much
more conducive to a productive developer discussion on the issue.

At this point, there has been so much noise about this topic, that I
feel confident that many developers will be able to participate in this
review.  I, for one, would love to have this taken care of, and put this
issue behind us.

After step 5, with the majority of the changesets already being merged,
the pressure on the author and reviewers will be lessened, and
discussions should be able to take place with clear heads.

What I am asking for here is very sensible --  This should not be
difficult for everybody to agree to.  It allows us to merge in changes
one step at a time, while adding support for all devices gradually.
Through this means, we will ultimately achieve the goal of being able to
discuss the actual requirements and reasons for why Markus is making
this proposal to change the tuner api.

I repeat:  huge changes will never blow over well.  The only way to do
this in small steps is to do it in such a way that I've described in
this email.

If you simply shoot me down for the idea of temporarily having a
separate dvb module for the dvb subsystem to interface with the xc3028
tuner,  then you are not seeing the big picture.

Regards,

Mike Krufky






--
Markus Rechberger

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Re: [RFC/PATCHES] xc3028 hybrid tuner, em28xx/em2880-dvb, saa7134, cx88

[Markus Rechberger]

On 5/16/07, Manu Abraham <[EMAIL PROTECTED]> wrote:

hermann pitton wrote:
> Manu,
> 


I am writing this reply with quite a lot of reluctance/hesitation, since
some people create unnecessary noise alone: people being stubborn,
practically creating a waste of time for others.

Removing all those CC's since they are already addressed on the ML's.
Sometimes it is better to keep quiet, seeing all those *noise*. The main
issue: half knowledge is too dangerous!

> what do you think already could have a GO?
> 
> Markus can't invade like that, but must have a next safe harbour to

> continue to work on it.
> 
> The hybrid stuff will invade the planet for long, and then ... die.


Convergence of media is not a new thing. Now it is Analog stuff added
in, the reason for a vendor: it does not make much of a difference in
terms of cost to make a chip like that, but with regards to marketing it
makes a huge difference. Later on, we will be seeing the convergence of
other media as well.

> Do you think to share tuners between digital and analog is really
> impossible, or just wait until these zilliards are gone?

I don't think it is impossible, just that it needs sufficient efforts to
do so. Now there are 2 types of designs, the analog interface is thrown
in additionally into each of them.

1) using a Single chip, bus interface + demodulator + tuner
2) using Two chips, chip1 = bus interface, chip2 = demodulator + tuner
3) using 3 chips, chip1 = bus interface, chip2 = demodulator, chip3 = tuner



I am aware of this constellation, but again I'm refering to the code now.
The dvb subsystem already uses a way to modularize some tuners.
The approach which is implemented in the em28xx/hybrid repository interfaces 
this design and all it does is to abstract the function arguments and adds 
support for it to the analogue framework.

As for the DVB side there is no redesign involved at all with that method, so 
everything else would still work the same way as it worked before.

I'll explain it more detailed:

The dvb framework already uses a broken out tuner approach. The structs look 
like following:

struct dvb_tuner_ops {

   struct dvb_tuner_info info;

   int (*release)(struct dvb_frontend *fe);
   int (*init)(struct dvb_frontend *fe);
   int (*sleep)(struct dvb_frontend *fe);

   /** This is for simple PLLs - set all parameters in one go. */
   int (*set_params)(struct dvb_frontend *fe, struct 
dvb_frontend_parameters *p);

   /** This is support for demods like the mt352 - fills out the supplied 
buffer with what to write. */
   int (*calc_regs)(struct dvb_frontend *fe, struct dvb_frontend_parameters 
*p, u8 *buf, int buf_len);

   int (*get_frequency)(struct dvb_frontend *fe, u32 *frequency);
   int (*get_bandwidth)(struct dvb_frontend *fe, u32 *bandwidth);

#define TUNER_STATUS_LOCKED 1
   int (*get_status)(struct dvb_frontend *fe, u32 *status);

   /** These are provided seperately from set_params in order to facilitate 
silicon
* tuners which require sophisticated tuning loops, controlling each 
parameter seperately. */
   int (*set_frequency)(struct dvb_frontend *fe, u32 frequency);
   int (*set_bandwidth)(struct dvb_frontend *fe, u32 bandwidth);
};

The updates struct looks like:
struct v4l_dvb_tuner_ops {

   void *priv; /* some privat data for internal use */
   void *dev; /* v4l private data for tuner-core */
   struct dvb_frontend *fe; /* dvb_frontend, for dvb only drivers, internal 
use */

   struct dvb_tuner_info info;

   int (*ioctl)(struct v4l_dvb_tuner_ops *dev, int cmd, int arg);

   int (*release)(struct v4l_dvb_tuner_ops *fe);
   int (*init)(struct v4l_dvb_tuner_ops *fe);
   int (*sleep)(struct v4l_dvb_tuner_ops *fe);

   /** This is for simple PLLs - set all parameters in one go. */
   int (*set_params)(struct v4l_dvb_tuner_ops *fe, struct 
dvb_int_frontend_parameters *p);

   /** This is support for demods like the mt352 - fills out the supplied 
buffer with what to write. */
   int (*calc_regs)(struct v4l_dvb_tuner_ops *fe, struct 
dvb_int_frontend_parameters *p, u8 *buf, int buf_len);

   int (*get_frequency)(struct v4l_dvb_tuner_ops *fe, u32 *frequency);
   int (*get_bandwidth)(struct v4l_dvb_tuner_ops *fe, u32 *bandwidth);

#define TUNER_STATUS_LOCKED 1
   int (*get_status)(struct v4l_dvb_tuner_ops *fe, u32 *status);

   /** These are provided seperately from set_params in order to facilitate 
silicon
* tuners which require sophisticated tuning loops, controlling each 
parameter seperately. */
   int (*set_frequency)(struct v4l_dvb_tuner_ops *fe, u32 frequency);
   int (*set_bandwidth)(struct v4l_dvb_tuner_ops *fe, u32 bandwidth);

   int (*set_mode)(struct v4l_dvb_tuner_ops *dev, struct 
dvb_int_frontend_parameters *params);
};

So the parameters change to not directly having a dependency to dvb_frontend, 
this is the only change at the dvb framew

Re: [linux-dvb] HVR3000 DVB-T problems

[Simon Santoro]

Simon Santoro wrote:
[CUT no DVB-T channels found]

I tried the analog scan with tvtime as well, and tvtime does not find
any analog channels too... Uhm, is there anything special I have to do
to get this card working? (I swear, the antenna cable is connected and
working! :))
I also removed the symlinks just in case, and tried everything again.
While kaffeine scanns, the green Lock circle flashes, but no channels
appear.
dmesg, lspci - and kaffeine stdout are attached.

$ tree /dev/dvb/
/dev/dvb/
|-- adapter0#<- Nova DVB-S
|   |-- demux0
|   |-- dvr0
|   |-- frontend0
|   `-- net0
`-- adapter1#<- HVR-3000 DVB-T
|-- demux0
|-- dvr0
|-- frontend0
`-- net0

2 directories, 8 files



0
/dev/dvb/adapter0/frontend0 : opened ( Conexant CX24123/CX24109 )
/dev/dvb/adapter0/frontend1 : : No such file or directory
/dev/dvb/adapter1/frontend0 : opened ( Conexant CX22702 DVB-T )
/dev/dvb/adapter1/frontend1 : : No such file or directory
/dev/dvb/adapter2/frontend0 : : No such file or directory
QLayout "unnamed" added to QWidget "unnamed", which already has a layout
DvbCam::probe(): /dev/dvb/adapter1/ca0: : No such file or directory
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 40200 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 41000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 41800 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 42600 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 43400 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 44200 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 45000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 45800 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 46600 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 47400 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 48200 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 49000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 49800 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 50600 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 51400 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 15/63

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 52200 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 1:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 53000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi

Re: [linux-dvb] New channel info file: es-Sevilla

[Mick]

Oops - I didn't realise. dvb-apps rpm that I'm using must be older than I 
thought. Thanks for your help.

Mick

On Wednesday 16 May 2007 20:30, you wrote:
> Hi,
>
> Am Freitag, 11. Mai 2007 18:29 schrieb Mick:
> > Hi
> >
> > Could someone add this new channel info file to the dvb-apps repository?
> >
> > thanks
> > Mick
> >
> > es-Sevilla
> >
> > # DVB-T Sevilla (Andalucia)
> > # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
> > T 76200 8MHz 2/3 NONE QAM64 8k 1/4 NONE # Mux 57 RTVE
> > T 79400 8MHz 2/3 NONE QAM64 8k 1/4 NONE # Mux 61 Canal Sur
> > T 83400 8MHz 2/3 NONE QAM64 8k 1/4 NONE # Mux 66 VEO
> > T 84200 8Mhz 2/3 NONE QAM64 8k 1/4 NONE # Mux 67 Cuatro, laSexta
> > T 85000 8Mhz 2/3 NONE QAM64 8k 1/4 NONE # Mux 68 Telecinco
> > T 85800 8Mhz 2/3 NONE QAM64 8k 1/4 NONE # Mux 69 Antena 3
>
> An identical file is already there for some time [1].
>
> Christoph
>
>
> [1]
> http://linuxtv.org/hg/dvb-apps?f=d34fb391bce8;file=util/scan/dvb-t/es-Sevil
>la;style=gitweb

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] HVR3000 DVB-T problems

[Simon Santoro]

Hello all!
When I scan for DVB-T channels with kaffeine I get a lot of

cx88[1]/2-mpeg: cx8802_timeout
cx88[1]/2-mpeg: cx8802_timeout
cx88[1]/2-mpeg: cx8802_timeout

messages in dmesg, and no channels found, even if the kaffeine autoscan
gets a lot of "lock"s.
I have two Hauppauge cards:

CORE cx88[0]: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus DVB-S
[card=37]

and

CORE cx88[1]: subsystem: 0070:1402, board: Hauppauge WinTV-HVR3000
TriMode Analog/DVB-S/DVB-T [card=53]

The Nova-S-Plus works with DVB-S, and I wanted to use the HVR3000 for
DVB-T and Analog reception, as that is supported in the stock kernel (i
am using the default ubuntu feisty 2.6.20 kernel).
The cable and antenna work fine, as they have no problems connected
directly with the TV (DVB-T tuner build in), and the card worked with
kernel 2.6.17 and Stevens hvr3000 tree in another box and connected to
the same antenna cable.
The dvb-utils scan utility is unable to find channels as well.
I am out of ideas.

Attached
dmesg|grep -i dvb
and the kaffeine stdout (/dev/dvb/adapter4/ is a symlink to
/dev/dvb/adapter1/  (that's just to have some flexibility with myth when
swapping cards)).

Any help is of course appreciated, thanks.
[   13.82] CORE cx88[0]: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus 
DVB-S [card=37,autodetected]
[   13.972000] tveeprom 0-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
[   13.972000] CORE cx88[1]: subsystem: 0070:1402, board: Hauppauge 
WinTV-HVR3000 TriMode Analog/DVB-S/DVB-T [card=53,autodetected]
[   14.324000] tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') 
PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xf4)
[   15.104000] cx2388x dvb driver version 0.0.6 loaded
[   15.104000] cx8802_register_driver() ->registering driver type=dvb 
access=shared
[   15.104000] CORE cx88[0]: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus 
DVB-S [card=37]
[   15.104000] cx88[0]/2: cx2388x based dvb card
[   15.156000] DVB: registering new adapter (cx88[0]).
[   15.156000] DVB: registering frontend 0 (Conexant CX24123/CX24109)...
[   15.156000] CORE cx88[1]: subsystem: 0070:1402, board: Hauppauge 
WinTV-HVR3000 TriMode Analog/DVB-S/DVB-T [card=53]
[   15.156000] cx88[1]/2: cx2388x based dvb card
[   15.196000] DVB: registering new adapter (cx88[1]).
[   15.196000] DVB: registering frontend 1 (Conexant CX22702 DVB-T)...
[   16.192000] /home/mythtv/source/sasc-ng/dvbloopback/module/dvb_loopback.c: 
frontend loopback driver v0.0.1
[   16.192000] dvbloopback: registering 1 adapters
[   16.192000] DVB: registering new adapter (DVB-LOOPBACK).
[EMAIL PROTECTED]:~$ kaffeine
0
/dev/dvb/adapter0/frontend0 : : Device or resource busy
/dev/dvb/adapter0/frontend1 : : No such file or directory
/dev/dvb/adapter1/frontend0 : opened ( Conexant CX22702 DVB-T )
/dev/dvb/adapter1/frontend1 : : No such file or directory
/dev/dvb/adapter2/frontend0 : : Operation not permitted
/dev/dvb/adapter2/frontend1 : : Device or resource busy
/dev/dvb/adapter2/frontend2 : : No such file or directory
/dev/dvb/adapter3/frontend0 : : Operation not permitted
/dev/dvb/adapter3/frontend1 : : Device or resource busy
/dev/dvb/adapter3/frontend2 : : No such file or directory
/dev/dvb/adapter4/frontend0 : opened ( Conexant CX22702 DVB-T )
/dev/dvb/adapter4/frontend1 : : No such file or directory
/dev/dvb/adapter5/frontend0 : : No such file or directory
QLayout "unnamed" added to QWidget "unnamed", which already has a layout
[EMAIL PROTECTED]:~$ DvbCam::probe(): /dev/dvb/adapter4/ca0: : No such file or 
directory
Using DVB device 4:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 40200 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 4:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 41000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 4:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 41800 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 4:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 42600 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 4:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 43400 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 4:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 44200 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
...
Not able to lock to the signal on the given frequency
Frontend closed
dvbsi: Cant tune DVB
Using DVB device 4:0 "Conexant CX22702 DVB-T"
tuning DVB-T to 45000 Hz
inv:2 bw:0 fe