Gunah Posted September 2, 2018 Posted September 2, 2018 (edited) I am trying to get my Win TV Dual HD running at the Tinkerboard. But idk where the issue is Build my own Kernel ./compile.sh BOARD=tinkerboard BRANCH=dev KERNEL_ONLY=yes RELEASE=stretch ~# uname -a Linux tinkerboard 4.18.5-rockchip #3 SMP PREEMPT Sat Sep 1 12:50:32 CEST 2018 armv7l GNU/Linux ~# dmesg | grep em28xx [ 7.639731] em28xx 1-1.3:1.0: New device HCW dualHD @ 480 Mbps (2040:0265, interface 0, class 0) [ 7.639738] em28xx 1-1.3:1.0: DVB interface 0 found: isoc [ 7.702511] em28xx 1-1.3:1.0: chip ID is em2874 [ 8.835994] em28xx 1-1.3:1.0: write to i2c device at 0xa0 failed with unknown error (status=5) [ 8.836001] em28xx 1-1.3:1.0: board has no eeprom [ 8.889385] em28xx 1-1.3:1.0: Identified as Hauppauge WinTV-dualHD DVB (card=99) [ 8.889393] em28xx 1-1.3:1.0: dvb set to isoc mode. [ 8.941500] em28xx 1-1.3:1.0: chip ID is em2874 [ 10.076258] em28xx 1-1.3:1.0: write to i2c device at 0xa0 failed with unknown error (status=5) [ 10.076268] em28xx 1-1.3:1.0: board has no eeprom [ 10.129399] em28xx 1-1.3:1.0: Identified as Hauppauge WinTV-dualHD DVB (card=99) [ 10.129408] em28xx 1-1.3:1.0: dvb ts2 set to isoc mode. [ 10.331731] usbcore: registered new interface driver em28xx [ 10.334456] em28xx 1-1.3:1.0: Binding DVB extension [ 10.377391] em28xx 1-1.3:1.0: write to i2c device at 0xc8 failed with unknown error (status=192) [ 10.377441] em28xx 1-1.3:1.0: Binding DVB extension [ 10.416389] em28xx 1-1.3:1.0: write to i2c device at 0xce failed with unknown error (status=192) [ 10.416438] em28xx: Registered (Em28xx dvb Extension) extension [ 10.419913] em28xx 1-1.3:1.0: Registering input extension [ 10.421204] em28xx 1-1.3:1.0: Input extension successfully initialized [ 10.421210] em28xx 1-1.3:1.0: Remote control support is not available for this card. [ 10.421213] em28xx: Registered (Em28xx Input Extension) extension My Kernel-.config file: https://gist.github.com/mklooss/8f7192492a4c7d2545d7e0a2ee7e2a84 Saw this Commit on Github for sunxi https://github.com/armbian/build/commit/0d39b31811f93d9208bcd166072499b7e5766842 and i can confirm, on my cubietruck the Stick will working ;-) - with your builds from beta.armbian.com may the issues based on i2c, but could not find the issue yet. linuxtv Page for the DualHD Stick https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-dualHD May someone here can help me Thanks Edited September 2, 2018 by Gunah
Gunah Posted September 3, 2018 Author Posted September 3, 2018 some additional data: ~# dmesg | grep si2168 [ 9.363730] si2168 7-0064: probe failed = -5 [ 9.363759] si2168: probe of 7-0064 failed with error -5 [ 9.402447] si2168 9-0067: probe failed = -5 [ 9.402466] si2168: probe of 9-0067 failed with error -5
Gunah Posted September 3, 2018 Author Posted September 3, 2018 did not try it but i think i found the issue and why it works on the cubietruck https://github.com/armbian/build/blob/master/config/kernel/linux-rockchip-dev.config#L1436 https://github.com/armbian/build/blob/master/config/kernel/linux-sunxi-dev.config#L1534 Edit: okay its not only this flag, bcz the Firmware will only be loaded at the cubietruck but not on the tinkerboard :/
Recommended Posts