Slovenia DVB-T scan
Hi! I noticed there isn't yet a tuning file for Slovenia so I'm giving you info on our receivers (scanned with w_scan): # Slovenia / Ljubljana # MULTIPLEX A #-- T 60200 8MHz 2/3 NONE QAM64 8k 1/4 NONE T 51400 8MHz 2/3 NONE QAM64 8k 1/8 NONE Regards, Aljaz -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: technisat cablestar hd2, 2.6.33-rc5, no remote (VP2040)
Hi Manu, I'm sorry to bother you with this one, but I'd really like to know if there's something I'm doing wrong or is there something more I can provide on this one. Below are some results from the newest kernel RC, while sometime back I also posted some more debug info. I just noticed that someone else also reported the same problem: http://www.spinics.net/lists/linux-media/msg14332.html Thanks in advance for any info. Regards, Aljaz On pet, 2010-01-22 at 21:57 +0100, Aljaž Prusnik wrote: Hi! I tried 2.6.33-rc5 kernel hoping to get the remote working, but it's the same behaviour as in my previous posts. TV reception works, however there's no VP2040 to be noticed anywhere in the logs. The device used to be detected like this: I: Bus=0001 Vendor= Product= Version=0001 N: Name=Mantis VP-2040 IR Receiver P: Phys=pci-:03:06.0/ir0 S: Sysfs=/devices/virtual/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=13 B: KEY=108fc330 2842041 0 200018000 21804801 9e96c0 ffc but now, this does not happen anymore. Any ideas? Below are some outputs of the current situation: mantis modules: $ lsmod | grep mantis mantis 14728 0 mantis_core23909 18 mantis ir_common 26893 1 mantis_core ir_core 3906 2 mantis_core,ir_common mb86a1616598 1 mantis tda100214822 1 mantis tda100235823 1 mantis zl10353 5893 1 mantis stv0299 7860 1 mantis dvb_core 77233 2 mantis_core,stv0299 devices (no mantis 2040 anywhere): $ cat /proc/bus/input/devices I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name=AT Translated Set 2 keyboard P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input0 U: Uniq= H: Handlers=kbd event0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: EV=3 B: KEY=10 0 I: Bus=0010 Vendor=001f Product=0001 Version=0100 N: Name=PC Speaker P: Phys=isa0061/input0 S: Sysfs=/devices/platform/pcspkr/input/input3 U: Uniq= H: Handlers=kbd event3 B: EV=40001 B: SND=6 I: Bus=0003 Vendor=03f0 Product=041d Version=0110 N: Name=Hewlett-Packard HP USB Travel Mouse P: Phys=usb-:00:12.1-1/input0 S: Sysfs=/devices/pci:00/:00:12.1/usb4/4-1/4-1:1.0/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0001 Vendor=10ec Product=0887 Version=0001 N: Name=HDA Digital PCBeep P: Phys=card0/codec#0/beep0 S: Sysfs=/devices/pci:00/:00:14.2/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=40001 B: SND=6 Regards, Aljaz Prusnik -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Which modules for the VP-2033? Where is the module mantis.ko?
Hi! Still no change regarding regaining IR support for VP2040 device. Despite successfully loading the module from Abraham's tree and starting the UART, I still do not see the input device that I can use with lirc. I tried both trees: today's Liplianin tree, dmesg on loading the mantis module: ir_common: Unknown symbol ir_g_keycode_from_table ir_common: Unknown symbol ir_core_debug today's Abraham's tree, dmesg on loading the mantis modulem verbose=5: the result is still the same as the last time I wrote about it (no input device is registered, despite successful uart initialization). -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Which modules for the VP-2033? Where is the module mantis.ko?
On pon, 2009-12-28 at 21:06 +0100, Aljaž Prusnik wrote: On pon, 2009-12-28 at 20:28 +0100, Aljaž Prusnik wrote: On pon, 2009-12-28 at 02:23 +0400, Manu Abraham wrote: Can you please do a lspci -vn for the Mantis card you have ? Also try loading the mantis.ko module with verbose=5 module parameter, to get more debug information. To continue, it seems the module is registering the remote commands, but dunno, why irw shows nothing: Well - to answer myself on this one, it doesn't because there is no input device registered. I used to have this under input devices (cat /proc/bus/input/devices): I: Bus=0001 Vendor= Product= Version=0001 N: Name=Mantis VP-2040 IR Receiver P: Phys=pci-:03:06.0/ir0 S: Sysfs=/devices/virtual/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=13 B: KEY=108fc330 2842041 0 200018000 21804801 9e96c0 ffc So the question is, why is it not registered as an input anymore? Regards, Aljaz -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Which modules for the VP-2033? Where is the module mantis.ko?
On pon, 2009-12-28 at 02:23 +0400, Manu Abraham wrote: Can you please do a lspci -vn for the Mantis card you have ? Also try loading the mantis.ko module with verbose=5 module parameter, to get more debug information. $ lspci -vn 03:07.0 0480: 1822:4e35 (rev 01) Subsystem: 1ae4:0002 Flags: bus master, medium devsel, latency 32, IRQ 21 Memory at fdcff000 (32-bit, prefetchable) [size=4K] Kernel driver in use: Mantis $ modprobe -v mantis verbose=5 insmod /lib/modules/2.6.33-rc1/kernel/drivers/media/dvb/mantis/mantis_core.ko insmod /lib/modules/2.6.33-rc1/kernel/drivers/media/dvb/mantis/mantis.ko verbose=5 $ dmesg [ 2371.762511] Mantis :03:07.0: PCI INT A disabled [ 2462.703393] Mantis :03:07.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [ 2462.704761] DVB: registering new adapter (Mantis DVB adapter) [ 2463.563234] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... [ 2522.842548] Mantis :03:07.0: PCI INT A disabled [ 2534.495759] found a VP-2040 PCI DVB-C device on (03:07.0), [ 2534.495771] Mantis :03:07.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [ 2534.495796] Mantis Rev 1 [1ae4:0002], irq: 21, latency: 32 [ 2534.495799] memory: 0x0, mmio: 0xc900128cc000 [ 2534.495818] mantis_stream_control (0): Set stream to HIF [ 2534.495841] mantis_i2c_init (0): Initializing I2C .. [ 2534.495845] mantis_i2c_init (0): Disabling I2C interrupt [ 2534.495849] mantis_i2c_xfer (0): Messages:2 [ 2534.495852] mantis_i2c_write: Address=[0x50] W[ 08 ] [ 2534.496243] mantis_i2c_read: Address=[0x50] R[ 00 08 c9 d0 02 09 ] [ 2534.497049] MAC Address=[00:08:c9:d0:02:09] [ 2534.497051] mantis_dma_init (0): Mantis DMA init [ 2534.497071] mantis_alloc_buffers (0): DMA=0x3d67 cpu=0x88003d67 size=65536 [ 2534.497073] mantis_alloc_buffers (0): RISC=0x3b731000 cpu=0x88003b731000 size=1000 [ 2534.497076] mantis_calc_lines (0): Mantis RISC block bytes=[4096], line bytes=[2048], line count=[32] [ 2534.497077] mantis_dvb_init (0): dvb_register_adapter [ 2534.497079] DVB: registering new adapter (Mantis DVB adapter) [ 2534.497081] mantis_dvb_init (0): dvb_dmx_init [ 2534.497166] mantis_dvb_init (0): dvb_dmxdev_init [ 2534.497269] mantis_frontend_power (0): Power ON [ 2534.497271] gpio_set_bits (0): Set Bit 12 to 1 [ 2534.497274] gpio_set_bits (0): GPIO Value 3000 [ 2534.598099] gpio_set_bits (0): Set Bit 12 to 1 [ 2534.598111] gpio_set_bits (0): GPIO Value 3000 [ 2534.699066] mantis_frontend_soft_reset (0): Frontend RESET [ 2534.699077] gpio_set_bits (0): Set Bit 13 to 0 [ 2534.699085] gpio_set_bits (0): GPIO Value 1000 [ 2534.800077] gpio_set_bits (0): Set Bit 13 to 0 [ 2534.800087] gpio_set_bits (0): GPIO Value 1000 [ 2534.901079] gpio_set_bits (0): Set Bit 13 to 1 [ 2534.901089] gpio_set_bits (0): GPIO Value 3000 [ 2535.002089] gpio_set_bits (0): Set Bit 13 to 1 [ 2535.002099] gpio_set_bits (0): GPIO Value 3000 [ 2535.354084] vp2040_frontend_init (0): Probing for CU1216 (DVB-C) [ 2535.354096] mantis_i2c_xfer (0): Messages:2 [ 2535.354103] mantis_i2c_write: Address=[0x50] W[ ff ] [ 2535.354328] mantis_i2c_read: Address=[0x50] R[ e4 ] [ 2535.354555] mantis_i2c_xfer (0): Messages:2 [ 2535.354560] mantis_i2c_write: Address=[0x0c] W[ 1a ] [ 2535.354781] mantis_i2c_read: Address=[0x0c] R[ 7d ] [ 2535.355034] mantis_i2c_xfer (0): Messages:2 [ 2535.355039] mantis_i2c_write: Address=[0x50] W[ ff ] [ 2535.355257] mantis_i2c_read: Address=[0x50] R[ e4 ] [ 2535.355482] mantis_i2c_xfer (0): Messages:1 [ 2535.355486] mantis_i2c_write: Address=[0x0c] W[ 00 33 ] [ 2535.355819] mantis_i2c_xfer (0): Messages:2 [ 2535.355823] mantis_i2c_write: Address=[0x0c] W[ 1a ] [ 2535.356055] mantis_i2c_read: Address=[0x0c] R[ 7d ] [ 2535.356279] vp2040_frontend_init (0): found Philips CU1216 DVB-C frontend (TDA10023) @ 0x0c [ 2535.356285] vp2040_frontend_init (0): Mantis DVB-C Philips CU1216 frontend attach success [ 2535.356291] vp2040_frontend_init (0): Done! [ 2535.356298] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... [ 2535.356573] mantis_uart_init (0): Initializing UART @ 9600bps parity:NONE [ 2535.356602] mantis_uart_read (0): Reading ... 3f [ 2535.356609] mantis_uart_work (0): UART BUF:0 3f [ 2535.356613] [ 2535.356619] mantis_uart_init (0): UART succesfully initialized -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Which modules for the VP-2033? Where is the module mantis.ko?
On pon, 2009-12-28 at 20:28 +0100, Aljaž Prusnik wrote: On pon, 2009-12-28 at 02:23 +0400, Manu Abraham wrote: Can you please do a lspci -vn for the Mantis card you have ? Also try loading the mantis.ko module with verbose=5 module parameter, to get more debug information. To continue, it seems the module is registering the remote commands, but dunno, why irw shows nothing: dmesg of typing on remote: [ 4854.805594] mantis_uart_read (0): Reading ... 3d [ 4854.805605] mantis_uart_work (0): UART BUF:0 3d [ 4854.805609] [ 4854.805615] mantis_uart_read (0): Reading ... 3d [ 4854.805621] mantis_uart_work (0): UART BUF:0 3d [ 4854.805624] [ 4895.266923] [ 4895.266926] -- Stat=4000800 Mask=800 --IRQ-1 [ 4895.266956] [ 4895.266958] -- Stat=4000800 Mask=800 --IRQ-1 [ 4895.266979] [ 4895.266981] -- Stat=4000800 Mask=800 --IRQ-1 [ 4895.266999] [ 4895.267000] -- Stat=4000800 Mask=800 --IRQ-1 [ 4895.267015] [ 4895.267016] -- Stat=4000800 Mask=800 --IRQ-1 [ 4895.267031] [ 4895.267032] -- Stat=4000800 Mask=800 --IRQ-1 [ 4895.267043] mantis_uart_read (0): Reading ... 3e [ 4895.267054] mantis_uart_work (0): UART BUF:0 3e [ 4895.267058] [ 4895.267065] mantis_uart_read (0): Reading ... 3e [ 4895.267070] mantis_uart_work (0): UART BUF:0 3e -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Which modules for the VP-2033? Where is the module mantis.ko?
On čet, 2009-12-24 at 17:45 +0100, Ruediger Dohmhardt wrote: Aljaž, thanks for the reply. As Manu said above there was a build problem. As said already in this Thread, I downloaded version 2315248f648c, which compiles fine and has all modules for the 2033 DVB-C. I have the same version and it doesn't work for me. I have a 2040 module. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Which modules for the VP-2033? Where is the module mantis.ko?
In the same vein, I'm interested in this one, namely: I have tried the http://jusst.de/hg/v4l-dvb, since recently the liplianin mantis driver is not working (unknown symbols...). However, the problems I have as opposed to the previously working driver are: - the module does not install in a way it gets autoloaded on startup - I have to manually add it (modprobe) or put it into /etc/modules (debian) - while the card itself works, I don't have IR functionality anymore. From what I gather from the kernel log, the input line input: Mantis VP-2040 IR Receiver as /devices/virtual/input/input4 just doesn't exist anymore. Further more the whole bunch is missing: mantis_ca_init (0): Registering EN50221 device mantis_ca_init (0): Registered EN50221 device mantis_hif_init (0): Adapter(0) Initializing Mantis Host Interface input: Mantis VP-2040 IR Receiver as /devices/virtual/input/input4 Creating IR device irrcv0 I tried 2.6.32 kernel which worked before, now I'm using 2.6.33-rc1 where I had to comment out #include linux/autoconf.h the from the v4l-dvb/v4l/config-compat.h. Any ideas how to get the comfort back? ;) Regards, Aljaz -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Which modules for the VP-2033? Where is the module mantis.ko?
On sre, 2009-12-23 at 17:53 +0200, Igor M. Liplianin wrote: Since module ir-common.ko moved to IR directory just remove old one. rm /lib/modules/$(uname -r)/kernel/drivers/media/common/ir-common.ko Also it would be good to do make remove Then again build and install drivers. Ok. There was no common folder in the above path. Anyway, I did rm and make remove and did a new build (2.6.33-rc1). First, there were warnings: WARNING: ir_input_register [/mnt/storage/temp/technisat/s2-liplianin/v4l/saa7134.ko] undefined! WARNING: ir_input_unregister [/mnt/storage/temp/technisat/s2-liplianin/v4l/saa7134.ko] undefined! WARNING: ir_input_register [/mnt/storage/temp/technisat/s2-liplianin/v4l/mantis.ko] undefined! WARNING: ir_input_register [/mnt/storage/temp/technisat/s2-liplianin/v4l/ir-kbd-i2c.ko] undefined! WARNING: ir_input_unregister [/mnt/storage/temp/technisat/s2-liplianin/v4l/ir-kbd-i2c.ko] undefined! WARNING: ir_core_debug [/mnt/storage/temp/technisat/s2-liplianin/v4l/ir-common.ko] undefined! WARNING: ir_g_keycode_from_table [/mnt/storage/temp/technisat/s2-liplianin/v4l/ir-common.ko] undefined! WARNING: ir_input_register [/mnt/storage/temp/technisat/s2-liplianin/v4l/em28xx.ko] undefined! WARNING: ir_input_unregister [/mnt/storage/temp/technisat/s2-liplianin/v4l/em28xx.ko] undefined! WARNING: ir_input_register [/mnt/storage/temp/technisat/s2-liplianin/v4l/cx88xx.ko] undefined! WARNING: ir_input_unregister [/mnt/storage/temp/technisat/s2-liplianin/v4l/cx88xx.ko] undefined! WARNING: ir_input_register [/mnt/storage/temp/technisat/s2-liplianin/v4l/cx23885.ko] undefined! WARNING: ir_input_unregister [/mnt/storage/temp/technisat/s2-liplianin/v4l/cx23885.ko] undefined! WARNING: ir_input_register [/mnt/storage/temp/technisat/s2-liplianin/v4l/bttv.ko] undefined! WARNING: ir_input_unregister [/mnt/storage/temp/technisat/s2-liplianin/v4l/bttv.ko] undefined! Then I restarted the machine and this is in the kernel log: ir_common: Unknown symbol ir_g_keycode_from_table ir_common: Unknown symbol ir_core_debug + no mantis module loaded. I have the IR folder under lib/modules where ir-common.ko resides. In the common folder there is no file ir-common.ko. If I do manual loading, I get: sudo modprobe mantis WARNING: Error inserting mb86a16 (/lib/modules/2.6.33-rc1/kernel/drivers/media/dvb/frontends/mb86a16.ko): Unknown symbol in module, or unknown parameter (see dmesg) FATAL: Error inserting mantis (/lib/modules/2.6.33-rc1/kernel/drivers/media/dvb/mantis/mantis.ko): Unknown symbol in module, or unknown parameter (see dmesg) dmesg says: [ 289.939402] ir_common: Unknown symbol ir_g_keycode_from_table [ 289.939690] ir_common: Unknown symbol ir_core_debug This is the s2-liplianin tree. If using the http://jusst.de/hg/v4l-dvb tree, everything compiles ok, module loads, but there is no remote anywhere (there is an IR folder with the ir-common.ko file, under common there is not). Aljaz -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Which modules for the VP-2033? Where is the module mantis.ko?
On sre, 2009-12-23 at 23:24 +0400, Manu Abraham wrote: Aljaz, do you have the module mantis.ko? There was a build issue when i posted the link originally, but it had been fixed.. m...@manu-04:/stor/work/merge/v4l-dvb/v4l ls *.ko |grep mantis mantis_core.ko mantis.ko Yup, I have both of them. I just compiled http://jusst.de/hg/v4l-dvb again and the result is (depmode -a was run): - ir-common.ko is under drivers/media/common (not drivers/media/IR like Igor suggested but that is probably because it's a different repository). - mantis.ko and mantis_core.ko are under drivers/media/dvb/mantis The modules loaded are: mantis 14728 0 mantis_core23909 12 mantis ir_common 27005 1 mantis_core mb86a1616598 1 mantis tda100214822 1 mantis tda100235823 1 mantis zl10353 5893 1 mantis stv0299 7860 1 mantis dvb_core 75201 2 mantis_core,stv0299 kernel log has only these lines on mantis: Mantis :03:07.0: PCI INT A - GSI 21 (level, low) - IRQ 21 DVB: registering new adapter (Mantis DVB adapter) DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... and that's it. No VP-2040 to be seen anywhere and it's not there even if I do cat /proc/bus/input/devices (used to be one of the inputs). So I guess this is now the work in progress if I understand correctly or should the input be recognized regardless? Just to confirm on the autoload: no, it does not happen by default. I have to manually put modules under /etc/modules to load them on startup. Regards, Aljaz -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
