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.
Posts by _emanuel_
-
-
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?
-
I've got shutdown problems.
see log
-
@chewitt: now it works nice
one patch hung, but build boots.
CodeAPPLY PATCH (device) projects/Amlogic/devices/AMLGX/patches/linux/amlogic-0028-FROMLIST-v6-arm64-dts-Fix-NPU-power-domain-reference.patch patching file arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi Hunk #2 succeeded at 2493 (offset 1 line). patching file arch/arm64/boot/dts/amlogic/meson-g12b.dtsi patching file arch/arm64/boot/dts/amlogic/meson-sm1.dtsiThe log in the attachment
-
@chewitt: woks nice without:
amlogic-0022-FROMLIST-v6-dt-bindings-power-Add-G12A-NNA-power-dom.patch.aus
amlogic-0023-FROMLIST-v6-soc-amlogic-meson-pwrc-Add-NNA-power-dom.patch.aus
amlogic-0024-FROMLIST-v6-arm64-dts-Add-DT-node-for-the-VIPNano-QI.patch.aus
amlogic-0025-FROMLIST-v6-drm-etnaviv-Add-nn_core_count-to-chip-fe.patch.aus
amlogic-0026-FROMLIST-v6-drm-etnaviv-Warn-when-probing-on-NPUs.patch.aus
amlogic-0028-FROMLIST-v6-arm64-dts-Fix-NPU-power-domain-reference.patch.aus
amlogic-0052-WIP-arm64-dts-meson-add-support-for-the-NPU-on-Radxa.patch.aus
Wifi only works setting
LibreELEC.tv/amlogic-0088-WIP-arm64-dts-meson-add-initial-device-trees-for-Dre.patch at bb98dc6f00cc16e33796ac0dc4fc672281a7093f · chewitt/LibreELEC.tvJust enough OS for KODI. Contribute to chewitt/LibreELEC.tv development by creating an account on GitHub.github.comto
Code<&gpio GPIOA_11 GPIO_ACTIVE_LOW>;The log in the attachment
-
@chewitt: I just built a testimg from your github amlogic branch.
Unfortunately, kernel 6.1.0 does not boot like this.
The log in the attachment
-
I've made a build from your github LE src (Branche "amlogic") 6.1-rc8 still do not boot on dreambox.
-
@chewitt: You recently gave me a test image that unfortunately didn't boot. It had a linux 6.1 kernel.
Did you fix that with the nand on some boxes?
If so, could you build the box img for me?
Would be interesting if wifi works there.
It works with my dtb in le-nightly (6.0.9) but not in armbian-current (6.0.14) or in armbian-etch (6.1).
(brcmfmac debug log attached)
>>> found the patch armbian bug, now wifi works on 6.0/6.1.1
-
@ chewitt: Since I'm dependent on a chain uboot, I noticed the following: since this commit https://github.com/u-boot/u-boot/…4b8373dbb7b6dc5 the terminal display only works if I explicitly add "CONFIG_BAUDRATE=1000000" to the u-boot config. Maybe I'm not the only one there.
-
@chewitt my update for the dreambox patches.
-
@chewitt I've found working dreambox gpio reset :-))
Codesdio_pwrseq: sdio-pwrseq { compatible = "mmc-pwrseq-simple"; reset-gpios = <&gpio GPIOA_11 GPIO_ACTIVE_LOW>; clocks = <&wifi32k>; clock-names = "ext_clock"; }; -
The image did not boot, see pic.
So I've copied the dtb in the nightly build. Booted, but no wifi.
-
I am trying to activate the Wifi (brcmfmac) on a Dreambox (s922x).
I have tested all g12b dtb, it does not work.
Also not by hand.
Blutooth works and that's the same brcm chip.
See log using a gtking like dtb: