If you're running from SD card, perhaps try another SD card - they don't always last forever. If running from internal emmc, perhaps try running from an SD card - for the same reason. Otherwise I don't see anything obvious 
Posts by chewitt
-
-
S905L is a cost-engineered version of S905X (no hardware VP9 decoder). There are no specific S905L device trees in the AMLGX image (check the official nightlies in Index of /) but S905X dtb's like meson-gxl-s905x-p212.dtb in the "box" SD card image might work.
If you do get something booted please run "dmesg | paste" and share the URL so I can see the SoC ID and other info.
-
Oleg is on an mission to ship a single "ARM" image that (multi)boots on Allwinner, Amlogic and Rockchip hardware. From a userspace perspective this not hard now that all three SoC plaforms are using lima/panfrost, but it requires some differences in the u-boot scripts and boot configuration. Other than this (once booted) his images should be much the same as official nightlies - he is normally using my Amlogic kernel patch-set as-is (he feeds me any changes he finds to send upstream so things are mostly in-sync) and Kodi things are based on LE master.
Playback should be smooth except for HEVC (software decode is beyond an S805X board, hardware decode for HEVC is still work in progress). If you attempt to seek you will see hangs and it's likely the end of playback might require a reboot. It is proving to be an epic quest to get someone interested in the changes the V4L2 stateful code path in ffmpeg needs to solve those things. Raspberry Pi is about to hit the same roadblock though, so that's probably the road to success for that quest.
-
The mainline kernel direct rendering manager subsystem (aka DRM, just to confuse) only has rudimentary support for HDCP on later Intel hardware, but nothing else so Amlogic, Rockchip etc. need to evolve "secure path" support before any further poking at widevine support. NB: the entire process of Widevine device certification is also designed to ensure it's legally impossible to use a common certificate accross many devices, even if it is technically possible.
-
I'm not sure if mali supported DVFS (dynamic re-clocking) of the GPU, but lima currently does not, so the GPU is allways running at full speed. I'm not sure if that's the issue or not, but there are patches on the mailing list to add DVFS support so it's being looked into. Again, no idea if that's the issue.
-
PANiCnz If using the official nightlies you can either use the "box" image with the correct dtb named in uEnv.ini written to USB - this uses the internal SPI u-boot which will find our boot files, or you can use the "lafrite" image which uses extlinux boot config and our own u-boot. The C2/K2 extlinux images will not boot on LaFrite; the C2/K2 are GXBB devices and LaFrite is GXL, so the device-specific u-boot 'fip' sources are not compatible. Note that the 512MB LaFrite board will boot but Kodi will not start due to the current CMA allocation in device-tree/kernel. If you search the forums there's a thread where another 512MB board user figured out some tweaked settings that allow Kodi to run - and he is sharing his images.
erbas If you want to boot a Ki-Pro you need to use the 'box' image. The C2 u-boot BL1 firmware checks for C2 hardware and aborts if not found. We do not (and have no plan to) support emmc install on GXBB hardware.
-
-
Sadly there is nobody anywhere working on mainline kernel support for the 8726MX chipset.
-
^ once this is merged to our master development branch it will be picked into a collection of backports for LE 9.2.3, so once you bump to that you won't need the extra files in /storage/.config/firmware. Enjoy
-
Great. Can you confirm which BT device worked - onboard or USB?
-
Kodi DSP development stopped because it was a one-man effort (nothing unusual in Kodi land) and that individual took a break due to research and work things in real-life. However, they surfaced again recently and said they would be resuming where they left off. I didn't see anything yet, but DSP may yet be revived. Removing it was still the right decision as it's was incomplete and it's been ~two years.
-
Code
mkdir -p /storage/.config/firmware/qca cd /storage/.config/firmware/qca wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qca/nvm_usb_00000302.bin wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qca/rampatch_usb_00000302.bin reboot^ run those commands and you should have the right firmware. If you confirm it works, it's trivial for us to add the firmware into a future LE release.
let us know..
-
NIC drivers should be as simple as editing the kernel defconfig in projects/Generic/linux/linux.x86_64.conf and re-running the build process. Get a working image first and then make the change.
-
LE 9.2.3 will come sometime shortly after Kodi ships v18.7 .. which has no scheduled date (when there's enough changes to justify a release).
-
Plan B .. is boot from an Ubuntu Live/Rescue USB and use gparted or similar to shrink the existing /storage partition and then grow the /flash partition with boot files. It will be painfully slow, but it can be done. Then you can do a simple update from OE to LE. I'd probably do the initial step to LE 8.0 as this the same era as the last OE release, and then make a backup of the Kodi config before doing an update to 9.2.2. As a rule Kodi updates fine from older releases, but there is usually some add-on breakage and that's where you're likely to hit roadbumps. If you have a backup on local disk, it's easy to experiment and tweak the pre-update config until things are successful.
-
LE 8.2.5 is the last/latest available version for Meson 8b hardware - although in the past we only supported specific devices and yours is not one of them; hence it has a "community" created image installed. We dropped support for Meson 8* devices some time ago as the hardware is old and the original vendor kernel (Linux 3.10) became difficult to support. There are ongoing efforts in the Amlogic community to provide mainline (current) Linux kernel support for Meson 8/8b/8m2 devices again, so in the future it might be possible to run something current again, but not right now.
-
For clarity.. can you share "route" and "ifconfig" details before/after.
-
Code
[ 3.392029] bluetooth hci0: Direct firmware load for qca/rampatch_usb_00000302.bin failed with error -2 [ 3.392032] Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00000302.bin (-2)^ hardware is detected but firmware is missing. I'll see if I can find it..