drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Bogdan Oprea]

[-- Attachment #1: Type: text/plain, Size: 230 bytes --]

this is a fix for this type of error

[18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error while loading driver (-19)
[18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' successfully deinitialized and disconnected

[-- Attachment #2: Asus-U3100Mini-Plus.patch --]
[-- Type: application/octet-stream, Size: 250 bytes --]

--- a/drivers/media/tuners/fc2580.c
+++ b/drivers/media/tuners/fc2580.c
@@ -506,6 +506,7 @@
        switch (chip_id) {
        case 0x56:
        case 0x5a:
+       case 0xff:
                break;
        default:
                goto err;

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Oliver Schinagl]

On 01-07-13 08:53, Bogdan Oprea wrote:
> this is a fix for this type of error
>
> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error while loading driver (-19)
> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' successfully deinitialized and disconnected
>
This isn't really a fix, I think i mentioned this on the ML ages ago, 
and I belive it was said by antti that it's a bogus/broken chipID ...

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Antti Palosaari]

On 07/01/2013 09:53 AM, Bogdan Oprea wrote:
> this is a fix for this type of error
>
> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error while loading driver (-19)
> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' successfully deinitialized and disconnected
>

--- a/drivers/media/tuners/fc2580.c
+++ b/drivers/media/tuners/fc2580.c
@@ -506,6 +506,7 @@
         switch (chip_id) {
         case 0x56:
         case 0x5a:
+       case 0xff:
                 break;
         default:
                 goto err;


That does not look correct. If chip id reading is returning 0x00 or 0xff 
it is about 100% sure there is I2C communication failure.

Could you make some test and tweak it a little bit more to see what is 
problem. Does I2C read work after that or is it failing all the time?

regards
Antti


-- 
http://palosaari.fi/

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Antti Palosaari]

On 07/01/2013 10:52 AM, Oliver Schinagl wrote:
> On 01-07-13 08:53, Bogdan Oprea wrote:
>> this is a fix for this type of error
>>
>> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error while
>> loading driver (-19)
>> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' successfully
>> deinitialized and disconnected
>>
> This isn't really a fix, I think i mentioned this on the ML ages ago,

Argh, I just replied that same. Oliver, do you has that same device? Is 
it working? Could you tweak to see if I2C readings are working at all?


regards
Antti


-- 
http://palosaari.fi/

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Oliver Schinagl]

On 01-07-13 15:23, Antti Palosaari wrote:
> On 07/01/2013 10:52 AM, Oliver Schinagl wrote:
>> On 01-07-13 08:53, Bogdan Oprea wrote:
>>> this is a fix for this type of error
>>>
>>> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error while
>>> loading driver (-19)
>>> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' successfully
>>> deinitialized and disconnected
>>>
>> This isn't really a fix, I think i mentioned this on the ML ages ago,
>
> Argh, I just replied that same. Oliver, do you has that same device? Is
> it working? Could you tweak to see if I2C readings are working at all?
I have the same device, but mine works normally (though I haven't 
checked for ages), I will try it tonight when I'm at home and don't 
forget what happens with my current kernel.
>
>
> regards
> Antti
>
>

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Antti Palosaari]

On 07/01/2013 04:26 PM, Oliver Schinagl wrote:
> On 01-07-13 15:23, Antti Palosaari wrote:
>> On 07/01/2013 10:52 AM, Oliver Schinagl wrote:
>>> On 01-07-13 08:53, Bogdan Oprea wrote:
>>>> this is a fix for this type of error
>>>>
>>>> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error while
>>>> loading driver (-19)
>>>> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' successfully
>>>> deinitialized and disconnected
>>>>
>>> This isn't really a fix, I think i mentioned this on the ML ages ago,
>>
>> Argh, I just replied that same. Oliver, do you has that same device? Is
>> it working? Could you tweak to see if I2C readings are working at all?
> I have the same device, but mine works normally (though I haven't
> checked for ages), I will try it tonight when I'm at home and don't
> forget what happens with my current kernel.

Actually, I has RTL2832U + FC2580, and it works. It is not Asus 
U3100Mini Plus.

Reading of that chip id must be working on the very first, is RTL2832U 
driver detects whole tuner by probing it.

	/* check FC2580 ID register; reg=01 val=56 */
	ret = rtl28xxu_ctrl_msg(d, &req_fc2580);
	if (ret == 0 && buf[0] == 0x56) {
		priv->tuner = TUNER_RTL2832_FC2580;
		priv->tuner_name = "FC2580";
		goto found;
	}

So I wonder if tuner I2C readings starts failing after that.

regards
Antti

-- 
http://palosaari.fi/

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Michael Krufky]

