F@ck, lame me. config_distro_bootcmd goes through all the configured device types and checks whether they have the given DOS partition or not.
Posts by harsszegi
-
-
Hello,
totally confused how LibreElec decides what bootcmd to use in u-boot.
Can anyone shed some light on it?
How is it decided what board what interface/device shall use for boot?
I don't fully understand how is it decided whether SPI, NAND, RKNAND, MMC will be used to find the DOS partition.
Or am I misunderstanding something completely? Is there a guide/doc on this?
Thanks,
-
Hats off Kwiboo,rm -rf build* sorted it out [would have never thought that though]. Thanks!
-
Hello, just did a pull and I can't compile my Rockchip image anymore.
Code
Display MoreBUILD libtool (host) TOOLCHAIN autotools AUTORECONF libtool autoreconf: Entering directory `/home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-Fireprime.arm-9.0-devel/libtool-2.4.6' autoreconf: configure.ac: not using Gettext autoreconf: running: /home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-Fireprime.arm-9.0-devel/toolchain/bin/aclocal -I /home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-Fireprime.arm-9.0-devel/toolchain/armv7ve-libreelec-linux-gnueabi/sysroot/usr/share/aclocal -I /home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-Fireprime.arm-9.0-devel/toolchain/armv7ve-libreelec-linux-gnueabi/sysroot/usr/share/aclocal --force -I m4 autoreconf: configure.ac: tracing autoreconf: running: /home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-Fireprime.arm-9.0-devel/toolchain/bin/libtoolize --copy --force --ltdl libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. libtoolize: copying file 'build-aux/compile' libtoolize: copying file 'build-aux/config.guess' libtoolize: copying file 'build-aux/config.sub' libtoolize: copying file 'build-aux/depcomp' libtoolize: copying file 'build-aux/install-sh' libtoolize: copying file 'build-aux/missing' libtoolize: copying file 'build-aux/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: You should add the contents of 'm4/libtool.m4' to 'aclocal.m4'. libtoolize: copying file 'm4/ltargz.m4' libtoolize: You should add the contents of 'm4/ltargz.m4' to 'aclocal.m4'. libtoolize: copying file 'm4/ltdl.m4' libtoolize: You should add the contents of 'm4/ltdl.m4' to 'aclocal.m4'. libtoolize: copying file 'm4/ltoptions.m4' libtoolize: You should add the contents of 'm4/ltoptions.m4' to 'aclocal.m4'. libtoolize: copying file 'm4/ltsugar.m4' libtoolize: You should add the contents of 'm4/ltsugar.m4' to 'aclocal.m4'. libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' libtoolize: You should add the contents of 'm4/lt~obsolete.m4' to 'aclocal.m4'. libtoolize: putting libltdl files in LT_CONFIG_LTDL_DIR, 'libltdl'. libtoolize: copying file 'libltdl/COPYING.LIB' libtoolize: copying file 'libltdl/Makefile.am' libtoolize: copying file 'libltdl/README' libtoolize: copying file 'libltdl/configure.ac' libtoolize: copying file 'libltdl/aclocal.m4' libtoolize: copying file 'libltdl/Makefile.in' libtoolize: copying file 'libltdl/config-h.in' libtoolize: copying file 'libltdl/configure' libtoolize: copying file 'libltdl/libltdl/lt__alloc.h' libtoolize: copying file 'libltdl/libltdl/lt__argz_.h' libtoolize: copying file 'libltdl/libltdl/lt__dirent.h' libtoolize: copying file 'libltdl/libltdl/lt__glibc.h' libtoolize: copying file 'libltdl/libltdl/lt__private.h' libtoolize: copying file 'libltdl/libltdl/lt__strl.h' libtoolize: copying file 'libltdl/libltdl/lt_dlloader.h' libtoolize: copying file 'libltdl/libltdl/lt_error.h' libtoolize: copying file 'libltdl/libltdl/lt_system.h' libtoolize: copying file 'libltdl/libltdl/slist.h' libtoolize: copying file 'libltdl/loaders/dld_link.c' libtoolize: copying file 'libltdl/loaders/dlopen.c' libtoolize: copying file 'libltdl/loaders/dyld.c' libtoolize: copying file 'libltdl/loaders/load_add_on.c' libtoolize: copying file 'libltdl/loaders/loadlibrary.c' libtoolize: copying file 'libltdl/loaders/preopen.c' libtoolize: copying file 'libltdl/loaders/shl_load.c' libtoolize: copying file 'libltdl/lt__alloc.c' libtoolize: copying file 'libltdl/lt__argz.c' libtoolize: copying file 'libltdl/lt__dirent.c' libtoolize: copying file 'libltdl/lt__strl.c' libtoolize: copying file 'libltdl/lt_dlloader.c' libtoolize: copying file 'libltdl/lt_error.c' libtoolize: copying file 'libltdl/ltdl.c' libtoolize: copying file 'libltdl/ltdl.h' libtoolize: copying file 'libltdl/slist.c' libtoolize: Remember to add 'LTDL_INIT' to configure.ac. autoreconf: running: /home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-Fireprime.arm-9.0-devel/toolchain/bin/autoconf --include=/home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-Fireprime.arm-9.0-devel/toolchain/armv7ve-libreelec-linux-gnueabi/sysroot/usr/share/aclocal --force autoreconf: running: /home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-Fireprime.arm-9.0-devel/toolchain/bin/autoheader --include=/home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-Fireprime.arm-9.0-devel/toolchain/armv7ve-libreelec-linux-gnueabi/sysroot/usr/share/aclocal --force autoreconf: running: /home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-Fireprime.arm-9.0-devel/toolchain/bin/automake --add-missing --copy --force-missing automake: error: cannot open < libltdl/ltdl.mk: No such file or directory autoreconf: /home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-Fireprime.arm-9.0-devel/toolchain/bin/automake failed with exit status: 1 Makefile:12: recipe for target 'image' failed make: *** [image] Error 1 harsszegi@harsszegi:~/rockchip/LibreELEC.tv$
Any thoughts?
Thanks,
-
Hello,
kinda clueless, hoping someone can shed some light on my problem.
I have enabled CONFIG_MALI400 + CONFIG_MALI400_DEBUG in the kernel config (testing a RK3036).
I'd say everything appears fine, apart from the "tiny" issue that "a bit after"
[ 33.078793] initcall init_module+0x0/0x178 [mali] returned 0 after 4001 usecs
the whole system locks up. If I remove MALI400, everything boots just fine.
Any idea what might be the issue?
Thanks,
[ 33.074335] calling init_module+0x0/0x178 [mali] @ 218
[ 33.074376] Mali<2>: Inserting Mali v900 device driver.
[ 33.074381] Mali<2>: Compiled: Feb 26 2018, time: 06:35:09.
[ 33.074385] Mali<2>: Driver revision: -7.90.001-5070-gd35be6b6b
[ 33.074394] I : [File] : drivers/gpu/arm/mali400/mali/linux/mali_kernel_linux.c; [Line] : 415; [Func] : mali_module_init(); svn_rev_string_from_arm of this mali_ko is '-7.90.001-5070-gd35be6b6b', rk_ko_ver is '5', built at '06:35:09', on 'Feb 26 2018'.
[ 33.074398] Mali<2>: mali_module_init() registering driver
[ 33.074696] Mali<2>: mali_probe(): Called for platform device 10091000.gpu
[ 33.074709] mali-utgard 10091000.gpu: mali_platform_device->num_resources = 9
[ 33.074717] mali-utgard 10091000.gpu: resource[0].start = 0x0x10091000
[ 33.074723] mali-utgard 10091000.gpu: resource[1].start = 0x0x10090000
[ 33.074729] mali-utgard 10091000.gpu: resource[2].start = 0x0x10093000
[ 33.074736] mali-utgard 10091000.gpu: resource[3].start = 0x0x10098000
[ 33.074742] mali-utgard 10091000.gpu: resource[4].start = 0x0x10094000
[ 33.074749] mali-utgard 10091000.gpu: resource[5].start = 0x0x00000019
[ 33.074755] mali-utgard 10091000.gpu: resource[6].start = 0x0x0000001a
[ 33.074761] mali-utgard 10091000.gpu: resource[7].start = 0x0x0000001b
[ 33.074767] mali-utgard 10091000.gpu: resource[8].start = 0x0x0000001a
[ 33.074775] D : [File] : drivers/gpu/arm/mali400/mali/platform/rk/rk.c; [Line] : 618; [Func] : mali_platform_device_init(); to add platform_specific_data to platform_device_of_mali.
[ 33.075244] Mali<2>: Init Mali devfreq
[ 33.075261] Mali<2>: mali devfreq table count 2
[ 33.075269] Mali<2>: mali devfreq table array[0] = 200000000
[ 33.075273] Mali<2>: mali devfreq table array[1] = 400000000
[ 33.075645] Mali<2>: mali_devfreq_cur_freq: freq = 400000000
[ 33.075656] Mali<2>: mali_devfreq_target:set_freq = 20654497726464 flags = 0x0
[ 33.076247] Mali<2>: Mali SWAP: Swap out threshold vaule is 60M
[ 33.076281] Mali<2>: Mali memory settings (shared: 0x40000000)
[ 33.076287] Mali<2>: Using device defined frame buffer settings (0x00000000@0x00000000)
[ 33.076300] Mali<2>: Mali PM domain: Creating Mali PM domain (mask=0x00001000)
[ 33.076351] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP0
[ 33.076356] Mali<2>: Mali PP: Base address of PP core: 0x10098000
[ 33.076582] Mali<2>: Found Mali GPU Mali-400 MP r1p1
[ 33.076754] Mali<2>: Mali L2 cache: Created Mali_L2: 32K, 4-way, 64byte cache line, 64bit external bus
[ 33.076776] Mali<2>: Mali MMU: Creating Mali MMU: Mali_GP_MMU
[ 33.076836] Mali<2>: mali_mmu_probe_irq_acknowledge: intstat 0x3
[ 33.076840] Mali<2>: Probe: Page fault detect: PASSED
[ 33.076843] Mali<2>: Probe: Bus read error detect: PASSED
[ 33.076874] Mali<2>: Mali GP: Creating Mali GP core: Mali_GP
[ 33.076976] Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP0_MMU
[ 33.077013] Mali<2>: mali_mmu_probe_irq_acknowledge: intstat 0x3
[ 33.077016] Mali<2>: Probe: Page fault detect: PASSED
[ 33.077020] Mali<2>: Probe: Bus read error detect: PASSED
[ 33.077046] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP0
[ 33.077051] Mali<2>: Mali PP: Base address of PP core: 0x10098000
[ 33.077095] Mali<2>: 1+0 PP cores initialized
[ 33.077111] Mali<2>: Mali GPU Utilization: No platform utilization handler installed
[ 33.077999] Mali<2>: mali_probe(): Successfully initialized driver for platform device mali-utgard
[ 33.078462] Mali: Mali device driver loaded
[ 33.078793] initcall init_module+0x0/0x178 [mali] returned 0 after 4001 usecs
-
Sorry don’t understand; there is the make error on line 11
Btw. this is the offending line in package.mk
makeinstall_host() {
[...]
cp -L nss/coreconf/nsinstall/*/nsinstall $TOOLCHAIN/bin
}
Oh f@ck. Missing "Linux" before the "*"
cp -L nss/coreconf/nsinstall/Linux*/nsinstall $TOOLCHAIN/bin
-
Hello,
nss fails to compile on the latest Rockchip branch.
Any idea?
Thanks,
Code
Display Moremake[3]: Entering directory '/home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-RK3036.arm-9.0-devel/nss-3.29.5/nss/cmd/pkix-errcodes' ../../coreconf/nsinstall/Linux4.13_x86_64_gcc_glibc_PTH_64_OPT.OBJ/nsinstall -R -m 775 Linux4.13_x86_64_gcc_glibc_PTH_64_OPT.OBJ/pkix-errcodes ../../../dist/Linux4.13_x86_64_gcc_glibc_PTH_64_OPT.OBJ/bin make[3]: Leaving directory '/home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-RK3036.arm-9.0-devel/nss-3.29.5/nss/cmd/pkix-errcodes' make[2]: Leaving directory '/home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-RK3036.arm-9.0-devel/nss-3.29.5/nss/cmd' cd config; make libs make[2]: Entering directory '/home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-RK3036.arm-9.0-devel/nss-3.29.5/nss/config' make[2]: Nothing to be done for 'libs'. make[2]: Leaving directory '/home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-RK3036.arm-9.0-devel/nss-3.29.5/nss/config' make[1]: Leaving directory '/home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-RK3036.arm-9.0-devel/nss-3.29.5/nss' cp: will not overwrite just-created '/home/harsszegi/rockchip/LibreELEC.tv/build.LibreELEC-RK3036.arm-9.0-devel/toolchain/bin/nsinstall' with 'nss/coreconf/nsinstall/Linux4.13_x86_64_gcc_glibc_PTH_64_OPT.OBJ/nsinstall' Makefile:12: recipe for target 'image' failed
-
Hello,
when compiling avahi the package complains about missing "./autogen.sh" (which should be executed in pre_configure_target()).
If I add $PKG_BUILD/autogen.sh, obviously everything works fine.
Any idea why the "./autogen.sh"?
Thanks,
-
Oh fsck. Obviously it wasn't freezing, I simply haven't updated systemd's serial console service setting, so it was missing the mmu for RK3036's ttys2
-
Hello,
trying to get RK3036 Kylin up and running in the Rockchip branch and it gives me the headache.
1.) I have tried using the solid working .config for the kernel which comes from the original rockchip-linux kernel, which works
just fine for a Debian rootfs, e.g. whole image boots -> no luck, when switching to rootfs(hopefully) the boot freezes2.) I have tried using the Tinkerboard linux.arm.conf which is in the repo, which has the same kernel config in the rockchip-linux kernel,
so I thought would be a good start -> no luck, boot hangs the same way
3.) I have copied back the linux.arm.conf (e.g. as .config, recompiled my kernel) in my "ethalon" RK3036 image, surprise the image boots just fine
4.) I have checked whether I am missing anything in the DTS or not,
So I am completely puzzled. Can anyone shed some light on what might go sideways? First I thought that the hardcoded tty0 (in the extlinux.cfg
kernel parameter) causes the issue, but even if I get rid of that the boot still hangs.
Thanks,
-
Hello,
just bumped into the issue that it doesn't matter what kernel config I use for LibreElec (practically wanted to take over the same kernel config
for my RockChip device I was using successfully up until now, but the system doesn't boot completely with that).
Is there any guide which lists what is the minimum featureset from the Linux kernel that is needed for LibreElec to work?
Thanks,
-
Hello,
I have a strange issue on my RK3036 the console should be on ttyS2.
When I boot with the "stock" rockchip kernel this is what I get:
[ 0.541192] 20060000.serial: ttyS0 at MMIO 0x20060000 (irq = 43, base_baud = 1500000) is a 16550A
[ 0.543286] console [ttyS2] disabled
[ 0.563776] 20068000.serial: ttyS2 at MMIO 0x20068000 (irq = 44, base_baud = 1500000) is a 16550A
[ 1.451507] console [ttyS2] enabled
however with the LibreElec config I get:[ 5.208566] ttyS2 - failed to request DMA
Any hint what might be wrong? I noticed that the kernel config is completely different in LibreElec what is stored in the rockchip-linux/kernel config(e.g. Tinkerboard's config is completely different compared with the corresponding RKxx defconfig (which is practically rockchip_linux-defconfig)
Thanks,
-
Hello,
turned on debugging in extlinux.cfg to figure out why my RK3036 doesn't start Kodi, how can I dump the rootfs of the LibreElec image?
I tried 'rkflashtool r' with various options (offset 0x40000), but couldn't really make it work (only zeroes were read).
So how can I dump the linux root partition?
Thanks,
-
Hello Chewitt,
thanks for the info. UART is not an issue
I saw the mediacenter service starting at the end of the kernel boot via minicom already.
U-boot, kernel boots fine, however I don’t have any shell (e.g login prompt - not even via ctrl-alt-f1/2/3), so I can’t get to check OS messages, my hunch is that X fails to start.
Most probably will check via extlinux.cfg + debugging and then I dump the rootfs and see the logs.
Mali400 should not be an issues, latest kernel supports that - at least this is what the Rockchip guys claim
-
Hello,
built a Kylin RK3036 image from the Rockchip branch. It boots fine, it gets to "Reached target Kodi Mediacenter interface".
However on the TV I see the LibreElec splash and nothing more. After a while the image is restarted.
I guess I don't have tty console enabled, neither SSH. What should I do to at least be able to get into the shell so that to check some dmesg,
Kodi logs, whatever to figure out what doesn't start and why?
Thanks,
-
Hello,
I get
config/Makefile:263: *** No gnu/libc-version.h found, please install glibc-dev[el]. Stop.
make[1]: *** [Makefile:69: all] Error 2
make[1]: Leaving directory '/home/harsszegi/rockchip/http://LibreELEC.tv/build.LibreELEC-TinkerBoard.arm-9.0-devel/linux-7b43537e/tools/perf'
Makefile:12: recipe for target 'image' failed
when using
PROJECT=Rockchip DEVICE=TinkerBoard ARCH=arm make image
it appears, like perf doesn't see the glibc project's include files.
Any advise?
Thanks,
p.s.: I have added a "TARGET_KERNEL_PERF" option to devices/options, and modded linux/package.mk so that if this is set to "NO" PKG_BUILD_PERF is also set to "NO", so this clears the problem for now
-
Hello,
I'm trying to use the rockchip branch, however it doesn't compile for me (on ubuntu 17.10). I get a compile error on the glib already.
Master builds just fine.
As I checked the rockchip branch is "a bit" outdated.
Can anyone provide a "guesstimate" when the Rockchip branch will be either synched with the master (I have tried to give it a go, but there
were substantial changes since) or will be merged back to master?
Thanks,