Re: Report of anomally in AVerMedia AVerTV Volar HD/PRO (A835) firmware

2013-03-01 Thread Mauro Carvalho Chehab
Hi Cristiano,

Em Fri, 1 Mar 2013 19:47:19 +
H. Cristiano Alves Machado heberto.mach...@gmail.com escreveu:

 Hello.
 
 I believe that this might already have been reported...
 
 
 The problem can only be solved by physically removing the usb-dvb
 plug, and plugging it back again... :(

Well, this driver doesn't use dvb-usb stack anymore, it got ported to
dvb-usb-v2. I suggest you to test it again on kernel 3.8.

Btw, you're also reporting the issue to the wrong ML... linux-dvb ML
was deprecated a long time ago ;)

Regards,
Mauro
 
 Below are the dmesg logs (both before dvb software reported error, and
 after, when the same software did not complain).
 
 I am currently using vlc software to access dvb-t card (Avermedia
 mentioned in the subject).
 
 Several times in the last few days/weeks, when I start the pc from off
 state (normal boot), the dvb card will fail to be accessed.
 
 Iam currently running a 'Linux 3.5.0-18-generic #29~precise1-Ubuntu
 SMP  x86_64 GNU/Linux' setup, and VLC media player 2.0.6 Twoflower
 (revision 2.0.5+git20130228+r534) from the daily stable 'repo'.
 
 Maybe the critical points could lie in the fact that after plugging
 the device  again it successfully loads the firmware. While during
 'boot' time it can only register it
 
 So, here are the 'dvb' dmesg greps, and at the end the cut down
 differences between the two moments.
 
 [   13.154237] dvb-usb: found a 'AVerMedia AVerTV Volar HD/PRO (A835)'
 in warm state.
 [   13.154325] dvb-usb: will pass the complete MPEG2 transport stream
 to the software demuxer.
 [   13.154774] DVB: registering new adapter (AVerMedia AVerTV Volar
 HD/PRO (A835))
 [   13.165623] dvb-usb: MAC address: 00:00:00:00:00:00
 [   13.175623] dvb-usb: no frontend was attached by 'AVerMedia AVerTV
 Volar HD/PRO (A835)'
 [   13.175761] input: IR-receiver inside an USB DVB receiver as
 /devices/pci:00/:00:1d.7/usb1/1-3/rc/rc0/input2
 [   13.175822] rc0: IR-receiver inside an USB DVB receiver as
 /devices/pci:00/:00:1d.7/usb1/1-3/rc/rc0
 [   13.175824] dvb-usb: schedule remote query interval to 250 msecs.
 [   13.175826] dvb-usb: AVerMedia AVerTV Volar HD/PRO (A835)
 successfully initialized and connected.
 [   13.194629] usbcore: registered new interface driver dvb_usb_af9035
 [17246.232556] dvb-usb: AVerMedia AVerTV Volar HD/PRO (A835)
 successfully deinitialized and disconnected.
 [17255.906733] dvb-usb: found a 'AVerMedia AVerTV Volar HD/PRO (A835)'
 in cold state, will try to load a firmware
 [17255.917426] dvb-usb: downloading firmware from file 'dvb-usb-af9035-02.fw'
 [17256.222632] dvb-usb: found a 'AVerMedia AVerTV Volar HD/PRO (A835)'
 in warm state.
 [17256.222739] dvb-usb: will pass the complete MPEG2 transport stream
 to the software demuxer.
 [17256.223030] DVB: registering new adapter (AVerMedia AVerTV Volar
 HD/PRO (A835))
 [17256.225735] dvb-usb: MAC address: 00:00:00:00:00:00
 [17256.227866] DVB: registering adapter 0 frontend 0 (Afatech AF9033 
 (DVB-T))...
 [17256.272866] input: IR-receiver inside an USB DVB receiver as
 /devices/pci:00/:00:1d.7/usb1/1-3/rc/rc1/input12
 [17256.272938] rc1: IR-receiver inside an USB DVB receiver as
 /devices/pci:00/:00:1d.7/usb1/1-3/rc/rc1
 [17256.272941] dvb-usb: schedule remote query interval to 250 msecs.
 [17256.272944] dvb-usb: AVerMedia AVerTV Volar HD/PRO (A835)
 successfully initialized and connected.
 
 Differences between the first section and the second:
 
 0a1,3
   dvb-usb: AVerMedia AVerTV Volar HD/PRO (A835) successfully deinitialized 
  and disconnected.
   dvb-usb: found a 'AVerMedia AVerTV Volar HD/PRO (A835)' in cold state, 
  will try to load a firmware
   dvb-usb: downloading firmware from file 'dvb-usb-af9035-02.fw'
 5,7c8,10
   dvb-usb: no frontend was attached by 'AVerMedia AVerTV Volar HD/PRO (A835)'
   input: IR-receiver inside an USB DVB receiver as
 /devices/pci:00/:00:1d.7/usb1/1-3/rc/rc0/input2
   rc0: IR-receiver inside an USB DVB receiver as
 /devices/pci:00/:00:1d.7/usb1/1-3/rc/rc0
 ---
   DVB: registering adapter 0 frontend 0 (Afatech AF9033 (DVB-T))...
   input: IR-receiver inside an USB DVB receiver as 
  /devices/pci:00/:00:1d.7/usb1/1-3/rc/rc1/input12
   rc1: IR-receiver inside an USB DVB receiver as 
  /devices/pci:00/:00:1d.7/usb1/1-3/rc/rc1
 10d12
   usbcore: registered new interface driver dvb_usb_af9035
 
 
 Hope there may be some solution to this... and at least that this
 report may have been useful.
 
 Best regards
 


