The function of that CEC is very limited to what you see at the screenshot, the other cec pins are basically not even there
Pls make sure you buy a card that fits your region (idk)
You need ATSC at the USA and you need DVB-T/T2/C at europe !! DVB-T/T2/C is not compatible with ATSC etc ... !!
Otherwise don't buy any RTL... DVB stick, just crap - also heavily outdated.
If you are located at europe you want an DVB T2/C stick, at the USA an ATSC stick.
DVB-T is basically outdated, some countries still use it - make this clear before
Everything you linked above is basically cheap crap
Try to look after Hauppauge WinTV-soloHD or Hauppauge WinTV-dualHD - they are rather cheap and well supported.
The reasons for this were what I didn't understand...
Zram makes ZERO sense at a typical LE workload and even worse it has an negative impact.
LE doesn't support swap memory
ofc i does
so you just need to activate it via some conf (sry forgot how it worked)
Just to be clear, this is NOT a CE forum, this is not a CE topic and this development has nothing in common with CE at all (completely different codebase).
It is not helpful that we have every month those useless discussions and spamming this development thread with stuff that has completely off topic from the usual guys. As this happens regular and the usual approach "common sense" didn't worked out, we are removing now everything without a warning or explanation that does not fit into this topic.
If you want to talk about CE:
- try the CE forum
- open a new thread here
there are different DVB standards,
DVB-T/C/S/S2 basically everywhere besides US and Brazil
So first thing is to ensure you need ATSC because you have a ATSC stick.
Second thing is that the log looks basically okay, driver is loaded okay.
That nothing is found could have several reasons, mainly wrong settings.Could you try an "blank" scan at Tvheadend without any preselected frequencies if something turns up?
MAYBE it is a driver problem, idk know.
There were a lot fixes for Hauppauge devices since the release of the kernel we are using. MAYBE this fixes something, you could try a Mihouse build if it works there (warning Kodi 19 PRE ALPHA and downgrade is not really possible) so make a backup.
you need to manually do it, autoupdate from major to major version has proven to be not 100% waf save
You can also try the web ssh addon from the repo, just install and start it.
Then you have a terminal at you browser
Uff the driver crashes
Pls unpluck the stick and reboot, plug it back in and redo the dmesg paste command
Also do you use a USB hub or something?
you need to wait for a new image, can't tell you an exact date but can't take too long
basically the addon hasn't updated yet, you can force the update at the Kodi repo settings (left menu)
WinTV-soloHD or WinTV-dualHD reported as working okay, no idea if they work well at RPi4 (but likely they do)
it is a Kodi bug that is already fixed and should arrive our nightly builds soon
milhouse builds LibreELEC Testbuilds for RaspberryPi (Kodi 19.0)
dmesg looks okay so likely the support is not there at that version, I would try a build from ^^^
if it does not work pls share an dmesg | paste again
btw make backup !!! you can't downgrade
The not that good usb hw at the RPi combined with a not that good usb hw at the dvb device creates random problems. The commands above disable some fixes at the kernel that has usually working well at proper hw.
So it's a bit hit and miss.
But great to hear that it works.
Do you use an Raspberry Pi ?
you could try to add dwc_otg.fiq_enable=0 dwc_otg.fiq_fsm_enable=0 dwc_otg.nak_holdoff=0 to your cmdline.txt at your SD card
pls make a backup from the cmdline.txt before !
not sure I can follow
we have Tvheadend 4.2 server at our addon repo
if you need Tvheadend server 4.3 (developement version) you can have a look at my signature for builds
the pvrnext server is now avaible at linux, I was not aware of it
this is not at our repo, meanwhile you could use docker for it - if needed