did you tired
modprobe em28xx card=94
echo "2040 8268" > /sys/bus/usb/drivers/em28xx/new_id
if it works afterwards ? (reboot resets this settings)
Posts by CvH
-
-
as long nobody does the drivers there is not too much we can do
thats the downside of old device kernels (7 years old) that have no proper support "upstream", you can throw away your device because it doesn't work anymore with newer stuff
same will happen with every new device that just ships some bsp kernel and has no upstream drivers available
-
https://wiki.libreelec.tv/how-to/add-firmware
then check dmesg if the version of the fw file really changed (firmware name loaded or similar should appear somewhere at dmesg output)
-
nobody from us uses facebook so we closed it some time ago
-
yea isn't fixed yet
-
TBS devices suffer proper kernel drivers for ages so expect to compile you own drivers for a long time.
So if you search "just works" choose the WinTV one.
The often recommend Dvbsky S960 was rereleased with different hardware under the same name, I am not sure they work at linux yet.
-
can you show a dmesg outbut before you reboot ?
dmesg | paste
-
for testing PROJECT=Generic ARCH=x86_64 scripts/build mc may help
-
there are pretty nice kind of cli browsers that support whatnot but they require a lot heavy dependencies for limited features
MAYBE docker + chromium is a way (there should be a topic in the forum about that)
-
tvheadend42: update to 4.1.2401 · LibreELEC/LibreELEC.tv@5fe3eb7 · GitHub
that was the change that was required to build it, so not sure if there has something changed till then
-
if it depends at this problem (i am not 100% sure) then its not fixable
-
its likely due the fact we are running chrome un-sandboxed and as root
-
it is very likely due that ffmpegx: disable nonfree - Tvh and ffmpeg-tools update by CvH · Pull Request #3164 · LibreELEC/LibreELEC.tv · GitHub
we can't revert that at the moment (there are future changes at OpenSSL that would allow us to use it again), the licence prohibit to share binaries that are build in that combination
you can build Tvheadend with that line changed and it should work, but you better do not share the file
-
And isn't an SSD drive pretty much the same soeed as SD cards?
SD cards are typical a lot slower (especial at multiple random read/write operations) compared to SSD.
This is quite noticeable at big libraries.
-
The simplest way of CLI access is via remotely logging in using SSH.
or you install the ttyd web terminal addon and use it at the browser
-
We use a different (much older) Kernel for LE9.2, there a all-in-one patch made it work (parts of it are already merged at 5.10).
Now we are at 5.10, at 5.11 the drivers where official added - but its not enough that I added the patch from this thread, there is something else needed I have no idea about.
I could spin up another build, easy peasy but currently no idea what to add.
-
problem with the alpha of tvheadend 4.3?
nope, the drivers are not listed so basically the drivers are not up
as long no drivers are working Tvh cant do anything
-
We saw that before, most of the times it was a problem with the SD card (the one or the other way).
Try a SD card writing software that verify that everything is correctly written to SD card - balenaEtcher.
If this is not working try a different SD card. Borderline power supplies can have similar effects.