I agree with Antti & Oliver - this is not a proper fix, rather, it's
an indication of something else that's wrong.  Does it actually work
the first time?  (I'm assuming, after a cold replug?)  Is the i2c bus
not being properly reset?

Does it ever read a sane value or is it always 0xFF?

-Mike

On Mon, Jul 1, 2013 at 9:36 AM, Antti Palosaari <crope@iki.fi> wrote:
> On 07/01/2013 04:26 PM, Oliver Schinagl wrote:
>>
>> On 01-07-13 15:23, Antti Palosaari wrote:
>>>
>>> On 07/01/2013 10:52 AM, Oliver Schinagl wrote:
>>>>
>>>> On 01-07-13 08:53, Bogdan Oprea wrote:
>>>>>
>>>>> this is a fix for this type of error
>>>>>
>>>>> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error while
>>>>> loading driver (-19)
>>>>> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' successfully
>>>>> deinitialized and disconnected
>>>>>
>>>> This isn't really a fix, I think i mentioned this on the ML ages ago,
>>>
>>>
>>> Argh, I just replied that same. Oliver, do you has that same device? Is
>>> it working? Could you tweak to see if I2C readings are working at all?
>>
>> I have the same device, but mine works normally (though I haven't
>> checked for ages), I will try it tonight when I'm at home and don't
>> forget what happens with my current kernel.
>
>
> Actually, I has RTL2832U + FC2580, and it works. It is not Asus U3100Mini
> Plus.
>
> Reading of that chip id must be working on the very first, is RTL2832U
> driver detects whole tuner by probing it.
>
>         /* check FC2580 ID register; reg=01 val=56 */
>         ret = rtl28xxu_ctrl_msg(d, &req_fc2580);
>         if (ret == 0 && buf[0] == 0x56) {
>                 priv->tuner = TUNER_RTL2832_FC2580;
>                 priv->tuner_name = "FC2580";
>                 goto found;
>         }
>
> So I wonder if tuner I2C readings starts failing after that.
>
>
> regards
> Antti
>
> --
> http://palosaari.fi/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Oliver Schinagl]

On 07/01/13 15:26, Oliver Schinagl wrote:
> On 01-07-13 15:23, Antti Palosaari wrote:
>> On 07/01/2013 10:52 AM, Oliver Schinagl wrote:
>>> On 01-07-13 08:53, Bogdan Oprea wrote:
>>>> this is a fix for this type of error
>>>>
>>>> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error while
>>>> loading driver (-19)
>>>> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' successfully
>>>> deinitialized and disconnected
>>>>
>>> This isn't really a fix, I think i mentioned this on the ML ages ago,
>>
>> Argh, I just replied that same. Oliver, do you has that same device? Is
>> it working? Could you tweak to see if I2C readings are working at all?
> I have the same device, but mine works normally (though I haven't
> checked for ages), I will try it tonight when I'm at home and don't
> forget what happens with my current kernel.

Hard to test when it 'just works (tm)' :)

After a clean reboot:
[  100.965450] usb 2-1: new high-speed USB device number 2 using ehci-pci
[  101.086860] usb 2-1: New USB device found, idVendor=0b05, idProduct=1779
[  101.086874] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[  101.086883] usb 2-1: Product: AF9035A USB Device
[  101.086889] usb 2-1: Manufacturer: Afa Technologies Inc.
[  101.086895] usb 2-1: SerialNumber: AF0102020700001
[  101.092237] input: Afa Technologies Inc. AF9035A USB Device as 
/devices/pci0000:00/0000:00:13.2/usb2/2-1/2-1:1.1/input/input14
[  101.092506] hid-generic 0003:0B05:1779.0003: input: USB HID v1.01 
Keyboard [Afa Technologies Inc. AF9035A USB Device] on 
usb-0000:00:13.2-1/input1
[  101.145576] usbcore: registered new interface driver dvb_usb_af9035
[  101.146220] usb 2-1: dvb_usb_v2: found a 'Asus U3100Mini Plus' in 
cold state
[  101.158094] usb 2-1: dvb_usb_v2: downloading firmware from file 
'dvb-usb-af9035-02.fw'
[  101.410106] usb 2-1: dvb_usb_af9035: bad firmware
[  101.467276] usb 2-1: dvb_usb_af9035: firmware version=12.13.15.0
[  101.467302] usb 2-1: dvb_usb_v2: found a 'Asus U3100Mini Plus' in 
warm state
[  101.469606] usb 2-1: dvb_usb_v2: will pass the complete MPEG2 
transport stream to the software demuxer
[  101.469680] DVB: registering new adapter (Asus U3100Mini Plus)
[  101.483031] i2c i2c-1: af9033: firmware version: LINK=12.13.15.0 
OFDM=6.20.15.0
[  101.486914] usb 2-1: DVB: registering adapter 0 frontend 0 (Afatech 
AF9033 (DVB-T))...
[  101.552160] i2c i2c-1: fc2580: FCI FC2580 successfully identified
[  101.564633] usb 2-1: dvb_usb_v2: 'Asus U3100Mini Plus' successfully 
initialized and connected

Linux valexia 3.9.4-gentoo #6 SMP PREEMPT Thu Jun 13 00:19:15 CEST 2013 
x86_64 AMD Phenom(tm) II X6 1090T Processor AuthenticAMD GNU/Linux


The bad firmware wories me, no clue where that error is from, using:
862604ab3fec0c94f4bf22b4cffd0d89  /lib/firmware/dvb-usb-af9035-02.fw

