current build works well on dreambox
Posts by _emanuel_
-
-
-
-
First I've tested "y", but also no install.
LibreELEC.tv/scripts/checkdeps at master · LibreELEC/LibreELEC.tvJust enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.github.com -
I've got a problem to build it:
-
I've just tried to get the wifi to work. I adapted the patch from you so that it works on both dreamboxes. I built it into an original LE.
I know this drive, but got one big problem:
android_kernel_gigaset_mt6768/drivers/gpu/drm/panel/panel-boe24-jd9853-vdo.c at 1382e85603836dbc1deebbe4d5da78500afd143c · nift4/android_kernel_gigaset_mt6768Contribute to nift4/android_kernel_gigaset_mt6768 development by creating an account on GitHub.github.com -
-
chewitt: can you add the dreambox patches again?
-
test-build from your amlogic branch 6.2.9:
Code
Display More[ 9.458149] brcmfmac: F1 signature read @0x18000000=0x17224356 [ 9.459823] Bluetooth: Core ver 2.22 [ 9.459938] NET: Registered PF_BLUETOOTH protocol family [ 9.459944] Bluetooth: HCI device and connection manager initialized [ 9.460100] Bluetooth: HCI socket layer initialized [ 9.460110] Bluetooth: L2CAP socket layer initialized [ 9.460205] Bluetooth: SCO socket layer initialized [ 9.462673] brcmfmac: brcmf_sdio_probe: brcmf_sdio_probe_attach failed [ 9.489571] brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19...
I reduced the speed to: "sd-uhs-sdr50;" like in the mainline-android and wifi works:
C
Display More// SPDX-License-Identifier: (GPL-2.0+ OR MIT) /* * Copyright (c) 2019 Christian Hewitt <[email protected]> */ /dts-v1/; #include "meson-g12b-dreambox.dtsi" / { compatible = "dream,dreambox-two", "amlogic,g12b"; model = "Dreambox Two"; }; &sd_emmc_a { sd-uhs-sdr50; };
-
I finally managed to get LibreElec to work on the dreamtv mini UltraHd (s905x2, u211, 2GB, 100Mbit LAN).
Unfortunately I still have to work with the u-boot.ext (from a u200) + a s905_autoscript.
I fail to boot with u-boot flashed on raw sd card, until now.
I tried it as described with the fip and bin built for a u211.
So far I haven't had any luck.
But I've already built a device tree that makes everything work (eth, wlan, bt, rc-remote, usb-2.0, usb-3.0).
The only thing that doesn't work is HW DRM decoding. The player gets stuck and you only hear audio.
But the box can also handle SW decoding well.
All boxes like videostrong/mecool KM3, KM9... (s905x2, 100Mbit LAN ) should run with the device tree.
-
playback will not be possible until someone authors a demux driver.
there is no playback at the moment for v4l/panfrost?
What about the avl tuners or other usb tuners/demods in LE nigthly - also no playback ?
-
Works well with "-f". I have to say that the LE is very stable. Yesterday I loaded my dvb test driver X times. And yesterday I was able to turn on the dvb demodulator for the first time. I don't know much about such things. Wish me luck.
-
log caught while box frozen:
Code
Display MoreLibreELEC:~ # reboot LibreELEC:~ # [ 252.701807] EXT4-fs (mmcblk1p4): unmounting filesystem. [ 252.704957] EXT4-fs (mmcblk1p5): unmounting filesystem. [ 262.748169] meson8b-dwmac ff3f0000.ethernet eth0: Link is Down [ 262.754785] systemd-journald[353]: Data hash table of /var/log/journal/7d291256aa5bbada6c7b94f263a1fbd1/system.journal has a fill level at 75.1 (1708 of 2275 items, 1310720 file size, 767 bytes per hash table item), suggesting rotation. [ 262.758566] systemd-journald[353]: /var/log/journal/7d291256aa5bbada6c7b94f263a1fbd1/system.journal: Journal header limits reached or header out-of-date, rotating. [ 263.826923] systemd-journald[353]: Received client request to relinquish /var/log/journal/7d291256aa5bbada6c7b94f263a1fbd1 access. [ 263.937647] watchdog: watchdog0: watchdog did not stop! [ 263.948214] systemd-shutdown[1]: Using hardware watchdog 'Meson GXBB Watchdog', version 0, device /dev/watchdog0 [ 263.949645] systemd-shutdown[1]: Watchdog running with a timeout of 10min. [ 263.952366] systemd-shutdown[1]: Syncing filesystems and block devices. [ 264.038342] systemd-shutdown[1]: Sending SIGTERM to remaining processes... [ 264.045521] systemd-journald[353]: Received SIGTERM from PID 1 (systemd-shutdow). [ 264.052503] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [ 264.059717] systemd-shutdown[1]: Unmounting file systems. [ 264.061652] [1590]: Unmounting '/var'. [ 264.064444] [1591]: Remounting '/storage' read-only with options ''. [ 264.080458] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: disabled. [ 264.089044] [1592]: Unmounting '/storage'. [ 264.132484] EXT4-fs (mmcblk0p2): unmounting filesystem. [ 264.136671] [1593]: Unmounting '/flash'. [ 264.139090] [1593]: Failed to unmount /flash: Device or resource busy [ 264.142861] [1594]: Unmounting '/flash'. [ 264.143832] [1594]: Failed to unmount /flash: Device or resource busy [ 264.145034] systemd-shutdown[1]: Not all file systems unmounted, 1 left. [ 264.146016] systemd-shutdown[1]: Deactivating swaps. [ 264.146892] systemd-shutdown[1]: All swaps deactivated. [ 264.147676] systemd-shutdown[1]: Detaching loop devices. [ 264.149053] systemd-shutdown[1]: Not all loop devices detached, 1 left. [ 264.149977] systemd-shutdown[1]: Stopping MD devices. [ 264.150918] systemd-shutdown[1]: All MD devices stopped. [ 264.151709] systemd-shutdown[1]: Detaching DM devices. [ 264.152610] systemd-shutdown[1]: All DM devices detached. [ 264.153502] systemd-shutdown[1]: Unmounting file systems. [ 264.155120] [1595]: Unmounting '/flash'. [ 264.155960] [1595]: Failed to unmount /flash: Device or resource busy [ 264.157093] systemd-shutdown[1]: Not all file systems unmounted, 1 left. [ 264.158036] systemd-shutdown[1]: Detaching loop devices. [ 264.159393] systemd-shutdown[1]: Not all loop devices detached, 1 left. [ 264.160397] systemd-shutdown[1]: Unmounting file systems. [ 264.162238] [1596]: Unmounting '/flash'. [ 264.164358] [1596]: Failed to unmount /flash: Device or resource busy [ 264.172580] systemd-shutdown[1]: Not all file systems unmounted, 1 left. [ 264.173606] systemd-shutdown[1]: Detaching loop devices. [ 264.174985] systemd-shutdown[1]: Not all loop devices detached, 1 left. [ 264.175940] systemd-shutdown[1]: Cannot finalize remaining file systems, loop devices, continuing. [ 264.177176] watchdog: watchdog0: watchdog did not stop! [ 264.178958] systemd-shutdown[1]: Failed to finalize file systems, loop devices, ignoring. [ 264.180359] systemd-shutdown[1]: Syncing filesystems and block devices. [ 264.181458] systemd-shutdown[1]: Rebooting.
-
That's all disabled by default in vendor dts. I thing they do only use the dt's value for their own closed src drivers.
linux-meson64/dreamone.dts at master · emanuel4you/linux-meson64linux meson64. Contribute to emanuel4you/linux-meson64 development by creating an account on GitHub.github.comlinux-meson64/dreamone.dts at master · emanuel4you/linux-meson64linux meson64. Contribute to emanuel4you/linux-meson64 development by creating an account on GitHub.github.comlinux-meson64/dreamone.dts at master · emanuel4you/linux-meson64linux meson64. Contribute to emanuel4you/linux-meson64 development by creating an account on GitHub.github.comgpio-keys-polled: ir keystoke issues on exit menus (armbian too)
leds: tested a lot without success, need to talk to vendor
adc_keys: I need to test this ones
by the way: my test driver hits two modulators and LNB on the i2c.
-
@chewitt: did you forget to remove the patch 'amlogic-0091-FIXUP-add-adc-gpio-keys-and-led-s-to-dreambox.patch' before merging nigthly? This only causes trouble, because the exit dialog opens with almost every keystroke on the infrared remote control.
Sometimes the box still hangs when switched off (even entering: # systemctl --force --force poweroff). I got a last error message in the terminal: Can't close watchdog. So this one hangs.
-
Quote
No change to G12A/B and SM1 support (still problematic).
So am I up to date with your amlogic branch? Don't I have to test anything?
-
New build from amlogic branch works nice as far as I can see, till now no shutdown (pm) problems.
-
I had tested it like this before:
Code
Display Moregpio-keys-polled { compatible = "gpio-keys-polled"; poll-interval = <100>; power-button { label = "power"; linux,code = <KEY_POWER>; gpios = <&gpio_ao GPIOAO_3 GPIO_ACTIVE_HIGH>; }; }; leds { compatible = "gpio-leds"; #status = "disabled"; sys-led { label="sys_led"; gpios=<&gpio_ao GPIOAO_11 GPIO_ACTIVE_HIGH>; default-state ="on"; retain-state-suspended; linux,default-trigger="cpu0"; }; };
but it only caused interference with the IR remote control. (gpio-keys-polled) After a few button presses, the exit menu suddenly starts to flicker on off on off... Kodi can then no longer be operated and must be terminated via terminal. I hadn't caught either the LED or the Power HW button at the time. With your patch I have the same flakes. The HW power button and the LED don't work either. Dreamtwo has an RGB LED. I think Dreamone is only blue. If I set the gpio-keys-polled to GPIO_ACTIVE_LOW, the menu stops flickering, but it still appears with almost every X keystroke, but you get out with exit.
What are the adc keys for? how can i test it?