Posts by chewitt

Quote from thebakker

No, still the same error as user burny02 has. But like chewitt says, it probably isn't possible on the pi4 without sudo

LE runs everything as root and I've known that for more than a decade, so I have never said sudo is required.

Quote from DereC

so what is needed? device drivers source so it could be compiled on new kernel? or?

Someone needs to write a V4L2 compatible demux driver; all the other pieces (tuner drivers, demod drivers, firmware) exist (although not in the upstream kernel). This has been the status-quo for about four years so I wouldn't hold breath on it happening anytime soon.

Quote from DereC

quess i dont fully understand problematic, but is it possible to use work of alf1? GitHub - afl1/dvb-firmware

No, it's entirely based on the legacy kernel, which is the wrong kernel. That repo is also incomplete, buggy and abandoned.

The only reason I still technically have a FB account is to cybersquat the LE page, which I marked hidden because there were too many twats determined to talk about piracy add-ons and spam posts for VPN services, and I couldn't be arsed to spend the time moderating the swamp it was turning into (typical for FB). If anyone else on the team ever admits to having an account I'd be happy to transfer it to them .. but so far nobody raised their hand.

I pushed my most recent efforts to this branch Commits · chewitt/usb-sd-creator · GitHub .. I was able to pick changes from the UNRAID fork of the creator app heree GitHub - limetech/usb-creator: unRAID USB Flash device creator which allowed it to build/work on Catalina (aside from the usual errors you get from not being a paid-up/registered Apple dev) until a recent macOS security update. It now starts, shows the GUI, then throws an error and exits. I've no idea why or how to proceed further.

The moment we provide a "limited" browser there will be a long line of pitch-fork waving villagers whinging that it doesn't support X/Y/Z website they watch videos from. No browser generates fewer support threads than wrong browser (sadly).

The rtw88 driver in the upstream kernel is under active development and has been adding support for 8822* chips, but I'm not sure what state things are in with the 5.10 kernel used in LE10, it might need something a bit newer to have things work.

DKMS solves a different problem. It allows you to recompile the driver to match the kernel - but it assumes the driver can be compiled for the kernel in the first place. LE's problem is that we frequently bump to the latest kernel and this results in drivers that simply do not compile on the target kernel version. Over time (and multiple drivers) you get rather bored of reinventing this wheel.

See if Dropbox - LibreELEC.USB-SD.Creator.macOS.dmg - Simplify your life works for you. It's a version that I built that worked for me under Catalina until a recent update, and since then it crashes (which is why it's never been shared widely). You might get further on the older OS version though.

Re known status .. I appear to be the only person on the team who gives a fcuk about it, and I don't code so my options for 'fixing' it beyond a bit of patch picking from a downstream fork of the app code is rather limited. I've rather given up on trying to entice/lure others to care about it and I think we'll just have to bin the app completely. That will suck, but .. nobody else is lifting a finger so it will be the inevitable conclusion.

You have installed LE via the Pi Foundation NOOBS installer; this installs the NOOBS environment and the files needed to run LE on-top of the NOOBS environment. NOOBS is not required, so all you need to do is download the LE 9.2.6 image for RPi2 and write this directly to the SD card using any SD image writing tool. Then you will boot directly into LE without NOOBS.

Quote from coolman

Hl!

Sorry for offtop.

I looking for dualboot script for amalogic s812 (tronsmart mx iii)

(on 4pda and freaktab exist the links on this file, but they are is the dead )

Big thank for any help

No idea what you're talking about

The problem with autostart is, it runs right at the start of userspace boot which is typically before everything else (including your scripts) ever gets touched. Best is to add some "logging" to your scripts (sending to /dev/console as described above) but schedule the scripts via systemd so they are ordered correctly in the startup sequence.

IIRC you will need to place a Font that contains the appropriate symbols into /storage/.kodi/userdata/Fonts/ and then select the font in the Kodi GUI. If you think it should be a permanent thing, open up a bug report in the Kodi forums and as their devs to add the missing symbols for whatever language it is (you didn't say) to the default Estuary font; and then we will pick up the inclusion in a future release.

Thanks for pointing out the dead links. I recently added some cushions, an alternative 'graffiti' t-shirt design, and need to finish off the listings for some coffee mugs off at some point this week. Exciting stuff

1. Write LE image for RPi2 to SD card

2. Insert SD card in RPi2

3. Boot RPi2

4. Enable SSH in first run wizard (gives CLI that you don't need)

5. Leave Samba enabled in first run wizard (it's embedded, no need to install it)

^ Notice there is no mention of NOOBS, which is not needed or required.

That should be all that's required, although it's a couple of years since I tested it. Check the routing tables and such.

Please rRetest with LE 9.95.2 or a currently nightly. If the issue is still present, report it to Kodi devs via their issue tracker on GitHub or via the forums as it's not an LE issue. If the issue isn't present .. you have a solution. There will be no more LE 9.2 releases so not much point/interest in bug reports there now.

dag There are probably no objections among the team to adding packages into the build-system to facilitate debugging when a DEBUG image is built, but they will not go into release images where 99.999999% of our userbase will never use them. I suspect you'll need to use a debug image anyway since we strip the binaries in release images.

Also worth pointing out that 4K HDR is 90% functional already; 4K@60 still needs work (but there is not much media in that refresh rate) and 10-bit/12-bit are still WIP, but 8-bit output is more than watchable.