From: Arthur Marsh <arthur.marsh@internode.on.net>
To: linux-media@vger.kernel.org
Cc: Joel Stanley <joel@jms.id.au>
Subject: Fwd: 0bda:2838 Ezcap DVB USB adaptor - no device files created
Date: Sat, 02 Jul 2011 16:36:39 +0930 [thread overview]
Message-ID: <4E0EC37F.1010201@internode.on.net> (raw)
Hi, I bought one of these things having seen the Linux penguin on the
box and compiled the code from the
http://jms.id.au/wiki/EzcapDvbAdapter web page on a quad core AMD64
machine using 3.0.0-rc5 Linux kernel and GCC 4.6.1 under Debian sid.
On boot-up the device is at least partially recognised:
[ 1.430924] usb 1-5: New USB device found, idVendor=0bda, idProduct=2838
[ 1.431005] usb 1-5: Product: RTL2838UHIDIR
[ 6.245292] IR NEC protocol handler initialized
[ 6.284327] IR RC5(x) protocol handler initialized
[ 6.338049] IR RC6 protocol handler initialized
[ 6.371470] IR JVC protocol handler initialized
[ 6.448155] IR Sony protocol handler initialized
[ 6.590577] lirc_dev: IR Remote Control driver registered, major 252
[ 6.591144] IR LIRC bridge handler initialized
[ 7.085160] usbcore: registered new interface driver dvb_usb_rtl2832u
$ lsmod|grep dvb
dvb_usb_rtl2832u 111764 0
dvb_usb 18302 1 dvb_usb_rtl2832u
dvb_core 77682 1 dvb_usb
rc_core 18294 7
dvb_usb,ir_lirc_codec,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,ir_nec_decoder
i2c_core 23876 7
dvb_usb,max6650,radeon,drm_kms_helper,drm,i2c_algo_bit,i2c_piix4
usbcore 119731 5 dvb_usb_rtl2832u,dvb_usb,ohci_hcd,ehci_hcd
but apparently no device files are created (there is no /dev/dvb tree).
Any suggestions for things to try to get this working welcome.
Regards,
Arthur.
next reply other threads:[~2011-07-02 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 7:06 Arthur Marsh [this message]
2011-07-02 20:23 ` Fwd: 0bda:2838 Ezcap DVB USB adaptor - no device files created / RTL2831U/RTL2832U Jan Hoogenraad
2011-07-03 2:47 ` Joel Stanley
2011-07-03 4:13 ` Arthur Marsh
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=4E0EC37F.1010201@internode.on.net \
--to=arthur.marsh@internode.on.net \
--cc=joel@jms.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.