Re: [PATCH] af9013 Extended monitoring in set_frontend.
> Trouble is, on a Nvidia motherboard I have it does not do it at all and > all applications work without any troubles. This seems to suggest a USB > motherboard driver issue. Right. Well, I can say with high confidence that my dual tuner worked flawlessly for 18 months using Ubuntu's kernel 2.6.32 up until some update around May. Some kernel (or other) update apparently made it all go pear shaped which prompted me to get another card then update the whole system to try fix the problem - I haven't gone back to an old 2.6.32 kernel. So I am wondering if some other non v4l related patch has affected us all. > I am continuing to look into it. OK, well I am still running my system with your two patches, with corruptions alas, so if you'd like me to independently try stuff out let me know. Jason -- 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: [PATCH] af9013 Extended monitoring in set_frontend.
On Tue, 2011-10-11 at 08:06 +1100, Jason Hecker wrote: > > Playing with Kaffeine or Mplayer all the devices are fine on the same > > system. > > Right, admittedly most of my testing has been done with MythTV. I > recall about a month ago I could also get corruption with mplayer. > > > At the moment, I am going step by step what Myth TV is sending to the > > devices. > > Great. If you want I can replicate your tests here to see what I get. > > Antti, my AF9015 chips are integrated on PCI so I can't swap cables > (alas, if only this was my problem!) Jason, do you get firmware loading fails on boot with the PCI device? There needs to be a delay put in the firmware download of at least 250uS after each write, but this does not solve the corruption. I have tried everything, but all of them fail to get rid of the corruption on the first frontend when the second frontend starts and then corruptions every 5 seconds or so. These only come through demux on endpoint 84 and are not caused by any other frontend operations. Trouble is, on a Nvidia motherboard I have it does not do it at all and all applications work without any troubles. This seems to suggest a USB motherboard driver issue. However, the frontend lock does make it at least work on Myth TV. I am continuing to look into it. Regards Malcolm -- 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: [PATCH] af9013 Extended monitoring in set_frontend.
> Playing with Kaffeine or Mplayer all the devices are fine on the same > system. Right, admittedly most of my testing has been done with MythTV. I recall about a month ago I could also get corruption with mplayer. > At the moment, I am going step by step what Myth TV is sending to the > devices. Great. If you want I can replicate your tests here to see what I get. Antti, my AF9015 chips are integrated on PCI so I can't swap cables (alas, if only this was my problem!) Cheers Jason -- 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: [PATCH] af9013 Extended monitoring in set_frontend.
On Mon, 2011-10-10 at 22:31 +0300, Antti Palosaari wrote: > On 10/08/2011 11:05 PM, Jason Hecker wrote: > >> Which kernels are you all running? > > > > 2.6.38-11-generic #50-Ubuntu SMP (Mythbuntu 11.04) > > Have you tried other USB-cable or connect it directly to the mobo USB port. > > I just used one af9015 + 2x mxl5007t and got some streaming corruptions. > I was WTF. Switched to af9015 + 2x mxl5005s since it is device I usually > have used. Still errors. Then I commented out remote controller polling > and all status polling from drivers. Still some stream corruptions. > Finally I realized I have other USB-cable than normally. Plugged device > directly to the mobo USB and now both tuners are streaming same time > without errors. I have just been testing af9015s both 399U and single, along with other devices on Mythbuntu 11.04 on 2.6.38-11 and getting the same corruption. Playing with Kaffeine or Mplayer all the devices are fine on the same system. This is very strange! At the moment, I am going step by step what Myth TV is sending to the devices. Regards Malcolm -- 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: [PATCH] af9013 Extended monitoring in set_frontend.
On 10/08/2011 11:05 PM, Jason Hecker wrote: Which kernels are you all running? 2.6.38-11-generic #50-Ubuntu SMP (Mythbuntu 11.04) Have you tried other USB-cable or connect it directly to the mobo USB port. I just used one af9015 + 2x mxl5007t and got some streaming corruptions. I was WTF. Switched to af9015 + 2x mxl5005s since it is device I usually have used. Still errors. Then I commented out remote controller polling and all status polling from drivers. Still some stream corruptions. Finally I realized I have other USB-cable than normally. Plugged device directly to the mobo USB and now both tuners are streaming same time without errors. Antti -- http://palosaari.fi/ -- 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: [PATCH] af9013 Extended monitoring in set_frontend.
> Which kernels are you all running? 2.6.38-11-generic #50-Ubuntu SMP (Mythbuntu 11.04) -- 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: [PATCH] af9013 Extended monitoring in set_frontend.
I have been following that discussion and hoping you would finally find out the reason. But I want to point out few things; * .set_frontend() is called only when channel changed * .set_params() is called only when channel changed * there is no I2C traffic for tuner after channel changed * there is I2C traffic to tuner only when channel is changed Since generally changes to .set_frontend() will not have effect in normal use, when both devices are already streaming. Only in case of lock is missed and re-tune initialized or channel changed. regards Antti -- http://palosaari.fi/ -- 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: [PATCH] af9013 Extended monitoring in set_frontend.
2011/10/8 Malcolm Priestley : > On Sat, 2011-10-08 at 15:13 +0200, Josu Lazkano wrote: >> 2011/10/8 Jason Hecker : >> >> Try this patch, it should stop start up corruption on the same frontend. >> > >> > Thanks. I'll try it today. >> > >> > Have you been able to reproduce any of the corruption issues I and >> > others are having? >> > >> > I noticed last night some recordings on the same card had different >> > levels of corruption depending on the order of tuning >> > >> > Tuner A then tuner B : Tuner A was heavily corrupted. Tuner B was a fine. >> > Tuner B then tuner A: Tuner A had a small corruption every few seconds >> > and the show was watchable, Tuner B was fine. >> > >> >> Thanks again, I try the patch and it works well last nigh. This >> morning one tuner is getting pixeled images and the other can not >> LOCK. >> >> This is the kernel messages: >> >> # tail /var/log/messages >> Oct 8 14:16:06 htpc kernel: [45025.328902] mxl5005s I2C write failed >> Oct 8 14:16:06 htpc kernel: [45025.333147] mxl5005s I2C write failed >> Oct 8 14:16:06 htpc kernel: [45025.333637] mxl5005s I2C write failed >> Oct 8 14:16:06 htpc kernel: [45025.490524] mxl5005s I2C write failed >> Oct 8 14:16:06 htpc kernel: [45025.491014] mxl5005s I2C write failed >> Oct 8 14:16:08 htpc kernel: [45027.642858] mxl5005s I2C write failed >> Oct 8 14:16:08 htpc kernel: [45027.647477] mxl5005s I2C write failed >> Oct 8 14:16:08 htpc kernel: [45027.647970] mxl5005s I2C write failed >> Oct 8 14:16:09 htpc kernel: [45027.806477] mxl5005s I2C write failed >> Oct 8 14:16:09 htpc kernel: [45027.806969] mxl5005s I2C write failed >> >> I try to increase the signal timeout from 1000 to 2000 ms and the >> tuning timeout from 3000 to 6000 ms on mythbackend. >> > I have left these at the default settings > > Which kernels are you all running? > > uname -rv > > I think replicate your systems on my test pc. > > Hello again, this is my kernel: $ uname -rv 2.6.32-5-686 #1 SMP Fri Sep 9 20:51:05 UTC 2011 This is a Debian Squeeze system. Regards. -- Josu Lazkano -- 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: [PATCH] af9013 Extended monitoring in set_frontend.
On Sat, 2011-10-08 at 15:13 +0200, Josu Lazkano wrote: > 2011/10/8 Jason Hecker : > >> Try this patch, it should stop start up corruption on the same frontend. > > > > Thanks. I'll try it today. > > > > Have you been able to reproduce any of the corruption issues I and > > others are having? > > > > I noticed last night some recordings on the same card had different > > levels of corruption depending on the order of tuning > > > > Tuner A then tuner B : Tuner A was heavily corrupted. Tuner B was a fine. > > Tuner B then tuner A: Tuner A had a small corruption every few seconds > > and the show was watchable, Tuner B was fine. > > > > Thanks again, I try the patch and it works well last nigh. This > morning one tuner is getting pixeled images and the other can not > LOCK. > > This is the kernel messages: > > # tail /var/log/messages > Oct 8 14:16:06 htpc kernel: [45025.328902] mxl5005s I2C write failed > Oct 8 14:16:06 htpc kernel: [45025.333147] mxl5005s I2C write failed > Oct 8 14:16:06 htpc kernel: [45025.333637] mxl5005s I2C write failed > Oct 8 14:16:06 htpc kernel: [45025.490524] mxl5005s I2C write failed > Oct 8 14:16:06 htpc kernel: [45025.491014] mxl5005s I2C write failed > Oct 8 14:16:08 htpc kernel: [45027.642858] mxl5005s I2C write failed > Oct 8 14:16:08 htpc kernel: [45027.647477] mxl5005s I2C write failed > Oct 8 14:16:08 htpc kernel: [45027.647970] mxl5005s I2C write failed > Oct 8 14:16:09 htpc kernel: [45027.806477] mxl5005s I2C write failed > Oct 8 14:16:09 htpc kernel: [45027.806969] mxl5005s I2C write failed > > I try to increase the signal timeout from 1000 to 2000 ms and the > tuning timeout from 3000 to 6000 ms on mythbackend. > I have left these at the default settings Which kernels are you all running? uname -rv I think replicate your systems on my test 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
Re: [PATCH] af9013 Extended monitoring in set_frontend.
2011/10/8 Jason Hecker : >> Try this patch, it should stop start up corruption on the same frontend. > > Thanks. I'll try it today. > > Have you been able to reproduce any of the corruption issues I and > others are having? > > I noticed last night some recordings on the same card had different > levels of corruption depending on the order of tuning > > Tuner A then tuner B : Tuner A was heavily corrupted. Tuner B was a fine. > Tuner B then tuner A: Tuner A had a small corruption every few seconds > and the show was watchable, Tuner B was fine. > Thanks again, I try the patch and it works well last nigh. This morning one tuner is getting pixeled images and the other can not LOCK. This is the kernel messages: # tail /var/log/messages Oct 8 14:16:06 htpc kernel: [45025.328902] mxl5005s I2C write failed Oct 8 14:16:06 htpc kernel: [45025.333147] mxl5005s I2C write failed Oct 8 14:16:06 htpc kernel: [45025.333637] mxl5005s I2C write failed Oct 8 14:16:06 htpc kernel: [45025.490524] mxl5005s I2C write failed Oct 8 14:16:06 htpc kernel: [45025.491014] mxl5005s I2C write failed Oct 8 14:16:08 htpc kernel: [45027.642858] mxl5005s I2C write failed Oct 8 14:16:08 htpc kernel: [45027.647477] mxl5005s I2C write failed Oct 8 14:16:08 htpc kernel: [45027.647970] mxl5005s I2C write failed Oct 8 14:16:09 htpc kernel: [45027.806477] mxl5005s I2C write failed Oct 8 14:16:09 htpc kernel: [45027.806969] mxl5005s I2C write failed I try to increase the signal timeout from 1000 to 2000 ms and the tuning timeout from 3000 to 6000 ms on mythbackend. Which will be the best value for the Kworld 399U? Thank for your great work on this device. Best regards! -- Josu Lazkano -- 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: [PATCH] af9013 Extended monitoring in set_frontend.
On Sat, 2011-10-08 at 09:46 +1100, Jason Hecker wrote: > > Try this patch, it should stop start up corruption on the same frontend. > > Thanks. I'll try it today. > > Have you been able to reproduce any of the corruption issues I and > others are having? Yes , I left it recording various programmes overnight, but the symptoms come and go. > > I noticed last night some recordings on the same card had different > levels of corruption depending on the order of tuning > > Tuner A then tuner B : Tuner A was heavily corrupted. Tuner B was a fine. > Tuner B then tuner A: Tuner A had a small corruption every few seconds > and the show was watchable, Tuner B was fine. It seems like a lagging effect, as if the devices firmware is slowing down. -- 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: [PATCH] af9013 Extended monitoring in set_frontend.
> Try this patch, it should stop start up corruption on the same frontend. Thanks. I'll try it today. Have you been able to reproduce any of the corruption issues I and others are having? I noticed last night some recordings on the same card had different levels of corruption depending on the order of tuning Tuner A then tuner B : Tuner A was heavily corrupted. Tuner B was a fine. Tuner B then tuner A: Tuner A had a small corruption every few seconds and the show was watchable, Tuner B was fine. -- 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
