The firmware file that seems to be downloaded don't install properly. It uncompress, but then portage complains that the extracted firmware file doesn't exist in /var/tmp/portage/media-tv/linuxtv-dvb-firmware Reproducible: Always Steps to Reproduce: 1. set DVB_CARDS="usb-af9015" in /etc/make.conf 2. emerge linuxtv-dvb-firmware
Created attachment 218229 [details] emerge log file
@media-tv: I am tending more and more to drop this ebuild from the tree. Probably we should have removed it with with Diegos last-rite. It is a huge the effort to maintain this complex ebuild which actually just installs a few binary files. Whereas everything that needs to be done is downloading the installer containing the firmware needed for the device and the right tools for extacting it or even simpler download pre-extracted files from the web and place them under /lib/firmware. For this procedure various sources for different devices exist on the web, so the user should be able to manage this on his own. What do you think about finally punting it from the tree?
You're right : this ebuild should be ripped from the tree, but the user should be informed by some way (perhaps a page in the gentoo wiki ? or with a message in the media-v/linuxtv-dvb-apps) that the firmware has to installed and where it should be installed. That's the reason of my bug : I understood that I could perhaps install the firmware, but I wasn't sure of the path in which I had to install the firmware (that I already got anyway) and if the ebuild would update some configuration file. If this ebuild just download a binary file and don't generate anything else like config file, then just kill this ebuild. IMO, ebuild are not made for downloading purposes. I understand that 1) you lose a huge time for maintaining a list a firmware up-to-date, with always being late 2) because between new hardware coming out every time and firmware upgrades, you could spend days updating the ebuild that it would still be out-of-date... I can write a page in the gentoo wiki, but I'd like some help to understand all the steps to follow. The "gentoo VDR" guide in the gentoo doc doesn't helped me much, but perhaps have I read it too fast ?!?
media-tv/linuxtv-dvb-firmware will be removed from the tree in 30 days. See bug #304047 for more information.
(In reply to comment #2) > @media-tv: > > I am tending more and more to drop this ebuild from the tree. Probably we > should have removed it with with Diegos last-rite. It is a huge the effort to > maintain this complex ebuild which actually just installs a few binary files. > Whereas everything that needs to be done is downloading the installer > containing the firmware needed for the device and the right tools for extacting > it or even simpler download pre-extracted files from the web and place them > under /lib/firmware. For this procedure various sources for different devices > exist on the web, so the user should be able to manage this on his own. > > What do you think about finally punting it from the tree? > Wrong. We'll mirror it else where and version it. It stays in the tree. We're not breaking half of media-tv.
*** Bug 304933 has been marked as a duplicate of this bug. ***
Created attachment 227055 [details, diff] updates ebuild to work with af9015 firmware Patch updates the checksum for the af9015 firmware so that the ebuild installs the extracted firmware correctly. Note I have not yet checked that this firmware actually works, but "something" is extracted Note there is a second hunk in this patch. This adds some debugging in the event of mismatched checksums. This extra hunk hopefully makes it much simpler to create new patches going forward
Comment on attachment 227055 [details, diff] updates ebuild to work with af9015 firmware Bother - the extracted firmware does not appear compatible with the kernel driver. Instead simply use the firmware from here:http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/4.95.0/dvb-usb-af9015.fw URL seems sound since it's referenced from the linuxtv.org website here: http://www.linuxtv.org/wiki/index.php/Afatech_AF9015
(In reply to comment #8) > (From update of attachment 227055 [details, diff]) > Bother - the extracted firmware does not appear compatible with the kernel > driver. > > Instead simply use the firmware from > here:http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/4.95.0/dvb-usb-af9015.fw > > URL seems sound since it's referenced from the linuxtv.org website here: > http://www.linuxtv.org/wiki/index.php/Afatech_AF9015 > It works for me. Could anyone replace the URL in the "FW_URLS=" ebuild variable? Thanks
*** Bug 324731 has been marked as a duplicate of this bug. ***
Created attachment 255175 [details, diff] new URL for fw usb-af9015 (In reply to comment #9) URL is replaced. I had to comment out the firmware files tda10045, vp7041 and mpc718 to make it work. The downloads for these files are broken.
(In reply to comment #5) > Wrong. We'll mirror it else where and version it. Good idea. Download all firmware (with version tag) and bundle it. This should reduce effort to maintain this package. You'll need to update the package if it is not compatible with the kernel driver any longer (like in comment #8). But this problem has other packages (vhba,...), too. Maybe the old package get a "DEPEND= <=gentoo/vanilla-kernel-x.y.z" entry then. Any progress on this?
(In reply to comment #11) > Created an attachment (id=255175) [details] > new URL for fw usb-af9015 > > (In reply to comment #9) > URL is replaced. > I had to comment out the firmware files > tda10045, vp7041 and mpc718 to make it work. > The downloads for these files are broken. > Today, I only need to remove vp7041.
(In reply to comment #13) > (In reply to comment #11) > > Created an attachment (id=255175) [details] [details] > > new URL for fw usb-af9015 > > > > (In reply to comment #9) > > URL is replaced. > > I had to comment out the firmware files > > tda10045, vp7041 and mpc718 to make it work. > > The downloads for these files are broken. > > > > Today, I only need to remove vp7041. > And I forgot: With you patch the get_dvb_firmware-2009.09.19 script is used. For a correct patch af9015 has to go in "own URL" section and can be deleted from get_dvb_firmware-2009.09.19.
ARGH... Sorry for the noise, I just had a look at the depending bug 314671 and saw there is done everything. ...I miss a edit function... Four posts, oh god...
The firmware version has changed. With the current driver version (9.6.3.1), the firmware version is 5.1.0.0. Changing the hash is not enough, you have to change fwoffset and fwlength. Here is the output with a TerraTec Cinergy T Stick RC and the new firmware : usb 1-5: new high speed USB device using ehci_hcd and address 4 input: NEWMI USB2.0 DVB-T TV Stick as /devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.1/input/input8 generic-usb 0003:0CCD:0097.0002: input: USB HID v1.01 Keyboard [NEWMI USB2.0 DVB-T TV Stick] on usb-0000:00:02.1-5/input1 dvb-usb: found a 'TerraTec Cinergy T Stick RC' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' dvb-usb: found a 'TerraTec Cinergy T Stick RC' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (TerraTec Cinergy T Stick RC) af9013: firmware version:5.1.0.0 <- New firmware version DVB: registering adapter 2 frontend 0 (Afatech AF9013 DVB-T)... tda18218: NXP TDA18218HN successfully identified. Registered IR keymap rc-empty input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:02.1/usb1/1-5/rc/rc2/input9 rc2: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:02.1/usb1/1-5/rc/rc2 dvb-usb: schedule remote query interval to 500 msecs. dvb-usb: TerraTec Cinergy T Stick RC successfully initialized and connected. usbcore: registered new interface driver dvb_usb_af9015
Created attachment 267069 [details, diff] Update for the new firmware version of af9015 Here is a patch to update the get_dvb_firmware script and get the new version of the firmware (5.1.0.0)
removed
