Posts by davidryderuk

    Hi Scummer,


    If your device is from 2014 then it will be using an earlier version of the 'M88DS3103 demodulator' chip so it won't be exactly the same issue. If you have still got access to kernel 4.15.0-45 with the CrazyCat drivers installed I'd try enabling the ds3k module's debug option (i.e. create a conf file in the '/etc/modprobe.d' directory with the line 'options ds3k debug=1'). It won't fix the issue, but it may provide a few more details. If you can find out when the device stopped working you may be able to work out what changes broke support for your device. I'd also try the most recent stable Linux kernel version without Crazycat's drivers installed (i.e. deb packages available from here).


    I sometimes get the 'dw2102: i2c transfer failed.' message. I think it has something to do with the USB connection being subject to a high load. Anyway, I'd try the following, if you haven't already:


    - Double check the device isn't plugged into a USB 1 port (you can use the 'lsusb -t' command if you are unsure).

    - Try not to plug the device into an external USB hub (at least until you've got it working correctly).

    - Reset the S4600 device before starting the computer (i.e. unplug the power cable, wait a few seconds and then plug the power it back in).


    Regards,

    David


    p.s.

    You'd also probably get more attention if you started a new thread, since it is a different issue.

    Sorry, I can only test it using symbol rates of 22000, 23000 and 27500 KSym/s. I have noticed a similar issue when transponders use Forward Error Correction of 3/4. I can tune into the transponder, but the feed is full of audio and visual distortions. My TV manages to tune into the same transponders without any issue, but it doesn't have any record function.

    I managed to download the media-build source code off bitbucket and compile it against the most recent Ubuntu 16.04 kernel (4.15.0-45). My DVB-S2 device is now working correctly on an Intel Atom Media PC, which is great. Thanks very much to crazycat ,@CvH and anyone else who helped get the device working.


    Just for the sake of completeness, I double checked the LibreELEC build I reported on in my last post. The build seems to match the one uploaded to Index of /test/ds3103b/. The kernel log also confirmed modules were being added from the 'kernel-overlays/driver.dvb.crazycat' folder. As before, I couldn't get the device to load.

    Hi CvH,


    I have a Geniatech HDStar device which I bought around March 2018. I've failed to get it working with Linux. I think it probably has the 3103B chip, but I'm not certain (see my earlier post here). I ran your build with the crazycat drivers and have attached the log. I couldn't see the adapter listed in TVHeadend, but I'm not very familiar with that software, since I normally use MythTV.


    Thanks,

    David

    Hi,

    I recently purchased a Geniatech HD Star device. Output from 'lsusb -v' is the same as that posted on linuxtv, however I've had some trouble getting it to work. I've tried compiling kernel 4.11 with the patch available here and mentioned here. I didn't have any issues compiling the kernel, but the device failed to load. I've also tried the Ubuntu Xenial 4.13 kernel and OpenELEC 8.2.5. In each case there has either been a null pointer error or 'no frontend was attached'. The device always seems to be in a 'warm state', so no firmware is loaded. The Windows driver shipped with the device is dated December 2017. The only thing which seems to work is the remote control. Is there any way I can check if this problem is due to the new 'M88DS3103B' demodulator chip? If so, is there any information I can provide which may help?


    Thanks,

    David