[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#615543: marked as done (base: Firmware files not found by boot process, despite specific files are there and readable for world)

Your message dated Fri, 30 Sep 2011 14:33:44 -0500
with message-id <20110930193344.GA1536@elie>
and subject line Re: base: Firmware files not found by boot process, despite specific files are there and readable for world
has caused the Debian Bug report #615543,
regarding base: Firmware files not found by boot process, despite specific files are there and readable for world
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
615543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615543
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: base
Severity: important

I have two DVB_T USB device, either or both of them can not read the firmware file,
nowadays this issue occurs with an (Alcor DTV-1000) Afatech 9015 USB device.

DMESG output:
usb 1-7: New USB device found, idVendor=15a4, idProduct=9016
usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-7: Product: DVB-T 2
usb 1-7: Manufacturer: Afatech
ata6: SATA link down (SStatus 0 SControl 310)
Freeing unused kernel memory: 464k freed
udev[117]: starting version 164
dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware
dvb-usb: did not find the firmware file. (dvb-usb-af9015.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2)
dvb_usb_af9015: probe of 1-7:1.0 failed with error -2

lsusb out:

root@torch:~# lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 06da:0003 Phoenixtec Power Co., Ltd 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 15a4:9016 Afatech Technologies, Inc. AF9015 DVB-T USB2.0 stick
Bus 001 Device 003: ID 2304:023d Pinnacle Systems, Inc. PCTV 340e
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And the firmware file is there:

root@torch:/lib/firmware# ls -l /lib/firmware/dvb-usb-af9015.fw 
-rw-r--r-- 1 root root 15913 2010 �   16 /lib/firmware/dvb-usb-af9015.fw

Packages installed contains firmwares:

root@torch:/lib/firmware# dpkg --list | grep "firmware"
ii  firmware-ivtv                        0.28                         Binary firmware for iTVC15-family MPEG codecs (ivtv and pvrusb2 drivers)
ii  firmware-linux                       0.28                         Binary firmware for various drivers in the Linux kernel (meta-package)
ii  firmware-linux-free                  2.6.32-30                    Binary firmware for various drivers in the Linux kernel
ii  firmware-linux-nonfree               0.28                         Binary firmware for various drivers in the Linux kernel
ii  firmware-realtek                     0.28                         Binary firmware for Realtek wired and wireless network adapters

Can you please look into why the boot process cannot read the firmware file, which exists
and readable?

Scope: Device is unable to use.
Exclusion: Other firmwares are detected and loaded.

User Status:
Reboot didn't help. Poweroff, unplug the computer didn't help.
Unplug the device then replug didn't helped.

The device worked properly under Ubuntu 10.04 LTS Lucid Lynx with (almost) the same kernel
(2.6.35.x).

The system itself is a :

root@torch:/lib/firmware# uname -a
Linux torch 2.6.35.10-3 #1 SMP Mon Dec 27 19:56:08 CET 2010 x86_64 GNU/Linux

Thank you very much for all the help, guideance.

-- System Information:
Debian Release: 6.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.35.10-3 (SMP w/4 CPU cores)
Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
(cc-ing the bug log, so others can take over if I get too busy)
Hodosi Szabolcs wrote:

> Thank you for your response and I can confirm somehow the udev agent make
> things wrong.
> I found that I have issues only when the kernel "module" is built into the
> kernel, in that case it cannot grab the firmware file, but when I recompiled
> the kernel in way to make DVB kernel modules be external (.ko) firmwares
> were found. So I assume I'm used the system inappropriate way / or this is a
> debian specific thing..
> By now I'm fine with my box, so we can close the issue.

When you build in a driver, that means it is likely to load before the
final root filesystem is mounted.  So if there is some reason you need
to build in the driver (maybe it is a network card used to send
messages from early boot over the network) then it is simplest to
build in the firmware as well, using the configuration "Device Drivers
→ Generic Driver Options → External firmware blobs to build into the
kernel binary" (CONFIG_EXTRA_FIRMWARE).

Closing.  If there is some documentation you looked at expecting
guidance that didn't mention this, please tell us so we can fix it.

> By the way, I found a new DVB-T reciever device on the market, which has a
> Conax SIM card slot:
> http://www.alcordigital.hu/product/alcor_dtv_conax_mpeg4_hd_dvb_t_receiver
> (This is mostly useful for hungarians)
> The manufacturer officially informed me about the internal of this usb
> stick. It uses Dibcom 7070-es tuner chip and the SIM card reader is a SMiT
> 1660 card module.
>
> What do you think about the linux support of it?
> I google for awhile but since this is a new product I haven't found too much
> valueable result..
>
> Thanks in advance,

No idea about that.  Your best bet is to look around under
drivers/media/, to look around at linuxtv.org, or to ask on the
appropriate upstream mailing list.

--- End Message ---
Reply to: