The chip vendor Uli  refuses to open all relevant information. Such driver would rely on kernel fuse and character device in user space support as well as libfuse. The quality of the code if open, there are also cases where you just get a binary blob too often just isn’t good enough and there’s still too much work to be done to make the device work. If you get no or poor signal on Linux, that’s “normal”. The list at the left side of this page gives you the names of other manufacturers. It “kind of works” for me with the older driver http: USB ID before firmware:
|Date Added:||6 October 2008|
|File Size:||64.85 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
In dmesg I see: If you’d like to add a new device supported or unsupportedplease go to Receivrr The chip vendor Uli  refuses to open all relevant information. Please feel free to create a device specific page if there is enough worthwhile information that doesn’t fit in the comments field.
CONFIG_DVB_USB_AF9005: Afatech AF9005 DVB-T USB1.1 support
Note that if your device is similar to or contains components for which receiverr development is currently being undertaken, then it is possible that you will pique the developers’ interest and can obtain some assistance that, possibly, leads to full support for your device. At this stage, AfaTech will not release full specifications, and so these cards are likely to remain unsupported.
The driver was completely reverse-engineered without the help of its real vendor assuming WideView is the manufacturer. See device page for details.
Linux Kernel Driver DataBase: CONFIG_DVB_USB_AF Afatech AF DVB-T USB support
Some “broken” devices where sold with cold id: The device specific article is linked via the device’s name but not all are linked yet. You could watch television channels of other countries.
The list at the left side of this page gives you the names of other manufacturers. If you have details for a particular device, please feel free to clone this entry and add the details.
If you are experiencing problems with USB devices, it may not be the fault of the tuner. The newer driver http: It seems to work with the realtek experimental driver see freecom v4 above:. The correct firmware is here: For example, while sitting in germany, you could watch brazilian or japanese tv stations.
But uwb are many other manufacturers as well. If the driver crashes, it won’t crash the system or kernel, only the driver and applications using the driver will be affected. In any regard, in respect to the above listed suggestions, you may find it to be the case that your device is actually already supported or that experimental support is available.
Or buy a device with better support. If you find an article e. Should be supported soon writing as of june 30 This is a generic entry for the Anysee E7 line.
If you own one or more devices from the following list and you want to help with support development, please contact the Linux-Media Mailing List Us. It “kind of works” for me with the older driver http: We selected the timezone ‘UTC’ for now, but please set date. This device looks identical to this one and is sold in Germany under the same name and in an almost identical box.
drivers/media/usb/dvb-usb/Kconfig – chromiumos/third_party/kernel – Git at Google
It is not safe to rely on the system’s timezone settings. At least they have a different usb id. The following list of devices will have to be organized into a table.
This page was last modified on 26 Octoberat It’s possible your device will work. No additional firmware vvb is needed. Such driver would rely on kernel fuse and character device in user space support as well as libfuse. The first revision of this device is EOL but still supported, all hardware Features are supported by Sundtek’s 3rd party userspace driver.