after downloading one of your firmwares and several hotplugs:
[  591.004936] usb 2-1: Product: AF9035A USB Device
[  591.004943] usb 2-1: Manufacturer: Afa Technologies Inc.
[  591.004949] usb 2-1: SerialNumber: AF0102020700001
[  591.010242] usb 2-1: dvb_usb_v2: found a 'Asus U3100Mini Plus' in 
cold state
[  591.010358] usb 2-1: dvb_usb_v2: downloading firmware from file 
'dvb-usb-af9035-02.fw'
[  591.011142] input: Afa Technologies Inc. AF9035A USB Device as 
/devices/pci0000:00/0000:00:13.2/usb2/2-1/2-1:1.1/input/input17
[  591.011292] hid-generic 0003:0B05:1779.0006: input: USB HID v1.01 
Keyboard [Afa Technologies Inc. AF9035A USB Device] on 
usb-0000:00:13.2-1/input1
[  591.318792] usb 2-1: dvb_usb_af9035: firmware version=12.13.15.0
[  591.318828] usb 2-1: dvb_usb_v2: found a 'Asus U3100Mini Plus' in 
warm state
[  591.320986] usb 2-1: dvb_usb_v2: will pass the complete MPEG2 
transport stream to the software demuxer
[  591.321062] DVB: registering new adapter (Asus U3100Mini Plus)
[  591.325398] i2c i2c-1: af9033: firmware version: LINK=12.13.15.0 
OFDM=6.20.15.0
[  591.329331] usb 2-1: DVB: registering adapter 0 frontend 0 (Afatech 
AF9033 (DVB-T))...
[  591.366046] i2c i2c-1: fc2580: FCI FC2580 successfully identified
[  591.378790] usb 2-1: dvb_usb_v2: 'Asus U3100Mini Plus' successfully 
initialized and connected

3735d499d945a6bb873a7f3ad5c701fa_12.13.15.0_6.20.15.0 is the one i used.

dvb-fe-tool -g works fine
dvb-fe-tool -g
INFO     Device Afatech AF9033 (DVB-T) (/dev/dvb/adapter0/frontend0) 
capabilities:
INFO          CAN_FEC_1_2
INFO          CAN_FEC_2_3
INFO          CAN_FEC_3_4
INFO          CAN_FEC_5_6
INFO          CAN_FEC_7_8
INFO          CAN_FEC_AUTO
INFO          CAN_GUARD_INTERVAL_AUTO
INFO          CAN_HIERARCHY_AUTO
INFO          CAN_INVERSION_AUTO
INFO          CAN_MUTE_TS
INFO          CAN_QAM_16
INFO          CAN_QAM_64
INFO          CAN_QAM_AUTO
INFO          CAN_QPSK
INFO          CAN_RECOVER
INFO          CAN_TRANSMISSION_MODE_AUTO
INFO     DVB API Version 5.10, Current v5 delivery system: DVBT
INFO     Supported delivery system:
INFO         [DVBT]
INFO     Got parameters for DVBT:
INFO     FREQUENCY = 0
INFO     MODULATION = QPSK
INFO     BANDWIDTH_HZ = 0
INFO     INVERSION = OFF
INFO     CODE_RATE_HP = NONE
INFO     CODE_RATE_LP = NONE
INFO     GUARD_INTERVAL = 1/32
INFO     TRANSMISSION_MODE = 2K
INFO     HIERARCHY = NONE
INFO     DELIVERY_SYSTEM = DVBT
INFO     FREQUENCY = 0
INFO     MODULATION = QPSK
INFO     BANDWIDTH_HZ = 0
INFO     INVERSION = OFF
INFO     CODE_RATE_HP = NONE
INFO     CODE_RATE_LP = NONE
INFO     GUARD_INTERVAL = 1/32
INFO     TRANSMISSION_MODE = 2K
INFO     HIERARCHY = NONE
INFO     DELIVERY_SYSTEM = DVBT

dvbscan fails horribly:
Unable to query frontend status

scan-dvb works fine:
0x0000 0x044d: pmt_pid 0x0000 Digitenne -- Nederland 1 (running)
0x0000 0x044e: pmt_pid 0x0000 Digitenne -- Nederland 2 (running)
0x0000 0x044f: pmt_pid 0x0000 Digitenne -- Nederland 3 (running)
0x0000 0x0450: pmt_pid 0x0000 Digitenne -- Omroep Brabant (running)
0x0000 0x0457: pmt_pid 0x0000 Digitenne -- Omroep Brabant (running)
0x0000 0x0458: pmt_pid 0x0000 Digitenne -- Radio 1 (running)
0x0000 0x0459: pmt_pid 0x0000 Digitenne -- Radio 2 (running)
0x0000 0x045a: pmt_pid 0x0000 Digitenne -- 3FM (running)
0x0000 0x045b: pmt_pid 0x0000 Digitenne -- Radio 4 (running)
0x0000 0x045c: pmt_pid 0x0000 Digitenne -- Radio 5 (running)
0x0000 0x045d: pmt_pid 0x0000 Digitenne -- Radio 6 (running)
0x0000 0x045f: pmt_pid 0x0000 Digitenne -- FunX (running)
Network Name 'Digitenne'


