All Activity

Hello all! After upgrading to OMV 7 and Debian 12 my OLED display remains dark. I am using Kobol Helios 4 NAS. Can anyone tell me where the problem is? When i try to execute git clone https://github.com/kobol-io/sys-oled.git cd sys-oled sudo ./install.sh I get the following error message via SSH. Installing luma.oled library error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to install. If you wish to install a non-Debian-packaged Python package, create a virtual environment using python3 -m venv path/to/venv. Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make sure you have python3-full installed. If you wish to install a non-Debian packaged Python application, it may be easiest to use pipx install xyz, which will manage a virtual environment for you. Make sure you have pipx installed. See /usr/share/doc/python3.11/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. Installing sys-oled files 'etc/sys-oled.conf' -> '/etc/sys-oled.conf' 'bin/sys-oled' -> '/usr/local/bin/sys-oled' 'share/sys-oled/C&C Red Alert [INET].ttf' -> '/usr/local/share/sys-oled/C&C Red Alert [INET].ttf' 'share/sys-oled/helios4_logo.png' -> '/usr/local/share/sys-oled/helios4_logo.png' 'system/sys-oled.service' -> '/etc/systemd/system/sys-oled.service' Enabling sys-oled at startup Does anyone have an Idea what to do?

I have reinstall the device and the docker. However, I need to install the firmware 5.10.160. Indeed the nanopc-t6 don ot star with any image with firmware 6.1.43 or 6.8.9. I do not understand why ?. Apprently I understand that you are able to install the version 6.1.43 without issue. Could you please explain me the procedure you have used ? Thanks in advance for your support.

This was more of an fyi. I am happy running the v20 image.

@helix ff510000.mmc is disabled in led-conf3 because led-conf3 is for MXQ-RK3328-D4 board, which accidentally has rk805 PMIC and fixes something. But clearly led-conf3 is not tailored for your board, hence not all the hardware works.

I think Windows Drives Management has difficulty with understanding Linux partitions. Hopefully SD Formatter detects SD cards without assigned drive letter. It formats cards to FAT16 and then Drives Management sees that drive and allows assigning drive letter. After that I was able to test one of my Kingston cards. h2test2 output: Warning: Only 14795 of 14796 MByte tested. Test finished without errors. You can now delete the test files *.h2w or verify them again. Writing speed: 9.82 MByte/s Reading speed: 77.9 MByte/s H2testw v1.4 Not very fast but with no problems. So I used that card and burned Armbian with balena Etcher. Earlier I wad using Rufus. After all, booting stops in the same place.

find a board with u-boot 2024 and rebase your board config file I use OrangePi3B as a base config

https://drive.google.com/file/d/1n_sMewTbbszuEFHhpL-dNqHBiOwUtdJT/view Part 2.6

Can't find that image anywhere and no matter what i try (even the banana pi supplyed ones) refuse to boot into emmc. When going into the U-Boot shell with a SD-Card plugged in i can get this env => env print arch=arm baudrate=115200 board=sunxi board_name=sunxi boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr} boot_efi_binary=load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootarm.efi; if fdt addr -q ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi boot_efi_bootmgr=if fdt addr -q ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr;fi boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf} boot_net_usb_start=usb start boot_prefixes=/ /boot/ boot_script_dhcp=boot.scr.uimg boot_scripts=boot.scr.uimg boot.scr boot_syslinux_conf=extlinux/extlinux.conf boot_targets=fel mmc_auto usb0 pxe dhcp bootcmd=run distro_bootcmd bootcmd_dhcp=devtype=dhcp; run boot_net_usb_start; if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi;setenv efi_fdtfile ${fdtfile}; if test -z "${fdtfile}" -a -n "${soc}"; then setenv efi_fdtfile ${soc}-${board}${boardver}.dtb; fi; setenv efi_old_vci ${bootp_vci};setenv efi_old_arch ${bootp_arch};setenv bootp_vci PXEClient:Arch:00010:UNDI:003000;setenv bootp_arch 0xa;if dhcp ${kernel_addr_r}; then tftpboot ${fdt_addr_r} dtb/${efi_fdtfile};if fdt addr -q ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r}; else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi;fi;setenv bootp_vci ${efi_old_vci};setenv bootp_arch ${efi_old_arch};setenv efi_fdtfile;setenv efi_old_arch;setenv efi_old_vci; bootcmd_fel=if test -n ${fel_booted} && test -n ${fel_scriptaddr}; then echo '(FEL boot)'; source ${fel_scriptaddr}; fi bootcmd_mmc0=devnum=0; run mmc_boot bootcmd_mmc1=devnum=1; run mmc_boot bootcmd_mmc_auto=if test ${mmc_bootdev} -eq 1; then run bootcmd_mmc1; run bootcmd_mmc0; elif test ${mmc_bootdev} -eq 0; then run bootcmd_mmc0; run bootcmd_mmc1; fi bootcmd_pxe=run boot_net_usb_start; dhcp; if pxe get; then pxe boot; fi bootcmd_usb0=devnum=0; run usb_boot bootdelay=1 bootm_size=0xa000000 console=ttyS0,115200 cpu=armv7 dfu_alt_info_ram=kernel ram 0x42000000 0x1000000;fdt ram 0x43000000 0x100000;ramdisk ram 0x43400000 0x4000000 distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done efi_dtb_prefixes=/ /dtb/ /dtb/current/ ethaddr=02:01:7e:b0:bb:78 fdt_addr_r=0x43000000 fdtcontroladdr=bbf5e620 fdtfile=sun8i-a83t-bananapi-m3.dtb fdtoverlay_addr_r=0x43300000 kernel_addr_r=0x42000000 load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}${efi_fdtfile} loadaddr=0x42000000 loadsplash= for prefix in ${boot_prefixes}; do if test -e mmc 0 ${prefix}boot.bmp; then load mmc 0 ${splashimage} ${prefix}boot.bmp; bmp d ${splashimage}; fi; done mmc_boot=if mmc dev ${devnum}; then devtype=mmc; run scan_dev_for_boot_part; fi mmc_bootdev=0 partitions=name=loader1,start=8k,size=32k,uuid=${uuid_gpt_loader1};name=loader2,size=984k,uuid=${uuid_gpt_loader2};name=esp,size=128M,bootable,uuid=${uuid_gpt_esp};name=system,size=-,uuid=${uuid_gpt_system}; preboot=usb start pxefile_addr_r=0x43200000 ramdisk_addr_r=0x43400000 scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;run scan_dev_for_efi; scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done; setenv devplist scan_dev_for_efi=setenv efi_fdtfile ${fdtfile}; if test -z "${fdtfile}" -a -n "${soc}"; then setenv efi_fdtfile ${soc}-${board}${boardver}.dtb; fi; for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${efi_fdtfile}; then run load_efi_dtb; fi;done;run boot_efi_bootmgr;if test -e ${devtype} ${devnum}:${distro_bootpart} efi/boot/bootarm.efi; then echo Found EFI removable media binary efi/boot/bootarm.efi; run boot_efi_binary; echo EFI LOAD FAILED: continuing...; fi; setenv efi_fdtfile scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${boot_syslinux_conf}; then echo Found ${prefix}${boot_syslinux_conf}; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done scriptaddr=0x43100000 serial#=32c004017eb0bb78 soc=sunxi splashimage=66000000 splashpos=m,m stderr=serial stdin=serial,usbkbd stdout=serial usb_boot=usb start; if usb dev ${devnum}; then devtype=usb; run scan_dev_for_boot_part; fi uuid_gpt_esp=c12a7328-f81f-11d2-ba4b-00a0c93ec93b uuid_gpt_system=69dad710-2ce4-4e3c-b16c-21a1d49abed3 Environment size: 4905/65532 bytes Also i can access the emmc once booted @Gunjan Gupta Do you have any idea where to go from here or where to find more info on how to maybe get it booting from emmc ?

@ebin-dev You are not alone, I also use the 2.5GB interface 😉

I have a very good understanding of bash commands I just read it differently than you intended, everything actually worked without applying the patch so I'm not sure what we've achieved. What doesn't work is downloading a fresh clone - thanks for your help Edit Someone must have merged the fix into the current tree as it now works perfectly again - thanks again

Unfortunately, it didn't work. I want to build u-boot 2024 (since the old u-boot 2019 is being used now). But it doesn't work out for me. I can't change defconf, since ./compile.sh CREATE_PATCHES="yes", doesn't work now. I try CREATE_PATCHES (uboot-patch) but I don't get a pause to make changes. I used to use CREATE_PATCHES=yes and everything worked, now I can't build u-boot with my settings. You need more detailed instructions in the description of build options

Hello, In led-conf3 overlay sdio card on mmc1 is disabled as I can see, so wifi does not work with this overlay. I'm trying to add lines about rk805 to the initial working config rk3318-box and compile it, but it breaks sdio somehow: [ 1.141446] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 1.141560] mmc1: error -110 whilst initialising SDIO card [ 1.141743] dwmmc_rockchip ff510000.mmc: card claims to support voltages below defined range [ 1.145758] mmc1: error -110 whilst initialising MMC card [ 1.171182] mmc_host mmc1: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0) [ 1.345809] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 1.345933] mmc1: error -110 whilst initialising SDIO card [ 1.346116] dwmmc_rockchip ff510000.mmc: card claims to support voltages below defined range [ 1.350139] mmc1: error -110 whilst initialising MMC card [ 1.376838] mmc_host mmc1: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0) [ 1.618019] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 1.618141] mmc1: error -110 whilst initialising SDIO card [ 1.618299] dwmmc_rockchip ff510000.mmc: card claims to support voltages below defined range [ 1.622240] mmc1: error -110 whilst initialising MMC card [ 1.648896] mmc_host mmc1: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0) [ 2.096685] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 2.096818] mmc1: error -110 whilst initialising SDIO card [ 2.097000] dwmmc_rockchip ff510000.mmc: card claims to support voltages below defined range [ 2.100963] mmc1: error -110 whilst initialising MMC card [ 2.114878] mmc1: Failed to initialize a non-removable card Same result with rk3328-evb.dts from mainlain kernel 6.6.30, which have rk805 support by default. Ok, may be &sdio { vmmc-supply = <&vcc_io>; } is missing, so i add this line also, but card still does not initialising: [ 1.144440] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 1.144552] mmc1: error -110 whilst initialising SDIO card [ 1.167189] mmc_host mmc1: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0) [ 1.341046] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 1.341166] mmc1: error -110 whilst initialising SDIO card [ 1.367235] mmc_host mmc1: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0) [ 1.599001] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 1.599115] mmc1: error -110 whilst initialising SDIO card [ 1.625242] mmc_host mmc1: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0) [ 2.077057] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 2.077170] mmc1: error -110 whilst initialising SDIO card [ 2.077353] dwmmc_rockchip ff510000.mmc: card claims to support voltages below defined range [ 2.081314] mmc1: error -110 whilst initialising MMC card [ 2.095266] mmc1: Failed to initialize a non-removable card finnaly i managed to initialize sdio with enabled rk805: &sdio { post-power-on-delay-ms = <0x100>; }

😞 Please read some documentation on BASH commands. The BASH command: ls ../fix-6.6.30-version.patch Command output: ../fix-6.6.30-version.patch This only tells you that the patch file is in /mnt/music/Armbian/fix-6.6.30-version.patch If there are modified files in the build system itself, you will not be able to update it. Therefore, it is necessary to check the status. git status And if the files exist then make a command: git restore file1 file2 .... Where file1 and file2 ... are the files reported by the command git status The git pull command will pull the latest updates from the remote repository. Apply the patch that I posted: patch -p1 -i ../fix-6.6.30-version.patch After that, run the build command: ./compile.sh .......... All commands must be executed in the /mnt/music/Armbian/build directory

The problem is that everything worked fine (with normal HDMI cable, 4K screen and stable Armbian 24.2.1 ). And suddenly on the next usual boot, there was no video output and no screen detected in settings. I've checked cable and monitor with another devices - everything works fine. I've checked another normal HDMI cable and monitor with this Orange PI 5 - no output detected. Also I can still see video using type-c to DisplayPort output. So the problem is something wrong with HDMI output. Either on firmware level (I have lots of error using sudo update/upgrade the last time everything worked ), or on hardware level (maybe something on my SBC just broken/heated due to poor quality). I flashed firmware several times and it didn't help

