[linux-dvb] TT DVB C1500 + QAM_256

2008-01-22 Thread lists
Hi, All.

Can anybody share of success story using TT DVB C1500 + QAM 256,
please, response personally or in list.

If anybody could recommend DVB card for working with QAM 256 signal
under linux I'll appreciate that.

And Thank you, dev@ team, for working on this great project.

-- 
 Anton P. Linevich

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


Re: [linux-dvb] Getting full mux of TS data from DVB adaptor.

2007-12-28 Thread lists
Greeting, David!  Fri, Dec 28, 2007 at 10:22:03PM +0800, davidtlwong wrote: 

> Hi all,
>  Sorry for a stupid question. How can I get full mux of TS data from DVB
> adapter device?

try to use dvbsnoop and -tsraw parameter
It works for me as well.

-- 
 Anton P. Linevich

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


[linux-dvb] Some problems with TT S-1500 and PayTV channels

2007-12-28 Thread lists
> > Pardon me for interrupting, but is CI module for S-1500 working for you?
> > I mean did you tryed grab crypted channel?
> 
> Yes, I use since two years and a half. I use a Matrix Reloaded, Ncas 
> programmed, with my Sky Italy Nds Subscription card. I use mythtv,

>From my side viaccess CAM working stable with S-1500, but some of
channels (which availiable from DreamBox for example) didn't showing.

I use gnutv. Will apreciate any recomendations.
Here is my output:
$ gnutv -channels channels.conf -adapter 2 -out dvr "Cartoon Network/TCM"
Using frontend "ST STV0299 DVB-S", type DVB-S
CAM Application type: 01cb | snr 710d | ber  | unc  |
CAM Application manufacturer: 0500
CAM Manufacturer code: 0500
CAM Menu string: Viaccess
CAM supports the following ca system ids:er  | unc  |

And one more with error messages:
$ gnutv -channels channels.conf -adapter 2 -out dvr "Cartoon Network/TCM"
Using frontend "ST STV0299 DVB-S", type DVB-S
en50221_tl_handle_sb: Received T_SB for connection not in T_STATE_ACTIVE
from module on slot 00

en50221_stdcam_llci_poll: Error reported by stack:-7

CAM Application type: 01cb | snr 7107 | ber  | unc  |
CAM Application manufacturer: 0500
CAM Manufacturer code: 0500
CAM Menu string: Viaccess
CAM supports the following ca system ids:er  | unc  |
  0x0500
  status SC| signal 593e | snr 70fb | ber  | unc  |




-- 
 Anton P. Linevich

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


Re: [linux-dvb] Some problems with TT S2-3200

2007-12-26 Thread lists
Greeting, Marco!  Wed, Dec 26, 2007 at 11:21:09PM +0100, marco.coli wrote: 

> Yes, I imagine this. So I did a make rrmod and after I loaded modules by 
> hand in the order you suggested. But no luck... In the log I see only 
> messages related to the S-1500

Pardon me for interrupting, but is CI module for S-1500 working for you?
I mean did you tryed grab crypted channel?

-- 
 Anton P. Linevich

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


[linux-dvb] v4l2apps and result

2007-06-20 Thread wouter lists
Hi all,

I was looking around in the v4l2apps directory and played a little bit
with the tools.

I ran driver-test and saw an error:
QUERYBUF: ERROR: VIDIOC_S_FMT said buffer should have 460800 size, but
received 462848 from QUERYBUF!

Can somebody explain please what this means and if it needs to be fixed?

Regards,

Wouter

./driver-test
driver=saa7134, card=AVerMedia A169 B, bus=PCI::06:00.0,
version=0.2.14, capabilities=CAPTURE OVERLAY VBI_
CAPTURE TUNER READWRITE STREAMING
STANDARD: index=0, id=0x00ff, name=PAL, fps=25.000, framelines=625
STANDARD: index=1, id=0x0007, name=PAL-BG, fps=25.000, framelines=625
STANDARD: index=2, id=0x0010, name=PAL-I, fps=25.000, framelines=625
STANDARD: index=3, id=0x00e0, name=PAL-DK, fps=25.000, framelines=625
STANDARD: index=4, id=0xb000, name=NTSC, fps=29.970, framelines=525
STANDARD: index=5, id=0x00ff, name=SECAM, fps=25.000, framelines=625
STANDARD: index=6, id=0x0032, name=SECAM-DK, fps=25.000, framelines=625
STANDARD: index=7, id=0x0040, name=SECAM-L, fps=25.000, framelines=625
STANDARD: index=8, id=0x0080, name=SECAM-Lc, fps=25.000, framelines=625
STANDARD: index=9, id=0x0100, name=PAL-M, fps=29.970, framelines=525
STANDARD: index=10, id=0x0400, name=PAL-Nc, fps=25.000, framelines=625
STANDARD: index=11, id=0x0800, name=PAL-60, fps=29.970, framelines=525
INPUT: index=0, name=Television, type=1, audioset=1, tuner=0,
std=00ffbdff, status=65792
INPUT: index=1, name=Composite1, type=2, audioset=1, tuner=0,
std=00ffbdff, status=0
INPUT: index=2, name=Composite2, type=2, audioset=1, tuner=0,
std=00ffbdff, status=0
INPUT: index=3, name=Svideo1, type=2, audioset=1, tuner=0,
std=00ffbdff, status=0
INPUT: index=4, name=Svideo2, type=2, audioset=1, tuner=0,
std=00ffbdff, status=0
FORMAT: index=0, type=1, flags=0, description='8 bpp gray'
fourcc=GREY
FORMAT: index=1, type=1, flags=0, description='15 bpp RGB, le'
fourcc=RGBO
FORMAT: index=2, type=1, flags=0, description='15 bpp RGB, be'
fourcc=RGBQ
FORMAT: index=3, type=1, flags=0, description='16 bpp RGB, le'
fourcc=RGBP
FORMAT: index=4, type=1, flags=0, description='16 bpp RGB, be'
fourcc=RGBR
FORMAT: index=5, type=1, flags=0, description='24 bpp RGB, le'
fourcc=BGR3
FORMAT: index=6, type=1, flags=0, description='24 bpp RGB, be'
fourcc=RGB3
FORMAT: index=7, type=1, flags=0, description='32 bpp RGB, le'
fourcc=BGR4
FORMAT: index=8, type=1, flags=0, description='32 bpp RGB, be'
fourcc=RGB4
FORMAT: index=9, type=1, flags=0, description='4:2:2 packed, YUYV'
fourcc=YUYV
FORMAT: index=10, type=1, flags=0, description='4:2:2 packed, UYVY'
fourcc=UYVY
FORMAT: index=11, type=1, flags=0, description='4:2:2 planar, Y-Cb-Cr'
fourcc=422P
FORMAT: index=12, type=1, flags=0, description='4:2:0 planar, Y-Cb-Cr'
fourcc=YU12
FORMAT: index=13, type=1, flags=0, description='4:2:0 planar, Y-Cb-Cr'
fourcc=YV12
FMT SET: 640x480, fourcc=GREY, 640 bytes/line, 307200 bytes/frame,
colorspace=0x
FMT SET: 640x480, fourcc=RGBO, 1280 bytes/line, 614400 bytes/frame,
colorspace=0x
FMT SET: 640x480, fourcc=RGBQ, 1280 bytes/line, 614400 bytes/frame,
colorspace=0x
FMT SET: 640x480, fourcc=RGBP, 1280 bytes/line, 614400 bytes/frame,
colorspace=0x
FMT SET: 640x480, fourcc=RGBR, 1280 bytes/line, 614400 bytes/frame,
colorspace=0x
FMT SET: 640x480, fourcc=BGR3, 1920 bytes/line, 921600 bytes/frame,
colorspace=0x
FMT SET: 640x480, fourcc=RGB3, 1920 bytes/line, 921600 bytes/frame,
colorspace=0x
FMT SET: 640x480, fourcc=BGR4, 2560 bytes/line, 1228800 bytes/frame,
colorspace=0x
FMT SET: 640x480, fourcc=RGB4, 2560 bytes/line, 1228800 bytes/frame,
colorspace=0x
FMT SET: 640x480, fourcc=YUYV, 1280 bytes/line, 614400 bytes/frame,
colorspace=0x
FMT SET: 640x480, fourcc=UYVY, 1280 bytes/line, 614400 bytes/frame,
colorspace=0x
FMT SET: 640x480, fourcc=422P, 1280 bytes/line, 614400 bytes/frame,
colorspace=0x
FMT SET: 640x480, fourcc=YU12, 960 bytes/line, 460800 bytes/frame,
colorspace=0x
FMT SET: 640x480, fourcc=YV12, 960 bytes/line, 460800 bytes/frame,
colorspace=0x
PARM: capability=0, capturemode=0, nan fps ext=0, readbuf=0
62.5 kHz step
board is at freq 121.250 MHz (1940)
62.5 kHz step
board set to freq 0.000 MHz (0)
62.5 kHz step
board set to freq 121.250 MHz (1940)
Preparing for frames...
REQBUFS: count=2, type=video-cap, memory=mmap
QUERYBUF: 00:00:00. index=0, type=video-cap, bytesused=0,
flags=0x, field=any, sequence=0, mem
ory=mmap, offset=0x, length=462848
TIMECODE: 00:00:00 type=0, flags=0x, frames=0,
userbits=0x
QUERYBUF: ERROR: VIDIOC_S_FMT said buffer should have 460800 size, but
received 462848 from QUERYBUF!
QUERYBUF: 00:00:00. index=1, type=video-cap, bytesused=0,
flags=0x, field=any, sequence=0, mem
ory=mmap, offset=0x000710

[linux-dvb] Patch Avermedia A169

2006-11-13 Thread wouter lists

Hi all,

Please find attached 2 patches, which enable the dual tuner
functionality of the Avermedia A169.

Before I forget: all credits for these patches go to Rickard Osser.

I'm running these patches without problems for more then 4 months.
Although you have to keep 2 things in mind when running these patches.
I think that's why Rickard hasn't yet sent these patches to the
mailing-list, but I don't want his work to get lost.

First: you have to unload and load the tuner module to get both cards working:
modprobe -r tuner ; modprobe tuner

dmesg before modprobe:
saa7134[0]: i2c scan: found device @ 0x86  [tda9887]
saa7134[0]: i2c scan: found device @ 0xa0  [eeprom]
saa7134[0]: i2c scan: found device @ 0xc0  [tuner (analog)]
saa7134[0]: i2c scan: found device @ 0xc2  [???]
tuner 1-0060: All bytes are equal. It is not a TEA5767
tuner 1-0060: chip found @ 0xc0 (saa7134[0])
tuner 1-0060: type set to 66 (LG TALN series)
tuner 1-0061: chip found @ 0xc2 (saa7134[0])
saa7134[1]: i2c scan: found device @ 0xa0  [eeprom]
saa7134[1]: i2c scan: found device @ 0xc0  [tuner (analog)]
tuner 2-0060: TEA5767 detected.
tuner 2-0060: chip found @ 0xc0 (saa7134[1])
tuner 2-0060: type set to 62 (Philips TEA5767HN FM Radio)

dmesg after modprobe:
tuner 1-0043: chip found @ 0x86 (saa7134[0])
tda9887 1-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 1-0060: All bytes are equal. It is not a TEA5767
tuner 1-0060: chip found @ 0xc0 (saa7134[0])
tuner 1-0060: type set to 66 (LG TALN series)
tuner 1-0061: chip found @ 0xc2 (saa7134[0])
tuner 2-0043: chip found @ 0x86 (saa7134[1])
tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 2-0060: Returned more than 5 bytes. It is not a TEA5767
tuner 2-0060: chip found @ 0xc0 (saa7134[1])
tuner 2-0060: type set to 66 (LG TALN series)
tuner 2-0061: chip found @ 0xc2 (saa7134[1])

It has something to do with the i2c-scan; but I haven't found what.


Second: I have to run my system with the irqpoll option

I have no idea what is causing this error. If I run my system with the
irqpoll option, everything works great.

tuner 2-0061: chip found @ 0xc2 (saa7134[1])
irq 74: nobody cared (try booting with the "irqpoll" option)

Call Trace:
 [] __report_bad_irq+0x30/0x7d
[] note_interrupt+0x1ed/0x22e
[] __do_IRQ+0xc7/0x105
[] __do_softirq+0x5e/0xd5
[] do_IRQ+0x65/0x73
[] mwait_idle+0x0/0x4a
[] ret_from_intr+0x0/0xa
 [] mwait_idle+0x36/0x4a
[] cpu_idle+0x95/0xb8
[] start_kernel+0x216/0x21b
[] _sinittext+0x288/0x28c

handlers:
[] (saa7134_irq+0x0/0x284 [saa7134])
[] (saa7134_alsa_irq+0x0/0x2b0 [saa7134_alsa])
Disabling IRQ #74
# cat /proc/interrupts
  CPU0   CPU1
 0:  41586  0IO-APIC-edge  timer
 8:  0  0IO-APIC-edge  rtc
 9:  0  0   IO-APIC-level  acpi
14: 38  0IO-APIC-edge  ide0
58:143  0   IO-APIC-level  uhci_hcd:usb1, ehci_hcd:usb5
66:605  0   IO-APIC-level  eth0
74: 10  0   IO-APIC-level  saa7134[0], saa7134[0]
169:   7178  0   IO-APIC-level  uhci_hcd:usb4, HDA Intel,
[EMAIL PROTECTED]::01:00.0
177:261  0   IO-APIC-level  ohci1394
185:  0  0   IO-APIC-level  uhci_hcd:usb3, saa7134[1],
saa7134[1]
193:   4583  0   IO-APIC-level  libata, uhci_hcd:usb2
NMI: 64 43
LOC:  41544  41522
ERR:  0
MIS:  0


Now it's up to you guys to decide whether to include these patches or
not. I hope they get included.

Thanks,

