The Apple EFI firmware on older models is woeful in places and finnicky about bootloaders; and what works from USB isn't necessarily what will work from SATA. I'd experiment with installing Ubuntu to the HDD. If that works (and boots from the HDD) then you can boot from the LiveUSB .. erase and partition the drive for LE (512MB for boot=/dev/device and the remainder for disk=/dev/device) then copy the KERNEL and SYSTEM files to the boot partition, install Grub to the drive and setup the bootloader config file.
Posts by chewitt
-
-
Create space for the partition and format it as EXT4 (must be a Linux partition type for SSH to work). Note the /dev/sdX device details for it under Linux and then modify boot params in syslinux.cfg to use disk=/dev/sdX .. then reboot. Kodi will start out with a clean install.
-
I wanted to try if my box boots with an older LE (eg Libreelec 8.2.2.3 as Senior Citizen wrote) but the download link in the forum ([8.2.2.3] LibreELEC 8.2 for S912) is not working. Do you have maybe a link from where i can download it?
There are no archives of those unofficial releases, sorry.
-
chewitt : Any thoughts? For about the same as the RPi4 4GB I can get the OPI 3LTS and don't have to wait...how do the LE development futures compare?
I don't have one so cannot talk from personal experience, but overall H6 is now well supported as a SoC. RPi4 will always have the advantage of Kodi support being actively, attentively, and directly maintained by RPi Foundation vs. the community led efforts for Allwinner devices; but it's maybe a thin advantage as Allwinner has a strong and active community and one of its major contributors is jernej our maintainer.
-
On Feb 12 there is a new version released on http://ftp.vim.org/pub/mediaplayer/libreelec/ (10.95.1)
But I don't see it anounced at https://libreelec.tv/
Which changes does it have
I'm not aware that VIM are an official mirror so that's probably something self-built. Official releases are now published and being replicated to official mirrors so release should be in the next 24h.
Changes are here: https://github.com/LibreELEC/Libr….95.0...10.95.1
-
It's also worthwhile to see if you can use an Ubuntu LiveUSB to boot the box. If yes, the BIOS has no problem with Grub and you could always install Grub to a USB stick and then do a manual install. All our installer does to the target device is install the bootloader, create two GPT partitions; first is 512MB to hold KERNEL/SYSTEM and the bootloader config file, and second is remaining space on the drive. The config file just needs to set (in grub format) the boot= and disk= content (using /dev/device, label or GUID as you like).
-
Code
cd /storage/.update wget https://chewitt.libreelec.tv/testing/LibreELEC-AMLGX.arm-10.95.1.tar reboot^ That version should have fixed Ethernet and USB, and I removed the keymap so IR is in a 'blank' state. IR isn't working in the staff members box either and (so far) none of us figured out why, it's most unusual.
-
You might need to fiddle with BIOS settings to enable legacy mode (not EFI, although we do support EFI boot). Worst case; pull the drive and connect it to a desktop and write the LE image direct to the HDD/SSD. Then interrupt boot and type "run" to skip the normal installer process and run LE from the install media (which is the internal drive). Variations on that theme include connecting the drive to another machine and booting installing to the drive on that machine before moving the drive back to the HP box.
-
Put Kodi in debug logging mode, clean boot, demonstrate the problem, then run "pastekodi" and share the URL.
-
Could you explain how to do that? I've only used the supplied SD creator to "install" to the MicroSD that I then use in the Cubox. I don't know how to "install" from the USB (which was also created by the SD creator?) to the "storage" (e.g. to the internal eMMC?)
The Generic image includes an installer; we assume that users boot from a USB stick and install LE to a HDD or SSD inside the box, although if you interrupt boot you can also skip the installer and run direct from the USB stick (one-time or persistently). On the ARM side of things we assume users are going to boot and run permanently from an SD card (or USB); either hooking vendor u-boot (on emmc) or using upstream u-boot that we created to boot into LE. ARM images don't support the installer .. hence you've never seen it with the Cubox.
-
Creating a non-static Qt6 version of the tool is simple, but this won't run on 95% of Linux desktops without lots of Qt dependencies being pre-installed and we've elected to not inflict that on our users.
Creating a static Qt6 version of the tool allows it to run basically everywhere but requires a new Qt6 static build recipe and nobody managed to guess at the right combination of juju to make that happen yet. It's one of those Linux "dark arts" challenges; sounds simple but reality is different.
Plan B (or C?) .. download the .img.gz file you need and use "dd" which is native in every OS and most Linux folks know how to use it.
-
Failure to set Gbit speeds is normally caused by bad cables, a problem switch/hub port, or (occasionally but not often) hardware issues. It is possible to force Gbit operations and full-duplex mode etc. using "ethtool" but if auto-detection fails this is unlikely to solve the problem.
Please share "pastekodi" URL so we can look for issues in the boot log and see what NIC is actually being used.
-
If you want to continue using LIRC we still support it and you can continue doing the same things. The only change will be dropping "sudo" from any commands being exectuted since in LE everything runs as root making sudo not necessary. Using LIRC also negates the need for Ubuntu, and all the dual-boot and boot menu things.
However, there is no HOWTO guide for your exact setup, nobody is going to volunteer to write one specially for you, and forum staff generally expect a modicum of initiative to be shown. So have a go, and if you get stuck, ask Q's.
-
https://chewitt.libreelec.tv/testing/LibreE…95.1-box.img.gz <= set "meson-gxm-t95z-plus.dtb" in uEnv.ini
please share "pastekodi" log URL afterwards, thanks.
-
The LE installer expects to have exclusive use of whatever disk /dev/device you install LE to so it does not support dual boot installs (and we have never offered to support dual-boot setups, it's too much hassle). However if you understand how to fiddle with partitions and create space for another OS and configure things (maybe, or maybe-not?) then it's completely possible. You can mod the syslinux config (or install grub if you or Ubuntu prefers it) and configure that to create a boot menu offering LE and Ubuntu. For a remote to work with that it probably needs to be the kind that acts like a wireless keyboard since there is no 'OS' at boot time to do fancy remote support. If the remote emulates USB keyboard arrow key navigation and USB is active (should be at BIOS level) it should work. There are probably threads in these forums on all those topics if you go (re)search for them. Again, we don't support dual-boot so there's an element of self-initiative required.
https://wiki.libreelec.tv/configuration/…es#lirc-support <= We dropped the lirc on/off from the settings add-on some time ago (wiki needs to be update) but AFAIK everything else documented there should still apply and lirc can be used if you really need it. Without knowing what other special things you are doing in Ubuntu it's hard to say whether it can be easily replicated in LE without old-school lirc, but in 99% of cases there's usually and easier way. Give detailed descriptions and share code/scripts involved (often more useful and a non-technical users bad description) if you want better guidance.
NB: HDR support requires an HDR capable Intel or AMD GPU (not nVidia) and the LE11b1 Generic image or newer. This uses GBM/V4L2 graphics which means no VNC. If you want to do things remotely you can SSH in use "kodi-remote" to do basic keyboard navigation around the GUI from an SSH client. If you really want VNC then you need to use the Generic-Legacy image, but that uses X11 and thus means no HDR. You cannot have both.
-
Interesting. I discovered that dtech (staff contributor) has the same box (or at least, something that claims to be - there are lots of clones) so I'll make a device-tree file for you both to test. I'll map the x96max remote to see if that works too.
-
btw, Ethernet is not working on the box. The same issue has been seen on several GXM devices and I'm not sure quite what the issue is yet.
-
Code
mkdir -p /storage/.config/rc_keymaps cp /usr/lib/udev/rc_keymaps/x96max.toml /storage/.config/rc_keymaps/custom_remote sed -i 's/x96max/custom_remote/g' /storage/.config/rc_keymaps/custom_remote echo "* * custom_remote" > /storage/.config/rc_maps.cfg rebootThis ^ should define a new custom_remote config that's the same as the x96max remote.
Codeecho "* * x96max" > /storage/.config/rc_maps.cfg rebootThis ^ might be an even easier version (see if it works first). It's been a while since I played around with the keymaps.
If neither of those work, the keycodes need to be persuaded into outputting something with `"ir-keytable" .. I'm not sure why that wouldn't be showing something.
