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

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

Well really I have no idea then. The only thing I can think of is that
it is entirely possible that this is restricted to a few types of
motherboards (in my case I am using an Abit NForce 2.0 -S Revision 2
board). As I said I have tried every available firmware version that has
been available over the last 18 months - prior to 2.17 - including those
that came with my original CD.

It is not a simple matter for me to try the 2.17 drivers (at least not
that I'm aware of) since due to running a 2.6.x kernel the only drivers
I am able to use are those in the kernel itself.So in my case the 2,17
drivers are probably unlikely to help at this time, since the drivers I
have don't support that firmware version.

However I am hopeful that these new drivers (along with any patch
proposed here - even if it is relatively minor) will make its way into
the kernel tree soon and hopefully it will be available for the next
kernel release.

I say hopefully, because I have no idea of the time scale over which
these events normally take place.

If it is likely to be a long time, I will certainly study the
instructions given here for repairing the kernel source files and will
post the results of my test here. (Possibly in the next day or so).

Best regards,

GJ

On Sun, 2004-08-15 at 17:40, Tim Dodge wrote:
> For what it's worth, the sugested firmware would not upload on my 
> Hauppauge Nova-T card either.
> 
> However renaming the DLL from the CD that came with the card did work, 
> and now the most recent version of the firmware works for me, using the 
> patch posted here a few weeks ago,
> 
> Tim
> 
> Q wrote:
> 
> >ls -l /usr/lib/hotplug/firmware/tda1004x.bin
> >-r-xr-xr-x  1 root root 245760 2002-11-14 09:00
> >/usr/lib/hotplug/firmware/tda1004x.bin
> >
> >Well I figured that someone might assume that it was a trivial oversight
> >on my part. But for that to be true it would have to be a persistent
> >oversite, repeated perhaps 10's or maybe 100's of times over, across
> >every major distribution currently in circulation, every 2.6x kernel
> >from 2.6.4 on and through every firmware file version available in the
> >last 18 months.
> >
> >I have been nothing if not thorough.
> >
> >Nonetheless the input of a number of members on this list has been
> >enlightening - and the prospect of a kernel patch to resolve what I have
> >come to believe is a fault in which I have had no part in creating, is
> >at least an enticing prospect.
> >
> >So to coin a phrase, Yay, to a patch!
> >
> >This is rather a frustrating behaviour - particularly when it represents
> >something that previously had seemed (as in watching TV) so
> >fundamentally trivial. It's not even as if I watch TV very often.
> >However I do enjoy a challenge, so perhaps the sheer challenge alone is
> >significant enough to justify the amount of time and effort I have
> >invested in attempting to resolve this issue. Perhaps if there is a
> >patch, or a fix of some other kind, in some very small way someone else
> >will benefit and will not experience the same issues and the cause of
> >Linux for the masses can advance that little bit further. Maybe.
> >
> >Anyway I would appreciate being kept informed of any kernel patch
> >progress and I will study the advice given here carefully - and if
> >successful - I will report the results.
> >
> >Best regards,
> >
> >GJ
> >
> >
> >
> >  
> >
> 
>