[linux-dvb] Hauppauge DEC-3000s

Heinz Wiesinger HMWiesinger at gmx.at
Mon Sep 10 14:30:52 CEST 2007


Hi!
I have a Hauppauge DEC-3000s at home, which should, according to the 
documentation, work under linux, at least for watching tv.
Now, as some other people already reported (some months ago)
this is actually not true. And I would like to help, finally fixing this.
However, all I can provide, is information.
With this mail, I give you all information I have at the moment.
First of all, initialisation seems to work. Dmesg reports the following:

[CODE]
usb 1-2: new full speed USB device using uhci_hcd and address 2
usb 1-2: configuration #1 chosen from 1 choice
ttusb_dec: Firmware 2.31<6>ttusb_dec: found DSP code "DEC2540-t".
usbcore: registered new interface driver ttusb-dec
usb 1-2: USB disconnect, address 2
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 1-2: configuration #1 chosen from 1 choice
DVB: registering new adapter (DEC3000-s).
DVB: registering frontend 0 (TechnoTrend/Hauppauge DEC3000-s Frontend)...
[/CODE]

The necessary files for dvb are there, so I guess the initialisation works, 
somehow.
I prefer using Kaffeine for watching tv, so I tried to scan for channels.
The resulting dmesg output:

[CODE]
ttusbdecfe_read_status: returned unknown value: 0
[/CODE]

and that about 15 times or so.
To also show, that it is not (only probably) caused by kaffeine, I used a 
shipped channels.conf from dvb-apps, and szap (20070816) to switch to 
ProSieben. Szap shows the following:

[CODE]
reading channels from file '/root/.szap/channels.conf'
zapping to 26 'ProSieben':
sat 0, frequency = 12480 MHz V, symbolrate 27500000, vpid = 0x00ff, apid = 
0x0100 sid = 0x0382
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
FE_DISEQC_SEND_BURST failed: Operation not supported
FE_READ_STATUS failed: Connection timed out
status 00 | signal fffe | snr fffe | ber fffffffe | unc fffffffe |
FE_READ_STATUS failed: Connection timed out
status 00 | signal fffe | snr fffe | ber fffffffe | unc fffffffe |
FE_READ_STATUS failed: Connection timed out
[/CODE]

and so forth. The coresponding dmesg output:

[CODE]
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusbdecfe_read_status: returned unknown value: 0
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusbdecfe_read_status: returned unknown value: 0
ttusbdecfe_read_status: returned unknown value: 0
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusbdecfe_read_status: returned unknown value: 0
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusbdecfe_read_status: returned unknown value: 0
ttusbdecfe_read_status: returned unknown value: 0
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusbdecfe_read_status: returned unknown value: 0
ttusbdecfe_read_status: returned unknown value: 0
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: Failed to lock usb mutex.
ttusb_dec_send_command: Failed to lock usb mutex.
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusb_dec_send_command: result bulk message failed: error -110
ttusbdecfe_read_status: returned unknown value: 0
ttusb_dec_send_command: result bulk message failed: error -110
[/CODE]

So this is all I have at the moment, but if someone is able to tell me, how to 
get more information, I'll do that.
However, I hope that this will bring some light in the current situation of 
DEC-support under linux.



More information about the linux-dvb mailing list