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.
Posts by chewitt
-
-
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..
-
actually.. linux/btusb.c at master · torvalds/linux · GitHub says it should be supported on the kernel side.
can you run "dmesg | paste" .. let's see if there's messages about missing firmware; share the URL
-
The fix should be in the 9.2.2 (Generic only) image.
-
See if you can find it here: kernel/git/firmware/linux-firmware.git - Repository of firmware blobs for use with the Linux kernel .. If yes, it's trivial to add.
If not, find it from somewhere else and create /storage/.config/firmware/firmware.fw .. whatever folders/filenames that exist under firmware/ will be mapped to /usr/lib/firmware on rebooting .. so you can self-fix. Check "dmesg" to make sure the driver is actually present in the kernel. If it is you'll see errors for missing firmware. If not, kernel modules will need to be enabled to provide the driver - this requires the image to be recompiled.
-
QCA9377 is not currently supported in the kernel bluetooth tree. I've been looking at what config is missing/neeed to add support for Amlogic SDIO devices, but this is not a huge priority for me at the moment.
This is as far as I've got (not a huge effort): WIP: Bluetooth: hci_qca: Add compatible for QCA9377 · chewitt/linux@ffd3f65 · GitHub