-- 

Cheers,
Mauro
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


AverTV Volar HD Pro (A835)

2011-02-09 Thread Josu Lazkano
Hello list, I want to buy the AverTV Volar HD Pro (A835) USB tuner, I
search it cheap on local shop. I search on the wiki and there is no
any info about it.

This is the device:
http://www.avermedia.com/avertv/Product/ProductDetail.aspx?Id=507

I search little info on the web:

http://forum.ubuntu-it.org/index.php/topic,384436.msg3370690.html#msg3370690
http://staredsi.wordpress.com/2011/01/12/avertv-volar-hd-pro-a835-en-gnulinux/

I have a Debian Squeeze (2.6.32), is possible to get it working here?
Someone with this device?

I want to use it on MythTV for HD channels.

Thanks and best regards.

-- 
Josu Lazkano
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


AverTV Volar HD Pro (A835)

2011-01-04 Thread Michal Bojda
Good evening,

at first I want to say thanks for your work in linux tv. Why I disturb
you... I am working on driver for AverTV Volar HD PRO (A835), USB card
for DVB-TV. At least, I am trying to make it. But still with no
success. I know the chip, demodulator and tuner, but thats all.
Everything I did, didnt helped. So I only want to ask you, if you ever
have anything to do with this card? Or are you worked with it? I just
cant make it working, so I will be glad for any hint.

Sorry for disturbing, and thanks for replying.

Regards, Michal Bojda.
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: AVerTV Volar HD PRO (A835)

2010-06-15 Thread Malte Zacharias

Hei Antti,

I picked this thread up from the web archive at
http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/18690/focus=19258

I too have  an Aver A835 DVB-T USB Stick and was wondering if it can be 
supported, after a thorough search I didn't find evidence in the web to 
support that, so I thought I might reopen the thread.


I checked the Windows driver .inf file as per your suggestion and can 
confirm that AF9035 appears to be the chipset. What steps are needed to 
get this supported? I am not afraid to patch my kernel and test whether 
it works, unfortunately I can't create such a patch by myself.


I have the hardware at hand and am willing to support you in every way 
possible (Preferarbly without harming the device :-) ). What more 
information would you need?


Greetings
Malte Z.
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: AVerTV Volar HD PRO (A835)

2010-05-13 Thread Antti Palosaari

Terve Honza,

On 04/28/2010 01:59 AM, Honza Stodola wrote:

I'm trying to use AVerTV Volar HD PRO (A835) in Linux, but it seems the
USB receiver is not supported by current kernel (2.6.34-rc5). Sending
some logs and configuration, let me know if you need some more. Any help
is appreciated.


lsusb looks like AF9035. Could you look windows driver .inf file content 
and file names to ensure that?


regards
Antti
--
http://palosaari.fi/
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


AVerTV Volar HD PRO (A835)

2010-04-27 Thread Honza Stodola

Hi,
I'm trying to use AVerTV Volar HD PRO (A835) in Linux, but it seems the 
USB receiver is not supported by current kernel (2.6.34-rc5). Sending 
some logs and configuration, let me know if you need some more. Any help 
is appreciated.


Thanks,
Honza

Product page:
http://www.avermedia.com/avertv/Product/ProductDetail.aspx?Id=507

# uname -r
2.6.34-rc5

# dmesg | tail -n 15
hub 1-2:1.0: state 7 ports 7 chg  evt 0004
hub 1-2:1.0: port 2, status 0101, change 0001, 12 Mb/s
hub 1-2:1.0: debounce: port 2: total 100ms stable 100ms status 0x101
usb 1-2.2: new high speed USB device using ehci_hcd and address 4
hub 1-2:1.0: port 2 not reset yet, waiting 10ms
usb 1-2.2: default language 0x0409
usb 1-2.2: udev 4, busnum 1, minor = 3
usb 1-2.2: New USB device found, idVendor=07ca, idProduct=a835
usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2.2: Product: A835
usb 1-2.2: Manufacturer: AVerMedia TECHNOLOGIES, Inc
usb 1-2.2: SerialNumber: 3030138014500
usb 1-2.2: usb_probe_device
usb 1-2.2: configuration #1 chosen from 1 choice
usb 1-2.2: adding 1-2.2:1.0 (config #1, interface 0)

# lsusb -vd 07ca:a835

Bus 001 Device 004: ID 07ca:a835 AVerMedia Technologies, Inc.
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize064
  idVendor   0x07ca AVerMedia Technologies, Inc.
  idProduct  0xa835
  bcdDevice2.03
  iManufacturer   1 AVerMedia TECHNOLOGIES, Inc
  iProduct2 A835
  iSerial 3 3030138014500
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   97
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0x80
  (Bus Powered)
MaxPower  500mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   5
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  0
  bInterfaceProtocol  0
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84  EP 4 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85  EP 5 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86  EP 6 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x  1x 0 bytes
bInterval   1
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   1
  bNumEndpoints   5
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  0
  bInterfaceProtocol  0
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7