Hi Fedes_gl! HDMI is working, but I could not play any video or audio due to missing applications and any internet connection.

@helix afaik, no tool for that. phandles are the way how kernel navigates the device tree. BTW, you may wish to try to enable box-wlan-ap6330 or box-wlan-ap6334 device tree overlay in /boot/armbianEnv.txt and see if you advance in getting bluetooth: broadcom chips have the need for some bits in the device tree to load the driver and attach the communication "bus" (which is usually a simple UART port). Also they are very similar chips. the driver is usually capable of handling the detection of features despite you declare a different chip in device tree. You can see the source of the ap6330 overlay here And yes, you definitely need to enable the led-conf3 because the dtb declares that your board definitely has a rk805 PMIC: that's why the photo of the board is heavily suggested in the first page to get help.

Description After testing, it was found that Firefly-RK3399 cannot boot using the mainline device tree due to issues with the PMU (Power Management Unit). Even after fixing the PMU problem, Bluetooth still cannot be used. Therefore, the original patch has been optimized by removing unnecessary parts. How Has This Been Tested? [x] Almost all hardware functions(HDMI, WiFi, BT, GbE, USB...). [x] System startup. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Cannot tell for sure since I do not have this board. However I would use a multimeter and measure the voltage between the outer pins to determ which is GND and which is 5V. Then I'd hook ground to ground and randomly connect rxd and txd. The chances are 50:50 to get it right the first try. If there is no output, swap rxd and txd and try again.

@going thank you for your time - I tried your suggestion and got this ../fix-6.6.30-version.patch diff: unrecognized option '--git' diff: Try 'diff --help' for more information. ../fix-6.6.30-version.patch: line 2: index: command not found ../fix-6.6.30-version.patch: line 3: ---: command not found ../fix-6.6.30-version.patch: line 4: +++: command not found ../fix-6.6.30-version.patch: line 5: @@: command not found ../fix-6.6.30-version.patch: line 7: syntax error near unexpected token `)' ../fix-6.6.30-version.patch: line 7: ` current)

Hi Werner, thanks a lot for your recommendations. I finally found some time to go back to the issue. I bought a CP2102 USB UART Adapter as you recommended in your video. The Odroid h1 has a Molex 5268-04a coonncetor mounted on its PCB. In the "ODROID Port description of UART Connector" (https://wiki.odroid.com/accessory/development/usb_uart_kit) the pins are described like follows. However, on the board itself the pins are not marked. I would not want to destroy anything here. Do you know which is which? _____UART____ |Pin 4 - VCC| |Pin 3 - RXD| |Pin 2 - TXD| |Pin 1 - GND| \___________| BTW: In the manual (https://magazine.odroid.com/wp-content/uploads/odroid-xu4-user-manual.pdf#page=7) the baud rate is specified with 115200.

lib & config: give shellcheck directions (to /dev/null for dynamic, to repo-relative path for static) for all sourced references lib & config: give shellcheck directions (to /dev/null for dynamic, to repo-relative path for static) for all sourced references in preparation for tightening the shellcheck severity level it needs to be able to follow all sources; dynamic ones are ignored, static ones need root-relative prefix View the full article

t95z: add board file (and u-boot 2024.04) for T95Z Plus Amlogic tvbox t95z: add board file (and u-boot 2024.04) for T95Z Plus Amlogic tvbox we've had kernel patches/DT (from chewitt) for this in meson64 for a long time, but I never sent the board uses blobs for the tartiflette-s912 which is also an DDR3 S912 (VIM2's blobs are DDR4 and won't boot) this adds u-boot 2024.04 support, using chewitt's DT & 000.patching_config.yaml & a specific BOOTPATCHDIR this is a full board as-if it was an SBC, and expects to boot from mainline u-boot; for that to work you've to wipe the eMMC and get rid of the vendor-supplied u-boot if this is not what you want/need, you can use the aml tvbox "board" instead, together with Android u-boot View the full article

khadas-vim3: fix stray closing brace in board file khadas-vim3: fix stray closing brace in board file a stray closing brace, meant for the function, that ends up doing the wrong config change View the full article

"OLED stats working also in debian, you need to activate I2C5 M3 overlay in orangepi-config" By doing above, do you still need to execute point #1 (add overlay) from original instructions?