AVerMedia AVerTV DVB-T Volar USB not initialised on startup

[monstermunch]

I have an AVerMedia AVerTV DVB-T Volar USB stick I use for watching TV under Linux (works flawlessly by the way except for this problem!). About 50% of the time, when I boot Ubuntu, the device is not detected. I can tell when this happens because Kaffeine cannot see the device, the blue light on the device is turned off (it turns on when loaded). The only relevant thing I can see in dmesg when this happens is:

 [ 42.890201] usb 2-1: new high speed USB device using ehci_hcd and address 2
 [ 57.982999] usb 2-1: device descriptor read/64, error -110
 [ 73.179674] usb 2-1: device descriptor read/64, error -110

When this happens, unplugging and plugging in the device fixes it. dmesg then contains this:

 [ 324.949916] usb 2-1: new high speed USB device using ehci_hcd and address 7
 [ 325.082713] usb 2-1: configuration #1 chosen from 1 choice
 [ 325.181890] dvb-usb: found a 'AVerMedia AVerTV DVB-T Volar' in cold state, will try to load a firmware
 [ 325.218123] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw'
 [ 325.900704] dvb-usb: found a 'AVerMedia AVerTV DVB-T Volar' in warm state.
 [ 325.900993] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
 [ 326.654729] dvb-usb: AVerMedia AVerTV DVB-T Volar successfully initialized and connected.
 [ 326.654762] usbcore: registered new interface driver dvb_usb_dib0700

The strange thing is, sometimes Ubuntu recognises the USB stick when I turn on the machine and other times I need to use this unplug/plugin trick after booting.

[monstermunch (monstermunch)]

Does anyone have any idea what I can try? It's a really irritating problem to have to go through this routine of plugging in/out and restarting applications most days.

[Nathan O'Sullivan (nathan-mammoth)]

I dont have this tuner but have been considering about buying one; while googling for potential problems I found one person who said this happened to them if ohci_hcd loaded before ehci_hcd (or the other way round?). Check your dmesg to see what order those two drivers are coming up in

[monstermunch (monstermunch)]

This issue still happens in Hardy.

How can I change the load order of o/ehci?

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[kernel-janitor (kernel-janitor)]

Hi monstermunch,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue? Can you try with the latest development release of Ubuntu? (ISO CD images are available from http://cdimage.ubuntu.com/releases/)

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 186129

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]