[linux-dvb] Re: performance degradation? (dvb_usb_dtt200u)
Hi all, trying to confirm that it is not a problem related with the USB stick (I guess it isn't since I've seen no messages in the list about that point), I've tried to watch TV from Windows with the same usb stick from Freecom... four hours [CSI Las Vegas, Miami and New York + ads] of high quality TV without any pixelation or degradation :( Trying to do some tests under Linux, I haven't been able to rmmod/insmod in order to prove wether reinitialization works: now the module is always in use (showing the same big number: 4294967295, that decreases by one each time I unplug the stick: 4294967294, 4294967293...). That count goes from 0 ant insert time to 4...13... and after that (removal after video pixelation/freeze) it goes to 429496xxx... So now, wat do you think I can do in order to determine where the problem is? The big problem is that, besides that strange large number in the usage count of the module, and the: dvb-usb: recv bulk message failed: -110 drivers/usb/input/hid-core.c: timeout initializing reports messages in dmesg at stick insert time, no other error/waring messages appear anywhere... Sorry for the inconvenience, but it would be great to get this stick working, since it's the third I'm trying (Zaapa, AVermedia Volar, and now Freecom), and I wouldn't like to go back again to the store to return it and try with the last one that remains there (a Hauppauge Stick). I think the guy of the store will kill me :) thanks in advance. Best, Jose On 11/13/06, José Oliver Segura [EMAIL PROTECTED] wrote: Hi all, after seeing that Zaapa is not supported and having some troubles with an AverMedia Volar (which wasn't able to find any channel using the roof antenna, only with the portable antenna - [curious, the Zaapa one worked just the reverse way]), I've been able to get a Freecom dvb usb stick. Things went ok (nice!) at first: downloaded the firmware, compiled installed code from Mercurial, plug the stick and it's recognized. After that, used scandvb to create channels.conf, OK. I've been able to watch TV using MPlayer with that channels.conf file, great. It works OK, but after sometime (maybe one hour, but is not deterministic), everything goes bad: image starts to goes slowmotion/frozen/pixelated, sound gets crappy, with lot of whistles (of course, audio and video are not synchronized at that point), and I have to close mplayer and start again. At this point, the degradation occurs before, just one or two minutes after the second mplayer starts running. At that point, It cannot be solved just restarting mplayer (neither removing/reinserting the dvb stick). What I've tried is to remove the stick, rmmod dvb_usb_dtt200u and start again, and it seems to work (I mean, it seems I can get an hour of tv..), but after some time all the problems start again. I've noticed, before the first rmmod, that dvb_usb_dtt200u was reported to be used by 4294967293 times (see lsmod output below) :-/ Usually, that number is 4/5 in my case (at the time of writing this, I've not been able to reproduce it, now -regarding that it's not working-, keeps the usage count at 4) Trying to remove mplayer from the equation, I've tried to do a test just with stream recording using tzap/cat and generating an mpeg file, and it seems to be the same. Playing it with mplayer shows up that the problem is in the mpeg data, not in mplayer. Is it possible that the driver/frontend has some bug that causes that time/use malfunction? I'll be glad to help if I can. Below comes some information: - OS Fedora Core 6 (kernel 2.6.18 i686 reinstalled after fedora bug installing the 386 kernel) lsusb: Bus 006 Device 006: ID 14aa:0226 AVerMedia (again) or CE Bus 006 Device 001: ID : Bus 001 Device 001: ID : Bus 002 Device 001: ID : Bus 003 Device 001: ID : Bus 004 Device 003: ID 05e3:0606 Genesys Logic, Inc. Bus 004 Device 001: ID : Bus 004 Device 004: ID 067b:3507 Prolific Technology, Inc. PL3507 ATAPI6 Bridge Bus 005 Device 001: ID : lsmod | grep dvb: dvb_usb_dtt200u16900 4294967293 dvb_usb28044 1 dvb_usb_dtt200u dvb_core 83496 1 dvb_usb dvb_pll18692 1 dvb_usb i2c_core 25537 4 i2c_ec,i2c_i801,dvb_usb,dvb_pll dmesg (filtered): usb 6-2: new high speed USB device using ehci_hcd and address 5 usb 6-2: configuration #1 chosen from 1 choice dvb-usb: found a 'WideView WT-220U PenType Receiver (Typhoon/Freecom)' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-wt220u-fc03.fw' usbcore: registered new driver dvb_usb_dtt200u usb 6-2: USB disconnect, address 5 dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. usb 6-2: new high speed USB device using ehci_hcd and address 6 usb 6-2: configuration #1 chosen from 1 choice
[linux-dvb] V4l-dvb and spca5xx...
Hi, I have a Terratec Cinergy Hybrid T XS USB and I followed the instructions found on : http://www.linuxtv.org/v4lwiki/index.php/Em2880#Installation I've compiled the modules and installed them (modprobe em28xx and modprobe em2880-dvb). Everything is ok and I can see the TV. But now, I have problems with my webcam and the spca5xx module. So, in the v4l-dvb-merge/v4l directory, I did : make kernel-links : cd ..; v4l/scripts/makelinks.sh /lib/modules/2.6.18-1-686/build patching /lib/modules/2.6.18-1-686/build... mkdir: created directory `/lib/modules/2.6.18-1-686/build/Documentation' mkdir: created directory `/lib/modules/2.6.18-1-686/build/Documentation/dvb' mkdir: created directory `/lib/modules/2.6.18-1-686/build/Documentation/video4li nux' mkdir: created directory `/lib/modules/2.6.18-1-686/build/Documentation/video4li nux/bttv' mkdir: created directory `/lib/modules/2.6.18-1-686/build/Documentation/video4li nux/cx2341x' mkdir: created directory `/lib/modules/2.6.18-1-686/build/Documentation/video4li nux/cx88' Then, I tried to compile spca5xx : p3010-ac-nantes:/opt/spca5xx-20060501# make Building SPCA5XX driver for 2.5/2.6 kernel. Remember: you must have read/write access to your kernel source tree. make -C /lib/modules/`uname -r`/build SUBDIRS=/opt/spca5xx-20060501 CC=cc module s make[1]: entrant dans le répertoire « /usr/src/linux-headers-2.6.18-1-686 » CC [M] /opt/spca5xx-20060501/drivers/usb/spca5xx.o /opt/spca5xx-20060501/drivers/usb/spca5xx.c: In function ‘spca5xx_open’: /opt/spca5xx-20060501/drivers/usb/spca5xx.c:2392: warning: implicit declaration of function ‘video_devdata’ /opt/spca5xx-20060501/drivers/usb/spca5xx.c:2392: warning: initialization makes pointer from integer without a cast /opt/spca5xx-20060501/drivers/usb/spca5xx.c:2397: warning: implicit declaration of function ‘video_get_drvdata’ /opt/spca5xx-20060501/drivers/usb/spca5xx.c:2397: warning: initialization makes pointer from integer without a cast /opt/spca5xx-20060501/drivers/usb/spca5xx.c: In function ‘spca5xx_close’: /opt/spca5xx-20060501/drivers/usb/spca5xx.c:2487: warning: initialization makes pointer from integer without a cast /opt/spca5xx-20060501/drivers/usb/spca5xx.c: In function ‘spca5xx_do_ioctl’: /opt/spca5xx-20060501/drivers/usb/spca5xx.c:2547: warning: initialization makes pointer from integer without a cast /opt/spca5xx-20060501/drivers/usb/spca5xx.c: In function ‘spca5xx_ioctl’: /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3091: warning: implicit declaration of function ‘video_usercopy’ /opt/spca5xx-20060501/drivers/usb/spca5xx.c: In function ‘spca5xx_read’: /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3110: warning: initialization makes pointer from integer without a cast /opt/spca5xx-20060501/drivers/usb/spca5xx.c: In function ‘spca5xx_mmap’: /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3209: warning: initialization makes pointer from integer without a cast /opt/spca5xx-20060501/drivers/usb/spca5xx.c: At top level: /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3261: error: variable ‘spca50x_templ ate’ has initializer but incomplete type /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3262: error: unknown field ‘owner’ s pecified in initializer /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3262: warning: excess elements in st ruct initializer /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3262: warning: (near initialization for ‘spca50x_template’) /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3263: error: unknown field ‘name’ sp ecified in initializer /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3263: warning: excess elements in st ruct initializer /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3263: warning: (near initialization for ‘spca50x_template’) /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3264: error: unknown field ‘type’ sp ecified in initializer /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3264: warning: excess elements in st ruct initializer /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3264: warning: (near initialization for ‘spca50x_template’) /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3265: error: unknown field ‘hardware ’ specified in initializer /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3265: warning: excess elements in st ruct initializer /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3265: warning: (near initialization for ‘spca50x_template’) /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3266: error: unknown field ‘fops’ sp ecified in initializer /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3266: warning: excess elements in st ruct initializer /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3266: warning: (near initialization for ‘spca50x_template’) /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3268: error: unknown field ‘release’ specified in initializer /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3268: error: ‘video_device_release’ undeclared here (not in a function) /opt/spca5xx-20060501/drivers/usb/spca5xx.c:3268: warning: excess elements in st ruct initializer
[linux-dvb] 3 patches for Kernel 2.6.19-rc5
Hi everybody,
I sent in the following three patches for three times now, and they are still
not even part of the mm-tree.
The first one is a documentation fix synchronizing the current as-is-state of
kernel compilation.
The second one makes a module called dvb-pll.c deselectable as it is completely
absurd in the special case that you use a Pinnacle DVB-S card as the only card
in your system.
The third one gets rid of two modules that are only needed by TwinHan DST cards
and / or Pinnacle cards WITH CI slot. I owe a Pinnacle card without CI slot. In
so far I defininitely DO NOT NEED those modules at all and I want so save RAM.
IN OTHER WORDS: The concept of a common backend called dvb-bt8xx.c for all
bt8xx cards is definitely a REACTIONARY concept: Backend parts for the specific
card should be selectable and deselectable as frontends like cx24110.c are
selectable and deselectable at the current state of kernel development.
The first two patches do not hurt at all:
Number one (the documentation fix) helps linux rookies and beginners to get a
clean kernel compiled without wasting time.
Number two (the dvb-pll.c one) saves RAM for two special cases:
a. the Pinnacle PCTVSAT (and maybe many many others too, which has got to be
proven – I mentioned this fact already – in vain!) is the only one in the
machine.
b. the Pinnacle PCTVSAT does not have a CI slot.
Number three hurts, as it wipes out support for all bt8xx cards that have a
slot for conditional access: Examples: Pinnacle PCTVSAT CI and TwinHan DST.
BUT: If you do NOT owe a card with CI slot this third patch definitely helps
you to save RAM! This patch hurts because I simply do not have an idea how to
make it better so that it does not hurt. In so far I said NOT to take this up
into vanilla, but leave it on the mailing list for users needing it. In vain!
So I simply followed two strategic lines:
a. offering clear and understandable documentation
b. offering two humble steps towards a far more progressive backend for bt8xx
cards: ability to deselect parts of the code and thus saving RAM.
All three patches: Signed-Off-By: Uwe Bugla [EMAIL PROTECTED]
Functional description: please see above.
Number ONE:
--- a/Documentation/dvb/bt8xx.txt
+++ b/Documentation/dvb/bt8xx.txt
@@ -9,9 +9,15 @@
Please see Documentation/dvb/cards.txt = o Cards based on the Conexant Bt8xx
PCI bridge:
Compiling kernel please enable:
-a.)Device drivers = Multimedia devices = Video For Linux = BT848
Video For Linux
+a.)Device drivers = Multimedia devices = Video For Linux = Enable
Video for Linux API 1 (DEPRECATED)
-b.)Device drivers = Multimedia devices = Digital Video Broadcasting
Devices
- = DVB for Linux DVB Core Support Bt8xx based PCI Cards
+b.)Device drivers = Multimedia devices = Video For Linux = Video
Capture Adapters = BT848 Video For Linux
+c.)Device drivers = Multimedia devices = Digital Video Broadcasting
Devices
+ = DVB for Linux DVB Core Support Bt8xx based PCI Cards
+
+Note: If you know the frontend driver that your specific card needs
furthermore please enable:
+d.)Device drivers = Multimedia devices = Digital Video Broadcasting
Devices
+ = DVB for Linux DVB Core Support Customize DVB Frontends = Customize
the frontend modules to build
+ Then you can save memory by deselecting every frontend module your specific
card does not need.
2) Loading Modules
==
Number TWO:
--- a/drivers/media/dvb/bt8xx/Kconfig
+++ b/drivers/media/dvb/bt8xx/Kconfig
@@ -1,7 +1,7 @@
config DVB_BT8XX
tristate BT8xx based PCI cards
depends on DVB_CORE PCI I2C VIDEO_BT848
-select DVB_PLL
+select DVB_PLL if !DVB_FE_CUSTOMISE
select DVB_MT352 if !DVB_FE_CUSTOMISE
select DVB_SP887X if !DVB_FE_CUSTOMISE
select DVB_NXT6000 if !DVB_FE_CUSTOMISE
--- a/drivers/media/dvb/frontends/Kconfig
+++ b/drivers/media/dvb/frontends/Kconfig
@@ -264,8 +264,11 @@
depends on DVB_CORE
config DVB_PLL
-tristate
+tristate PLL support for DVB tuners
depends on DVB_CORE I2C
+default m if !DVB_FE_CUSTOMISE
+help
+ You can safely deselect this if you're only running a Pinnacle PCTV Sat
DVB-S card.
config DVB_TDA826X
tristate Philips TDA826X silicon tuner
Number Three: (the destructive RAM saver!)
--- a/drivers/media/dvb/bt8xx/Makefile
+++ b/drivers/media/dvb/bt8xx/Makefile
@@ -1,3 +1,3 @@
-obj-$(CONFIG_DVB_BT8XX) += bt878.o dvb-bt8xx.o dst.o dst_ca.o
+obj-$(CONFIG_DVB_BT8XX) += bt878.o dvb-bt8xx.o
EXTRA_CFLAGS = -Idrivers/media/dvb/dvb-core/ -Idrivers/media/video/bt8xx
-Idrivers/media/dvb/frontends
--- a/drivers/media/dvb/bt8xx/dvb-bt8xx.c
+++ b/drivers/media/dvb/bt8xx/dvb-bt8xx.c
@@ -403,9 +403,6 @@
.demod_init = advbt771_samsung_tdtc9251dh0_demod_init,
};
-static struct dst_config dst_config = {
-.demod_address = 0x55,
-};
static int or51211_request_firmware(struct dvb_frontend* fe, const struct
firmware **fw, char* name)
{
@@ -568,34 +565,9 @@
.demod_init =
[linux-dvb] Hauppauge WinTV NOVA-T Stick problems
I've build the drivers from http://linuxtv.org/hg/~pb/v4l-dvb, but the frontend on the stick is still not recognized - (on FC6) I get: usb 2-8: new high speed USB device using ehci_hcd and address 20 usb 2-8: configuration #1 chosen from 1 choice dib0700: loaded with support for 2 different device-types FW GET_VERSION length: -32 cold: 1 dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw' dib0700: firmware started successfully. dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-T Stick). I2C read failed on address 9 I2C read failed on address 40 DiB7000P:-D- DiB7000PC not detected I2C read failed on address 9 DiB7000M:i2c read error on 896 DiB7000M:-E- DiB7000M: wrong Vendor ID (read=0x400d) dvb-usb: no frontend was attached by 'Hauppauge Nova-T Stick' dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected. usbcore: registered new driver dvb_usb_dib0700 Interesting things here are: FW GET_VERSION length is returning -32? I2C reads of 9, 40 and 896 are all failing why ? This is with a *new* WinTV NOVA-T USB stick. I've tried plugging it in and out several times (10+) but it makes no difference. Any help would be greatfully received. Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: 3 patches for Kernel 2.6.19-rc5
Em Ter, 2006-11-14 às 17:47 +0100, Uwe Bugla escreveu:
Hi everybody,
Number ONE:
--- a/Documentation/dvb/bt8xx.txt
+++ b/Documentation/dvb/bt8xx.txt
@@ -9,9 +9,15 @@
Please see Documentation/dvb/cards.txt = o Cards based on the Conexant
Bt8xx PCI bridge:
Compiling kernel please enable:
-a.)Device drivers = Multimedia devices = Video For Linux = BT848
Video For Linux
+a.)Device drivers = Multimedia devices = Video For Linux = Enable
Video for Linux API 1 (DEPRECATED)
-b.)Device drivers = Multimedia devices = Digital Video Broadcasting
Devices
- = DVB for Linux DVB Core Support Bt8xx based PCI Cards
+b.)Device drivers = Multimedia devices = Video For Linux = Video
Capture Adapters = BT848 Video For Linux
+c.)Device drivers = Multimedia devices = Digital Video Broadcasting
Devices
+ = DVB for Linux DVB Core Support Bt8xx based PCI Cards
+
+Note: If you know the frontend driver that your specific card needs
furthermore please enable:
No. For most users, it is a risky option to allow DVB_CUSTOMISE. A
warning should be added here, marking that this option may make DVB to
stop working.
+d.)Device drivers = Multimedia devices = Digital Video Broadcasting
Devices
+ = DVB for Linux DVB Core Support Customize DVB Frontends =
Customize the frontend modules to build
+ Then you can save memory by deselecting every frontend module your specific
card does not need.
Same as above.
2) Loading Modules
==
Number TWO:
--- a/drivers/media/dvb/bt8xx/Kconfig
+++ b/drivers/media/dvb/bt8xx/Kconfig
@@ -1,7 +1,7 @@
config DVB_BT8XX
tristate BT8xx based PCI cards
depends on DVB_CORE PCI I2C VIDEO_BT848
-select DVB_PLL
+select DVB_PLL if !DVB_FE_CUSTOMISE
select DVB_MT352 if !DVB_FE_CUSTOMISE
select DVB_SP887X if !DVB_FE_CUSTOMISE
select DVB_NXT6000 if !DVB_FE_CUSTOMISE
--- a/drivers/media/dvb/frontends/Kconfig
+++ b/drivers/media/dvb/frontends/Kconfig
@@ -264,8 +264,11 @@
depends on DVB_CORE
config DVB_PLL
-tristate
+tristate PLL support for DVB tuners
depends on DVB_CORE I2C
+default m if !DVB_FE_CUSTOMISE
+help
+ You can safely deselect this if you're only running a Pinnacle PCTV
Sat DVB-S card.
This comment doesn't help. For 99,9% of the current DVB boards, DVB_PLL
is needed. So, help should be something like this is required for most
boards. You should disable it only if you know what you are doing.
config DVB_TDA826X
tristate Philips TDA826X silicon tuner
Number Three: (the destructive RAM saver!)
-static struct dst_config dst_config = {
-.demod_address = 0x55,
-};
snip/
NO! You are just removing DST support from the driver! Saves some memory
for your board, but breaks support for a large number of boards.
Cheers,
Mauro.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Freecom - recv bulk message failed: -110
Hi, the Freecom dvb-t receiver that I bought last week gives the following error in dmesg: dvb-usb: recv bulk message failed: -110 the device uses the dvb-usb-tt200u driver and identifies in lsusb as Bus 004 Device 002: ID 14aa:0226 AVerMedia (again) or CE This is also mentioned in some other posts to this list. But without anyone working on the issue or having an interest in resolving it. I hope this will get picked up. Full dmesg of the boot: http://www.rafb.net/paste/results/PE71Cl33.html Best regards, Stefan ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
RE: [linux-dvb] Freecom - recv bulk message failed: -110
Steven, What kernel are you using? I had this problem which seemed to resolve itself when I changed kernels 2.6.16-2.6.17 IIRC. However, I never resolved the tuning offset issues. Cheers Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Schweizer Sent: 14 November 2006 17:57 To: linux-dvb@linuxtv.org Subject: [linux-dvb] Freecom - recv bulk message failed: -110 Hi, the Freecom dvb-t receiver that I bought last week gives the following error in dmesg: dvb-usb: recv bulk message failed: -110 the device uses the dvb-usb-tt200u driver and identifies in lsusb as Bus 004 Device 002: ID 14aa:0226 AVerMedia (again) or CE This is also mentioned in some other posts to this list. But without anyone working on the issue or having an interest in resolving it. I hope this will get picked up. Full dmesg of the boot: http://www.rafb.net/paste/results/PE71Cl33.html Best regards, Stefan ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- No virus found in this incoming message. Checked by AVG. Version: 7.5.431 / Virus Database: 268.14.5/533 - Release Date: 13/11/2006 20:56 -- No virus found in this outgoing message. Checked by AVG. Version: 7.5.431 / Virus Database: 268.14.5/533 - Release Date: 13/11/2006 20:56 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] RE: Freecom - recv bulk message failed: -110
Mark Howells wrote: Steven, What kernel are you using? I had this problem which seemed to resolve itself when I changed kernels 2.6.16-2.6.17 IIRC. However, I never resolved the tuning offset issues. I have the kernel 2.6.18-ck1 as can be seen in the dmesg. Do you think it has something to do with the kernel version? I built dvb drivers independently from the hg repository. -Stefan ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] No frontend with Nova-t stick
Dave Leatherdale wrote: Hi I recently got a few of the Hauppauge nova-t stick devices. I tried using the latest source from http://linuxtv.org/hg/v4l-dvb and the /~pb/v4l-dvb trees but I always get no frontend was attached. I'm running Ubuntu 6.10 powerpc on a mac mini. dmesg output: [ 611.770214] usb 2-2: new high speed USB device using ehci_hcd and address 8 [ 611.903803] usb 2-2: configuration #1 chosen from 1 choice [ 611.904072] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware [ 611.942956] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw' [ 612.120666] dib0700: firmware started successfully. [ 612.622218] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state. [ 612.622320] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 612.622940] DVB: registering new adapter (Hauppauge Nova-T Stick). [ 612.816267] dvb-usb: no frontend was attached by 'Hauppauge Nova-T Stick' [ 612.816285] dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected. I assume the numbers on the device itself have some sort of meaning so the first line is: M/R:70001/A1B5 #3006 The second line changes between devices but its along the lines of 000DFE0A84D2 LF Can I provide any additional information or help in order to help work out why this doesn't work? Many thanks, Dave ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Dave, It's the same type of stick that I've got - same problem as I see. If you turn on debugging by adding 'options dvb_usb_dib0700 debug=1' to the /etc/modprobe.conf. (or whatever, try /sbin/modinfo dvb_usb_dib0700 and it'll print out the parameters that it uses), you may get the same as I do: I2C read failed on address 9 DiB7000M:i2c read error on 896 DiB7000M:-E- DiB7000M: wrong Vendor ID (read=0x4602) dvb-usb: no frontend was attached by 'Hauppauge Nova-T Stick' I emailed Patrick Boettcher and this list describing the problem. (I actually bought the stick when he announced preliminary support ;(. Patrick seems to have access to the specs for the DibCom 7000 or the frontend. (I think that he may work with/for DibCom), but he appears to be very busy. I wish companies would open up their specs a bit more. I could spend time reading them rather than waiting for someone to have some free time to work on it. I mustn't grumble though at least some progress has been made. So as it stands it doesn't work. Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] No frontend with Nova-t stick
I get a very slightly different output if it helps [ 107.404506] DVB: registering new adapter (Hauppauge Nova-T Stick). [ 107.595411] I2C read failed on address 9 [ 107.595747] I2C read failed on address 40 [ 107.596288] I2C read failed on address 9 [ 107.596293] DiB7000M:i2c read error on 896 [ 107.596297] DiB7000M:-E- DiB7000M: wrong Vendor ID (read=0x0) [ 107.596361] dvb-usb: no frontend was attached by 'Hauppauge Nova-T Stick' Dave On 15/11/06 00:01, Steven Cockeram [EMAIL PROTECTED] wrote: Dave Leatherdale wrote: Hi I recently got a few of the Hauppauge nova-t stick devices. I tried using the latest source from http://linuxtv.org/hg/v4l-dvb and the /~pb/v4l-dvb trees but I always get no frontend was attached. I'm running Ubuntu 6.10 powerpc on a mac mini. dmesg output: [ 611.770214] usb 2-2: new high speed USB device using ehci_hcd and address 8 [ 611.903803] usb 2-2: configuration #1 chosen from 1 choice [ 611.904072] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware [ 611.942956] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw' [ 612.120666] dib0700: firmware started successfully. [ 612.622218] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state. [ 612.622320] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 612.622940] DVB: registering new adapter (Hauppauge Nova-T Stick). [ 612.816267] dvb-usb: no frontend was attached by 'Hauppauge Nova-T Stick' [ 612.816285] dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected. I assume the numbers on the device itself have some sort of meaning so the first line is: M/R:70001/A1B5 #3006 The second line changes between devices but its along the lines of 000DFE0A84D2 LF Can I provide any additional information or help in order to help work out why this doesn't work? Many thanks, Dave ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Dave, It's the same type of stick that I've got - same problem as I see. If you turn on debugging by adding 'options dvb_usb_dib0700 debug=1' to the /etc/modprobe.conf. (or whatever, try /sbin/modinfo dvb_usb_dib0700 and it'll print out the parameters that it uses), you may get the same as I do: I2C read failed on address 9 DiB7000M:i2c read error on 896 DiB7000M:-E- DiB7000M: wrong Vendor ID (read=0x4602) dvb-usb: no frontend was attached by 'Hauppauge Nova-T Stick' I emailed Patrick Boettcher and this list describing the problem. (I actually bought the stick when he announced preliminary support ;(. Patrick seems to have access to the specs for the DibCom 7000 or the frontend. (I think that he may work with/for DibCom), but he appears to be very busy. I wish companies would open up their specs a bit more. I could spend time reading them rather than waiting for someone to have some free time to work on it. I mustn't grumble though at least some progress has been made. So as it stands it doesn't work. Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] USB2 DVB-S support
Graham Leggett wrote: Hi all, I have been searching for a USB2 DVB-S receiver that is capable of receiving a full transport stream, with working Linux drivers. The last time I looked, the only USB capable receivers out there were v1.1, and incapable of receiving a full TS as a result. Are there any devices out there that are known to work? actually there is at least this pinnaclesys pctv400e: http://www.pinnaclesys.com/PublicSite/uk/Products/Consumer+Products/PCTV+Tuners/PCTV+Digital+PVR+%28DVB-S_DVB-T%29/PCTV+400e.htm i see now that is called a legacy product because it's superseeded by another device DVB-S2 compliant (and on linux DVB-S2 is still a WIP) i own the pctv400e it is composed by a bunch of well known chips, so Patrick Boettcher made the first tentative of a driver: http://www.mail-archive.com/linux-dvb@linuxtv.org/msg20124.html and i tried to run it just one time with an oops.. i never had the time to work on it, because i've quite a busy schedule, these days, anyway i'd like to make a second trial on a fresh 2.6.18 kernel and without the nvidia binary module that is tainting my PC! i hope to post you about this, in the next days.. bye andrea venturi ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
