[linux-dvb] Pinnacle Dual DVB-T diversity
Hi A patch for the Pinnacle Dual DVB-T diversity USB device can be found at www.chez.com/treza/mt2266.htm The main addition is a Microtune MT2266 driver. It is still a preliminary fixture, please be indulgent. Olivier (sorry for the bogus Tr: Pinnacle mobility mail) - ALICE SECURITE ENFANTS - Protégez vos enfants des dangers d'Internet en installant Sécurité Enfants, le contrôle parental d'Alice. http://www.aliceadsl.fr/securitepc/default_copa.asp ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] stb0899 troubles
On 2/23/07, Bernhard Rosenkraenzer [EMAIL PROTECTED] wrote: Hi, I've just tried using an STB0899 (KNC1 DVB-S2 card) with current hg + stb0899 patches. The card is recognized correctly, but doesn't tune to any channel - any ideas? If it matters, the app I'm using to tune uses the old (as in current v4l-dvb) API, and works perfectly on a KNC1 DVB-S1 card even with the stb0899 (and therefore multiproto) patches applied. You need to use the modified version of szap (temporarily) ..http://kromtek.com/dvb/szap.c Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-C+, CineView v. 3.0 and Conax CAM: PC card did not respond
Op donderdag 22-02-2007 om 23:28 uur [tijdzone +0200], schreef [EMAIL PROTECTED]: Inserting the Conax CAM with the Conax card gives these messages: budget-av: cam inserted B budget_av: ciintf_slot_reset(): ciintf_slot_reset dvb_ca adaptor 0: PC card did not respond :( Removing it gives these messages: budget_av: ciintf_slot_shutdown(): ciintf_slot_shutdown budget-av: cam ejected 5 dvb_ca_en50221_slot_shutdown budget_av: ciintf_slot_shutdown(): ciintf_slot_shutdown Slot 0 shutdown rmmod budget_av gives this message: ACPI: PCI interrupt for device :04:08.0 disabled What can be learned from this? My guess (I am no DVB programmer) the software detects a card inserted and then it waits on the attribute adres for a value of 0x1D however it looks like this is never returned by the CAM. I don't know what 0x1D actually means though. I have the same problem when I load the budget-av driver while the CAM module is still inserted I only get it working by ejecting and reinserting the CAM module. Which also seems to fail for you. In my case it looked like the CAM module keeps in some kind of initialized state and doesn't output the value 0x1D. I don't know what the solution is though :( - Jeroen ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Working DVB-S + CAM question
Hi gurus, I've two questions for you. 1. Could you point me to a DVB-S hardware supports external CAM modules that is 100% working with Linux. Just tell me a Card and a model. Pointing me to online shop that sells these babies will be perfect. I'm interested in using that card with Irdeto 2 module. 2. Is it possible using the above mentioned card with CAM module to configure the card so I can receive whole PVC (couple of channels) at one time, having in mind that all channels can be decrypted using the same Irdeto2 card? If decryption could happen within CAM module and I'm able to receive couple of channels like F2A channels that would be perfect. -- Cheers, Nick. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Kenerl 2.6.20, mantis and vp-1034
Just bought a new cpu and motherboard and made a clean install of FC6 and made a vanilla 2.6.20 kernel. tried to merge the kromtek.com/dvb/mantis.tar.bz2 driver into the 2.6.20 kernel. I copied the directory linux/driver/media/dvb/mantis to 2.6.20-source/driver/media/dvb Modified the Kconfig and Makefile in 2.6.20-source/driver/media/dvb Copied the file mb86* and cu1216* to 2.6.20-source/driver/media/dvb/frontends And modified the Kconfig and Makefile in 2.6.20-source/driver/media/dvb/frontends Did a make menuconfig to compile the Mantis driver as a module and did a make modules. I received the following two problems and some warnings: 1. Had to remove one line in cu1216.c file (#include linux/config.h) 2. and had to modify the line #include mantis_core.h into #include ../mantis/mantis_core.h. I installed the modules (make modules_install) and loaded the modules (modprobe mantis) Following is the result in the messagelog: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 16 ACPI: PCI Interrupt :02:05.0[A] - Link [LNKB] - GSI 16 (level, low) - IRQ 16 irq: 16, latency: 32 memory: 0xf68ff000, mmio: 0xc2026000 found a VP-1034 PCI DVB-S/DSS device on (02:05.0), Mantis Rev 1 [1822:0014], irq: 16, latency: 32 memory: 0xf68ff000, mmio: 0xc2026000 **WARNING** I2C adapter driver [Mantis I2C] forgot to specify physical device; fix it! MAC Address=[00:08:ca:19:9f:0b] mantis_alloc_buffers (0): DMA=0x2d31 cpu=0x81002d31 size=65536 mantis_alloc_buffers (0): RISC=0x282c5000 cpu=0x8100282c5000 size=1000 DVB: registering new adapter (Mantis dvb adapter). mantis_frontend_init (0): Probing for MB86A16 (DVB-S/DSS) mantis_frontend_init (0): found MB86A16 DVB-S/DSS frontend @0x08 DVB: registering frontend 0 (Fujitsu MB86A16 DVB-S)... Just one WARNING line which I have never seen before. Removed the modules and loaded the mb86a16 and the mantis module with verbose=255 and had the following output in messagelog: ACPI: PCI Interrupt :02:05.0[A] - Link [LNKB] - GSI 16 (level, low) - IRQ 16 gpif status: 6080 irqcfg: 0002 mantis_set_direction (0): TS direction setup irq: 16, latency: 32 memory: 0xf68ff000, mmio: 0xc2062000 found a VP-1034 PCI DVB-S/DSS device on (02:05.0), Mantis Rev 1 [1822:0014], irq: 16, latency: 32 memory: 0xf68ff000, mmio: 0xc2062000 **WARNING** I2C adapter driver [Mantis I2C] forgot to specify physical device; fix it! mantis_i2c_init (0): Initializing I2C .. mantis_i2c_init (0): [0x0408/] mantis_i2c_write: Address=[0x50] W[ 08 === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === ] mantis_i2c_read: Address=[0x50] R[ === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === 00 === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === 08 === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === ca === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === 19 === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === 9f === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === 0b ] MAC Address=[00:08:ca:19:9f:0b] mantis_dma_init (0): Mantis DMA init mantis_alloc_buffers (0): DMA=0x2d31 cpu=0x81002d31 size=65536 mantis_alloc_buffers (0): RISC=0xe465000 cpu=0x81000e465000 size=1000 mantis_calc_lines (0): Mantis RISC block bytes=[4096], line bytes=[2048], line count=[32] mantis_dvb_init (0): dvb_register_adapter DVB: registering new adapter (Mantis dvb adapter). mantis_dvb_init (0): dvb_dmx_init mantis_dvb_init (0): dvb_dmxdev_init mantis_frontend_init (0): Mantis frontend Init mantis_fe_powerup (0): Frontend Power ON mantis_frontend_reset (0): Frontend Reset mantis_frontend_init (0): Device ID=14 mantis_frontend_init (0): Probing for MB86A16 (DVB-S/DSS) mantis_i2c_write: Address=[0x08] W[ 7f === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === ] mantis_i2c_read: Address=[0x08] R[ === Interrupts[4080001/0001]= [* I2C R-ACK ** PCMCIA-07 ** I2C DONE *] === fe ] mantis_frontend_init (0): found MB86A16 DVB-S/DSS frontend @0x08 DVB: registering frontend 0 (Fujitsu MB86A16 DVB-S)... I can scan channels and watch channels without a problem. Currently not able to rotate my rotor but I'm still investigating what the problem might be. Regards, Michel. Some info about the environment: [EMAIL PROTECTED] linux-2.6.20]# uname -a Linux garfield.verbraak.thuis 2.6.20 #3 SMP Sun Feb 18 11:33:30 CET 2007 x86_64 x86_64 x86_64 GNU/Linux [EMAIL PROTECTED] linux-2.6.20]# lspci -v 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) Subsystem: ASRock Incorporation Unknown device 00e1 Flags: bus master, 66MHz, fast devsel, latency 0 Memory at f800 (32-bit, prefetchable) [size=64M] Capabilities: [44] HyperTransport: Slave or Primary Interface
[linux-dvb] saa7134
H all I have tried to get my Compro DVB300T working in Linux for the past two weeks but I have finally conceded defeat! I was told to install the latest drivers into my 2.6-16 kernel, which I did with no luck. So then I installed the latest version of PClinuxOS which has the latest kernel with the relative drivers installed and the modules compiled into the kernel. Now, on startup I can get analogue tv working in Xawtv IF I DON'T load the modules saa7134 or saa7134-dvb. After I load the modules I cannot get any program, Tvtime, xawtv, kaffeine or mplayer to find any channels. My hope is to be able to get Digital video stations showing in Mythtv. BUT I hav'nt installed Mythtv yet as I don't want to commit myself to that weekend of work until I can be assured that I can get the stations working. Can someone help me please I am not a newbie, but I am far from an expert either. I am happy to install any program or do anything that you ask of me. Thanks in advance Vaughan Famularo ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re : [linux-dvb] Working DVB-S + CAM question
Le 23.02.2007 08:07:44, Nick Tannenberg a écrit : Hi gurus, I've two questions for you. 1. Could you point me to a DVB-S hardware supports external CAM modules that is 100% working with Linux. Just tell me a Card and a model. Pointing me to online shop that sells these babies will be perfect. I'm interested in using that card with Irdeto 2 module. 2. Is it possible using the above mentioned card with CAM module to configure the card so I can receive whole PVC (couple of channels) at one time, having in mind that all channels can be decrypted using the same Irdeto2 card? I am pretty sure that you can't do that and I think its because the hardware itself can't do that, but I am not sure. Bye Manu ___ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Working DVB-S + CAM question
On 2/23/07, Nick Tannenberg [EMAIL PROTECTED] wrote: Hi gurus, I've two questions for you. 1. Could you point me to a DVB-S hardware supports external CAM modules that is 100% working with Linux. Just tell me a Card and a model. Technotrend S-1500 + CI works for me. Andy Pointing me to online shop that sells these babies will be perfect. I'm interested in using that card with Irdeto 2 module. 2. Is it possible using the above mentioned card with CAM module to configure the card so I can receive whole PVC (couple of channels) at one time, having in mind that all channels can be decrypted using the same Irdeto2 card? If decryption could happen within CAM module and I'm able to receive couple of channels like F2A channels that would be perfect. -- Cheers, Nick. ___ 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
Re: [linux-dvb] Working DVB-S + CAM question
Andrew Lyon wrote: On 2/23/07, Andrew Lyon [EMAIL PROTECTED] wrote: On 2/23/07, Nick Tannenberg [EMAIL PROTECTED] wrote: Hi gurus, I've two questions for you. 1. Could you point me to a DVB-S hardware supports external CAM modules that is 100% working with Linux. Just tell me a Card and a model. Technotrend S-1500 + CI works for me. http://www.dvbshop.net/product_info.php/info/p146_Technotrend-Budget-S-1500-incl--Remote--W98-ME-2K-XP-MCE-.html Thanks a lot. I buy one now for testing. -- Cheers, Nick. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Working DVB-S + CAM question
On 2/23/07, Andrew Lyon [EMAIL PROTECTED] wrote: On 2/23/07, Nick Tannenberg [EMAIL PROTECTED] wrote: Hi gurus, I've two questions for you. 1. Could you point me to a DVB-S hardware supports external CAM modules that is 100% working with Linux. Just tell me a Card and a model. Technotrend S-1500 + CI works for me. http://www.dvbshop.net/product_info.php/info/p146_Technotrend-Budget-S-1500-incl--Remote--W98-ME-2K-XP-MCE-.html Andy Pointing me to online shop that sells these babies will be perfect. I'm interested in using that card with Irdeto 2 module. 2. Is it possible using the above mentioned card with CAM module to configure the card so I can receive whole PVC (couple of channels) at one time, having in mind that all channels can be decrypted using the same Irdeto2 card? If decryption could happen within CAM module and I'm able to receive couple of channels like F2A channels that would be perfect. -- Cheers, Nick. ___ 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
Re: Re : [linux-dvb] Working DVB-S + CAM question
manu wrote: Le 23.02.2007 08:07:44, Nick Tannenberg a écrit : Hi gurus, I've two questions for you. 1. Could you point me to a DVB-S hardware supports external CAM modules that is 100% working with Linux. Just tell me a Card and a model. Pointing me to online shop that sells these babies will be perfect. I'm interested in using that card with Irdeto 2 module. 2. Is it possible using the above mentioned card with CAM module to configure the card so I can receive whole PVC (couple of channels) at one time, having in mind that all channels can be decrypted using the same Irdeto2 card? I am pretty sure that you can't do that and I think its because the hardware itself can't do that, but I am not sure. Bye Manu As far as i know, a CAM can decrypt only 1 channel at the same time. Irrespective of which CAM make model. Rudy ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Could somebody please provide a link to the Mantis VP-1033\2033\3033 Driver patches
Manu Abraham wrote: On 1/28/07, Ruediger Dohmhardt [EMAIL PROTECTED] wrote: Manu Abraham wrote: On 1/22/07, Ruediger Dohmhardt [EMAIL PROTECTED] wrote: How, and from where, can I download the patches in order to build driver modules for the Mantis chips VP-1033\2033\3033 http://kromtek.com/dvb/mantis.tar.bz2 Ok, I got the driver for the Mantis VP-2033 (the one for the cable) on my Turion-AMD x86_64 working. I took your code from http://kromtek.com/dvb/, patched it with you don't need any patches, all the patches are applied to that tree that which the tarball contains. manu Yes, it's right. The tarball from http://kromtek.com/dvb/mantis.tar.bz2 does not require any patches. I just installed kernel 2.6.20.1 on my AMD-Turion X86_64. I applied the same changes to the Kernel-tree as described by Michel Verbraak in his E-Mail two hours ago. The TwinhanDTV Cab-CI (2033 Mantis) works fine. Two notes: -Switching channels is a bit slow (lasts 4 seconds). I'm not sure, whether this is an issue with Kaffeine 0.83 or with the driver. -CI/CAM does not work. Is this supported by the driver? Do I miss CI/CAM support only from Kaffeine? Ciao Ruediger D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: Re : [linux-dvb] Working DVB-S + CAM question
On Fri, Feb 23, 2007 at 03:03:37PM +0100, Rudy Zijlstra wrote: manu wrote: Le 23.02.2007 08:07:44, Nick Tannenberg a écrit : Hi gurus, I've two questions for you. 1. Could you point me to a DVB-S hardware supports external CAM modules that is 100% working with Linux. Just tell me a Card and a model. Pointing me to online shop that sells these babies will be perfect. I'm interested in using that card with Irdeto 2 module. 2. Is it possible using the above mentioned card with CAM module to configure the card so I can receive whole PVC (couple of channels) at one time, having in mind that all channels can be decrypted using the same Irdeto2 card? I am pretty sure that you can't do that and I think its because the hardware itself can't do that, but I am not sure. Bye Manu As far as i know, a CAM can decrypt only 1 channel at the same time. Irrespective of which CAM make model. This depends on the CAM, the CI stack you use and what streams you want to decrypt of each programme. Alphacrypt and Cryptoworks can at least decrypt two services with two program streams each, I did not get this to work with some other modules. For Conax and Viaccess, have a look here: http://www.precon.com/sat/receiver/module.htm Rudy Regards, Wolfgang ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Nexus-S Oops when used on a 3.3-volt bus
I recently put together a system which consists entirely of 3.3-volt
PCI 2.3slots. All modules load successfully and recognize my Nexus. I
can do an
femon without issue. However, when tuning the card I get an oops. Can anyone
point me in the right direction? The Nexus is keyed for 3.3-volt PCI, is it
not compatible? Am I barking up the wrong tree here?
BUG: unable to handle kernel NULL pointer dereference at virtual address
0001
printing eip:
0001
*pde =
Oops: [#1]
SMP
Modules linked in: ir_common compat_ioctl32 btcx_risc binfmt_misc nfs nfsd
exportfs lockd nfs_acl sunrpc ppdev parport_pc lp parport ipv6 sg aic7xxx
scsi_transport_spi pcnet32 af_packet lnbp21 stv0299 ivtv wm8775 cx25840
saa7115 msp3400 dvb_usb_gp8psk dvb_usb tuner joydev dvb_pll dvb_ttpci
dvb_core psmouse mousedev serio_raw saa7146_vv tsdev evdev i2c_algo_bit
video_buf saa7146 cx2341x ttpci_eeprom tveeprom videodev v4l2_common
v4l1_compat 8250_pnp ibmphp floppy pcspkr rtc e100 mii ibmasm dm_round_robin
dm_multipath ext3 jbd mbcache dm_mirror dm_snapshot multipath raid10 raid1
raid0 linear md_mod sd_mod ide_cd cdrom generic qla2xxx firmware_class
scsi_transport_fc acenic scsi_mod ehci_hcd shpchp pci_hotplug ohci_hcd
serverworks usbcore ide_core i2c_piix4 i2c_core thermal processor fan unix
dm_mod
CPU:1
EIP:0060:[0001]Not tainted VLI
EFLAGS: 00010246 (2.6.18-4-686-smp #2)
EIP is at 0x1
eax: efe9625c ebx: 80046f45 ecx: 80046f45 edx: ec9c2680
esi: efe9625c edi: 0004 ebp: ec613ec8 esp: ec613eb0
ds: 007b es: 007b ss: 0068
Process dvbscan_na (pid: 13560, ti=ec612000 task=ecf0a570 task.ti=ec612000)
Stack: f0dae109 ec613ec8 ec9c2680 efe9625c 0002 0001
0002
ec613f30 ec613f2c b5d4567f 0670 c01223fa
ec613f10
00d851f0 ec613f10 0009 dfb40570 dfb40570 b5d4a7ae 0670
487c
Call Trace:
[f0dae109] dvb_usercopy+0xa3/0x117 [dvb_core]
[c01223fa] getnstimeofday+0x30/0xb9
[c012e9ed] lock_hrtimer_base+0x19/0x35
[c012ea86] hrtimer_try_to_cancel+0x33/0x48
[c012eaa9] hrtimer_cancel+0xe/0x14
[f0dae1b7] dvb_generic_ioctl+0x3a/0x44 [dvb_core]
[c016ca34] do_ioctl+0x64/0x6d
[c016ca8d] vfs_ioctl+0x50/0x279
[c0111f9d] do_page_fault+0xdd/0x571
[c016cd13] sys_ioctl+0x5d/0x6e
[c0102bab] syscall_call+0x7/0xb
Code: Bad EIP value.
EIP: [0001] 0x1 SS:ESP 0068:ec613eb0
1BUG: unable to handle kernel paging request at virtual address 30303030
printing eip:
30303030
*pde =
Oops: [#2]
SMP
Modules linked in: ir_common compat_ioctl32 btcx_risc binfmt_misc nfs nfsd
exportfs lockd nfs_acl sunrpc ppdev parport_pc lp parport ipv6 sg aic7xxx
scsi_transport_spi pcnet32 af_packet lnbp21 stv0299 ivtv wm8775 cx25840
saa7115 msp3400 dvb_usb_gp8psk dvb_usb tuner joydev dvb_pll dvb_ttpci
dvb_core psmouse mousedev serio_raw saa7146_vv tsdev evdev i2c_algo_bit
video_buf saa7146 cx2341x ttpci_eeprom tveeprom videodev v4l2_common
v4l1_compat 8250_pnp ibmphp floppy pcspkr rtc e100 mii ibmasm dm_round_robin
dm_multipath ext3 jbd mbcache dm_mirror dm_snapshot multipath raid10 raid1
raid0 linear md_mod sd_mod ide_cd cdrom generic qla2xxx firmware_class
scsi_transport_fc acenic scsi_mod ehci_hcd shpchp pci_hotplug ohci_hcd
serverworks usbcore ide_core i2c_piix4 i2c_core thermal processor fan unix
dm_mod
CPU:1
EIP:0060:[30303030]Not tainted VLI
EFLAGS: 00010246 (2.6.18-4-686-smp #2)
EIP is at 0x30303030
eax: effeabe8 ebx: effeabe8 ecx: 30303030 edx:
esi: ec9c2680 edi: effeaddc ebp: efe9625c esp: ec613d58
ds: 007b es: 007b ss: 0068
Process dvbscan_na (pid: 13560, ti=ec612000 task=ecf0a570 task.ti=ec612000)
Stack: f0db46c2 efe96384 0008 ec9c2680 efe9625c ef824c6c
c015ca48
dff547c0 ec9c2680 ed005b40 ed005b40
c015a1d7
0001 dfd092c0 c011bf2f
000c
Call Trace:
[f0db46c2] dvb_frontend_release+0x41/0x67 [dvb_core]
[c015ca48] __fput+0x93/0x175
[c015a1d7] filp_close+0x3e/0x62
[c011bf2f] put_files_struct+0xa8/0xc3
[c011d01a] do_exit+0x146/0x8b2
[c0103677] apic_timer_interrupt+0x1f/0x24
[c01040a1] do_trap+0x0/0xb5
[c0112139] do_page_fault+0x279/0x571
[c0111ec0] do_page_fault+0x0/0x571
[c0103729] error_code+0x39/0x40
[f0dae109] dvb_usercopy+0xa3/0x117 [dvb_core]
[c01223fa] getnstimeofday+0x30/0xb9
[c012e9ed] lock_hrtimer_base+0x19/0x35
[c012ea86] hrtimer_try_to_cancel+0x33/0x48
[c012eaa9] hrtimer_cancel+0xe/0x14
[f0dae1b7] dvb_generic_ioctl+0x3a/0x44 [dvb_core]
[c016ca34] do_ioctl+0x64/0x6d
[c016ca8d] vfs_ioctl+0x50/0x279
[c0111f9d] do_page_fault+0xdd/0x571
[c016cd13] sys_ioctl+0x5d/0x6e
[c0102bab] syscall_call+0x7/0xb
Code: Bad EIP value.
EIP: [30303030] 0x30303030 SS:ESP 0068:ec613d58
1Fixing recursive fault but reboot is needed!
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: STB0899 and TT 3200-S2
I do have an update: I was able to patch the v4l-dvb mercurial tip with patches from http://kromtek.com/dvb/patches/ and build the stb0899 modules. I was able to load the stb0899 kernel module successfully along with the budget kernel module but I can't see and /dev/dvb devices. I saw the post from manu about the new szap, but I can't even get the card up. Manu - have you ever used the TT3200-S2 successfully? Has anyone? --Mike The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DVB-T tuning data for au-SpencerGulf
Hi, according to google, this is the right place to send... if not, please pass on. following is the data for digital TV for the spencer gulf area in south australia #Australia / South Australia / Pt Pirie (THE BLUFF) # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy # ABC T 59950 7MHz 3/4 NONE QAM64 8k 1/16 NONE # Southern Cross T 64150 7MHz 3/4 NONE QAM64 8k 1/16 NONE # SBS T 62050 7MHz 3/4 NONE QAM64 8k 1/8 NONE (ref: http://www.dba.org.au/index.asp?sectionID=22 ) HTH, adam ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] patch, which supports some new DVB-C budget cards
On Tuesday 13 February 2007 21:54:49 Janne Grunau wrote: I would like it, if the owners of such new cards do test the patch. The patch may also affect all cards which are supported by the modules budget-av and budget. The patched hg version works with following two cards: saa7146: found saa7146 @ mem c2058000 (revision 1, irq 17) (0x1894,0x0020). DVB: registering new adapter (KNC1 DVB-C). TDA10021: i2c-addr = 0x0d, id = 0x7c This card stops delivering data as soon as a CAM is inserted. gnutv -cammenu works fine though. saa7146: found saa7146 @ mem c2078000 (revision 1, irq 19) (0x153b,0x1156). DVB: registering new adapter (Terratec Cinergy 1200 DVB-C). TDA10021: i2c-addr = 0x0c, id = 0x7c My Cinergy works flawlessly with the same CI and CAM. Janne ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] stb0899 troubles
On Friday, 23. February 2007 12:03, Manu Abraham wrote: You need to use the modified version of szap (temporarily) ..http://kromtek.com/dvb/szap.c Thanks - but it doesn't help: [EMAIL PROTECTED] szap]# ./patched_szap -c channels-conf/dvb-s/Astra-19.2E n24 reading channels from file 'channels-conf/dvb-s/Astra-19.2E' zapping to 34 'N24': sat 0, frequency = 12480 MHz V, symbolrate 2750, vpid = 0x07ff, apid = 0x0800 sid = 0x002f Querying info .. Delivery system=DVB-S using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' FE_DISEQC_SEND_MASTER_CMD failed: Connection timed out --- Using 'STB0899 DVB-S' DVB-Sstatus 00 | signal | snr | ber | unc fffe | status 00 | signal | snr | ber | unc fffe | status 00 | signal | snr | ber | unc fffe | ... While patched_szap is running, the driver logs these bits: stb0899_init: Initializing STB0899 ... stb0899_init: init device stb0899_read_reg: Reg=[0xf2ff], data=00 stb0899_read_reg: Reg=[0xf2ff], data=00 stb0899_init: init S2 demod stb0899_init: init S1 demod stb0899_read_reg: Reg=[0xf6ff], data=00 last message repeated 30 times stb0899_init: init S2 FEC stb0899_init: init TST stb0899_read_reg: Reg=[0xf412], data=41 stb0899_read_reg: Reg=[0xf1b3], data=15 stb0899_get_mclk: div=21, mclk=9900 stb0899_read_reg: Reg=[0xf40e], data=00 dvb_frontend_ioctl: DVBFE_GET_INFO stb0899_get_info: Get Info stb0899_get_info: Querying DVB-S info stb0899_get_info: delivery system=1 stb0899_read_reg: Reg=[0xf0a8], data=20 stb0899_read_reg: Reg=[0xf0a0], data=32 stb0899_read_reg: Reg=[0xf0a8], data=20 last message repeated 26 times stb0899_wait_diseqc_fifo_empty: timed out!! stb0899_read_reg: Reg=[0xf0a8], data=20 stb0899_read_reg: Reg=[0xf0a0], data=36 stb0899_read_reg: Reg=[0xf0a0], data=36 stb0899_read_reg: Reg=[0xf0a8], data=11 stb0899_read_reg: Reg=[0xf0a8], data=11 stb0899_read_reg: Reg=[0xf0a8], data=30 stb0899_read_reg: Reg=[0xf0a8], data=20 stb0899_search: set DVB-S params stb0899_search: delivery system=1 stb0899_search: Frequency=0, Srate=0 stb0899_read_reg: Reg=[0xf50d], data=00 last message repeated 2 times stb0899_search: set DVB-S params stb0899_search: delivery system=1 stb0899_search: Frequency=0, Srate=0 stb0899_read_reg: Reg=[0xf50d], data=00 stb0899_read_reg: Reg=[0xf50d], data=00 stb0899_search: set DVB-S params stb0899_search: delivery system=1 stb0899_search: Frequency=0, Srate=0 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: Nexus-S Oops when used on a 3.3-volt bus
I enabled debug mode in the stv0299 module and get the following: Feb 23 12:52:02 corbin2 kernel: stv0299: stv0299: init chip Feb 23 12:52:02 corbin2 kernel: stv0299: stv0299_wait_diseqc_idle Feb 23 12:52:02 corbin2 kernel: stv0299: stv0299_send_diseqc_msg Feb 23 12:52:02 corbin2 kernel: stv0299: stv0299_wait_diseqc_idle Feb 23 12:52:02 corbin2 kernel: stv0299: stv0299_readreg: readreg error (reg == 0x0a, ret == -1) Feb 23 12:52:03 corbin2 last message repeated 2 times Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_wait_diseqc_idle: timeout!! Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_set_frontend : FE_SET_FRONTEND Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_readreg: readreg error (reg == 0x0c, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_writeregI: writereg error (reg == 0x0c, val == 0x01, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_writeregI: writereg error (reg == 0x05, val == 0xb5, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_writeregI: writereg error (reg == 0x05, val == 0x35, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_set_FEC Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_writeregI: writereg error (reg == 0x31, val == 0x10, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_writeregI: writereg error (reg == 0x13, val == 0xb6, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_writeregI: writereg error (reg == 0x14, val == 0x53, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_writeregI: writereg error (reg == 0x1f, val == 0x3a, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_writeregI: writereg error (reg == 0x20, val == 0x2e, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_writeregI: writereg error (reg == 0x21, val == 0x90, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_writeregI: writereg error (reg == 0x22, val == 0x00, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_writeregI: writereg error (reg == 0x23, val == 0x00, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_readreg: readreg error (reg == 0x18, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_readreg: readreg error (reg == 0x1b, ret == -1) Feb 23 12:52:03 corbin2 kernel: stv0299: stv0299_read_status : FE_READ_STATUS : VSTATUS: 0x00 This is 2.6.18 kernel running linux-dvb from 01/16/07. - Mark. On 2/23/07, Mark Buechler [EMAIL PROTECTED] wrote: I recently put together a system which consists entirely of 3.3-volt PCI 2.3 slots. All modules load successfully and recognize my Nexus. I can do an femon without issue. However, when tuning the card I get an oops. Can anyone point me in the right direction? The Nexus is keyed for 3.3-voltPCI, is it not compatible? Am I barking up the wrong tree here? BUG: unable to handle kernel NULL pointer dereference at virtual address 0001 printing eip: 0001 *pde = Oops: [#1] SMP Modules linked in: ir_common compat_ioctl32 btcx_risc binfmt_misc nfs nfsd exportfs lockd nfs_acl sunrpc ppdev parport_pc lp parport ipv6 sg aic7xxx scsi_transport_spi pcnet32 af_packet lnbp21 stv0299 ivtv wm8775 cx25840 saa7115 msp3400 dvb_usb_gp8psk dvb_usb tuner joydev dvb_pll dvb_ttpci dvb_core psmouse mousedev serio_raw saa7146_vv tsdev evdev i2c_algo_bit video_buf saa7146 cx2341x ttpci_eeprom tveeprom videodev v4l2_common v4l1_compat 8250_pnp ibmphp floppy pcspkr rtc e100 mii ibmasm dm_round_robin dm_multipath ext3 jbd mbcache dm_mirror dm_snapshot multipath raid10 raid1 raid0 linear md_mod sd_mod ide_cd cdrom generic qla2xxx firmware_class scsi_transport_fc acenic scsi_mod ehci_hcd shpchp pci_hotplug ohci_hcd serverworks usbcore ide_core i2c_piix4 i2c_core thermal processor fan unix dm_mod CPU:1 EIP:0060:[0001]Not tainted VLI EFLAGS: 00010246 (2.6.18-4-686-smp #2) EIP is at 0x1 eax: efe9625c ebx: 80046f45 ecx: 80046f45 edx: ec9c2680 esi: efe9625c edi: 0004 ebp: ec613ec8 esp: ec613eb0 ds: 007b es: 007b ss: 0068 Process dvbscan_na (pid: 13560, ti=ec612000 task=ecf0a570 task.ti=ec612000 ) Stack: f0dae109 ec613ec8 ec9c2680 efe9625c 0002 0001 0002 ec613f30 ec613f2c b5d4567f 0670 c01223fa ec613f10 00d851f0 ec613f10 0009 dfb40570 dfb40570 b5d4a7ae 0670 487c Call Trace: [f0dae109] dvb_usercopy+0xa3/0x117 [dvb_core] [c01223fa] getnstimeofday+0x30/0xb9 [c012e9ed] lock_hrtimer_base+0x19/0x35 [c012ea86] hrtimer_try_to_cancel+0x33/0x48 [c012eaa9] hrtimer_cancel+0xe/0x14 [f0dae1b7] dvb_generic_ioctl+0x3a/0x44 [dvb_core] [c016ca34] do_ioctl+0x64/0x6d [c016ca8d] vfs_ioctl+0x50/0x279 [c0111f9d] do_page_fault+0xdd/0x571 [c016cd13] sys_ioctl+0x5d/0x6e [c0102bab] syscall_call+0x7/0xb Code: Bad EIP value. EIP: [0001] 0x1 SS:ESP 0068:ec613eb0 1BUG: unable to handle kernel paging request at virtual address 30303030 printing eip: 30303030 *pde = Oops: [#2] SMP Modules linked in: ir_common compat_ioctl32
[linux-dvb] Re: twinhan alpha vp7045A newer rev, firmware
Hi, I have managed to capture some traffic with usbsnoop, I´ve captured from insertion of the stick to a few seconds of tuning. The snoop can be found here, http://www.struct.se/usbsnoop.log-1.bz2 Any hints on extracting the firmware ? http://www.isely.net/pvrusb2/utils.html been looking at the code but nothing further yet. Anyone ? /Henrik On 2/22/07, Henrik Beckman [EMAIL PROTECTED] wrote: Hi, Anyone had any succes with getting the newer alphas to work ? http://www.linuxtv.org/pipermail/linux-dvb/2006-November/014202.html If not I will try to extract the firmware from the latest windows driver, can anyone help me with hints on how to do this. Would it be possible to initialize the stick in windows and then without deinitializing it connect it to linux and download the firmware ? (thinking vmware or a powered hub here). TIA /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] about nova TD stick
Hi all, I just got myself a Nova-TD stick and plugged it in to one of my MythTV boxes just for the fun of it ;). I've noted on the linuxtv.org web that there is currently no support for this DVB stick. Is there any way I can help out with that? I'd consider myself a decent programmer (although I mostly work in Java nowadays) but I have done no kernel development whatsoever. How difficult do you think it would be to implement a driver for this stick? Would anyone be able to give me a push in the right direction? // J ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] saa7134
Hi, Vaughan Famularo schrieb: H all I have tried to get my Compro DVB300T working in Linux for the past two weeks but I have finally conceded defeat! I was told to install the latest drivers into my 2.6-16 kernel, which I did with no luck. So then I installed the latest version of PClinuxOS which has the latest kernel with the relative drivers installed and the modules compiled into the kernel. Hm, did you really mean this? 1) You should not try to merge code from linuxtv.org into the kernel source tree. You should compile it separately (but you need installed kernel sources and you need to have v4l2 enabled in the kernel). 2) You should compile the video and dvb code as modules. Don't compile them into the kernel. Now, on startup I can get analogue tv working in Xawtv IF I DON'T load the modules saa7134 or saa7134-dvb. After I load the modules I cannot get any program, Tvtime, xawtv, kaffeine or mplayer to find any channels. Hm, the card can't work at all without the saa7134 driver... Unless you really compiled the stuff into the kernel - see above. My hope is to be able to get Digital video stations showing in Mythtv. BUT I hav'nt installed Mythtv yet as I don't want to commit myself to that weekend of work until I can be assured that I can get the stations working. Can someone help me please I am not a newbie, but I am far from an expert either. I am happy to install any program or do anything that you ask of me. The card should work with recent kernels, i have a very similar one. But besides the module issue, there are 2 pitfalls: - For a technical reason, you must not load the tuner module before the saa7134 module. - There was a bug in some versions that made dvb-t support fail. This is fixed in the current repository (and also in 2.6.20) After you corrected these things and it still doesn't work, you need to provide more information. Please send us the kernel log messages caused by the modprobe Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: Re : Re : [linux-dvb] Working DVB-S + CAM question
On Fri, Feb 23, 2007 at 06:30:03PM -0400, manu wrote: Le 23.02.2007 10:45:31, Wolfgang Wegner a écrit : [...] This depends on the CAM, the CI stack you use and what streams you want to decrypt of each programme. Alphacrypt and Cryptoworks can at least decrypt two services with two program streams each, I did not get this to work with some other modules. For Conax and Viaccess, have a look here: http://www.precon.com/sat/receiver/module.htm Hmm you're right, but is this supported with the current DVB drivers? Bye Manu I have to admit: I do not know. Currently I have no CI in my linux-DVB setup. Experience with CI modules is from my work, with non-linux (closed source) CI stack. Regards, Wolfgang ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] saa7134
Attn Hartmut Hm, did you really mean this? *No I meant that they are modules Sorry 1) You should not try to merge code from linuxtv.org into the kernel source tree. You should compile it separately (but you need installed kernel sources and you need to have v4l2 enabled in the kernel). 2) You should compile the video and dvb code as modules. Don't compile them into the kernel. Now, on startup I can get analogue tv working in Xawtv IF I DON'T load the modules saa7134 or saa7134-dvb. After I load the modules I cannot get any program, Tvtime, xawtv, kaffeine or mplayer to find any channels. Hm, the card can't work at all without the saa7134 driver... Unless you really compiled the stuff into the kernel - see above. ** So the saa7134 module MUST be loaded on startup YES? If so, why does it stop working when I modprobe saa7134-dvb?? And I am never able to get digital stations in Linux although I can in WinXP? Just meaning that the stations are available My hope is to be able to get Digital video stations showing in Mythtv. BUT I hav'nt installed Mythtv yet as I don't want to commit myself to that weekend of work until I can be assured that I can get the stations working. Can someone help me please I am not a newbie, but I am far from an expert either. I am happy to install any program or do anything that you ask of me. The card should work with recent kernels, i have a very similar one. But besides the module issue, there are 2 pitfalls: - For a technical reason, you must not load the tuner module before the saa7134 module. - There was a bug in some versions that made dvb-t support fail. This is fixed in the current repository (and also in 2.6.20) Should I install a 2.6.20 kernel then??? Thanks for your help Hartmut! After you corrected these things and it still doesn't work, you need to provide more information. Please send us the kernel log messages caused by the modprobe Hartmut This email was sent from Netspace Webmail: http://www.netspace.net.au ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] stb0899 troubles
On 2/23/07, Bernhard Rosenkraenzer [EMAIL PROTECTED] wrote: On Friday, 23. February 2007 12:03, Manu Abraham wrote: You need to use the modified version of szap (temporarily) ..http://kromtek.com/dvb/szap.c Thanks - but it doesn't help: Works at my side and for a couple of others..looking at the logs, [EMAIL PROTECTED] szap]# ./patched_szap -c channels-conf/dvb-s/Astra-19.2E n24 reading channels from file 'channels-conf/dvb-s/Astra-19.2E' zapping to 34 'N24': sat 0, frequency = 12480 MHz V, symbolrate 2750, vpid = 0x07ff, apid = 0x0800 sid = 0x002f Querying info .. Delivery system=DVB-S using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' FE_DISEQC_SEND_MASTER_CMD failed: Connection timed out --- Using 'STB0899 DVB-S' DVB-Sstatus 00 | signal | snr | ber | unc fffe | status 00 | signal | snr | ber | unc fffe | status 00 | signal | snr | ber | unc fffe | ... While patched_szap is running, the driver logs these bits: stb0899_init: Initializing STB0899 ... [..] stb0899_search: Frequency=0, Srate=0 the application failed to send Frequency and symbol rate to the driver .. ? Did you use the patches or the tarball ? (You shouldn't see this issue if you are using the tree) If you used the patches, change MINOR VERSION from 1 to 2 in version.h and you are ahead. (Forgot to push in the version patch) will need to push in that as well. Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: STB0899 and TT 3200-S2
On 2/23/07, Mike Kazmier [EMAIL PROTECTED] wrote: I do have an update: I was able to patch the v4l-dvb mercurial tip with patches from http://kromtek.com/dvb/patches/ and build the stb0899 modules. I was able to load the stb0899 kernel module successfully along with the budget kernel module but I can't see and /dev/dvb devices. I saw the post from manu about the new szap, but I can't even get the card up. Manu - have you ever used the TT3200-S2 successfully? Has anyone? Yep, will update the tree soon. manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
