[linux-dvb] Re: HELP! - old Nova-T - Gentoo 2.6.10 - firmware- not working.

[Alberto López Navarro <alopez@ambar.es>]

	Hi all, this is my first post also.

	Not sure it's exactly the same, but I have a similar problem with redhat 9, kernel upgraded to 2.6.10 (yes, only the kernel and modutils). I think the problem is related to hotplug configuration, but I'm not an expert on that. The problem appears at this point:

        /* request the firmware, this will block until someone uploads it */
        printk("tda1004x: waiting for firmware upload (%s)...\n",TDA10045_DEFAULT_FIRMWARE);
        ret = state->config->request_firmware(fe, &fw, TDA10045_DEFAULT_FIRMWARE);
        if (ret) {
                printk("tda1004x: no firmware upload (timeout or file not found?)\n");
                return ret;
        }

	So the call to request_firmware fails to return a valid fw file. It doesn't even get to try to upload the data.

	I've tried to upgrade hotplug (BTW, it seems that "cat /proc/sys/kernel/hotplug" should return the path to the hotplug executable (usually /sbin/hotplug) but in my case it gave "/bin/true". I tried further to upgrade to a newer version of hotplug (that pulled the usual dependency string with hwdata and kudzu), but no way.

	The funniest thing is that while I was doing something else, I turned to look at a window where I was running tzap... and it had locked. In dmesg there was still the "tda1004x: firmware upload failed" message. It seems the card needs some time to heat up!

	For the moment it's working OK, but the result is not reproducible. It seems to begin receiving after some tries... Does anyone have a fix?

	Alberto




-----Mensaje original-----
De: Scott White [mailto:scott-dvb@riskboys.com]
Enviado el: Tuesday, February 01, 2005 12:30 AM
Para: linux-dvb@linuxtv.org
Asunto: [linux-dvb] Re: HELP! - old Nova-T - Gentoo 2.6.10 - firmware-
not working.


Aha!  I'm suffering the same problem.  Gentoo 2.6.10-r6

# lspci
0000:01:02.0 Multimedia controller: Philips Semiconductors SAA7146 (rev
01)
0000:01:06.0 Multimedia controller: Philips Semiconductors SAA7146 (rev
01)

# lspci -vn
0000:01:02.0 Class 0480: 1131:7146 (rev 01)
        Subsystem: 13c2:1011
        Flags: bus master, medium devsel, latency 32, IRQ 17
        Memory at f7f20400 (32-bit, non-prefetchable)

0000:01:06.0 Class 0480: 1131:7146 (rev 01)
        Subsystem: 13c2:1011
        Flags: bus master, medium devsel, latency 32, IRQ 20
        Memory at f7f20000 (32-bit, non-prefetchable)

and I am seeing 

tda1004x: waiting for firmware upload...

I tried the one line change to the kernel source and recompile, but didn't fix it.

Tried CVS and now firmware loads :-)  

All I need to do is remember how to permanently replace my kernel modules 

Scott


On Wed, 2005-01-26 at 21:22 +0000, Andrew de Quincey wrote:
> On Wednesday 26 Jan 2005 20:48, Johannes Stezenbach wrote:
> > On Wed, Jan 26, 2005 at 04:03:38PM +0000, Andrew de Quincey wrote:
> > > On Wednesday 26 Jan 2005 14:47, Andrew de Quincey wrote:
> > > > Strange!! check the output of lspci -vn. My DVB device has somehow
> > > > suddenly got the wrong subsystem manufacturer ID:
> > > >
> > > > 0000:00:0b.0 Class 0480: 1131:7146 (rev 01)
> > > >         Subsystem: 1342:1011
> > > >         Flags: bus master, medium devsel, latency 32, IRQ 127
> > > >         Memory at e1000000 (32-bit, non-prefetchable) [disabled]
> > > >
> > > > That 1342 should be 13c2. It was fine yesterday!
> > >
> > > Hmm, even weirder - I pulled the card out of the machine, let it "rest"
> > > for half an hour, and now it is back at 13c2 again, and working
> > > perfectly!
> > >
> > > Could this be caused by the saa7146-reset-race problem as well? I'm now
> > > using the CVS drivers (previously I was using the in-kernel ones for
> > > 2.6.11-rc1)
> >
> > I don't know what exactly you mean by saa7146-reset-race problem.
> > The saa7146 master reset is still not enabled in CVS.
> 
> Oh right, sorry, I thought all that stuff had been comitted? Must have 
> misread.
> 
> Hmm, in that case, has anyone else seen this problem? It would seem as if the 
> DVB devices no longer appeared until the machine was turned for a longish 
> while... now I come to think of it, I think I have seen this once before ages 
> ago.
> 
> 
>