openSuSE 13.1: Trouble with WinTV MiniStick SE

English Multimedia
1

Greetings!

I’m attempting to set up a WinTV MiniStick SE on my notebook, and although it is properly discovered by the USB subsystem, something goes awry here.

A dmesg | grep dvb produces the following output:


    7.277858] usb 4-1.2: dvb_usb_af9035: prechip_version=83 chip_version=02 chip_type=9135
    7.278226] usb 4-1.2: dvb_usb_v2: found a 'Hauppauge WinTV-MiniStick 2' in cold state
    7.300718] usb 4-1.2: dvb_usb_v2: downloading firmware from file 'dvb-usb-it9135-02.fw'
    7.414986] usb 4-1.2: dvb_usb_af9035: firmware version=3.39.1.0
    7.415008] usb 4-1.2: dvb_usb_v2: found a 'Hauppauge WinTV-MiniStick 2' in warm state
    7.418797] usb 4-1.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
    7.467816] usb 4-1.2: dvb_usb_v2: schedule remote query interval to 500 msecs
    7.467829] usb 4-1.2: dvb_usb_v2: 'Hauppauge WinTV-MiniStick 2' successfully initialized and connected
    7.467935] usbcore: registered new interface driver dvb_usb_af9035
    9.964719] usb 4-1.2: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110
    9.964734] usb 4-1.2: dvb_usb_v2: rc.query() failed=-110
[21718.836576] dvbnet[6022]: segfault at 1 ip 00007f6f51b07380 sp 00007fff64fd14

Something seems to go wrong at around 10 secs in the boot process, and I think that that makes any attempt in accessing the DVB-T stick moot (the error message of dvbnet seems to be symptomatic of this).

When looking at /dev/dvb/ I find the directory adapter0 containing these device nodes:
demux0
dvr0
frontend0
net0

However, no matter what I do (dvbsnoop, scan, etc.) I cannot access the stick.

Any ideas what could be going on here?

Any help would be greatly appreciated.

2

IMO this appears to be a Windows only device. It requires installing software from a CD in Windows so unless you can find some Linux software I doubt you will get it to work

3

At least it’s working here now. Don’t ask me why, but now the stick is working without problems (I haven’t changed anything, and somehow things went right after a second reboot).
I don’t know why it hiccuped earlier, but that problem seems to mysteriously have vanished. :question: