Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates

  1. Past hour
  2. regular-mate-tegra-arm-20211217-aarch64.img - screen flickers Armbian_21.08.1_Jetson-nano_focal_legacy_4.9.201_xfce_desktop.img.xz - no flickering It looks like the mainline kernel has issues with 4K displays on the Nano. Is support for the Intel 9560NGW enabled in the Armbian kernel? I think it needs the iwlwifi-9000 modules. I was unable to update the latest jammy test image due to the attached apt errors. Thanks Balbes!
  3. Today
  4. @MarcoFdN Yes, armbian-config is not included in any Armbian minimal releases (not just mine), because if it was it would not be minimal anymore: armbian-config requires lots of dependencies and, for this reason, it is undergoing a vast refactoring which I don't know when it will be ready. In the meantime, no armbian-config for minimal images. Plus minimal images are for more experienced debian users, since target is server-like tasks. dmesg log is essential for such issues: x88 boards have wifi over "external" sdmmc controller, thus rk3318-config should already have warned you that you had to configure, reboot and then run again rk3318-config to get wifi and bluetooth detected and working. wifi can be configured either from command line with nmcli, but also with nmtui which provide a nice and simpler text-based UI even on minimal distros.
  5. aml_autoscript.zip --> inside image , boot partition image --> there are 3 storage spaces from blabes , yandisk (in this thread, some other forum ) ; mega ( in this thread somewhere) ; armbian space ( at s905 there was also a s8xx folder)
  6. Yesterday
  7. Since it is just a shell script, you can pipe the output to a file
  8. I am running Linux via the fedora distribution, but the distribution does not really matter. Stock fedora would not have any VP9 acceleration support in place. Only the particular rebuild packages make the difference. The plasma user is running the Plasma DE with Wayland backend and the lxqt user is running the LXQt DE with Xorg backend. Currently installed: 5.11.12, 5.12.0, 5.12.10, 5.13.0.rc1, 5.13.0.rc2, 5.13.0.rc3, 5.13.0.rc4, 5.13.0.rc5, 5.13.0.rc6, 5.13.0.rc7, 5.13.0, 5.14.0.rc1, 5.14.0.rc2, 5.14.0.rc3, 5.14.0, 5.15.0.rc6, 5.15.0, 5.16.0.rc2, 5.16.0.rc6, 5.16.0.rc7, 5.16.0 Currently running 5.16.0 with media staging commits at time of building on top, i.e. technically 5.17.0.rc1 media wise. I have build from the development branch, the 1.22 release is just around the corner.
  9. I was thinking (= not knowing) it was the same device tree used in the normal armbian ;-(( Was fighting getting one loader and this board is very kinky and was only finding 2 that was working and the first was older then original in Android and the second was RK322XMiniLoaderAll_V2.47_spectek_en_ddr2_rd_odt_171127.bin and then i can also booting from eMMC (then getting the system installed). After little try and error i was booting my Armbian 21.08.6 Focal patched with boot for MT. And "only" installing system on eMMC and it was working 110% !! then booting eMMC is the bootloader showing: DDR Version V1.10 20190926 In ID:0x0 330MHz LPDDR3 Bus Width=32 Col=10 Bank=8 Row=14 CS=2 Die Bus-Width=32 Size=1024MB mach:14 OUT U-Boot SPL 2021.04-armbian (Aug 08 2021 - 18:01:12 +0200) Trying to boot from MMC2 INF [0x0] TEE-CORE:init_primary_helper:377: Initializing (1.1.0-333-gc9d95d1 #2 2018年 08月 17日 星期五 03:32:22 UTC arm) INF [0x0] TEE-CORE:init_primary_helper:378: Release version: 2.0 INF [0x0] TEE-CORE:init_primary_helper:379: Next entry point address: 0x61000000 INF [0x0] TEE-CORE:init_teecore:83: teecore inits done So its update OK and then its internal or external card / USB and if finding one OK system its booting OK. After some more installations from zer i can only see degraded speed of the eMMC before updating and also the DDR confing is being made earlier after system update and i think the secret is that the initframes being rebuild for the kernel so the DDR config is being made earlier and the init of the eMMC is being later so its loading OK with full speed. Latest boot on one SD-card and the DDR / eMMC init: [ 4.316399] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req 52000000Hz, actual 50000000HZ div = 0) [ 4.336705] mmc2: new high speed MMC card at address 0001 [ 4.338689] mmcblk2: mmc2:0001 P1J95L 7.30 GiB [ 4.339550] mmcblk2boot0: mmc2:0001 P1J95L partition 1 2.00 MiB [ 4.340626] mmcblk2boot1: mmc2:0001 P1J95L partition 2 2.00 MiB [ 4.341295] mmcblk2rpmb: mmc2:0001 P1J95L partition 3 2.00 MiB, chardev (241:0) [ 4.345284] mmcblk2: p1 [ 4.435008] rk3228-dmc 11200000.dmc: memory type LPDDR2 S2, timings (tCL, tRCD, tRP, tRAS): CL8-8-8-14 command rate: 1T (mcfg register: 0x6b0000) [ 4.435052] rk3228-dmc 11200000.dmc: detected LPDDR3 memory [ 4.435074] devfreq-event event0: Rockchip DFI interface enabled [ 4.438371] rk3228-dmc 11200000.dmc: TEE DRAM configuration initialized [ 4.440520] rk3228-dmc 11200000.dmc: Failed to register cooling device Was running the test from armbian-config and the CUP tem was up to around 70° but normal its its idle around 55° so its not having the heating problem H3 devices is having :-))) Great thanks for helping getting this bow working without HDMI and WiFi but all other things needed for running on good real Linux on it and and Ubuntu Focal is making it working long as one small IOT server with updated for long time !! If can helping other getting the HDMI working its being even better but is no large use in my case. Mvh Mattias
  10. (Moved post to a more appropriate location) You will need to provide more information than just a screen shot. Lets start with the TV Box you have, what dtb you are using, etc. I think I saw in another thread you mention that you are sucessfully running a box from the SD card, so I'm not sure what your actual problem is.
  11. Hi Werner, oh yes, I definitively have access. I run two of these boards in my DACs for several years now: https://github.com/teknoid/dac/blob/master/pics/sabre18-top.jpg
  12. I use the patch and compile the image with the armbian. Compilation is ok. There isn't tve overlay to use, i don't know if it's necessary. I power on the board with the image builded and Image work and I can connect via SSH but no image output. I also test to add tve overlay to image, add tve to dts overlay Make file. I now have the dtbo tve file but adding it to overlay don't give me the solution, no image output. If I use old kernel (with fex) image output via CVBS works. UPDATE: add the patch for enable tve overlays kernel-sunxi-current.patch
  13. Please don't hijack this for your random TV Box. Its uses the same SoC doesn't mean we have any idea what goes into your particular TV box. There is a section for TV boxes in this forum. You can post your queries there.
  14. Great work. Currently still running building, so i dont know if it will work. building for a while now & ill leave it for the night 😴. Just a suggestion, I see that my terminal is showing its building for all canon printer models. (see screenshot) In the future it would be nice if a specific model can be chosen instead of all model, to save time. Goodnight.
  15. Last week
  16. Just quick note here to say , with the great help of @jock i get the wifi working.
  17. hello Ning.. Can you point to a detailed step by step instructions? I am running (bullseye) with Linux 5.9.0-arm-64 on a Amlogic s905x (1G+8G T95x) from the sd card and want to run it from the emmc. I dont care about the vendor android OS that came on the box Thank you!
  18. @srinath or there may be a problem with the csi socket pin order. It should match with ov5640 pin order.
  19. Hi Friend, what is the exact command line in the kernel actually ? I want to try it.
  20. Hi, people ! E-paper displays (I have 2.9 from Waveshare) are working well with Orange Pi Zero LTS under Armbian 21.08.6 Focal without WiringPi. Uncomment option USELIB_RPI = USE_DEV_LIB and comment others in C-example from Waveshare Regards
  21. After struggling many days with alsa, vlc and usb audio devices, I inevitably was confronted with "RPI usb problem". My feeling so far is that there are some bugs in the linux USB2 kernel driver, but those bugs are making havoc the "RPI firmware", that is to say the underlying OS witch manage the GPU and all devices. The consequence is that any power or driver (video driver, usb driver) problem can turn the RPI in a state where it become unusable (not because of Linux but the firmware itself) until a reboot and electrical reset ! In such case, the fs on a disk plugged in the USB3 bus is also corrupted. (force fsck is greatly encouraged). So, it is quite difficult to reproduce and diagnose linux or devices problems !
  22. Try change the disp_mode option in the file /boot/armbianEnv.txt to the resolution of the screen If it doesn't work: - ls /sys/class/drm/ - cat /sys/class/drm/*/modes The first one is to discovery the exact name of your display connection. In my case (orange pi pc connected via hdmi) it appears card0-HDMI-A-1, so the name of display connection is HDMI-A-1. The second one is to check the available resolutions from your display device. In addition to change disp_mode, add a line with extraargs to the file /boot/armbianEnv.txt. Here is my example, adapt it to your case: extraargs=video=HDMI-A-1:1920x1080@60 Note: the refresh rate does not appears in the command "cat /sys/class/drm/*/modes"
  23. I have bisected the issue for helios64. See: Could you try to revert this commit and check the issue vanish ? You could also try to revert those commits against latest kernel : 06653ebc0ad2e0b7d799cd71a5c2933ed2fb7a66 and probably also aea6cb99703e17019e025aa71643b4d3e0a24413 (both commits are related). Point is that helios64 is not a mainline supported architecture (the patches for it are not upstream but only Armbian) so maybe you will be in a better position to report the regression upstream and have one investigate the roots of the regression.
  24. Hi, I managed to compile 5.16.1 for my Rockpi4 board, I did not flash it yet as I try to polish things before I flash things. Also awaiting my 4A+ ( with POE HAT ) but first things first. Could one please update the edge entry to " 5.16.y " # /config/sources/families/include/ rockchip64_common.inc Also imho for rockpi4a(+) all bluetooth and WiFi entries should be removed from the kernel .config: - bluetooth-rtl8822cs-hci_ver-0x8.patch - Bluetooth-hci_h5-Add-power-reset-via-gpio-in-h5_btrt.patch - kali-wifi-injection-*.patch - wireless-*.patch - general-bluetooth-add-new-quirk.patch - board-pbp-fix-wonky-wifi-bt.patch - wifi-hf-lps170-bl602-kconfig-makefile.patch - wifi-hf-lps170-bl602.patch To build 5.16.y following patches have been removed : - board-rockpi4-0005-arm64-dts-enable-es8316-audio.patch ? general-fix-es8316-kernel-panic.patch # did not remove but should be imho ? - bootsplash-5.10.y-0003-Revert-fbcon-remove-soft-scrollback-code.patch - 0001-bootsplash.patch - 0006-bootsplash.patch - 0007-bootsplash.patch - 0008-bootsplash.patch - 0009-bootsplash.patch ./compile.sh BOARD=rockpi-4a BRANCH=edge RELEASE=bullseye BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=yes EXPERT=YES EXTRAWIFI=no This way it built ( with WARNINGS : which is to be polished ) at least 5.16, Armbian_22.02.0-trunk_Rockpi-4a_bullseye_edge_5.16.1_minimal.img. However patches removed either need to be revised ( and come back in ) or in most happy scenario indeed simply can be removed ( like for ess audio ) Also I would be happy to see an "lsmod" from rockpi4a+ which can be compared with rockpi4a. Perhaps also radxa image and armbian image need to be put side by side so a proper ".config" can be created for 5.16.y edge kernels. Hopefully we ( community ) can spend some effort coming months ( years :-) ) getting the 4a+ stable as I assume there are loose ends with this 'new' OP1 board. Meanwhile like to do some trial and error on its .config next few days, but won't expect my 4a+ in before February 2022... If appreciated I can post my current compilation and other output logs, I attached " compilation.log " and rgd WARNINGS: - Bootsplashes fail due to removal patches ( missing dependencies ) - Bluetooth can be ignored for rockpi4a/4a+ These need to be looked in to ( as well bootsplashes ): [ warn ] * [l][c] board-pbp-setup-USB-type-c-port-as-dual-dat.patch [ failed ] [ warn ] * [l][c] board-rockpis-0008-thermal-rockchip-add-tsadc-support-for-rk3308.patch [ failed ] [ warn ] * [l][c] board-rockpis-0016-ASoC-rockchip-add-support-for-rockchip-i2s-tdm-contr.patch [ failed ] [ warn ] * [l][c] general-add-panel-simple-dsi.patch [ failed ] Yup most likely there is some rework required... compilation.zip
  25. We are moving soon to next LTS kernel, where my OrangePi 4 has not problems connecting to wifi: http://ix.io/3MKQ WiFi chip - at least on mine - is Broadcom: [ 7.839285] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 [ 7.840127] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 7.841615] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Feb 11 2020 11:54:51 version XXX.XXX.96.61 (be7af2d@shgit) (r745790) FWID 01-a41d86bd es7.c5.n4.a3
  1. Load more activity