Posts by marc.bau

CvH After a few days of testing your latest build with kernel drivers only the issue seems to be half resolved for me after a year. I have seen artefacts only once on TV.

• The "Transport errors" are 0 with your build; with official LE releases it was increasing and seems to have caused a lot of issues.
• The "Continuity errors" are still there e.g. 20, with 7.90.010 it was still 0 after weeks of runtime.

I hope this remaining bug can be resolved, too. I have no idea what you make different to official LE releases, but this changes should go into official releases ASAP.

Could you also refresh with Kodi 17.6 aka 8.2.1, please?

I installed every alpha until 7.90.10 and all of them worked well. The first broken version was the version after 7.90.10. That was the first beta1 as I remember.

Aside bridge the bridge card... not mine.

Sure, so you changed labels. Nothing I can do in setup or that is done automatically by setup if a conflicting label has been found.

The UUID would be much safer and is the defacto standard.

I do not think this is ddbridge. The bridge as I know is a 1 year newer card. The ngene18 driver is used for my card as I know.

I‘m only aware that the vendor of the chip on my card has discontinued further development. The vendor also do no longer provide updated and support to dd. However this does not mean the card / driver itself no longer works. It just do not get new features.

The continuity errors are caused by something different and have been introduced after 7.90.10.

Quote from CvH

pls try if this image works better for you because that card should not have that problem here described

LibreELEC 8.x images for additional dvb drivers

could you also pls test my image if the new drivers change anything ?

I‘m on DD Cine S2 v5.4. The other DD drivers seems not working with my card. I guess they are for v6.0 or 6.5 and later cards that are embedded in kernel 4.14 and later. At least not as click and forget replacement. Switched back to kernel default drivers.

Continuity errors persist with this image, but maybe less than before. Htsp also has 2 errors (localhost tvheadend).

Installed LibreELEC-Generic.x86_64-8.2.0-dvb-1.1.img.gz and after selecting Digital Devices drivers tvheadend stopped working. After the reboot tvheadend client got no connection, what means tvheadend was dead. Switched to latest kernel 8.2 drivers and it worked again.

In have a DD Cine S2 v5.4. The driver for this v5.4 card is embedded into the kernel for years. tvheadend runs locally on the htpc.

I have not checked if tvheadend had shown other cards with this driver as it was written that my old config still works.

Continuity errors still exists. After 30 minutes I see 8 continuity errors, no transport errors yet and on hstp (localhost connection) i see two errors.

With 7.90.10 I always have 0, after hours.

Great. Please explain how you solved this boot issue.

CvH I understand that buying hardware is not the best solution, but how about ordering on Amazon, debug the issue and send it back within the first 30 days? So it would be free of charge for you. I guess most people here are not qualified enough to debug a kernel issue.

Thanks for feedback. Good to know.

Maybe just not tested. I can assure it works without issues on my system with a DVB-S2 card.

CvH I only have Digital Devices Cine S2 v5.4 (DVB-S2 card), but exactly the same issues.

Quote

Unfortunately Tvheadend does not provide an automatic upgrade or configuration export/import process so 4.0 users must perform a new installation of Tvheadend 4.2. This is inconvenient, but there is no other option.

This information seems incorrect from my point of view. I have found out that a migration is possible and not difficult. With thousands of channels and a complex configuration people should not get told there is no way to upgrade if this works.

Please see How to migrate tvheadend settings from 4.0 to 4.2? for a how-to. I'm not sure why you document this incorrectly. Can you fix this incorrect information or explain what is not working if I may missed something serious, please?

Looks like I need to wait for DVB issue since LE switched to kernel 4.9.x to be fixed first. Than I will buy this killer card DD MAX S8. Not sure when LE 9 will be released. So it helps me nothing to switch to 4.14+ now, if I still see artefacts what makes TV useless. Once this is done I'm willingly to sponsor this driver inclusion for LE 8.2. Until then I'm stuck at 7.90.010.

Do you have more than one disk with LibreELEC installed in parallel? I guess you have one disk only.

DVB issue since LE switched to kernel 4.9.x may be a duplicate.

I'm also on x86 generic build with of 8.2 and have this issues. Latest working official release was 7.90.10 that had already a 4.9.0 kernel. After this release LE was not usable anymore. I tested with every release up to 8.02 and than stopped testing. Now tested again with 8.2 on a brand new install and things improved a bit, but the bug is still not solved. I see artefacts on SD channels, too.

I already reported this in TV broken in v7.95.1 and later / artefacts on all channels where nobody answered at all. Thanks.

I'd also like to test with older kernel 4.8 if this solves the issue.

Digital Devices Cine S2 v5.4, Unicable, Intel Atom, 7.90.10 runs fine.

Labels are extreme risky. This can destroy a system. It boots from sdb1 and mounts sda2 with userdata, but needs sdb2.

If the big linux distributions use UUID than I think there are good reasons for this. However i‘m not aware of all the reason, but the issue I faced is a clear prove.

Still an issue on 8.2

Per kernel release notes Digital Devices drivers for Cine v7 and Max8 have been added to linux kernel 4.14. Please see Home · herrnst/dddvb-linux-kernel Wiki · GitHub.

Can you upgrade to add these important TV card drivers, please?