From: sibu xolo <sibxol@btconnect.com>
To: linux-media@vger.kernel.org
Subject: Re: udev-161 dvbT kernel-2.6.35.5
Date: Mon, 4 Oct 2010 20:26:10 +0100 [thread overview]
Message-ID: <201010042026.10301.sibxol@btconnect.com> (raw)
In-Reply-To: <201010040116.35961.sibxol@btconnect.com>
On Monday 04 October 2010 01:16:35 sibu xolo wrote:
> Greetings,
>
> I am attempting to set up DVBT on a computer with these:
>
> --------cpu: amd64 2 cores, gpu nvidia gforce nouveau drm
> --------o/s cblfslinux 64-bit kernel-2.6.35.5 udev-161 kde-4.4.5
> --------dvb device Hauppauge wintvNovaT DVBT usb2
>
> I have the foollowing in /lib/firmware
>
>
> dvb-usb-dib0700-01.fw
> dvb-usb-dib0700-1.20.fw
>
>
> ############# my udev rule looks like so:-
>
> KERNEL="dvb*",
> PROGRAM="/etc/udev/scripts/dvb.sh %k",
> ATTRS{serial}=="123456789a",
> ATTRS{product}=="Nova-T Stick",
> GROUP="video",
> MODE="0660",
> SYMLINK+="Nova-T-usb2"
>
> ###### the machine dwells a litle on booting
> ###### lsmod yoelds:-
>
> root [ ~teeveey ]# lsmod
> Module Size Used by
> snd_hda_codec_realtek 294785 1
> dvb_usb_dib0700 77625 0
> dib7000p 15705 1 dvb_usb_dib0700
> dib0090 12297 1 dvb_usb_dib0700
> dib7000m 12868 1 dvb_usb_dib0700
> dib0070 7510 1 dvb_usb_dib0700
> dvb_usb 16683 1 dvb_usb_dib0700
> dib8000 23992 1 dvb_usb_dib0700
> dvb_core 87312 3 dib7000p,dvb_usb,dib8000
> dib3000mc 11061 1 dvb_usb_dib0700
> dibx000_common 3213 4 dib7000p,dib7000m,dib8000,dib3000mc
> nouveau 387642 2
> ttm 53985 1 nouveau
> drm_kms_helper 25234 1 nouveau
> snd_hda_intel 24006 3
> snd_hda_codec 82672 2 snd_hda_codec_realtek,snd_hda_intel
> pcspkr 1854 0
> ohci_hcd 33354 0
> cfbcopyarea 3037 1 nouveau
> cfbimgblt 2205 1 nouveau
> cfbfillrect 3113 1 nouveau
> snd_hwdep 6048 1 snd_hda_codec
> root [ ~teeveey ]#
>
>
>
> ############# but ls for /dev/dvb* yields nought like so:-
>
> root [ ~teeveey ]# ls -l /dev/dvb*
> ls: cannot access /dev/dvb*: No such file or directory
> root [ ~teeveey ]#
>
> I used the said device successfully in a build wih 2,6.28.8/udev-113 last
> year but it appears the setup for DVB on linux has changed recently.
> Accordingly guidance on where I am gping wrong would be much appreciated.
>
> Yours sincerely
>
> sibuXolo
I sent the email above to the list a day or so ago and received no response.
If I am on the wrong list I would be grateful if someone aufait inform me
of the appropriate list. Otherwise suggestions of where I am going wrong
would be much apprecuated.
as an update:-
I tested the setup described above on a machine with kernel-2.6.31.6 and
/dev/dvb/adapter0 is generated
I recall a while back when DVB drivers were not in the kernel. Then they
were integrated within thus requiring only a kernel compilation. I came
across the somewhat ubuntified wiki
( http://www.linuxtv.org/wiki/index.php/Bug_Report )
(which seems to suggest the old method is now needed.. I would thus be
grateful for some clarity as per:-
Is compiling the kernel as up to 2.6.28.8 and with prior selection of the
appropriate devices under device/drivers/multimedia/video sufficient or does
one now need to follow the recipe given by the link above.
sx
next prev parent reply other threads:[~2010-10-04 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 0:16 udev-161 dvbT kernel-2.6.35.5 sibu xolo
2010-10-04 19:26 ` sibu xolo [this message]
2010-10-05 21:17 ` sibu xolo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201010042026.10301.sibxol@btconnect.com \
--to=sibxol@btconnect.com \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox