> Thanks Dave, I have a MCP79 nvidia USB controller:
I too have:
USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0
Controller (rev a1)
BUT I have never had boot trouble if I plugged in a 4-port hub.
I think Dave means that you need to buy a USB to PCI or PCIe card.
Avoid VIA
2011/10/6 dave cunningham :
> In message
> , Josu
> Lazkano wrote
>
>
>>
>> I get this I2C messages:
>>
>> # tail -f /var/log/messages
>> Oct 5 20:16:44 htpc kernel: [ 534.168957] af9013: I2C read failed
>> reg:d330
>> Oct 5 20:16:49 htpc kernel: [ 538.626152] af9013: I2C read failed
>> reg:d3
On Thu, 2011-10-06 at 01:12 +0200, Josu Lazkano wrote:
> 2011/10/6 Jason Hecker :
> >> http://palosaari.fi/linux/v4l-dvb/firmware/af9015/5.1.0.0/dvb-usb-af9015.fw
> >
> > 5.1? OK, I might eventually try that one too.
> >
> Oct 5 21:40:46 htpc kernel: [ 5576.241897] af9013: I2C read failed reg:d2
In message
,
Josu Lazkano wrote
I get this I2C messages:
# tail -f /var/log/messages
Oct 5 20:16:44 htpc kernel: [ 534.168957] af9013: I2C read failed reg:d330
Oct 5 20:16:49 htpc kernel: [ 538.626152] af9013: I2C read failed reg:d330
Oct 5 21:22:15 htpc kernel: [ 4464.930734] af9013:
> http://dl.dropbox.com/u/1541853/VID_20111006_004447.3gp
That looks very familiar! Does it occur on tuner A or B?
> I get this I2C messages:
> # tail -f /var/log/messages
> Oct 5 20:16:44 htpc kernel: [ 534.168957] af9013: I2C read failed reg:d330
As far as I know I never had any such messag
2011/10/6 Jason Hecker :
>> http://palosaari.fi/linux/v4l-dvb/firmware/af9015/5.1.0.0/dvb-usb-af9015.fw
>
> 5.1? OK, I might eventually try that one too.
>
>> This morning I get a little pixeled playback, less than a second.
>
> OK, mine was fine for a few days then the pixellation started up in e
> http://palosaari.fi/linux/v4l-dvb/firmware/af9015/5.1.0.0/dvb-usb-af9015.fw
5.1? OK, I might eventually try that one too.
> This morning I get a little pixeled playback, less than a second.
OK, mine was fine for a few days then the pixellation started up in earnest.
At the moment my symptoms
2011/10/5 Jason Hecker :
>> Which Firmware are your using?
>
> 4.95
>
>> Yes, because it is also happening with other duo devices on Myth TV
>> 0.24.1
>
> OK, well that is what I am using so I guess I am stuck until it's fixed.
>
> Josu what software and versions are you using?
>
Hello, I am using
> Which Firmware are your using?
4.95
> Yes, because it is also happening with other duo devices on Myth TV
> 0.24.1
OK, well that is what I am using so I guess I am stuck until it's fixed.
Josu what software and versions are you using?
--
To unsubscribe from this list: send the line "unsubscri
On Wed, 2011-10-05 at 07:44 +1100, Jason Hecker wrote:
> I have had some luck with this patch. I am still getting fouled
> recordings with tuner A but it's not consistent. I have yet to
> ascertain if the problem occurs depending on the order of tuning to
> have both tuners recording different fr
I have had some luck with this patch. I am still getting fouled
recordings with tuner A but it's not consistent. I have yet to
ascertain if the problem occurs depending on the order of tuning to
have both tuners recording different frquencies at the same time, ie
Tuner B then Tuner A or vice vers
2011/9/28 tvboxspy :
> Frontend bus lock for af9015 devices.
>
> Last week, I aqcuired a dual KWorld PlusTV Dual DVB-T Stick (DVB-T 399U).
>
> The lock is intended for dual frontends that share the same tuner I2C address
> to stop either frontend sending data while any gate is open. The patch
> sho
Frontend bus lock for af9015 devices.
Last week, I aqcuired a dual KWorld PlusTV Dual DVB-T Stick (DVB-T 399U).
The lock is intended for dual frontends that share the same tuner I2C address
to stop either frontend sending data while any gate is open. The patch
should have no effect on single devi
13 matches
Mail list logo
