random "no frontend was attached"
I have a DVB USB device which identifies as:
# lsusb Bus 001 Device 006: ID 04ca:f001 Lite-On Technology Corp.
Randomly, upon machine bootup, it is not detected properly ("no frontend was attached"):
usb 1-6: new high speed USB device using ehci_hcd and address 4 usb 1-6: configuration #1 chosen from 1 choice
dvb-usb: found a 'LITE-ON USB2.0 DVB-T Tuner' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (LITE-ON USB2.0 DVB-T Tuner)
dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner'
input: IR-receiver inside an USB DVB receiver as /class/input/input6
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: LITE-ON USB2.0 DVB-T Tuner successfully initialized and connected.
As a result, using DVB is impossible until I plug the device out and plug it in again.
This is the only solution to bring it back to life - if I remove DVB modules and insert them again, I get:
dvb-usb: bulk message failed: -22 (1/2)
dvb-usb: bulk message failed: -22 (1/-150651080)
dvb-usb: bulk message failed: -22 (1/662)
dvb-usb: bulk message failed: -22 (1/1024)
dvb-usb: bulk message failed: -22 (1/2)
Are there any "better" solutions to that, other then re-inserting the USB device? If not, what could be the cause of it?
I use Linux kernel 2.6.28.
Signature · 7 lines
Tomasz Chmielewski http://wpkg.org _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 19 lines · Tomasz Chmielewski
I have a DVB USB device which identifies as:
# lsusb Bus 001 Device 006: ID 04ca:f001 Lite-On Technology Corp.Randomly, upon machine bootup, it is not detected properly ("no frontend was attached"):
usb 1-6: new high speed USB device using
ehci_hcdand address 4 usb 1-6: configuration #1 chosen from 1 choice
dvb-usb: found a 'LITE-ON USB2.0 DVB-T Tuner' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (LITE-ON USB2.0 DVB-T Tuner)
dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner'
input: IR-receiver inside an USB DVB receiver as /class/input/input6
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: LITE-ON USB2.0 DVB-T Tuner successfully initialized and connected.
Quoted 2 lines
As a result, using DVB is impossible until I plug the device out and plug it in again.
Does not work here.
Quoted 11 lines
This is the only solution to bring it back to life - if I remove DVB modules and insert them again, I get:
dvb-usb: bulk message failed: -22 (1/2)
dvb-usb: bulk message failed: -22 (1/-150651080)
dvb-usb: bulk message failed: -22 (1/662)
dvb-usb: bulk message failed: -22 (1/1024)
dvb-usb: bulk message failed: -22 (1/2)
Quoted 6 lines
Are there any "better" solutions to that, other then re-inserting the USB device? If not, what could be the cause of it?
I use Linux kernel 2.6.28.
http://www.linuxtv.org/pipermail/linux-dvb/2009-January/031165.html
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 13 lines · thomas schorpp
Quoted 13 lines
Randomly, upon machine bootup, it is not detected properly ("no frontend was attached"):
usb 1-6: new high speed USB device using
ehci_hcdand address 4 usb 1-6: configuration #1 chosen from 1 choice
dvb-usb: found a 'LITE-ON USB2.0 DVB-T Tuner' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (LITE-ON USB2.0 DVB-T Tuner)
dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner'
input: IR-receiver inside an USB DVB receiver as /class/input/input6
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: LITE-ON USB2.0 DVB-T Tuner successfully initialized and connected.
Quoted 4 lines
Quoted 2 lines
As a result, using DVB is impossible until I plug the device out and plug it in again.
Does not work here.
It does not work always for me as well. Sometimes, I have to replug the device 2-3-4 times until it's eventually properly detected. Most of the time, it's not detected initially.
Did it work for you properly with earlier kernels?
Signature · 8 lines
Tomasz Chmielewski http://wpkg.org _______________________________________________ linux-dvb users mailing list For V4L/DVB development, please use instead [email protected] [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 8 lines · Tomasz Chmielewski
Quoted 8 lines
Quoted 8 lines
dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner'
input: IR-receiver inside an USB DVB receiver as /class/input/input6
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: LITE-ON USB2.0 DVB-T Tuner successfully initialized and connected.As a result, using DVB is impossible until I plug the device out and plug it in again.
Quoted 7 lines
Quoted 1 line
Does not work here.
It does not work always for me as well. Sometimes, I have to replug the device 2-3-4 times until it's eventually properly detected. Most of the time, it's not detected initially.
Did it work for you properly with earlier kernels?
I noticed that after I do (without device unplugging/replugging):
# rmmod dvb_usb_dibusb_mc dvb_usb_dibusb_common dib3000mc dibx000_common ehci_hcd
# modprobe -a dvb_usb_dibusb_mc dvb_usb_dibusb_common dib3000mc dibx000_common ehci_hcd
it is detected properly _always_.
?
Signature · 11 lines
Tomasz Chmielewski http://wpkg.org _______________________________________________ linux-dvb users mailing list For V4L/DVB development, please use instead [email protected] [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 19 lines · Tomasz Chmielewski
Quoted 6 lines · Tomasz Chmielewski
Quoted 6 lines
Quoted 6 lines
dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner'
input: IR-receiver inside an USB DVB receiver as /class/input/input6
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: LITE-ON USB2.0 DVB-T Tuner successfully initialized and connected.Quoted 8 lines
Quoted 3 lines
Quoted 2 lines
As a result, using DVB is impossible until I plug the device out and plug it in again.
Does not work here.
It does not work always for me as well. Sometimes, I have to replug the device 2-3-4 times until it's eventually properly detected. Most of the time, it's not detected initially.
Did it work for you properly with earlier kernels?
I noticed that after I do (without device unplugging/replugging):
Quoted 9 lines
# rmmod dvb_usb_dibusb_mc dvb_usb_dibusb_common dib3000mc dibx000_common ehci_hcd# modprobe -a dvb_usb_dibusb_mc dvb_usb_dibusb_common dib3000mc dibx000_common ehci_hcdit is detected properly _always_.
?
no.
Y
tom
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 8 lines · thomas schorpp
Quoted 8 lines
Quoted 1 line
Did it work for you properly with earlier kernels?
I noticed that after I do (without device unplugging/replugging):
# rmmod dvb_usb_dibusb_mc dvb_usb_dibusb_common dib3000mc dibx000_common ehci_hcd# modprobe -a dvb_usb_dibusb_mc dvb_usb_dibusb_common dib3000mc dibx000_common ehci_hcd
Quoted 6 lines
Quoted 4 lines
it is detected properly _always_.
?
no.
With what earlier kernels does it for you?
Signature · 8 lines
Tomasz Chmielewski http://wpkg.org _______________________________________________ linux-dvb users mailing list For V4L/DVB development, please use instead [email protected] [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 12 lines · Tomasz Chmielewski
Quoted 10 lines · thomas schorpp
Quoted 10 lines
Quoted 1 line
Did it work for you properly with earlier kernels?
I noticed that after I do (without device unplugging/replugging):
# rmmod dvb_usb_dibusb_mc dvb_usb_dibusb_common dib3000mc dibx000_common ehci_hcd# modprobe -a dvb_usb_dibusb_mc dvb_usb_dibusb_common dib3000mc dibx000_common ehci_hcd
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
it is detected properly _always_.
?
no.
With what earlier kernels does it for you?
irrelevant.
yes for:
tom1:~# modprobe -r dvb_usb_dibusb_mc ehci_hcd tom1:~# modprobe -r uhci_hcd tom1:~# tom1:~# tom1:~# modprobe uhci_hcd tom1:~# tom1:~# dmesg |grep frontend DVB: registering adapter 0 frontend 0 (Philips TDA10021 DVB-C)... DVB: registering adapter 1 frontend 0 (VLSI VES1820 DVB-C)... dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner' dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner' DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)... DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)... DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)... dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner' dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner' DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)... DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)... DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)... DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)... DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)... DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)... DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)... tom1:~# tom1:~# tom1:~#
thanks for pointing the right direction.
try this if it works for cold and warm boot (machine/device), too:
tom1:~# grep hcd /etc/modprobe.d/dvb install ehci-hcd /sbin/modprobe dvb_usb_dibusb_mc; /sbin/modprobe --ignore-install ehci-hcd tom1:~#
y
tom
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 25 lines · thomas schorpp
Quoted 12 lines · Tomasz Chmielewski
Quoted 10 lines · thomas schorpp
Quoted 10 lines
Quoted 1 line
Did it work for you properly with earlier kernels?
I noticed that after I do (without device unplugging/replugging):
# rmmod dvb_usb_dibusb_mc dvb_usb_dibusb_common dib3000mc dibx000_common ehci_hcd# modprobe -a dvb_usb_dibusb_mc dvb_usb_dibusb_common dib3000mc dibx000_common ehci_hcdQuoted 8 lines
Quoted 6 lines
Quoted 4 lines
it is detected properly _always_.
?
no.
With what earlier kernels does it for you?
irrelevant.
Quoted 6 lines
tom1:~# tom1:~# tom1:~# thanks for pointing the right direction. try this if it works for cold and warm boot (machine/device), too:tom1:~# grep hcd /etc/modprobe.d/dvb install ehci-hcd /sbin/modprobe dvb_usb_dibusb_mc; /sbin/modprobe
no.
needed this to get it work after linux cold boot:
tom1:~# cat /etc/modprobe.d/usb install uhci-hcd /sbin/modprobe ehci-hcd; /sbin/modprobe --ignore-install uhci-hcd
tom1:~# cat /etc/modprobe.d/dvb ... install dvb_usb_dibusb_mc /sbin/modprobe --ignore-install dvb_usb_dibusb_mc; \ /sbin/modprobe -r dvb_usb_dibusb_mc ehci_hcd; \ /sbin/modprobe -a --ignore-install dvb_usb_dibusb_mc ehci_hcd # runvdr
but second is ignored by udev and/or modprobe at bootup for some reason,
tom1:~# dmesg |grep frontend DVB: registering adapter 0 frontend 0 (Philips TDA10021 DVB-C)... DVB: registering adapter 1 frontend 0 (VLSI VES1820 DVB-C)... dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner' dvb-usb: no frontend was attached by 'LITE-ON USB2.0 DVB-T Tuner' DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)...
so I need
tom1:~# diff -U3 /usr/sbin/runvdr.dist /usr/sbin/runvdr --- /usr/sbin/runvdr.dist 2008-10-02 00:22:53.000000000 +0200 +++ /usr/sbin/runvdr 2009-01-10 17:52:28.000000000 +0100 @@ -73,6 +73,9 @@
[ -z "$MODULES" ] && load_dvb_modules
+/sbin/modprobe -r dvb_usb_dibusb_mc mt2060
+/sbin/modprobe dvb_usb_dibusb_mc
+
while (true) do
set_permissions
Can You pls confirm this, I won't touch the driver code before, maybe usb-h/w dependant.
y
tom
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 7 lines · thomas schorpp
Quoted 6 lines · thomas schorpp
Quoted 5 lines · Tomasz Chmielewski
Quoted 3 lines · thomas schorpp
Quoted 3 lines
Quoted 1 line
Did it work for you properly with earlier kernels?
I noticed that after I do (without device unplugging/replugging):
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
# rmmod dvb_usb_dibusb_mc dvb_usb_dibusb_common dib3000mc dibx000_common ehci_hcd# modprobe -a dvb_usb_dibusb_mc dvb_usb_dibusb_common dib3000mc dibx000_common ehci_hcdCan You pls confirm this, I won't touch the driver code before, maybe usb-h/w dependant.
I noticed it is probably enough to remove ehci_hcd.
In that case, the device will be re-detected on uhci_hcd (which is USB 1.1). And if you remove uhci_hcd and insert ehci_hcd again, it will be re-detected there.
Signature · 9 lines
Tomasz Chmielewski http://wpkg.org _______________________________________________ linux-dvb users mailing list For V4L/DVB development, please use instead [email protected] [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb