running multiple DVB cards successfully.. what do I need to know?? (major and minor numbers??)
Hi All Some of you may have read some of my posts about an incorrect firmware readback message appearing in my dmesg, shortly after a tuner was engaged. I have isolated this problem, but the workaround so far has not been pretty. On a hunch I removed my Dvico Fusion HDTV lite card from the system, running now only with the Dvico Fusion Dual Express. The issue has gone, I am not getting the kdvb process hogging cpu cycles and this message has stopped. I had tried both letting the kernel (or is it udev) assign the major and minor numbers and I had tried to manually set them via modprobe.conf (formerly modules.conf, I don't know if this is a global change or specific to Gentoo) I had the major number the same for both cards, with a separate minor number for each of the three tuners, this seems to be the same. Is this how I should be setting up for 2 cards or should I be using some other type of configuration. cheers Allan -- 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: running multiple DVB cards successfully.. what do I need to know?? (major and minor numbers??)
Thanks Mike Is this likely to stop the Incorrect Readback of kernel version issue as well? cheers Allan On Mon Feb 23 17:57 , Michael Krufky sent: On Mon, Feb 23, 2009 at 5:49 PM, sonof...@iinet.net.au sonof...@iinet.net.au wrote: Some of you may have read some of my posts about an incorrect firmware readback message appearing in my dmesg, shortly after a tuner was engaged. I have isolated this problem, but the workaround so far has not been pretty. On a hunch I removed my Dvico Fusion HDTV lite card from the system, running now only with the Dvico Fusion Dual Express. The issue has gone, I am not getting the kdvb process hogging cpu cycles and this message has stopped. I had tried both letting the kernel (or is it udev) assign the major and minor numbers and I had tried to manually set them via modprobe.conf (formerly modules.conf, I don't know if this is a global change or specific to Gentoo) I had the major number the same for both cards, with a separate minor number for each of the three tuners, this seems to be the same. Is this how I should be setting up for 2 cards or should I be using some other type of configuration. Allan, I recommend to use the 'adapter_nr' module option. You can specify this option in modprobe.conf -- the name of this file is distro-specific. For instance, to make the dual card appear before the lite card: options cx23885 adapter_nr=0,1 options dvb-bt8xx adapter_nr=2 to make the lite card appear before the dual card: options cx23885 adapter_nr=0 options dvb-bt8xx adapter_nr=1,2 I hope you find this helpful. Regards, Mike ) -- 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: POLL: for/against dropping support for kernels 2.6.22
Yes... On Mon Feb 23 12:13 , hermann pitton sent: Am Sonntag, den 22.02.2009, 11:15 +0100 schrieb Hans Verkuil: Hi all, There are lot's of discussions, but it can be hard sometimes to actually determine someone's opinion. So here is a quick poll, please reply either to the list or directly to me with your yes/no answer and (optional but welcome) a short explanation to your standpoint. It doesn't matter if you are a user or developer, I'd like to see your opinion regardless. Please DO NOT reply to the replies, I'll summarize the results in a week's time and then we can discuss it further. Should we drop support for kernels _: Yes _: No Yes. Optional question: Why: Keeping too old kernels supported makes others lazy and in worst case they ask you to support v4l2 version one. (happened) Our user base for new devices is covered with down to 2.6.22 for now, we likely never got anything from those on old commercial distribution kernels, same for Debian and stuff derived from there. Since new drivers actually prefer to avoid the compat work and are happy to make it just into the latest rc1 during the merge window and further from there, there is no loss either. Some new devices we likely get on already established drivers should not be hard to add to a v4l-dvb tar ball we leave with support for the even older kernels. Cheers, Hermann -- 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 ) -- 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: Fwd: [linux-dvb] dvico dual express continuuing issues.
Hi All In december I posted a message regarding some issues with the dvico driver. http://www.linuxtv.org/pipermail/linux-dvb/2008-December/031137.html The kernel is reporting incorrect callback of the firmware. Also, if the tuner isn't being used for a few hours, I then get errors from mythtv about it not being able to contact the backend and only rebooting the system will fix the problem (restarting mythbackend and frontend does not help). I eventually reported this as fixed to do with bios settings but I was wrong. I have done alot more testing and have found that it seems to be only after mythtv has accessed the device where this problem beings begins... I will try the latest hg version and see what happens. I will also try another tv application and see if that makes a difference (but I really would like to continue using mythtv as I have 2 other frontends). More information.. (and questions). I know I definitely didn't have this problem with earlier versions of the driver (roughly pre September.. Chris Pascoe's original version actually seemed more stable although didn't report correct signal strength) The cpu is a an opteron 170 2GB of OCZ DDR500 RAM (clocked at standard 400 of course, not overclocking this thing actually unless watching HD it is usually sitting at 1000MHZ) Nvidia 7600 GS video card (as I read horrible things about my onboard ATI chipset) using nvidia drivers not using xvmc however. I have eliminated the motherboard as since I originally reported the issue I have changed mobo (from nvidia nforce4 chipset to ati chipset primarily to get a micro atx mobo for my HTPC case). Fairly standard kernel with pre-emption (should I be using an rt patched kernel??) Are there any other kernel options I should remove or add??? I am using the most recent unstable Gentoo release of mythtv (0.21_p19046) but saw the same problem on the most recent stable release too. Are there any compile time options (or USE flags) I need to set or unset?? The system also houses my third tuner/second card, a dvico fusion lite (older pci version rock solid stable).. Are there any modules.conf settings I need to look out for (although it worked before ...) As I said, I will try out the latest hg version tonight.. but any advice would be appreciated greatly!!! cheers Allan Same result with the hg version updated tonight. I haven't had a chance to use another tv app yet as we are currently watching TV. I will send a further update later. -- 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: Fwd: [linux-dvb] dvico dual express incorrect firmware version readback!!!
On Mon Feb 16 22:51 , sonof...@iinet.net.au sent: Hi All In december I posted a message regarding some issues with the dvico driver. http://www.linuxtv.org/pipermail/linux-dvb/2008-December/031137.html The kernel is reporting incorrect callback of the firmware. Also, if the tuner isn't being used for a few hours, I then get errors from mythtv about it not being able to contact the backend and only rebooting the system will fix the problem (restarting mythbackend and frontend does not help). I eventually reported this as fixed to do with bios settings but I was wrong. I have done alot more testing and have found that it seems to be only after mythtv has accessed the device where this problem beings begins... I will try the latest hg version and see what happens. I will also try another tv application and see if that makes a difference (but I really would like to continue using mythtv as I have 2 other frontends). More information.. (and questions). I know I definitely didn't have this problem with earlier versions of the driver (roughly pre September.. Chris Pascoe's original version actually seemed more stable although didn't report correct signal strength) The cpu is a an opteron 170 2GB of OCZ DDR500 RAM (clocked at standard 400 of course, not overclocking this thing actually unless watching HD it is usually sitting at 1000MHZ) Nvidia 7600 GS video card (as I read horrible things about my onboard ATI chipset) using nvidia drivers not using xvmc however. I have eliminated the motherboard as since I originally reported the issue I have changed mobo (from nvidia nforce4 chipset to ati chipset primarily to get a micro atx mobo for my HTPC case). Fairly standard kernel with pre-emption (should I be using an rt patched kernel??) Are there any other kernel options I should remove or add??? I am using the most recent unstable Gentoo release of mythtv (0.21_p19046) but saw the same problem on the most recent stable release too. Are there any compile time options (or USE flags) I need to set or unset?? The system also houses my third tuner/second card, a dvico fusion lite (older pci version rock solid stable).. Are there any modules.conf settings I need to look out for (although it worked before ...) As I said, I will try out the latest hg version tonight.. but any advice would be appreciated greatly!!! cheers Allan Same result with the hg version updated tonight. I haven't had a chance to use another tv app yet as we are currently watching TV. I will send a further update later. Is anyone else actually seeing this Incorrect Firmware Version Readback error?? Is there something I am missing? (stupid kernel setup or something??)... Should I try and source the firmware again or is this unlikely to be the issue? -- 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
Fwd: [linux-dvb] dvico dual express continuuing issues.
I got a deprecated list message (so how do I unsubscribe from linux-dvb) - Original Message - From: 'sonof...@iinet.net.au' sonof...@iinet.net.au To: linux-...@linuxtv.org Sent: Mon Feb 16 15:56 Subject: Fwd: [linux-dvb] dvico dual express continuuing issues. Hi All In december I posted a message regarding some issues with the dvico driver. http://www.linuxtv.org/pipermail/linux-dvb/2008-December/031137.html The kernel is reporting incorrect callback of the firmware. Also, if the tuner isn't being used for a few hours, I then get errors from mythtv about it not being able to contact the backend and only rebooting the system will fix the problem (restarting mythbackend and frontend does not help). I eventually reported this as fixed to do with bios settings but I was wrong. I have done alot more testing and have found that it seems to be only after mythtv has accessed the device where this problem beings begins... I will try the latest hg version and see what happens. I will also try another tv application and see if that makes a difference (but I really would like to continue using mythtv as I have 2 other frontends). More information.. (and questions). I know I definitely didn't have this problem with earlier versions of the driver (roughly pre September.. Chris Pascoe's original version actually seemed more stable although didn't report correct signal strength) The cpu is a an opteron 170 2GB of OCZ DDR500 RAM (clocked at standard 400 of course, not overclocking this thing actually unless watching HD it is usually sitting at 1000MHZ) Nvidia 7600 GS video card (as I read horrible things about my onboard ATI chipset) using nvidia drivers not using xvmc however. I have eliminated the motherboard as since I originally reported the issue I have changed mobo (from nvidia nforce4 chipset to ati chipset primarily to get a micro atx mobo for my HTPC case). Fairly standard kernel with pre-emption (should I be using an rt patched kernel??) Are there any other kernel options I should remove or add??? I am using the most recent unstable Gentoo release of mythtv (0.21_p19046) but saw the same problem on the most recent stable release too. Are there any compile time options (or USE flags) I need to set or unset?? The system also houses my third tuner/second card, a dvico fusion lite (older pci version rock solid stable).. Are there any modules.conf settings I need to look out for (although it worked before ...) As I said, I will try out the latest hg version tonight.. but any advice would be appreciated greatly!!! cheers Allan ___ linux-dvb users mailing list For V4L/DVB development, please use instead linux-media@vger.kernel.org linux-...@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ) -- 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
