Re: [linux-dvb] Twinhan 1034 question
Abylai Ospan schreef: Hello ! I have gentoo linux with kernel.org stock kernel 2.6.20 and I have compiled and installed v4l source from http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 dated 01-Apr-2007 17:46 4.8M. After 'modprobe mantis' I'v see in dmesg: ACPI: PCI Interrupt :02:03.0[A] - GSI 23 (level, low) - IRQ 19 irq: 19, latency: 32 memory: 0xfbfff000, mmio: 0xf8826000 found a VP-1034 PCI DVB-S/DSS device on (02:03.0), Mantis Rev 1 [1822:0014], irq: 19, latency: 32 memory: 0xfbfff000, mmio: 0xf8826000 MAC Address=[00:08:ca:1a:a3:68] mantis_alloc_buffers (0): DMA=0x301f cpu=0xf01f size=65536 mantis_alloc_buffers (0): RISC=0x377af000 cpu=0xf77af000 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)... and /dev/dvb/adapter0/ tree is created. It's looks like card correctly detected. But I don't see /dev/dvb/adapter0/ca0 for CI module. Is this driver supports Twinhan 1034 CI interface ? May be some repository with newer version is available ? Thanks ! -- Abylai Ospan [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] NetUP Inc. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Currently not in the supplied open source drivers. There is a binary package at the Twinhan (download page) website which does support the CI but the modules were compiled for the first Fedore Core 6 kernel on a i586 platform. Regards, Michel ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan 1034 question
Abylai Ospan schreef: В Вск, 02/09/2007 в 19:53 +0200, Michel Verbraak пишет: Abylai Ospan schreef: Hello ! I have gentoo linux with kernel.org stock kernel 2.6.20 and I have compiled and installed v4l source from http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 dated 01-Apr-2007 17:46 4.8M. After 'modprobe mantis' I'v see in dmesg: ACPI: PCI Interrupt :02:03.0[A] - GSI 23 (level, low) - IRQ 19 irq: 19, latency: 32 memory: 0xfbfff000, mmio: 0xf8826000 found a VP-1034 PCI DVB-S/DSS device on (02:03.0), Mantis Rev 1 [1822:0014], irq: 19, latency: 32 memory: 0xfbfff000, mmio: 0xf8826000 MAC Address=[00:08:ca:1a:a3:68] mantis_alloc_buffers (0): DMA=0x301f cpu=0xf01f size=65536 mantis_alloc_buffers (0): RISC=0x377af000 cpu=0xf77af000 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)... and /dev/dvb/adapter0/ tree is created. It's looks like card correctly detected. But I don't see /dev/dvb/adapter0/ca0 for CI module. Is this driver supports Twinhan 1034 CI interface ? May be some repository with newer version is available ? Thanks ! -- Abylai Ospan [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] NetUP Inc. ___ linux-dvb mailing list linux-dvb@linuxtv.org mailto:linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Currently not in the supplied open source drivers. There is a binary package at the Twinhan (download page) website which does support the CI but the modules were compiled for the first Fedore Core 6 kernel on a i586 platform. Ok, thanks. But this module can't loading under linux kernel 2.6.20 (as expected): insmod: error inserting 'linuxdriver/v4l/mantis.ko': -1 Invalid module format mantis: version magic '2.6.18-1.2798.fc6 SMP mod_unload 686 REGPARM 4KSTACKS gcc-4.1' should be '2.6.20 SMP mod_unload PENTIUM4 ' Do you know how to force load this module ? May be some way to change magic string for matching ? I don't want to install FC6 ... :) Thanks! -- Abylai Ospan [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] NetUP Inc. You could try a 'modprobe --force mantis'. But hte other modules neede should be that of the binary package and should also be loade with the --force option. Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] modprobe mantis stalls/hangs/freezes (Twinhan VP-1034 and ivtv)
Manu Abraham schreef: Michel Verbraak wrote: I have a Twinhan VP-1034 and I use the the latest hg, today, and http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 with kernel 2.6.22.1. When I do a 'modprobe mantis' my prompt never returns. The machine still is working. [snip] Address=[0x25] W[ 00 3mantis_ack_wait (0): Waiting for Slave RACK Aug 25 17:53:33 recorder kernel: mantis_ack_wait (0): Waiting for Slave RACK Aug 25 17:53:42 recorder last message repeated 499 times Aug 25 17:53:42 recorder kernel: mantis_ack_wait (0): Slave RACK Fail ! Aug 25 17:53:42 recorder kernel: mantis_i2c_write (0): ACK failedW I must say I also have a Hauppauge PVR-150 and a PVR-350 in this machine, using ivtv from hg, and when I remove both I do not have this problem. The modules load without any problems. with ivtv modules loaded somebody else mentioned of issues with regards to DMA transfers on the 878 based cards. I don't really understand why ivtv modules causes those problems. (IIRC it was Sigmund, i think) lspci -vv gives: 02:09.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01) Subsystem: Twinhan Technology Co. Ltd Unknown device 0014 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (2000ns min, 63750ns max) Interrupt: pin A routed to IRQ 22 Region 0: Memory at f7eff000 (32-bit, prefetchable) [size=4K] 02:0b.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01) Subsystem: Hauppauge computer works Inc. WinTV PVR-350 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 16 bytes Interrupt: pin A routed to IRQ 19 Region 0: Memory at f000 (32-bit, prefetchable) [size=64M] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 02:0d.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01) Subsystem: Hauppauge computer works Inc. WinTV PVR 150 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 16 bytes Interrupt: pin A routed to IRQ 5 Region 0: Memory at ec00 (32-bit, prefetchable) [size=64M] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- If more verbose messages are needed from othe modules please let me know. I do not have this problem with kernel versions 2.6.20 and below. Something changed in 2.6.21 and I do not know what. Without any any driver loaded for the ivtv hardware, do you still experience the same problems ? When I do not load the ivtv modules or any other modules needed bu ivtv, but the cards are still in the computer, and I load the mantis and mb86a16 module following is in the message log: Aug 26 09:47:30 recorder kernel: ACPI: PCI Interrupt :02:09.0[A] - GSI 21 (level, low) - IRQ 22 Aug 26 09:47:30 recorder kernel: Aug 26 09:47:30 recorder kernel: gpif status: 6000 irqcfg: Aug 26 09:47:30 recorder kernel: mantis_set_direction (0): TS direction setup Aug 26 09:47:30 recorder kernel: irq: 22, latency: 64 Aug 26 09:47:30 recorder kernel: memory: 0xf7eff000, mmio: 0xf88de000 Aug 26 09:47:30 recorder kernel: found a VP-1034 PCI DVB-S/DSS device on (02:09.0), Aug 26 09:47:30 recorder kernel: Mantis Rev 1 [1822:0014], irq: 22, latency: 64 Aug 26 09:47:30 recorder kernel: memory: 0xf7eff000, mmio: 0xf88de000 Aug 26 09:47:30 recorder kernel: mantis_i2c_init (0): Initializing I2C .. Aug 26 09:47:30 recorder kernel: mantis_i2c_init (0): [0x0401/] Aug 26 09:47:30 recorder kernel: mantis_i2c_write: Address=[0x50] W[ 08 === Interrupts[401/0001]= [* I2C R-ACK ** I2C DONE *] === Aug 26 09:47:30 recorder kernel: ] Aug 26 09:47:30 recorder kernel: mantis_i2c_read: Address=[0x50] R[ === Interrupts[401/0001]= [* I2C R-ACK ** I2C DONE *] === Aug 26 09:47:30 recorder kernel: 00 === Interrupts[401/0001]= [* I2C R-ACK ** I2C DONE *] === Aug 26 09:47:30 recorder kernel: 08 === Interrupts[401/0001]= [* I2C R-ACK ** I2C DONE *] === Aug 26 09:47:30 recorder kernel: ca === Interrupts[401/0001]= [* I2C R-ACK ** I2C
Re: [linux-dvb] (temp. solution) modprobe mantis stalls/hangs/freezes (Twinhan VP-1034 and ivtv)
Hans Verkuil schreef:
On Sunday 26 August 2007 11:18:56 Michel Verbraak wrote:
Manu Abraham schreef:
Michel Verbraak wrote:
I have a Twinhan VP-1034 and I use the the latest hg, today, and
http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 with kernel 2.6.22.1.
When I do a 'modprobe mantis' my prompt never returns. The machine
still is working.
Aug 26 11:08:32 recorder kernel: ivtv0: Autodetected Hauppauge WinTV
PVR-350 Aug 26 11:08:32 recorder kernel: tuner 2-0061: chip found @
0xc2 (ivtv i2c driver #0)
Aug 26 11:08:32 recorder kernel: ivtv0 i2c: i2c client attach
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ ]
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ 00 00 ]
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ 00 ]
Aug 26 11:08:32 recorder kernel: mantis_i2c_read:
Address=[0x25] R[ 00 ]
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ 00 01 === Interrupts[0001/0001]= [* I2C DONE *]
Ah, ivtv is probing for the saa7115 device. The saa7115 driver probes
among others i2c address 0x25, which is also used by the mantis.
And what's changed is that in kernel 2.6.21 the following change was
made to the saa7115.c driver:
static int saa711x_probe(struct i2c_adapter *adapter)
{
if (adapter-class I2C_CLASS_TV_ANALOG || adapter-class
I2C_CLASS_TV_DIGITAL)
return i2c_probe(adapter, addr_data, saa711x_attach);
return 0;
}
The TV_DIGITAL check was added, so now it is also suddenly used by the
mantis. Apparently added to support the Nexus CA.
The only solution at this time is to add the following module option to
saa7115: ignore=-1,0x25
This should ensure it that it ignores i2c address 0x25. Work is being
done to make probing unnecessary or at least much smarter, but that
will be quite a long transition period, most likely. For the time being
this is probably your only solution.
Regards,
Hans
Hans and Manu,
The mantis and ivtv module loaded ok with the following options for
saa7115 in /etc/modprobe.conf:
options saa7115 ignore=-1,0x25,-1,0x24,-1,0x21,-1,0x20
But ivtv is not working anymore and I get the following when I try to
watch live tv with mythtv:
ivtv0: i2c addr 0x21 not found for command 0xc0445624
ivtv0: i2c addr 0x21 not found for command 0xc008561c
ivtv1: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
ivtv1: Encoder revision: 0x02060039
cx25840 3-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
ivtv0: i2c addr 0x21 not found for command 0xc0445624
ivtv0: i2c addr 0x21 not found for command 0xc008561c
ivtv0: i2c addr 0x21 not found for command 0xc0445624
ivtv0: i2c addr 0x21 not found for command 0xc008561c
ivtv0: i2c addr 0x21 not found for command 0xc0445624
ivtv0: i2c addr 0x21 not found for command 0xc008561c
ivtv0: i2c addr 0x21 not found for command 0xc0cc5605
ivtv0: i2c addr 0x21 not found for command 0x40045613
ivtv0: i2c addr 0x21 not found for command 0x40045612
ivtv0: i2c addr 0x21 not found for command 0xc0cc5605
ivtv0: i2c addr 0x21 not found for command 0x40045613
ivtv0: i2c addr 0x21 not found for command 0x40045612
ivtv0: i2c addr 0x21 not found for command 0xc0cc5605
ivtv0: i2c addr 0x21 not found for command 0x40045613
ivtv0: i2c addr 0x21 not found for command 0x40045612
ivtv0: i2c addr 0x21 not found for command 0xc0cc5605
ivtv0: i2c addr 0x21 not found for command 0x40045613
ivtv0: i2c addr 0x21 not found for command 0x40045612
ivtv0: i2c addr 0x21 not found for command 0xc0cc5605
ivtv0: i2c addr 0x21 not found for command 0x40045613
ivtv0: i2c addr 0x21 not found for command 0x40045612
Probably because saa7115 is ignoring 0x21.
The vp-1034 is working allright.
What I did to get it working is removing the saa7115 module options.
Change the probe function in saa7115.c to:
static int saa711x_probe(struct i2c_adapter *adapter)
{
#ifdef I2C_CLASS_TV_ANALOG
if (adapter-class I2C_CLASS_TV_ANALOG)
#else
if (adapter-id == I2C_HW_B_BT848)
#endif
return i2c_probe(adapter, addr_data, saa711x_attach);
return 0;
}
Recompiled and both modules load without problems now and al is working
again. I know this is not the right work around for everybody but it
works for me.
Regards,
Michel.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] (temp. solution) modprobe mantis stalls/hangs/freezes (Twinhan VP-1034 and ivtv)
Hans Verkuil schreef:
On Sunday 26 August 2007 11:18:56 Michel Verbraak wrote:
Manu Abraham schreef:
Michel Verbraak wrote:
I have a Twinhan VP-1034 and I use the the latest hg, today, and
http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 with kernel 2.6.22.1.
When I do a 'modprobe mantis' my prompt never returns. The machine
still is working.
Aug 26 11:08:32 recorder kernel: ivtv0: Autodetected Hauppauge WinTV
PVR-350 Aug 26 11:08:32 recorder kernel: tuner 2-0061: chip found @
0xc2 (ivtv i2c driver #0)
Aug 26 11:08:32 recorder kernel: ivtv0 i2c: i2c client attach
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ ]
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ 00 00 ]
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ 00 ]
Aug 26 11:08:32 recorder kernel: mantis_i2c_read:
Address=[0x25] R[ 00 ]
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ 00 01 === Interrupts[0001/0001]= [* I2C DONE *]
Ah, ivtv is probing for the saa7115 device. The saa7115 driver probes
among others i2c address 0x25, which is also used by the mantis.
And what's changed is that in kernel 2.6.21 the following change was
made to the saa7115.c driver:
static int saa711x_probe(struct i2c_adapter *adapter)
{
if (adapter-class I2C_CLASS_TV_ANALOG || adapter-class
I2C_CLASS_TV_DIGITAL)
return i2c_probe(adapter, addr_data, saa711x_attach);
return 0;
}
The TV_DIGITAL check was added, so now it is also suddenly used by the
mantis. Apparently added to support the Nexus CA.
The only solution at this time is to add the following module option to
saa7115: ignore=-1,0x25
This should ensure it that it ignores i2c address 0x25. Work is being
done to make probing unnecessary or at least much smarter, but that
will be quite a long transition period, most likely. For the time being
this is probably your only solution.
Regards,
Hans
Hans and Manu,
The mantis and ivtv module loaded ok with the following options for
saa7115 in /etc/modprobe.conf:
options saa7115 ignore=-1,0x25,-1,0x24,-1,0x21,-1,0x20
But ivtv is not working anymore and I get the following when I try to
watch live tv with mythtv:
ivtv0: i2c addr 0x21 not found for command 0xc0445624
ivtv0: i2c addr 0x21 not found for command 0xc008561c
ivtv1: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
ivtv1: Encoder revision: 0x02060039
cx25840 3-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
ivtv0: i2c addr 0x21 not found for command 0xc0445624
ivtv0: i2c addr 0x21 not found for command 0xc008561c
ivtv0: i2c addr 0x21 not found for command 0xc0445624
ivtv0: i2c addr 0x21 not found for command 0xc008561c
ivtv0: i2c addr 0x21 not found for command 0xc0445624
ivtv0: i2c addr 0x21 not found for command 0xc008561c
ivtv0: i2c addr 0x21 not found for command 0xc0cc5605
ivtv0: i2c addr 0x21 not found for command 0x40045613
ivtv0: i2c addr 0x21 not found for command 0x40045612
ivtv0: i2c addr 0x21 not found for command 0xc0cc5605
ivtv0: i2c addr 0x21 not found for command 0x40045613
ivtv0: i2c addr 0x21 not found for command 0x40045612
ivtv0: i2c addr 0x21 not found for command 0xc0cc5605
ivtv0: i2c addr 0x21 not found for command 0x40045613
ivtv0: i2c addr 0x21 not found for command 0x40045612
ivtv0: i2c addr 0x21 not found for command 0xc0cc5605
ivtv0: i2c addr 0x21 not found for command 0x40045613
ivtv0: i2c addr 0x21 not found for command 0x40045612
ivtv0: i2c addr 0x21 not found for command 0xc0cc5605
ivtv0: i2c addr 0x21 not found for command 0x40045613
ivtv0: i2c addr 0x21 not found for command 0x40045612
Probably because saa7115 is ignoring 0x21.
The vp-1034 is working allright.
What I did to get it working is removing the saa7115 module options.
Change the probe function in saa7115.c to:
static int saa711x_probe(struct i2c_adapter *adapter)
{
#ifdef I2C_CLASS_TV_ANALOG
if (adapter-class I2C_CLASS_TV_ANALOG)
#else
if (adapter-id == I2C_HW_B_BT848)
#endif
return i2c_probe(adapter, addr_data, saa711x_attach);
return 0;
}
Recompiled and both modules load without problems now and al is working
again. I know this is not the right work around for everybody but it
works for me.
Regards,
Michel.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] (solved) modprobe mantis stalls/hangs/freezes (Twinhan VP-1034 and ivtv)
Michael Krufky schreef:
Michel Verbraak wrote:
Hans Verkuil schreef:
On Sunday 26 August 2007 11:18:56 Michel Verbraak wrote:
Manu Abraham schreef:
Michel Verbraak wrote:
I have a Twinhan VP-1034 and I use the the latest hg, today, and
http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 with kernel 2.6.22.1.
When I do a 'modprobe mantis' my prompt never returns. The machine
still is working.
Aug 26 11:08:32 recorder kernel: ivtv0: Autodetected Hauppauge WinTV
PVR-350 Aug 26 11:08:32 recorder kernel: tuner 2-0061: chip found @
0xc2 (ivtv i2c driver #0)
Aug 26 11:08:32 recorder kernel: ivtv0 i2c: i2c client attach
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ ]
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ 00 00 ]
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ 00 ]
Aug 26 11:08:32 recorder kernel: mantis_i2c_read:
Address=[0x25] R[ 00 ]
Aug 26 11:08:32 recorder kernel: mantis_i2c_write:
Address=[0x25] W[ 00 01 === Interrupts[0001/0001]= [* I2C DONE *]
Ah, ivtv is probing for the saa7115 device. The saa7115 driver probes
among others i2c address 0x25, which is also used by the mantis.
And what's changed is that in kernel 2.6.21 the following change was
made to the saa7115.c driver:
static int saa711x_probe(struct i2c_adapter *adapter)
{
if (adapter-class I2C_CLASS_TV_ANALOG || adapter-class
I2C_CLASS_TV_DIGITAL)
return i2c_probe(adapter, addr_data, saa711x_attach);
return 0;
}
The TV_DIGITAL check was added, so now it is also suddenly used by the
mantis. Apparently added to support the Nexus CA.
The only solution at this time is to add the following module option
to saa7115: ignore=-1,0x25
This should ensure it that it ignores i2c address 0x25. Work is being
done to make probing unnecessary or at least much smarter, but that
will be quite a long transition period, most likely. For the time
being this is probably your only solution.
Regards,
Hans
Hans and Manu,
The mantis and ivtv module loaded ok with the following options for
saa7115 in /etc/modprobe.conf:
options saa7115 ignore=-1,0x25,-1,0x24,-1,0x21,-1,0x20
^^
Just change the -1 to the i2c bus ID of the mantis device, to prevent saa7115
from probing on the mantis bus. This way, it would not prevent successful
attachment to the ivtv i2c bus, and you wouldn't have to do the hack described
below.
Regards,
Mike
Mike,
I tried your suggestion and it worked. Took me some time to find the
right i2c bus ID because they are ordered from first come first served.
For any one who will read this in the future this is how it can be solved:
1. In my case the mantis driver is claiming an i2c bus id before the
ivtv driver.
2. Make sure your ivtv modules do not load. Rename the ivtv.ko module
file to ivtv.ko.old and do a depmod -a. blacklisting in
/etc/depmod.d/blacklist did not work for me.
3. reboot.
4. 'modprobe i2c-dev' and do 'i2cdetect -l'
5. find the i2c bus id for the Mantis driver. Mine looks like 'i2c-1
smbus Mantis I2C SMBus adapter'.
The bus id is 1 from the i2c-1 part.
6. Add the following line to /etc/modprobe.conf: options saa7115
ignore=1,0x25,1,0x24,1,0x21,1,0x20 (replace the 1's (ones) to your bus id).
7. Rename ivtv.ko.old back to ivtv.ko and do a depmod -a.
8. Reboot and al should be fine. If not the bus-id is wrong.
Thanks to all who helped.
Michel.
snip
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] modprobe mantis stalls/hangs/freezes (Twinhan VP-1034 and ivtv)
I have a Twinhan VP-1034 and I use the the latest hg, today, and http://jusst.de/manu/mantis-v4l-dvb.tar.bz2 with kernel 2.6.22.1. When I do a 'modprobe mantis' my prompt never returns. The machine still is working. Following is in my log with option verbose=255 for mantis module: Aug 25 17:53:32 recorder kernel: ACPI: PCI Interrupt :02:09.0[A] - GSI 21 (level, low) - IRQ 22 Aug 25 17:53:32 recorder kernel: Aug 25 17:53:32 recorder kernel: gpif status: 6000 irqcfg: Aug 25 17:53:32 recorder kernel: mantis_set_direction (0): TS direction setup Aug 25 17:53:32 recorder kernel: irq: 22, latency: 64 Aug 25 17:53:32 recorder kernel: memory: 0xf7eff000, mmio: 0xf88fe000 Aug 25 17:53:32 recorder kernel: found a VP-1034 PCI DVB-S/DSS device on (02:09.0), Aug 25 17:53:32 recorder kernel: Mantis Rev 1 [1822:0014], irq: 22, latency: 64 Aug 25 17:53:32 recorder kernel: memory: 0xf7eff000, mmio: 0xf88fe000 Aug 25 17:53:32 recorder kernel: mantis_i2c_write: Address=[0x25] W[ ] Aug 25 17:53:33 recorder kernel: mantis_i2c_write: Address=[0x25] W[ 00 3mantis_ack_wait (0): Waiting for Slave RACK Aug 25 17:53:33 recorder kernel: mantis_ack_wait (0): Waiting for Slave RACK Aug 25 17:53:42 recorder last message repeated 499 times Aug 25 17:53:42 recorder kernel: mantis_ack_wait (0): Slave RACK Fail ! Aug 25 17:53:42 recorder kernel: mantis_i2c_write (0): ACK failedW I must say I also have a Hauppauge PVR-150 and a PVR-350 in this machine, using ivtv from hg, and when I remove both I do not have this problem. The modules load without any problems. If more verbose messages are needed from othe modules please let me know. I do not have this problem with kernel versions 2.6.20 and below. Something changed in 2.6.21 and I do not know what. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] PCTV200e driver: solved NULL pointer dereference
Juan Antonio Garcia schreef:
After a bit of work I have found the reason for getting the NULL
Pointer dereference error when the PCTV200e is initialized.
The reason is that in the function pctv200e_frontend_attach
adap-fe is NULL, and when the mt352 registration fails it continues
being NULL. When the mt2060 is attached, in mt2060.c the following
line:
struct dvb_frontend *fe = ops-fe;
Tries to reference the NULL pointer.
I have made the following modification to pctv200e.c:
static int pctv200e_frontend_attach(struct dvb_usb_adapter *adap)
{
struct dvb_frontend *fe;
if ((adap-fe = dvb_attach(mt352_attach, pctv200e_mt352_config,
adap-dev-i2c_adap)) != NULL) {
adap-fe-ops.tuner_ops.calc_regs = dvb_usb_tuner_calc_regs;
return 0;
} else {
warn(frontend_attach failed (mt352));
fe = kzalloc(sizeof(struct dvb_frontend), GFP_KERNEL);
if (fe == NULL)
return -EIO;
adap-fe = fe;
}
warn(next: attaching tuner.);
After this the PCTV200e registers and unregisters successfully.
So I guess these changes help...
I would like to continue helping. But I would need some directions,
because I don't know what to do next...
And I am really interested in having the PCTV200e under Linux.
Thanks,
Juan
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
http://us.rd.yahoo.com/mail/es/tagline/messenger/*http://es.voice.yahoo.com/
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Juan,
Have a look at the following page fo your patch and how to get it into
mainline. Create a patch file and send it to this list and it should get
incorporated ito mainline as it looks to me as a sound solution to a bug.
http://www.linuxtv.org/v4lwiki/index.php/SubmittingPatches
Regards,
Michel.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Mantis (vp-1034) and CI (linux driver from Twinhan) question?
Manu, You can probably answer this one. If not maybe someone else. The linux driver which can be downloaded from the Twinhan website for the Mantis family (AZLinux_v1.4.2_CI_FC6), And in my case the vp-1034, is only suitable for the first FC6 kernel. Is has precompiled module binaries. I tried to compile the driver myself but found the dvb sources are missing a directory linux/drivers/media/dvb/cimodule which should contain the file mantis_ca.h I tried it in a xen domain with the specified kernel version but it is offcourse a xen kernel version which is not compatible with the inlcuded precompiled non-xen modules. Why is this part missing? Can we get it from somewhere? I would like to test the ci part of my vp-1034 but I do not want to downgrade my installation to the 2.6.18 kernel of FC6. Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mantis driver with ivtv
joep admiraal schreef: Hello Michel, Thank you for the mini howto. I have downloaded the kernel-source and applied the patches you have described. Now when I do a make menuconfig I can select the mantis device driver. It then has an M in front of it. The frontends are selected as loadable modules. I can not change this. Then I did a make This went without problems Now when I do a make modules_install it does not say anything about mantis, mb86a16 or cu1216... When I do a modprobe mantis it gives me: FATAL: Module mantis not found. Have you got an idea about what I'm doing wrong? thanx, Joep Joep, Forget my last email. My mini howto was not yet complete. I compiled the latest kernel, 2.6.21.1, myself and found it was not complete. I update my mini howto and it works. I tested this myself and have it up and running now. Have a look at http://www.verbraak.org/wiki/index.php/Linux_Mantis_driver Sorry for the misinformation. Michel. Op donderdag 3 mei 2007 07:48, schreef Michel Verbraak: joep admiraal schreef: Hello, I downloaded the mantis file from http://jusst.de/manu/mantis-v4l-dvb.tar.bz2. and used Marko's patch. I can watch FTA channels. The next step is to get my hauppauge 350 working again. It worked fine with ivtv 10.1 but since I installed v4l-dvb it doesn't work anymore. I also downloaded the latest v4l-dvb from cvs. It appears that ivtv is merged into v4l-dvb. When I install that one ivtv is also working. However there's no mantis driver in that one. So now I have 2 versions of v4l-dvb. One with support for the 1034 and the other one with support for the hauppauge 350. Can someone please tell me how I can use both cards at the same time? b.t.w. Great you are all still working on the mantis driver. Can't wait to try the CI when it's ready :) Thanx, Joep ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Joep, Have a look at my mini howto http://www.verbraak.org/wiki/index.php/Linux_Mantis_driver In this I explain how I did it. Regards, Michel. ___ 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] [PROBLEM] Mantis (vp-1034) and ivtv and kernel 2.6.21.1
I tried to upgrade my kernel today from 2.6.20.3 to 2.6.21.1 and the following problem appeared: When I only load the Mantis driver, and not the ivtv driver, everything is OK. When I only load the ivtv driver, and not the mantis driver, everything is OK. When I first load the mantis driver, this loads OK, and then load the ivtv driver this modprobe hangs dead, the system is still up and running but i never get a command promt return, and the following is in the message log: May 5 13:24:09 garfield kernel: mantis_ack_wait (0): Slave RACK Fail ! I have not yet tested to load mantis and ivtv the other way around. Because of this problem I reverted back to kernel 2.6.20.3 Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mantis and MB86A16 (VP-1034) and DiseqC commands
Manu Abraham schreef:
Zoilo Gomez wrote:
Manu Abraham wrote:
sounds like you don't have the tone burst working. Looking in there..
Can you please try the modified burst callback ? You may/may not
need to
play a bit with a bit of sleep after the break in each case.
Sorry Manu, but this is not about diseqc-burst either ...
There are 4 things
1) 13v/18v (LNB Polarization control) (vp1034_set_voltage)
2) 22k tone control (it has OFF/ON) (mb86a16_set_tone)
3) burst (A/B unmodulated/modulated) uses 22k modulation
(mb86a16_send_diseqc_burst)
4) diseqc functions (mb86a16_send_diseqc_msg)
Exactly.
Unless our mutual terminology is inconsistent, diseqc-burst is a
simple enhancement method of controlling an individual 2-state switch,
in addition to existing conventional control by 18/13V for pol selection
and 22kHz for band selection (see:
http://www.eutelsat.com/satellites/pdf/Diseqc/Reference%20docs/bus_spec.pdf).
What I need is DiSEqC 1.0 support, as specified in the above document,
where the entire control information (sat,pol,band) is being passed by
means of a digital message. No voltages or tones.
that one you are looking at send_diseqc_msg. You just managed to confuse
me with the additional 22kmodulation in there
... sorry ...!
IIRC, send_msg had been working. need to see what's wrong. (Maybe diseqc
bus is busy ?)
Can you add a dumb short sleep (~10 ms) before the for loop and try a
larger sleep within the for loop (~100 - 200mS) and see whether any
change in behaviour ?
Assuming that you mean the for-loop in send_diseqc_msg: makes no
difference.
Anyway, it would have surprised me if this had any effect, because the
loop seems to be merely filling a 4-byte hardware buffer with the
message to be sent, and I assume that only when writing 0x90 + msg
length into MB86A16_DCC1, followed by a writeof DISEN (DiSEqC enable?)
to MB86A16_DCCOUT, the hardware is actually being triggered to dispatch
the message.
The last part is almost correct except for a slight change. There is a
bug in there from my side, don't understand how it worked
DISEN = DiSEqC (Mode) enable
DISTA = DiSEqC Transaction Activate
I notice that all other signaling methods are running in parallel
(18/13V, tone bursts etc). Could it be that message dispatch for DiSEqC
is being set up correctly, but then accidentally disabled while in
progress, by one of the other functions? Settings are being poked
straight into the registers as constants, instead of reading back the
actual setting and modifying only the appropriate bit(s). Just a thought.
modified send_msg a bit (didn't compile test yet)
static int mb86a16_send_diseqc_msg(struct dvb_frontend *fe,
struct dvb_diseqc_master_cmd *cmd)
{
struct mb86a16_state *state = fe-demodulator_priv;
int i;
u8 regs = 0x18;
if (cmd-msg_len 6 || cmd-msg_len 3)
return -EINVAL;
// Enable DiSEqC Mode with 50% duty cycle
if (mb86a16_write(state, MB86A16_DCCOUT, MB86A16_DCCOUT_DISEN) 0)
goto err;
// Select DiSEqC and Clock
if (mb86a16_write(state, MB86A16_TONEOUT1, 0x5b) 0)
goto err;
if (mb86a16_write(state, MB86A16_TONEOUT2, 0x04) 0)
goto err;
// Write to registers
for (i = 0; i cmd-msg_len; i++) {
if (mb86a16_write(state, regs, cmd-msg[i]) 0)
goto err;
regs++;
}
msleep_interruptible(10);
// Load length and transmit
if (mb86a16_write(state, MB86A16_DCC1, MB86A16_DCC1_DISTA |
cmd-msg_len))
goto err;
return 0;
err:
dprintk(verbose, MB86A16_ERROR, 1, I2C transfer error);
return -EREMOTEIO;
}
Manu,
Is the above version of mb86a16.c downloadable?
The current download locations
(http://thadathil.net:8000/cgi-bin/hgwebdir.cgi/mantis and
http://jusst.de/manu/mantis-v4l-dvb.tar.bz2) do not contain the above
version of the mb86a16_send_diseqc_msg function.
Michel.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [PATCH] for libdvbsec. Correcting calculation of Goto X diseqc commands
I allready send this patch back in november 2006 but it is still not yet
implemented into the hg tree at linuxtv.org.
Following is a copy from my email from november 2006:
I'm testing the dvbsec api for the Goto X part to control my rotor and
found it did not respond as it should be.
I pulled the DiseqC 1.2 spec from the Eutelsat website and found a bug
in the dvbsec_api.c file. The first diff file solves the bug and makes
the api follow the spec as it should be. But after testing I found out
my rotor did not what it should do.
I looked into the source for MythTV and found that the Angle part of the
DiseqC command is build differently from the spec. So I changed the
dvbsec_api.c file again to act like the MythTV source. See the second
diff file.
With the second diff file my rotor does what I tell it to do. When I say
15.2 Degrees it goes to 15.2 degrees East.
I do not know why there is a difference to the Eutelsat Diseqc 1.2 specs
for this. If somebody knows please tell?
Who is able to apply this patch to the hg repository on linuxtv.org.
Regards,
Michel Verbraak
dvbsec_api.c2nd.diff Signed-off-by: Michel Verbraak [EMAIL PROTECTED]
--- dvb-apps.orig/lib/libdvbsec/dvbsec_api.c 2006-11-25 15:44:50.0 +0100
+++ dvb-apps/lib/libdvbsec/dvbsec_api.c 2006-11-25 19:48:01.0 +0100
@@ -536,19 +536,12 @@ int dvbsec_diseqc_goto_rotator_bearing(s
}
// generate the command
- if (integer -256) {
- return -EINVAL;
- } else if (integer 0) {
- integer = -integer;
- data[3] = 0xf0;
- } else if (integer 256) {
- data[3] = 0x00;
- } else if (integer 512) {
- integer -= 256;
- data[3] = 0x10;
- } else {
- return -EINVAL;
+ if (integer 0.0) {
+ data[3] = 0xD0; // West is a negative angle value
+ } else if (integer = 0.0) {
+ data[3] = 0xE0; // East is a positive angle value
}
+ integer = abs(integer);
data[3] |= ((integer / 16) 0x0f);
integer = integer % 16;
data[4] |= ((integer 0x0f) 4) | fraction;
--- dvbsec_api.c.orig 2006-11-25 15:44:50.0 +0100
+++ dvbsec_api.c2006-11-25 15:43:18.0 +0100
@@ -539,7 +539,7 @@ int dvbsec_diseqc_goto_rotator_bearing(s
if (integer -256) {
return -EINVAL;
} else if (integer 0) {
- integer = -integer;
+ integer += 256;
data[3] = 0xf0;
} else if (integer 256) {
data[3] = 0x00;
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Small gotox program to rotate rotor
I created a small program with which I'm able to rotate my rotor to any given angle with gotox commands. Have a look at my webpage http://www.verbraak.org/wiki/index.php/Goto_X_program I'm posting it to this list because some people requested a copy of the program. Regards, Michel Verbraak ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Small gotox program to rotate rotor
Manu Abraham schreef: Michel Verbraak wrote: I created a small program with which I'm able to rotate my rotor to any given angle with gotox commands. Have a look at my webpage http://www.verbraak.org/wiki/index.php/Goto_X_program I'm posting it to this list because some people requested a copy of the program. would you mind if i pull it in to dvb-apps ? No problem ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mantis and MB86A16 (VP-1034) and DiseqC commands not working.
Manu Abraham schreef: Zoilo Gomez wrote: Hi Manu, Any chance we can finish this issue soon? What i don't understand is.. Michel has diseqc working. Quite a bit lost. Please let me know how I can help; without proper chip-set documentation it seems to me that I can only wait for you to fix it for me ... but I can test your patches of course. The doc isn't great either. Just register addresses and bitfield names and a one line description with regards to the mantis, there is absolutely no documentation at all. Zoilo, Which program are you using and does the setting of your switch? I only have a rotor and not a switch,yet ;) , so I'm not able to test this part either. I will ask a friend if I can borrow one of his. This can take some time but will let you know. Regards Michel Thank you and best regards, Zoilo. = Zoilo Gomez wrote: rest removed because of size This my 3rd try but had the to address wrong the first two times. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mantis and MB86A16 (VP-1034) and DiseqC commands not working.
Zoilo Gomez schreef:
Hi Michel,
Michel Verbraak wrote:
Zoilo Gomez schreef:
I am also at loss now
Michel: can you confirm that DiSEqC is working for you using the
Mantis driver? Are you 100% that it is DiSEqC that is doing the
work, and not some conventional compatibility function like
18/13V+22kHz etc (which initially fooled me to believe that DiSEqC
was working)?
Manu: a couple of emails ago, you wrote that you were puzzled how
the code could ever have worked, and came up with some changes ... ?
What I made from this is that you had found some quirks in the
register settings (but perhaps i completely misunderstood you).
Looks like I must go and borrow an oscilloscope somehow, so I can
measure what is going on at the coax level ...
The driver does send diseqc commands. Because I control my rotor with
DiseqC 1.2 gotox commands. Have a look at my gotox program. I posted
a bit earlier about it. It uses the dvb api which is in dvb-apps at
linuxtv.org
So I understand that what you are saying is that your driver is
sending DiSEqC commands, *but you are not using them, so you cannot
sure that they work*, correct?
Instead you are controlling your rotor with a separate program, that
is not using the Mantis driver, correct?
No, my gotox program is using an API and the API is using the Mantis
driver to send out the DiseqC message. I also have another program which
does not use the API but talks directly to the Mantis driver. It talks
to the /dev/dvb/adapter0/frontend0 device with ioctl calls. The
following is an example:
int TDVBSDevice::SendRotorMoveCommand(float angle)
{
int ret = 0;
struct dvb_diseqc_master_cmd diseqc_message;
int integer = (int) angle;
uint8_t data[] = { *0xE0, 0x31, 0x6e, 0x00, 0x00*};
// transform the fraction into the correct representation
int fraction = (int) (((angle - integer) * 16.0) + 0.9) 0x0f;
switch(fraction) {
case 1:
case 4:
case 7:
case 9:
case 12:
case 15:
fraction--;
break;
}
// generate the command
if (integer 0.0) {
data[3] = 0xD0; // West is a negative angle value
} else if (integer = 0.0) {
data[3] = 0xE0; // East is a positive angle value
}
integer = abs(integer);
data[3] |= ((integer / 16) 0x0f);
integer = integer % 16;
data[4] |= ((integer 0x0f) 4) | fraction;
diseqc_message.msg_len = 5;
memcpy(diseqc_message.msg, data, 5);
ret = *ioctl(vfrontendfd, FE_DISEQC_SEND_MASTER_CMD, diseqc_message);*
if (ret == -1)
syslog(LOG_ERR, rotor_goto_bearing: IOCTL failed);
else
ret = 0;
return ret;
}
I really use the Mantis driver and as you can see I specify the complete
DiseqC command, see uint8_t data[] = { *0xE0, 0x31, 0x6e, 0x00,
0x00*};, to send not the driver. The example above is the same as used
by the API internally.
Michel
Z.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mantis and MB86A16 (VP-1034) and DiseqC commands not working.
Zoilo Gomez schreef: Michel Verbraak wrote: Zoilo, Which program are you using and does the setting of your switch? dvbtune (slightly modified because DiSEqC implementation of dvbtune-0.5 contains a bug, see my emails about this a couple of days ago) and also szap. With KNC1 DVB-S (stv2099 driver) these utils work perfectly, but VP1034 (mb86a16 driver) does *not* work. Z. Will have a look into this. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mantis driver with ivtv
joep admiraal schreef: Hello, I downloaded the mantis file from http://jusst.de/manu/mantis-v4l-dvb.tar.bz2. and used Marko's patch. I can watch FTA channels. The next step is to get my hauppauge 350 working again. It worked fine with ivtv 10.1 but since I installed v4l-dvb it doesn't work anymore. I also downloaded the latest v4l-dvb from cvs. It appears that ivtv is merged into v4l-dvb. When I install that one ivtv is also working. However there's no mantis driver in that one. So now I have 2 versions of v4l-dvb. One with support for the 1034 and the other one with support for the hauppauge 350. Can someone please tell me how I can use both cards at the same time? b.t.w. Great you are all still working on the mantis driver. Can't wait to try the CI when it's ready :) Thanx, Joep ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Joep, Have a look at my mini howto http://www.verbraak.org/wiki/index.php/Linux_Mantis_driver In this I explain how I did it. Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mantis and MB86A16 (VP-1034) and DiseqC commands not working.
Zoilo Gomez schreef: Manu Abraham wrote: Zoilo Gomez wrote: Manu Abraham wrote: Zoilo Gomez wrote: Manu Abraham wrote: Michel Verbraak wrote: Manu, list, SNIP Freq+symrate is correct; I tried several freqs / pols / symbol rates on sat=2. I am quite sure that the problem is simple and diseqc related, for the several reasons: = my normal sat receiver is working fine on all 16 sat feeds (4*4) = KNC1 DVB-C is also working fine on all sats / pols / bands; the fact that it is capable to select different sats proves that its diseqc commands are working. = however VP1034 is working only on first satellite (out of 4). This seems to be caused by 18/13V+22kHz signaling (not diseqc), which is applied simultaneously with the diseqc command. However, switching to a different sat is impossible, because diseqc is not working. In fact, if I use the very same freq+pol+symrate, but only change the sat number (f.e. sat=2 of sat=3), I get the exact same transport stream from sat=1. So no sat switching occurs, hence diseqc is apparently not working, and 18/13V+22kHz must be responsible for pol+band selection. Can't see the bug from a quick glance, will take a look at it, these days. Please let me know where I can help. Z. Zoilo and Manu, DiseqC is working for me with my own programs and the patch i made for libdvbsec. I only use the GotoX function. Not preprogrammed positions. When I have time again I will have a look into this. When I tried the latest version of kaffeine, it now supports rotors, it was not able to rotate my rotor with kaffeine. I did not yet spend time to look into this because my own software still works. I can send you a small c-program which I made to rotate the rotor, by angle, I can send it or make it available trough a website. Please let me know. It uses my patched libdvbsec. As far as I know my patch is not implemented yet (do not know why). Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Fwd: Mantis gpio_set_bits() fix]
Marko, Did not have time yet to find out. Next weekend I will have a look into it and report back. Regards, Michel. Marko Ristola schreef: Hi Michel, Great that the fix helped you. The last problem might well be with the card, because those channels don't work under Windows either. Do you have any clue that how those channels differ from the ones that you find with a scan? Astra might have details of their channels in their Website. Here in Finland on some cards DVB text works under Linux, but not under Windows. Extracting text from TS is done in software. Regards, Marko Ristola Michel Verbraak kirjoitti: Marko Ristola schreef: Onderwerp: Mantis gpio_set_bits() fix Van: Marko Ristola [EMAIL PROTECTED] Datum: Sat, 17 Mar 2007 11:14:08 +0200 Aan: Manu Abraham [EMAIL PROTECTED] Aan: Manu Abraham [EMAIL PROTECTED] Hi Manu, Here is a bugfix for gpio_set_bits(). What do you think about this bugfix? The bug is that the function is only able to turn the given bit on, but it can never turn a bit off. My patch fixes that issue. With my patched version gpio_set_bits is able to turn a single bit on or off. I haven't verified that it actually does turn the device's power off when requested. I tested only rmmod and insmod. It seems to work with this version: I haven't seen a lost frontend. Regards, Marko Ristola This patch solves also the modulation change problem (18v or 13v). I can now receive and scan the same channels as the Windows driver is capable of. I still have the problem that the driver cannot tune to all available channels on a satellite. The windows driver has the same problem. Could this be a problem of the card? Regards, Michel. ___ 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] [Fwd: Mantis gpio_set_bits() fix]
Marko Ristola schreef: Onderwerp: Mantis gpio_set_bits() fix Van: Marko Ristola [EMAIL PROTECTED] Datum: Sat, 17 Mar 2007 11:14:08 +0200 Aan: Manu Abraham [EMAIL PROTECTED] Aan: Manu Abraham [EMAIL PROTECTED] Hi Manu, Here is a bugfix for gpio_set_bits(). What do you think about this bugfix? The bug is that the function is only able to turn the given bit on, but it can never turn a bit off. My patch fixes that issue. With my patched version gpio_set_bits is able to turn a single bit on or off. I haven't verified that it actually does turn the device's power off when requested. I tested only rmmod and insmod. It seems to work with this version: I haven't seen a lost frontend. Regards, Marko Ristola This patch solves also the modulation change problem (18v or 13v). I can now receive and scan the same channels as the Windows driver is capable of. I still have the problem that the driver cannot tune to all available channels on a satellite. The windows driver has the same problem. Could this be a problem of the card? Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] bug in szap-utility
Uwe Bugla schreef: Hi folks, as part of the Debain package dvb-utils 1.1.1-2 the szap utility has the following bug: 1. The start transponder file of Eutelsat Hotbird13.0E contains a H as description of the polarization. 2. Unfortunately this H is being interpreted as V. 3. So if you try to produce a transponder list with the start transponder you are trapped as nothing works! To see the error yourself, try the following example in the console: szap -r -a0 -c trapz.txt -n1 where trapz.txt looks like this: Hotbird-13.0E:12539:H:1:27500 With which program did you create the trapz.txt file? My scan or scandvb program creates only lower cases polarization characters (v or h). I think the szap program only recognizes lowercase by design. In the console you will see the right frequency and the right symbol rate. But the polarization will be printed out as V (vertical) instead of H (horizontal). In other words: The bug is: szap cannot set equal the letter h with the letter H Regards Uwe P. S.: I solved the problem by a TCL-TK workaround, but it rather should be solved in the sourcecode, shouldn't it? So can someone reading this please fix that bug in the source code? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Is Twinhan Sat-CI 1034 working?
[EMAIL PROTECTED] schreef: On Mon, 26 Feb 2007, Michel Verbraak wrote: Is Twinhan Sat-CI 1034 working? Yes, The driver is currently in Alpha state. Look at the archives of this mailing list. The CI slot is currently not working. hm maybe, missing something, but I was unable to find a driver... can You redirect me there? and, also, is there any documentation for the chip, or it is a kind of blind development? Look at http://kromtek.com/dvb. It is the mantis driver. And there have been multiple posting on this list about this driver in combination with the vp-1034. Look form my name or for Manu Abraham who is currently developing the driver. Manu probably has papers but I think he is working under NDA (non disclosure agreement). Happy searching and testing. Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Kenerl 2.6.20, mantis and vp-1034
Manu Abraham schreef: On 2/23/07, Michel Verbraak [EMAIL PROTECTED] wrote: 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. Sorry for the delayed mail, somehow it skipped my eye. Did quite a bit of work and ported the mantis tree .. http://kromtek.com/dvb/mantis-v4l-dvb.tar.bz2 that warning, what you saw is fine, it came in after the i2c changes in .20. It is fixed in the tree that i have put at the URL above. diseqc stuff shouldn't be a problem though. Would be interesting to know how it goes at your side. regards, manu Manu, I will test this version tonight and report back. My rotor is working fine I discovered a small bug in my own software. When this was fixed I could rotate the dish without problems. Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Kenerl 2.6.20, mantis and vp-1034
Michel Verbraak schreef: Manu Abraham schreef: On 2/23/07, Michel Verbraak [EMAIL PROTECTED] wrote: 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. Sorry for the delayed mail, somehow it skipped my eye. Did quite a bit of work and ported the mantis tree .. http://kromtek.com/dvb/mantis-v4l-dvb.tar.bz2 that warning, what you saw is fine, it came in after the i2c changes in .20. It is fixed in the tree that i have put at the URL above. diseqc stuff shouldn't be a problem though. Would be interesting to know how it goes at your side. regards, manu Manu, I will test this version tonight and report back. My rotor is working fine I discovered a small bug in my own software. When this was fixed I could rotate the dish without problems. Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Manu, The 24th of february 2007 version works allright for me. Following in messagelog: ACPI: PCI Interrupt :02:05.0[A] - Link [LNKB] - GSI 19 (level, low) - IRQ 19 irq: 19, latency: 32 memory: 0xf68ff000, mmio: 0xc202e000 found a VP-1034 PCI DVB-S/DSS device on (02:05.0), Mantis Rev 1 [1822:0014], irq: 19, latency: 32 memory: 0xf68ff000, mmio: 0xc202e000 MAC Address=[00:08:ca:19:9f:0b] mantis_alloc_buffers (0): DMA=0xde5 cpu=0x81000de5 size=65536 mantis_alloc_buffers (0): RISC=0x30a04000 cpu=0x810030a04000 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)... Rotor is working allright so DiseqC is transfered normal. I merged only the mantis part into my kernel sources. This is a x86_64 kernel. What should be the differences to the previous version? I did not yet try a scan for the missing channels to see if they are visible right now because my dish needs reallignement, reception is poort, after a storm a few weeks ago and currently it is pooring rain here so I was not able to get on my roof. Regards, Michel. ___ 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] [BUG]: Mantis + VP-1034 driver lock up machine
As previous reported by me I had sometimes problems of my machine locking up probably by the driver. This morning I experienced the same type of crash and had a tail -f /var/log/messages running and saw the following appear: Jan 17 06:54:37 garfield kernel: mantis start feed dma Jan 17 06:54:47 garfield kernel: BUG: soft lockup detected on CPU#0! Jan 17 06:54:47 garfield kernel: [c040510b] dump_trace+0x69/0x1af Jan 17 06:54:47 garfield kernel: [c0405269] show_trace_log_lvl+0x18/0x2c Jan 17 06:54:47 garfield kernel: [c040581c] show_trace+0xf/0x11 Jan 17 06:54:47 garfield kernel: [c0405916] dump_stack+0x15/0x17 Jan 17 06:54:47 garfield kernel: [c044b1c1] softlockup_tick+0xad/0xc4 Jan 17 06:54:47 garfield kernel: [c042e279] update_process_times+0x39/0x5c Jan 17 06:54:47 garfield kernel: [c0418912] smp_apic_timer_interrupt+0x5b/0x61 Jan 17 06:54:47 garfield kernel: [c0404a0f] apic_timer_interrupt+0x1f/0x24 Jan 17 06:54:47 garfield kernel: DWARF2 unwinder stuck at apic_timer_interrupt+0x1f/0x24 Jan 17 06:54:47 garfield kernel: Leftover inexact backtrace: Jan 17 06:54:47 garfield kernel: [f8a1320a] mb86a16_set_frontend+0x433/0x1c3d [mb86a16] Jan 17 06:54:47 garfield kernel: [c042dfbb] del_timer_sync+0xa/0x14 Jan 17 06:54:47 garfield kernel: [c060c3a1] schedule_timeout+0x82/0x96 Jan 17 06:54:47 garfield kernel: [c060d4e8] _spin_lock_irqsave+0x9/0xd Jan 17 06:54:47 garfield kernel: [f8a12dd7] mb86a16_set_frontend+0x0/0x1c3d [mb86a16] Jan 17 06:54:47 garfield kernel: [f89887cb] dvb_frontend_thread+0x239/0x2dc [dvb_core] Jan 17 06:54:47 garfield kernel: [c0436974] autoremove_wake_function+0x0/0x35 Jan 17 06:54:47 garfield kernel: [f8988592] dvb_frontend_thread+0x0/0x2dc [dvb_core] Jan 17 06:54:47 garfield kernel: [c0404ce7] kernel_thread_helper+0x7/0x10 Jan 17 06:54:47 garfield kernel: === This was about 20 seconds after a proces of mine opened one handle to the frontend device and two handles to the demux device and the only ioctl issued was FE_GET_FRONTEND to the frontend device. I wil try to get some more logging tonight. Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
RE: [linux-dvb] [BUG]: Mantis + VP-1034 driver lock up machine
Hi Michel. I've just got a 1034 card but haven't been able to connect to thadathil.net in order to download the driver source. Would it be possible for you to make a tarball of the code you have and put it somewhere I could download it? Thanks, -jgs _ Advertisement: Fresh jobs daily. Stop waiting for the newspaper. Search Now! www.seek.com.au http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau_t=757263760_r=Hotmail_EndText_Dec06_m=EXT I put a copy of the Mantis driver on my website http://www.verbraak.org. It is the latest version I was able to download. Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] State of TwinhanDTV Sat-CI VP-1034 support
Cedric Roijakkers schreef: Hi All, I'm looking into building a MythTV-based HTPC at the moment. I would like to view digital satellite channels, and I'm looking into the hardware now. I would like to view the TV Vlaanderen (CanaDigitaal sister company in Belgium) encrypted channels, so I'll require a card with a CI slot and a CAM. TV Vlaanderen sells its own CAMs, so I'll go for one of those. But the PCI card is the one I'm asking about. I was planning on going for a TwinhanDTV Sat-CI VP-1034, Mantis-based card. What is the current support status in the Linux kernel for this card? Does it work at all, and does it work with crypted channels? Currently the driver for the TwinhanDTV Mantis cards is in alpha phase. Currently tuning and channel viewing works but not all channels are found on the satellite. The CI slot is currently not supported so encrypted channels are not viewable. Work is currently going on to get CI support and to get the missing channels back. Or do you have any suggestions for other cards that will do the trick in Linux? And if possible a reseller of those via mail order in Belgium or the Netherlands? I bought mine through www.factoryprices.nl (www.factoryprices.be) but they do not sell it anymore. Greets Cedric ___ 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] Re: Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033
Joep, Within windows with the Twinhan Software scanning for the dutch channels does not work either. It does not find any dutch channels. Regards, Michel. (Still working to get it working on my fc5) joep admiraal schreef: I installed Kaffeine from source today. It appeared that the version I was using didn't have dvb support :) So now I can do a channel scan with Kaffeine. It does find the same channels I get with dvb-scan or mythtv. I don't have to reboot after each transponder with Kaffeine. However it does not find the dutch channels wich are all on the horizontal (18v) channels. Am I the only one who is trying to use this driver with a dvb-s card and horizontal transponders? Op zaterdag 11 november 2006 08:38, schreef Marko Ristola: The MythTV single TS scanning problem might be on MythTV, not on the driver. I can repeat that with Kaffeine: If I watch a channel during a scan, I can get only channels from one TS. If I stop watching the channel, scanning finds channels from multiple TS. With Finnish file fi-HTV (C 27400 690 AUTO QAM128 for kaffeine) that TS contains information from other frequencies also. So after scanning that TS, it changes frequency until all TSes are scanned. I use cu1216. Ealier I had also some reboot problems with scanning. Now I don't have them anymore. I have now a newer kaffeine, but the mantis driver hasn't changed. The latest kaffeine works fine on Livna repository. The patches that I sent are enough for me. This is the last problem that I have: When I do the following commands by hand: #rmmod mantis #rmmod cu1216 #modprobe mantis dmesg: DVB: registering new adapter (Mantis dvb adapter). mantis_frontend_init (1): Probing for CU1216 (DVB-C) mantis_frontend_init (1): !!! NO Frontends found !!! Now the only fix that I know is to do a reboot. I never need to remove mantis driver though. I haven't tested suspending the computer at all. Regards, Marko Ristola Michel Verbraak wrote: joep admiraal schreef: Hello Michel, I am using the same file you are. It contains the same info as your's. After I do a reboot it does find some channels. Before I applied the patch it did find channels on a few transponders. Now it only finds channels on the first transponder. I am doing some tests with Mythtv now. From mythtv I can also scan for channels. It generates a list of tranponders and I can perform a scan per transponder. So I do a scan and after that I do a reboot so I can scan the next transponder. This seems to work for all vertical transponders. For some reason it gives me timeout's for all the horizontal transponders. Looks like a lot of work to reboot every time. Manu any solutions? I know it is still Alpha release. regards, joep Op dinsdag 7 november 2006 17:52, schreef Michel Verbraak: Joep, What is the content of the file you are using to test your scan, even if it only does one transponder. I'm testing with the default one and only get the following result: scanning /usr/share/dvb-apps/dvb-s/Astra-19.2E using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 12551500 V 2200 5 tune to: 12551:v:0:22000 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 dumping lists (0 services) Done. Content of the Astra-19.2E file is: # Astra 19.2E SDT info service transponder # freq pol sr fec S 12551500 V 2200 5/6 Regards, Michel. joep admiraal schreef: Thanx! I can watch the channels from my channels.conf with super picture quality. Only the channel scanning doesn't work yet. It now only finds channels from the 1st transponder, after that is just gives timeout's. Is there anyone on this list that has the channels from canaldigitaal (the netherlands) in his/her channels.conf? If so, please send a copy to me :) Thanx Joep ___ 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 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 mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033
Joep, What is the content of the file you are using to test your scan, even if it only does one transponder. I'm testing with the default one and only get the following result: scanning /usr/share/dvb-apps/dvb-s/Astra-19.2E using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 12551500 V 2200 5 tune to: 12551:v:0:22000 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 dumping lists (0 services) Done. Content of the Astra-19.2E file is: # Astra 19.2E SDT info service transponder # freq pol sr fec S 12551500 V 2200 5/6 Regards, Michel. joep admiraal schreef: Thanx! I can watch the channels from my channels.conf with super picture quality. Only the channel scanning doesn't work yet. It now only finds channels from the 1st transponder, after that is just gives timeout's. Is there anyone on this list that has the channels from canaldigitaal (the netherlands) in his/her channels.conf? If so, please send a copy to me :) Thanx Joep ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033
joep admiraal schreef: Hello Michel, I am using the same file you are. It contains the same info as your's. After I do a reboot it does find some channels. Before I applied the patch it did find channels on a few transponders. Now it only finds channels on the first transponder. I am doing some tests with Mythtv now. From mythtv I can also scan for channels. It generates a list of tranponders and I can perform a scan per transponder. So I do a scan and after that I do a reboot so I can scan the next transponder. This seems to work for all vertical transponders. For some reason it gives me timeout's for all the horizontal transponders. Looks like a lot of work to reboot every time. Manu any solutions? I know it is still Alpha release. regards, joep Op dinsdag 7 november 2006 17:52, schreef Michel Verbraak: Joep, What is the content of the file you are using to test your scan, even if it only does one transponder. I'm testing with the default one and only get the following result: scanning /usr/share/dvb-apps/dvb-s/Astra-19.2E using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 12551500 V 2200 5 tune to: 12551:v:0:22000 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 dumping lists (0 services) Done. Content of the Astra-19.2E file is: # Astra 19.2E SDT info service transponder # freq pol sr fec S 12551500 V 2200 5/6 Regards, Michel. joep admiraal schreef: Thanx! I can watch the channels from my channels.conf with super picture quality. Only the channel scanning doesn't work yet. It now only finds channels from the 1st transponder, after that is just gives timeout's. Is there anyone on this list that has the channels from canaldigitaal (the netherlands) in his/her channels.conf? If so, please send a copy to me :) Thanx Joep ___ 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] Re: Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033
joep admiraal schreef: Hello I have a Twinhan 1034 dvb-s card. A modprobe mantis goes fine. When I do "dvbcan mychannel channel.conf" I get the following output: -- scanning mychannel using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 12324000 V 2750 5 tune to: 12324:v:0:27500 WARNING: tuning failed!!! tune to: 12324:v:0:27500 (tuning failed) WARNING: tuning failed!!! ERROR: initial tuning failed -- I have attached the output of dmesg to this email. When I use the Windows software that came with the card I can tune into the channel that I put into the file 'mychannel'. Do you have an idea of what I am doing wrong? Thanks, Joep Admiraal Joep, I get the same results. I did not yet report anything to the list because I have a motor in between which could also couse my problems. So i'm also still testing. Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033
joep admiraal schreef: Hello I have a Twinhan 1034 dvb-s card. A modprobe mantis goes fine. When I do "dvbcan mychannel channel.conf" I get the following output: -- scanning mychannel using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 12324000 V 2750 5 tune to: 12324:v:0:27500 WARNING: tuning failed!!! tune to: 12324:v:0:27500 (tuning failed) WARNING: tuning failed!!! ERROR: initial tuning failed -- I have attached the output of dmesg to this email. When I use the Windows software that came with the card I can tune into the channel that I put into the file 'mychannel'. Do you have an idea of what I am doing wrong? Thanks, Joep Admiraal Joep, I get the same results. I did not yet report anything to the list because I have a motor in between which could also couse my problems. So i'm also still testing. Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033
joep admiraal schreef: Hello I downloaded the code from Manu. It compiled without any problems. When I do a modprobe mantis I get the following message: Error inserting mantis (/lib/modules/2.6.16.21-0.13-default/kernel/drivers/media/dvb/mantis/mantis.ko): Unknown symbol in module, or unknown parameter (see dmesg) dmesg gives me: mantis: Unknown symbol cu1216_attach Joep, The cu1216.ko module needs to be copied by hand to the modules directory /lib/moduleskernel version/kernel/drivers/media/dvb/frontends Copy it from the directory /mantis-25021de30f36/v4l. Does anyone knows what I could be doing wrong? Thanks, Joep Admiraal ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Regards, Michel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033
Joep, After the copy do not forget to do the depmod -a command as root. Michel. Michel Verbraak schreef: joep admiraal schreef: Hello I downloaded the code from Manu. It compiled without any problems. When I do a modprobe mantis I get the following message: Error inserting mantis (/lib/modules/2.6.16.21-0.13-default/kernel/drivers/media/dvb/mantis/mantis.ko): Unknown symbol in module, or unknown parameter (see dmesg) dmesg gives me: mantis: Unknown symbol cu1216_attach Joep, The cu1216.ko module needs to be copied by hand to the modules directory /lib/moduleskernel version/kernel/drivers/media/dvb/frontends Copy it from the directory /mantis-25021de30f36/v4l. Does anyone knows what I could be doing wrong? Thanks, Joep Admiraal ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Regards, Michel. ___ 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] Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033
Manu, Thanks for the first preview. I compiled the driver without problems, only the know dvb_net problem on FC5 kernel 2.6.17. As Jens allready wrote I had to copy the cu1216.ko module by hand to the right modules location. I have a VP-1034. A modprobe mantis gives me the following in dmesg: ACPI: PCI Interrupt :02:0d.0[A] - GSI 21 (level, low) - IRQ 217 Mantis Rev 1, irq: 217, latency: 64 memory: 0xf7eff000, mmio: 0xf8902000 get_mac_address (1): MAC Address=[00:08:ca:19:9f:0b] get_subvendor_id (1): Sub Vendor ID=[0x1822] get_subdevice_id (1): Sub Device ID=[0x0014] mantis_alloc_buffers (1): DMA=0x32ce cpu=0xf2ce size=65536 mantis_alloc_buffers (1): RISC=0xec51000 cpu=0xcec51000 size=1000 DVB: registering new adapter (Mantis dvb adapter). mantis_frontend_init (1): Probing for MB86A16 (DVB-S/DSS) mantis_frontend_init (1): found MB86A16 DVB-S/DSS frontend @0x08 DVB: registering frontend 0 (Fujitsu MB86A16 DVB-S)... It created the /dev/dvb/adapter0/(demux0 dvr0 frontend0 net0) devices. lspci -vv gives 02:0d.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01) Subsystem: Twinhan Technology Co. Ltd Unknown device 0014 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (2000ns min, 63750ns max) Interrupt: pin A routed to IRQ 217 Region 0: Memory at f7eff000 (32-bit, prefetchable) [size=4K] I will try to test it with different programs. Does the driver also handle a diseqc motor ? Regards, Michel. Manu Abraham schreef: Hi All, I have uploaded a preview for the Mantis based cards (VP-1027 / VP-1033 / VP-1034 / VP-2033 / VP-3033) The update contains a new PCI bridge called the Mantis and 2 frontends as well The MB86A16 is a Direct Conversion DVB-S / DSS receiver, which requires no external components, for functionality. It does have a lot of features, but in the preview, due to a whole lot of changes and a complex driver for the same, i was forced to do a minimal driver for the same. The Mantis PCI bridge can handle 4 different CA slots (according to the specs) but the cards that are out there have just one CA slot alone. I haven't yet finished on the CA part of the Mantis, the snapshot provides a stable snapshot, without the CA parts. The CA part will take some more time before a preview/release I have currently tested only the VP-1034, with some amount of success. Proper support on the VP-3033 is still pending The VP-1040/VP-1041 DVB-S2 cards are not supported by this tree, but will be supported a while later. Due to large span, the relevant work could be hard to get going for many and could have many bugs. It is not at all for the faint hearted at this point of time. It would be nice to have some feedback on this. http://thadathil.net:8000/cgi-bin/hgwebdir.cgi/mantis http://thadathil.net:8000/cgi-bin/hgwebdir.cgi/mantis?ca=tip;type=bz2 Thanks, Manu ___ 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] Twinhan Sat-CI 1034 v1.2 Is there any progress?
On juli 20th there was some conversation going on about the Twinhan Sat-CI 1034 v1.2 card. The conversation was about that there is not yet support for this card in linux dvb but Manu Abraham said it would take probably some weeks. Is there any repository allready available with some work for this card or is no one yet working on it. I have such a card and would like to help to develop the driver. I am not a driver developer but I do have programming experience and am willing to do testing. Regards, Michel. Info about the chips on the card: Twinhan 1034 ver1.2 board One chip with text: Japan MB86A16L D610 K0B E1 (Is a Fujitsu Tuner and Decoder in one) Could not find detailed specs yet only what it should be capable of. And one: Mantis K61468.2A-2 041213 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan Sat-CI 1034 v1.2 Is there any progress?
Thanks for the answer. Looking forward for the first examples. Regards, Michel. Manu Abraham schreef: Michel Verbraak wrote: On juli 20th there was some conversation going on about the Twinhan Sat-CI 1034 v1.2 card. The conversation was about that there is not yet support for this card in linux dvb but Manu Abraham said it would take probably some weeks. Is there any repository allready available with some work for this card or is no one yet working on it. Work is going on. This device is a bit different from other frontends (It is a DC receiver and lot of strange things it brings along). Repository is not available yet. It is not only the frontend that is different for this card, but the PCI bridge and everything is completely new. I have such a card and would like to help to develop the driver. I am not a driver developer but I do have programming experience and am willing to do testing. Have couple of cards here CA and FTA types, work still in progress. Current status is that PCI bridge is done and work is going on with the frontends. Lot of new cards, with the same PCI bridge. Manu ___ 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
