LE 9.2 should start public beta in a couple of weeks time.
Posts by chewitt
-
-
Test LibreELEC images with KODI-18 for S9xxx
Which will take you to:
https://yadi.sk/d/dhepyyrcterlf/leia-18/kernel_5.x/20190608/amlg12_odroid_n2_s922
Once the mainline project gets merged to LE master some proper nightlies will start. Audio is currently 2.0 (or 7.1 pass-through for AC3/DTS) and hardware decoding is mostly working .. no HEVC yet, and 4k needs further work once 10-bit video support. The other thread is tracking updates.
-
balbes150 chewitt Just one question!
is there a developer here to help and answer questions?
Thank God today there is a bridge called CoreELEC.
For here they only respond and help what is of interest to you.
More donation requests can be found throughout the forum.
If all is well they are all here.
As everything is wrong we will be hiding.
^ bad translation - I've no idea what point you're trying to make
-
If the NFS mounts are done via Kodi .. enable debug logging and share the log. If they are handled in the OS layer via systemd, share the systemd journal from a clean boot and after demonstrating the issue.
-
Is the Wetek Core generally capable of TrueHD bitstream output and I'm only have some wrong settings?
It's technically capable under Android but I forget whether it ever worked under Linux. I know we fixed the kernel audio presentation to Kodi under the 3.14 kernel but I'm not sure if the work was ever fully backported to 3.10.
-
Resizing partitions is normally slow and requires you to boot some other OS (e.g. Ubuntu) to use graphical tools like gparted, so most users will follow a backup > clean install > restore process. Have a look at MrChromebox.tech for the latest BIOS and quick-install routines for LE.
-
If you want to install LibreELEC on the devvice we can help. If you want to restore Android on it .. that's someone else's problem and you're asking for help in the wrong forum. I'm not trying to be awkward, but our expertise is all about erasing Android not installing and recovering it.
-
Tuner drivers are not installed.
If you (and the persistent +1/me-too tuner-using collective) want tuner drivers in mainline kernel images please petition afl1 to reach-out to the linux-amlogic kernel maintainers and start upstreaming them. It's the only way forwards. There are people who are willing to help/assist this activity.. but it's his code and responsibilty to initiate the process. As the saying goes "the ball is in his hands" (not ours).
-
Is hw decoding working on the N2 with mainline?
And how about hdmi audio and ethernet?
Yes .. with caveats for 4K and HEVC which have dependencies on 10-bit video work (which is now active work-in-progress again). HDMI audio is 2.0 at the moment but we've started looking into what's needed for multi-channel .. although bizarely 7.1 pass-through (AC3/DTS) also appears to be working as long as you set 'optimised' not 'best match' in Kodi. Ethernet is no problem.
-
I see both HK and Khadas as different shades of the same grey when it comes to software support. HK definitely have a more active user community around their products and some reasonable staff, but you can count the number of upstream kernel/u-boot/etc. commits from those staff on the same lack of fingers as Khadas (and several other SBC vendors). At the end of the day they all have the same business model which relies on seeding free samples among the Linux community in the hope that enthusiasts will do most of the work for them. The *only* board manufacturer who gets my vote for contribution is LibreComputer; who don't code anything themselves, but have been bankrolling Amlogic GX mainline development for some time - which has directly benefitted the entire community in addition to their own products. LibreComputer customers don't need much vendor support because you can just grab the latest upstream source for kernel, u-boot, etc. and everything is already supported.
VIM3 has a reworked heatsink and fan; there are taller vanes on the heatsink and the fan (which is allegedly silent now) has swapped sides to improve the cooling .. although I wouldn't know as Khadas forgot to include one in the sample kit. I have the board in one of their fancy cases (which I think are a bit crap, but they do the job) and it's warmer than cool (and the N2) but also shows no signs of overheating and it's still nowhere near the "raging inferno" temp that mk1 AppleTV's used to reach. Once G12 devices start running at full speed I might need to check the temps - right now they're on minimum clock at 1.2GHz (and still faster than previous generations) - but then adding the fan is the obvious addition. I wouldn't want to run one for long without the heatsink.
NB: The initial VIM3 device-tree that I made was literally a 10 mins copy/paste exercise (in a Hotel room .. no special tools needed). Once we have a few more devices under our belt I think G12A/B will be an identikit exercise.
-
I have an untested device-tree for the GT-King in my repo .. I'll pick a couple of people to test it and give feedback. Once we have at least one "box" device-tree for S922X it should be a simply copy/paste exercise to create more - the only thing that's likely to be different is the Ethernet spec and the remote control keymap.
-
Both HardKernel and Khadas are producing decent hardware. I personally prefer the VIM3 over N2 as it has eMMC and Bluetooth on-board; both of which make my development and testing work easier - one less SD card needed, and I can use a BT remote (which I prefer) instead of IR. In theory VIM3 also has WiFi but in practice the chip is not supported in the mainline kernel yet (and Ethernet is better anyway) so that's not a big factor. I'm sure Minix make reasonable hardware too, but I've never personally had anything to do with them. Do they have any S905X2/S922X product?
NB: I do not work for Khadas or any other box/board vendor .. fiddling with ARM boards for a living would never fund my Porsche habit
-
LE doesn't look at any "box" devices but one of the main upstream support targets is S905X2 so G12A hardware is well supported. S905X3 is being sampled to manufacturers but I'm not aware of anyone shipping product with it yet. LE prefers "board" devices because the manufacturers who sell them take fewer shortcuts and provide better customer support. Boot on the VIM3 is not as fancy/complicated as the N2.
-
I have a pre-production VIM3 board which works fine (same as the N2). Once we have multi-channel LPCM audio and mainline u-boot support working (soon hopefully) I'll be using it as the family daily-driver. I'll submit the device-tree so it goes upstream before/for the Linux 5.3 merge window.
-
You can delay when autostart.sh runs, but you cannot control when it finishes or the sequence with Kodi start.
If you move commands to a systemd .service file in /storage/.config/system.d/ you can control the sequencing, e.g.
Code
Display More[Unit] Description=EPG Download ServiceAfter=network-online.target nss-lookup.target Wants=network-online.target nss-lookup.target [Service] Type=oneshot RemainAfterExit=yes ExecStart=/usr/bin/wget http://XXXX:XXXXX@XXXXX/guide-zatoo.xml -O /storage/.kodi/userdata/guide-zatoo.xml [Install] WantedBy=multi-user.target
I won't guarantee this ^ will work as I'm no systemd expert, but "After=network-online.target nss-lookup.target" ensures the network is up, and then "WantedBy=multi-user.target" ensures it runs before Kodi startup.
-
-
You need to create a keymap. It's not hard, see: Infrared Remotes [LibreELEC.wiki]
-
No idea, but probably foul code in the legacy kernel. You already have a good solution.