2014-05-02, 09:39
Let's fix the problem with exactly _one_ tuner first. I personally think, that this is a kernel regression (to be more exact: A side effect, a change that produces some race). So it's worth looking for changes to the USB subsystem and to the relevant driver. Therefore I'd need a kernel dmesg with the working version and with the non working version with the debugging options for both USB and the driver turned on.
I still don't get the point, that Ubuntu Users with "old kernel" - the one matching this old OE release keep having that problem, that fact makes me quite clueless. So let's gather the kernel debug logs first.
Edit: Those are module parameters for the em28xx module, all of them are worth a try.
I still don't get the point, that Ubuntu Users with "old kernel" - the one matching this old OE release keep having that problem, that fact makes me quite clueless. So let's gather the kernel debug logs first.
Edit: Those are module parameters for the em28xx module, all of them are worth a try.
Quote:parm: card:card type (array of int)
parm: usb_xfer_mode:USB transfer mode for frame data (-1 = auto, 0 = prefer isoc, 1 = prefer bulk) (int) <- looks interesting (try those also, plese)
parm: i2c_debug:i2c debug message level (1: normal debug, 2: show I2C transfers) (int) <- increase those
parm: core_debug:enable debug messages [core] (int) <- that one
parm: reg_debug:enable debug messages [URB reg] (int) <- that one