[linux-dvb] Re: TDA1004x and 2.6.10 kernel fw loading problem

[Richard Hamnett <r.hamnett@gmail.com>]

Hi there, I have just had this problem recently, and it was because i
was using udev 0.50 which seems to have a new firmware loading agent.

I have reverted back to udev 0.45 for the time being, and i presume
this will resolve your issue too

Thing is, we need someone with more knowledge than myself to try and
figure out why udev 0.50's new firmware loader isn't working properly

Rick


On Sat, 8 Jan 2005 13:08:52 +1100, Hamish Moffatt <hamish@cloud.net.au> wrote:
> On Fri, Jan 07, 2005 at 06:45:59PM +0100, Tomá? Chaloupka wrote:
> > Hamish Moffatt wrote:
> > >Do you have hotplug installed? (It's probably /sbin/hotplug.)
> > >It is needed to pass the file from /usr/lib/hotplug/firmware to the
> > >kernel when the driver requests it.
> > >
> > >The new firmware files are dvb-fe-tda10045.fw (and ...6.fw). They are
> > >30K for the 10045 and 24K for the 10046. The old tda1004x.bin (much
> > >bigger) is no longer required but it's ok to leave it in the directory.
> > >
> > Yes I have it installed. Before new kernel it worked just fine.
> > When I boot the old kernel it also works fine.
> 
> The old kernel does not need hotplug to load the DVB firmware.
> The driver would read the file directly from /usr/lib/hotplug/firmware.
> In 2.6.10, the driver uses hotplug to get the firmware instead.
> 
> Depending on your distribution you might have to put the firmware in
> /lib/firmware instead.
> 
> > So I thought that fw is already in, but then I don't get the second
> > messages when i try to watch something.
> 
> I think it will usually load the firmware when you first try to tune.
> (Or each time you tune until it loads successfully.)
> 
> > When I try just to tzap something -r
> > I get an normal output:
> > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> > tuning to 506000000 Hz
> > video pid 0x0201, audio pid 0x0295
> > status 00 | signal ffff | snr 0000 | ber 0001fffe | unc 00000000 |
> 
> tzap won't fail if the firmware isn't loaded, but it won't lock.
> 
> Did you get any error messages from the kernel? (dmesg).
> 
> 
> Hamish
> --
> Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
> 
>