Posts by petediscrete

This is October 2022 and I’m wondering if anyone successfully installed this unit in LE. I’m using LE10.02.3 on a RockPro64 and the unit is recognised on boot but no front end is loaded.

The board is marked SU3000 V3.0 111024 so obviously it’s the V3 version. From previous posts here I’ve seen the following

download firmware from here dvb-demod-m88ds3103.fw

rename from dvb-demod-m88ds3103.fw to dvb-demod-m88ds3103b.fw and copy to /lib/firmware

this works on current kernels...

Is this instruction relevant now. Did anyone actually get the V3 version working in LE.

I already have a TVH setup via a PCIe tuner in a PC. This was something I wanted to get working purely out of curiosity. I’ve had USB DVBS tuners in the past and most of them failed owing to heat problems.

Remember what the Raspberry Pi Foundation’s aims and aspirations were from the outset, availability and affordability of computing for all. Clearly that objective has changed somewhat and that coupled with the proliferation of alternative single board computers from other manufacturers you may well not see an RPI5. I imagine they will concentrate more on project building from an educational perspective and producing boards accordingly. Items like kits and the Pico. Remember the introduction of the original RPI had unintended consequences in that the demand from industry outstripped the demand from the education sector.

Just installed TVH 4.3 Alpha from the repository on a RockPro64 (RK3399) on LE10.0.2 official (it was so simple, thanks guys). Configured IPTV to test and everything is working fine.

I want to add a USB DVBS tuner to the RockPro64 now. I’ve read quite a bit about the adventures of others trying to get their USB tuners to work. I’m wondering if anyone has any suggestions what tuner would be the simplest to configure on this board using LE10.0.2. I currently have a MyGica HDStar DVBS2 boxed I bought a while back so I’m going to try that first. In the event it doesn’t work would anyone have any suggestions on an alternative.

Thanks !

I assume you are seeing these messages at boot time only. How familiar are you with Linux. What you are seeing is the Linux bootloader doing its job. Those messages are usually suppressed using quiet and splash. I’ve no doubt your system is fine as you have no LE log errors.

If you really are desperate to capture those messages read all about how it is generally achieved here https://www.cyberciti.biz/faq/debian-ubu…-boot-messages/

Take what’s been offered. With what you save get yourself an external usb DAC. Something like a Cambridge Audio DAC Magic100. I have one and LE recognises it as a Class 2 USB device straight out of the box. Sound is amazing too.

Quote from Nekromantik

5e

Its fine on Pi OS but not on LE so not cable

That may be but the cable quality may not be up to standard. Spurious results on different OSes would be a true indicator.

Before ruling out an Ethernet cable issue try a different Cat5e Ethernet cable. If you did have Cat6 to hand I’d try that too. It could save you a lot of troubleshooting.

What’s the Cat rating on your Ethernet cable.

Here’s a good starting point https://ubuntu.com/tutorials/how-…pi-4#1-overview

As soon as you have it up and running you can install Kodi quite easily. Report back if you’re having any difficulty. This should allow you to fully test your drive in a Linux environment as you have many disk tools available to you using this method.

Just curious if you tried the full RPI OS install or possibly one of the Linux Distros and connected the 6Tb drive directly to the RPI4. If so what does the system report. Possibly try installing Ubuntu and Kodi as an experiment and see what results it reports.

Wrong link above. Micro SD extension cable of course.

https://cablematic.com/en/products/mi…tAaAjdPEALw_wcB

They can be found from many different retail outlets.

I managed to revive the on board sd card reader by sliding a thin piece of card in with the sd card into the sd card reader on the non contact side of the card. It managed to retain the sd card in place so it could be read. I then removed the card and followed the same procedure using the piece of card on the contact end of the extension cable. Permanent fix now.

Here’s a quick how to video

You could try getting one of these working in the slot in case your slot is failing. No more swapping in/out on the main board card reader. https://www.amazon.co.uk/Adapter-Extens…405058951&psc=1

It pays to walk away and revisit the problem when your mind is clearer. I knew you’d get their eventually. Glad all is good now. Patience is a virtue particularly in computing.

LibreELEC is rock solid so I knew the problem didn’t lie there.

I’ve laid out some simple steps above that should help others who are struggling with getting the Kodi add on working in any Kodi distribution.

1. Go to https://console.developers.google.com/
2. On the top left beside the words "Google APIs" click the project dropdown on the right
3. Ensure that your correct project is selected
4. Click "OAuth consent screen" on the left side of the screen (below "Credentials")
5. If you have not created a consent screen, do that first
6. Under "Test users" there is a button called "+ ADD USERS"
7. Type the email of the account you will be testing with, press enter, then click save.
8. It should work now!

This might help you.

YouTube Plug-in Thread

I have to admit I’ve never had any issue running YouTube Kodi add on and I’m using it on Kodi Windows, Linux, Android and LibreElec

With copy/paste you may be pasting unwanted characters from the browser into the credentials field in the YouTube Kodi add on. It’s not particularly nice but to rule that out try manually entering the credentials fields in the Kodi YouTube add on.

You may want to create a plain text file with your API credentials which you can use to directly copy/paste from to avoid this happening.

Highlight the recording and right click on it.

So your backend server TVH and your LibreELEC TVH frontend client are on the same machine. Is that correct.

I suggest disabling all your EPG grabbers and then enabling them one by one to see which one is responsible for the crashing. What priority is each grabber assigned.