[linux-dvb] Re: Nebula dvb-t PCI problems

[aunola+dvb@ydin.org]

On Sun, Sep 05, 2004 at 09:06:18PM +0300, Jukka Tastula wrote:
> > So, no signal information. Is this normal with Nebula card? I can see
> > the picture. Also "femon" plugin in vdr have problems in showing those
> > signal and other diagnostic values.
> 
> Yes. Perfectly normal. Nothing wrong.
> 

Well, it would be nice to see signal strengts and other "useful"
information.

> > Another "problem" is that "./dvbscan dvb-t/fi-Lahti" finds channels, but
> > when it's trying other frequencies it complains:
> >
> > .>>> tune to:
> > .>>> 682000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:
> > TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE
> > WARNING: >>> tuning failed!!!
> 
> Digita's web says 682 is a valid frequency for mux b (mtv3, nelonen,...

I have no idea about this, but yes, I can scan every channels and watch
them. Just that "tuning failed" message is confusing me. And here is the
content of dvb-t/fi-Lahti file (it wasn't in original scan sources):

# Lahti A-mux (Digita Finland)
# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
T 570000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE
T 682000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE
T 762000000 8MHz 2/3 NONE QAM64 8k 1/8 NONE

> The first one isn't a problem at all. The second is probably a 
> misunderstanding.  The hangs I can't say much about as I haven't 
> experienced any (if you don't count modprobe bttv with wrong card option). 
> 

Well, in my case computer usually hangs when uptime is something around
10 days. Have you any special modprobe parametres? I just use modprobe
dvb-bt8xx and nxt6000.

By the way, have you got your remote control receiver working on linux?


-- 
Joonas Aunola, aunola@ydin.org