All the info i can supply for now ;) If anything else is needed; shoot.
>>
>>
>> regards
>> Antti
>>
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Antti Palosaari]

On 07/01/2013 11:39 PM, Oliver Schinagl wrote:
> On 07/01/13 15:26, Oliver Schinagl wrote:
>> On 01-07-13 15:23, Antti Palosaari wrote:
>>> On 07/01/2013 10:52 AM, Oliver Schinagl wrote:
>>>> On 01-07-13 08:53, Bogdan Oprea wrote:
>>>>> this is a fix for this type of error
>>>>>
>>>>> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error while
>>>>> loading driver (-19)
>>>>> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' successfully
>>>>> deinitialized and disconnected
>>>>>
>>>> This isn't really a fix, I think i mentioned this on the ML ages ago,
>>>
>>> Argh, I just replied that same. Oliver, do you has that same device? Is
>>> it working? Could you tweak to see if I2C readings are working at all?
>> I have the same device, but mine works normally (though I haven't
>> checked for ages), I will try it tonight when I'm at home and don't
>> forget what happens with my current kernel.
>
> Hard to test when it 'just works (tm)' :)

> The bad firmware wories me, no clue where that error is from, using:
> 862604ab3fec0c94f4bf22b4cffd0d89  /lib/firmware/dvb-usb-af9035-02.fw

It means firmware is too short or long what is calculated. I added that 
printing to notify users firmware is broken and could cause problems.


I suspect it is same issue what is with MxL5007t tuners too.
Maybe that kind of fix is needed:
https://patchwork.kernel.org/patch/2418471/

Someone should really find out whether or not these are coming with 
register read operation with REPEATED START of STOP condition. Attach 
hardware sniffer to device tuner I2C bus and look what kind of messages 
there is actually.

regards
Antti

-- 
http://palosaari.fi/

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Oliver Schinagl]

On 07/01/13 22:51, Antti Palosaari wrote:
> On 07/01/2013 11:39 PM, Oliver Schinagl wrote:
>> On 07/01/13 15:26, Oliver Schinagl wrote:
>>> On 01-07-13 15:23, Antti Palosaari wrote:
>>>> On 07/01/2013 10:52 AM, Oliver Schinagl wrote:
>>>>> On 01-07-13 08:53, Bogdan Oprea wrote:
>>>>>> this is a fix for this type of error
>>>>>>
>>>>>> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error while
>>>>>> loading driver (-19)
>>>>>> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' successfully
>>>>>> deinitialized and disconnected
>>>>>>
>>>>> This isn't really a fix, I think i mentioned this on the ML ages ago,
>>>>
>>>> Argh, I just replied that same. Oliver, do you has that same device? Is
>>>> it working? Could you tweak to see if I2C readings are working at all?
>>> I have the same device, but mine works normally (though I haven't
>>> checked for ages), I will try it tonight when I'm at home and don't
>>> forget what happens with my current kernel.
>>
>> Hard to test when it 'just works (tm)' :)
>
>> The bad firmware wories me, no clue where that error is from, using:
>> 862604ab3fec0c94f4bf22b4cffd0d89  /lib/firmware/dvb-usb-af9035-02.fw
>
> It means firmware is too short or long what is calculated. I added that
> printing to notify users firmware is broken and could cause problems.
Ah, good call, it did get me to re-download it. no clue why it was 
broken all of a sudden.
>
>
> I suspect it is same issue what is with MxL5007t tuners too.
> Maybe that kind of fix is needed:
> https://patchwork.kernel.org/patch/2418471/
>
> Someone should really find out whether or not these are coming with
> register read operation with REPEATED START of STOP condition. Attach
> hardware sniffer to device tuner I2C bus and look what kind of messages
> there is actually.
Well mine works fine, so hard to say. IF you have a buspirate you should 
be able to intercept the i2c bus ON the device though :) Good luck 
Bogdan, I wish I could help here, but lack the broken hardware.

>
> regards
> Antti
>

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Antti Palosaari]

