Posts by kszaq
-
-
If you run from SD card, you can simply put dtb.img on SD card. To run with different device tree from internal memory, you have to flash it to /dev/dtb.
-
edit4ever You get magic number error because 1Gbit device tree is 4 trees concatenated with Amlogic tool. Further explanation in device trees thread.
-
edit4ever I had a look at the tree you posted and it looks like you should be able to use a device tree that is already supplied with my images, i.e. you don't need to replace it. I think you might get booting issues with that device tree because your bootloader doesn't support multi-device device tree blobs and that's what supplied image is. I will later try to provide separate device trees so you can try using one.
-
lama0900 This is a known issue in devel build. Current workaround: set audio to fixed 44.1kHz in Kodi settings and don't use passthrough. I'm working to fix it.
-
Installing to internal will sometimes fail with .006 and .007 if partition table is different from standard Amlogic partition table. At the moment I know no way to provide a universal table in device tree and for these boxes you have to run LE from SD now.
-
edit4ever By "older kernel" I meant older Amlogic revision which is also based on 3.14.29. It is a matter of luck/no luck but I would bet that for a S905 they have used an "older" Amlogic kernel and in that case device tree from factory firmware will only work up to 7.0.2.005. For 7.0.2.006 and later you will need to supply an updated tree.
-
wotikar Some devices have a file named "remotesecond.conf" in Android image. Have a look, maybe your firmware has one. If yes, rename it to remote.conf and copy for LE. Also remember that after you copy a new configuration file you need to reboot the box to apply it.
-
NAND (or rather internal memory) install overwrites the following partitons: system, data and dtb. It won't overwrite dtb only if you use ZIP file to install and don't have ledtb.img on your SD card. It will overwrite dtb if you ues installtointernal.
If you want to try using device tree from original firmware, simply delete dtb.img from SD card you run LE from. You should note that if device tree from original firmware was compiled for older kernel, your box won't boot.
-
DEcosse This package provides firmware but not the driver. Both firmware and driver are needed. You can see that in Amlogic download folder Index of /download/ARM/wifi there are many tarballs with Realtek, Broadcom and Mediatek drivers but there is no Qualcomm driver. I also know that QCA9377 driver is available in compat sources but it is only for PCI devices and we need SDIO driver.
I will try compiling a driver from Codeaurora.
-
edit4ever I will look at the device tree you posted in the other thread.
plikmuny Audio has not been fixed yet, I will post a notice when I get it right. I'm out of home for the weekend, so no dev builds today or tomorrow. It would be too much work for me to create a change log for every dev build, I do this only for release builds.
-
Even if we don't get a reply from Beelink/Netxeon, Amlogic should eventually post the drivers.
-
edit4ever From your log I can tell 2 things: you have BCM4335 WiFi and 1Gbit Ethernet. The latter seems to be an update from the previous K2 Pro.
Try using gxbb_p200_1Gbit.dtb
-
My Videostrong KII Pro (2G/16G) seems to use the Broadcom 4329/30 wifi chipset. I've tried most of the dtb files that are in the downloads for 006 and 007 but can't get wifi to work. I do have ethernet when using gxbb_p200_2G_mini_mxg_2_16.dtb or gxbb_p200_2G_beelink_minimxIII.dtbIs there an existing dtb for this setup or should I try to track down an android update file?
Also - just to make sure - is the Broadcom 4239/30 supported in 007?
According to my information, KII Pro uses BCM4335. Don't make guesses, use a proper device tree and post a log if WiFi doesn't work.
-
Vodkaneat It will freeze if partition table is different than in device tree. You can try using gxbb_p200_1G_100M_RealtekWiFI device tree, although it might also not work.
-
pec @chbmub Many thanks for your work! I will ask Codesnake to have a look at the patch as I don't watch/have access to DVB channels and maybe this could also be merged to upstream project.
-
kszaq you wouldn't mind telling me how to compile your sources would you, I'm getting build errors with "PROJECT=S905 ARCH=aarch64 make -j4 image"
CodeUsage: /home-new/adamg/LibreELEC.tv/build.LibreELEC-S905.aarch64-7.0.2.007-adamg/linux-bca261f/scripts/depmod.sh /sbin/depmod <kernelrelease> <symbolprefix> Makefile:1048: recipe for target '_modinst_post' failed make[1]: *** [_modinst_post] Error 1 make[1]: Leaving directory '/home-new/adamg/LibreELEC.tv/build.LibreELEC-S905.aarch64-7.0.2.007-adamg/linux-bca261f' Makefile:12: recipe for target 'image' failed make: *** [image] Error 2
You can use either make image or make amlpkg. The very short log you posted tells nothing about where error occurs, you need to post a full build log - preferably collected after a 2nd failed attempt to make it shorter. Please also post a diff if you made any changes in source.
-
Suspend is something I am working on now, it is expected not to work in this build.
Do you have any VP9 videos that you can test hardware decoding on? I have added some basic code to enable it and I'm wondering if it works (no S905X here yet to test).