Re: Latest media-tree results in system hang, an no IR.
JD jdg8tb at gmail.com writes: With the latest media-tree, any access to my TV card (using tvtime and mplayer to watch through composite) results in my Arch Linux (2.6.39) system freezing. Here is the relavent part of my dmesg upon the freeze: http://codepad.org/q5MxDqAI I compiled the latest media-tree in order to, finally, get my infrared receiver working, however it still does not. An entry is made in /proc/bus/input/devices which points to /dev/input/event5; however. the /dev/lirc device node is not present, and using irw does not seem to recognise any input. Is anyone else experiencing such issues, and has anyone managed to get IR actually working on the HVR-1120. Thanks. I've have just tried this again on a fresh install of Arch Linux (Linux media 2.6.39-ARCH #1); however it is still a no-go. My steps are as follows: 1. git clone git://linuxtv.org/media_build.git 2. ./build.sh (reports it built fine with no errors) 3. reboot system (errors are now reported during boot-up, see dmesg) 4. try to access tv card using any program (mplayer or tvtime to watch composite), my X server crashes, I am thrown out to a TTY and the system appears unresponsive. dmesg (line 720 is where things start to appear interesting): http://codepad.org/OaeWUfAp lsmod: http://codepad.org/GMHFddGU lspci: http://codepad.org/paZ5hoCU Thanks. -- 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
Latest media-tree results in system hang, an no IR.
With the latest media-tree, any access to my TV card (using tvtime and mplayer to watch through composite) results in my Arch Linux (2.6.39) system freezing. Here is the relavent part of my dmesg upon the freeze: http://codepad.org/q5MxDqAI I compiled the latest media-tree in order to, finally, get my infrared receiver working, however it still does not. An entry is made in /proc/bus/input/devices which points to /dev/input/event5; however. the /dev/lirc device node is not present, and using irw does not seem to recognise any input. Is anyone else experiencing such issues, and has anyone managed to get IR actually working on the HVR-1120. Thanks. -- 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: Fwd: Firmware for HVR-1110
hermann pitton hermann-pitton at arcor.de writes: Hi JD,http://pastebin.ca/1894929 Am Samstag, den 03.07.2010, 03:32 +0100 schrieb JD: I'm confused as to what firmware in needed for the HVR-1110. Scouring the web, everywhere claims that the dvb-fe-tda10046 is required; however, dmesg logs show that this fails to be uploaded, and instead it is looking for dvb-fe-tda-10048: If I use tda-10048 then this seems to successfully loaded, but I am unable to find any channels with a scan; the dvb nodes within /dev/ are created and modules loaded, but dvbscan fails to tune. -- dmesg $ dmesg |grep firmware tda10048_firmware_upload: waiting for firmware upload (dvb-fe-tda10048-1.0.fw)... saa7134 :03:04.0: firmware: requesting dvb-fe-tda10048-1.0.fw tda10048_firmware_upload: firmware read 24878 bytes. tda10048_firmware_upload: firmware uploading tda10048_firmware_upload: firmware uploaded Any tips? Thanks. -- all variants of the HVR-1110 have a tda 10046. I can't see, how firmware loading can fail on auto detection of those and even switch over to tda10048 as an alternative. Do you force some card = number and are maybe on a not yet detected HVR-1120? Please provide the full dmesg log related to your card and make sure you are on Michael Krufky's latest patches. Cheers, Hermann Hi, thanks for the reply. To be sure that I hadn't set a certain card type somewhere, I used a clean install of a different OS (Linux Mint on a live USB); however, dmesg still shows that for some reason it is looking for the tda-10048 firmware. Here's the dmesg output: http://pastebin.ca/1894693 Here's the dmesg out after installing the tda10048 firmware if it is any help: http://pastebin.ca/1894929 I am able to find two or three analogue channels with tvtime, but no digital channels at all: dvbscan always says tuning failed, and using vlc to search for dvb-t channels results in none. I do not have the patches you mention, as I am quite new to tv for linux, but I'll take a look shortly. My card is definitely the WinTV-HVR1110 as it states it on the card itself, but the packaging states HVR-1110. -- 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: Fwd: Firmware for HVR-1110
All seems to be working fine now, I followed the installtion guide for the HVR-1120 and used the tda10048 f/w and I can now find DVB channels; I am still not sure as to why my card is looking for a different f/w tho, and would like to know why if anyone finds out. Thanks for your help. -- 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
Fwd: Firmware for HVR-1110
I'm confused as to what firmware in needed for the HVR-1110. Scouring the web, everywhere claims that the dvb-fe-tda10046 is required; however, dmesg logs show that this fails to be uploaded, and instead it is looking for dvb-fe-tda-10048: If I use tda-10048 then this seems to successfully loaded, but I am unable to find any channels with a scan; the dvb nodes within /dev/ are created and modules loaded, but dvbscan fails to tune. -- dmesg $ dmesg |grep firmware tda10048_firmware_upload: waiting for firmware upload (dvb-fe-tda10048-1.0.fw)... saa7134 :03:04.0: firmware: requesting dvb-fe-tda10048-1.0.fw tda10048_firmware_upload: firmware read 24878 bytes. tda10048_firmware_upload: firmware uploading tda10048_firmware_upload: firmware uploaded Any tips? Thanks. -- 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: [PATCH] Compro S350 GPIO change
On Mon, 2010-01-18 at 09:52 +0200, Theunis Potgieter wrote: 2010/1/17 JD Louw jd.l...@mweb.co.za: Hi, This patch enables LNB power on newer revision d1 Compro S350 and S300 DVB-S cards. While I don't have these cards to test with I'm confident that this works. See http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/7471 and http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/14296 and new windows driver as reference. Signed-off-by: JD Louw jd.l...@mweb.co.za diff -r 59e746a1c5d1 linux/drivers/media/video/saa7134/saa7134-cards.c --- a/linux/drivers/media/video/saa7134/saa7134-cards.c Wed Dec 30 09:10:33 2009 -0200 +++ b/linux/drivers/media/video/saa7134/saa7134-cards.c Sun Jan 17 14:51:07 2010 +0200 @@ -7037,8 +7037,8 @@ int saa7134_board_init1(struct saa7134_d break; case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; - saa_andorl(SAA7134_GPIO_GPMODE0 2, 0x8000, 0x8000); - saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0x8000, 0x8000); + saa_andorl(SAA7134_GPIO_GPMODE0 2, 0xC000, 0xC000); + saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0xC000, 0xC000); break; } return 0; -- Hi Jan, This does not fix the problem where the card is suppose to suspend and the Voltage drops to 0V? Do you still require the windows registry reference for this part? Hi, No, the aim of the patch is just to get the basic driver support for all S300/S350 revisions. A windows regspy capture on a d1 revision card may still be useful in double checking the GPIO values, but I already know which GPIO controls LNB voltage: GPIO15 = modulator reset GPIO14 = LNB power -- 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
[PATCH] Compro S350 GPIO change
Hi, This patch enables LNB power on newer revision d1 Compro S350 and S300 DVB-S cards. While I don't have these cards to test with I'm confident that this works. See http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/7471 and http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/14296 and new windows driver as reference. Signed-off-by: JD Louw jd.l...@mweb.co.za diff -r 59e746a1c5d1 linux/drivers/media/video/saa7134/saa7134-cards.c --- a/linux/drivers/media/video/saa7134/saa7134-cards.c Wed Dec 30 09:10:33 2009 -0200 +++ b/linux/drivers/media/video/saa7134/saa7134-cards.c Sun Jan 17 14:51:07 2010 +0200 @@ -7037,8 +7037,8 @@ int saa7134_board_init1(struct saa7134_d break; case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; - saa_andorl(SAA7134_GPIO_GPMODE0 2, 0x8000, 0x8000); - saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0x8000, 0x8000); + saa_andorl(SAA7134_GPIO_GPMODE0 2, 0xC000, 0xC000); + saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0xC000, 0xC000); break; } return 0; -- 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: Fwd: Compro S300 - ZL10313
On Wed, 2010-01-06 at 22:17 +0200, Theunis Potgieter wrote: 2010/1/2 JD Louw jd.l...@mweb.co.za: On Sat, 2010-01-02 at 09:39 +0200, Theunis Potgieter wrote: 2010/1/1 JD Louw jd.l...@mweb.co.za: On Tue, 2009-12-29 at 23:23 +0200, Theunis Potgieter wrote: Hi mailing list, I have a problem with my Compro S300 pci card under Linux 2.6.32. I cannot tune with this card and STR/SNRA is very bad compared to my Technisat SkyStar 2 pci card, connected to the same dish. I have this card and are willing to run tests, tested drivers etc to make this work. I currently load the module saa7134 with options: card=169 I enabled some debug parameters on the saa7134, not sure what else I should enable. Please find my dmesg log attached. lsmod shows : # lsmod Module Size Used by zl10039 6268 2 mt312 12048 2 saa7134_dvb41549 11 saa7134 195664 1 saa7134_dvb nfsd 416819 11 videobuf_dvb8187 1 saa7134_dvb dvb_core 148140 1 videobuf_dvb ir_common 40625 1 saa7134 v4l2_common21544 1 saa7134 videodev 58341 2 saa7134,v4l2_common v4l1_compat24473 1 videodev videobuf_dma_sg17830 2 saa7134_dvb,saa7134 videobuf_core 26534 3 saa7134,videobuf_dvb,videobuf_dma_sg tveeprom 12550 1 saa7134 thermal20547 0 processor 54638 1 # uname -a Linux vbox 2.6.32-gentoo #4 Sat Dec 19 00:54:19 SAST 2009 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux Thanks, Theunis Hi, It's probably the GPIO settings that are wrong for your SAA7133 based card revision. See http://osdir.com/ml/linux-media/2009-06/msg01256.html for an explanation. For quick confirmation check if you have 12V - 20V DC going to your LNB. The relevant lines of code is in ~/v4l-dvb/linux/drivers/media/video/saa7134/saa7134-cards.c: case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; saa_andorl(SAA7134_GPIO_GPMODE0 2, 0x8000, 0x8000); saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0x8000, 0x8000); break; Hi thanks for the hint. I changed it to the following: case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; saa_andorl(SAA7134_GPIO_GPMODE0 2, 0xc000, 0xc000); saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0xc000, 0xc000); break; I now get the same SNR as on my skystar2 card, signal is still indicating 17% where as the skystar2 would show 68%. At least I'm getting a LOCK on channels :) Thanks! Looking at your log, at least the demodulator and tuner is responding correctly. You can see this by looking at the i2c traffic addressed to 0x1c (demodulator) and 0xc0 (tuner). Attached is a dmesg trace from my working SAA7130 based card. Regards JD Hi, Just to clarify, can you now watch channels? At the moment the signal strength measurement is a bit whacked, so don't worry too much about it. I also get the 75%/17% figures you mentioned when tuning to strong signals. The figure is simply reported wrongly: even weaker signals should tune fine. If you want you can have a look in ~/v4l-dvb/linux/drivers/media/dvb/frontends/mt312.c at mt312_read_signal_strength(). Also, if you have a multimeter handy, can you confirm that the 0xc000 GPIO fix enables LNB voltage? I'd like to issue a patch for this. I've already tested this on my older card with no ill effect. This is what happened when I started vdr. Vertical gave a Volt reading between 13.9 and 14.1, Horizontal Gave 19.4 ~ 19.5. When I stopped vdr, the Voltage went back to 14V. I thought that it would read 0V. What is suppose to happen? Theunis Regards JD Hi, The newer revision cards should be able to shut down LNB power when the card is closed. This is what the Windows driver does; not yet implemented in Linux. I'd like to document the different variants of this card on the wiki. Can you send me the output of lspci -vvnn for your variant? If you have Windows, can you also send me some RegSpy states similar to the ones I'm attaching to this mail? Regards JD SAA7130 Card [0]: Vendor ID: 0x1131 Device ID: 0x7130 Subsystem ID:0xc900185b 7 states dumped Clean PC boot - no tuning yet -- SAA7130 Card - State 0: SAA7134_GPIO_GPMODE: 0080c000 ( 1000 1100 ) SAA7134_GPIO_GPSTATUS: 0084bf00 * ( 1100 1011 ) SAA7134_ANALOG_IN_CTRL1: 88 (10001000) SAA7134_ANALOG_IO_SELECT:02
Re: Fwd: Compro S300 - ZL10313
On Sat, 2010-01-02 at 09:39 +0200, Theunis Potgieter wrote: 2010/1/1 JD Louw jd.l...@mweb.co.za: On Tue, 2009-12-29 at 23:23 +0200, Theunis Potgieter wrote: Hi mailing list, I have a problem with my Compro S300 pci card under Linux 2.6.32. I cannot tune with this card and STR/SNRA is very bad compared to my Technisat SkyStar 2 pci card, connected to the same dish. I have this card and are willing to run tests, tested drivers etc to make this work. I currently load the module saa7134 with options: card=169 I enabled some debug parameters on the saa7134, not sure what else I should enable. Please find my dmesg log attached. lsmod shows : # lsmod Module Size Used by zl10039 6268 2 mt312 12048 2 saa7134_dvb41549 11 saa7134 195664 1 saa7134_dvb nfsd 416819 11 videobuf_dvb8187 1 saa7134_dvb dvb_core 148140 1 videobuf_dvb ir_common 40625 1 saa7134 v4l2_common21544 1 saa7134 videodev 58341 2 saa7134,v4l2_common v4l1_compat24473 1 videodev videobuf_dma_sg17830 2 saa7134_dvb,saa7134 videobuf_core 26534 3 saa7134,videobuf_dvb,videobuf_dma_sg tveeprom 12550 1 saa7134 thermal20547 0 processor 54638 1 # uname -a Linux vbox 2.6.32-gentoo #4 Sat Dec 19 00:54:19 SAST 2009 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux Thanks, Theunis Hi, It's probably the GPIO settings that are wrong for your SAA7133 based card revision. See http://osdir.com/ml/linux-media/2009-06/msg01256.html for an explanation. For quick confirmation check if you have 12V - 20V DC going to your LNB. The relevant lines of code is in ~/v4l-dvb/linux/drivers/media/video/saa7134/saa7134-cards.c: case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; saa_andorl(SAA7134_GPIO_GPMODE0 2, 0x8000, 0x8000); saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0x8000, 0x8000); break; Hi thanks for the hint. I changed it to the following: case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; saa_andorl(SAA7134_GPIO_GPMODE0 2, 0xc000, 0xc000); saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0xc000, 0xc000); break; I now get the same SNR as on my skystar2 card, signal is still indicating 17% where as the skystar2 would show 68%. At least I'm getting a LOCK on channels :) Thanks! Looking at your log, at least the demodulator and tuner is responding correctly. You can see this by looking at the i2c traffic addressed to 0x1c (demodulator) and 0xc0 (tuner). Attached is a dmesg trace from my working SAA7130 based card. Regards JD Hi, Just to clarify, can you now watch channels? At the moment the signal strength measurement is a bit whacked, so don't worry too much about it. I also get the 75%/17% figures you mentioned when tuning to strong signals. The figure is simply reported wrongly: even weaker signals should tune fine. If you want you can have a look in ~/v4l-dvb/linux/drivers/media/dvb/frontends/mt312.c at mt312_read_signal_strength(). Also, if you have a multimeter handy, can you confirm that the 0xc000 GPIO fix enables LNB voltage? I'd like to issue a patch for this. I've already tested this on my older card with no ill effect. Regards JD -- 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: Fwd: Compro S300 - ZL10313
On Tue, 2009-12-29 at 23:23 +0200, Theunis Potgieter wrote: Hi mailing list, I have a problem with my Compro S300 pci card under Linux 2.6.32. I cannot tune with this card and STR/SNRA is very bad compared to my Technisat SkyStar 2 pci card, connected to the same dish. I have this card and are willing to run tests, tested drivers etc to make this work. I currently load the module saa7134 with options: card=169 I enabled some debug parameters on the saa7134, not sure what else I should enable. Please find my dmesg log attached. lsmod shows : # lsmod Module Size Used by zl10039 6268 2 mt312 12048 2 saa7134_dvb41549 11 saa7134 195664 1 saa7134_dvb nfsd 416819 11 videobuf_dvb8187 1 saa7134_dvb dvb_core 148140 1 videobuf_dvb ir_common 40625 1 saa7134 v4l2_common21544 1 saa7134 videodev 58341 2 saa7134,v4l2_common v4l1_compat24473 1 videodev videobuf_dma_sg17830 2 saa7134_dvb,saa7134 videobuf_core 26534 3 saa7134,videobuf_dvb,videobuf_dma_sg tveeprom 12550 1 saa7134 thermal20547 0 processor 54638 1 # uname -a Linux vbox 2.6.32-gentoo #4 Sat Dec 19 00:54:19 SAST 2009 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux Thanks, Theunis Hi, It's probably the GPIO settings that are wrong for your SAA7133 based card revision. See http://osdir.com/ml/linux-media/2009-06/msg01256.html for an explanation. For quick confirmation check if you have 12V - 20V DC going to your LNB. The relevant lines of code is in ~/v4l-dvb/linux/drivers/media/video/saa7134/saa7134-cards.c: case SAA7134_BOARD_VIDEOMATE_S350: dev-has_remote = SAA7134_REMOTE_GPIO; saa_andorl(SAA7134_GPIO_GPMODE0 2, 0x8000, 0x8000); saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0x8000, 0x8000); break; Looking at your log, at least the demodulator and tuner is responding correctly. You can see this by looking at the i2c traffic addressed to 0x1c (demodulator) and 0xc0 (tuner). Attached is a dmesg trace from my working SAA7130 based card. Regards JD 07:00.0 Multimedia controller [0480]: Philips Semiconductors SAA7130 Video Broadcast Decoder [1131:7130] (rev 01) Subsystem: Compro Technology, Inc. Device [185b:c900] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 (21000ns min, 8000ns max) Interrupt: pin A routed to IRQ 21 Region 0: Memory at 50004800 (32-bit, non-prefetchable) [size=1K] Capabilities: access denied Kernel driver in use: saa7134 Kernel modules: saa7134 and [6.560811] Linux video capture interface: v2.00 [6.602624] saa7130/34: v4l2 driver version 0.2.15 loaded [6.602776] saa7134 :07:00.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [6.602783] saa7130[0]: found at :07:00.0, rev: 1, irq: 21, latency: 32, mmio: 0x50004800 [6.602788] saa7130[0]: subsystem: 185b:c900, board: Compro VideoMate S350/S300 [card=169,autodetected] [6.602803] saa7130[0]: board init: gpio is 843f00 [6.602873] input: saa7134 IR (Compro VideoMate S3 as /devices/pci:00/:00:1e.0/:07:00.0/input/input14 [6.602935] Creating IR device irrcv0 [6.602939] IRQ 21/saa7130[0]: IRQF_DISABLED is not guaranteed on shared IRQs [6.710132] saa7130[0]: i2c xfer: a0 00 [6.730092] saa7130[0]: i2c xfer: a1 =5b =18 =00 =c9 =54 =20 =1c =00 =43 =43 =a9 =1c =55 =d2 =b2 =92 =00 =ff =86 =0f =ff =20 =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =01 =40 =01 =02 =02 =01 =03 =01 =08 =ff =00 =87 =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =d6 =00 =c0 =86 =1c =02 =01 =02 =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =cb =30 =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff = ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =f f =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff =ff [6.780031] saa7130[0]: i2c eeprom 00: 5b 18 00 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 [6.780044] saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff [6.780056] saa7130[0]: i2c eeprom 20: 01 40 01 02 02 01 03 01 08 ff 00 87 ff
