Archiv > Raspberry PI
RPI 2
noggin72:
OK :
DVB-T Dual Tuner Diversity : http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-TD-Stick
dmesg : http://pastebin.com/aiRfx21n
lsusb -v :
--- Code: ---Bus 001 Device 002: ID 0424:9514
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 0424:ec00
Bus 001 Device 004: ID 04d9:1203
Bus 001 Device 005: ID 05e3:0608
Bus 001 Device 006: ID 2040:9580
Bus 001 Device 007: ID 147a:e03e
--- End code ---
PCTV 290e DVB-T/T2 http://www.linuxtv.org/wiki/index.php/PCTV_Systems_nanoStick_T2_290e
dmesg : http://pastebin.com/j05NdXBt
lsusb -v :
--- Code: ---Bus 001 Device 002: ID 0424:9514
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 0424:ec00
Bus 001 Device 004: ID 04d9:1203
Bus 001 Device 005: ID 05e3:0608
Bus 001 Device 006: ID 2013:024f
Bus 001 Device 007: ID 147a:e03e
--- End code ---
August T210 DVB-T/T2
dmesg : http://pastebin.com/z64JUZPx
lsusb -v :
--- Code: ---Bus 001 Device 002: ID 0424:9514
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 0424:ec00
Bus 001 Device 004: ID 04d9:1203
Bus 001 Device 005: ID 05e3:0608
Bus 001 Device 006: ID 1f4d:d220
Bus 001 Device 007: ID 147a:e03e
--- End code ---
Hope this helps.
Think the DVB devices are Bus 001 Device 006 as they are the only devices that change? I have a USB powered hub and a Windows Media Center IR receiver plugged in, as well as a small keyboard.
pbriesch:
If you look at the output of dmesg then you will see lines with disagrees about version of symbol module_layout:
--- Code: ---[ 5.886695] i2c_dev: disagrees about version of symbol module_layout
[ 6.005365] uinput: disagrees about version of symbol module_layout
[ 6.096474] i2c_dev: disagrees about version of symbol module_layout
[ 6.186871] i2c_dev: disagrees about version of symbol module_layout
[ 6.280957] i2c_dev: disagrees about version of symbol module_layout
[ 6.963312] udevd[333]: starting version 175
[ 7.126178] i2c_bcm2708: disagrees about version of symbol module_layout
[ 7.180665] snd: disagrees about version of symbol module_layout
[ 7.357286] rc_core: disagrees about version of symbol module_layout
--- End code ---
The problem is that the kernel for raspberry pi 2 is different in regards to the earlier raspberries. The MLD team is working on this issue and will most likely come up with a special build for raspberry pi 2. As you experienced yourself the DVB drivers don't work right now.
You can see if the DVB driver works by typing
--- Code: ---MLD> ls /dev/dvb/adapter0/
demux0 dvr0 frontend0
MLD>
--- End code ---
If you get an error message then no DVB device was created.
Furthermore you can check if you look at the dmesg output for usb 1-5: DVB: registering adapter 1 frontend 0 (Afatech AF9013)...
--- Code: ---usb 1-5: new high-speed USB device number 4 using ehci-pci
Afatech DVB-T 2: Fixing fullspeed to highspeed interval: 16 -> 8
input: Afatech DVB-T 2 as /devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.1/0003:15A4:9016.0003/input/input7
hid-generic 0003:15A4:9016.0003: input,hidraw2: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-0000:00:1d.7-5/input1
WARNING: You are using an experimental version of the media stack.
As the driver is backported to an older kernel, it doesn't offer
enough quality for its usage in production.
Use it with care.
Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
dd0a6fe2bc3055cd61e369f97982c88183b1f0a0 [media] dvb-usb-dvbsky: fix i2c adapter for sp2 device
b6851419409664bc564ce5148bbec1141944c710 [media] m88ds3103: change ts clock config for serial mode
c29d6a83b3c14cf81a4c90a941eb923625192398 [media] cx23885: add DVBSky S952 support
experimental: 1969cdc5388b711e2aef3d1747b5f7dd1cd965f3 experimental/ddbridge: Fix 'inlining failed in call to always_inline ...: recursive inlining'.
v4l-dvb-saa716x: d7e98fc592305a600909003da2b7cc4338242511 saa716x_ff: Do not return on command ready timeout
usb 1-5: dvb_usb_v2: found a 'Afatech AF9015 reference design' in cold state
usb 1-5: dvb_usb_v2: downloading firmware from file 'dvb-usb-af9015.fw'
usb 1-5: dvb_usb_v2: found a 'Afatech AF9015 reference design' in warm state
usb 1-5: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
DVB: registering new adapter (Afatech AF9015 reference design)
i2c i2c-3: af9013: firmware version 4.95.0.0
usb 1-5: DVB: registering adapter 1 frontend 0 (Afatech AF9013)...
tda18271 3-00c0: creating new instance
TDA18271HD/C1 detected @ 3-00c0
Registered IR keymap rc-empty
input: Afatech AF9015 reference design as /devices/pci0000:00/0000:00:1d.7/usb1/1-5/rc/rc0/input8
rc0: Afatech AF9015 reference design as /devices/pci0000:00/0000:00:1d.7/usb1/1-5/rc/rc0
usb 1-5: dvb_usb_v2: schedule remote query interval to 500 msecs
usb 1-5: dvb_usb_v2: 'Afatech AF9015 reference design' successfully initialized and connected
usbcore: registered new interface driver dvb_usb_af9015
--- End code ---
So please be patient until the MLD team will have fixed this issue.
Regards, Paul
noggin72:
Would that be related to the i2c errors I posted in my earlier post?
Totally understand that it's early days though - good luck with the bug hunting!
pbriesch:
--- Quote from: noggin72 on March 07, 2015, 02:06:00 ---Would that be related to the i2c errors I posted in my earlier post?
--- End quote ---
Yes, it would.
noggin72:
Because I really want to trial VDR on a Pi / Pi 2 I tried the same 4.0.1 install on a Pi B (512MB) I also have.
The Dibcom-based Nova-T DT Diversity was recognised - but I don't think all is well.
dmesg : http://pastebin.com/EgJL2Y4K
ls /dev/dvb shows adapter0 as you would expect, but ls /dev/dvb/adapter0 only shows demux0,dvr0 and demux0 with no frontend0 - so there is something wrong there?
lsusb -v :
--- Code: ---Bus 001 Device 002: ID 0424:9512
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 0424:ec00
Bus 001 Device 004: ID 04d9:1203
Bus 001 Device 005: ID 05e3:0608
Bus 001 Device 006: ID 2040:9580
Bus 001 Device 007: ID 147a:e03e
--- End code ---
So even on a Pi there are issues at the moment with the current 4.0.1 build?
My PCTV 290e is recognised as a USB device, but not as a DVB-T/T2 tuner (the drivers for the 290e have been in the kernel since 3.0?).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version