[linux-dvb] Informations/Problems about Asus P7131 Hybrid
Hallo, I'm writing here becuase I need some informations about the Asus P7131 Hybrid (1043:4876, board: ASUSTeK P7131 Hybrid [card=112,autodetected]). 1. Which is the newest firmware for this board? I downloaded the "revision 29" from lifeview, is this the right one? 2. Is it possible to have the DVB-T on the TV input? In windows I plug the antenna (i have only one cable) to the TV-input and then I can decide between analog or digital TV. With Linux I have to plug the digital antenna on the FM input. That means plugging and unplugging each time I want to switch between analog or digital. (well, I will build an Y-cable!) 3. Digital reception is not very good. If I use my Pinnacle Hybryd Pro Stick I can watch more channels and reception is more stable. There is something I can do? I read about a "lowNoiseAmplifier" in kernel 2.6.22. I have kernel 2.6.20. Do I have to upgrade? (Sorry, but I cannot re-test the board under windows so I don't know if it's a "driver" problem or a "feature" of the board, lol) Information about my system: Hardware: Pentium IV 3.2GHz O.S.: Linux Ubuntu Feisty Fawn 7.04 Kernel: 2.6.20-16-generic V4L: updated on 4 Aug 2007 ( hg clone http://linuxtv.org/hg/v4l-dvb) Thank you for your suggestions. Paolo dmesg (excerpt) [...] [ 16.558570] saa7133[0]: found at :01:09.0, rev: 209, irq: 17, latency: 64, mmio: 0xcdcff800 [ 16.558579] saa7133[0]: subsystem: 1043:4876, board: ASUSTeK P7131 Hybrid [card=112,autodetected] [ 16.558590] saa7133[0]: board init: gpio is 0 [ 16.558691] input: saa7134 IR (ASUSTeK P7131 Hybri as /class/input/input4 [ 16.644515] NET: Registered protocol family 10 [ 16.644629] lo: Disabled Privacy Extensions [ 16.644690] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 16.644693] ADDRCONF(NETDEV_UP): eth1: link is not ready [ 16.692936] saa7133[0]: i2c eeprom 00: 43 10 76 48 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 [ 16.692957] saa7133[0]: i2c eeprom 10: ff ff ff 0f ff 20 ff ff ff ff ff ff ff ff ff ff [ 16.692976] saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff 00 d5 ff ff ff ff [ 16.692993] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 16.693011] saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 55 50 ff ff ff ff ff ff [ 16.693029] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 16.693047] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 16.693066] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 16.728324] nvidia: module license 'NVIDIA' taints kernel. [ 17.075942] tuner 0-004b: chip found @ 0x96 (saa7133[0]) [ 17.123871] tuner 0-004b: setting tuner address to 61 [ 17.163865] tuner 0-004b: type set to tda8290+75a [ 17.552228] NET: Registered protocol family 17 [ 18.047866] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both [ 18.315271] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 18.544574] tuner 0-004b: setting tuner address to 61 [ 18.584483] tuner 0-004b: type set to tda8290+75a [ 19.925491] saa7133[0]: registered device video0 [v4l2] [ 19.925692] saa7133[0]: registered device vbi0 [ 19.925877] saa7133[0]: registered device radio0 [ 19.989199] ACPI: PCI Interrupt :05:00.0[A] -> GSI 16 (level, low) -> IRQ 16 [ 19.989215] PCI: Setting latency timer of device :05:00.0 to 64 [ 19.989340] NVRM: loading NVIDIA UNIX x86 Kernel Module 1.0-9755 Mon Feb 26 23:21:15 PST 2007 [ 19.989356] ACPI: PCI Interrupt :00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16 [ 19.989378] PCI: Setting latency timer of device :00:1b.0 to 64 [ 20.039518] saa7134 ALSA driver for DMA sound loaded [ 20.039554] saa7133[0]/alsa: saa7133[0] at 0xcdcff800 irq 17 registered as card -2 [ 20.213308] DVB: registering new adapter (saa7133[0]) [ 20.213313] DVB: registering frontend 0 (Philips TDA10046H DVB-T)... [ 20.284505] tda1004x: setting up plls for 48MHz sampling clock [ 20.484453] fuse init (API version 7.8) [ 20.532912] lp0: using parport0 (interrupt-driven). [ 20.567846] tda1004x: found firmware revision 29 -- ok [...] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [RFC PATCH] Choose dvb adapter number with a driver specific module option
Oliver Endriss wrote:
> Janne Grunau wrote:
>> Dynamic loading of modules by udev on startup (aka coldplugging) doesn't
>> result in deterministic dvb adapter numbers.
>>
>> Besides following changes in dvb-core and dvb-usb core the patch adds to
>> all drivers
>> ...
>
> While I don't care much whether there is an option for this in the
> driver, I'd like to point out that this is the wrong approach (imho).
>
> Citing Greg Kroah-Hartman (udev-113/docs/udev_vs_devfs):
> |...
> |2) udev does not care about the major/minor number schemes. If the
> | kernel tomorrow switches to randomly assign major and minor numbers
> | to different devices, it would work just fine (this is exactly
> | what I am proposing to do in 2.7...)
> |3) This is the main reason udev is around. It provides the ability
> | to name devices in a persistent manner. More on that below.
> |...
>
> According to this, adding such an option is a step into the wrong
> direction. The right way is to fix the udev scripts...
I've just written udev rules for my set-up. udev may be the correct way
to do this but it is far from easy. Having the adapter number specified
as a driver option would be much simpler.
I have an Opera DVB-S USB device and a Nova T-500 containing two DVB-T
devices. Depending on whether the Opera is in warm or cold state the
kernel may number the Opera as 0 and the two Nova devices as 1 and 2 or
the Nova as 0 and 1 with the Opera as 2. For Myth, though, I want to be
sure that the Opera has a specific device (e.g. /dev/dvb/adapter7/*)
while the Nova devices have two other specific devices (e.g.
/dev/dvb/adapter0/* and /dev/dvb/adapter1/*).
Writing a udev rule to pin the Opera to a specific adapter number was
fairly easy. Since there is only a single device I could match on the
USB identifiers. The Nova, though, has two devices and these are
indistinguishable, at least from what udevinfo provides. That means
that it isn't possible to write a udev rule that would match one device
and make it /dev/dvb/adapter0 and a different rule to make the other
/dev/dvb/adapter1. I was reduced to writing a script that would detect
whether /dev/dvb/adapter{0,1} existed and if it did whether the entries
that were already in that directory had the same minor device number
divided by 64 as the minor device number of new device, divided by 64.
This was the only way to make sure that /dev/dvb/adapter0 and
/dev/dvb/adapter1 contained the correct devices and entries weren't
mixed up.
There may be another way to do this but I couldn't think of one. Maybe
the Nova device driver should be changed to ensure the two devices are
distinguishable in some way. If udev is being relied upon as the only
way to pin device entries there needs to be a library of udev rules for
each device that people can copy. Otherwise I think Janne's patch is a
sensible way to go.
David.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] extra switch for tzap
Hi, Am Freitag, 20. Juli 2007 12:37 schrieb P. van Gaans: > diff -urN oldfile.c newfile.c > lolwat.diff appears to work luckily. If you clone dvb-apps with hg you can simply do "hg diff" to get the modifications. The other possibility is to copy the whole directory before modifying and to diff them recursively (-r) afterwards. Anyway, doesn't matter here anymore - I'll deal with the stuff you attached (+ fix a bit coding style :) > Tzap was patched already. > Szap patched, compiles, tested and OK. > Czap patched, compiles without errors, untested because I hate my cable > provider and the box I would have to install the cable card in is really > noisy and unstable. Whoever wants to test: please report results, czap > looks a little different from szap and tzap but I'm pretty certain it'll > work straightaway. I assume this is OK, you couldn't expect all linuxtv > developers to own cards for all DVB-systems anyway.. > Femon patched in a different way: Femon already has a "human readable" > switch, I just made BER and uncorrected show up as decimal instead of > hex in human readable mode. Adding another switch sounds pointless to me. Hmm, maybe the same switch name should be used everywhere, for example "-H" (for human readable)? > The numbers/output seem to differ between devices and between szap and > tzap greatly so for now I'm not going to try to make them more > human-readable because of the possibility of breaking something. > > Everything attached. Thanks, Christoph ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] New tuning file for Astra 28.2E
Hi, Am Mittwoch, 25. Juli 2007 13:46 schrieb Marvin Hankley: > Hi! > > > > So, I made the complete list. I > > > know scan is capable of detecting other transponders from a smaller > > > number but do we lose anything from having a more complete list than > > > is strictly necessary? > > > > The problem arises when some of them become invalid because you get > > timeouts then. It's also a bit more difficult to maintain them (but > > that's the case anyway ;) - hmm, will see and think a bit about this ... > > the main issue remains: where to get an authoritative source of > > information? > > Right, that is a problem, so I guess there must be some balance > between receiving timeouts on one hand and not receiving the full list > of channels on the other hand. Personally, I'd be slightly inclined > towards enabling users to get the full list of channels. I'd think > re-scanning is not something people are going to do too often, so > perhaps if it might potentially take a little longer, that could be a > price worth paying, in order to get the full list of channels? > > Another potential good use for a complete list is when searching for > feeds. These transponders tend to be only used occasionally and I > doubt they will appear in NITs. So, I suspect that the only way of > detecting these channels will be to manually scan the transponder > list. > > Given all that, these are just text files in some obscure corner of > the filesystem. My full list containing all the transponders from the > four satellites at 28.2E was only 4 Kb, so perhaps it might be > feasible to ship _two_ channel lists, where available? A minimal > starter file and, where available, a more complete list? > > I'm not aware of any authoritative source of information. What I used > to produce my list was a combination of two internet sites, > http://www.lyngsat.com/ and http://en.kingofsat.net/ (another good one > is http://www.satcodx.com/ ), and then verifying those against the > satellite itself. > > Cheers, > Marv Right, so I'll apply your file (as there is no better option I can think of). Hmm, maybe a small tool that helps people to check whether their scan file is still ok or to actually produce a valid&correct scan file (from another scan file or whatever) would be feasible - let's see ... (this should simplify users to deal with that stuff so that more involvement is possible in cases where no authoritative source of information exists). Thanks, Christoph ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [linnux-dvb] add service type
Hi, Am Mittwoch, 18. Juli 2007 09:48 schrieb Younghyun Jo: > I add service type based on EN 300 468 V1.7.1(2005-12) Thanks, adding it :) Christoph ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] a new DVB-T initial-tuning-data file for Germany - City Leipzig
Hi, Am Mittwoch, 25. Juli 2007 21:29 schrieb Karsten: > Hi list, > > for the city Leipzig some dvb-t channels have changed since 07-23-2007. > Here is a new initial-tuning-data file for dvb-t in Germany, > City Leipzig. > > # DVB-T Leipzig > # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy > T 49800 8MHz 2/3 NONE QAM64 8k 1/4 NONE # ard einsfestival arte > phoenix > T 48200 8MHz 2/3 NONE QAM16 8k 1/4 NONE # zdf kika 3sat > T 20550 7MHz 2/3 NONE QAM64 8k 1/16 NONE # mdr rbb wdr br > > cheers > Karsten Applying, thanks :) Christoph ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Fwd: [Kaffeine-user] DVB-T in Dresden
From a kaffeine user ... Christoph -- Weitergeleitete Nachricht -- Subject: [Kaffeine-user] DVB-T in Dresden Date: Dienstag, 31. Juli 2007 21:45 From: HG Zaunick <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Hi, this is the channellist for the new DVB-T Transmitter in Dresden/Germany (on air since 23/7/07). cheers Hans Georg --- # DVB-T Dresden # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 53800 8MHz 2/3 NONE QAM64 8k 1/4 NONE # Kanal 29, mdr, rbb, wdr, br T 59400 8MHz 2/3 NONE QAM16 8k 1/4 NONE # Kanal 36, zdf, 3sat, kika, none T 61800 8MHz 2/3 NONE QAM64 8k 1/4 NONE # Kanal 39, ard, arte, phoenix, 1festival ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] initial scan file for nilesat
Hi, From a kaffeine user. Christoph # Nilesat 101/102 & Atlantic Bird @ 7W # freq pol sr fec S 10758000 V 2750 AUTO S 10796000 V 2750 AUTO S 10853000 H 2750 AUTO S 10873000 V 2750 AUTO S 10892000 H 2750 AUTO S 10911000 V 2750 AUTO S 1093 H 2750 AUTO S 11747000 V 2750 AUTO S 11766000 H 2750 AUTO S 11785000 V 2750 AUTO S 11804000 H 2750 AUTO S 11823000 V 2750 AUTO S 11843000 H 2750 AUTO S 11862000 V 2750 AUTO S 11881000 H 2750 AUTO S 1190 V 2750 AUTO S 11919000 H 2750 AUTO S 11938000 V 2750 AUTO S 11958000 H 2750 AUTO S 11977000 V 2750 AUTO S 11996000 H 2750 AUTO S 12015000 V 2750 AUTO S 12034000 H 2750 AUTO S 12054000 V 2750 AUTO S 12073000 H 2750 AUTO S 1213 V 2750 AUTO S 12149000 H 2750 AUTO S 12207000 V 2750 AUTO S 12226000 H 2750 AUTO S 12284000 V 2750 AUTO S 12303000 H 2750 AUTO S 12341000 V 2750 AUTO S 1236 H 2750 AUTO S 12399000 H 2750 AUTO ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [PATCH] DVB: remove bogus BUG_ON in videobuf_dvb_thread
Since videobuf_waiton is called with intr=1, it can return -EINTR and therefore err may be non-zero. This happens when the system goes into the standby state. Without the BUG() occurring, there's no problem with standby mode while DVB is being used. --- int videobuf_waiton(struct videobuf_buffer *vb, int non_blocking, int intr); [ 224.561803] Stopping tasks ... <0>[ cut here ] [ 224.712939] kernel BUG at drivers/media/video/video-buf-dvb.c:59! [ 224.712951] invalid opcode: [#1] [ 224.712957] PREEMPT [ 224.712969] Modules linked in: [ 224.712985] CPU:0 [ 224.712987] EIP:0060:[]Not tainted VLI [ 224.712989] EFLAGS: 00010286 (2.6.23-rc2-git #282) [ 224.713019] EIP is at videobuf_dvb_thread+0x160/0x170 [ 224.713028] eax: fffc ebx: 0282 ecx: edx: [ 224.713038] esi: eeda63c0 edi: b1a1fa3c ebp: ea82bfcc esp: ea82bfb0 [ 224.713046] ds: 007b es: 007b fs: gs: ss: 0068 [ 224.713055] Process saa7134[0] dvb (pid: 6649, ti=ea82a000 task=eb1d5550 task.ti=ea82a000) [ 224.713064] Stack: 0009 b011ec68 b1a1fa44 b1a1fb28 b1a1fa3c b03a05e0 fffc ea82bfe0 [ 224.713103]b0135dec b0135d90 b0104e57 ea82fd70 [ 224.713140] 09010df7 862a0510 [ 224.713170] Call Trace: [ 224.713178] [] show_trace_log_lvl+0x1a/0x30 [ 224.713206] [] show_stack_log_lvl+0x8b/0xb0 [ 224.713220] [] show_registers+0x1c3/0x320 [ 224.713235] [] die+0xff/0x210 [ 224.713248] [] do_trap+0x91/0xd0 [ 224.713261] [] do_invalid_op+0x88/0xa0 [ 224.713274] [] error_code+0x6a/0x70 [ 224.713296] [] kthread+0x5c/0x90 [ 224.713313] [] kernel_thread_helper+0x7/0x10 [ 224.713327] === [ 224.713335] Code: 8b 00 c7 04 24 c8 21 63 b0 89 44 24 04 e8 c9 29 d8 ff e9 cd fe ff ff 8b 07 c7 04 24 e8 21 63 b0 89 44 24 04 e8 b2 29 d8 ff eb c2 <0f> 0b eb fe 8d b6 00 00 00 00 8d bf 00 00 00 00 55 ba ea ff ff [ 224.713590] EIP: [] videobuf_dvb_thread+0x160/0x170 SS:ESP 0068:ea82bfb0 [ 224.713893] done. drivers/media/video/video-buf-dvb.c |1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/media/video/video-buf-dvb.c b/drivers/media/video/video-buf-dvb.c index e617925..d2af82d 100644 --- a/drivers/media/video/video-buf-dvb.c +++ b/drivers/media/video/video-buf-dvb.c @@ -56,7 +56,6 @@ static int videobuf_dvb_thread(void *data) struct videobuf_buffer, stream); list_del(&buf->stream); err = videobuf_waiton(buf,0,1); - BUG_ON(0 != err); /* no more feeds left or stop_feed() asked us to quit */ if (0 == dvb->nfeeds) -- 1.5.0.1 -- Simon Arlott ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] a new DVB-T initial-tuning-data file for Germany - City Leipzig
[ adding CC to the contributor of this file; maybe you have some comment? ] 2007/8/5, Christoph Pfister <[EMAIL PROTECTED]>: > Hi, > > Am Mittwoch, 25. Juli 2007 21:29 schrieb Karsten: > > Hi list, > > > > for the city Leipzig some dvb-t channels have changed since 07-23-2007. > > Here is a new initial-tuning-data file for dvb-t in Germany, > > City Leipzig. > > > > # DVB-T Leipzig > > # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy > > T 49800 8MHz 2/3 NONE QAM64 8k 1/4 NONE # ard einsfestival arte > > phoenix > > T 48200 8MHz 2/3 NONE QAM16 8k 1/4 NONE # zdf kika 3sat > > T 20550 7MHz 2/3 NONE QAM64 8k 1/16 NONE # mdr rbb wdr br > > > > cheers > > Karsten > > Applying, thanks :) > > Christoph The relevant change is 64200 --> 49800 afaics ... Christoph ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [PATCH] Updated GenPix USB driver
I've been pretty lax with this, and there are now 4 different versions
of the GENPIX USB adapter. The newest 'Skywalker' models are fully
self-contained, and need no additional hardware to be used. A very
reliable DVB-S card even without using any of the alternate
modulatations (which this kernel module does not currently support)
The following patch adds support for all 4 versions of the genpix
adapter (www.genpix-electronics.com).
Please apply,
Sign-off: Alan Nisota [EMAIL PROTECTED]
diff -r c45e373bbca3 linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
--- a/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h Sat Jul 28 00:06:44
2007 -0300
+++ b/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h Sun Aug 05 12:35:29
2007 -0700
@@ -152,8 +152,11 @@
#define USB_PID_WINFAST_DTV_DONGLE_COLD0x6025
#define USB_PID_WINFAST_DTV_DONGLE_WARM0x6026
#define USB_PID_WINFAST_DTV_DONGLE_STK7700P0x6f00
-#define USB_PID_GENPIX_8PSK_COLD 0x0200
-#define USB_PID_GENPIX_8PSK_WARM 0x0201
+#define USB_PID_GENPIX_8PSK_REV_1_COLD 0x0200
+#define USB_PID_GENPIX_8PSK_REV_1_WARM 0x0201
+#define USB_PID_GENPIX_8PSK_REV_2 0x0202
+#define USB_PID_GENPIX_SKYWALKER_1 0x0203
+#define USB_PID_GENPIX_SKYWALKER_CW3K 0x0204
#define USB_PID_SIGMATEK_DVB_110 0x6610
#define USB_PID_MSI_DIGI_VOX_MINI_II 0x1513
#define USB_PID_OPERA1_COLD0x2830
diff -r c45e373bbca3 linux/drivers/media/dvb/dvb-usb/gp8psk-fe.c
--- a/linux/drivers/media/dvb/dvb-usb/gp8psk-fe.c Sat Jul 28 00:06:44
2007 -0300
+++ b/linux/drivers/media/dvb/dvb-usb/gp8psk-fe.c Sun Aug 05 12:36:44
2007 -0700
@@ -1,7 +1,8 @@
/* DVB USB compliant Linux driver for the
- * - GENPIX 8pks/qpsk USB2.0 DVB-S module
- *
- * Copyright (C) 2006 Alan Nisota ([EMAIL PROTECTED])
+ * - GENPIX 8pks/qpsk/DCII USB2.0 DVB-S module
+ *
+ * Copyright (C) 2006,2007 Alan Nisota ([EMAIL PROTECTED])
+ * Copyright (C) 2006,2007 Genpix Electronics ([EMAIL PROTECTED])
*
* Thanks to GENPIX for the sample code used to implement this module.
*
@@ -17,27 +18,39 @@
struct gp8psk_fe_state {
struct dvb_frontend fe;
-
struct dvb_usb_device *d;
-
+ u8 lock;
u16 snr;
-
- unsigned long next_snr_check;
+ unsigned long next_status_check;
+ unsigned long status_check_interval;
};
+static int gp8psk_fe_update_status(struct gp8psk_fe_state *st)
+{
+ u8 buf[6];
+ if (time_after(jiffies,st->next_status_check)) {
+ gp8psk_usb_in_op(st->d, GET_SIGNAL_LOCK, 0,0,&st->lock,1);
+ gp8psk_usb_in_op(st->d, GET_SIGNAL_STRENGTH, 0,0,buf,6);
+ st->snr = (buf[1]) << 8 | buf[0];
+ st->next_status_check = jiffies +
(st->status_check_interval*HZ)/1000;
+ }
+ return 0;
+}
+
static int gp8psk_fe_read_status(struct dvb_frontend* fe, fe_status_t *status)
{
struct gp8psk_fe_state *st = fe->demodulator_priv;
- u8 lock;
-
- if (gp8psk_usb_in_op(st->d, GET_SIGNAL_LOCK, 0, 0, &lock,1))
- return -EINVAL;
-
- if (lock)
+ gp8psk_fe_update_status(st);
+
+ if (st->lock)
*status = FE_HAS_LOCK | FE_HAS_SYNC | FE_HAS_VITERBI |
FE_HAS_SIGNAL | FE_HAS_CARRIER;
else
*status = 0;
+ if (*status & FE_HAS_LOCK)
+ st->status_check_interval = 1000;
+ else
+ st->status_check_interval = 100;
return 0;
}
@@ -60,33 +73,29 @@ static int gp8psk_fe_read_snr(struct dvb
static int gp8psk_fe_read_snr(struct dvb_frontend* fe, u16 *snr)
{
struct gp8psk_fe_state *st = fe->demodulator_priv;
- u8 buf[2];
-
- if (time_after(jiffies,st->next_snr_check)) {
- gp8psk_usb_in_op(st->d,GET_SIGNAL_STRENGTH,0,0,buf,2);
- *snr = (int)(buf[1]) << 8 | buf[0];
- /* snr is reported in dBu*256 */
- /* snr / 38.4 ~= 100% strength */
- /* snr * 17 returns 100% strength as 65535 */
- if (*snr <= 3855)
- *snr = (*snr<<4) + *snr; // snr * 17
- else
- *snr = 65535;
- st->next_snr_check = jiffies + (10*HZ)/1000;
- } else {
- *snr = st->snr;
- }
+ gp8psk_fe_update_status(st);
+ /* snr is reported in dBu*256 */
+ *snr = st->snr;
return 0;
}
static int gp8psk_fe_read_signal_strength(struct dvb_frontend* fe, u16
*strength)
{
- return gp8psk_fe_read_snr(fe, strength);
+ struct gp8psk_fe_state *st = fe->demodulator_priv;
+ gp8psk_fe_update_status(st);
+ /* snr is reported in dBu*256 */
+ /* snr / 38.4 ~= 100% strength */
+ /* snr * 17 returns 100% strength as 65535 */
+ if
[linux-dvb] nova-t 500 usb disconnect
After running with the new firmware and current hg drivers for about 18 hours, I've got a USB disconnect. Below are excerpts from my log; Aug 1 18:14:13 htpc2 kernel: MT2060: Spurs after : f_lo1: 1811000 f_lo2: 1196700 (kHz) Aug 1 18:14:13 htpc2 kernel: MT2060: IF1: 1229MHz Aug 1 18:14:13 htpc2 kernel: MT2060: PLL freq=578166kHz f_lo1=1811000kHz f_lo2=1196700kHz Aug 1 18:14:13 htpc2 kernel: MT2060: PLL div1=113 num1=12 div2=74 num2=6502 Aug 1 18:14:13 htpc2 kernel: MT2060: PLL [1..5]: 43 71 6 96 95 Aug 1 18:14:13 htpc2 kernel: MT2060: IF1: 1204MHz Aug 1 18:14:13 htpc2 kernel: MT2060: PLL freq=482000kHz f_lo1=1686000kHz f_lo2=1167850kHz Aug 1 18:14:13 htpc2 kernel: MT2060: PLL div1=105 num1=24 div2=72 num2=8115 Aug 1 18:14:13 htpc2 kernel: MT2060: PLL [1..5]: 56 69 3 fb 91 Aug 1 18:14:14 htpc2 kernel: MT2060: IF1: 1229MHz Aug 1 18:14:14 htpc2 kernel: MT2060: PLL freq=506000kHz f_lo1=1735000kHz f_lo2=1192850kHz Aug 1 18:14:14 htpc2 kernel: MT2060: PLL div1=108 num1=28 div2=74 num2=4531 Aug 1 18:14:14 htpc2 kernel: MT2060: PLL [1..5]: 57 6c 3 1b 95 Aug 1 18:14:14 htpc2 kernel: modifying (0) streaming state for 0 Aug 1 18:14:14 htpc2 kernel: data for streaming: 0 10 Aug 1 18:14:15 htpc2 kernel: modifying (1) streaming state for 1 Aug 1 18:14:15 htpc2 kernel: data for streaming: 10 12 Aug 1 18:14:15 htpc2 kernel: modifying (0) streaming state for 1 Aug 1 18:14:15 htpc2 kernel: data for streaming: 0 10 Aug 1 18:14:15 htpc2 kernel: modifying (1) streaming state for 1 Aug 1 18:14:15 htpc2 kernel: data for streaming: 10 12 Aug 1 18:14:15 htpc2 kernel: modifying (0) streaming state for 1 Aug 1 18:14:15 htpc2 kernel: data for streaming: 0 10 Aug 1 18:14:15 htpc2 kernel: modifying (1) streaming state for 1 Aug 1 18:14:15 htpc2 kernel: data for streaming: 10 12 Aug 1 18:14:15 htpc2 kernel: usb 6-1: USB disconnect, address 6 Aug 1 18:14:15 htpc2 kernel: mt2060 I2C write failed Aug 1 18:14:15 htpc2 kernel: dvb-usb: could not submit URB no. 0 - get them all back Aug 1 18:14:15 htpc2 kernel: modifying (1) streaming state for 0 Aug 1 18:14:15 htpc2 kernel: data for streaming: 10 13 Aug 1 18:14:15 htpc2 kernel: dvb-usb: error while enabling fifo. Aug 1 18:14:15 htpc2 vdr: [23167] ERROR: can't set filter (pid=18, tid=4E, mask=FE): No such device Aug 1 18:14:15 htpc2 kernel: ep 0 read error (status = -19) Aug 1 18:14:15 htpc2 kernel: I2C read failed on address b Aug 1 18:14:15 htpc2 kernel: ep 0 read error (status = -19) Aug 1 18:14:15 htpc2 kernel: I2C read failed on address b Aug 1 18:14:15 htpc2 kernel: ep 0 read error (status = -19) Aug 1 18:14:15 htpc2 kernel: I2C read failed on address b Aug 1 18:14:16 htpc2 kernel: ep 0 read error (status = -19) Aug 1 18:14:16 htpc2 kernel: I2C read failed on address b Aug 1 18:14:16 htpc2 vdr: [23168] frontend 3 lost lock on channel 1, tp 506 Aug 1 18:14:16 htpc2 kernel: ep 0 read error (status = -19) Aug 1 18:14:16 htpc2 kernel: I2C read failed on address b Aug 1 18:14:16 htpc2 vdr: [23168] frontend 3 regained lock on channel 1, tp 506 Aug 1 18:14:17 htpc2 kernel: ep 0 read error (status = -19) when loading the firrmware; Aug 1 00:01:16 htpc2 kernel: dib0700: loaded with support for 3 different device-types Aug 1 00:01:16 htpc2 kernel: FW GET_VERSION length: -32 Aug 1 00:01:16 htpc2 kernel: cold: 1 Aug 1 00:01:16 htpc2 kernel: dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware Aug 1 00:01:16 htpc2 kernel: b2c2-flexcop: found the stv0299 at i2c address: 0x68 Aug 1 00:01:16 htpc2 kernel: DVB: registering frontend 0 (ST STV0299 DVB-S)... Aug 1 00:01:16 htpc2 kernel: b2c2-flexcop: initialization of 'Sky2PC/ SkyStar 2 DVB-S' at the 'PCI' bus controlled by a 'FlexCopIIb' complete Aug 1 00:01:16 htpc2 kernel: ACPI: PCI Interrupt :00:08.0[A] -> GSI 19 (level, low) -> IRQ 18 Aug 1 00:01:16 htpc2 kernel: CORE cx88[0]: subsystem: 0070:9002, board: Hauppauge Nova-T DVB-T [card=18,autodetected] Aug 1 00:01:16 htpc2 kernel: TV tuner 4 at 0x1fe, Radio tuner -1 at 0x1fe Aug 1 00:01:16 htpc2 kernel: dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw' Aug 1 00:01:16 htpc2 kernel: tveeprom 2-0050: Hauppauge model 90002, rev C176, serial# 47706 Aug 1 00:01:16 htpc2 kernel: tveeprom 2-0050: MAC address is 00-0D- FE-00-BA-5A Aug 1 00:01:16 htpc2 kernel: tveeprom 2-0050: tuner model is Thompson DTT7592 (idx 76, type 4) Aug 1 00:01:16 htpc2 kernel: tveeprom 2-0050: TV standards ATSC/DVB Digital (eeprom 0x80) Aug 1 00:01:16 htpc2 kernel: tveeprom 2-0050: audio processor is None (idx 0) Aug 1 00:01:16 htpc2 kernel: tveeprom 2-0050: decoder processor is CX882 (idx 25) Aug 1 00:01:16 htpc2 kernel: tveeprom 2-0050: has no radio, has IR receiver, has no IR transmitter Aug 1 00:01:16 htpc2 kernel: cx88[0]: hauppauge eeprom: model=90002 Aug 1 00:01:16 htpc2 kernel: input: cx88 IR (Hauppauge Nova-T DVB-T a
Re: [linux-dvb] nova-t 500 usb disconnect
Torgeir, I think that you are not running the latest code with the latest firmware. > Aug 1 00:01:16 htpc2 kernel: dib0700: loaded with support for 3 different > device-types It should say "5 different devices", not 3. > Aug 1 00:01:16 htpc2 kernel: dvb-usb: downloading firmware from file > 'dvb-usb-dib0700-01.fw' You should have a "*03-pre1.fw" file. Check my kernel output here: http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Informations/Problems about Asus P7131 Hybrid
Hi Paolo, Am Sonntag, den 05.08.2007, 09:56 +0200 schrieb Paolo Dell'Aquila: > Hallo, I'm writing here becuase I need some informations about the > Asus P7131 Hybrid (1043:4876, board: ASUSTeK P7131 Hybrid > [card=112,autodetected]). > > 1. > Which is the newest firmware for this board? I downloaded the > "revision 29" from lifeview, is this the right one? latest available for download, as far as I know. > 2. > Is it possible to have the DVB-T on the TV input? > In windows I plug the antenna (i have only one cable) to the TV-input > and then I can decide between analog or digital TV. > With Linux I have to plug the digital antenna on the FM input. That > means plugging and unplugging each time I want to switch between analog > or digital. (well, I will build an Y-cable!) That's interesting. The Asus P7131 Dual (card=78) was changed like it is now, because there was a report the Philips ms driver works like this, no functional reason, but we also assumed more people will have cable-TV and DVB-T from different sources as on one single antenna cable. Also the inputs of that card were marked CATV-IN and the upper connector RF/FM-IN. On your P7131 Hybrid it might have also a functional reason with the LNA enabled now, to stay on the _non_ FM antenna input. At least I think this is a outstanding test on your card. For analog TV on it we know that the LNA is correctly configured on the antenna input closer to the motherboard. > 3. > Digital reception is not very good. If I use my Pinnacle Hybryd Pro > Stick I can watch more channels and reception is more stable. There is > something I can do? I read about a "lowNoiseAmplifier" in kernel 2.6.22. > I have kernel 2.6.20. Do I have to upgrade? > (Sorry, but I cannot re-test the board under windows so I don't know if > it's a "driver" problem or a "feature" of the board, lol) No need to upgrade, since you have already updated to recent v4l-dvb code. You might try the attached patch, which sets the other atenna input during digital usage and check if DVB-T reception is /unchanged/better/worse. Cheers, Hermann > Information about my system: > Hardware: Pentium IV 3.2GHz > O.S.: Linux Ubuntu Feisty Fawn 7.04 > Kernel: 2.6.20-16-generic > V4L: updated on 4 Aug 2007 ( hg clone http://linuxtv.org/hg/v4l-dvb) > > > Thank you for your suggestions. > > Paolo > > dmesg (excerpt) > [...] > [ 16.558570] saa7133[0]: found at :01:09.0, rev: 209, irq: 17, > latency: 64, mmio: 0xcdcff800 > [ 16.558579] saa7133[0]: subsystem: 1043:4876, board: ASUSTeK P7131 > Hybrid [card=112,autodetected] > [ 16.558590] saa7133[0]: board init: gpio is 0 > [ 16.558691] input: saa7134 IR (ASUSTeK P7131 Hybri as /class/input/input4 > [ 16.644515] NET: Registered protocol family 10 > [ 16.644629] lo: Disabled Privacy Extensions > [ 16.644690] ADDRCONF(NETDEV_UP): eth0: link is not ready > [ 16.644693] ADDRCONF(NETDEV_UP): eth1: link is not ready > [ 16.692936] saa7133[0]: i2c eeprom 00: 43 10 76 48 54 20 1c 00 43 43 > a9 1c 55 d2 b2 92 > [ 16.692957] saa7133[0]: i2c eeprom 10: ff ff ff 0f ff 20 ff ff ff ff > ff ff ff ff ff ff > [ 16.692976] saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff > 00 d5 ff ff ff ff > [ 16.692993] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff > [ 16.693011] saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 55 50 > ff ff ff ff ff ff > [ 16.693029] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff > [ 16.693047] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff > [ 16.693066] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff > [ 16.728324] nvidia: module license 'NVIDIA' taints kernel. > [ 17.075942] tuner 0-004b: chip found @ 0x96 (saa7133[0]) > [ 17.123871] tuner 0-004b: setting tuner address to 61 > [ 17.163865] tuner 0-004b: type set to tda8290+75a > [ 17.552228] NET: Registered protocol family 17 > [ 18.047866] sky2 eth0: Link is up at 100 Mbps, full duplex, flow > control both > [ 18.315271] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > [ 18.544574] tuner 0-004b: setting tuner address to 61 > [ 18.584483] tuner 0-004b: type set to tda8290+75a > [ 19.925491] saa7133[0]: registered device video0 [v4l2] > [ 19.925692] saa7133[0]: registered device vbi0 > [ 19.925877] saa7133[0]: registered device radio0 > [ 19.989199] ACPI: PCI Interrupt :05:00.0[A] -> GSI 16 (level, > low) -> IRQ 16 > [ 19.989215] PCI: Setting latency timer of device :05:00.0 to 64 > [ 19.989340] NVRM: loading NVIDIA UNIX x86 Kernel Module 1.0-9755 Mon > Feb 26 23:21:15 PST 2007 > [ 19.989356] ACPI: PCI Interrupt :00:1b.0[A] -> GSI 16 (level, > low) -> IRQ 16 > [ 19.989378] PCI: Setting latency timer of device :00:1b.0 to 64 > [ 20.039518] saa7134 ALSA driver for DMA sound loaded > [ 20.039554] saa7133[0]/alsa: saa7133[0] at 0xcdcff800 irq 17 > registered as
Re: [linux-dvb] [RFC PATCH] Choose dvb adapter number with a driver specific module option
On Sunday 05 August 2007 06:01:46 Oliver Endriss wrote: > Janne Grunau wrote: > > Hi, > > > > Dynamic loading of modules by udev on startup (aka coldplugging) > > doesn't result in deterministic dvb adapter numbers. > > > > Besides following changes in dvb-core and dvb-usb core the patch > > adds to all drivers > > ... > > While I don't care much whether there is an option for this in the > driver, I'd like to point out that this is the wrong approach (imho). > > Citing Greg Kroah-Hartman (udev-113/docs/udev_vs_devfs): > |... > |2) udev does not care about the major/minor number schemes. If > | the kernel tomorrow switches to randomly assign major and minor > | numbers to different devices, it would work just fine (this is > | exactly what I am proposing to do in 2.7...) > |3) This is the main reason udev is around. It provides the > | ability to name devices in a persistent manner. More on that > | below. ... > > According to this, adding such an option is a step into the wrong > direction. The right way is to fix the udev scripts... I'm not sure that this is actually consent on lkml and not just Greg Kroah-Hartman's opinion. I find the module options much more conveniant than writing udev rules myself. The automatic persistent network interface generator as used by Gentoo atm has issues (it's not possible to just change a broken nic without changing udev rules). Janne ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] WinTV Nova-T PCI 500 new issues
Hi, With the recent flurry of activity relating to firmware and support for this card, I decided to upgrade the modules from the Mercurial repository and deploy the new firmware. For the first couple of days, things were looking good and I noticed a marked improvement against 2.6.21. I tried to then compile a new 2.6.22 kernel and it was at this point it all went horribly wrong. The 2.6.22 kernel with the new drivers would not lock to most channels, so I reverted back to 2.6.21. However, upon doing this - the card now appears to have suffered an almighty problem.. see tzap results below :- basil:~# tzap -c /usr/share/doc/dvb-utils/examples/channels.conf-dvbt-crystal-palace "BBC ONE" using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 50583 Hz video pid 0x0258, audio pid 0x0259 status 00 | signal | snr | ber 001f | unc | status 00 | signal | snr | ber 001f | unc | status 00 | signal | snr | ber 001f | unc | status 00 | signal | snr | ber 001f | unc | status 00 | signal | snr | ber 001f | unc | status 00 | signal | snr | ber 001f | unc | status 00 | signal | snr | ber 001f | unc | status 00 | signal | snr | ber 001f | unc | status 00 | signal | snr | ber 001f | unc | etc etc. basil:~# scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-CrystalPalace scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-CrystalPalace using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 50583 0 3 9 1 0 0 0 >>> tune to: 50583:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: 50583:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: >>> tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done. The aerial configuration has not changed, I have line of sight to the transmitter in question and dmesg looks reasonably healthy: dib0700: loaded with support for 5 different device-types usb 3-3: reset full speed USB device using ohci_hcd and address 2 dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) DVB: registering frontend 0 (DiBcom 3000MC/P)... DVB: Unable to find symbol mt2060_attach() dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) DVB: registering frontend 1 (DiBcom 3000MC/P)... DVB: Unable to find symbol mt2060_attach() input: IR-receiver inside an USB DVB receiver as /class/input/input2 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected. I have also (for the sake of argument) compiled new modules from the Mercurial repository today and make install'd them but it has made no difference. I know that the firmware it is loading is correct (-03-pre1.fw), but I haven't been near the system to do a full cold reboot recently. I appreciate this is a weird issue, but I would appreciate anyone's pointers as to how to gain more extensive diagnostics to figure out what is going on with the card, and how I might be able to go about fixing it! Thanks Chris ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Doubt about the file: dvb-usb-dvb.c
>在2007-08-04，"Mauro Carvalho Chehab" <[EMAIL PROTECTED]> 写道： >It is very unlikely to have a bug on make_myconfig.pl for such a simple >task. Probably, you didn't selected the newer module with "make >menuconfig". >One alternative to avoid needing to manually select, is to indicate the >minimum kernel version that the module requires. This is done >via /v4/versions.txt file. Of course I selected. It still doesn't work. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] ASUS My Cinema-U3000 Mini
Hi All. I have managed to compile the latest dib0700_devices.c (v4l-dvb-5bb1af77fdc5) after modifying it to include the ASUS My Cinema-U3000 Mini. Like other posts in this mailing list have found, it loads OK, but dmesg does not show a tuner being instantiated for the device. Lsmod lists the mt2060 tuner module with 0 against the ‘used by’ column. My assumption is that this device is supposed to use the MT2266 module for tuning. Does anyone have this device tuning correctly? If so can you guide me down the path of enlightenment? Cheers Jim Bartlett No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.11.6/938 - Release Date: 5/08/2007 4:16 PM ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Doubt about the file: dvb-usb-dvb.c
lwtbenben wrote: >> ??2007-08-04??"Mauro Carvalho Chehab" <[EMAIL PROTECTED]> ?? >> It is very unlikely to have a bug on make_myconfig.pl for such a simple >> task. Probably, you didn't selected the newer module with "make >> menuconfig". >> One alternative to avoid needing to manually select, is to indicate the >> minimum kernel version that the module requires. This is done >> via /v4/versions.txt file. > Of course I selected. > It still doesn't work. This is silly. If you want help, then show us your code. Otherwise, you'll have to figure it out yourself. -Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] nova-t 500 usb disconnect
Hi, Nicolas Will wrote: > Torgeir, > > I think that you are not running the latest code with the latest > firmware. > > >> Aug 1 00:01:16 htpc2 kernel: dib0700: loaded with support for 3 different >> device-types > > > It should say "5 different devices", not 3. > > > >> Aug 1 00:01:16 htpc2 kernel: dvb-usb: downloading firmware from file >> 'dvb-usb-dib0700-01.fw' > > > You should have a "*03-pre1.fw" file. > I guess he forgot to halt the box for a few seconds to force the card into "cold state". Same thing hit me before I found it written somewhere on the wiki. Thus: power it off, wait for a few seconds and power it on again. Carsten ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] WinTV Nova-T PCI 500 new issues
On Mon, 2007-08-06 at 01:32 +0100, Chris Murton wrote: > drivers would not lock to most channels Do you have the LNA turned on? http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#On-board_amplifier Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] frequency out of range - Problems
Hello, has anyone seen errors like this before?: I am getting these messages using the latest available tip-version (v4l-dvb-5bb1af77fdc5). -- Aug 6 07:07:17 gwmuc kernel: DVB: frontend 0 frequency 151 out of range (95..140) Aug 6 07:08:05 gwmuc kernel: DVB: frontend 0 frequency 1958000 out of range (95..140) -- Well, this means some channels are just dark. This error did not occur for the last version of the driver I was running for some time (dvb-pll-0549f1757f66). Background: My box is a Debian V3.1 running VDR V1.4.7 on this hardware: - FF Technotrend - Card, Frontend: Philips TDA8083 DVB-S - Hauppauge Win-TV Nova-T-USB-2 (the old Box, using DIB3000MC driver) I am suffering from the USB-Disconnect - Problem, so I wanted to test Jose Albertos patch he posted some days ago which made me install a new kernel, new dvb-drivers ect. Working version: - Kernel V2.6.22.1 / dvb-pll-0549f1757f66 Tuning-Problems: - Kernel V2.6.22.1 / v4l-dvb-5bb1af77fdc5 Here is an example from my vdr channels.conf: "hr fernsehen" and "WDR Köln" are working, NDR and SR dont. - hr-fernsehen;ARD:11837:hC34:S19.2E:27500:301:302=deu:304:0:28108:1:1101:0 NDR FS MV;ARD:12110:hC34:S19.2E:27500:2401:2402=deu:2404:0:28224:1:1073:0 SR Fernsehen;ARD:12266:hC34:S19.2E:27500:1301:1302=deu:1304:0:28486:1:1093:0 WDR Köln;ARD:11837:hC34:S19.2E:27500:601:602=deu:604:0:28111:1:1101:0 - Switching to "NRD FS MV": DVB: frontend 0 frequency 151 out of range (95..140) Switching to "SR Fernsehen": DVB: frontend 0 frequency 1666000 out of range (95..140) Does anyone else have the same problems? I could not find anything related to this in the list... I am of course willing to do any tests if you need some more info, so if I should try a specific version of the drivers, just ask for it :) Thanks, Lars ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] frequency out of range - Problems
Lars Buerding wrote: > Hello, > > > has anyone seen errors like this before?: > > I am getting these messages using the latest available tip-version > (v4l-dvb-5bb1af77fdc5). > > -- > Aug 6 07:07:17 gwmuc kernel: DVB: frontend 0 frequency 151 out of > range (95..140) > Aug 6 07:08:05 gwmuc kernel: DVB: frontend 0 frequency 1958000 out of > range (95..140) > -- > > > Well, this means some channels are just dark. > > This error did not occur for the last version of the driver I was > running for some time (dvb-pll-0549f1757f66). > > > Background: > My box is a Debian V3.1 running VDR V1.4.7 on this hardware: > - FF Technotrend - Card, Frontend: Philips TDA8083 DVB-S > - Hauppauge Win-TV Nova-T-USB-2 (the old Box, using DIB3000MC driver) > > > I am suffering from the USB-Disconnect - Problem, so I wanted to test > Jose Albertos patch he posted some days ago which made me install a > new kernel, new dvb-drivers ect. > > > Working version: > - Kernel V2.6.22.1 / dvb-pll-0549f1757f66 ^^^ This is an invalid revision. Where did you get that tree? > > Tuning-Problems: > - Kernel V2.6.22.1 / v4l-dvb-5bb1af77fdc5 > > > > Here is an example from my vdr channels.conf: "hr fernsehen" and > "WDR Köln" are working, NDR and SR dont. > > - > hr-fernsehen;ARD:11837:hC34:S19.2E:27500:301:302=deu:304:0:28108:1:1101:0 > NDR FS MV;ARD:12110:hC34:S19.2E:27500:2401:2402=deu:2404:0:28224:1:1073:0 > SR Fernsehen;ARD:12266:hC34:S19.2E:27500:1301:1302=deu:1304:0:28486:1:1093:0 > WDR Köln;ARD:11837:hC34:S19.2E:27500:601:602=deu:604:0:28111:1:1101:0 > - > > Switching to "NRD FS MV": > DVB: frontend 0 frequency 151 out of range (95..140) > > Switching to "SR Fernsehen": > DVB: frontend 0 frequency 1666000 out of range (95..140) > > > > Does anyone else have the same problems? I could not find anything > related to this in the list... > > I am of course willing to do any tests if you need some more info, > so if I should try a specific version of the drivers, just ask for it :) ...quoting tda8083.c: 446 .frequency_min = 95, /* FIXME: guessed! */ 447 .frequency_max = 140,/* FIXME: guessed! */ ... looks like this min / max was guessed incorrectly. This issue has only been made visible recently due to this recent changeset from Oliver Endriss: dvb_frontend: Range check of frequency and symbol rate http://linuxtv.org/hg/v4l-dvb/rev/8186a34dd0a6 Oliver's patch is correct, but it exposed this bug inside tda8083.c for a TEMPORARY workaround, you can backout Oliver's patch: hg backout 8186a34dd0a6 ...or instead, you can just increase .frequency_max inside tda8083.c ... but that doesn't fix it for everybody else. Somebody needs to get a spec for the tda8083 and correct the frequency range. Regards, Mike Krufky ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Old remote/IR receiver (PVR 350) fail to work with Nova T500
Hi, at least for its true, that my old IR receiver and the Hauppauge remote from the PVR350 do NOT work with the T500. At least not yet ;) I was testing the latest changes on Saturday and was not seeing anything with irw and/or event-something. One of the final resorts was using the remote and the IR receiver coming with the T500. Although they look the same, it seems that the generated codes are different [1]. After I got it working, I tried all four possibilities with old/new receiver and remotes but only the T500 remote + T500 receiver did work for me. If this is a generic "feature" maybe someone can put this on the wiki (or I can do it myself if people tell me to do so) as a warning and to save time a hassle. Cheers & thanks a lot for the effort!!! Carsten [1] A few of the keycodes are also not working, but I'll have to dig into that a bit later. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
