View Full Version : [SF8008] RTL2832 Drivers
I've done a fresh flash using image 5.3.016 on an SF8008 and installed the drivers (RTL2832) from the plugin menu for a USB-DVB-T stick. The stick is recognised ok.
Whenever I attempt to scan channels the VIX icon spins continually until the box is rebooted.
Just as a comparison I have loaded image 5.3.016 on an vu+solov2se and installed the drivers (RTL2832) from the plugin menu for the same USB-DVB-T stick and it works fine.
I'm thinking the problem is the arm box vs the mips box?
What's the best way to view and report the crashlog?
What's the best way to view and report the crashlog?It sounds as though it's looping rather than crashing, so there will be no crash log.
Sending a debug log may provide some info, but also the dmesg and messages files from /var/log.
Thanks for that, I have attached both the messages file and the dmesg file.
Interestingly if I disconnect the DVB-T antenna but leave the DVB-T USB device in the box, then it scans through OK (obviously doesn't pick up any channels).
If I connect the antenna lead half way through a scan the software starts looping.
According the the messages file it appears to be looping when it gets to 1435.5 MHz.
But it should never get there - the UK DVB terrestrial channels have never gone beyond 900 MHz.
Are you doing a "full" scan, rather than configuring your transmitter and scanning the (up to) 8 channels actually in use?
What is your actual tuner setup?
Have you disabled the internal DVB-S tuner(s)? It seems to be those that are looping (si2166 chipset)?
What is your actual tuner setup?
Have you disabled the internal DVB-S tuner(s)? It seems to be those that are looping (si2166 chipset)?
I have 1 X Sat cable going into the tuner B (DVBS2) and the one Terrestrial cable going into the USB DVB-T Tuner.
OpenVix is configured so that Tuner A (DVBS2) is disabled.
I have tried doing a full scan and also just sending over my current DVB-T cahaanles using dremboxedit.
I'm from Australia and so am using this file (which I use in other E2 boxes):
<?xml version="1.0" encoding="UTF-8"?>
<!--
Countries sorted by two letter country code (ISO 3166-1).
Regions sorted alpabetically.
Transponders sorted by frequency.
system:
0 = DVB-T
1 = DVB-T2
bandwidth:
0 = 8 MHz,
1 = 7 MHz,
2 = 6 MHz,
3 = Auto (unsupported, default)
constellation:
0 = QPSK,
1 = 16-QAM (default),
2 = 64-QAM,
3 = Auto
code_rate_{lp,hp}:
0 = 1/2,
1 = 2/3,
2 = 3/4,
3 = 5/6,
4 = 7/8,
5 = Auto (default),
6 = None
guard_interval:
0 = 1/32,
1 = 1/16,
2 = 1/8,
3 = 1/4,
4 = Auto (default)
transmission_mode:
0 = 2K,
1 = 8K,
2 = Auto (default)
hierarchy_information:
0 = None,
1 = 1,
2 = 2,
3 = 4,
4 = Auto (default)
inversion:
0 = Off,
1 = On,
2 = Auto (default)
flags:
1: Network Scan
2: use BAT
4: use ONIT
8: skip NITs of known networks
and combinations of this.
Please report missing frequencies and pointers to regional standards to
https://github.com/oe-alliance/oe-alliance-tuxbox-common/blob/master/src/terrestrial.xml
-->
<locations>
<terrestrial name="Australia, all regions(au) (DVB-T/T2)" flags="5">
<transponder centre_frequency="177500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="184500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="191500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="198500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="205500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="212500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="219500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="226500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="529500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="536500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="543500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="550500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="557500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="564500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="571500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="578500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="585500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="592500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="599500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="606500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="613500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="620500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="627500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="634500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="641500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="648500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="655500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="662500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="669500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="676500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="683500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="690500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="697500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="704500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="711500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="718500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="725500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="732500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="739500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="746500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="753500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="760500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="767500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="774500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="781500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="788500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="795500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="802500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="809500000" bandwidth="1" constellation="3"/>
<transponder centre_frequency="816500000" bandwidth="1" constellation="3"/>
</terrestrial>
</locations>
Hmmm...the si2166 is running as "Build Option: Si2183_B60_COMPATIBLE", so can handle DVB-T2.
However, my suspicion is that there an issue with the virtual tuner set up:
Feb 21 21:45:53 sf8008 user.err kernel: vtunerc0: unknown IOCTL 0x3
Feb 21 21:45:53 sf8008 user.err kernel: vtunerc0: unknown IOCTL 0x4
Feb 21 21:45:53 sf8008 user.err kernel: vtunerc0: unknown IOCTL 0x6
Feb 21 21:45:53 sf8008 user.err kernel: vtunerc0: unknown IOCTL 0x5
Feb 21 21:45:53 sf8008 user.warn kernel: vtunerc0: usb frontend initialized as type=0but I have no idea as to what that would be. Sorry.
Hmmm...the si2166 is running as "Build Option: Si2183_B60_COMPATIBLE", so can handle DVB-T2.
However, my suspicion is that there an issue with the virtual tuner set up:
but I have no idea as to what that would be. Sorry.
OK, cheers for the help.
I tried the usb tuner on another SF8008 with current version openvix today and it does the same thing. I might post this in the SF8008 forum.
abu baniaz
24-02-20, 08:17
Try another image, it could be the drivers.
Try another image, it could be the drivers.
Hi, yes it works properly if I use openatv but I'd prefer to use openvix if I can.
Is there any information or files I can pull out of openatv to help?
Which OpenATV image 6.3 or 6.4????
Which OpenATV image 6.3 or 6.4????
OpenATV image 6.3 works OK.
I currently have 6.3 running with the usb tuner in it if you would like me to get any further information.
Whats in /etc/vtuner.conf on ATV and ViX???
Whats in /etc/vtuner.conf on ATV and ViX???
The only file I can find in ATV containing vtuner is vtunerc.ko in /lib/modules/4.4.35/extra
This Octagon SF8008 I am testing on now has 1 dvb-s2 and 1 dvb-T connections just fyi. The USB tuner i'm having issues with using this box and openvix but working in ATV is coming up in ATV as RTL2838UHIDIR in the tuner menu.
I will have to look at /etc/vtuner.conf in Openvix in the morning sorry.
59724
59723
Whats in /etc/vtuner.conf on ATV and ViX???
There is no file called vtuner.conf in the /etc directory of either image.
Any suggestions where or how to report this bug? Am willing to provide as much details as possible.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.