Re: Hauppauge HVR-930C problems
On 01/10/12 20:30, Mihai Dobrescu wrote: Hello, Just compiled the latest again, but still no difference. kaffeine doesn't see any source in channels dialog, two devices are in 'Configure Television' dialog: DRXK DVB-C - device not connected - as Device 1 and DRXK DVB-C DVB-T as Device 2. Concerning the last one, no source is selected, as I am in Romania, which is not in the list scan_w finds nothing. What should I do next? Regards, Mike. Mike, I did some more w_scan and dvbscan tests with the last three releases, that is, http://linuxtv.org/downloads/drivers/linux-media-2012-01-07.tar.bz2, http://linuxtv.org/downloads/drivers/linux-media-2012-01-08.tar.bz2, and http://linuxtv.org/downloads/drivers/linux-media-2012-01-11.tar.bz2 respectively. Using 2012-01-11 scanning don't work and using 2012-01-08 scanning sort-of works but I need to use 2011-01-07 first, unload it, install 2011-01-08, load it (without rebooting) and then I can scan with 2011-01-08. w_scan finds significantly fewer channels with the default settings [1] than dvbscan [2]. However, I discovered that if I increase the filter timout for w_scan then I find much more channels. Try something like, lin-tv media_build # w_scan -fc -t 3 -Q 1 -S 0 -c NO The -t, -Q and -S parameters are so called "expert" paramaters (check the w_scan man page). Leave out the -Q and -S parameters if you don't know the symbol rate and modulation type. To test it do something like: lin-tv ~ # cd /usr/src lin-tv src # git clone git://linuxtv.org/media_build.git lin-tv src # cd media_build Then edit the linux/Makefile and change LATEST_TAR := http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2 LATEST_TAR_MD5 := http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2.md5 to LATEST_TAR := http://linuxtv.org/downloads/drivers/linux-media-2012-01-07.tar.bz2 LATEST_TAR_MD5 := http://linuxtv.org/downloads/drivers/linux-media-2012-01-07.tar.bz2.md5 Then build, install, and reload the drivers. lin-tv media_build # ./build lin-tv media_build # make unload lin-tv media_build # make install lin-tv media_build # make load You can also try scanning with MythTV. You only need a starting freq (and perhaps modulation type, for example I use QAM256). If you have a PVR-decoder, maybe you can find the freq. etc info there? /Fredrik [1] lin-tv media_build # w_scan -fc -c NO w_scan version 20111011 (compiled for DVB API 5.2) using settings for NORWAY DVB cable DVB-C frontend_type DVB-C, channellist 7 output format vdr-1.6 WARNING: could not guess your codepage. Falling back to 'UTF-8' output charset 'UTF-8', use -C to override Info: using DVB adapter auto detection. /dev/dvb/adapter0/frontend0 -> DVB-C "DRXK DVB-C DVB-T": good :-) Using DVB-C frontend (adapter /dev/dvb/adapter0/frontend0) -_-_-_-_ Getting frontend capabilities-_-_-_-_ Using DVB API 5.5 frontend 'DRXK DVB-C DVB-T' supports INVERSION_AUTO QAM_AUTO not supported, trying QAM_64 QAM_256. FEC_AUTO FREQ (47.00MHz ... 865.00MHz) SRATE (0.870MBd ... 11.700MBd) -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ searching QAM64... 73000: sr6900 (time: 00:00) sr6875 (time: 00:03) 81000: sr6900 (time: 00:05) sr6875 (time: 00:08) 113000: sr6900 (time: 00:10) sr6875 (time: 00:13) 121000: sr6900 (time: 00:15) sr6875 (time: 00:18) 129000: sr6900 (time: 00:20) sr6875 (time: 00:23) 137000: sr6900 (time: 00:26) sr6875 (time: 00:28) 145000: sr6900 (time: 00:31) sr6875 (time: 00:33) 153000: sr6900 (time: 00:36) sr6875 (time: 00:38) 161000: sr6900 (time: 00:41) sr6875 (time: 00:43) 169000: sr6900 (time: 00:46) sr6875 (time: 00:48) 314000: sr6900 (time: 00:51) sr6875 (time: 00:53) 322000: sr6900 (time: 00:56) sr6875 (time: 00:59) 858000: sr6900 (time: 06:36) sr6875 (time: 06:39) searching QAM256... 73000: sr6900 (time: 06:41) sr6875 (time: 06:44) 81000: sr6900 (time: 06:47) sr6875 (time: 06:49) 113000: sr6900 (time: 06:52) sr6875 (time: 06:54) 121000: sr6900 (time: 06:57) sr6875 (time: 06:59) 129000: sr6900 (time: 07:02) sr6875 (time: 07:04) 137000: sr6900 (time: 07:07) sr6875 (time: 07:09) 145000: sr6900 (time: 07:12) sr6875 (time: 07:15) 153000: sr6900 (time: 07:17) sr6875 (time: 07:20) 161000: sr6900 (time: 07:22) sr6875 (time: 07:25) 169000: sr6900 (time: 07:27) sr6875 (time: 07:30) 314000: sr6900 (time: 07:32) (time: 07:33) sr6875 (time: 07:34) 322000: sr6900 (time: 07:37) (time: 07:38) sr6875 (time: 07:39) 33: sr6900 (time: 07:42) (time: 07:43) sr6875 (time: 07:44) 338000: sr6900 (time: 07:46) (time: 07:48) sr6875 (time: 07:49) 346000: sr6900 (time: 07:51) (time: 07:52) sr6875 (time: 07:53) 354000: sr6900 (time: 07:56) (time: 07:57) sr6875 (time: 07:58) 362000: sr6900 (time: 08:01) (time: 08:02) sr6875 (time: 08:03) 37: sr6900 (time: 08:05) (time: 08:06) sr6875 (time: 08:07) 378000: sr6900 (time: 08:10) (time: 08:11) sr6875 (time: 08:12) 386000: sr6900 (time: 08:15) (time: 08:16) sr6875 (time: 08:17) 394000: sr6900 (time: 08:19) sr6875 (time: 08:22) 402000: sr690
Re: Hauppauge HVR-930C problems
On 11-01-2012 03:28, Mihai Dobrescu wrote: > I've got the sources, I've successfully built everything. > Where should I expect to have the binary files after the make install? By default, make install puts everything inside /usr/local. So, the binaries should be at /usr/local/bin. Regards, Mauro > > Thank you. > > On Tue, Jan 10, 2012 at 10:35 PM, Mauro Carvalho Chehab > wrote: >> On 10-01-2012 18:23, Mihai Dobrescu wrote: >>> I can't find dvb-fe-util tool. >> >> http://git.linuxtv.org/v4l-utils.git/blob/ad284d9ef6600e091515b0abd7cec64736097265:/utils/dvb/dvb-fe-tool.c >> >> Regards, >> Mauro >> >>> >>> On Tue, Jan 10, 2012 at 9:41 PM, Mauro Carvalho Chehab >>> wrote: On 10-01-2012 17:30, Mihai Dobrescu wrote: > Hello, > > Just compiled the latest again, but still no difference. > kaffeine doesn't see any source in channels dialog, two devices are in > 'Configure Television' dialog: DRXK DVB-C - device not connected - as > Device 1 and DRXK DVB-C DVB-T as Device 2. Concerning the last one, no > source is selected, as I am in Romania, which is not in the list > scan_w finds nothing. > > What should I do next? Kaffeine doesn't work with MFE tuners (at least not the version I have). It only sees one delivery system. If you're using the very latest version of the driver (the one at the media-build tree), you can use the dvb-fe-util tool to change the delivery system to DVB-C or to DVB-T. The tool is now part of the v4l-utils. You may also request a Kaffeine developer or to submit a patch for it, in order to add support on it to detect the frontend supported delivery systems and to change it dynamically. > > Regards, Mike. > > On Tue, Jan 10, 2012 at 4:42 PM, Fredrik Lingvall > wrote: >> On 12/25/11 16:56, Fredrik Lingvall wrote: >>> >>> On 12/18/11 10:20, Fredrik Lingvall wrote: On 12/17/11 20:53, Mihai Dobrescu wrote: > > > > > Mihai, > > I got some success. I did this, > > # cd /usr/src (for example) > > # git clone git://linuxtv.org/media_build.git > > # emerge dev-util/patchutils > # emerge Proc-ProcessTable > > # cd media_build > # ./build > # make install > > Which will install the latest driver on your running kernel (just in > case > make sure /usr/src/linux points to your running kernel sources). Then > reboot. > > You should now see that (among other) modules have loaded: > > # lsmod > > > > em28xx 93528 1 em28xx_dvb > v4l2_common 5254 1 em28xx > videobuf_vmalloc4167 1 em28xx > videobuf_core 15151 2 em28xx,videobuf_vmalloc > > Then try w_scan and dvbscan etc. I got mythtv to scan too now. There > were > some warnings and timeouts and I'm not sure if this is normal or not. > > You can also do a dmesg -c while scanning to monitor the changes en > the > kernel log. > > Regards, > > /Fredrik > > > In my case I have: > > lsmod |grep em2 > em28xx_dvb 12608 0 > dvb_core 76187 1 em28xx_dvb > em28xx 82436 1 em28xx_dvb > v4l2_common 5087 1 em28xx > videodev 70123 2 em28xx,v4l2_common > videobuf_vmalloc3783 1 em28xx > videobuf_core 12991 2 em28xx,videobuf_vmalloc > rc_core11695 11 > > rc_hauppauge,ir_lirc_codec,ir_mce_kbd_decoder,ir_sanyo_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,em28xx,ir_nec_decoder > tveeprom 12441 1 em28xx > i2c_core 14232 9 > > xc5000,drxk,em28xx_dvb,em28xx,v4l2_common,videodev,tveeprom,nvidia,i2c_i801 > > yet, w_scan founds nothing. I was able to scan using the "media_build" install method described above but when trying to watch a free channel the image and sound was stuttering severly. I have tried both MythTV and mplayer with similar results. I created the channel list for mplayer with: lintv ~ # dvbscan -x0 -fc /usr/share/dvb/dvb-c/no-Oslo-Get -o zap > .mplayer/channels.conf And, for example, I get this output from mplayer plus a very (blocky) stuttering image and sound: lin-tv ~ # mplayer dvb://1@"TV8 Oslo" -ao jack >>> >>> I did some more tests with release snapshots 2011-12-13, 2011-12-21, and >>> 20
Re: Hauppauge HVR-930C problems
On 01/10/12 15:42, Fredrik Lingvall wrote: On 12/25/11 16:56, Fredrik Lingvall wrote: On 12/18/11 10:20, Fredrik Lingvall wrote: On 12/17/11 20:53, Mihai Dobrescu wrote: Mihai, I got some success. I did this, # cd /usr/src (for example) # git clone git://linuxtv.org/media_build.git # emerge dev-util/patchutils # emerge Proc-ProcessTable # cd media_build # ./build # make install Which will install the latest driver on your running kernel (just in case make sure /usr/src/linux points to your running kernel sources). Then reboot. You should now see that (among other) modules have loaded: # lsmod em28xx 93528 1 em28xx_dvb v4l2_common 5254 1 em28xx videobuf_vmalloc4167 1 em28xx videobuf_core 15151 2 em28xx,videobuf_vmalloc Then try w_scan and dvbscan etc. I got mythtv to scan too now. There were some warnings and timeouts and I'm not sure if this is normal or not. You can also do a dmesg -c while scanning to monitor the changes en the kernel log. Regards, /Fredrik In my case I have: lsmod |grep em2 em28xx_dvb 12608 0 dvb_core 76187 1 em28xx_dvb em28xx 82436 1 em28xx_dvb v4l2_common 5087 1 em28xx videodev 70123 2 em28xx,v4l2_common videobuf_vmalloc3783 1 em28xx videobuf_core 12991 2 em28xx,videobuf_vmalloc rc_core11695 11 rc_hauppauge,ir_lirc_codec,ir_mce_kbd_decoder,ir_sanyo_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,em28xx,ir_nec_decoder tveeprom 12441 1 em28xx i2c_core 14232 9 xc5000,drxk,em28xx_dvb,em28xx,v4l2_common,videodev,tveeprom,nvidia,i2c_i801 yet, w_scan founds nothing. I was able to scan using the "media_build" install method described above but when trying to watch a free channel the image and sound was stuttering severly. I have tried both MythTV and mplayer with similar results. I created the channel list for mplayer with: lintv ~ # dvbscan -x0 -fc /usr/share/dvb/dvb-c/no-Oslo-Get -o zap > .mplayer/channels.conf And, for example, I get this output from mplayer plus a very (blocky) stuttering image and sound: lin-tv ~ # mplayer dvb://1@"TV8 Oslo" -ao jack I did some more tests with release snapshots 2011-12-13, 2011-12-21, and 2011-12-25, respectively. I did this by changing LATEST_TAR := http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2 LATEST_TAR_MD5 := http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2.md5 in linux/Makefile to the corresponding release. Results: * linux-media-2011-12-13.tar.bz2 The ./build script builds the drivers cleanly, scanning works, but watching video does not work correctly. * linux-media-2011-12-21.tar.bz2 The ./build script fails at the as3645a.c file (on this machine but I can build it on two other machines using the same kernel and kernel 2.6.39-gentoo-r3, respectively). I can build it with make menuconfig etc (where I disabled stuff I don't need, eg. disabling [ ] Media Controller API (EXPERIMENTAL) ). The em28xx generate a kernel core dump though [1]. * linux-media-2011-12-25.tar.bz2 Same problem as 2011-12-21. Regards, /Fredrik Here's some more test results. I have upgraded the kernel to 3.1.6-gentoo (where I enabled DVB when I build the kernel). Both http://linuxtv.org/downloads/drivers/linux-media-2012-01-07.tar.bz2 and http://linuxtv.org/downloads/drivers/linux-media-2012-01-08.tar.bz2 now builds using the lin-tv ~ # cd /usr/src lin-tv src # git clone git://linuxtv.org/media_build.git lin-tv src # cd media_build lin-tv media_build # ./build lin-tv media_build # make install method. Scanning and (finally) watching video works but not flawlessly. I also suspect that I don't find all channels when I scan. I have scanned using, * dvbscan -x 0 -fc /usr/share/dvb/dvb-c/no-Oslo-Get > .mplayer/channels.conf * Kaffeine (1.2.2) * MythTV (0.25_pre20120103) respectively. Both kaffeine and mythtv reports a very low signal level (0%) and an SNR of only 1%. (kaffeine). I'm not sure if the driver reports this correctly though. Whatching live TV works on some channels but not all. HD channels seems more difficult than SD channels, and I have not figured out why some channels work and some don't. I get Signal 0% | S/N 2.6dB | BE 0 | (_L_S) Partial Lock and no video on many channels in mythtv. Regards, /Fredrik Tried the http://linuxtv.org/downloads/drivers/linux-media-2012-01-11.tar.bz2 release and the scan setting now looks different in MythTV (it has more parameters) and dvbscan fails (mythtv scanning fails too): lin-tv ~ # dvbscan -xo -fc /usr/share/dvb/dvb-c/no-Oslo-Get scanning /usr/share/dvb/dvb-c/no-Oslo-Get using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 24100 690 0 5 initial transponder 27200 690 0 5 initial transponder 28000 690 0 5 initial transpon
Re: Hauppauge HVR-930C problems
I've got the sources, I've successfully built everything. Where should I expect to have the binary files after the make install? Thank you. On Tue, Jan 10, 2012 at 10:35 PM, Mauro Carvalho Chehab wrote: > On 10-01-2012 18:23, Mihai Dobrescu wrote: >> I can't find dvb-fe-util tool. > > http://git.linuxtv.org/v4l-utils.git/blob/ad284d9ef6600e091515b0abd7cec64736097265:/utils/dvb/dvb-fe-tool.c > > Regards, > Mauro > >> >> On Tue, Jan 10, 2012 at 9:41 PM, Mauro Carvalho Chehab >> wrote: >>> On 10-01-2012 17:30, Mihai Dobrescu wrote: Hello, Just compiled the latest again, but still no difference. kaffeine doesn't see any source in channels dialog, two devices are in 'Configure Television' dialog: DRXK DVB-C - device not connected - as Device 1 and DRXK DVB-C DVB-T as Device 2. Concerning the last one, no source is selected, as I am in Romania, which is not in the list scan_w finds nothing. What should I do next? >>> >>> Kaffeine doesn't work with MFE tuners (at least not the version I have). >>> It only sees one delivery system. >>> >>> If you're using the very latest version of the driver (the one at the >>> media-build tree), you can use the dvb-fe-util tool to change >>> the delivery system to DVB-C or to DVB-T. >>> >>> The tool is now part of the v4l-utils. >>> >>> You may also request a Kaffeine developer or to submit a patch for it, >>> in order to add support on it to detect the frontend supported >>> delivery systems and to change it dynamically. >>> Regards, Mike. On Tue, Jan 10, 2012 at 4:42 PM, Fredrik Lingvall wrote: > On 12/25/11 16:56, Fredrik Lingvall wrote: >> >> On 12/18/11 10:20, Fredrik Lingvall wrote: >>> >>> On 12/17/11 20:53, Mihai Dobrescu wrote: Mihai, I got some success. I did this, # cd /usr/src (for example) # git clone git://linuxtv.org/media_build.git # emerge dev-util/patchutils # emerge Proc-ProcessTable # cd media_build # ./build # make install Which will install the latest driver on your running kernel (just in case make sure /usr/src/linux points to your running kernel sources). Then reboot. You should now see that (among other) modules have loaded: # lsmod em28xx 93528 1 em28xx_dvb v4l2_common 5254 1 em28xx videobuf_vmalloc 4167 1 em28xx videobuf_core 15151 2 em28xx,videobuf_vmalloc Then try w_scan and dvbscan etc. I got mythtv to scan too now. There were some warnings and timeouts and I'm not sure if this is normal or not. You can also do a dmesg -c while scanning to monitor the changes en the kernel log. Regards, /Fredrik In my case I have: lsmod |grep em2 em28xx_dvb 12608 0 dvb_core 76187 1 em28xx_dvb em28xx 82436 1 em28xx_dvb v4l2_common 5087 1 em28xx videodev 70123 2 em28xx,v4l2_common videobuf_vmalloc 3783 1 em28xx videobuf_core 12991 2 em28xx,videobuf_vmalloc rc_core 11695 11 rc_hauppauge,ir_lirc_codec,ir_mce_kbd_decoder,ir_sanyo_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,em28xx,ir_nec_decoder tveeprom 12441 1 em28xx i2c_core 14232 9 xc5000,drxk,em28xx_dvb,em28xx,v4l2_common,videodev,tveeprom,nvidia,i2c_i801 yet, w_scan founds nothing. >>> >>> >>> I was able to scan using the "media_build" install method described >>> above >>> but when trying to watch a free channel the image and sound was >>> stuttering >>> severly. I have tried both MythTV and mplayer with similar results. >>> >>> I created the channel list for mplayer with: >>> >>> lintv ~ # dvbscan -x0 -fc /usr/share/dvb/dvb-c/no-Oslo-Get -o zap > >>> .mplayer/channels.conf >>> >>> And, for example, I get this output from mplayer plus a very (blocky) >>> stuttering image and sound: >>> >>> lin-tv ~ # mplayer dvb://1@"TV8 Oslo" -ao jack >>> >> >> I did some more tests with release snapshots 2011-12-13, 2011-12-21, and >> 2011-12-25, respectively. I did this by changing >> >> LATEST_TAR := >> http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2 >> LATEST_TAR_MD5 := >> http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2.md5 >> >> in linux/Makefile to the corresponding release. >> >> Res
Re: Hauppauge HVR-930C problems
On 10-01-2012 18:23, Mihai Dobrescu wrote: > I can't find dvb-fe-util tool. http://git.linuxtv.org/v4l-utils.git/blob/ad284d9ef6600e091515b0abd7cec64736097265:/utils/dvb/dvb-fe-tool.c Regards, Mauro > > On Tue, Jan 10, 2012 at 9:41 PM, Mauro Carvalho Chehab > wrote: >> On 10-01-2012 17:30, Mihai Dobrescu wrote: >>> Hello, >>> >>> Just compiled the latest again, but still no difference. >>> kaffeine doesn't see any source in channels dialog, two devices are in >>> 'Configure Television' dialog: DRXK DVB-C - device not connected - as >>> Device 1 and DRXK DVB-C DVB-T as Device 2. Concerning the last one, no >>> source is selected, as I am in Romania, which is not in the list >>> scan_w finds nothing. >>> >>> What should I do next? >> >> Kaffeine doesn't work with MFE tuners (at least not the version I have). >> It only sees one delivery system. >> >> If you're using the very latest version of the driver (the one at the >> media-build tree), you can use the dvb-fe-util tool to change >> the delivery system to DVB-C or to DVB-T. >> >> The tool is now part of the v4l-utils. >> >> You may also request a Kaffeine developer or to submit a patch for it, >> in order to add support on it to detect the frontend supported >> delivery systems and to change it dynamically. >> >>> >>> Regards, Mike. >>> >>> On Tue, Jan 10, 2012 at 4:42 PM, Fredrik Lingvall >>> wrote: On 12/25/11 16:56, Fredrik Lingvall wrote: > > On 12/18/11 10:20, Fredrik Lingvall wrote: >> >> On 12/17/11 20:53, Mihai Dobrescu wrote: >>> >>> >>> >>> >>> Mihai, >>> >>> I got some success. I did this, >>> >>> # cd /usr/src (for example) >>> >>> # git clone git://linuxtv.org/media_build.git >>> >>> # emerge dev-util/patchutils >>> # emerge Proc-ProcessTable >>> >>> # cd media_build >>> # ./build >>> # make install >>> >>> Which will install the latest driver on your running kernel (just in >>> case >>> make sure /usr/src/linux points to your running kernel sources). Then >>> reboot. >>> >>> You should now see that (among other) modules have loaded: >>> >>> # lsmod >>> >>> >>> >>> em28xx 93528 1 em28xx_dvb >>> v4l2_common 5254 1 em28xx >>> videobuf_vmalloc4167 1 em28xx >>> videobuf_core 15151 2 em28xx,videobuf_vmalloc >>> >>> Then try w_scan and dvbscan etc. I got mythtv to scan too now. There >>> were >>> some warnings and timeouts and I'm not sure if this is normal or not. >>> >>> You can also do a dmesg -c while scanning to monitor the changes en the >>> kernel log. >>> >>> Regards, >>> >>> /Fredrik >>> >>> >>> In my case I have: >>> >>> lsmod |grep em2 >>> em28xx_dvb 12608 0 >>> dvb_core 76187 1 em28xx_dvb >>> em28xx 82436 1 em28xx_dvb >>> v4l2_common 5087 1 em28xx >>> videodev 70123 2 em28xx,v4l2_common >>> videobuf_vmalloc3783 1 em28xx >>> videobuf_core 12991 2 em28xx,videobuf_vmalloc >>> rc_core11695 11 >>> >>> rc_hauppauge,ir_lirc_codec,ir_mce_kbd_decoder,ir_sanyo_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,em28xx,ir_nec_decoder >>> tveeprom 12441 1 em28xx >>> i2c_core 14232 9 >>> >>> xc5000,drxk,em28xx_dvb,em28xx,v4l2_common,videodev,tveeprom,nvidia,i2c_i801 >>> >>> yet, w_scan founds nothing. >> >> >> I was able to scan using the "media_build" install method described above >> but when trying to watch a free channel the image and sound was >> stuttering >> severly. I have tried both MythTV and mplayer with similar results. >> >> I created the channel list for mplayer with: >> >> lintv ~ # dvbscan -x0 -fc /usr/share/dvb/dvb-c/no-Oslo-Get -o zap > >> .mplayer/channels.conf >> >> And, for example, I get this output from mplayer plus a very (blocky) >> stuttering image and sound: >> >> lin-tv ~ # mplayer dvb://1@"TV8 Oslo" -ao jack >> > > I did some more tests with release snapshots 2011-12-13, 2011-12-21, and > 2011-12-25, respectively. I did this by changing > > LATEST_TAR := > http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2 > LATEST_TAR_MD5 := > http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2.md5 > > in linux/Makefile to the corresponding release. > > Results: > > * linux-media-2011-12-13.tar.bz2 > > The ./build script builds the drivers cleanly, scanning works, but > watching video does not work correctly. > > * linux-media-2011-12-21.tar.bz2 > > The ./build script fails at the as3645a.c file (on this machine but I can > build it on two other machines using the same
Re: Hauppauge HVR-930C problems
I can't find dvb-fe-util tool. On Tue, Jan 10, 2012 at 9:41 PM, Mauro Carvalho Chehab wrote: > On 10-01-2012 17:30, Mihai Dobrescu wrote: >> Hello, >> >> Just compiled the latest again, but still no difference. >> kaffeine doesn't see any source in channels dialog, two devices are in >> 'Configure Television' dialog: DRXK DVB-C - device not connected - as >> Device 1 and DRXK DVB-C DVB-T as Device 2. Concerning the last one, no >> source is selected, as I am in Romania, which is not in the list >> scan_w finds nothing. >> >> What should I do next? > > Kaffeine doesn't work with MFE tuners (at least not the version I have). > It only sees one delivery system. > > If you're using the very latest version of the driver (the one at the > media-build tree), you can use the dvb-fe-util tool to change > the delivery system to DVB-C or to DVB-T. > > The tool is now part of the v4l-utils. > > You may also request a Kaffeine developer or to submit a patch for it, > in order to add support on it to detect the frontend supported > delivery systems and to change it dynamically. > >> >> Regards, Mike. >> >> On Tue, Jan 10, 2012 at 4:42 PM, Fredrik Lingvall >> wrote: >>> On 12/25/11 16:56, Fredrik Lingvall wrote: On 12/18/11 10:20, Fredrik Lingvall wrote: > > On 12/17/11 20:53, Mihai Dobrescu wrote: >> >> >> >> >> Mihai, >> >> I got some success. I did this, >> >> # cd /usr/src (for example) >> >> # git clone git://linuxtv.org/media_build.git >> >> # emerge dev-util/patchutils >> # emerge Proc-ProcessTable >> >> # cd media_build >> # ./build >> # make install >> >> Which will install the latest driver on your running kernel (just in >> case >> make sure /usr/src/linux points to your running kernel sources). Then >> reboot. >> >> You should now see that (among other) modules have loaded: >> >> # lsmod >> >> >> >> em28xx 93528 1 em28xx_dvb >> v4l2_common 5254 1 em28xx >> videobuf_vmalloc 4167 1 em28xx >> videobuf_core 15151 2 em28xx,videobuf_vmalloc >> >> Then try w_scan and dvbscan etc. I got mythtv to scan too now. There >> were >> some warnings and timeouts and I'm not sure if this is normal or not. >> >> You can also do a dmesg -c while scanning to monitor the changes en the >> kernel log. >> >> Regards, >> >> /Fredrik >> >> >> In my case I have: >> >> lsmod |grep em2 >> em28xx_dvb 12608 0 >> dvb_core 76187 1 em28xx_dvb >> em28xx 82436 1 em28xx_dvb >> v4l2_common 5087 1 em28xx >> videodev 70123 2 em28xx,v4l2_common >> videobuf_vmalloc 3783 1 em28xx >> videobuf_core 12991 2 em28xx,videobuf_vmalloc >> rc_core 11695 11 >> >> rc_hauppauge,ir_lirc_codec,ir_mce_kbd_decoder,ir_sanyo_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,em28xx,ir_nec_decoder >> tveeprom 12441 1 em28xx >> i2c_core 14232 9 >> >> xc5000,drxk,em28xx_dvb,em28xx,v4l2_common,videodev,tveeprom,nvidia,i2c_i801 >> >> yet, w_scan founds nothing. > > > I was able to scan using the "media_build" install method described above > but when trying to watch a free channel the image and sound was stuttering > severly. I have tried both MythTV and mplayer with similar results. > > I created the channel list for mplayer with: > > lintv ~ # dvbscan -x0 -fc /usr/share/dvb/dvb-c/no-Oslo-Get -o zap > > .mplayer/channels.conf > > And, for example, I get this output from mplayer plus a very (blocky) > stuttering image and sound: > > lin-tv ~ # mplayer dvb://1@"TV8 Oslo" -ao jack > I did some more tests with release snapshots 2011-12-13, 2011-12-21, and 2011-12-25, respectively. I did this by changing LATEST_TAR := http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2 LATEST_TAR_MD5 := http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2.md5 in linux/Makefile to the corresponding release. Results: * linux-media-2011-12-13.tar.bz2 The ./build script builds the drivers cleanly, scanning works, but watching video does not work correctly. * linux-media-2011-12-21.tar.bz2 The ./build script fails at the as3645a.c file (on this machine but I can build it on two other machines using the same kernel and kernel 2.6.39-gentoo-r3, respectively). I can build it with make menuconfig etc (where I disabled stuff I don't need, eg. disabling [ ] Media Controller API (EXPERIMENTAL) ). The em28xx generate a kernel core dump though [1]. * linux-media-2011-12-25.tar.bz2 Same problem
Re: Hauppauge HVR-930C problems
On 10-01-2012 17:30, Mihai Dobrescu wrote: > Hello, > > Just compiled the latest again, but still no difference. > kaffeine doesn't see any source in channels dialog, two devices are in > 'Configure Television' dialog: DRXK DVB-C - device not connected - as > Device 1 and DRXK DVB-C DVB-T as Device 2. Concerning the last one, no > source is selected, as I am in Romania, which is not in the list > scan_w finds nothing. > > What should I do next? Kaffeine doesn't work with MFE tuners (at least not the version I have). It only sees one delivery system. If you're using the very latest version of the driver (the one at the media-build tree), you can use the dvb-fe-util tool to change the delivery system to DVB-C or to DVB-T. The tool is now part of the v4l-utils. You may also request a Kaffeine developer or to submit a patch for it, in order to add support on it to detect the frontend supported delivery systems and to change it dynamically. > > Regards, Mike. > > On Tue, Jan 10, 2012 at 4:42 PM, Fredrik Lingvall > wrote: >> On 12/25/11 16:56, Fredrik Lingvall wrote: >>> >>> On 12/18/11 10:20, Fredrik Lingvall wrote: On 12/17/11 20:53, Mihai Dobrescu wrote: > > > > > Mihai, > > I got some success. I did this, > > # cd /usr/src (for example) > > # git clone git://linuxtv.org/media_build.git > > # emerge dev-util/patchutils > # emerge Proc-ProcessTable > > # cd media_build > # ./build > # make install > > Which will install the latest driver on your running kernel (just in > case > make sure /usr/src/linux points to your running kernel sources). Then > reboot. > > You should now see that (among other) modules have loaded: > > # lsmod > > > > em28xx 93528 1 em28xx_dvb > v4l2_common 5254 1 em28xx > videobuf_vmalloc4167 1 em28xx > videobuf_core 15151 2 em28xx,videobuf_vmalloc > > Then try w_scan and dvbscan etc. I got mythtv to scan too now. There > were > some warnings and timeouts and I'm not sure if this is normal or not. > > You can also do a dmesg -c while scanning to monitor the changes en the > kernel log. > > Regards, > > /Fredrik > > > In my case I have: > > lsmod |grep em2 > em28xx_dvb 12608 0 > dvb_core 76187 1 em28xx_dvb > em28xx 82436 1 em28xx_dvb > v4l2_common 5087 1 em28xx > videodev 70123 2 em28xx,v4l2_common > videobuf_vmalloc3783 1 em28xx > videobuf_core 12991 2 em28xx,videobuf_vmalloc > rc_core11695 11 > > rc_hauppauge,ir_lirc_codec,ir_mce_kbd_decoder,ir_sanyo_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,em28xx,ir_nec_decoder > tveeprom 12441 1 em28xx > i2c_core 14232 9 > > xc5000,drxk,em28xx_dvb,em28xx,v4l2_common,videodev,tveeprom,nvidia,i2c_i801 > > yet, w_scan founds nothing. I was able to scan using the "media_build" install method described above but when trying to watch a free channel the image and sound was stuttering severly. I have tried both MythTV and mplayer with similar results. I created the channel list for mplayer with: lintv ~ # dvbscan -x0 -fc /usr/share/dvb/dvb-c/no-Oslo-Get -o zap > .mplayer/channels.conf And, for example, I get this output from mplayer plus a very (blocky) stuttering image and sound: lin-tv ~ # mplayer dvb://1@"TV8 Oslo" -ao jack >>> >>> I did some more tests with release snapshots 2011-12-13, 2011-12-21, and >>> 2011-12-25, respectively. I did this by changing >>> >>> LATEST_TAR := >>> http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2 >>> LATEST_TAR_MD5 := >>> http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2.md5 >>> >>> in linux/Makefile to the corresponding release. >>> >>> Results: >>> >>> * linux-media-2011-12-13.tar.bz2 >>> >>> The ./build script builds the drivers cleanly, scanning works, but >>> watching video does not work correctly. >>> >>> * linux-media-2011-12-21.tar.bz2 >>> >>> The ./build script fails at the as3645a.c file (on this machine but I can >>> build it on two other machines using the same kernel and kernel >>> 2.6.39-gentoo-r3, respectively). I can build it with make menuconfig etc >>> (where I disabled stuff I don't need, eg. disabling [ ] Media Controller API >>> (EXPERIMENTAL) ). The em28xx generate a kernel core dump though [1]. >>> >>> * linux-media-2011-12-25.tar.bz2 >>> >>> Same problem as 2011-12-21. >>> >>> Regards, >>> >>> /Fredrik >>> >> >> Here's some more test results. >> >> I have upgraded the kernel to 3.1.6-gentoo (where I enabled DVB when I build >> the kernel). Both >> >> http://linuxtv.org/downloads/drivers/linux-media-
Re: Hauppauge HVR-930C problems
Hello, Just compiled the latest again, but still no difference. kaffeine doesn't see any source in channels dialog, two devices are in 'Configure Television' dialog: DRXK DVB-C - device not connected - as Device 1 and DRXK DVB-C DVB-T as Device 2. Concerning the last one, no source is selected, as I am in Romania, which is not in the list scan_w finds nothing. What should I do next? Regards, Mike. On Tue, Jan 10, 2012 at 4:42 PM, Fredrik Lingvall wrote: > On 12/25/11 16:56, Fredrik Lingvall wrote: >> >> On 12/18/11 10:20, Fredrik Lingvall wrote: >>> >>> On 12/17/11 20:53, Mihai Dobrescu wrote: Mihai, I got some success. I did this, # cd /usr/src (for example) # git clone git://linuxtv.org/media_build.git # emerge dev-util/patchutils # emerge Proc-ProcessTable # cd media_build # ./build # make install Which will install the latest driver on your running kernel (just in case make sure /usr/src/linux points to your running kernel sources). Then reboot. You should now see that (among other) modules have loaded: # lsmod em28xx 93528 1 em28xx_dvb v4l2_common 5254 1 em28xx videobuf_vmalloc 4167 1 em28xx videobuf_core 15151 2 em28xx,videobuf_vmalloc Then try w_scan and dvbscan etc. I got mythtv to scan too now. There were some warnings and timeouts and I'm not sure if this is normal or not. You can also do a dmesg -c while scanning to monitor the changes en the kernel log. Regards, /Fredrik In my case I have: lsmod |grep em2 em28xx_dvb 12608 0 dvb_core 76187 1 em28xx_dvb em28xx 82436 1 em28xx_dvb v4l2_common 5087 1 em28xx videodev 70123 2 em28xx,v4l2_common videobuf_vmalloc 3783 1 em28xx videobuf_core 12991 2 em28xx,videobuf_vmalloc rc_core 11695 11 rc_hauppauge,ir_lirc_codec,ir_mce_kbd_decoder,ir_sanyo_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,em28xx,ir_nec_decoder tveeprom 12441 1 em28xx i2c_core 14232 9 xc5000,drxk,em28xx_dvb,em28xx,v4l2_common,videodev,tveeprom,nvidia,i2c_i801 yet, w_scan founds nothing. >>> >>> >>> I was able to scan using the "media_build" install method described above >>> but when trying to watch a free channel the image and sound was stuttering >>> severly. I have tried both MythTV and mplayer with similar results. >>> >>> I created the channel list for mplayer with: >>> >>> lintv ~ # dvbscan -x0 -fc /usr/share/dvb/dvb-c/no-Oslo-Get -o zap > >>> .mplayer/channels.conf >>> >>> And, for example, I get this output from mplayer plus a very (blocky) >>> stuttering image and sound: >>> >>> lin-tv ~ # mplayer dvb://1@"TV8 Oslo" -ao jack >>> >> >> I did some more tests with release snapshots 2011-12-13, 2011-12-21, and >> 2011-12-25, respectively. I did this by changing >> >> LATEST_TAR := >> http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2 >> LATEST_TAR_MD5 := >> http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2.md5 >> >> in linux/Makefile to the corresponding release. >> >> Results: >> >> * linux-media-2011-12-13.tar.bz2 >> >> The ./build script builds the drivers cleanly, scanning works, but >> watching video does not work correctly. >> >> * linux-media-2011-12-21.tar.bz2 >> >> The ./build script fails at the as3645a.c file (on this machine but I can >> build it on two other machines using the same kernel and kernel >> 2.6.39-gentoo-r3, respectively). I can build it with make menuconfig etc >> (where I disabled stuff I don't need, eg. disabling [ ] Media Controller API >> (EXPERIMENTAL) ). The em28xx generate a kernel core dump though [1]. >> >> * linux-media-2011-12-25.tar.bz2 >> >> Same problem as 2011-12-21. >> >> Regards, >> >> /Fredrik >> > > Here's some more test results. > > I have upgraded the kernel to 3.1.6-gentoo (where I enabled DVB when I build > the kernel). Both > > http://linuxtv.org/downloads/drivers/linux-media-2012-01-07.tar.bz2 > > and > > http://linuxtv.org/downloads/drivers/linux-media-2012-01-08.tar.bz2 > > now builds using the > > lin-tv ~ # cd /usr/src > lin-tv src # git clone git://linuxtv.org/media_build.git > lin-tv src # cd media_build > lin-tv media_build # ./build > lin-tv media_build # make install > > method. Scanning and (finally) watching video works but not flawlessly. > > I also suspect that I don't find all channels when I scan. I have scanned > using, > > * dvbscan -x 0 -fc /usr/share/dvb/dvb-c/no-Oslo-Get > .mplayer/channels.conf > * Kaffeine (1.2.2) > * MythTV (0.25_pre20120103) > > respectively. Both kaffeine and mythtv reports a very low signal level (0%) > and an SNR of only 1%. (k
Re: Hauppauge HVR-930C problems
On 12/25/11 16:56, Fredrik Lingvall wrote: On 12/18/11 10:20, Fredrik Lingvall wrote: On 12/17/11 20:53, Mihai Dobrescu wrote: Mihai, I got some success. I did this, # cd /usr/src (for example) # git clone git://linuxtv.org/media_build.git # emerge dev-util/patchutils # emerge Proc-ProcessTable # cd media_build # ./build # make install Which will install the latest driver on your running kernel (just in case make sure /usr/src/linux points to your running kernel sources). Then reboot. You should now see that (among other) modules have loaded: # lsmod em28xx 93528 1 em28xx_dvb v4l2_common 5254 1 em28xx videobuf_vmalloc4167 1 em28xx videobuf_core 15151 2 em28xx,videobuf_vmalloc Then try w_scan and dvbscan etc. I got mythtv to scan too now. There were some warnings and timeouts and I'm not sure if this is normal or not. You can also do a dmesg -c while scanning to monitor the changes en the kernel log. Regards, /Fredrik In my case I have: lsmod |grep em2 em28xx_dvb 12608 0 dvb_core 76187 1 em28xx_dvb em28xx 82436 1 em28xx_dvb v4l2_common 5087 1 em28xx videodev 70123 2 em28xx,v4l2_common videobuf_vmalloc3783 1 em28xx videobuf_core 12991 2 em28xx,videobuf_vmalloc rc_core11695 11 rc_hauppauge,ir_lirc_codec,ir_mce_kbd_decoder,ir_sanyo_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,em28xx,ir_nec_decoder tveeprom 12441 1 em28xx i2c_core 14232 9 xc5000,drxk,em28xx_dvb,em28xx,v4l2_common,videodev,tveeprom,nvidia,i2c_i801 yet, w_scan founds nothing. I was able to scan using the "media_build" install method described above but when trying to watch a free channel the image and sound was stuttering severly. I have tried both MythTV and mplayer with similar results. I created the channel list for mplayer with: lintv ~ # dvbscan -x0 -fc /usr/share/dvb/dvb-c/no-Oslo-Get -o zap > .mplayer/channels.conf And, for example, I get this output from mplayer plus a very (blocky) stuttering image and sound: lin-tv ~ # mplayer dvb://1@"TV8 Oslo" -ao jack I did some more tests with release snapshots 2011-12-13, 2011-12-21, and 2011-12-25, respectively. I did this by changing LATEST_TAR := http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2 LATEST_TAR_MD5 := http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2.md5 in linux/Makefile to the corresponding release. Results: * linux-media-2011-12-13.tar.bz2 The ./build script builds the drivers cleanly, scanning works, but watching video does not work correctly. * linux-media-2011-12-21.tar.bz2 The ./build script fails at the as3645a.c file (on this machine but I can build it on two other machines using the same kernel and kernel 2.6.39-gentoo-r3, respectively). I can build it with make menuconfig etc (where I disabled stuff I don't need, eg. disabling [ ] Media Controller API (EXPERIMENTAL) ). The em28xx generate a kernel core dump though [1]. * linux-media-2011-12-25.tar.bz2 Same problem as 2011-12-21. Regards, /Fredrik Here's some more test results. I have upgraded the kernel to 3.1.6-gentoo (where I enabled DVB when I build the kernel). Both http://linuxtv.org/downloads/drivers/linux-media-2012-01-07.tar.bz2 and http://linuxtv.org/downloads/drivers/linux-media-2012-01-08.tar.bz2 now builds using the lin-tv ~ # cd /usr/src lin-tv src # git clone git://linuxtv.org/media_build.git lin-tv src # cd media_build lin-tv media_build # ./build lin-tv media_build # make install method. Scanning and (finally) watching video works but not flawlessly. I also suspect that I don't find all channels when I scan. I have scanned using, * dvbscan -x 0 -fc /usr/share/dvb/dvb-c/no-Oslo-Get > .mplayer/channels.conf * Kaffeine (1.2.2) * MythTV (0.25_pre20120103) respectively. Both kaffeine and mythtv reports a very low signal level (0%) and an SNR of only 1%. (kaffeine). I'm not sure if the driver reports this correctly though. Whatching live TV works on some channels but not all. HD channels seems more difficult than SD channels, and I have not figured out why some channels work and some don't. I get Signal 0% | S/N 2.6dB | BE 0 | (_L_S) Partial Lock and no video on many channels in mythtv. Regards, /Fredrik -- 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: Hauppauge HVR-930C problems
On 12/18/11 10:20, Fredrik Lingvall wrote: On 12/17/11 20:53, Mihai Dobrescu wrote: Mihai, I got some success. I did this, # cd /usr/src (for example) # git clone git://linuxtv.org/media_build.git # emerge dev-util/patchutils # emerge Proc-ProcessTable # cd media_build # ./build # make install Which will install the latest driver on your running kernel (just in case make sure /usr/src/linux points to your running kernel sources). Then reboot. You should now see that (among other) modules have loaded: # lsmod em28xx 93528 1 em28xx_dvb v4l2_common 5254 1 em28xx videobuf_vmalloc4167 1 em28xx videobuf_core 15151 2 em28xx,videobuf_vmalloc Then try w_scan and dvbscan etc. I got mythtv to scan too now. There were some warnings and timeouts and I'm not sure if this is normal or not. You can also do a dmesg -c while scanning to monitor the changes en the kernel log. Regards, /Fredrik In my case I have: lsmod |grep em2 em28xx_dvb 12608 0 dvb_core 76187 1 em28xx_dvb em28xx 82436 1 em28xx_dvb v4l2_common 5087 1 em28xx videodev 70123 2 em28xx,v4l2_common videobuf_vmalloc3783 1 em28xx videobuf_core 12991 2 em28xx,videobuf_vmalloc rc_core11695 11 rc_hauppauge,ir_lirc_codec,ir_mce_kbd_decoder,ir_sanyo_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,em28xx,ir_nec_decoder tveeprom 12441 1 em28xx i2c_core 14232 9 xc5000,drxk,em28xx_dvb,em28xx,v4l2_common,videodev,tveeprom,nvidia,i2c_i801 yet, w_scan founds nothing. I was able to scan using the "media_build" install method described above but when trying to watch a free channel the image and sound was stuttering severly. I have tried both MythTV and mplayer with similar results. I created the channel list for mplayer with: lintv ~ # dvbscan -x0 -fc /usr/share/dvb/dvb-c/no-Oslo-Get -o zap > .mplayer/channels.conf And, for example, I get this output from mplayer plus a very (blocky) stuttering image and sound: lin-tv ~ # mplayer dvb://1@"TV8 Oslo" -ao jack I did some more tests with release snapshots 2011-12-13, 2011-12-21, and 2011-12-25, respectively. I did this by changing LATEST_TAR := http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2 LATEST_TAR_MD5 := http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2.md5 in linux/Makefile to the corresponding release. Results: * linux-media-2011-12-13.tar.bz2 The ./build script builds the drivers cleanly, scanning works, but watching video does not work correctly. * linux-media-2011-12-21.tar.bz2 The ./build script fails at the as3645a.c file (on this machine but I can build it on two other machines using the same kernel and kernel 2.6.39-gentoo-r3, respectively). I can build it with make menuconfig etc (where I disabled stuff I don't need, eg. disabling [ ] Media Controller API (EXPERIMENTAL) ). The em28xx generate a kernel core dump though [1]. * linux-media-2011-12-25.tar.bz2 Same problem as 2011-12-21. Regards, /Fredrik [1] [ 2231.881231] em28xx #0: chip ID is em2884 [ 2231.933025] em28xx #0: Identified as Hauppauge WinTV HVR 930C (card=81) [ 2231.933132] em28xx #0: Config register raw data: 0xcb [ 2231.933139] BUG: unable to handle kernel NULL pointer dereference at 0028 [ 2231.933325] IP: [] em28xx_wake_i2c+0x28/0xe0 [em28xx] [ 2231.933425] PGD 1181ef067 PUD 118383067 PMD 0 [ 2231.933513] Oops: [#1] PREEMPT SMP [ 2231.933601] CPU 0 [ 2231.933607] Modules linked in: em28xx(+) xc5000 coretemp drxk nvidia(P) dvb_core rc_hauppauge ir_lirc_codec lirc_dev ir_mce_kbd_decoder ir_sanyo_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder v4l2_common videobuf_vmalloc videobuf_core uvcvideo rc_core videobuf2_core videodev tveeprom media v4l2_compat_ioctl32 videobuf2_vmalloc videobuf2_memops firewire_ohci iwlagn firewire_core mac80211 crc_itu_t snd_hdsp snd_rawmidi e1000e [last unloaded: em28xx] [ 2231.934117] [ 2231.934117] Pid: 20150, comm: modprobe Tainted: P 3.0.6-gentoo #2 Dell Inc. Precision M2400 /0HT029 [ 2231.934117] RIP: 0010:[] [] em28xx_wake_i2c+0x28/0xe0 [em28xx] [ 2231.934117] RSP: 0018:88011a34fbc8 EFLAGS: 00010213 [ 2231.934117] RAX: RBX: RCX: [ 2231.934117] RDX: 81c13468 RSI: 0082 RDI: 8801184ca000 [ 2231.934117] RBP: 88011a34fbe8 R08: R09: [ 2231.934117] R10: R11: R12: 8801184ca038 [ 2231.934117] R13: 8801184ca000 R14: 8801184ca000 R15: 880119db0800 [ 2231.934117] FS: 7f1b79fc2700() GS:88011fc0() knlGS: [ 2231.934117] CS: 0010 DS: ES: CR0: 8005003b [ 2231.934117] CR2: 0028 CR3: 00011445f0
Re: Hauppauge HVR-930C problems
On 12/17/11 20:53, Mihai Dobrescu wrote: Mihai, I got some success. I did this, # cd /usr/src (for example) # git clone git://linuxtv.org/media_build.git # emerge dev-util/patchutils # emerge Proc-ProcessTable # cd media_build # ./build # make install Which will install the latest driver on your running kernel (just in case make sure /usr/src/linux points to your running kernel sources). Then reboot. You should now see that (among other) modules have loaded: # lsmod em28xx 93528 1 em28xx_dvb v4l2_common 5254 1 em28xx videobuf_vmalloc4167 1 em28xx videobuf_core 15151 2 em28xx,videobuf_vmalloc Then try w_scan and dvbscan etc. I got mythtv to scan too now. There were some warnings and timeouts and I'm not sure if this is normal or not. You can also do a dmesg -c while scanning to monitor the changes en the kernel log. Regards, /Fredrik In my case I have: lsmod |grep em2 em28xx_dvb 12608 0 dvb_core 76187 1 em28xx_dvb em28xx 82436 1 em28xx_dvb v4l2_common 5087 1 em28xx videodev 70123 2 em28xx,v4l2_common videobuf_vmalloc3783 1 em28xx videobuf_core 12991 2 em28xx,videobuf_vmalloc rc_core11695 11 rc_hauppauge,ir_lirc_codec,ir_mce_kbd_decoder,ir_sanyo_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,em28xx,ir_nec_decoder tveeprom 12441 1 em28xx i2c_core 14232 9 xc5000,drxk,em28xx_dvb,em28xx,v4l2_common,videodev,tveeprom,nvidia,i2c_i801 yet, w_scan founds nothing. I was able to scan using the "media_build" install method described above but when trying to watch a free channel the image and sound was stuttering severly. I have tried both MythTV and mplayer with similar results. I created the channel list for mplayer with: lintv ~ # dvbscan -x0 -fc /usr/share/dvb/dvb-c/no-Oslo-Get -o zap > .mplayer/channels.conf And, for example, I get this output from mplayer plus a very (blocky) stuttering image and sound: lin-tv ~ # mplayer dvb://1@"TV8 Oslo" -ao jack MPlayer SVN-r33094-4.5.3 (C) 2000-2011 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing dvb://1@TV8 Oslo. dvb_tune Freq: 30600 TS file format detected. VIDEO MPEG2(pid=1585) AUDIO MPA(pid=1586) NO SUBS (yet)! PROGRAM N. 0 VIDEO: MPEG2 720x576 (aspect 3) 25.000 fps 15000.0 kbps (1875.0 kbyte/s) == Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family Selected video codec: [ffmpeg2] vfm: ffmpeg (FFmpeg MPEG-2) == == Opening audio decoder: [mp3lib] MPEG layer-2, layer-3 AUDIO: 48000 Hz, 2 ch, s16le, 192.0 kbit/12.50% (ratio: 24000->192000) Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3) == AO: [jack] 48000Hz 2ch floatle (4 bytes per sample) Starting playback... Movie-Aspect is 1.78:1 - prescaling to correct movie aspect. VO: [xv] 720x576 => 1024x576 Planar YV12 [VO_XV] Shared memory not supported Reverting to normal Xv. [VO_XV] Shared memory not supported Reverting to normal Xv. [mpeg2video @ 0xac0bc0]ac-tex damaged at 10 0 [mpeg2video @ 0xac0bc0]skipped MB in I frame at 16 1 [mpeg2video @ 0xac0bc0]skipped MB in I frame at 26 3 [mpeg2video @ 0xac0bc0]ac-tex damaged at 26 6 [mpeg2video @ 0xac0bc0]ac-tex damaged at 12 10 [mpeg2video @ 0xac0bc0]invalid mb type in I Frame at 22 12 [mpeg2video @ 0xac0bc0]skipped MB in I frame at 44 13 [mpeg2video @ 0xac0bc0]ac-tex damaged at 28 16 [mpeg2video @ 0xac0bc0]ac-tex damaged at 4 17 [mpeg2video @ 0xac0bc0]skipped MB in I frame at 16 19 [mpeg2video @ 0xac0bc0]skipped MB in I frame at 14 20 [mpeg2video @ 0xac0bc0]skipped MB in I frame at 5 22 [mpeg2video @ 0xac0bc0]invalid mb type in I Frame at 6 23 [mpeg2video @ 0xac0bc0]ac-tex damaged at 16 24 [mpeg2video @ 0xac0bc0]ac-tex damaged at 5 25 [mpeg2video @ 0xac0bc0]skipped MB in I frame at 21 27 [mpeg2video @ 0xac0bc0]skipped MB in I frame at 42 28 [mpeg2video @ 0xac0bc0]ac-tex damaged at 24 31 [mpeg2video @ 0xac0bc0]invalid mb type in I Frame at 7 34 [mpeg2video @ 0xac0bc0]ac-tex damaged at 43 35 [mpeg2video @ 0xac0bc0]Warning MVs not available [mpeg2video @ 0xac0bc0]concealing 1296 DC, 1296 AC, 1296 MV errors [mpeg2video @ 0xac0bc0]concealing 1320 DC, 1320 AC, 1320 MV errors [mpeg2video @ 0xac0bc0]concealing 1320 DC, 1320 AC, 1320 MV errors [mpeg2video @ 0xac0bc0]concealing 1320 DC, 1320 AC, 1320 MV errors [mpeg2video @ 0xac0bc0]concealing 1320 DC, 1320 AC, 1320 MV errors [mpeg2video @ 0xac0bc0]ac-tex damaged at 44 7 [mpeg2video @ 0xac0bc0]invalid mb type in P Frame at 11 13 [mpeg2video @ 0
Re: Hauppauge HVR-930C problems
On Sat, Dec 17, 2011 at 9:53 PM, Mihai Dobrescu wrote: > On Sat, Dec 17, 2011 at 8:46 PM, Fredrik Lingvall > wrote: >> On 12/17/11 16:18, Fredrik Lingvall wrote: >> >> On 12/16/11 19:35, Mihai Dobrescu wrote: >> >> Please excuse the dumbness of the question, but, could you direct me >> to the repository having these patches applied? >> >> >> No it's not a dumpness question - I have struggeled with this too. >> >> First I got confused which kernel source to use. There are two git repos >> mentioned on the linuxtv.org site: >> >> 1) on http://linuxtv.org/repo/ >> >> ~ # git clone >> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git v4l-dvb >> >> and 2) on http://git.linuxtv.org/media_tree.git >> >> ~ # git clone git://github.com/torvalds/linux.git v4l-dvb >> >> >> I'm also a bit confused on how to get the linux-media tree. My guess was to >> do a >> >> # cd v4l-dvb >> # git remote add linuxtv git://linuxtv.org/media_tree.git >> # git remote update >> >> >> They also now and then create tar-files, and right know I'm testing the one >> from 2011-12-13, That is, >> >> ~ # cd /usr/src >> src # git clone git://github.com/torvalds/linux.git v4l-dvb >> src # wget >> http://linuxtv.org/downloads/drivers/linux-media-2011-12-13.tar.bz2 >> src # cd v4l-dvb >> v4l-dvb # tar xvjf ../linux-media-2011-12-13.tar.bz2 >> >> Then configure and build the kernel:make menuconfig (enable the drivers >> etc), make -j2 && make modules_install & make install >> and add the new kernel to lilo/grub etc and reboot. >> >> The media tree don't build cleanly on the stock Gentoo kernel (3.0.6) so >> that's why I'm using Linux' dev kernel (which is the one recommended on >> Linuxtv). However, not everything works with this kernel (I can't emerge >> virtualbox for example). >> >> /Fredrik >> >> Mihai, >> >> I got some success. I did this, >> >> # cd /usr/src (for example) >> >> # git clone git://linuxtv.org/media_build.git >> >> # emerge dev-util/patchutils >> # emerge Proc-ProcessTable >> >> # cd media_build >> # ./build >> # make install >> >> Which will install the latest driver on your running kernel (just in case >> make sure /usr/src/linux points to your running kernel sources). Then >> reboot. >> >> You should now see that (among other) modules have loaded: >> >> # lsmod >> >> >> >> em28xx 93528 1 em28xx_dvb >> v4l2_common 5254 1 em28xx >> videobuf_vmalloc 4167 1 em28xx >> videobuf_core 15151 2 em28xx,videobuf_vmalloc >> >> Then try w_scan and dvbscan etc. I got mythtv to scan too now. There were >> some warnings and timeouts and I'm not sure if this is normal or not. >> >> You can also do a dmesg -c while scanning to monitor the changes en the >> kernel log. >> >> Regards, >> >> /Fredrik >> >> > > In my case I have: > > lsmod |grep em2 > em28xx_dvb 12608 0 > dvb_core 76187 1 em28xx_dvb > em28xx 82436 1 em28xx_dvb > v4l2_common 5087 1 em28xx > videodev 70123 2 em28xx,v4l2_common > videobuf_vmalloc 3783 1 em28xx > videobuf_core 12991 2 em28xx,videobuf_vmalloc > rc_core 11695 11 > rc_hauppauge,ir_lirc_codec,ir_mce_kbd_decoder,ir_sanyo_decoder,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,em28xx,ir_nec_decoder > tveeprom 12441 1 em28xx > i2c_core 14232 9 > xc5000,drxk,em28xx_dvb,em28xx,v4l2_common,videodev,tveeprom,nvidia,i2c_i801 > > yet, w_scan founds nothing. Additionally: dmesg -c [139676.064539] usb 1-4: new high speed USB device number 8 using ehci_hcd [139676.180076] usb 1-4: New USB device found, idVendor=2040, idProduct=1605 [139676.180081] usb 1-4: New USB device strings: Mfr=0, Product=1, SerialNumber=2 [139676.180085] usb 1-4: Product: WinTV HVR-930C [139676.180087] usb 1-4: SerialNumber: 4034564214 [139676.646185] WARNING: You are using an experimental version of the media stack. [139676.646187] As the driver is backported to an older kernel, it doesn't offer [139676.646188] enough quality for its usage in production. [139676.646189] Use it with care. [139676.646190] Latest git patches (needed if you report a bug to linux-media@vger.kernel.org): [139676.646192] bcc072756e4467dc30e502a311b1c3adec96a0e4 [media] STV0900: Query DVB frontend delivery capabilities [139676.646193] 6bad3aeb8cc542b90ae62b35caca44305cd93ef5 [media] STV090x: Query DVB frontend delivery capabilities [139676.646195] 61d4f9c918c591e4f7970ef29bafb302664be466 [media] STB0899: Query DVB frontend delivery capabilities [139676.660297] IR NEC protocol handler initialized [139676.680225] Linux media interface: v0.10 [139676.683437] Linux video capture interface: v2.00 [139676.683440] WARNING: You are using an experimental version of the media stack. [139676.683442] As the driver is backported to an older kernel, it doesn't offer [139676.683443] enough quality for its usage in p
Re: Hauppauge HVR-930C problems
On Sat, Dec 17, 2011 at 5:18 PM, Fredrik Lingvall wrote: > On 12/16/11 19:35, Mihai Dobrescu wrote: > > Please excuse the dumbness of the question, but, could you direct me > to the repository having these patches applied? > > > No it's not a dumpness question - I have struggeled with this too. > > First I got confused which kernel source to use. There are two git repos > mentioned on the linuxtv.org site: > > 1) on http://linuxtv.org/repo/ > > ~ # git clone > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git v4l-dvb > > and 2) on http://git.linuxtv.org/media_tree.git > > ~ # git clone git://github.com/torvalds/linux.git v4l-dvb > > > I'm also a bit confused on how to get the linux-media tree. My guess was to > do a > > # cd v4l-dvb > # git remote add linuxtv git://linuxtv.org/media_tree.git > # git remote update > > > They also now and then create tar-files, and right know I'm testing the one > from 2011-12-13, That is, > > ~ # cd /usr/src > src # git clone git://github.com/torvalds/linux.git v4l-dvb > src # wget > http://linuxtv.org/downloads/drivers/linux-media-2011-12-13.tar.bz2 > src # cd v4l-dvb > v4l-dvb # tar xvjf ../linux-media-2011-12-13.tar.bz2 > > Then configure and build the kernel:make menuconfig (enable the drivers > etc), make -j2 && make modules_install & make install > and add the new kernel to lilo/grub etc and reboot. > > The media tree don't build cleanly on the stock Gentoo kernel (3.0.6) so > that's why I'm using Linux' dev kernel (which is the one recommended on > Linuxtv). However, not everything works with this kernel (I can't emerge > virtualbox for example). > > /Fredrik > Thank you. So, there would be no success on Sabayon 7 64 bit having kernel version 3.1? I would not rebuild all the kernel, just the media. Does this suffice? Mike -- 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: Hauppauge HVR-930C problems
On 12/10/11 17:02, Mauro Carvalho Chehab wrote: I noticed the new patches you are working with on the list. Let me know I there's something I can test? The patches that are pertinent are already at the main repository. It would be interesting if you could test it again with those patches, with both w_scan and scan. Regards, Mauro Success (I think :-). Tested the git://linuxtv.org/media_build.git method using the stock Gentoo 3.0.6 kernel. I got more channels with dvbscan (using the no-Oslo-Get profile) than with w_scan. There are some timeouts and warnings but that may be normal? lin-tv ~ # w_scan -fc -c NO w_scan version 20111011 (compiled for DVB API 5.2) using settings for NORWAY DVB cable DVB-C frontend_type DVB-C, channellist 7 output format vdr-1.6 WARNING: could not guess your codepage. Falling back to 'UTF-8' output charset 'UTF-8', use -C to override Info: using DVB adapter auto detection. /dev/dvb/adapter0/frontend0 -> DVB-C "DRXK DVB-C": good :-) /dev/dvb/adapter0/frontend1 -> DVB-T "DRXK DVB-T": specified was DVB-C -> SEARCH NEXT ONE. Using DVB-C frontend (adapter /dev/dvb/adapter0/frontend0) -_-_-_-_ Getting frontend capabilities-_-_-_-_ Using DVB API 5.5 frontend 'DRXK DVB-C' supports INVERSION_AUTO QAM_AUTO not supported, trying QAM_64 QAM_256. FEC_AUTO FREQ (47.00MHz ... 862.00MHz) SRATE (0.870MBd ... 11.700MBd) -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ searching QAM64... 73000: sr6900 (time: 00:07) sr6875 (time: 00:09) 81000: sr6900 (time: 00:12) sr6875 (time: 00:14) 113000: sr6900 (time: 00:17) sr6875 (time: 00:20) 121000: sr6900 (time: 00:22) sr6875 (time: 00:25) 129000: sr6900 (time: 00:27) sr6875 (time: 00:30) 137000: sr6900 (time: 00:32) sr6875 (time: 00:35) 145000: sr6900 (time: 00:37) sr6875 (time: 00:40) 153000: sr6900 (time: 00:42) sr6875 (time: 00:45) 161000: sr6900 (time: 00:48) sr6875 (time: 00:50) 169000: sr6900 (time: 00:53) sr6875 (time: 00:55) 314000: sr6900 (time: 00:58) sr6875 (time: 01:00) 322000: sr6900 (time: 01:03) sr6875 (time: 01:05) 33: sr6900 (time: 01:08) sr6875 (time: 01:10) 338000: sr6900 (time: 01:13) sr6875 (time: 01:15) 346000: sr6900 (time: 01:18) sr6875 (time: 01:21) 354000: sr6900 (time: 01:23) sr6875 (time: 01:26) 362000: sr6900 (time: 01:28) sr6875 (time: 01:31) 37: sr6900 (time: 01:33) sr6875 (time: 01:36) 378000: sr6900 (time: 01:38) sr6875 (time: 01:41) 386000: sr6900 (time: 01:43) sr6875 (time: 01:46) 394000: sr6900 (time: 01:48) sr6875 (time: 01:51) 402000: sr6900 (time: 01:54) sr6875 (time: 01:56) 41: sr6900 (time: 01:59) sr6875 (time: 02:01) 418000: sr6900 (time: 02:04) sr6875 (time: 02:06) 426000: sr6900 (time: 02:09) sr6875 (time: 02:11) 434000: sr6900 (time: 02:14) sr6875 (time: 02:16) 442000: sr6900 (time: 02:19) sr6875 (time: 02:21) 45: sr6900 (time: 02:24) sr6875 (time: 02:27) 458000: sr6900 (time: 02:29) sr6875 (time: 02:32) 466000: sr6900 (time: 02:34) sr6875 (time: 02:37) 474000: sr6900 (time: 02:39) sr6875 (time: 02:42) 482000: sr6900 (time: 02:44) sr6875 (time: 02:47) 49: sr6900 (time: 02:49) sr6875 (time: 02:52) 498000: sr6900 (time: 02:55) sr6875 (time: 02:57) 506000: sr6900 (time: 03:00) sr6875 (time: 03:02) 514000: sr6900 (time: 03:05) sr6875 (time: 03:07) 522000: sr6900 (time: 03:10) sr6875 (time: 03:12) 53: sr6900 (time: 03:15) sr6875 (time: 03:17) 538000: sr6900 (time: 03:20) sr6875 (time: 03:22) 546000: sr6900 (time: 03:25) sr6875 (time: 03:28) 554000: sr6900 (time: 03:30) sr6875 (time: 03:33) 562000: sr6900 (time: 03:35) sr6875 (time: 03:38) 57: sr6900 (time: 03:40) sr6875 (time: 03:43) 578000: sr6900 (time: 03:45) sr6875 (time: 03:48) 586000: sr6900 (time: 03:50) sr6875 (time: 03:53) 594000: sr6900 (time: 03:55) sr6875 (time: 03:58) 602000: sr6900 (time: 04:01) sr6875 (time: 04:03) 61: sr6900 (time: 04:06) sr6875 (time: 04:08) 618000: sr6900 (time: 04:11) sr6875 (time: 04:13) 626000: sr6900 (time: 04:16) sr6875 (time: 04:18) 634000: sr6900 (time: 04:21) sr6875 (time: 04:23) 642000: sr6900 (time: 04:26) sr6875 (time: 04:29) 65: sr6900 (time: 04:31) sr6875 (time: 04:34) 658000: sr6900 (time: 04:36) sr6875 (time: 04:39) 666000: sr6900 (time: 04:41) sr6875 (time: 04:44) 674000: sr6900 (time: 04:46) sr6875 (time: 04:49) 682000: sr6900 (time: 04:51) sr6875 (time: 04:54) 69: sr6900 (time: 04:56) sr6875 (time: 04:59) 698000: sr6900 (time: 05:02) sr6875 (time: 05:04) 706000: sr6900 (time: 05:07) sr6875 (time: 05:09) 714000: sr6900 (time: 05:12) sr6875 (time: 05:14) 722000: sr6900 (time: 05:17) sr6875 (time: 05:19) 73: sr6900 (time: 05:22) sr6875 (time: 05:24) 738000: sr6900 (time: 05:27) sr6875 (time: 05:29) 746000: sr6900 (time: 05:32) sr6875 (time: 05:35) 754000: sr6900 (time: 05:37) sr6875 (time: 05:40) 762000: sr6900 (time: 05:42) sr6875 (time: 05:45) 77: sr6900 (time: 05:47) sr6875 (time: 05:50) 778000: sr6900 (time: 05:52) sr6875 (time: 05:55) 786000: sr6900 (time: 05:57) sr6875 (time: 06:00) 794000: sr6900 (time: 06:02) sr6875 (time: 06:0
Re: Hauppauge HVR-930C problems
On 12/15/11 10:08, Mihai Dobrescu wrote: Hello Fredrik, I have extracted the firmware, but I've noticed there are 2 versions, one for 32 bit and one for 64 bit. Which one should it be? There is probably a 64-bit and a 32-bit Windows driver but the firmware should be the same I think. My OS is 64 bit, I use the kernel sys-kernel/linux-sabayon-3.1-r2: uname --all Linux USC 3.1.0-sabayon #1 SMP Wed Nov 30 10:37:12 UTC 2011 x86_64 Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux I have successfully compiled the sources from media_build taking the latest sources I've found, using: git clone git://linuxtv.org/media_build.git Also, what to do next? I've tried w_scan: w_scan -fc -c RO -k w_scan version 20101204 (compiled for DVB API 5.2) using settings for ROMANIA Country identifier RO not defined. Using defaults. frontend_type DVB-C, channellist 4 output format kaffeine channels.dvb Info: using DVB adapter auto detection. /dev/dvb/adapter0/frontend0 -> DVB-C "DRXK DVB-C": good :-) /dev/dvb/adapter0/frontend1 -> DVB-T "DRXK DVB-T": specified was DVB-C -> SEARCH NEXT ONE. Using DVB-C frontend (adapter /dev/dvb/adapter0/frontend0) -_-_-_-_ Getting frontend capabilities-_-_-_-_ Using DVB API 5.5 frontend DRXK DVB-C supports INVERSION_AUTO QAM_AUTO not supported, trying QAM_64. FEC_AUTO -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ searching QAM64... 177500: sr6900 (time: 00:07) sr6875 (time: 00:10) 184500: sr6900 (time: 00:12) sr6875 (time: 00:15) 191500: sr6900 (time: 00:18) sr6875 (time: 00:20) 198500: sr6900 (time: 00:23) sr6875 (time: 00:25) 205500: sr6900 (time: 00:28) sr6875 (time: 00:30) 212500: sr6900 (time: 00:33) sr6875 (time: 00:35) 219500: sr6900 (time: 00:38) sr6875 (time: 00:40) 226500: sr6900 (time: 00:43) sr6875 (time: 00:46) 474000: sr6900 (time: 00:48) sr6875 (time: 00:51) 482000: sr6900 (time: 00:53) sr6875 (time: 00:56) 49: sr6900 (time: 00:58) sr6875 (time: 01:01) 498000: sr6900 (time: 01:03) sr6875 (time: 01:06) 506000: sr6900 (time: 01:08) sr6875 (time: 01:11) 514000: sr6900 (time: 01:13) sr6875 (time: 01:16) 522000: sr6900 (time: 01:19) sr6875 (time: 01:21) 53: sr6900 (time: 01:24) sr6875 (time: 01:26) 538000: sr6900 (time: 01:29) sr6875 (time: 01:31) 546000: sr6900 (time: 01:34) sr6875 (time: 01:36) 554000: sr6900 (time: 01:39) sr6875 (time: 01:41) 562000: sr6900 (time: 01:44) sr6875 (time: 01:46) 57: sr6900 (time: 01:49) sr6875 (time: 01:52) 578000: sr6900 (time: 01:54) sr6875 (time: 01:57) 586000: sr6900 (time: 01:59) sr6875 (time: 02:02) 594000: sr6900 (time: 02:04) sr6875 (time: 02:07) 602000: sr6900 (time: 02:09) sr6875 (time: 02:12) 61: sr6900 (time: 02:14) sr6875 (time: 02:17) 618000: sr6900 (time: 02:19) sr6875 (time: 02:22) 626000: sr6900 (time: 02:25) sr6875 (time: 02:27) 634000: sr6900 (time: 02:30) sr6875 (time: 02:32) 642000: sr6900 (time: 02:35) sr6875 (time: 02:37) 65: sr6900 (time: 02:40) sr6875 (time: 02:42) 658000: sr6900 (time: 02:45) sr6875 (time: 02:47) 666000: sr6900 (time: 02:50) sr6875 (time: 02:53) 674000: sr6900 (time: 02:55) sr6875 (time: 02:58) 682000: sr6900 (time: 03:00) sr6875 (time: 03:03) 69: sr6900 (time: 03:05) sr6875 (time: 03:08) 698000: sr6900 (time: 03:10) sr6875 (time: 03:13) 706000: sr6900 (time: 03:15) sr6875 (time: 03:18) 714000: sr6900 (time: 03:20) sr6875 (time: 03:23) 722000: sr6900 (time: 03:26) sr6875 (time: 03:28) 73: sr6900 (time: 03:31) sr6875 (time: 03:33) 738000: sr6900 (time: 03:36) sr6875 (time: 03:38) 746000: sr6900 (time: 03:41) sr6875 (time: 03:43) 754000: sr6900 (time: 03:46) sr6875 (time: 03:48) 762000: sr6900 (time: 03:51) sr6875 (time: 03:53) 77: sr6900 (time: 03:56) sr6875 (time: 03:59) 778000: sr6900 (time: 04:01) sr6875 (time: 04:04) 786000: sr6900 (time: 04:06) sr6875 (time: 04:09) 794000: sr6900 (time: 04:11) sr6875 (time: 04:14) 802000: sr6900 (time: 04:16) sr6875 (time: 04:19) 81: sr6900 (time: 04:21) sr6875 (time: 04:24) 818000: sr6900 (time: 04:27) sr6875 (time: 04:29) 826000: sr6900 (time: 04:32) sr6875 (time: 04:34) 834000: sr6900 (time: 04:37) sr6875 (time: 04:39) 842000: sr6900 (time: 04:42) sr6875 (time: 04:44) 85: sr6900 (time: 04:47) sr6875 (time: 04:49) 858000: sr6900 (time: 04:52) sr6875 (time: 04:54) ERROR: Sorry - i couldn't get any working frequency/transponder Nothing to scan!! There are unencrypted channels, as I receive them under Windows. I have had the same problem with scanning on the 930C. There has been several new patches commited to the git tree the last couple of weeks so try the latest driver from git. I had no time this week to test it but I will test this too next week. And, I recommend that you CC the linux-media list with as detailed reports as possible of your tests so the poeple working on it get the test results. Regards, /Fredrik -- 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.k
Re: Hauppauge HVR-930C problems
On 15-12-2011 06:04, Fredrik Lingvall wrote:
> On 12/14/11 17:33, Mihai Dobrescu wrote:
>> Hello,
>>
>> I need to make my tunner working too.
>> Did you make it work?
>> Where did you get the firmware (dvb-usb-hauppauge-hvr930c-drxk.fw)?
>> I have Sabayon 7 64 bit, which is sort of Gentoo, as I've seen you have.
>>
>> Thank you.
> Hi Mihai,
>
> There is a perl script get_dvb_firmware that downloads the firmware and
> extract it (from the Windows driver I think). You need a version of
> get_dvb_firmware where this has been added:
>
> +sub drxk_hauppauge_hvr930c {
> +my $url = "http://www.wintvcd.co.uk/drivers/";;
> +my $zipfile = "HVR-9x0_5_10_325_28153_SIGNED.zip";
> +my $hash = "83ab82e7e9480ec8bf1ae0155ca63c88";
> +my $tmpdir = tempdir(DIR => "/tmp", CLEANUP => 1);
> +my $drvfile = "HVR-900/emOEM.sys";
> +my $fwfile = "dvb-usb-hauppauge-hvr930c-drxk.fw";
> +
> +checkstandard();
> +
> +wgetfile($zipfile, $url . $zipfile);
> +verify($zipfile, $hash);
> +unzip($zipfile, $tmpdir);
> +extract("$tmpdir/$drvfile", 0x117b0, 42692, "$fwfile");
> +
> +"$fwfile"
> +}
> +
>
> Do a git checkout of the linux-media tree to get it (I think).
>
> Also, before I found the perl script I did it "manually" using:
>
> 1)
>
> wget http://www.wintvcd.co.uk/drivers/HVR-9x0_5_10_325_28153_SIGNED.zip
>
> 2) unzip it
>
> 3) extact it with dd [0x117b (hex) = 71600 (dec)]:
>
> dd if=HVR-900/emOEM.sys of=dvb-usb-hauppauge-hvr930c-drxk.fw bs=1 skip=71600
> count=42692
This is basically what the script does, with one difference:
it will double check if the extracted binary blob is really a firmware,
by comparing it with a known hash value. This way, if the driver there gots
updated, the script will fail, instead of writing some random values to a
.fw file.
>
> 4) copy it to the firmware dir
>
> cp dvb-usb-hauppauge-hvr930c-drxk.fw /lib/firmware/'
>
> HTH
>
> /Fredrik
>
> --
> 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
--
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: Hauppauge HVR-930C problems
On 12/14/11 17:33, Mihai Dobrescu wrote:
Hello,
I need to make my tunner working too.
Did you make it work?
Where did you get the firmware (dvb-usb-hauppauge-hvr930c-drxk.fw)?
I have Sabayon 7 64 bit, which is sort of Gentoo, as I've seen you have.
Thank you.
Hi Mihai,
There is a perl script get_dvb_firmware that downloads the firmware and
extract it (from the Windows driver I think). You need a version of
get_dvb_firmware where this has been added:
+sub drxk_hauppauge_hvr930c {
+my $url = "http://www.wintvcd.co.uk/drivers/";;
+my $zipfile = "HVR-9x0_5_10_325_28153_SIGNED.zip";
+my $hash = "83ab82e7e9480ec8bf1ae0155ca63c88";
+my $tmpdir = tempdir(DIR => "/tmp", CLEANUP => 1);
+my $drvfile = "HVR-900/emOEM.sys";
+my $fwfile = "dvb-usb-hauppauge-hvr930c-drxk.fw";
+
+checkstandard();
+
+wgetfile($zipfile, $url . $zipfile);
+verify($zipfile, $hash);
+unzip($zipfile, $tmpdir);
+extract("$tmpdir/$drvfile", 0x117b0, 42692, "$fwfile");
+
+"$fwfile"
+}
+
Do a git checkout of the linux-media tree to get it (I think).
Also, before I found the perl script I did it "manually" using:
1)
wget http://www.wintvcd.co.uk/drivers/HVR-9x0_5_10_325_28153_SIGNED.zip
2) unzip it
3) extact it with dd [0x117b (hex) = 71600 (dec)]:
dd if=HVR-900/emOEM.sys of=dvb-usb-hauppauge-hvr930c-drxk.fw bs=1
skip=71600 count=42692
4) copy it to the firmware dir
cp dvb-usb-hauppauge-hvr930c-drxk.fw /lib/firmware/'
HTH
/Fredrik
--
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: Hauppauge HVR-930C problems
On 10-12-2011 11:43, Fredrik Lingvall wrote:
On 12/08/11 16:02, Mauro Carvalho Chehab wrote:
#!/bin/bash
for i in `seq 1 20`;
do
w_scan -fc -c NO 1>> scan$i.log 2>> scan$i.log
done
And I get outputs like this (the timing numbers differs of course somewhat
between different runs):
586000: sr6900 (time: 10:21) sr6875 (time: 10:23)
594000: sr6900 (time: 10:26) sr6875 (time: 10:28)
602000: sr6900 (time: 10:31) (time: 10:32) signal ok:
QAM_256 f = 602000 kHz S6900C999
Info: NIT(actual) filter timeout
61: sr6900 (time: 10:44) sr6875 (time: 10:47)
618000: sr6900 (time: 10:49) sr6875 (time: 10:52)
626000: sr6900 (time: 10:54) sr6875 (time: 10:57)
Then I did the test that you suggested:
lin-tv ~ # strace -e ioctl dvbscan -fc test_channel_file
scanning test_channel_file
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
ioctl(3, FE_GET_INFO, 0x60b180) = 0
initial transponder 60200 690 0 5
>>> tune to: 60200:INVERSION_AUTO:690:FEC_NONE:QAM_256
ioctl(3, FE_SET_FRONTEND, 0x7fff0581fb20) = 0
ioctl(3, FE_READ_STATUS, 0x7fff0581fb4c) = 0
ioctl(3, FE_READ_STATUS, 0x7fff0581fb4c) = 0
ioctl(4, DMX_SET_FILTER, 0x7fff0581e930) = 0
ioctl(5, DMX_SET_FILTER, 0x7fff0581e930) = 0
ioctl(6, DMX_SET_FILTER, 0x7fff0581e930) = 0
WARNING: filter timeout pid 0x0011
ioctl(5, DMX_STOP, 0x23) = 0
WARNING: filter timeout pid 0x
ioctl(4, DMX_STOP, 0x23) = 0
WARNING: filter timeout pid 0x0010
ioctl(6, DMX_STOP, 0x23) = 0
dumping lists (0 services)
Done.
I did not get the:
602000: sr6900 (time: 10:32) (time: 10:33) signal ok:
QAM_256 f = 602000 kHz S6900C999
start_filter:1415: ERROR: ioctl DMX_SET_FILTER failed: 28 No space left on
device
Info: NIT(actual) filter timeout
that I got before. The changes I made from before was 1) I unmounted the USB
disk and 2) I rebuild the xc5000 module where I removed the
mutex_lock(&xc5000_list_mutex);
and
mutex_unlock(&xc5000_list_mutex);
lines according to the discussion in the " ... em28xx: initial support for HAUPPAUGE
HVR-930C again" thread.
Ok, let's go by parts.
1) error 28 at DMX_SET_FILTER is really due to lack of space at the USB bus.
I've
double-checked at the code. The only place there where it could occur is when
dvb_dmxdev_feed_start() calls feed->ts->start_filtering(feed->ts), with should
be
pointing to em28xx_start_feed(), with tries to start the transfer URB's at
em28xx_init_isoc() by calling usb_submit_urb(). This is the only routine that
returns
ENOSPC on this chain.
It is very likely that what fixed it were the removal of the USB disk.
2) There is an error at the bandwidth calculus on xc5000. It is likely that it
is
using a 6MHz bandwidth filter, instead of a 8MHz one.
Please try the enclosed patch.
[media] xc5000,tda18271c2dd: Fix bandwidth calculus
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/common/tuners/xc5000.c
b/drivers/media/common/tuners/xc5000.c
index ecd1f95..8279c45 100644
--- a/drivers/media/common/tuners/xc5000.c
+++ b/drivers/media/common/tuners/xc5000.c
@@ -708,9 +708,9 @@ static int xc5000_set_params(struct dvb_frontend *fe,
* is equal to 0.15 for Annex A, and 0.13 for annex C
*/
if (fe->dtv_property_cache.rolloff == ROLLOFF_13)
- bw = (params->u.qam.symbol_rate * 13) / 10;
+ bw = (params->u.qam.symbol_rate * 113) / 100;
else
- bw = (params->u.qam.symbol_rate * 15) / 10;
+ bw = (params->u.qam.symbol_rate * 115) / 100;
if (bw <= 600) {
priv->bandwidth = BANDWIDTH_6_MHZ;
priv->video_standard = DTV6;
diff --git a/drivers/media/dvb/frontends/tda18271c2dd.c
b/drivers/media/dvb/frontends/tda18271c2dd.c
index de544f6..b66ca29 100644
--- a/drivers/media/dvb/frontends/tda18271c2dd.c
+++ b/drivers/media/dvb/frontends/tda18271c2dd.c
@@ -1158,9 +1158,9 @@ static int set_params(struct dvb_frontend *fe,
* is equal to 0.15 for Annex A, and 0.13 for annex C
*/
if (fe->dtv_property_cache.rolloff == ROLLOFF_13)
- bw = (params->u.qam.symbol_rate * 13) / 10;
+ bw = (params->u.qam.symbol_rate * 113) / 100;
else
- bw = (params->u.qam.symbol_rate * 15) / 10;
+ bw = (params->u.qam.symbol_rate * 115) / 100;
if (bw <= 600)
Standard = HF_DVBC_6MHZ;
else if (bw <= 700)
Changing 13 -> 113 and 15 -> 115 in the two files made no difference. However,
I figured out that the
586000: sr6900 (time: 10:22) sr6875 (time: 10:24)
594000: sr6900 (time: 10:27) sr6875 (time: 10:30)
602000: sr6900 (time: 10:32) (time: 10:33) signal ok:
QAM_256 f = 602000 kHz S6900C999
start_filter:1417: ERROR: ioctl DMX_SET_FILTER failed: 28 No space left on
device
Info: NIT(actual) filter timeout
61: sr6900 (time: 10:55) sr6875 (time: 10:57)
618000: sr6900 (time: 11:00) sr6875 (time: 11:02)
626000: sr6900 (time: 11:05) sr6875 (time: 11:07)
output from w_scan only happends the first time after the driver has been
loaded. That is, running this script
#!/bin/bash
for i in `seq 1 20`;
do
rmmod em28xx_dvb
rmmod em28xx
sleep 5
modprobe em28xx
sleep 5
echo $i
w_scan -fc -c NO 1>> scan_out$i.log 2>> scan_err$i.lo
Re: Hauppauge HVR-930C problems
On 12/08/11 16:02, Mauro Carvalho Chehab wrote:
#!/bin/bash
for i in `seq 1 20`;
do
w_scan -fc -c NO 1>> scan$i.log 2>> scan$i.log
done
And I get outputs like this (the timing numbers differs of course
somewhat between different runs):
586000: sr6900 (time: 10:21) sr6875 (time: 10:23)
594000: sr6900 (time: 10:26) sr6875 (time: 10:28)
602000: sr6900 (time: 10:31) (time: 10:32) signal ok:
QAM_256 f = 602000 kHz S6900C999
Info: NIT(actual) filter timeout
61: sr6900 (time: 10:44) sr6875 (time: 10:47)
618000: sr6900 (time: 10:49) sr6875 (time: 10:52)
626000: sr6900 (time: 10:54) sr6875 (time: 10:57)
Then I did the test that you suggested:
lin-tv ~ # strace -e ioctl dvbscan -fc test_channel_file
scanning test_channel_file
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
ioctl(3, FE_GET_INFO, 0x60b180) = 0
initial transponder 60200 690 0 5
>>> tune to: 60200:INVERSION_AUTO:690:FEC_NONE:QAM_256
ioctl(3, FE_SET_FRONTEND, 0x7fff0581fb20) = 0
ioctl(3, FE_READ_STATUS, 0x7fff0581fb4c) = 0
ioctl(3, FE_READ_STATUS, 0x7fff0581fb4c) = 0
ioctl(4, DMX_SET_FILTER, 0x7fff0581e930) = 0
ioctl(5, DMX_SET_FILTER, 0x7fff0581e930) = 0
ioctl(6, DMX_SET_FILTER, 0x7fff0581e930) = 0
WARNING: filter timeout pid 0x0011
ioctl(5, DMX_STOP, 0x23) = 0
WARNING: filter timeout pid 0x
ioctl(4, DMX_STOP, 0x23) = 0
WARNING: filter timeout pid 0x0010
ioctl(6, DMX_STOP, 0x23) = 0
dumping lists (0 services)
Done.
I did not get the:
602000: sr6900 (time: 10:32) (time: 10:33) signal ok:
QAM_256 f = 602000 kHz S6900C999
start_filter:1415: ERROR: ioctl DMX_SET_FILTER failed: 28 No space
left on device
Info: NIT(actual) filter timeout
that I got before. The changes I made from before was 1) I unmounted
the USB disk and 2) I rebuild the xc5000 module where I removed the
mutex_lock(&xc5000_list_mutex);
and
mutex_unlock(&xc5000_list_mutex);
lines according to the discussion in the " ... em28xx: initial
support for HAUPPAUGE HVR-930C again" thread.
Ok, let's go by parts.
1) error 28 at DMX_SET_FILTER is really due to lack of space at the
USB bus. I've
double-checked at the code. The only place there where it could occur
is when
dvb_dmxdev_feed_start() calls feed->ts->start_filtering(feed->ts),
with should be
pointing to em28xx_start_feed(), with tries to start the transfer
URB's at
em28xx_init_isoc() by calling usb_submit_urb(). This is the only
routine that returns
ENOSPC on this chain.
It is very likely that what fixed it were the removal of the USB disk.
2) There is an error at the bandwidth calculus on xc5000. It is
likely that it is
using a 6MHz bandwidth filter, instead of a 8MHz one.
Please try the enclosed patch.
[media] xc5000,tda18271c2dd: Fix bandwidth calculus
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/common/tuners/xc5000.c
b/drivers/media/common/tuners/xc5000.c
index ecd1f95..8279c45 100644
--- a/drivers/media/common/tuners/xc5000.c
+++ b/drivers/media/common/tuners/xc5000.c
@@ -708,9 +708,9 @@ static int xc5000_set_params(struct dvb_frontend *fe,
* is equal to 0.15 for Annex A, and 0.13 for annex C
*/
if (fe->dtv_property_cache.rolloff == ROLLOFF_13)
-bw = (params->u.qam.symbol_rate * 13) / 10;
+bw = (params->u.qam.symbol_rate * 113) / 100;
else
-bw = (params->u.qam.symbol_rate * 15) / 10;
+bw = (params->u.qam.symbol_rate * 115) / 100;
if (bw <= 600) {
priv->bandwidth = BANDWIDTH_6_MHZ;
priv->video_standard = DTV6;
diff --git a/drivers/media/dvb/frontends/tda18271c2dd.c
b/drivers/media/dvb/frontends/tda18271c2dd.c
index de544f6..b66ca29 100644
--- a/drivers/media/dvb/frontends/tda18271c2dd.c
+++ b/drivers/media/dvb/frontends/tda18271c2dd.c
@@ -1158,9 +1158,9 @@ static int set_params(struct dvb_frontend *fe,
* is equal to 0.15 for Annex A, and 0.13 for annex C
*/
if (fe->dtv_property_cache.rolloff == ROLLOFF_13)
-bw = (params->u.qam.symbol_rate * 13) / 10;
+bw = (params->u.qam.symbol_rate * 113) / 100;
else
-bw = (params->u.qam.symbol_rate * 15) / 10;
+bw = (params->u.qam.symbol_rate * 115) / 100;
if (bw <= 600)
Standard = HF_DVBC_6MHZ;
else if (bw <= 700)
Changing 13 -> 113 and 15 -> 115 in the two files made no difference.
However, I figured out that the
586000: sr6900 (time: 10:22) sr6875 (time: 10:24)
594000: sr6900 (time: 10:27) sr6875 (time: 10:30)
602000: sr6900 (time: 10:32) (time: 10:33) signal ok:
QAM_256 f = 602000 kHz S6900C999
start_filter:1417: ERROR: ioctl DMX_SET_FILTER failed: 28 No space left
on device
Info: NIT(actual) filter timeout
61: sr6900 (time: 10:55) sr6875 (time: 10:57)
618000: sr6900 (time: 11:00) sr6875 (time: 11:02)
626000: sr6900 (time: 11:05) sr6875 (time: 11:07)
output from w_scan o
Re: Hauppauge HVR-930C problems
On 08-12-2011 06:31, Fredrik Lingvall wrote:
On 12/07/11 15:54, Mauro Carvalho Chehab wrote:
lin-tv ~ # lsusb | grep "Bus 002"
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 008: ID 2040:1605 Hauppauge
There's nothing at the DVB core returning -ENOSPC.
Try to add just one line to a channels file, like this one:
C 60200 690 NONE QAM256
(this is the transponder that failed with w_scan. You could also use one
of the transponders where you got a pid timeout with scan)
Then call scan with this file, using strace:
$ strace -e ioctl dvbscan channelfile
This would allow to see what ioctl returned -ENOSPC (error -28).
Regards,
Mauro
Mauro,
I made a small script to check if the w_scan results are consistent:
#!/bin/bash
for i in `seq 1 20`;
do
w_scan -fc -c NO 1>> scan$i.log 2>> scan$i.log
done
And I get outputs like this (the timing numbers differs of course somewhat
between different runs):
586000: sr6900 (time: 10:21) sr6875 (time: 10:23)
594000: sr6900 (time: 10:26) sr6875 (time: 10:28)
602000: sr6900 (time: 10:31) (time: 10:32) signal ok:
QAM_256 f = 602000 kHz S6900C999
Info: NIT(actual) filter timeout
61: sr6900 (time: 10:44) sr6875 (time: 10:47)
618000: sr6900 (time: 10:49) sr6875 (time: 10:52)
626000: sr6900 (time: 10:54) sr6875 (time: 10:57)
Then I did the test that you suggested:
lin-tv ~ # strace -e ioctl dvbscan -fc test_channel_file
scanning test_channel_file
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
ioctl(3, FE_GET_INFO, 0x60b180) = 0
initial transponder 60200 690 0 5
>>> tune to: 60200:INVERSION_AUTO:690:FEC_NONE:QAM_256
ioctl(3, FE_SET_FRONTEND, 0x7fff0581fb20) = 0
ioctl(3, FE_READ_STATUS, 0x7fff0581fb4c) = 0
ioctl(3, FE_READ_STATUS, 0x7fff0581fb4c) = 0
ioctl(4, DMX_SET_FILTER, 0x7fff0581e930) = 0
ioctl(5, DMX_SET_FILTER, 0x7fff0581e930) = 0
ioctl(6, DMX_SET_FILTER, 0x7fff0581e930) = 0
WARNING: filter timeout pid 0x0011
ioctl(5, DMX_STOP, 0x23) = 0
WARNING: filter timeout pid 0x
ioctl(4, DMX_STOP, 0x23) = 0
WARNING: filter timeout pid 0x0010
ioctl(6, DMX_STOP, 0x23) = 0
dumping lists (0 services)
Done.
I did not get the:
602000: sr6900 (time: 10:32) (time: 10:33) signal ok:
QAM_256 f = 602000 kHz S6900C999
start_filter:1415: ERROR: ioctl DMX_SET_FILTER failed: 28 No space left on
device
Info: NIT(actual) filter timeout
that I got before. The changes I made from before was 1) I unmounted the USB
disk and 2) I rebuild the xc5000 module where I removed the
mutex_lock(&xc5000_list_mutex);
and
mutex_unlock(&xc5000_list_mutex);
lines according to the discussion in the " ... em28xx: initial support for HAUPPAUGE
HVR-930C again" thread.
Ok, let's go by parts.
1) error 28 at DMX_SET_FILTER is really due to lack of space at the USB bus.
I've
double-checked at the code. The only place there where it could occur is when
dvb_dmxdev_feed_start() calls feed->ts->start_filtering(feed->ts), with should
be
pointing to em28xx_start_feed(), with tries to start the transfer URB's at
em28xx_init_isoc() by calling usb_submit_urb(). This is the only routine that
returns
ENOSPC on this chain.
It is very likely that what fixed it were the removal of the USB disk.
2) There is an error at the bandwidth calculus on xc5000. It is likely that it
is
using a 6MHz bandwidth filter, instead of a 8MHz one.
Please try the enclosed patch.
[media] xc5000,tda18271c2dd: Fix bandwidth calculus
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/common/tuners/xc5000.c
b/drivers/media/common/tuners/xc5000.c
index ecd1f95..8279c45 100644
--- a/drivers/media/common/tuners/xc5000.c
+++ b/drivers/media/common/tuners/xc5000.c
@@ -708,9 +708,9 @@ static int xc5000_set_params(struct dvb_frontend *fe,
* is equal to 0.15 for Annex A, and 0.13 for annex C
*/
if (fe->dtv_property_cache.rolloff == ROLLOFF_13)
- bw = (params->u.qam.symbol_rate * 13) / 10;
+ bw = (params->u.qam.symbol_rate * 113) / 100;
else
- bw = (params->u.qam.symbol_rate * 15) / 10;
+ bw = (params->u.qam.symbol_rate * 115) / 100;
if (bw <= 600) {
priv->bandwidth = BANDWIDTH_6_MHZ;
priv->video_standard = DTV6;
diff --git a/drivers/media/dvb/frontends/tda18271c2dd.c
b/drivers/media/dvb/frontends/tda18271c2dd.c
index de544f6..b66ca29 100644
--- a/drivers/media/dvb/frontends/tda18271c2dd.c
+++ b/drivers/media/dvb/frontends/tda18271c2dd.c
@@ -1158,9 +1158,9 @@ static int set_params(struct dvb_frontend *fe,
* is equal to 0.15 for Annex A, and 0.13 for annex C
*/
if (fe->dtv_property_cache.rolloff == ROLLOFF_13)
- bw = (params->u.qam.symbol_rate * 13) / 1
Re: Hauppauge HVR-930C problems
On 12/07/11 15:54, Mauro Carvalho Chehab wrote: lin-tv ~ # lsusb | grep "Bus 002" Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 008: ID 2040:1605 Hauppauge There's nothing at the DVB core returning -ENOSPC. Try to add just one line to a channels file, like this one: C 60200 690 NONE QAM256 (this is the transponder that failed with w_scan. You could also use one of the transponders where you got a pid timeout with scan) Then call scan with this file, using strace: $ strace -e ioctl dvbscan channelfile This would allow to see what ioctl returned -ENOSPC (error -28). Regards, Mauro Mauro, I made a small script to check if the w_scan results are consistent: #!/bin/bash for i in `seq 1 20`; do w_scan -fc -c NO 1>> scan$i.log 2>> scan$i.log done And I get outputs like this (the timing numbers differs of course somewhat between different runs): 586000: sr6900 (time: 10:21) sr6875 (time: 10:23) 594000: sr6900 (time: 10:26) sr6875 (time: 10:28) 602000: sr6900 (time: 10:31) (time: 10:32) signal ok: QAM_256 f = 602000 kHz S6900C999 Info: NIT(actual) filter timeout 61: sr6900 (time: 10:44) sr6875 (time: 10:47) 618000: sr6900 (time: 10:49) sr6875 (time: 10:52) 626000: sr6900 (time: 10:54) sr6875 (time: 10:57) Then I did the test that you suggested: lin-tv ~ # strace -e ioctl dvbscan -fc test_channel_file scanning test_channel_file using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' ioctl(3, FE_GET_INFO, 0x60b180) = 0 initial transponder 60200 690 0 5 >>> tune to: 60200:INVERSION_AUTO:690:FEC_NONE:QAM_256 ioctl(3, FE_SET_FRONTEND, 0x7fff0581fb20) = 0 ioctl(3, FE_READ_STATUS, 0x7fff0581fb4c) = 0 ioctl(3, FE_READ_STATUS, 0x7fff0581fb4c) = 0 ioctl(4, DMX_SET_FILTER, 0x7fff0581e930) = 0 ioctl(5, DMX_SET_FILTER, 0x7fff0581e930) = 0 ioctl(6, DMX_SET_FILTER, 0x7fff0581e930) = 0 WARNING: filter timeout pid 0x0011 ioctl(5, DMX_STOP, 0x23)= 0 WARNING: filter timeout pid 0x ioctl(4, DMX_STOP, 0x23)= 0 WARNING: filter timeout pid 0x0010 ioctl(6, DMX_STOP, 0x23)= 0 dumping lists (0 services) Done. I did not get the: 602000: sr6900 (time: 10:32) (time: 10:33) signal ok: QAM_256 f = 602000 kHz S6900C999 start_filter:1415: ERROR: ioctl DMX_SET_FILTER failed: 28 No space left on device Info: NIT(actual) filter timeout that I got before. The changes I made from before was 1) I unmounted the USB disk and 2) I rebuild the xc5000 module where I removed the mutex_lock(&xc5000_list_mutex); and mutex_unlock(&xc5000_list_mutex); lines according to the discussion in the " ... em28xx: initial support for HAUPPAUGE HVR-930C again" thread. /Fredrik -- 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: Hauppauge HVR-930C problems
On 07-12-2011 12:25, Fredrik Lingvall wrote: On 12/07/11 14:55, Mauro Carvalho Chehab wrote: Bus 2 doesn't seem to do anything [Alloc= 0/800 us ( 0%)] while I'm scanning!? Scanning envolves 2 different things: 1) tuning and locking into a channel; 2) streaming and filtering, in order to seek for program tables inside the MPEG-TS. Step 1 uses USB control messages. Only at step 2, the device will use the USB ISOC packets. The USB core will see if is there enough bandwidth to reserve for ISOC transfers on that time (based on other traffic data), and submit the URB's (or return -ENOSPC otherwise). BTW: I'm running Gentoo x86_64 (amd64) on a Dell M2400 laptop with an SSD disk. Other hardware connected is a 200 GB disk using the eSata slot, a 1TB WD disk connected using another USB slot, a RME Multiface II soundcard using the expresscard slot. The external USB disk may be interfering, if it is also at bus 2. Also, some laptops use USB for some internal components like wireless. Please remove all other USB devices, disable wireless (if your device is USB) and try again. Regards, Mauro No there's nothing else at Bus 2 (I did a umount on the WD usb disk, cannot unplug devices since I'm logged in remotely right now), and Wireless is a pci device: lin-tv ~ # lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03) 00:1f.2 RAID bus controller: Intel Corporation Mobile 82801 SATA RAID Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) 01:00.0 VGA compatible controller: nVidia Corporation Device 06fb (rev a1) 03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21) 03:01.2 SD Host controller: Ricoh Co Ltd R5C843 MMC Host Controller (rev 11) 0c:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection 0e:00.0 Multimedia audio controller: Xilinx Corporation RME Hammerfall DSP (rev 3c) lin-tv ~ # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 413c:2513 Dell Computer Corp. internal USB Hub of E-Port Replicator Bus 001 Device 005: ID 0c45:63f8 Microdia Sonix Integrated Webcam Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 006 Device 002: ID 0451:2036 Texas Instruments, Inc. TUSB2036 Hub Bus 003 Device 003: ID 413c:8157 Dell Computer Corp. Integrated Keyboard Bus 003 Device 004: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick Bus 006 Device 004: ID 046d:c704 Logitech, Inc. diNovo Wireless Desktop Bus 003 Device 005: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card Bus 002 Device 008: ID 2040:1605 Hauppauge Devices at Bus 2: lin-tv ~ # lsusb | grep "Bus 002" Bus 002 Device 001:
Re: Hauppauge HVR-930C problems
On 12/07/11 14:55, Mauro Carvalho Chehab wrote: Bus 2 doesn't seem to do anything [Alloc= 0/800 us ( 0%)] while I'm scanning!? Scanning envolves 2 different things: 1) tuning and locking into a channel; 2) streaming and filtering, in order to seek for program tables inside the MPEG-TS. Step 1 uses USB control messages. Only at step 2, the device will use the USB ISOC packets. The USB core will see if is there enough bandwidth to reserve for ISOC transfers on that time (based on other traffic data), and submit the URB's (or return -ENOSPC otherwise). BTW: I'm running Gentoo x86_64 (amd64) on a Dell M2400 laptop with an SSD disk. Other hardware connected is a 200 GB disk using the eSata slot, a 1TB WD disk connected using another USB slot, a RME Multiface II soundcard using the expresscard slot. The external USB disk may be interfering, if it is also at bus 2. Also, some laptops use USB for some internal components like wireless. Please remove all other USB devices, disable wireless (if your device is USB) and try again. Regards, Mauro No there's nothing else at Bus 2 (I did a umount on the WD usb disk, cannot unplug devices since I'm logged in remotely right now), and Wireless is a pci device: lin-tv ~ # lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03) 00:1f.2 RAID bus controller: Intel Corporation Mobile 82801 SATA RAID Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) 01:00.0 VGA compatible controller: nVidia Corporation Device 06fb (rev a1) 03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21) 03:01.2 SD Host controller: Ricoh Co Ltd R5C843 MMC Host Controller (rev 11) 0c:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection 0e:00.0 Multimedia audio controller: Xilinx Corporation RME Hammerfall DSP (rev 3c) lin-tv ~ # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 413c:2513 Dell Computer Corp. internal USB Hub of E-Port Replicator Bus 001 Device 005: ID 0c45:63f8 Microdia Sonix Integrated Webcam Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 006 Device 002: ID 0451:2036 Texas Instruments, Inc. TUSB2036 Hub Bus 003 Device 003: ID 413c:8157 Dell Computer Corp. Integrated Keyboard Bus 003 Device 004: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick Bus 006 Device 004: ID 046d:c704 Logitech, Inc. diNovo Wireless Desktop Bus 003 Device 005: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card Bus 002 Device 008: ID 2040:1605 Hauppauge Devices at Bus 2: lin-tv ~ # lsusb | grep "Bus 002" Bus 002 Device 001: ID 1d6b:0002 Linu
Re: Hauppauge HVR-930C problems
On 07-12-2011 11:31, Fredrik Lingvall wrote: On 12/07/11 13:56, Mauro Carvalho Chehab wrote: On 02-12-2011 17:41, Fredrik Lingvall wrote: Hi , I noticed that HVR 930C support was added 21-11-2011. I have build the new driver and installed the firmware but I'm struggling to get it working. 4) DVB scanning # w_scan -c NO -f c ... 602000: sr6900 (time: 10:32) (time: 10:33) signal ok: QAM_256 f = 602000 kHz S6900C999 This means that it detected a QAM_256 carrier, at 602000 kHz, with 6.900 Kbauds symbol rate. start_filter:1415: ERROR: ioctl DMX_SET_FILTER failed: 28 No space left on device -ENOSPC error is generally associated with the lack of USB bandwidth support. This means that the USB bus doesn't have enough free slots for the traffic required in order to support your stream. It generally means that your device is connected into a USB 1.1 hub or port. There are some new USB interfaces that are known to have troubles with the Linux USB 2.0 implementation, as they internally use some USB hubs. It could be your case, as the driver detects it on an USB 2.0 port: [90072.073832] em28xx: New device WinTV HVR-930C @ 480 Mbps (2040:1605, interface 0, class 0) Please do a: # mount usbfs /proc/bus/usb -t usbfs $ cat /proc/bus/usb/devices It should see you something like: T: Bus=08 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 29/900 us ( 3%), #Int= 2, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1d.2 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=08 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=2101 ProdID=020f Rev= 0.01 C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms T: Bus=07 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1d.1 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=06 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1d.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1a.2 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1a.1 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1a.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=:00:1d.7 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#
Re: Hauppauge HVR-930C problems
On 12/07/11 13:56, Mauro Carvalho Chehab wrote: On 02-12-2011 17:41, Fredrik Lingvall wrote: Hi , I noticed that HVR 930C support was added 21-11-2011. I have build the new driver and installed the firmware but I'm struggling to get it working. 4) DVB scanning # w_scan -c NO -f c ... 602000: sr6900 (time: 10:32) (time: 10:33) signal ok: QAM_256 f = 602000 kHz S6900C999 This means that it detected a QAM_256 carrier, at 602000 kHz, with 6.900 Kbauds symbol rate. start_filter:1415: ERROR: ioctl DMX_SET_FILTER failed: 28 No space left on device -ENOSPC error is generally associated with the lack of USB bandwidth support. This means that the USB bus doesn't have enough free slots for the traffic required in order to support your stream. It generally means that your device is connected into a USB 1.1 hub or port. There are some new USB interfaces that are known to have troubles with the Linux USB 2.0 implementation, as they internally use some USB hubs. It could be your case, as the driver detects it on an USB 2.0 port: [90072.073832] em28xx: New device WinTV HVR-930C @ 480 Mbps (2040:1605, interface 0, class 0) Please do a: # mount usbfs /proc/bus/usb -t usbfs $ cat /proc/bus/usb/devices It should see you something like: T: Bus=08 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 29/900 us ( 3%), #Int= 2, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1d.2 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=08 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=2101 ProdID=020f Rev= 0.01 C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms T: Bus=07 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1d.1 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=06 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1d.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1a.2 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1a.1 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1a.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=:00:1d.7 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00
Re: Hauppauge HVR-930C problems
On 02-12-2011 17:41, Fredrik Lingvall wrote: Hi , I noticed that HVR 930C support was added 21-11-2011. I have build the new driver and installed the firmware but I'm struggling to get it working. 4) DVB scanning # w_scan -c NO -f c ... 602000: sr6900 (time: 10:32) (time: 10:33) signal ok: QAM_256 f = 602000 kHz S6900C999 This means that it detected a QAM_256 carrier, at 602000 kHz, with 6.900 Kbauds symbol rate. start_filter:1415: ERROR: ioctl DMX_SET_FILTER failed: 28 No space left on device -ENOSPC error is generally associated with the lack of USB bandwidth support. This means that the USB bus doesn't have enough free slots for the traffic required in order to support your stream. It generally means that your device is connected into a USB 1.1 hub or port. There are some new USB interfaces that are known to have troubles with the Linux USB 2.0 implementation, as they internally use some USB hubs. It could be your case, as the driver detects it on an USB 2.0 port: [90072.073832] em28xx: New device WinTV HVR-930C @ 480 Mbps (2040:1605, interface 0, class 0) Please do a: # mount usbfs /proc/bus/usb -t usbfs $ cat /proc/bus/usb/devices It should see you something like: T: Bus=08 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 29/900 us ( 3%), #Int= 2, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1d.2 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=08 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=2101 ProdID=020f Rev= 0.01 C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms T: Bus=07 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1d.1 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=06 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1d.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1a.2 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1a.1 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1a.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 3.01 S: Manufacturer=Linux 3.1.1-2.fc16.x86_64 ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=:00:1d.7 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS=
Re: Hauppauge HVR-930C problems
On 05-12-2011 21:37, Eddi De Pieri wrote: try using scan from dvb-apps and not w_scan. Actually It seems to me w_scan isn't compatible with this driver due some missing lock. It works for me. The only parameter that it is mandatory is "-f c", in order to use the DVB-C frontend, instead of DVB-T. I've passed a few other parameters to speedup it (otherwise, it would take hours, as it tries first QAM_64, on all possible symbol rates, and then QAM_256). Anyway: $ w_scan -f c -S 13 -Q 1 w_scan version 20111011 (compiled for DVB API 5.3) guessing country 'BR', use -c to override using settings for BRAZIL DVB cable DVB-C BR frontend_type DVB-C, channellist 10 output format vdr-1.6 output charset 'UTF-8', use -C to override Info: using DVB adapter auto detection. /dev/dvb/adapter0/frontend0 -> DVB-C "DRXK DVB-C": good :-) /dev/dvb/adapter0/frontend1 -> DVB-T "DRXK DVB-T": specified was DVB-C -> SEARCH NEXT ONE. Using DVB-C frontend (adapter /dev/dvb/adapter0/frontend0) -_-_-_-_ Getting frontend capabilities-_-_-_-_ Using DVB API 5.4 frontend 'DRXK DVB-C' supports INVERSION_AUTO QAM_AUTO not supported, trying QAM_256. FEC_AUTO FREQ (47.00MHz ... 862.00MHz) SRATE (0.870MBd ... 11.700MBd) -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ searching QAM256... 57000: sr5217 (time: 00:01) 63000: sr5217 (time: 00:03) 69000: sr5217 (time: 00:06) 79000: sr5217 (time: 00:08) 85000: sr5217 (time: 00:11) 177000: sr5217 (time: 00:13) 183000: sr5217 (time: 00:16) 189000: sr5217 (time: 00:18) 195000: sr5217 (time: 00:21) 201000: sr5217 (time: 00:23) 207000: sr5217 (time: 00:26) 213000: sr5217 (time: 00:28) 123000: sr5217 (time: 00:31) 129000: sr5217 (time: 00:34) 135000: sr5217 (time: 00:36) 141000: sr5217 (time: 00:39) 147000: sr5217 (time: 00:41) 153000: sr5217 (time: 00:44) 159000: sr5217 (time: 00:46) 165000: sr5217 (time: 00:49) 171000: sr5217 (time: 00:51) 219000: sr5217 (time: 00:54) 225000: sr5217 (time: 00:56) 231000: sr5217 (time: 00:59) 237000: sr5217 (time: 01:01) 243000: sr5217 (time: 01:04) 249000: sr5217 (time: 01:07) 255000: sr5217 (time: 01:09) 261000: sr5217 (time: 01:12) 267000: sr5217 (time: 01:14) 273000: sr5217 (time: 01:17) 279000: sr5217 (time: 01:19) 285000: sr5217 (time: 01:22) 291000: sr5217 (time: 01:24) 297000: sr5217 (time: 01:27) 303000: sr5217 (time: 01:29) 309000: sr5217 (time: 01:32) 315000: sr5217 (time: 01:34) 321000: sr5217 (time: 01:37) 327000: sr5217 (time: 01:40) 333000: sr5217 (time: 01:42) 339000: sr5217 (time: 01:45) 345000: sr5217 (time: 01:47) 351000: sr5217 (time: 01:50) 357000: sr5217 (time: 01:52) 363000: sr5217 (time: 01:55) 369000: sr5217 (time: 01:57) 375000: sr5217 (time: 02:00) 381000: sr5217 (time: 02:02) 387000: sr5217 (time: 02:05) 393000: sr5217 (time: 02:08) 399000: sr5217 (time: 02:10) 405000: sr5217 (time: 02:13) 411000: sr5217 (time: 02:15) 417000: sr5217 (time: 02:18) 423000: sr5217 (time: 02:20) 429000: sr5217 (time: 02:23) 435000: sr5217 (time: 02:25) 441000: sr5217 (time: 02:28) 447000: sr5217 (time: 02:30) 453000: sr5217 (time: 02:33) 459000: sr5217 (time: 02:35) 465000: sr5217 (time: 02:38) 471000: sr5217 (time: 02:41) 477000: sr5217 (time: 02:43) 483000: sr5217 (time: 02:46) 489000: sr5217 (time: 02:48) 495000: sr5217 (time: 02:51) 501000: sr5217 (time: 02:53) 507000: sr5217 (time: 02:56) 513000: sr5217 (time: 02:58) 519000: sr5217 (time: 03:01) 525000: sr5217 (time: 03:03) 531000: sr5217 (time: 03:06) 537000: sr5217 (time: 03:08) 543000: sr5217 (time: 03:11) 549000: sr5217 (time: 03:14) 555000: sr5217 (time: 03:16) 561000: sr5217 (time: 03:19) 567000: sr5217 (time: 03:21) 573000: sr5217 (time: 03:24) (time: 03:25) signal ok: QAM_256 f = 573000 kHz S5217C999 new transponder: (QAM_256 f = 591000 kHz S5217C34) new transponder: (QAM_256 f = 597000 kHz S5217C34) new transponder: (QAM_256 f = 603000 kHz S5217C34) new transponder: (QAM_256 f = 609000 kHz S5217C34) new transponder: (QAM_256 f = 615000 kHz S5217C34) new transponder: (QAM_256 f = 621000 kHz S5217C34) new transponder: (QAM_256 f = 627000 kHz S5217C34) new transponder: (QAM_256 f = 633000 kHz S5217C34) new transponder: (QAM_256 f = 639000 kHz S5217C34) new transponder: (QAM_256 f = 681000 kHz S5217C34) new transponder: (QAM_256 f = 651000 kHz S5217C34) new transponder: (QAM_256 f = 693000 kHz S5217C34) new transponder: (QAM_256 f = 699000 kHz S5217C34) new transponder: (QAM_256 f = 687000 kHz S5217C34) new transponder: (QAM_256 f = 657000 kHz S5217C34) new transponder: (QAM_256 f = 663000 kHz S5217C34) new transponder: (QAM_256 f = 669000 kHz S5217C34) new transponder: (QAM_256 f = 705000 kHz S5217C34) new transpo
Re: Hauppauge HVR-930C problems
On 12/06/11 00:37, Eddi De Pieri wrote: try using scan from dvb-apps and not w_scan. Actually It seems to me w_scan isn't compatible with this driver due some missing lock. I've tired dvbscan (=scan on Gentoo?). Apperently I need some initial scan file and I found one here: http://www.mail-archive.com/linuxtv-commits@linuxtv.org/msg02599.html for the provider I have (I'm not really sure if it's correct though). The scan file: # no-Oslo-Get (cable) C 24100 690 NONE QAM256 C 27200 690 NONE QAM256 C 28000 690 NONE QAM256 C 29000 690 NONE QAM256 C 29800 690 NONE QAM256 C 30600 690 NONE QAM256 C 31400 690 NONE QAM256 C 32200 690 NONE QAM256 C 33000 690 NONE QAM256 C 33800 690 NONE QAM256 C 34600 690 NONE QAM256 C 35400 690 NONE QAM256 C 36200 690 NONE QAM256 C 37000 690 NONE QAM256 C 37800 690 NONE QAM256 C 38600 690 NONE QAM256 C 39400 690 NONE QAM256 C 41000 690 NONE QAM256 C 44200 6952000 NONE QAM256 C 48200 690 NONE QAM256 C 49800 690 NONE QAM256 Scan results: # dvbscan -a0 /usr/share/dvb/dvb-c/no-Oslo-Get scanning /usr/share/dvb/dvb-c/no-Oslo-Get using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 24100 690 0 5 initial transponder 27200 690 0 5 initial transponder 28000 690 0 5 initial transponder 29000 690 0 5 initial transponder 29800 690 0 5 initial transponder 30600 690 0 5 initial transponder 31400 690 0 5 initial transponder 32200 690 0 5 initial transponder 33000 690 0 5 initial transponder 33800 690 0 5 initial transponder 34600 690 0 5 initial transponder 35400 690 0 5 initial transponder 36200 690 0 5 initial transponder 37000 690 0 5 initial transponder 37800 690 0 5 initial transponder 38600 690 0 5 initial transponder 39400 690 0 5 initial transponder 41000 690 0 5 initial transponder 44200 6952000 0 5 initial transponder 48200 690 0 5 initial transponder 49800 690 0 5 >>> tune to: 24100:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: >>> tuning failed!!! >>> tune to: 24100:INVERSION_AUTO:690:FEC_NONE:QAM_256 (tuning failed) WARNING: >>> tuning failed!!! >>> tune to: 27200:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 28000:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 29000:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 29800:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 30600:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 31400:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 32200:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 33000:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 33800:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 34600:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 35400:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 36200:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 37000:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 37800:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 38600:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 >>> tune to: 39400:INVERSION_AUTO:690:FEC_NONE:QAM_256 WARNING: filter timeo
Re: Hauppauge HVR-930C problems
try using scan from dvb-apps and not w_scan. Actually It seems to me w_scan isn't compatible with this driver due some missing lock. On Fri, Dec 2, 2011 at 8:45 PM, Devin Heitmueller wrote: > On Fri, Dec 2, 2011 at 2:41 PM, Fredrik Lingvall > wrote: >> The HVR 930C device has three connectors/inputs: an antenna input, an >> S-video, and a composite video, respectively, >> >> The provider I have here in Norway (Get) has both analog tv and digital >> (DVB-C) so can I get analog tv using the antenna input or is analog only on >> the S-video/composite inputs? And, how do I select which analog input that >> is used? > > The analog support for that device isn't currently supported (due to a > lack of a Linux driver for the analog demodulator). The digital > should work fine though (and if not, bring it to Mauro's attention > since he has been actively working on it). > > Devin > > -- > Devin J. Heitmueller - Kernel Labs > http://www.kernellabs.com > -- > 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 -- 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: Hauppauge HVR-930C problems
On Fri, Dec 2, 2011 at 2:41 PM, Fredrik Lingvall wrote: > The HVR 930C device has three connectors/inputs: an antenna input, an > S-video, and a composite video, respectively, > > The provider I have here in Norway (Get) has both analog tv and digital > (DVB-C) so can I get analog tv using the antenna input or is analog only on > the S-video/composite inputs? And, how do I select which analog input that > is used? The analog support for that device isn't currently supported (due to a lack of a Linux driver for the analog demodulator). The digital should work fine though (and if not, bring it to Mauro's attention since he has been actively working on it). Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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
Hauppauge HVR-930C problems
Hi , I noticed that HVR 930C support was added 21-11-2011. I have build the new driver and installed the firmware but I'm struggling to get it working. I have the firmwares: dvb-usb-hauppauge-hvr930c-drxk.fw and dvb-fe-xc5000-1.6.114.fw in /lib/firmware (on a Gentoo x86_64 system) Since I'm new to tv devices, what tools should I use? Some tests I've done: 1) Driver loading: # modprobe em28xx # dmesg -c [90072.073823] em28xx 2-3:1.0: usb_probe_interface [90072.073827] em28xx 2-3:1.0: usb_probe_interface - got id [90072.073832] em28xx: New device WinTV HVR-930C @ 480 Mbps (2040:1605, interface 0, class 0) [90072.073834] em28xx: Audio Vendor Class interface 0 found [90072.077038] em28xx #0: chip ID is em2884 [90072.129073] em28xx #0: Identified as Hauppauge WinTV HVR 930C (card=81) [90072.129451] Registered IR keymap rc-hauppauge [90072.129575] input: em28xx IR (em28xx #0) as /devices/pci:00/:00:1d.7/usb2/2-3/rc/rc4/input17 [90072.129625] rc4: em28xx IR (em28xx #0) as /devices/pci:00/:00:1d.7/usb2/2-3/rc/rc4 [90072.130444] em28xx #0: Config register raw data: 0xcb [90072.130446] em28xx #0: v4l2 driver version 0.1.3 [90072.135290] em28xx #0: V4L2 video device registered as video1 [90072.140241] usbcore: registered new interface driver em28xx [90072.140243] em28xx driver loaded [90073.298578] drxk: detected a drx-3913k, spin A2, xtal 20.250 MHz [90074.641068] DRXK driver version 0.9.4300 [90074.655586] xc5000 1-0061: creating new instance [90074.656091] xc5000: Successfully identified at address 0x61 [90074.656094] xc5000: Firmware has not been loaded previously [90074.656098] DVB: registering new adapter (em28xx #0) [90074.656101] DVB: registering adapter 0 frontend 0 (DRXK DVB-C)... [90074.656172] DVB: registering adapter 0 frontend 1 (DRXK DVB-T)... [90074.656389] em28xx #0: Successfully loaded em28xx-dvb [90074.656392] Em28xx: Initialized (Em28xx dvb Extension) extension which looks ok to me. 2) Analog scanning: # scantv -a -n PAL vid-open-auto: failed to open an analog TV device at /dev/video1 vid-open: could not find a suitable videodev no analog TV device available # dmesg -c [90174.629465] ehci_hcd :00:1a.7: reused qh 880118578f80 schedule [90174.629469] usb 1-6: link qh4-0001/880118578f80 start 2 [1/0 us] [90174.629711] usb 1-6: unlink qh4-0001/880118578f80 start 2 [1/0 us] 3) Mplayer # mplayer tv:// -tv driver=v4l2:norm=PAL:input=0:amode=1:width=384:height=288:outfmt=yv12:device=/dev/video1:chanlist=europe-west:channel=S14 MPlayer SVN-r33094-4.5.3 (C) 2000-2011 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing tv://. TV file format detected. Selected driver: v4l2 name: Video 4 Linux 2 input author: Martin Olschewski comment: first try, more to come ;-) Selected device: Hauppauge WinTV HVR 930C Capabilities: video capture read/write streaming supported norms: 0 = NTSC; 1 = NTSC-M; 2 = NTSC-M-JP; 3 = NTSC-M-KR; 4 = NTSC-443; 5 = PAL; 6 = PAL-BG; 7 = PAL-H; 8 = PAL-I; 9 = PAL-DK; 10 = PAL-M; 11 = PAL-N; 12 = PAL-Nc; 13 = PAL-60; 14 = SECAM; 15 = SECAM-B; 16 = SECAM-G; 17 = SECAM-H; 18 = SECAM-DK; 19 = SECAM-L; 20 = SECAM-Lc; inputs: Current input: 0 Current format: YUYV v4l2: ioctl set format failed: Invalid argument v4l2: ioctl enum input failed: Invalid argument Selected input hasn't got a tuner! v4l2: ioctl queue buffer failed: No space left on device v4l2: 0 frames successfully processed, 0 frames dropped. Exiting... (End of file) # dmesg -c [90262.194863] ehci_hcd :00:1d.7: iso resched full 8800d7df9000 (now 5829 max 14021) [90262.194870] submit of urb 0 failed (error=-28) 4) DVB scanning # w_scan -c NO -f c w_scan version 20110702 (compiled for DVB API 5.2) using settings for NORWAY DVB cable DVB-C frontend_type DVB-C, channellist 7 output format vdr-1.6 WARNING: could not guess your codepage. Falling back to 'UTF-8' output charset 'UTF-8', use -C to override Info: using DVB adapter auto detection. /dev/dvb/adapter0/frontend0 -> DVB-C "DRXK DVB-C": good :-) /dev/dvb/adapter0/frontend1 -> DVB-T "DRXK DVB-T": specified was DVB-C -> SEARCH NEXT ONE. Using DVB-C frontend (adapter /dev/dvb/adapter0/frontend0) -_-_-_-_ Getting frontend capabilities-_-_-_-_ Using DVB API 5.4 frontend 'DRXK DVB-C' supports INVERSION_AUTO QAM_AUTO not supported, trying QAM_64 QAM_256. FEC_AUTO FREQ (47.00MHz ... 862.00MHz) SRATE (0.870MBd ... 11.700MBd) -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ searching QAM64... 73000: sr6900 (time: 00:00) sr6875 (time: 00:03) 81000: sr6900 (time: 00:06) sr6875 (time: 00:08) 113000: sr6900 (time: 00:11) sr6875 (time: 00:13) 121000: sr6900 (time: 00:16) sr6875 (time: 00:18) 129000: sr6900 (time: 00:21) sr6875 (time: 00:23) 137000: sr6900 (time: 00:26) sr6875 (time: 00:28) 145000: sr6900 (time: 00:31) sr6875 (time: 00:34) 153000: sr6900 (time: 00:36)
