Re: Can't find firmware when resuming

Re: Can't find firmware when resuming

[Patrick Boettcher]

Hi Gonsolo,

I'm adding the LMML.

On Fri, 5 Jun 2009, Gonsolo wrote:

> Hello!
>
> Is the following problem known?
> The Hauppauge Nova-T stick hangs the resume for 60 seconds.
> The firmware is there and I can watch TV before suspending.
>
> From my dmesg:
>
> [34258.180072] usb 1-1: reset high speed USB device using ehci_hcd and 
> address 4
> [34258.312799] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will 
> try to load a firmware
> [34258.312805] usb 1-1: firmware: requesting dvb-usb-dib0700-1.20.fw
> [34318.312097] dvb-usb: did not find the firmware file. 
> (dvb-usb-dib0700-1.20.fw) Please see linux/Documentation/dvb/ for mor
> e details on firmware-problems. (-2)

You are resuming from suspend2disk, right?

The driver is using a standard method to retrieve the firmware buffer from 
user-space, if it does not work, it is a problem of you installation, 
namely udev.

OTOH, the dvb-usb-framework is not ready to handle a suspend2disk 
correctly. E.g. being able to suspend2disk while watching TV will work, 
but when resuming it will be seen as a device disconnect and the 
application will stop to work.


Patrick.

--
   Mail: patrick.boettcher@desy.de
   WWW:  http://www.wi-bw.tfh-wildau.de/~pboettch/

Re: Can't find firmware when resuming

[Gonsolo]

>> Is the following problem known?
>> The Hauppauge Nova-T stick hangs the resume for 60 seconds.
>> The firmware is there and I can watch TV before suspending.
>>
>> From my dmesg:
>>
>> [34258.180072] usb 1-1: reset high speed USB device using ehci_hcd and 
>> address 4
>> [34258.312799] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold 
>> state, will try to load a firmware
>> [34258.312805] usb 1-1: firmware: requesting dvb-usb-dib0700-1.20.fw
>> [34318.312097] dvb-usb: did not find the firmware file. 
>> (dvb-usb-dib0700-1.20.fw) Please see linux/Documentation/dvb/ for mor
>> e details on firmware-problems. (-2)
> 
> You are resuming from suspend2disk, right?

This was suspend to ram but it happened with suspend to disk too.

> The driver is using a standard method to retrieve the firmware buffer 
> from user-space, if it does not work, it is a problem of you 
> installation, namely udev.

This is Ubuntu Jaunty with a kernel 2.6.30rc8 from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/ but I am pretty confident 
that it happened with the 2.6.28, too.

Ok, I grepped for udev in /var/log and found:

May 30 15:08:24 ups firmware.sh[30098]: udev firmware loader misses 
sysfs directory

It seems that the dev in sysfs can't be found.
I will try to investigate that.

> OTOH, the dvb-usb-framework is not ready to handle a suspend2disk 
> correctly. E.g. being able to suspend2disk while watching TV will work, 
> but when resuming it will be seen as a device disconnect and the 
> application will stop to work.

As long I only have to push a button in me-tv to turn it on again that's 
ok with me.

Thank you for your answer.

g

Re: Can't find firmware when resuming

[Gonsolo]

>> Is the following problem known?
>> The Hauppauge Nova-T stick hangs the resume for 60 seconds.
>> The firmware is there and I can watch TV before suspending.
>>
>> From my dmesg:
>>
>> [34258.180072] usb 1-1: reset high speed USB device using ehci_hcd and 
>> address 4
>> [34258.312799] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold 
>> state, will try to load a firmware
>> [34258.312805] usb 1-1: firmware: requesting dvb-usb-dib0700-1.20.fw
>> [34318.312097] dvb-usb: did not find the firmware file. 
>> (dvb-usb-dib0700-1.20.fw) Please see linux/Documentation/dvb/ for mor
>> e details on firmware-problems. (-2)
> 
> You are resuming from suspend2disk, right?
> 
> The driver is using a standard method to retrieve the firmware buffer 
> from user-space, if it does not work, it is a problem of you 
> installation, namely udev.

Is it possible that this is a initrd problem?
I found out that device initialization is done before running /sbin/init 
(which includes running running /etc/rcS which includes mounting sysfs).
I also found out about the FIRMWARE_IN_KERNEL config. The Ubuntu kernel 
leaves this unset.

Is it possible that the kernel tries to initialize the device when 
running the initial ramdisk? Then it seems natural that it can't find 
the firmware because it is not included as I found out with:

file-roller /boot/initrd.img-2.6.30-020630rc8-generic

So I guess this is an Ubuntu bug about initrd/firmare configuration?

Thank you.

g