Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 245813

Summary: media-tv/linuxtv-dvb-firmware wrong filename for dibusb dib3000mb firmware
Product: Gentoo Linux Reporter: Chí-Thanh Christopher Nguyễn <chithanh>
Component: Current packagesAssignee: Television related Applications in Gentoo's Portage <media-tv>
Status: RESOLVED FIXED    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on: 275667    
Bug Blocks:    

Description Chí-Thanh Christopher Nguyễn gentoo-dev 2008-11-06 11:42:14 UTC
The firmware name for dib3000mb as expected by drivers/media/dvbdvb-usb/dibusb-mb.c is "dvb-usb-dibusb-5.0.0.11.fw", however the ebuild names it "dvb-dibusb-5.0.0.11.fw" which causes firmware loading to fail.

Reproducible: Always

Steps to Reproduce:
1. DVB_CARDS="dibusb-usb1" emerge media-tv/linuxtv-dvb-firmware
2. Connect a dib3000mb USB DVB-T device (in my case, Twinhan DTV MagicBox)

Actual Results:  
from dmesg:
usb 4-2: new full speed USB device using uhci_hcd and address 3
usb 4-2: configuration #1 chosen from 1 choice
dvb-usb: found a 'TwinhanDTV USB-Ter USB1.1 / Magic Box I / HAMA USB1.1 DVB-T device' in cold state, will try to load a firmware
firmware: requesting dvb-usb-dibusb-5.0.0.11.fw
dvb-usb: did not find the firmware file. (dvb-usb-dibusb-5.0.0.11.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2)
dvb_usb_dibusb_mb: probe of 4-2:1.0 failed with error -22
usbcore: registered new interface driver dvb_usb_dibusb_mb


Expected Results:  
Load driver and firmware successfully

Renaming the firmware to "dvb-usb-dibusb-5.0.0.11.fw" makes it load correctly.
Comment 1 Daniel Pielmeier gentoo-dev 2009-07-29 18:42:04 UTC
This is fixed in the ebuild at bug #275667.
Comment 2 Daniel Pielmeier gentoo-dev 2009-09-02 21:32:48 UTC
Everything should be fixed in linuxtv-dvb-firmware-2009.07.06. If you
experience fetch issues for some firmwares please try again at a later time and
only open a new bug if the problem remains.