[linux-dvb] Re: Firmware won't upload.

["raid517@fairadsl.co.uk" <raid517@fairadsl.co.uk>]

Hi guys, I should have known it wouldn't be so straightforward I guess. 
Well as I said in my boot messages no longer complain that it can't 
upload the firmware. Just to refresh this is what boot now says:

Linux video capture interface: v1.00
saa7146: register extension 'budget dvb'.
saa7146: register extension 'budget dvb /w video in'.
saa7146: register extension 'budget_ci dvb'.
ACPI: PCI interrupt 0000:01:09.0[A] -> GSI 17 (level, high) -> IRQ 17
saa7146: found saa7146 @ mem e087d000 (revision 1, irq 17) (0x13c2,0x1011).
DVB: registering new adapter (TT-Budget/WinTV-NOVA-T  PCI).
TT-Budget/WinTV-NOVA-T  PCI adapter 0 has MAC addr = 00:d0:5c:22:0b:bf
saa7146: register extension 'budget_patch dvb'.
saa7146: register extension 'dvb'.
usbcore: registered new driver ttusb-dec
usbcore: registered new driver Technotrend/Hauppauge USB-Nova

So bo errors there to speak of.

However when I try to run 'scan' I just get an error message saying:

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
main:1882: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 6 No 
such device or address

I had to use the MAKEDEV-DVB.sh script to build these devices in /dev as 
they weren't automatically created by the kernel - although I supect it 
would have been better if they had been.

But from what I can work out what it's saying is that even though the 
front end firmware appears to be loaded now, the DVB scan app still 
can't find it.

I have tried changing the permsissions on all the files and directories 
in /dev/dvb to read write and execute, but this has had no effect.

The question is, where now from here?

I have no clue at all how to move forward from this point. It seems I 
have hit an impasse.

Has anyone got any suggestions?

GJ



Christoph Burger-Scheidlin wrote:

> Hello,
>
> I have a Nova-T card and experienced the same problem on a debian box. I
> managed to solve it by simply compiling the code as modules and then
> loading of the firmware worked.
>
> As far as I understand your post, you compiled everything into the
> kernel and tried to load the firmware during boot. If that is the case,
> using modules should fix your problem.
>
>
> Here are some thoughts on the problem as I experienced it, maybe someone
> who has a better understanding on the bootup process can comment on it
> to clarify it for me or even better lend a hand in fixing it.
>
> The problem as I experienced it is not in the kernel not loading the
> firmware, but simply that the filesystem on which the firmware is
> residing is not mounted during initialization of the dvb-kernel part.
> This prevents the kernel from accessing the file
> /usr/lib/hotplug/firmware/tda1004x.bin. Having realized that problem, I
> tried circumventing it by using an initrd image, which seemes to fail as
> well, since the initrd is executed after kernel initialization, so also
> after the kernel tries to load the firmware. The bootup process appears
> the same when reading the error messages.
>
> Digging in the 2.6 kernel features, I came accross an initial ramfs
> filesystem which is loaded at the same time as the kernel is. This
> initramfs is a cpio archieve. From what I understand about the
> bootprocess, this is the place to put the firmware, since then the
> kernel can load it when the kernel is initialized. However, I have not
> managed to produce a working initramfs, so I haven't yet managed to
> either put the firmware file in it nor be able to load it.
>
>
> Although it is not ideal, I hope modularizing the code works for you as
> well Q.
>
>
> Hth,
>
> Christoph Burger-Scheidlin
>
>
>
>
>
>