Template:Firmware:dvb-usb-dib0700: Difference between revisions
(→Firmware: Update on i2c issues and 1.20fw) |
(→Firmware: Broken links) |
||
| Line 4: | Line 4: | ||
'''August 21, 2008 - New firmware file''' fixing the last cause for i2c errors and disconnects and providing a new, more modular i2c request formatting. |
'''August 21, 2008 - New firmware file''' fixing the last cause for i2c errors and disconnects and providing a new, more modular i2c request formatting. |
||
You will need the [http:// |
You will need the [http://linuxtv.org/downloads/firmware/dvb-usb-dib0700-1.20.fw <tt>dvb-usb-dib0700-1.20.fw</tt> firmware file] in <tt>/lib/firmware</tt> or the relevant place for your distribution. |
||
You may need to change the name of the file to <tt>dvb-usb-dib0700-1.10.fw</tt> or create a link until the driver code reflects that change. |
You may need to change the name of the file to <tt>dvb-usb-dib0700-1.10.fw</tt> or create a link until the driver code reflects that change. |
||
For archival purposes: [http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0700-1.10.fw <tt>dvb-usb-dib0700-1.10.fw</tt> firmware file] |
<strike>For archival purposes: [http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0700-1.10.fw <tt>dvb-usb-dib0700-1.10.fw</tt> firmware file]</strike> |
||
'''August 29,2008 - Issues with Firmware 1.20'''. Some issues have been found with the latest version of the firmware. Users may wish to continue to use 1.10 unless they have patched their v4l-dvb code with dib0700_new_i2c_api.patch. |
'''August 29,2008 - Issues with Firmware 1.20'''. Some issues have been found with the latest version of the firmware. Users may wish to continue to use 1.10 unless they have patched their v4l-dvb code with dib0700_new_i2c_api.patch. |
||
| Line 14: | Line 14: | ||
'''November 15,2008 - Issues with Firmware 1.20'''. |
'''November 15,2008 - Issues with Firmware 1.20'''. |
||
* The above mentioned dib0700_new_12c_api.patch is not available discretely but is now rolled into the mercurial drivers |
* The above mentioned dib0700_new_12c_api.patch is not available discretely but is now rolled into the mercurial drivers |
||
* [http://www.wi-bw.tfh-wildau.de/~pboettch/home/files/dvb-usb-dib0700-1.20.fw <tt>dvb-usb-dib0700-1.20.fw</tt> firmware file] is now stable for reception, but remote control functionality is broken; any key press is repeated until the next key is pressed. The only way to get remote control functionality presently is to roll back to 1.10 firmware and suffer the occasional disconnect. |
* <strike>[http://www.wi-bw.tfh-wildau.de/~pboettch/home/files/dvb-usb-dib0700-1.20.fw <tt>dvb-usb-dib0700-1.20.fw</tt> firmware file]</strike> is now stable for reception, but remote control functionality is broken; any key press is repeated until the next key is pressed. The only way to get remote control functionality presently is to roll back to 1.10 firmware and suffer the occasional disconnect. |
||
* The mercurial drivers have been changed so they now load 1.20 firmware. To revert to 1.10 firmware you need to rename your firmware file to <tt>dvb-usb-dib0700-1.20.fw</tt> or provide a link of that name. |
* The mercurial drivers have been changed so they now load 1.20 firmware. To revert to 1.10 firmware you need to rename your firmware file to <tt>dvb-usb-dib0700-1.20.fw</tt> or provide a link of that name. |
||
* To avoid spurious remote control signals with 1.20 firmware, you need to edit <tt>/etc/modprobe.d/options</tt> or from Ubuntu onwards <tt>/etc/modprobe.d/options.conf</tt>and add: |
* To avoid spurious remote control signals with 1.20 firmware, you need to edit <tt>/etc/modprobe.d/options</tt> or from Ubuntu onwards <tt>/etc/modprobe.d/options.conf</tt>and add: |
||
Latest revision as of 14:42, 5 February 2013
Firmware
August 21, 2008 - New firmware file fixing the last cause for i2c errors and disconnects and providing a new, more modular i2c request formatting.
You will need the dvb-usb-dib0700-1.20.fw firmware file in /lib/firmware or the relevant place for your distribution.
You may need to change the name of the file to dvb-usb-dib0700-1.10.fw or create a link until the driver code reflects that change.
For archival purposes: dvb-usb-dib0700-1.10.fw firmware file
August 29,2008 - Issues with Firmware 1.20. Some issues have been found with the latest version of the firmware. Users may wish to continue to use 1.10 unless they have patched their v4l-dvb code with dib0700_new_i2c_api.patch.
November 15,2008 - Issues with Firmware 1.20.
- The above mentioned dib0700_new_12c_api.patch is not available discretely but is now rolled into the mercurial drivers
dvb-usb-dib0700-1.20.fw firmware fileis now stable for reception, but remote control functionality is broken; any key press is repeated until the next key is pressed. The only way to get remote control functionality presently is to roll back to 1.10 firmware and suffer the occasional disconnect.- The mercurial drivers have been changed so they now load 1.20 firmware. To revert to 1.10 firmware you need to rename your firmware file to dvb-usb-dib0700-1.20.fw or provide a link of that name.
- To avoid spurious remote control signals with 1.20 firmware, you need to edit /etc/modprobe.d/options or from Ubuntu onwards /etc/modprobe.d/options.confand add:
options dvb_usb disable-rc-polling=1
November 28,2008 - i2c errors. Changes were made to the remote control drivers on November 16,2008 to correct the repeat key problem. The card is generally stable for dual tuner reception and remote control function with Firmware 1.20.
November 10,2009 - mt2060 I2C write failed. Possible regression of a driver bug raised against Ubuntu running 2.6.27-14 and 2.6.31-2.17 causing mt2060 I2C errors in MythTV useage with firmware 1.20. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/397696 Recommend check the kernel extensions listed here for Low Noise Activation and rc_polling are loaded with correct config file name for your distribution, EIT listings information is turned off until a suitable delay (500ms-1000ms)is added to a single card (not both) and the card has correctly been added to the database as two tuners (no additional NULL entries) in the mythtv recordcard table.