On 07/02/2013 12:03 AM, Oliver Schinagl wrote:
> On 07/01/13 22:51, Antti Palosaari wrote:
>> On 07/01/2013 11:39 PM, Oliver Schinagl wrote:
>>> On 07/01/13 15:26, Oliver Schinagl wrote:
>>>> On 01-07-13 15:23, Antti Palosaari wrote:
>>>>> On 07/01/2013 10:52 AM, Oliver Schinagl wrote:
>>>>>> On 01-07-13 08:53, Bogdan Oprea wrote:
>>>>>>> this is a fix for this type of error
>>>>>>>
>>>>>>> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error
>>>>>>> while
>>>>>>> loading driver (-19)
>>>>>>> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus'
>>>>>>> successfully
>>>>>>> deinitialized and disconnected
>>>>>>>
>>>>>> This isn't really a fix, I think i mentioned this on the ML ages ago,
>>>>>
>>>>> Argh, I just replied that same. Oliver, do you has that same
>>>>> device? Is
>>>>> it working? Could you tweak to see if I2C readings are working at all?
>>>> I have the same device, but mine works normally (though I haven't
>>>> checked for ages), I will try it tonight when I'm at home and don't
>>>> forget what happens with my current kernel.
>>>
>>> Hard to test when it 'just works (tm)' :)
>>
>>> The bad firmware wories me, no clue where that error is from, using:
>>> 862604ab3fec0c94f4bf22b4cffd0d89  /lib/firmware/dvb-usb-af9035-02.fw
>>
>> It means firmware is too short or long what is calculated. I added that
>> printing to notify users firmware is broken and could cause problems.
> Ah, good call, it did get me to re-download it. no clue why it was
> broken all of a sudden.
>>
>>
>> I suspect it is same issue what is with MxL5007t tuners too.
>> Maybe that kind of fix is needed:
>> https://patchwork.kernel.org/patch/2418471/
>>
>> Someone should really find out whether or not these are coming with
>> register read operation with REPEATED START of STOP condition. Attach
>> hardware sniffer to device tuner I2C bus and look what kind of messages
>> there is actually.
> Well mine works fine, so hard to say. IF you have a buspirate you should
> be able to intercept the i2c bus ON the device though :) Good luck
> Bogdan, I wish I could help here, but lack the broken hardware.

I have one AF9035 + FC0012 device having similar problems. Unfortunately 
I wasn't able to detect I2C bus to take capture using Bus Pirate.

There seems to be two revisions of AF9035 chips, AF9035A and AF9035B. I 
suspect it is newer B version which has these problems. I also visually 
compared to A and B versions and I suspect pinout is different.

Could you take USB sniffs from that device? Just install sniffer (like 
SniffUSB), tune to channel and stop immediately when there is picture. 
FC2580 driver does some register reads, so it should be possible to see 
what is correct I2C access format by looking sniffs.

Here is few good pictures from my problematic AF9035B + FC0012 device. 
If someone could say which are FC0012 I2C pins, I could use Pirate to 
check (as that device has same problem).
http://blog.palosaari.fi/2013/05/naked-hardware-8-cabletech-urz0185.html

regards
Antti

-- 
http://palosaari.fi/

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Oliver Schinagl]

On 02-07-13 00:37, Antti Palosaari wrote:
> On 07/02/2013 12:03 AM, Oliver Schinagl wrote:
>> On 07/01/13 22:51, Antti Palosaari wrote:
>>> On 07/01/2013 11:39 PM, Oliver Schinagl wrote:
>>>> On 07/01/13 15:26, Oliver Schinagl wrote:
>>>>> On 01-07-13 15:23, Antti Palosaari wrote:
>>>>>> On 07/01/2013 10:52 AM, Oliver Schinagl wrote:
>>>>>>> On 01-07-13 08:53, Bogdan Oprea wrote:
>>>>>>>> this is a fix for this type of error
>>>>>>>>
>>>>>>>> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error
>>>>>>>> while
>>>>>>>> loading driver (-19)
>>>>>>>> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus'
>>>>>>>> successfully
>>>>>>>> deinitialized and disconnected
>>>>>>>>
>>>>>>> This isn't really a fix, I think i mentioned this on the ML ages
>>>>>>> ago,
>>>>>>
>>>>>> Argh, I just replied that same. Oliver, do you has that same
>>>>>> device? Is
>>>>>> it working? Could you tweak to see if I2C readings are working at
>>>>>> all?
>>>>> I have the same device, but mine works normally (though I haven't
>>>>> checked for ages), I will try it tonight when I'm at home and don't
>>>>> forget what happens with my current kernel.
>>>>
>>>> Hard to test when it 'just works (tm)' :)
>>>
>>>> The bad firmware wories me, no clue where that error is from, using:
>>>> 862604ab3fec0c94f4bf22b4cffd0d89  /lib/firmware/dvb-usb-af9035-02.fw
>>>
>>> It means firmware is too short or long what is calculated. I added that
>>> printing to notify users firmware is broken and could cause problems.
>> Ah, good call, it did get me to re-download it. no clue why it was
>> broken all of a sudden.
>>>
>>>
>>> I suspect it is same issue what is with MxL5007t tuners too.
>>> Maybe that kind of fix is needed:
>>> https://patchwork.kernel.org/patch/2418471/
>>>
>>> Someone should really find out whether or not these are coming with
>>> register read operation with REPEATED START of STOP condition. Attach
>>> hardware sniffer to device tuner I2C bus and look what kind of messages
>>> there is actually.
>> Well mine works fine, so hard to say. IF you have a buspirate you should
>> be able to intercept the i2c bus ON the device though :) Good luck
>> Bogdan, I wish I could help here, but lack the broken hardware.
>
> I have one AF9035 + FC0012 device having similar problems. Unfortunately
> I wasn't able to detect I2C bus to take capture using Bus Pirate.
Actually, I have the af9035b (see the picture i uploaded to the wiki)
>
> There seems to be two revisions of AF9035 chips, AF9035A and AF9035B. I
> suspect it is newer B version which has these problems. I also visually
> compared to A and B versions and I suspect pinout is different.
>
> Could you take USB sniffs from that device? Just install sniffer (like
> SniffUSB), tune to channel and stop immediately when there is picture.
> FC2580 driver does some register reads, so it should be possible to see
> what is correct I2C access format by looking sniffs.
Of my working version? I can try, i'll see if I have time to work with 
sniffusb, but if I load the driver from linux, won't we already know 
whats on the USB bus? If you speak of windows, I don't have that.
>
> Here is few good pictures from my problematic AF9035B + FC0012 device.
> If someone could say which are FC0012 I2C pins, I could use Pirate to
> check (as that device has same problem).
> http://blog.palosaari.fi/2013/05/naked-hardware-8-cabletech-urz0185.html
>
> regards
> Antti
>

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Antti Palosaari]

On 07/02/2013 10:04 AM, Oliver Schinagl wrote:
> On 02-07-13 00:37, Antti Palosaari wrote:
>> On 07/02/2013 12:03 AM, Oliver Schinagl wrote:
>>> On 07/01/13 22:51, Antti Palosaari wrote:
>>>> On 07/01/2013 11:39 PM, Oliver Schinagl wrote:
>>>>> On 07/01/13 15:26, Oliver Schinagl wrote:
>>>>>> On 01-07-13 15:23, Antti Palosaari wrote:
>>>>>>> On 07/01/2013 10:52 AM, Oliver Schinagl wrote:
>>>>>>>> On 01-07-13 08:53, Bogdan Oprea wrote:
>>>>>>>>> this is a fix for this type of error
>>>>>>>>>
>>>>>>>>> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error
>>>>>>>>> while
>>>>>>>>> loading driver (-19)
>>>>>>>>> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus'
>>>>>>>>> successfully
>>>>>>>>> deinitialized and disconnected
>>>>>>>>>
>>>>>>>> This isn't really a fix, I think i mentioned this on the ML ages
>>>>>>>> ago,
>>>>>>>
>>>>>>> Argh, I just replied that same. Oliver, do you has that same
>>>>>>> device? Is
>>>>>>> it working? Could you tweak to see if I2C readings are working at
>>>>>>> all?
>>>>>> I have the same device, but mine works normally (though I haven't
>>>>>> checked for ages), I will try it tonight when I'm at home and don't
>>>>>> forget what happens with my current kernel.
>>>>>
>>>>> Hard to test when it 'just works (tm)' :)
>>>>
>>>>> The bad firmware wories me, no clue where that error is from, using:
>>>>> 862604ab3fec0c94f4bf22b4cffd0d89  /lib/firmware/dvb-usb-af9035-02.fw
>>>>
>>>> It means firmware is too short or long what is calculated. I added that
>>>> printing to notify users firmware is broken and could cause problems.
>>> Ah, good call, it did get me to re-download it. no clue why it was
>>> broken all of a sudden.
>>>>
>>>>
>>>> I suspect it is same issue what is with MxL5007t tuners too.
>>>> Maybe that kind of fix is needed:
>>>> https://patchwork.kernel.org/patch/2418471/
>>>>
>>>> Someone should really find out whether or not these are coming with
>>>> register read operation with REPEATED START of STOP condition. Attach
>>>> hardware sniffer to device tuner I2C bus and look what kind of messages
>>>> there is actually.
>>> Well mine works fine, so hard to say. IF you have a buspirate you should
>>> be able to intercept the i2c bus ON the device though :) Good luck
>>> Bogdan, I wish I could help here, but lack the broken hardware.
>>
>> I have one AF9035 + FC0012 device having similar problems. Unfortunately
>> I wasn't able to detect I2C bus to take capture using Bus Pirate.
> Actually, I have the af9035b (see the picture i uploaded to the wiki)
>>
>> There seems to be two revisions of AF9035 chips, AF9035A and AF9035B. I
>> suspect it is newer B version which has these problems. I also visually
>> compared to A and B versions and I suspect pinout is different.
>>
>> Could you take USB sniffs from that device? Just install sniffer (like
>> SniffUSB), tune to channel and stop immediately when there is picture.
>> FC2580 driver does some register reads, so it should be possible to see
>> what is correct I2C access format by looking sniffs.

> Of my working version? I can try, i'll see if I have time to work with
> sniffusb, but if I load the driver from linux, won't we already know
> whats on the USB bus? If you speak of windows, I don't have that.

I wonder if Bogdan could took the sniffs as his device has the problems.

My FC0012 sniffs are useless as FC0012 windows does not any register reads.

Your sniffs could be also handy, better than nothing, even likely 
produce just same logs as Bogdan (I suspect it is issue AF9035A vs AF9035B).

>> Here is few good pictures from my problematic AF9035B + FC0012 device.
>> If someone could say which are FC0012 I2C pins, I could use Pirate to
>> check (as that device has same problem).
>> http://blog.palosaari.fi/2013/05/naked-hardware-8-cabletech-urz0185.html
>>
>> regards
>> Antti
>>
>

Antti

-- 
http://palosaari.fi/

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Oliver Schinagl]

