Re: [linux-dvb] DVICO NANO Australia
I'm still having the same problem with my NANO2 as well. Managed to use a workaround: 1. Removed the dvb_usb_cxusb module using rmmod 2. Connected the USB device into a VMWare instance running XP 3. The Windows driver seems to bootstrap the firmware.. 4. Disconnected from vmware 5. did a 'modprobe dvb_usb_cxusb' 6. The device gets recognised as having a zl10353 ;) I'm using 2.6.21.1 with the xc-bluebird.patch -- Eugene On Nov 8, 2007 3:31 PM, Collier Family [EMAIL PROTECTED] wrote: Thanks for the fast response - yes it does work in windows. - Original Message - From: Michael Krufky [EMAIL PROTECTED] To: Collier Family [EMAIL PROTECTED] Cc: linux-dvb@linuxtv.org Sent: Thursday, November 08, 2007 2:58 PM Subject: Re: [linux-dvb] DVICO NANO Australia Michael Krufky wrote: Collier Family wrote: I have a DVICO NANO but I am having the same troubles others had in June. It appears it is not being recognised as being cold. I have followed the instructions at http://fremnet.net/article/228/dvico-fusionhdtv-dual-digital-4-under-linux and all went well except the frontend not set. dmesg follows usb 5-8: new high speed USB device using ehci_hcd and address 9 usb 5-8: configuration #1 chosen from 1 choice dvb-usb: found a 'DViCO FusionHDTV DVB-T NANO2' in warm state. dvb-usb: bulk message failed: -22 (2/0) dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (DViCO FusionHDTV DVB-T NANO2) dvb-usb: bulk message failed: -110 (1/0) dvb-usb: bulk message failed: -110 (3/0) dvb-usb: bulk message failed: -110 (3/0) dvb-usb: bulk message failed: -110 (5/0) dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T NANO2' dvb-usb: DViCO FusionHDTV DVB-T NANO2 successfully initialized and connected. Is there any other information that may help I am running vanilla 2.6.23.1 kernel on Scientific linux 5.0 Thanks a lot for the work so far. The DVB-T NANO2 does not require the bluebird firmware -- the fx2 boots it from the eeprom. So, the device does not have a cold state. The only firmware that you need for it is the xc3028 firmware that was used in Markus' xc3028 kernel driver. However, there is alternate firmware required for the xc3028 for use in Australia. I assume that you already have that. Sorry, I forgot to add the helpful advice ;-) ...It looks like the driver is having trouble accessing the zl10353. Can you check to make sure the device works in windows? -Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Anysee E30 DVB-devices
hello I haven't got too many test reports (ONLY 4-5, but this is most likely that driver works I hope :) and I don't even have those three devices driver support. I have only E30C Plus (DVB-T) borrowed by Jyrinki. Also I know there is performance issue in DVB-C device coming from tda10023 demodulator driver. At least, I have to isolate this problem before I can pull. tda10023 demodulator driver is also used by some other cards so we need test reports from others as well in this case. The problem I know is reported by user in cable network Salo Finland. He says that all channels are not locked. I have send test version of tda10023 driver to him and after that all channels are locked. Anyhow, he haven't isolated needed value yet. If there is any other who can help this question please contact. And please, send reports even if driver works. Thats the only way I know how much it has been tested. Reports can be send directly to my mail if subscription to linux-dvb mailing list is too big task :) Regards Antti Palosaari Mauro Carvalho Chehab wrote: Hi Tuomas, I'm sorry to interrupt you like this, because I have only one tiny question. When those Anysee E30 drivers are embedded from http://linuxtv.org/hg/~anttip/anysee/ to the main release ? It depends on the driver author, since I didn't received any pull request from Antti. With the current Kernel workflow, if I receive the pull request while the latest kernel is 2.6.23, the newer features will be available for kernel 2.6.25. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan VP1041 and 64-bit FC6 troubles
hy, pherhaps you like to try this patch against the current multiproto branch on http://jusst.de/hg/multiproto/. http://pansy.at/gernot/twinhan-vp1041.diff.gz it's working much better for me. also it compiles with recent kernels. gernot p.s.: if you want to test it mythtv, youd could try this hack against current svn: http://pansy.at/gernot/mythtv-multiproto-hack.diff.gz On Saturday 06 October 2007 19:16:57 Simeon Simeonov wrote: Hello everyone, I have hard time getting the VP1041 (Azureware AD-SP 400) to work properly with 64-bit FC6. I used the drivers from Twinhan web site. First compiled them with the stock kernel-2.6.18-1.2798, then I tried with the latest 2.6.22 -2 FC6 kernel. The drivers compile OK. They also load just fine, the frontend is created and all of the nodes in /dev/dvb* are created just fine. The problem is when I try to use the interface - as soon as I try to open the frontend I get kernel Oops. It looks like stb0899 module is not happy about something. I've seen that some people are using the card - how did you guys get it to work? Could it be the 64-bit that is giving me problems? Thanks. Simeon ___ _ Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppauge Nova-T stick variants
Simeon Walker wrote: Can anyone tell me about the different versions of the Nova-T USB Stick? I see the model 00294 at a few shops in the UK and that seems to be supported, but I also sometimes see the model 99063 called the WinTV Nova-T Stick Lite. Is this version supported? A friend of mine recently bought a WIN-TV NOVA T-LITE DVB-T STICK. The box is marked with model 308 (it is a German version). This item is supported, it wants to load the firmware dvb-usb-dib0700-01.fw. The same supplier has another model called HAUPPAUGE NOVA T DVB-T STICK RC - I have no idea if it is supported. The difference seems to be that the non-lite version is delivered with an additional remote control, which nearly doubles the price :) Nils ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [v4l-dvb-maintainer] [RFC: 2.6 patch] remove saa7134-oss
Hi Adrian, Em Sex, 2007-11-09 às 07:03 +0100, Adrian Bunk escreveu: The saa7134-oss is deprecated for quite some time, it's the only remaining OSS user outside of sound/oss/, and considering how few and what kind of soundcards are left supported by OSS I hardly see any use cases left. Since saa7134-alsa seems to do the job, it seems ok to remove saa7134-oss. Signed-off-by: Adrian Bunk [EMAIL PROTECTED] Acked-by: Mauro Carvalho Chehab [EMAIL PROTECTED] I'll commit this patch soon at my tree. Cheers, Mauro ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [Fwd: Re: [hg:v4l-dvb] [PATCH] Leadtek Winfast DTV Dongle remote control]
Hi all, I was adviced that Leadtek Winfast DTV Dongle remote controller uses NEC communication protocol (dvb_usb_dib0700_ir_proto=0 param) instead RC5 (require patch from http://www.grunau.be/dib0700_rc_query.diff is in hg sources now?). I repair patch, but not send it again to v4l-dvd mailing list. http://blog.djaara.net/DTV_Dongle_keycodes_NEC.patch Patch from Jaroslav Barton píše v Po 12. 11. 2007 v 14:50 +0100: The patch number 6588 was added via Patrick Boettcher [EMAIL PROTECTED] to http://linuxtv.org/hg/v4l-dvb master development tree. Kernel patches at this development tree might be modified to keep backward compatibility with older kernels. Those compatibility stuff will be removed during preparation to be included at kernel mainstream. If anyone has any objections, please let us know by sending a message to: [EMAIL PROTECTED] -- From: Jaroslav Barton [EMAIL PROTECTED] [PATCH] Leadtek Winfast DTV Dongle remote control Add remote controller support for Leadtek Winfast DTV Dongle based on DiB7700P, MT2060 and using last drivers (6040:6a79c243aecc), firmware dvb-usb-dib0700-03-pre1.fw Signed-off-by: Jaroslav Barton [EMAIL PROTECTED] Signed-off-by: Patrick Boettcher [EMAIL PROTECTED] -- Jaroslav Bartoň DjAARA [EMAIL PROTECTED] [EMAIL PROTECTED] +420 608 620 897 JID : [EMAIL PROTECTED] JID2: [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan VP1041 and 64-bit FC6 troubles
hy, i have updated my patch. now it's also based on the current mantis tree on jusst.de (much improved i2c code, so intialization tunning is much faster) http://pansy.at/gernot/twinhan-vp1041-2.diff.gz gernot On Monday 12 November 2007 13:54:27 Gernot Pansy wrote: hy, pherhaps you like to try this patch against the current multiproto branch on http://jusst.de/hg/multiproto/. http://pansy.at/gernot/twinhan-vp1041.diff.gz it's working much better for me. also it compiles with recent kernels. gernot p.s.: if you want to test it mythtv, youd could try this hack against current svn: http://pansy.at/gernot/mythtv-multiproto-hack.diff.gz On Saturday 06 October 2007 19:16:57 Simeon Simeonov wrote: Hello everyone, I have hard time getting the VP1041 (Azureware AD-SP 400) to work properly with 64-bit FC6. I used the drivers from Twinhan web site. First compiled them with the stock kernel-2.6.18-1.2798, then I tried with the latest 2.6.22 -2 FC6 kernel. The drivers compile OK. They also load just fine, the frontend is created and all of the nodes in /dev/dvb* are created just fine. The problem is when I try to use the interface - as soon as I try to open the frontend I get kernel Oops. It looks like stb0899 module is not happy about something. I've seen that some people are using the card - how did you guys get it to work? Could it be the 64-bit that is giving me problems? Thanks. Simeon _ __ _ Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Review] Multiproto tree
Manu Abraham wrote:
Oliver Endriss wrote:
...
For now I ignored all differences, except for:
- frontend.h
- dvb_frontend.[ch]
- budget-ci.c
- budget-av.c
API extensions (frontend.h)
---
looks fine
Card drivers (budget-ci, budget-av)
---
I didn't check the details, but the extensions look ok.
You might consider whether parts of the stb0899/stb6100 stuff could be
factored out into a header file. See bsru6.h for an example.
It would reduce the file size, and tables etc could be reused.
The tables in some cases can't be reused, but the functions can be, due to
the initial cut and paste (tables), both set of tables have some amount of
common factor, But still in the end there will be a large common factor
altogether.
Ok, It does make sense to move it out to a common header.
If there are only minor differences, some settings could be moved to the
xxx_config struct. A different approach might use #ifdef blocks within
the header file. One could easily select a configuration by doing
#define xxx_CONFIG_A
#include xxx.h
dvb-core: dvb_frontend.c
fe-legacy is turned on/off by various ioctls:
- FE_SET_FRONTEND, FE_GET_FRONTEND - 1
- DVBFE_SET_PARAMS - 0/1
- DVBFE_GET_PARAMS, DVBFE_GET_DELSYS, DVBFE_GET_INFO - 0
fe-legacy controls how the frontend thread works.
Since the frontend device can be accessed by multiple readers,
fe-legacy might be toggled in funny ways.
This might confuse the fe thread or dvb_frontend_add_event. ;-(
Imho ioctls should not set fe-legacy. All parameter conversions should
be done within the ioctl. For example:
- new driver: FE_SET_FRONTEND converts parms to new driver API
- old driver: DVBFE_SET_PARAMS converts parms to old driver API
Then the fe thread can simply use the old driver interface
(fe-legacy==1) or the new one (fe-legacy==0).
What's your thought, if i just checked for the new callbacks and handled the
legacy switch, ie: the check occuring in the init, so on an fe_open() the
legacy switch will be set, depending upon the driver. That way things would
be set just before the thread is started and still be independent of any
ioctl
handling, thereby avoiding the flip-flop case with an ioctl.
What do you think ?
Doing this in dvb_register_frontend() seems to be the perfect place,
because all callbacks have been set, and fe device/thread do not exist
yet.
The error msg should display the offending parameter:
Instead of
+ printk(%s: Unsupported FEC\n, __func__);
you might use
+ printk(KERN_ERR %s: Unsupported FEC %x\n, __func__,
new_fec);
(same way for other conversion routines)
Ok, fine. Better in fact.
+ /* Legacy */
+ if (fe-legacy) {
+ if (fe-ops.set_frontend)
+ fe-ops.set_frontend(fe, fepriv-parameters);
+ } else {
+// if ((dvbfe_sanity_check(fe) == 0)) {
+ /* Superseding */
+ if (fe-ops.set_params)
+ fe-ops.set_params(fe, fepriv-fe_params);
+// } else
+// return -EINVAL;
+ }
Sanity checks should be done in FE_SET_FRONTEND/DVBFE_SET_PARAMS ioctls.
(See HG master where I added this some time ago.)
Otherwise the application would not see an error status.
True, didn't think about returning the error back to the app. Will fix.
/* don't actually do anything if we're in the LOSTLOCK state,
-* the frontend is set to FE_CAN_RECOVER, and the max_drift is 0 */
- if ((fepriv-state FESTATE_LOSTLOCK)
- (fe-ops.info.caps FE_CAN_RECOVER) (fepriv-max_drift ==
0)) {
- dvb_frontend_swzigzag_update_delay(fepriv, s FE_HAS_LOCK);
- return;
+* the frontend is set to FE_CAN_RECOVER, and the max_drift is 0
+*/
+ /* Legacy */
+ if (fe-legacy) {
+ if ((fepriv-state FESTATE_LOSTLOCK)
(fepriv-max_drift == 0)) {
+ if (fe-ops.get_frontend_algo)
+ if (fe-ops.get_frontend_algo(fe) ==
DVBFE_ALGO_RECOVERY)
+
dvb_frontend_swzigzag_update_delay(fepriv, s FE_HAS_LOCK);
+
+ return 0;
+ }
+ } else {
+ if (fepriv-state FESTATE_LOSTLOCK) {
+ if (fe-ops.get_frontend_algo) {
+ if ((fe-ops.get_frontend_algo(fe) ==
DVBFE_ALGO_RECOVERY)
+ (fepriv-max_drift == 0)) {
+
+
dvb_frontend_swzigzag_update_delay(fepriv, s DVBFE_HAS_LOCK);
+ return 0;
+ }
Re: [linux-dvb] KNC1 TV-Station S, revision 0x1894, doesn't tune
thanks for the suggestions
the results are both good and less good ...
the motherboard is an M2NPV-VM, which has 2 PCI slots
I tried both cards in both slots : in one slot both cards work but in the other
slot none of them
(it's possible that the card in the 'right' slot wasn't seated properly earlier)
so the good news is that the drivers are working, and tuning is ok (haven't
tried encrypted channels yet)
more good news : both cards are ok too
the bad news is that I'm left with a single working PCI slot (and MythTV really
shines with multiple cards)
assuming it's a PCI-power problem, how can this be fixed ?
would changing the power supply work ?
thanks again,
Luc
Oliver Endriss wrote:
Luc Brosens wrote:
hello,
I've just put two of these card in my machine, and seem to run into the
tuner issue described at
http://www.linuxtv.org/wiki/index.php/TerraTec_Cinergy_1200_DVB-S_budget/Typhoon/KNC1_DVB-S_budget
has anybody gotten these cards to work ?
any pointers on how to get tuning to work ?
I'm new to dvb-driver development, suggestions on how to get started are
welcome too
below are lspci output, dmesg output and scan output :
DMESG
saa7146: register extension 'budget_av'.
PCI: Setting latency timer of device :00:10.1 to 64
ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
ACPI: PCI Interrupt :04:08.0[A] - Link [APC1] - GSI 16 (level, low) -
IRQ 16
saa7146: found saa7146 @ mem c20010606000 (revision 1, irq 16)
(0x1894,0x0016).
saa7146 (0): dma buffer size 192512
DVB: registering new adapter (KNC TV STAR DVB-S)
adapter failed MAC signature check
encoded MAC from EEPROM was
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff
KNC1-0: MAC addr = 00:09:d6:65:9d:14
DVB: registering frontend 0 (ST STV0299 DVB-S)...
budget-av: ci interface initialised.
The initialisation of the first card looks ok.
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
ACPI: PCI Interrupt :04:09.0[A] - Link [APC2] - GSI 17 (level, low) -
IRQ 17
saa7146: found saa7146 @ mem c2001061c000 (revision 1, irq 17)
(0x1894,0x0016).
saa7146 (1): dma buffer size 192512
DVB: registering new adapter (KNC TV STAR DVB-S)
saa7146 (1) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer
saa7146 (1) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer
saa7146 (1) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer
saa7146 (1) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer
Couldn't read from EEPROM: not there?
saa7146 (1) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer
saa7146 (1) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer
saa7146 (1) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer
saa7146 (1) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer
KNC1-1: Could not read MAC from KNC1 card
DVB: registering frontend 1 (ST STV0299 DVB-S)...
budget-av: ci interface initialised.
budget-av: cam inserted B
saa7146: register extension 'dvb'.
dvb_ca adaptor 1: PC card did not respond :(
not all of these messages seem positive, should I worry ?
Yes. The second card does not work properly (I2C bus errors).
SCAN
silverstar:/home/myth # scan -vvv -a 1 /usr/share/dvb/dvb-s/Astra-19.2E
scanning /usr/share/dvb/dvb-s/Astra-19.2E
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder 12551500 V 2200 5
tune to: 12551:v:0:22000
DiSEqC: switch pos 0, 13V, hiband (index 2)
diseqc_send_msg:56: DiSEqC: e0 10 38 f1 00 00
DVB-S IF freq is 1951500
tuning status == 0x02
tuning status == 0x02
tuning status == 0x03
tuning status == 0x02
tuning status == 0x03
tuning status == 0x02
tuning status == 0x02
tuning status == 0x02
tuning status == 0x02
tuning status == 0x02
WARNING: tuning failed!!!
tune to: 12551:v:0:22000 (tuning failed)
DiSEqC: switch pos 0, 13V, hiband (index 2)
diseqc_send_msg:56: DiSEqC: e0 10 38 f1 00 00
DVB-S IF freq is 1951500
tuning status == 0x02
tuning status == 0x02
tuning status == 0x02
tuning status == 0x02
tuning status == 0x02
tuning status == 0x01
tuning status == 0x01
tuning status == 0x02
tuning status == 0x02
tuning status == 0x02
WARNING: tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.
scan works with the first card ('-a 0'), correct?
the signal from the satellite is fine, have been using a settop box for
several months
a Skystar 2 card in the same machine scanned successfully and gave access to
the FTA channels
I'm using OpenSUSE 10.3, kernel version 2.6.22.12, dvb archive 816f256c2973
(downloaded it yesterday)
Swap the cards.
- If the errors moves to saa7146(0), the card might be broken.
- If the errors still come from saa7146(1), try a different PCI slot.
(I2C errors might be caused by noise on power supply lines.)
CU
Oliver
___
linux-dvb mailing list
Re: [linux-dvb] Is SkyStar2 Rev 2.7V supported?
Hi Patrick, first of all: Thanks for your answer. I was starting in 2006 to write a driver the SS2 Rev 2.7A. I'm not sure how much different the V-version is, but all my work so far can be found here: http://linuxtv.org/hg/~pb/v4l-dvb.skystar2.rev27/ Yes, I saw that last week but gave up because it didn't compile with kernel 2.6.23. And since there was no modification for seven months, I assumed this branch isn't actively developed on... ... I even don't have a windows driver for the card I have, so I'm not even sure whether they work at all. As far as I can tell, my card (SkyStar2 Rev2.7V) works with Windows Vista Ultimate and Windows XP Home, see below. The drivers in my repository are not complete, in fact they will not tune at all, but they can be used as a base to finish development. Ok, then I'm happy a good friend which uses Windows only offered to exchange his Nova-S+ against my SkyStar2. So I'm happy with the Nova-S+ (together with a Nexus-S and a Nova-S) and he's using the SkyStar2 with Windows. Problem solved - at least for me ;-) Greetings, Alex ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppauge Nova-T stick variants
I demand that Nils Kassube may or may not have written... Simeon Walker wrote: Can anyone tell me about the different versions of the Nova-T USB Stick? I see the model 00294 at a few shops in the UK and that seems to be supported, but I also sometimes see the model 99063 called the WinTV Nova-T Stick Lite. Is this version supported? A friend of mine recently bought a WIN-TV NOVA T-LITE DVB-T STICK. The box is marked with model 308 (it is a German version). This item is supported, it wants to load the firmware dvb-usb-dib0700-01.fw. What's on the label? (Ignore the MAC address.) What's its USB ID? The same supplier has another model called HAUPPAUGE NOVA T DVB-T STICK RC - I have no idea if it is supported. The difference seems to be that the non-lite version is delivered with an additional remote control, which nearly doubles the price :) That's probably the only difference, given that mine has an IR sensor but wasn't supplied with a remote control. Still, confirmation that that is the only difference would be helpful. Information should be added to this page: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-Stick -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | URL:http://www.youmustbejoking.demon.co.uk/ (PGP 2.6, GPG keys) A bird in the hand is worth what it will bring. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppauge Nova-T stick variants
Darren Salt wrote: I demand that Nils Kassube may or may not have written... Simeon Walker wrote: Can anyone tell me about the different versions of the Nova-T USB Stick? I see the model 00294 at a few shops in the UK and that seems to be supported, but I also sometimes see the model 99063 called the WinTV Nova-T Stick Lite. Is this version supported? A friend of mine recently bought a WIN-TV NOVA T-LITE DVB-T STICK. The box is marked with model 308 (it is a German version). This item is supported, it wants to load the firmware dvb-usb-dib0700-01.fw. What's on the label? (Ignore the MAC address.) M/R: 70009/C1B5 #3107 MAC address LF What's its USB ID? 2040:7060 Nils ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppauge Nova-T stick variants
I believe it may be a model 00294 without the remote control. I should be finding out tomorrow. I just hope eBay does not beckon again... ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Need help in setting up my kworld nb 220 card on ubuntu 7.10
On Nov 12, 2007 5:36 PM, hermann pitton [EMAIL PROTECTED] wrote: Am Sonntag, den 11.11.2007, 20:56 -0600 schrieb ying lcs: On Nov 11, 2007 8:19 PM, hermann pitton [EMAIL PROTECTED] wrote: ... We have some how to add a new card stuff on the v4l-wiki then. Nevertheless, to try card=88. modprobe -vr saa7134-dvb saa7134-alsa tuner tda827x modprobe -v saa7134 i2c_scan=1 My, modprobe -v saa7134 card=88 i2c_scan=1 Hermann Thanks for the help. I tried your suggestion: # modprobe -v saa7134 card=88 i2c_scan=1 # dmesg | grep dvb # dmesg | grep dvb # ls -l /dev/dvb/adapter* ls: /dev/dvb/adapter*: No such file or directory But there is still nothing in /dev/dvb/adapter* Thanks for any more pointers. Hi, if you are not on recent v4l-dvb from linux-tv.org or on some latest kernels, you need to modprobe saa7134-dvb debug=1 manually. This goes for saa7134-alsa too until today. See the v4l-wiki for that. I am runnning ubuntu 7.10. And I just tried # modprobe saa7134-dvb debug=1 # dmesg | grep dvb # And I still get nothing dmesg. Still interested in your dmesg for saa7134 card=88 and detection of tuner and other chips with i2c_scan=1. As said, a Kworld NB 220 PCI card is unknown to me. Try google, there are only this new NB-TV 220 pcmcia/cardbus. Here are good details of the hardware on that one. http://www.ixbt.com/monitor/kworld-nb-tv220.shtml This one _could eventually_ work with card=88. To try FlyDVB-T Duo with different audio clock, we can override with with audio_clock=N seems not to have any advantage against card=88 on a device without analog radio and remote. If you can't verify that you have almost the same on a PCI variant, as listed previously for chips, xtals and i2c addresses, we need all details. There is not much left for try and error luck on such recent devices. That you have a new Kworld card with new subdevice ID is all we have so far. Also nothing else in the eeprom and no patterns on gpio pins. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Need help in setting up my kworld nb 220 card on ubuntu 7.10
Am Sonntag, den 11.11.2007, 20:56 -0600 schrieb ying lcs: On Nov 11, 2007 8:19 PM, hermann pitton [EMAIL PROTECTED] wrote: ... We have some how to add a new card stuff on the v4l-wiki then. Nevertheless, to try card=88. modprobe -vr saa7134-dvb saa7134-alsa tuner tda827x modprobe -v saa7134 i2c_scan=1 My, modprobe -v saa7134 card=88 i2c_scan=1 Hermann Thanks for the help. I tried your suggestion: # modprobe -v saa7134 card=88 i2c_scan=1 # dmesg | grep dvb # dmesg | grep dvb # ls -l /dev/dvb/adapter* ls: /dev/dvb/adapter*: No such file or directory But there is still nothing in /dev/dvb/adapter* Thanks for any more pointers. Hi, if you are not on recent v4l-dvb from linux-tv.org or on some latest kernels, you need to modprobe saa7134-dvb debug=1 manually. This goes for saa7134-alsa too until today. See the v4l-wiki for that. Still interested in your dmesg for saa7134 card=88 and detection of tuner and other chips with i2c_scan=1. As said, a Kworld NB 220 PCI card is unknown to me. Try google, there are only this new NB-TV 220 pcmcia/cardbus. Here are good details of the hardware on that one. http://www.ixbt.com/monitor/kworld-nb-tv220.shtml This one _could eventually_ work with card=88. To try FlyDVB-T Duo with different audio clock, we can override with with audio_clock=N seems not to have any advantage against card=88 on a device without analog radio and remote. If you can't verify that you have almost the same on a PCI variant, as listed previously for chips, xtals and i2c addresses, we need all details. There is not much left for try and error luck on such recent devices. That you have a new Kworld card with new subdevice ID is all we have so far. Also nothing else in the eeprom and no patterns on gpio pins. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Need help in setting up my kworld nb 220 card on ubuntu 7.10
Am Montag, den 12.11.2007, 17:41 -0600 schrieb ying lcs: On Nov 12, 2007 5:36 PM, hermann pitton [EMAIL PROTECTED] wrote: Am Sonntag, den 11.11.2007, 20:56 -0600 schrieb ying lcs: On Nov 11, 2007 8:19 PM, hermann pitton [EMAIL PROTECTED] wrote: ... We have some how to add a new card stuff on the v4l-wiki then. Nevertheless, to try card=88. modprobe -vr saa7134-dvb saa7134-alsa tuner tda827x modprobe -v saa7134 i2c_scan=1 My, modprobe -v saa7134 card=88 i2c_scan=1 Hermann Thanks for the help. I tried your suggestion: # modprobe -v saa7134 card=88 i2c_scan=1 # dmesg | grep dvb # dmesg | grep dvb # ls -l /dev/dvb/adapter* ls: /dev/dvb/adapter*: No such file or directory But there is still nothing in /dev/dvb/adapter* Thanks for any more pointers. Hi, if you are not on recent v4l-dvb from linux-tv.org or on some latest kernels, you need to modprobe saa7134-dvb debug=1 manually. This goes for saa7134-alsa too until today. See the v4l-wiki for that. I am runnning ubuntu 7.10. And I just tried # modprobe saa7134-dvb debug=1 # dmesg | grep dvb # And I still get nothing dmesg. See above, you must unload all related modules previously with modprobe -vr Can't believe that you have a custom kernel with all statically compiled in. Then modprobe saa7134 i2c_scan=1. Then modprobe saa7134-dvb or set options saa7134 ..., options saa7134-dvb ... amd whatsoever in /etc/modprobe.conf or what ever Ubuntu uses for it and depmod -a. Use modinfo module_name to know more. What says uname -a? Where can one buy this card? Cheers, Hermann Still interested in your dmesg for saa7134 card=88 and detection of tuner and other chips with i2c_scan=1. As said, a Kworld NB 220 PCI card is unknown to me. Try google, there are only this new NB-TV 220 pcmcia/cardbus. Here are good details of the hardware on that one. http://www.ixbt.com/monitor/kworld-nb-tv220.shtml This one _could eventually_ work with card=88. To try FlyDVB-T Duo with different audio clock, we can override with with audio_clock=N seems not to have any advantage against card=88 on a device without analog radio and remote. If you can't verify that you have almost the same on a PCI variant, as listed previously for chips, xtals and i2c addresses, we need all details. There is not much left for try and error luck on such recent devices. That you have a new Kworld card with new subdevice ID is all we have so far. Also nothing else in the eeprom and no patterns on gpio pins. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppauge Nova-T stick variants
[relevant context restored] I demand that Simeon Walker may or may not have written... I demand that Simeon Walker may or may not have written... Can anyone tell me about the different versions of the Nova-T USB Stick? I see the model 00294 at a few shops in the UK and that seems to be supported, but I also sometimes see the model 99063 called the WinTV Nova-T Stick Lite. Is this version supported? The former definitely is; I have no idea about the latter. Of course, you could always test one and report back (with the USB ID)... I believe it may be a model 00294 without the remote control. Hmm? Mine wasn't supplied with a remote control, and there's no evidence that it should have been. [snip] -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Lobby friends, family, business, government.WE'RE KILLING THE PLANET. Vital documents move from where they were left to where they can't be found. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Initial tuning file fi-3KTV DVB-C
hello There is file containing reference channels used in 3KTV networks around the Finland. There is about 20 3KTV networks but all didn't use exactly same channel list for reason or other. Now there is fi-Rauma and fi-Salo that contains same channels, should those removed? fi-3ktv (replace) fi-Rauma (same channels) fi-Salo (same channels) regards Antti # 3KTV network reference channels # freq sr fec mod C 17000 6875000 NONE QAM128 C 37000 6875000 NONE QAM128 C 36200 6875000 NONE QAM128 C 35400 6875000 NONE QAM128 C 34600 6875000 NONE QAM128 C 33800 6875000 NONE QAM128 C 32200 6875000 NONE QAM128 C 31400 6875000 NONE QAM128 C 16200 6875000 NONE QAM128 C 30600 6875000 NONE QAM128 C 15400 6875000 NONE QAM128 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] How could I play my composite tv using mplayer???
Dear everyone: How could I use mplayer to play my composite tv program. I use this command mplayer tv:// -tv driver=v4l2:device=/dev/video0:norm=NTSC:noaudio Seems no result. :-( ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
