Problems with Hauppauge driver
I've been using Satdreamgr in flash with a Duo2 receiver and Hauppauge Wintv 850 usb tuner for a while. Problem is the Hauppauge driver does not recognize my Wintv 850 usb tuner. I've installed and uninstalled it many times to no avail.
The only way I can get the usb tuner to work correctly is to:
opkg update
opkg install kernel-module-cx231xx-dvb
opkg install kernel-module-cx231xx-alsa
opkg install kernel-module-cx2341x
opkg install kernel-module-cx231xx
opkg install kernel-module-lgdt3305
opkg install kernel-module-tda18271
opkg install kernel-module-tda18271c2dd
reboot
Then once rebooted, I have to select enigma restart from the standby menu. Once the gui reboots, the usb tuner is recognized and everything works properly. Anotherr problem is, should the receiver be shut down over night, once rebooted the usb tuner is not recognized unless an enigma restart is selected from the menu. Then, the usb tuner works perfectly.
For general information, I tried VIX since it has the Hauppauge driver available in the plugins. Once installed it did not recognize the usb tuner. Tried the opkg install routine and it would not install due to "unknown package and cannot install errors".
Also tried ATV and the Hauppauge driver did recognize the usb tuner. The tuner is listed under Tuner Configuration menu as enabled, but it will not allow the atsc settings to be configured. I tried the opkg install routine and received "unknown package and cannot install errors". I did install the atsc.xml file in to /etc/tuxbox in both instances.
Any thoughts on how to get the Hauppauge driver in Satdreamgr to recognized the usb tuner and not have to keep using the enigma restart?
Thanks.
Απ: Problems with Hauppauge driver
Hi,
As you can see here: https://www.linuxtv.org/wiki/index.p..._WinTV-HVR-850 the 850 has three flavors.
We can include the missing depends, in order 850 to installed automatically.
Now regarding the issue you are mentioning, we need to provide some logs after reboot and after restart of enigma to try figure out what is going on.
Code:
dmesg
lsusb
cat /proc/bus/nim_sockets
dvb-fe-tool -a 1
If command dvb-fe-tool misses you need to install v4l-utils (opkg install v4l-utils).
Re: Problems with Hauppauge driver
Thank you for the quick response.
From the pachaging material the Wintv 850 is a model 1230.
Attached is the putty log file. Forgot to mention a big thank you for the atsc epg addition.
Απ: Problems with Hauppauge driver
There are some errors in the log like :
Code:
cx231xx #0: Changing the i2c master port to 1
cx231xx #0: Reloading firmware for XC5000
cx231xx #0: UsbInterface::sendCommand, failed with status --32
__tda18271_write_regs: [6-0060|M] ERROR: idx = 0x5, len = 1, i2c_transfer returned: -32
tda18271_init: [6-0060|M] error -32 on line 832
cx231xx #0: XC5000 firmware download failed !!!
Is enigma2-plugin-drivers-atsc-usb-hauppauge install as well?
Re: Problems with Hauppauge driver
My mistake, I forgot to uninstall the hauppauge 950 and 955 driver and will resubmit a putty log.
Re: Problems with Hauppauge driver
Here's the putty log with no Hauppauge drivers installed from the plugins>drivers section.
Απ: Problems with Hauppauge driver
I think the driver takes too long to get recognized, enigma2 when runs needs the devices recognized, if the tuner comes later Enigma doesnt know his existance, so a restarting of Enigma recognizes the tuner.
In enigma2.sh script you can add those command with logging (command >> /tmp/debug.log).
Can you add those commands with debug to file, in order to see what Enigma sees when stats?
Re: Problems with Hauppauge driver
Started from a cold boot.... attached are the logs.
Re: Problems with Hauppauge driver
Here's the debug file with commands.
Απ: Problems with Hauppauge driver
According to this the ATSC tuner is available when enigma2 starts.
Code:
NIM Socket 4:
Type: ATSC
Name: Hauppauge Device
Frontend_Device: 4
So on cold boot the device is not displayed on tuner list?
It's really strange, I cannot figure out what is wrong then.
Edit1.
On the other hand the from first debug log the ATSC misses.
Code:
root@vuduo2:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-S2
Name: Vuplus DVB-S NIM(AVL6222)
Frontend_Device: 0
I2C_Device: 2
NIM Socket 1:
Type: DVB-S2
Name: Vuplus DVB-S NIM(AVL6222)
Frontend_Device: 1
I2C_Device: 2
NIM Socket 2:
Type: DVB-S2
Name: Vuplus DVB-S NIM(AVL6222)
Frontend_Device: 2
I2C_Device: 4
NIM Socket 3:
Type: DVB-S2
Name: Vuplus DVB-S NIM(AVL6222)
Frontend_Device: 3
I2C_Device: 4
root@vuduo2:~# dvb-fe-tool -a 1
Device LG Electronics LGDT3305 VSB/QAM Frontend (/dev/dvb/adapter1/frontend0) capabilities:
CAN_8VSB
CAN_INVERSION_AUTO
CAN_QAM_64
CAN_QAM_256
DVB API Version 5.10, Current v5 delivery system: ATSC
Supported delivery systems:
[ATSC]
DVBC/ANNEX_B
root@vuduo2:~# exit