On 07/02/13 21:55, Antti Palosaari wrote:
> On 07/02/2013 10:04 AM, Oliver Schinagl wrote:
>> On 02-07-13 00:37, Antti Palosaari wrote:
>>> On 07/02/2013 12:03 AM, Oliver Schinagl wrote:
>>>> On 07/01/13 22:51, Antti Palosaari wrote:
>>>>> On 07/01/2013 11:39 PM, Oliver Schinagl wrote:
>>>>>> On 07/01/13 15:26, Oliver Schinagl wrote:
>>>>>>> On 01-07-13 15:23, Antti Palosaari wrote:
>>>>>>>> On 07/01/2013 10:52 AM, Oliver Schinagl wrote:
>>>>>>>>> On 01-07-13 08:53, Bogdan Oprea wrote:
>>>>>>>>>> this is a fix for this type of error
>>>>>>>>>>
>>>>>>>>>> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error
>>>>>>>>>> while
>>>>>>>>>> loading driver (-19)
>>>>>>>>>> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus'
>>>>>>>>>> successfully
>>>>>>>>>> deinitialized and disconnected
>>>>>>>>>>
>>>>>>>>> This isn't really a fix, I think i mentioned this on the ML ages
>>>>>>>>> ago,
>>>>>>>>
>>>>>>>> Argh, I just replied that same. Oliver, do you has that same
>>>>>>>> device? Is
>>>>>>>> it working? Could you tweak to see if I2C readings are working at
>>>>>>>> all?
>>>>>>> I have the same device, but mine works normally (though I haven't
>>>>>>> checked for ages), I will try it tonight when I'm at home and don't
>>>>>>> forget what happens with my current kernel.
>>>>>>
>>>>>> Hard to test when it 'just works (tm)' :)
>>>>>
>>>>>> The bad firmware wories me, no clue where that error is from, using:
>>>>>> 862604ab3fec0c94f4bf22b4cffd0d89  /lib/firmware/dvb-usb-af9035-02.fw
>>>>>
>>>>> It means firmware is too short or long what is calculated. I added that
>>>>> printing to notify users firmware is broken and could cause problems.
>>>> Ah, good call, it did get me to re-download it. no clue why it was
>>>> broken all of a sudden.
>>>>>
>>>>>
>>>>> I suspect it is same issue what is with MxL5007t tuners too.
>>>>> Maybe that kind of fix is needed:
>>>>> https://patchwork.kernel.org/patch/2418471/
>>>>>
>>>>> Someone should really find out whether or not these are coming with
>>>>> register read operation with REPEATED START of STOP condition. Attach
>>>>> hardware sniffer to device tuner I2C bus and look what kind of messages
>>>>> there is actually.
>>>> Well mine works fine, so hard to say. IF you have a buspirate you should
>>>> be able to intercept the i2c bus ON the device though :) Good luck
>>>> Bogdan, I wish I could help here, but lack the broken hardware.
>>>
>>> I have one AF9035 + FC0012 device having similar problems. Unfortunately
>>> I wasn't able to detect I2C bus to take capture using Bus Pirate.
>> Actually, I have the af9035b (see the picture i uploaded to the wiki)
>>>
>>> There seems to be two revisions of AF9035 chips, AF9035A and AF9035B. I
>>> suspect it is newer B version which has these problems. I also visually
>>> compared to A and B versions and I suspect pinout is different.
>>>
>>> Could you take USB sniffs from that device? Just install sniffer (like
>>> SniffUSB), tune to channel and stop immediately when there is picture.
>>> FC2580 driver does some register reads, so it should be possible to see
>>> what is correct I2C access format by looking sniffs.
>
>> Of my working version? I can try, i'll see if I have time to work with
>> sniffusb, but if I load the driver from linux, won't we already know
>> whats on the USB bus? If you speak of windows, I don't have that.
>
> I wonder if Bogdan could took the sniffs as his device has the problems.
>
> My FC0012 sniffs are useless as FC0012 windows does not any register reads.
>
> Your sniffs could be also handy, better than nothing, even likely
> produce just same logs as Bogdan (I suspect it is issue AF9035A vs AF9035B).
>
>>> Here is few good pictures from my problematic AF9035B + FC0012 device.
>>> If someone could say which are FC0012 I2C pins, I could use Pirate to
>>> check (as that device has same problem).
I don't know what the FC0012 I2C pins are, but don't we know where they 
are on the AF9035B?

I know on the FCI 2580 pin 18 is SCLK, Pin 19 is SDATA and pin 20 is VDD.

My bad camera skills made the image blurry and I don't have a microscope 
(scanner would have been cool though I suppose) but the I2C lines appear 
to enter the af9035b on the 'left' side, if you look at the numbers on 
the far left, '131' and head towards the chip, you see two via's comming 
up and going slightly diagonally up towards the chip. That's the I2C bus 
if i'm not mistaken. SCLK is the top one of the two, SDATA the lower 
one. I know it's hard to see in the image, but still quite possible :)

http://www.linuxtv.org/wiki/images/1/1b/Asus_U3100_Mini_plus_DVB-T_03.JPG

>>> http://blog.palosaari.fi/2013/05/naked-hardware-8-cabletech-urz0185.html
>>>
>>> regards
>>> Antti
>>>
>>
>
> Antti
>

Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)