Wouter
# HG changeset patch
# User [EMAIL PROTECTED]
# Node ID d506f555aa5926c804eb9ceb814e2ab19ffe869f
# Parent  0bcf77433dc08f0e4ffcc6af8bd0e23f16d6ecc5

AVerMedia A169 cleanup patch
Corrected subdevice ID

From: Rickard Osser <[EMAIL PROTECTED]>


Cleanup of AVerMedia A169 B and B1 settings. All ports enabled based on future changes in the TEA5767 detection code.
Corrected subdevice ID to correctly correspond with information from AVerMedia.


Signed-off-by: Rickard Osser <[EMAIL PROTECTED]>

diff -r 0bcf77433dc0 -r d506f555aa59 linux/Documentation/video4linux/CARDLIST.saa7134
--- a/linux/Documentation/video4linux/CARDLIST.saa7134	Thu Jun 29 21:30:51 2006 +0200
+++ b/linux/Documentation/video4linux/CARDLIST.saa7134	Fri Jun 30 00:36:16 2006 +0200
@@ -89,8 +89,8 @@
  88 -> Tevion/KWorld DVB-T 220RF[17de:7201]
  89 -> ELSA EX-VISION 700TV [1048:226c]
  90 -> Kworld ATSC110   [17de:7350]
- 91 -> AVerMedia A169 B [1461:7360]
- 92 -> AVerMedia A169 B1[1461:6360]
+ 91 -> AVerMedia A169 B [1461:6360]
+ 92 -> AVerMedia A169 B1[1461:7360]
  93 -> Medion 7134 Bridge #2[16be:0005]
  94 -> LifeView FlyDVB-T Hybrid Cardbus [5168:3306,5168:3502]
  95 -> LifeView FlyVIDEO3000 (NTSC) [5169:0138]
diff -r 0bcf77433dc0 -r d506f555aa59 linux/drivers/media/video/saa7134/saa7134-cards.c
--- a/lin

[linux-dvb] problems with alsa and compiling

2006-09-08 Thread wouter lists

All,

In order to get my capturecard and soundcard working, I need the
latest version of alsa together with the linux-dvb repository.

I installed the latest alsa-drivers (1.0.12) from source. Afterwards I
compiled the linux-dvb stuff.

My capturecard is saa7134-based. When I try to load the module
saa7134-alsa, I get the following errors;
saa7134_alsa: disagrees about version of symbol snd_ctl_add
saa7134_alsa: Unknown symbol snd_ctl_add
saa7134_alsa: disagrees about version of symbol snd_pcm_new
saa7134_alsa: Unknown symbol snd_pcm_new
saa7134_alsa: disagrees about version of symbol snd_card_register
saa7134_alsa: Unknown symbol snd_card_register
saa7134_alsa: disagrees about version of symbol snd_card_free
saa7134_alsa: Unknown symbol snd_card_free
saa7134_alsa: disagrees about version of symbol snd_pcm_stop
saa7134_alsa: Unknown symbol snd_pcm_stop
saa7134_alsa: disagrees about version of symbol snd_ctl_new1
saa7134_alsa: Unknown symbol snd_ctl_new1
saa7134_alsa: disagrees about version of symbol snd_card_new
saa7134_alsa: Unknown symbol snd_card_new
saa7134_alsa: disagrees about version of symbol snd_pcm_lib_ioctl
saa7134_alsa: Unknown symbol snd_pcm_lib_ioctl
saa7134_alsa: disagrees about version of symbol snd_pcm_set_ops
saa7134_alsa: Unknown symbol snd_pcm_set_ops
saa7134_alsa: disagrees about version of symbol snd_pcm_hw_constraint_integer
saa7134_alsa: Unknown symbol snd_pcm_hw_constraint_integer
saa7134_alsa: disagrees about version of symbol snd_pcm_period_elapsed
saa7134_alsa: Unknown symbol snd_pcm_period_elapsed

If I don't update alsa, I don't get these errors.

I'm missing something, but I have no idea what.

Regards,

Wouter

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


[linux-dvb] read mac address from dvb card

2004-07-16 Thread julian somers (lists only)
Does anyone have a reliable way to read the mac address from the dvb card 
(hauppauge wintv nova-s)? I want to use it in a script. I thought I would be 
able to find it in /proc, but have only found it in /var/log/messages, where 
it is written by insmod. 

TIA, Julian





[linux-dvb] output of szap

2004-06-22 Thread julian somers (lists only)
Hi

I am trying to make szap write its output to a file like this

szap channel 2>&1 >> out &

But get an erratic output -- it writes many lines at once, instead of one at a 
time. I want to use this output to drive a signal strength meter on a php 
page, so I need it to be regular. 

Im using gentoo kernel 2.4.26, linuxtv 1.1.1, szap and dvbnet on this proxy 
and masq server.

Any suggestions woudl be most welcome,

Thanks, 
Julian