Re: [linux-dvb] Nova-T 500 issues - losing one tuner
I have a hunch about this problem... I had this problem (I tink 3 times last weekend) after initially updating my hg tree and recompiling the modules. I then turned on full debugging for the dib0700 module in order to try to see what happens when it goes wrong, but with full debugging on I haven't been able to reproduce the problem. I ran with full debugging on from monday to saturday and *really* tried to make it go away. I tried starting all tuners at once (ie scheduling three programs with the same start time), I tried running long recordings, I tried running plenty of retuning, and I tried doing it my normal way of a few recordings a day. Nothing made the tuner die. So yesterday, I finally gave up in trying to cause the problem. I turned debugging back off, and this morning one of the tuners is dead again (MythTV stopping at L__ instead of proceeding to LMS.) The *ONLY* change I have made is changing the debugging setting. This, in combination with the fact that some people see it and some don't, leads me to believe that this is timer-induced. Something can't keep up. Adding debugging makes the operations slightly slower (the module needs to do additional IO to speak to syslogd), and this delay seems to be enough to keep it operational. I don't think this has anything to do with the remote since I have the RC feature disabled (I'm using an M$ MCE remote instead). I set it up with full debugging (options dvb_usb_0700 debug=15). This will cause a whole bunch of logging in the system logs, but appears to keep the tuner alive. I have now changed the debug setting to 1 (only 'info' type messages) to see if that also keeps the tuner alive. My system has a 3.3 Ghz Celeron processor. Shaun, Ben, Nicolas -- what kind of systems are you running? If my hunch is correct, I'd expect Shaun and Ben to have faster processors than Nicolas since they are seeing this issue and Nicolas isn't. // J On Sat, 2008-02-02 at 10:20 +, Shaun wrote: On Friday 01 February 2008 21:43:51 Nicolas Will wrote: On Fri, 2008-02-01 at 21:07 +, Ben Firshman wrote: Feb 1 20:52:04 mythtv kernel: [ 11.072000] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware Feb 1 20:52:04 mythtv kernel: [ 11.132000] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' ... Feb 1 20:52:04 mythtv kernel: [ 11.844000] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. Feb 1 20:52:04 mythtv kernel: [ 11.844000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 11.844000] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) Feb 1 20:52:04 mythtv kernel: [ 11.956000] DVB: registering frontend 1 (DiBcom 3000MC/P)... ... Feb 1 20:52:04 mythtv kernel: [ 12.50] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 12.50] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) Feb 1 20:52:04 mythtv kernel: [ 12.508000] DVB: registering frontend 2 (DiBcom 3000MC/P)... Feb 1 20:52:04 mythtv kernel: [ 13.068000] input: IR-receiver inside an USB DVB receiver as /class/input/input2 Feb 1 20:52:04 mythtv kernel: [ 13.068000] dvb-usb: schedule remote query interval to 150 msecs. Feb 1 20:52:04 mythtv kernel: [ 13.068000] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected. Got the tree from the day of your message, and I'm still having problems. I'm not the only one either: http://www.linuxtv.org/pipermail/linux-dvb/2008-January/022629.html Thanks Ben Nicolas Will wrote: On Sun, 2008-01-27 at 14:30 +, Ben Firshman wrote: I am using the (almost) latest SVN version of mythtv. I am using the v4l-dvb sources from a couple of days back. I have followed and used the patches that were on (are they in the repos now?): http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 After a short while, one of the tuners dies. I get a (L__) Partial Lock message from mythtv. If it's any help, I also get messages like: DVB: frontend 0 frequency limits undefined - fix the driver In syslog, but that's even when it's working fine. Weird issue that I never encountered since I started using the card in August... Get a brand new tree, there have been a lot of changes very recently, merge of old patches and new fixes too. Make sure that you have the right firmware too. Then do a cold reboot, going through a power down, then check in the messages that the card was found in a cold state before a firmware upload. http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#Firmware Nico Ben, I'm at loss for an explanation. I'm just not experiencing your problem.
Re: [linux-dvb] What is the MAC of a DVB card?
There's a nicie guide about how to get DVB-H in http://amuse.ftw.at/downloads/dvbh-relay. It explains how to do that (and relay the video) quite well. And about receiving the MPEG-TS from the network... I don't know I suppose the way would be to receive it in VLC and then stream it. Josep On Feb 1, 2008 12:28 AM, Arris [ML] [EMAIL PROTECTED] wrote: Hi, I've always wanted to ask, but always forgotten... I've got a Hauppauge WinTV NOVA T USB2 and it has a MAC address. What is it useful for? Was it an attempt to access the card over the network? Just curiosity. u can use it for dvb-h downstream channels. http://en.wikipedia.org/wiki/DVB-H senseless but funny thing here in vienna zsolt ___ 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] Nova-T 500 issues - losing one tuner
Hi People, Jonas I like your never give up attitude. I am running on a 3Ghz P4. At the moment I am running with a very slightly modified driver. I have my remote plugged in and I sometimes get hundreds of messages like the one below: Jan 23 22:01:00 media-desktop kernel: [ 1062.522880] dib0700: Unknown remote controller key : 0 20 I have included a line in linux/drivers/media/dvb/dvb-usb/dib0700_devices.c that eats the unknown controller key and prevents the message repeating, as was suggested by Jonas. From my mythwatcher logs: [27-1-08 17:02:21] --- Started --- [27-1-08 19:51:02] --- Started --- [27-1-08 23:50:20] --- Started --- [29-1-08 05:41:07] ERROR: Disconnect Detected. [29-1-08 05:41:07] ACTION: Attempting mythtv-backend restart. [29-1-08 19:36:37] ERROR: Disconnect Detected. [29-1-08 19:36:37] ACTION: Attempting mythtv-backend restart. [30-1-08 04:55:17] ERROR: Disconnect Detected. [30-1-08 04:55:17] ACTION: Attempting mythtv-backend restart. [30-1-08 05:00:16] ERROR: Disconnect Detected. [30-1-08 05:00:16] ACTION: Attempting mythtv-backend restart. [1-2-08 06:24:17] ERROR: Disconnect Detected. [1-2-08 06:24:17] ACTION: Attempting mythtv-backend restart. [1-2-08 20:18:48] ERROR: Disconnect Detected. [1-2-08 20:18:48] ACTION: Attempting mythtv-backend restart. [2-2-08 12:24:58] --- Started --- I have been using the modified driver since [2-2-08 12:24:58]. I have been up for 24 hours with no disconnect. I will let you know how it goes. If I do get a disconnect, I will turn on debugging and see how that goes. Cheers, Shaun On Sunday 03 February 2008 09:39:01 Jonas Anden wrote: I have a hunch about this problem... I had this problem (I tink 3 times last weekend) after initially updating my hg tree and recompiling the modules. I then turned on full debugging for the dib0700 module in order to try to see what happens when it goes wrong, but with full debugging on I haven't been able to reproduce the problem. I ran with full debugging on from monday to saturday and *really* tried to make it go away. I tried starting all tuners at once (ie scheduling three programs with the same start time), I tried running long recordings, I tried running plenty of retuning, and I tried doing it my normal way of a few recordings a day. Nothing made the tuner die. So yesterday, I finally gave up in trying to cause the problem. I turned debugging back off, and this morning one of the tuners is dead again (MythTV stopping at L__ instead of proceeding to LMS.) The *ONLY* change I have made is changing the debugging setting. This, in combination with the fact that some people see it and some don't, leads me to believe that this is timer-induced. Something can't keep up. Adding debugging makes the operations slightly slower (the module needs to do additional IO to speak to syslogd), and this delay seems to be enough to keep it operational. I don't think this has anything to do with the remote since I have the RC feature disabled (I'm using an M$ MCE remote instead). I set it up with full debugging (options dvb_usb_0700 debug=15). This will cause a whole bunch of logging in the system logs, but appears to keep the tuner alive. I have now changed the debug setting to 1 (only 'info' type messages) to see if that also keeps the tuner alive. My system has a 3.3 Ghz Celeron processor. Shaun, Ben, Nicolas -- what kind of systems are you running? If my hunch is correct, I'd expect Shaun and Ben to have faster processors than Nicolas since they are seeing this issue and Nicolas isn't. // J On Sat, 2008-02-02 at 10:20 +, Shaun wrote: On Friday 01 February 2008 21:43:51 Nicolas Will wrote: On Fri, 2008-02-01 at 21:07 +, Ben Firshman wrote: Feb 1 20:52:04 mythtv kernel: [ 11.072000] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware Feb 1 20:52:04 mythtv kernel: [ 11.132000] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' ... Feb 1 20:52:04 mythtv kernel: [ 11.844000] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. Feb 1 20:52:04 mythtv kernel: [ 11.844000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 11.844000] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) Feb 1 20:52:04 mythtv kernel: [ 11.956000] DVB: registering frontend 1 (DiBcom 3000MC/P)... ... Feb 1 20:52:04 mythtv kernel: [ 12.50] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 12.50] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) Feb 1 20:52:04 mythtv kernel: [ 12.508000] DVB: registering frontend 2 (DiBcom 3000MC/P)... Feb 1 20:52:04 mythtv kernel: [ 13.068000] input: IR-receiver inside an USB DVB receiver as /class/input/input2 Feb 1
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
I'm running a 2.66ghz Pentium D. I don't use the remote. It seems to be pretty sporadic - it's been working for a couple of days now. Ben On 3 Feb 2008, at 09:39, Jonas Anden wrote: I have a hunch about this problem... I had this problem (I tink 3 times last weekend) after initially updating my hg tree and recompiling the modules. I then turned on full debugging for the dib0700 module in order to try to see what happens when it goes wrong, but with full debugging on I haven't been able to reproduce the problem. I ran with full debugging on from monday to saturday and *really* tried to make it go away. I tried starting all tuners at once (ie scheduling three programs with the same start time), I tried running long recordings, I tried running plenty of retuning, and I tried doing it my normal way of a few recordings a day. Nothing made the tuner die. So yesterday, I finally gave up in trying to cause the problem. I turned debugging back off, and this morning one of the tuners is dead again (MythTV stopping at L__ instead of proceeding to LMS.) The *ONLY* change I have made is changing the debugging setting. This, in combination with the fact that some people see it and some don't, leads me to believe that this is timer-induced. Something can't keep up. Adding debugging makes the operations slightly slower (the module needs to do additional IO to speak to syslogd), and this delay seems to be enough to keep it operational. I don't think this has anything to do with the remote since I have the RC feature disabled (I'm using an M$ MCE remote instead). I set it up with full debugging (options dvb_usb_0700 debug=15). This will cause a whole bunch of logging in the system logs, but appears to keep the tuner alive. I have now changed the debug setting to 1 (only 'info' type messages) to see if that also keeps the tuner alive. My system has a 3.3 Ghz Celeron processor. Shaun, Ben, Nicolas -- what kind of systems are you running? If my hunch is correct, I'd expect Shaun and Ben to have faster processors than Nicolas since they are seeing this issue and Nicolas isn't. // J On Sat, 2008-02-02 at 10:20 +, Shaun wrote: On Friday 01 February 2008 21:43:51 Nicolas Will wrote: On Fri, 2008-02-01 at 21:07 +, Ben Firshman wrote: Feb 1 20:52:04 mythtv kernel: [ 11.072000] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware Feb 1 20:52:04 mythtv kernel: [ 11.132000] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' ... Feb 1 20:52:04 mythtv kernel: [ 11.844000] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. Feb 1 20:52:04 mythtv kernel: [ 11.844000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 11.844000] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) Feb 1 20:52:04 mythtv kernel: [ 11.956000] DVB: registering frontend 1 (DiBcom 3000MC/P)... ... Feb 1 20:52:04 mythtv kernel: [ 12.50] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 12.50] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) Feb 1 20:52:04 mythtv kernel: [ 12.508000] DVB: registering frontend 2 (DiBcom 3000MC/P)... Feb 1 20:52:04 mythtv kernel: [ 13.068000] input: IR-receiver inside an USB DVB receiver as /class/input/input2 Feb 1 20:52:04 mythtv kernel: [ 13.068000] dvb-usb: schedule remote query interval to 150 msecs. Feb 1 20:52:04 mythtv kernel: [ 13.068000] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected. Got the tree from the day of your message, and I'm still having problems. I'm not the only one either: http://www.linuxtv.org/pipermail/linux-dvb/2008-January/022629.html Thanks Ben Nicolas Will wrote: On Sun, 2008-01-27 at 14:30 +, Ben Firshman wrote: I am using the (almost) latest SVN version of mythtv. I am using the v4l-dvb sources from a couple of days back. I have followed and used the patches that were on (are they in the repos now?): http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 After a short while, one of the tuners dies. I get a (L__) Partial Lock message from mythtv. If it's any help, I also get messages like: DVB: frontend 0 frequency limits undefined - fix the driver In syslog, but that's even when it's working fine. Weird issue that I never encountered since I started using the card in August... Get a brand new tree, there have been a lot of changes very recently, merge of old patches and new fixes too. Make sure that you have the right firmware too. Then do a cold reboot, going through a power down, then check in the messages that the card was found in a cold state before a firmware upload.
Re: [linux-dvb] TT-1401 budget card support broken since 2.6.24-rc6
Hi Oliver, I've revoked the changes of the patch you've mentioned below on a plain vanilla 2.6.24 kernel - and it works! ;-) If I should do more testing on this issue, please advice ... Thanks Dirk Oliver Endriss schrieb: Dirk Brenken wrote: Hi, I'm running a budget-only (Technotrend S-1401) vdr system (1.5.13) with xinelibouput plugin (latest cvs checkout). It's based on debian sid and it runs fine with kernel 2.6.23.14 ... up to kernel 2.6.24-rc5. After that version, my budget card system stops working ... here some log file stuff: ... The problem also occurs with kernel 2.6.23.14 plus latest v4l-dvb checkout. Any idea how to track down this error? Any help is appreciated! Could you please check whether patch http://linuxtv.org/hg/v4l-dvb/rev/816f256c2973 broke the driver? CU Oliver ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Any chance of help with v4l-dvb-experimental / Avermedia A16D please?
I tried contacting Markus with the following but no response - probably one of you experienced coders on this list will know what's wrong though? As I say below, the 'standard' v4l-dvb builds fine but is no use with this card. Cheers Richard (MQ) Having another try to get my Avermedia A16D card working with latest hg code. I'm also using the very latest OpenSuSE 'factory' platform, with kernel 2.6.24-rc8-git2-5-default. gcc is 4.3.0 I can build the 'standard' v4l-dvb tree OK, though as expected it doesn't see my card. However, when I try to build your v4l-dvb-experimental tree (in a separate directory) I get [EMAIL PROTECTED]:~/Progs/v4l-dvb-experimental/v4l make ... make -C ../../../linux-2.6.24-rc8-git2-5 O=../linux-2.6.24-rc8-git2-5-obj/i386/default modules CC [M] /home/rpm/Progs/v4l-dvb-experimental/v4l/flexcop-pci.o In file included from /home/rpm/Progs/v4l-dvb-experimental/v4l/flexcop-common.h:23, from /home/rpm/Progs/v4l-dvb-experimental/v4l/flexcop-pci.c:10: /home/rpm/Progs/v4l-dvb-experimental/v4l/dvb_frontend.h:42:33: error: media/v4l_dvb_tuner.h: No such file or directory Indeed there's no directory 'media' at the current level, though there's one at ../linux, so I tried ln -s ../linux/include/media media Now make gets a bit further, but dies building bttv-driver Please have you any suggestions? By the way - is it more appropriate to post this e.g. at linux-dvb? Many thanks Richard. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [v4l-dvb-maintainer] [PATCH] [rivers/media/video/tvaudio.c] add parentheses
Hi, On Sun, 3 Feb 2008, Bodo Eggert wrote: Roel Kluin [EMAIL PROTECTED] wrote: '!' has a higher priority than '': bitanding has no effect. +++ b/drivers/media/video/tvaudio.c @@ -1571,14 +1571,14 @@ static int tvaudio_get_ctrl(struct CHIPSTATE *chip, ctrl-value=chip-muted; return 0; case V4L2_CID_AUDIO_VOLUME: - if (!desc-flags CHIP_HAS_VOLUME) + if (!(desc-flags CHIP_HAS_VOLUME)) This is a cosmetic change, because: !1100101 100 == 0011010 100 == 0 /* false */ !(1100101 100) == !100 == 0 /* false */ !111 100 == 000 100 == 100 /* non-false */ !(111 100) == !000 == 1 /* non-false */ OTOH, your change may result in better code by using a negated jump instead of explicitely negating the value. If I'm not totally wrong, ! is negating integers: !123 == 0. At least I hope that, otherwise I have to go through a lot of code ;) Your interpretation of ! is actually achieved by using ~ . Patrick. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Sun, 2008-02-03 at 10:39 +0100, Jonas Anden wrote: My system has a 3.3 Ghz Celeron processor. Shaun, Ben, Nicolas -- what kind of systems are you running? If my hunch is correct, I'd expect Shaun and Ben to have faster processors than Nicolas since they are seeing this issue and Nicolas isn't. I have a fast Core 2 Duo, 2.66 GHz, tons of cache, 64-bit OS. Nico http://www.youplala.net/linux/home-theater-pc ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Sun, 2008-02-03 at 11:37 +, Shaun wrote: Hi People, Jonas I like your never give up attitude. I am running on a 3Ghz P4. At the moment I am running with a very slightly modified driver. I have my remote plugged in and I sometimes get hundreds of messages like the one below: Jan 23 22:01:00 media-desktop kernel: [ 1062.522880] dib0700: Unknown remote controller key : 0 20 I have included a line in linux/drivers/media/dvb/dvb-usb/dib0700_devices.c that eats the unknown controller key and prevents the message repeating, as was suggested by Jonas. There is a patch on the wiki for this, and I'm using it. Related? Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TDA10086 with Pinnacle 400e tuning broken
Hi, Patrick Patrick Boettcher schrieb: Hi, On Wed, 30 Jan 2008, Hartmut Hackmann wrote: If i understand the LNBp21 and isl64xx datasheets correctly, these chips will always use their internal 22kHz oscillator, it can just be turned on and off. I don't see how to turn on 22kHz on LNBP21. How can this be done? Patrick. My understanding is that this needs to be done through the diseqc control: via i2c control of the lnbp21, yo can either turn the tone permanently on or let it be controlled by a pin - through the channel decoder. The tda10086 is not generating the tone? Only the lnbp21 can do it? The bit7 only enables that on the lnb21, because it is configured to only do it, when a specific line is 1? In that case the lnbp21-driver is not prepared for having the tone forced, it seems. So data sheet reading. Are we talking about different chips / datashets? Mine says that if the TEN bit is 0, the 22kHz generator is controlled by the DSQIN pin. A high at this pin turns the OSCILLATOR on. And to my understanding this is the only way to do it: the tda10086 has to generate the ENVELOPE of the 22kHz signal. If it contains the carrier, this will disturb the on chip oscillator. This might still work in the static case, but not if we want to generate diseqc messages with bursts of just 11 periods. Actually I'm asking myself why it is wrong to not set the bit7 of the tda10086? Could be a config option. See above. We might make it a config option, but we should only do it if we really need to and i am not convinced yet. Could it be that you somehow just forgot to choose the upper band in your tuning data / dvb application? I'm only using dvbscan and vdr - never bothering about that - it simply worked ;) Patrick. Are you sure that it is a lnbp21 on your board? What kind of satellite equipment do you have? - a single LNB, so the 22kHz tone is enough. - a Multiswitch? if yes, which commands does it need / understand? - nothing but the tone? - a tone burst to switch between satellites and the tone? - full diseqc (2?) serial messages? I got a board with tda10086 and lnbp21 let and started measuring. voltage switching and static tone work fine with the current configuration. Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] hi
Hi, I just wanna know if in linux 2.6 kernel, DVB driver will support more than 4 cards or not. Can any one help me. Regards Ashim Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] linux-dvb Digest, Vol 37, Issue 5
-- Missatge reenviat -- From: Nicolas Will [EMAIL PROTECTED] To: linux-dvb linux-dvb@linuxtv.org Date: Sun, 03 Feb 2008 21:36:23 + Subject: Re: [linux-dvb] Nova-T 500 issues - losing one tuner On Sun, 2008-02-03 at 10:39 +0100, Jonas Anden wrote: My system has a 3.3 Ghz Celeron processor. Shaun, Ben, Nicolas -- what kind of systems are you running? If my hunch is correct, I'd expect Shaun and Ben to have faster processors than Nicolas since they are seeing this issue and Nicolas isn't. I have a fast Core 2 Duo, 2.66 GHz, tons of cache, 64-bit OS. Nico http://www.youplala.net/linux/home-theater-pc Just my 0.02€ to the statistics: I'm running an AthlonXP 3800+, 1 GB RAM, Gentoo 64 bits. I can't even remember when I had my last disconnect Best regards, Eduard ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
