> I have 3 usb dvb devices connected to my system. I would like each device to
> be assigned a specific adapter number (i.e. /dev/dvb/adapter0 is always my
> dvbt device adapter1 is my dvbs device etc) no matter which order they are
> plugged in or detected at boot. Is this possible?
udev can do t
> DVB: registering frontend 0 (LG Electronics LGDT3303 VSB/QAM
> Frontend)...
>
> This seems to match my actual device which is the "FusionHDTV 5 RT
> Gold". I had read that the "FusionHDTV5 RT Gold" and the "FusionHDTV5
> Gold Plus" were actually identical boards. The chips seemed to match
> up w
> I'm continuing to troubleshoot the above problem. Since I was seeing
> this under 2.6.18-r7 and 2.6.17-r8-gentoo (uses a slightly older
> version of linux-dvb and cx88 driver) I've moved back to using the
> 2.6.17-r8-gentoo kernel. That of course didn't make to much of a
> difference, I didn't ex
> I am using one external antenna. I think that Philip is doing the
> same. Signal strength seems quite good here. Kaffeine is reporting
> signal strength of about 94% and snr or about 80%.
external antenna here as well (Hills DMX 100).
no mast-head amplifier used. connected with all quad-shi
> >> How do you determine what the correct center frequency is? Trial and
> >> error edits to /etc/dvb/channels.conf-dvbt-australia? Or do I just
> >> wait until the driver evolves to the standard of the driver for the
> >> Kworld with its cx8800?
>
> > Try and error or search for appropriate in
> regardless of that, the key differences seem to be that v4l/dvb tip-of-
> tree
> identify & enable the devices at both :01:08.0 & :01:08.2 whereas
> the stock 2.6.18-rc5 only enables :01:08.2.
scrap that, i posted the wrong diff. correct diff attached here.
end result is the same:
> Richard Dale speaks of a problem that he had in 2.6.18-rc6 with his
> DViCO card...
>
> http://linuxtv.org/pipermail/linux-dvb/2006-September/012639.html
>
> ...Is this the same problem that you had experienced? If not, could you
> provide some more information?
just tested 2.6.18rc5 without
> I am happy to see that you and Andrew were able to determine that the
> problem with dvb_attach was due to an old version of module_init_tools,
> however, I am also very interested to hear about what was wrong with the
> vanilla 2.6.18-rc kernel, that lead you to install the newer modules
> from
't yet fix my
other 2 cards - neither dst nor dvb-bt8xx get loaded automatically.
i'll look into those now.
(if my mailer mangles the patch, i've also put it at
<http://www.interlink.com.au/ltd/dvb_mod_load_by_name.patch>)
--
From: Lincoln Dale <[EMAIL PROTECTED]>
[PATCH
>> from looking at the resulting /lib/modules/2.6.18-rc5ltd1/modules.dep,
>> i can see that no modules seem to think they have a dependency on
>> mt352. same for dst.
>
> yep, thats right.. dvb_attach does the dependencies at runtime.
hmm, ok. that's where the twisty maze of
symbol_request/try_
g'day,
> How are you installing the new kernel? DVB in 2.6.18 has a new feature,
> "dvb attach", designed to minimise the number of loaded modules. It
> this that is breaking. If for some reason, your depmod information is
> incorrect, it'll break, and wont be able to load the modules.
i'm insta
g'day,
i recently upgraded my mythtv backend machine to much faster hardware (dual
core goodness).
my system consists of 3 DVB-T single-tuner cards & 1 analog tuner.
specifically:
1 x DvICO Fusion HDTV DVB-T1 (OEM version of T Plus;
requires: cx88, cx2388x, cx88-dvb, Zarlink MT352 fronte
12 matches
Mail list logo