[Bogdan Oprea]

i don't know how to "sniff" the usb port. if you want i can give you root access to the machine with the device plugged into it. it's a raspberry pi with raspbian wheezy.



________________________________
From: Antti Palosaari <crope@iki.fi>
To: Oliver Schinagl <oliver+list@schinagl.nl> 
Cc: Bogdan Oprea <bogdaninedit@yahoo.com>; "linux-media@vger.kernel.org" <linux-media@vger.kernel.org> 
Sent: Tuesday, July 2, 2013 10:55 PM
Subject: Re: drivers:media:tuners:fc2580c fix for Asus U3100Mini Plus error while loading driver (-19)


On 07/02/2013 10:04 AM, Oliver Schinagl wrote:
> On 02-07-13 00:37, Antti Palosaari wrote:
>> On 07/02/2013 12:03 AM, Oliver Schinagl wrote:
>>> On 07/01/13 22:51, Antti Palosaari wrote:
>>>> On 07/01/2013 11:39 PM, Oliver Schinagl wrote:
>>>>> On 07/01/13 15:26, Oliver Schinagl wrote:
>>>>>> On 01-07-13 15:23, Antti Palosaari wrote:
>>>>>>> On 07/01/2013 10:52 AM, Oliver Schinagl wrote:
>>>>>>>> On 01-07-13 08:53, Bogdan Oprea wrote:
>>>>>>>>> this is a fix for this type of error
>>>>>>>>>
>>>>>>>>> [18384.579235] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus' error
>>>>>>>>> while
>>>>>>>>> loading driver (-19)
>>>>>>>>> [18384.580621] usb 6-5: dvb_usb_v2: 'Asus U3100Mini Plus'
>>>>>>>>> successfully
>>>>>>>>> deinitialized and disconnected
>>>>>>>>>
>>>>>>>> This isn't really a fix, I think i mentioned this on the ML ages
>>>>>>>> ago,
>>>>>>>
>>>>>>> Argh, I just replied that same. Oliver, do you has that same
>>>>>>> device? Is
>>>>>>> it working? Could you tweak to see if I2C readings are working at
>>>>>>> all?
>>>>>> I have the same device, but mine works normally (though I haven't
>>>>>> checked for ages), I will try it tonight when I'm at home and don't
>>>>>> forget what happens with my current kernel.
>>>>>
>>>>> Hard to test when it 'just works (tm)' :)
>>>>
>>>>> The bad firmware wories me, no clue where that error is from, using:
>>>>> 862604ab3fec0c94f4bf22b4cffd0d89  /lib/firmware/dvb-usb-af9035-02.fw
>>>>
>>>> It means firmware is too short or long what is calculated. I added that
>>>> printing to notify users firmware is broken and could cause problems.
>>> Ah, good call, it did get me to re-download it. no clue why it was
>>> broken all of a sudden.
>>>>
>>>>
>>>> I suspect it is same issue what is with MxL5007t tuners too.
>>>> Maybe that kind of fix is needed:
>>>> https://patchwork.kernel.org/patch/2418471/
>>>>
>>>> Someone should really find out whether or not these are coming with
>>>> register read operation with REPEATED START of STOP condition. Attach
>>>> hardware sniffer to device tuner I2C bus and look what kind of messages
>>>> there is actually.
>>> Well mine works fine, so hard to say. IF you have a buspirate you should
>>> be able to intercept the i2c bus ON the device though :) Good luck
>>> Bogdan, I wish I could help here, but lack the broken hardware.
>>
>> I have one AF9035 + FC0012 device having similar problems. Unfortunately
>> I wasn't able to detect I2C bus to take capture using Bus Pirate.
> Actually, I have the af9035b (see the picture i uploaded to the wiki)
>>
>> There seems to be two revisions of AF9035 chips, AF9035A and AF9035B. I
>> suspect it is newer B version which has these problems. I also visually
>> compared to A and B versions and I suspect pinout is different.
>>
>> Could you take USB sniffs from that device? Just install sniffer (like
>> SniffUSB), tune to channel and stop immediately when there is picture.
>> FC2580 driver does some register reads, so it should be possible to see
>> what is correct I2C access format by looking sniffs.

> Of my working version? I can try, i'll see if I have time to work with
> sniffusb, but if I load the driver from linux, won't we already know
> whats on the USB bus? If you speak of windows, I don't have that.

I wonder if Bogdan could took the sniffs as his device has the problems.

My FC0012 sniffs are useless as FC0012 windows does not any register reads.

Your sniffs could be also handy, better than nothing, even likely 
produce just same logs as Bogdan (I suspect it is issue AF9035A vs AF9035B).

>> Here is few good pictures from my problematic AF9035B + FC0012 device.
>> If someone could say which are FC0012 I2C pins, I could use Pirate to
>> check (as that device has same problem).
>> http://blog.palosaari.fi/2013/05/naked-hardware-8-cabletech-urz0185.html
>>
>> regards
>> Antti
>>
>

Antti

-- 
http://palosaari.fi/