[linux-dvb] Re: new Nova-S docs (Re: DVB-T, no data fron cardon cold boot)

[Mark Reiche <mark.reiche@gmx.de>]

The problem with your diff-out is that I cannot see *what* function you 
commented out...
And I do not think that it is satisfying to have to load and unload this 
d*** driver all the time....
there should be a better solution (after all we are talking about linux, 
not windows, aren't we?)

Simeon Walker schrieb:

> Mark Reiche wrote:
>
> > In most cases, this won't be a solution. If you take budget instead 
> > of budget-ci, the card does not work at all. The problem is, that 
> > those Nova-cards seem to tune correctly, but do not deliver any data. 
> > My Nova-S for instance only works correctly after a warm boot from 
> > Windows.
> I have an old model Nova-T that shows similar symptoms. I find that it 
> will never work after a cold boot unless I do the following:
>
> First, using dvb-kernel I have to un-comment a function...
>
> tv dvb-kernel # cvs diff ./linux/drivers/media/common/saa7146_core.c
> Index: ./linux/drivers/media/common/saa7146_core.c
> ===================================================================
> RCS file: 
> /cvs/linuxtv/dvb-kernel/linux/drivers/media/common/saa7146_core.c,v
> retrieving revision 1.51
> diff -r1.51 saa7146_core.c
> 374c374
> < /*
> ---
> >
> 376c376
> < */
> ---
> >
>
> Then, in my script that starts vdr I do this:
>        modprobe grundig_29504-401
>        modprobe saa7146
>        modprobe budget_core
>        modprobe budget
>        sleep 1
>        rmmod budget
>        rmmod grundig_29504-401
>        rmmod budget_core
>        rmmod saa7146
>        rmmod ttpci_eeprom
>        sleep 1
>        modprobe grundig_29504-401
>        modprobe saa7146
>        modprobe budget_core
>        modprobe budget
>
> Then, when vdr loads it gets no data so I have a remote key to kill 
> it. If it's going to record something then it will do an emergency 
> exit and achieve the same thing
>
> Honestly, anything less does not work!!
>
> Regards,
> Simeon
>
> > The sad thing is, that even in this developer list no one could give 
> > at least some advise on how to investigate on the reason for this 
> > behaviour. In fact, most of the mails regarding this problem are 
> > simply ignored.
> >
> > Maybe, someone should try and port vdr to Windows, as the budget(-ci) 
> > driver under Linux is still broken
> >
> > Best Regards anyway,
> > Mark
> >
> > Olaf Titz schrieb: