Re: AF9015 Dual tuner i2c write failures
On Sat, 2011-11-12 at 13:47 +, Tim Draper wrote: > since i'm new to this mailing list, and have only used v4l in > pre-configured linux distro's, how will this fix be distributed to > people - as a patch i presume? > are there any how-to's with prerequisites of whats required to apply a > patch? Quite easy, in fact. Once the patch gets into the v4l trunk: http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: PCTV nanoStick T2 290e support - Thank you!
> -Original Message- > From: linux-media-ow...@vger.kernel.org [mailto:linux-media- > ow...@vger.kernel.org] On Behalf Of Bjørn Mork > Sent: 27 May 2011 12:37 > To: linux-media@vger.kernel.org > Subject: Re: PCTV nanoStick T2 290e support - Thank you! > > Antti Palosaari writes: > > On 05/27/2011 12:25 AM, Nicolas WILL wrote: > >> Just installed mine for MythTV. > >> > >> Works great on the first try! > >> > >> Many, many thanks! > > > > Thank you for the feedback! > > I'm a bit curious about this device. It seems to only be marketed as a > DVB-T2 device in areas where that spec is used. But looking at your > driver, it seems that the device also supports DVB-C. Is that correct? [ 12.921835] DVB: registering adapter 4 frontend 0 (Sony CXD2820R (DVB-T/T2))... [ 12.921904] DVB: registering adapter 4 frontend 1 (Sony CXD2820R (DVB-C))... Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
PCTV nanoStick T2 290e support - Thank you!
Just installed mine for MythTV. Works great on the first try! Many, many thanks! Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: build errors on kinect and rc-main - 2.6.38 (mipi-csis not rc-main)
On Wed, 2011-05-25 at 18:02 -0400, Jarod Wilson wrote: > On May 25, 2011, at 5:41 PM, Jarod Wilson wrote: > > > On May 25, 2011, at 3:01 AM, Nicolas WILL wrote: > > > >> On Wed, 2011-05-25 at 07:43 +0100, Nicolas WILL wrote: > >>> The second one is on rc-main (I probably need that!): > >>> > >>> CC [M] /home/nico/src/media_build/v4l/rc-main.o > >>> /home/nico/src/media_build/v4l/rc-main.c: In function > 'rc_allocate_device': > >>> /home/nico/src/media_build/v4l/rc-main.c:993:29: warning: > assignment from incompatible pointer type > >>> /home/nico/src/media_build/v4l/rc-main.c:994:29: warning: > assignment from incompatible pointer type > >>> CC [M] /home/nico/src/media_build/v4l/ir-raw.o > >>> CC [M] /home/nico/src/media_build/v4l/mipi-csis.o > >>> /home/nico/src/media_build/v4l/mipi-csis.c:29:28: fatal error: > plat/mipi_csis.h: No such file or directory > >>> compilation terminated. > >> > >> Oh, not rc-main, but mipi-csis! > > > > True, but the rc-main warning is actually a valid issue that needs > to > > be fixed as well. I'll get the necessary backport patch into > media_build > > shortly, I hope... > > Patches pushed. :o) Thanks ! Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: build errors on kinect and rc-main - 2.6.38 (mipi-csis not rc-main)
On Wed, 2011-05-25 at 07:43 +0100, Nicolas WILL wrote: > The second one is on rc-main (I probably need that!): > > CC [M] /home/nico/src/media_build/v4l/rc-main.o > /home/nico/src/media_build/v4l/rc-main.c: In function 'rc_allocate_device': > /home/nico/src/media_build/v4l/rc-main.c:993:29: warning: assignment from > incompatible pointer type > /home/nico/src/media_build/v4l/rc-main.c:994:29: warning: assignment from > incompatible pointer type > CC [M] /home/nico/src/media_build/v4l/ir-raw.o > CC [M] /home/nico/src/media_build/v4l/mipi-csis.o > /home/nico/src/media_build/v4l/mipi-csis.c:29:28: fatal error: > plat/mipi_csis.h: No such file or directory > compilation terminated. Oh, not rc-main, but mipi-csis! Sorry... Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
build errors on kinect and rc-main - 2.6.38
Hello, I'm trying to build the media tree using the automatic script and end-up with at least two errors not allowing me to move forward positively. Ubuntu 11.04 x86_64 2.6.38-8-generic First one is on Kinect (don't need it, I can disable the build): CC [M] /home/nico/src/media_build/v4l/kinect.o /home/nico/src/media_build/v4l/kinect.c:38:19: error: 'D_ERR' undeclared here (not in a function) /home/nico/src/media_build/v4l/kinect.c:38:27: error: 'D_PROBE' undeclared here (not in a function) /home/nico/src/media_build/v4l/kinect.c:38:37: error: 'D_CONF' undeclared here (not in a function) /home/nico/src/media_build/v4l/kinect.c:38:46: error: 'D_STREAM' undeclared here (not in a function) /home/nico/src/media_build/v4l/kinect.c:38:57: error: 'D_FRAM' undeclared here (not in a function) /home/nico/src/media_build/v4l/kinect.c:38:66: error: 'D_PACK' undeclared here (not in a function) /home/nico/src/media_build/v4l/kinect.c:39:2: error: 'D_USBI' undeclared here (not in a function) /home/nico/src/media_build/v4l/kinect.c:39:11: error: 'D_USBO' undeclared here (not in a function) /home/nico/src/media_build/v4l/kinect.c:39:20: error: 'D_V4L2' undeclared here (not in a function) make[3]: *** [/home/nico/src/media_build/v4l/kinect.o] Error 1 make[2]: *** [_module_/home/nico/src/media_build/v4l] Error 2 The second one is on rc-main (I probably need that!): CC [M] /home/nico/src/media_build/v4l/rc-main.o /home/nico/src/media_build/v4l/rc-main.c: In function 'rc_allocate_device': /home/nico/src/media_build/v4l/rc-main.c:993:29: warning: assignment from incompatible pointer type /home/nico/src/media_build/v4l/rc-main.c:994:29: warning: assignment from incompatible pointer type CC [M] /home/nico/src/media_build/v4l/ir-raw.o CC [M] /home/nico/src/media_build/v4l/mipi-csis.o /home/nico/src/media_build/v4l/mipi-csis.c:29:28: fatal error: plat/mipi_csis.h: No such file or directory compilation terminated. Thanks for looking into it! Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
PCTV nanoStick T2 in stock - Driver work?
Hello The DVB-T2 USB stick appears to be in stock in the UK. Product page: http://www.pctvsystems.com/Products/ProductsEuropeAsia/Digitalproducts/PCTVnanoStickT2/tabid/248/language/en-GB/Default.aspx Play.com, Dabs and Amzon.co.uk list it as in stock. Is there any work started on a driver at this point? If no work has started, would a loan/donation of a stick help? What can be done to trigger/accelerate the provision of a driver? Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
PCTV nanoStick T2
Hello, Anybody got one of those? http://www.pctvsystems.com/Products/ProductsEuropeAsia/Digitalproducts/PCTVnanoStickT2/tabid/248/language/en-GB/Default.aspx It is now official on PCTV's site. Some online store are listing it, but with zero stock. I would be willing to sponsor driver development, if needed, by buying a unit when possible and then loaning it to a developer. Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: RFC: Phase 1: Proposal to convert V4L1 drivers
On Sun, 2010-03-21 at 09:19 +0100, Hans Verkuil wrote: > > > - cpia_pp > > > > > > Parallel port webcam driver for the Creative Webcam II. I found > one on eBay, > > > so with luck I can get hold of the hardware and get it to HdG. > > > > > > > Although I appreaciate your effort in getting this cam into my > hands, I don't > > know what to with it once I have it, my stance on it can be > summarized as: > > It is parallel port only so lets just drop it. I have one of those in my toys. I can donate it to anyone in Europe. I guess that my willingness to get rid of it is a testimony to how important it is to me... Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Call for Testers - dib0700 IR improvements
Hello, On Wed, 2010-01-06 at 09:36 -0500, Devin Heitmueller wrote: > Just to be clear, this patch does *not* address the warm reboot > problem. I am continuing to work that issue, but there should be no > expectation that this patch allows the device to survive a warm > reboot. > That one would be cool. > It should address concerns people were seeing where the system load > would be between 0.50 and 1.0 just by having the device connected, and > *may* help in cases where you start to see mt2060 errors after several > hours of operation. hmmm... 32 days uptime, no mt2060 error from my NovaT500, outside of a failed read at startup. regarding the load, I'm not sure I am experiencing it, or it is shadowed by MythTV's frontend "idling" at 15% cpu... I'll stop the frontend during the night and look at the load in the morning. I may be able to provide a graph from munin, as I have multiple recordings, some concurrent, of the kids shows in the morning. If I have the load thing, I'll test the patch, otherwise I'll keep the WAF, and KAF, as I would not be a proper guinea pig anyway. Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Nova-TD-500 (84xxx) problems (was Re: dib0700 diversity support)
On Tue, 2009-08-25 at 00:36 +0930, Malcolm Caldwell wrote: > > Have you tried adding: > > > > dvb_usb_dib0700.force_lna_activation=1 > > > > to the modprobe options? > > > > The device I had wouldn't tune without this. > > I should have mentioned that I have tried this and buggy sfn > workaround for the relavent modules. I have read that sometimes the problem is not a low signal, but too strong a signal. Have you tried placing an attenuator in front of the card? Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dib0700 diversity support
Patrick Boettcher wrote: On Tue, 18 Aug 2009, Nicolas Will wrote: This change should improve reception conditions for devices based on the DiB0070-tuner (DiB7070P e.g) . We tried this driver with our reference boards and it works well, but sometimes DiBcom's customers are adding things, DiBcom is not really aware of. That's why there is a risk that it breaks supports for some cards. Well, breakage is easier to notice! I can test on the Nova-T 500. For you _nothing_ should change. The Nova-T is using dib3000mc+mt2060. If it does not work for you any longer, something else is broken. If it works better for you, it's simply magic. Well then, I'll step out of the way and leave the testing to relevant people! So why does dib0070 appear in my lsmod? Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dib0700 diversity support
Patrick Boettcher wrote: Hi Nicolas, On Tue, 18 Aug 2009, Nicolas Will wrote: Patrick Boettcher wrote: Hi Paul, On Fri, 14 Aug 2009, Paul Menzel wrote: I'll post a request for testing soon. I am looking forward to it. Can you please try the drivers from here: http://linuxtv.org/hg/~pb/v4l-dvb/ In the best case they improve the situation for you. In the worst case (not wanted :) ) it will degrade. Hi Patrick, Could you give us a summary of what changes are included in you tree, what we should expect, what we should test for and report on? Yeah, sorry, I'm not very professional: bo! ;o) Let's list first the commits: DiB8000: fix channel search parameter initialization DiB0700: add support for STK807XP and STK807XPVR DiB8000: added support for DiBcom ISDB-T/ISDB-Tsb demodulator DiB8000 DiB0070: Indenting driver with indent -linux DiB0070: Update to latest internal release As you can see, there are a lot of new things, the most important for users of existing devices is the 'DiB0070: Update to latest internal release' . This change should improve reception conditions for devices based on the DiB0070-tuner (DiB7070P e.g) . Fine. Now, how do I measure this objectively so that I can give you meaningful results (before/after)? My system is currntly working fine, using a hg clone from quite a few months ago, so if things are not directly visible... We tried this driver with our reference boards and it works well, but sometimes DiBcom's customers are adding things, DiBcom is not really aware of. That's why there is a risk that it breaks supports for some cards. Well, breakage is easier to notice! I can test on the Nova-T 500. n...@favia:~$ lsmod | grep dib dvb_usb_dib070054536 16 dib7000p 27400 1 dvb_usb_dib0700 dib7000m 24964 1 dvb_usb_dib0700 dvb_usb27148 2 dvb_usb_dtt200u,dvb_usb_dib0700 dib3000mc 22280 3 dvb_usb_dib0700 dibx000_common 12292 3 dib7000p,dib7000m,dib3000mc dib007016772 1 dvb_usb_dib0700 Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dib0700 diversity support
Patrick Boettcher wrote: Hi Paul, On Fri, 14 Aug 2009, Paul Menzel wrote: I'll post a request for testing soon. I am looking forward to it. Can you please try the drivers from here: http://linuxtv.org/hg/~pb/v4l-dvb/ In the best case they improve the situation for you. In the worst case (not wanted :) ) it will degrade. Hi Patrick, Could you give us a summary of what changes are included in you tree, what we should expect, what we should test for and report on? Thanks! Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [linux-dvb] problem: Hauppauge Nova TD500
On Wed, 2009-08-12 at 23:04 +1000, Tim Docker wrote: > On 11/08/2009, at 11:11 PM, Nicolas Will wrote: > > > On Tue, 2009-08-11 at 13:53 +0100, Tim Docker wrote: > >> Hi, > >> > >> I'm trying to diagnose a problem with a mythtv setup based upon a > >> hauppauge nova td 500. I've had the setup for some months - it > seemed > >> to > >> work reasonably reliably initially, but over the last few weeks > I've > >> had > >> consistent problems with the tuner card entering a state where it > is > >> unable to receive a signal. > > > This problem is most probably caused by the tuner being in USB > suspend > > when MythTV wants to use it too quickly. > > > > Either disable usb suspend in your kernel, or tell mythtv to take > wait > > some more before tuning. > > > > I told MythTV to wait some more, and all is fine. > > > > > http://www.youplala.net/linux/home-theater-pc#toc-not-losing-one-of-the-nova-t-500s-tuners > > Thanks - I've make the changes, and it's survived the first 24 > hours, > which is an improvement. Time will tell if the problem has really > gone. It should be. My system has been up for more than 14 days, since the last kernel update that required a reboot. Before that it was up for more than a month. Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [linux-dvb] problem: Hauppauge Nova TD500
On Tue, 2009-08-11 at 13:53 +0100, Tim Docker wrote: > Hi, > > I'm trying to diagnose a problem with a mythtv setup based upon a > hauppauge nova td 500. I've had the setup for some months - it seemed > to > work reasonably reliably initially, but over the last few weeks I've > had > consistent problems with the tuner card entering a state where it is > unable to receive a signal. I was seeing multiple errors via dmesg of > the form: > > [27317.617958] DiB0070 I2C write failed > > Web trawling suggested that this could be resolved with an updated > driver - I did this yesterday, with the latest version from > mercurial, > obtained and built as per the instructions here: > > http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers > > > > I installed this over the top of the 2.6.27-14-generic kernel from > the > mythbuntu distribution, and manually installed the 1.20 firmware. > > In 24 uptime hours I haven't seen any I2C errors, but unfortunately, > it > has still entered some state where I can't received a signal. > Mysteriously, there doesn't appear to be any relevant errors or > messages > in dmesg. From the log snippet below, you can see that no signal is > being returned by tzap, but if I unload and reload the modules, > everything comes back to life. > > I'd really appreciate any tips or pointers on what might be going > wrong > here. This problem is most probably caused by the tuner being in USB suspend when MythTV wants to use it too quickly. Either disable usb suspend in your kernel, or tell mythtv to take wait some more before tuning. I told MythTV to wait some more, and all is fine. http://www.youplala.net/linux/home-theater-pc#toc-not-losing-one-of-the-nova-t-500s-tuners Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Nova-T 500 does not survive reboot
On Fri, 2009-05-22 at 15:30 +0200, Soeren Moch wrote: > >>> Hi, > >>>Any news on this? I'd like to try the URB patch someone mentioned, > >>> but I > >>> can't find the link. > >> > >> http://www.mail-archive.com/linux-media@vger.kernel.org/msg04643.html > >> > >> I am running a current dvb tree with this patch. > >> > >> so far so good. > >> > >> I did not find the time to check if I regained proper reboots, though. I > >> know, sad excuse... > >> > >> nico > >> > >> > > > > I'll give it a try. Thanks for the tip! > > Cheers, > > Eduard > > Hi nico, Eduard, > > can you confirm that the patch solves your Nova-T 500 boot problem? > In this case I would resend the buffer count part as separate patch to > Patrick. It doesn;t appear to fix it. I'll retry this evening, after the F1 Grand Prix. Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Nova-T 500 does not survive reboot
On Thu, 2009-04-30 at 16:08 +0100, Nicolas Will wrote: > > I mention that the URB part is a quick hack. *you* mention, I wouldn't dare... ;o) Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Nova-T 500 does not survive reboot
On Thu, 2009-04-30 at 13:56 +0200, soeren.m...@stud.uni-hannover.de wrote: > > Apr 29 22:42:41 favia kernel: [ 72.272045] ehci_hcd > :07:01.2: > > force halt; handhake c2666814 4000 -> -110 > > [...] > > Do you know if the issue is the same with a Nova-TD stick? If it is, > > then I could be able to use debugging as an excuse to buy one, and > then > > add 2 tuners to the system when all is done :o) > > I had the same "ehci_hcd force halt" error when I was debugging the > Nova-TD dual-stream-switchon-problem: > http://www.mail-archive.com/linux-media@vger.kernel.org/msg04643.html > > Reducing the urb count to 1 (as included in the patch) solved the > "ehci_hcd force halt" issue for me. I mention that the URB part is a quick hack. You were asking for opinions on that, and apparently did not get any feedback. Time for another call? Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Nova-T 500 does not survive reboot
On Thu, 2009-04-30 at 10:16 +, Eduard Huguet wrote: > I can remenber that other guy posted about this issue some time > ago, but I can't find the link. http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/2423/focus=2591 I guess. nico getting used to gmame :o) -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Nova-T 500 does not survive reboot
On Thu, 2009-04-30 at 10:16 +, Eduard Huguet wrote: > Nicolas Will youplala.net> writes: > > > > > Hello all, > > > > I am running an hg clone from a few days ago with firmware 1.20 on a > > 64-bit Ubuntu Intrepid (2.6.27 kernel). > > > > I have noticed that for some time now the card/driver/firmware > > combination does not like warm reboots. > > > > If I reboot the system and try to use any Nova-T 500 tuner, I > > immediately get the mt2060 I2C errors. > > > > If I completely shut down the system, remove the power, then reboot, all > > is fine. > > > > I have missed most of the linux-media traffic, I was still stuck on > > linux-dvb. Have I missed some discussions about this? > > > > Thanks! > > > > Nico > Hi, Nicholas > > I posted the very same thing 3 days ago: > http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/4973 Argh, I missed it (I don't really like gmame's archiving... I will need to get used to it). I have the same : Apr 29 22:42:41 favia kernel: [ 72.272045] ehci_hcd :07:01.2: force halt; handhake c2666814 4000 -> -110 then Apr 29 22:43:02 favia kernel: [ 92.900094] mt2060 I2C write failed Apr 29 22:43:02 favia kernel: [ 92.905830] mt2060 I2C write failed (len=2) Apr 29 22:43:02 favia kernel: [ 92.905835] mt2060 I2C write failed (len=6) Apr 29 22:43:02 favia kernel: [ 92.905838] mt2060 I2C read failed Apr 29 22:43:02 favia kernel: [ 92.912552] mt2060 I2C read failed Apr 29 22:43:02 favia kernel: [ 92.920572] mt2060 I2C read failed Apr 29 22:43:02 favia kernel: [ 92.928552] mt2060 I2C read failed Apr 29 22:43:02 favia kernel: [ 92.936554] mt2060 I2C read failed Apr 29 22:43:02 favia kernel: [ 92.944552] mt2060 I2C read failed ... and at one point I get the following before I shut down Apr 29 22:44:27 favia kernel: [ 177.818215] dvb-usb: could not submit URB no. 0 - get them all back Apr 29 22:44:27 favia kernel: [ 177.818222] dvb-usb: error while enabling fifo. > > > This is something that has been occuring lately, since some months ago. I > don't > know when exactly was this bug introduced, but it has been in HG for a couple > of > months at least. I can remenber that other guy posted about this issue some > time > ago, but I can't find the link. I'm with that too. I was just really busy at the time to dig into it. > > > And for what I see, Janne Grunau is also having problems with the card. See > what > he have just posted...: > http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/4973 I saw that one too, it arrived as I subscribed to the proper list. I'm not directly concerned now, but I will be facing this too when I will want to upgrade my system to the current Ubuntu release. Soo... What can I/we do to help track/fix this? I'm game for a bit of testing, within reason, though, at the system is in production. Do you know if the issue is the same with a Nova-TD stick? If it is, then I could be able to use debugging as an excuse to buy one, and then add 2 tuners to the system when all is done :o) Nico http://www.youplala.net/linux/home-theater-pc/ -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Nova-T 500 does not survive reboot
Hello all, I am running an hg clone from a few days ago with firmware 1.20 on a 64-bit Ubuntu Intrepid (2.6.27 kernel). I have noticed that for some time now the card/driver/firmware combination does not like warm reboots. If I reboot the system and try to use any Nova-T 500 tuner, I immediately get the mt2060 I2C errors. If I completely shut down the system, remove the power, then reboot, all is fine. I have missed most of the linux-media traffic, I was still stuck on linux-dvb. Have I missed some discussions about this? Thanks! Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [linux-dvb] Klear?
On Fri, 2009-02-20 at 15:57 +0200, Juhana Sadeharju wrote: > > I will pick up Kaffeine, but Ubuntu is missing the package. > I try compile it. You must be kidding, right ? http://packages.ubuntu.com/search?suite=default§ion=all&arch=any&searchon=names&keywords=kaffeine Nico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
