Created attachment 197641 [details] Messages during resume with built-in firmware After normal boot DVB-T USB is working with vlc After resume from hibernate vlc cannot connect to DVB-T stick. Led shows connection, but color does not change to green during activation. Disconnecting the stick and connecting it again does not help. Problem occurred before, seemed to be solved (Bug 94816). But now it is there again. Workaround for me was: Building my own kernel with DVB-T firmware built-in. But this is only working up to kernel 4.3.X Messages from resume: See attachment.
On Thu, Dec 17, 2015 at 05:31:31PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=109521 > > Bug ID: 109521 > Summary: kernel 4.4-RCx does not connect DVB-T USB Stick during > resume from hibernate Please send to the linux-media@vger.kernel.org mailing list.
On Date: Thu, 17 Dec 2015 19:35:56 +0100 this bug was sent to linux-media@vger.kernel.org, and it entered the thread index. Since then nobody picked it up. As kernel 4.3.5 seems to come to EOL, I am forced to go back to kernel 4.1.18 to have a working kernel for my issue. Could it be usefully, to mark this bug as a regression, which in fact it is , to get any progress into this case? Or is there any other way to deal with this problem?
Yesterday I wrote this mail to linux-media@vger.kernel.org: " At 2015-12-17 I sent this to you: > https://bugzilla.kernel.org/show_bug.cgi?id=109521 > > Bug ID: 109521 > Summary: kernel 4.4-RCx does not connect DVB-T USB Stick during > resume from hibernate This is a regression, because the earlier desktop-kernel did not have this bug. It came up with default-kernel. Is there any chance for me to get it fixed, or can I forget it? " Now there are two threads with the same topic. One named "dvb-t" ( 2015-12-17 ) and another named "Thread dvb-t" ( 21 Jun 2016). And crope from linux-media added himself to the CC list. I changed "REGRESSION" to "yes" and added tiwai to the CC list. What could happen now? Or can I do anything to get this started? On Linux Media thread index I can see a lot of activities. As I have no other idea, I would like to repeat my question from above: Is there any chance for me to get it fixed, or can I forget it?
Does 4.1.18 work without compiling in the firmware?
Yes. I tested from http://download.opensuse.org/repositories/home:/tiwai:/kernel:/3.18/standard/ both versions, the desktop and the default one. Both are working. Then I tested from http://download.opensuse.org/repositories/home:/tiwai:/kernel:/3.19/standard/ both versions and both are not working. (All my self-compiled kernel-versions seem to be developed from kernel-desktop 3.18, so I got the wrong guess, that it had to do with the desktop-version.)
Created attachment 245191 [details] Parts os Messages
Now it went from bad to worse. I tried Linux version 4.9.0-rc5-1.g8930e43-default (geeko@buildhost) (gcc version 6.2.1 20160830 [gcc-6-branch revision 239856] (SUSE Linux). The result is: After normal start: DVB-USB is working. After resume from hibernate: DVB-USB is completely not working Main error message is: 2016-11-20T11:32:58.067888+01:00 noname kernel: [ 141.664466] usb 6-4: dtv_property_legacy_params_sync: doesn't know how to handle a DVBv3 call to delivery system 0 and 2016-11-20T11:34:30.360114+01:00 noname kernel: [ 172.957415] dvb-usb: could not stop the USB controller CPU. 2016-11-20T11:34:30.360116+01:00 noname kernel: [ 172.957419] dvb-usb: error while transferring firmware (transferred size: -11, block size: 16) 2016-11-20T11:34:30.360118+01:00 noname kernel: [ 172.957421] dvb-usb: firmware download failed at 21 with -22 Details at attachment 245191 [details] (part of messages)
Additional comment to comment # 7: After reboot with this kernel DBV-USB is not working anymore. Self compiled Kernel from 4.9.0-rc5.tar.xz shows same problem.
Self compiled Kernel from 4.10-rc1.tar.xz shows same problem. My "WideView WT-220U PenType Receiver (Typhoon/Freecom)" is dead in this system. My current kernel 4.8.xx will reache EOL very soon. So I have to go back to kernel 4.4.xx in order to get a working kernel for this issue again.
Hibernating-problem solved with kernel 4.11-rc2