Active threads

Hi, To my side, it's too complex and risky for me to change hardware components on Helios64. I prefer for my case of uses change CPU Freq and Governor for less performance but stable inside take risk of damage my board by change components. Have a good day

@Igor This line may sound rude, but you are probably waiting for the developers of the source code to take some action to improve patches or kernel settings. As long as this heresy is present in the build system (bad package build scripts), the project will receive crumbs from what developers can and do locally.

I don't have a TTL at the moment, but I can confirm too that: Armbian 24.2.1 Jammy CLI - does not boot Armbian 24.2.1 Bookworm CLI - boots tagging the maintainer for visibility @schwar3kat

Currently as a desktop. Wanted to try it out, but the kernel update over apt upgrade bricked my device. So I need to reflash everything. I am still doing everything on the current 6.6 kernel. IR works I just need to create a keymap and I will test KODI out - just need to recompile it in a VM. I am still waiting for my sound bar that has SPDIF to test it out. I think currently it is not working as I saw that spdif@fe460000 is currently disabled. I am also looking for the current Linux-headers file 6.6.28 so that I can try with openvfd. I was unable to find them with the previous kernel version 6.6.27. Once I install everything back I will retry this. What is funny about this box - every reinstallation brings a new MAC address. I am also trying to set up a CasaOS - currently in YouTube mode on how to set up Cloudflare tunnels.

You are choosing to use the edge kernel, which is the 'bleeding edge" development work area, it is expected to be unstable. If you want fewer issues you shouldn't be using edge.

Installed this on an old Heltec Helium miner Any idea how to enable SPI so spidev shows in /dev/?

Manged to boot latest armbian on Transpeed T98 6K clone. Don't quite understand actions needed to boot from SD card, but investigating uBoot setup I noticed, that it can also boot from USB stick. I'd like to join the development. Device looks promising.

After blaming: - networkmanager - ifupdown - systemd - my router - my provider - myself I tested with a separate wifi AP (not managed by my provider) and sprdwl_ng crashes to the point of being incapable of "seeing" any network again (until rmmod and insmod) when the same ESSID is broadcast both under 2.4Ghz and 5.5Ghz My wild assumption is that this driver doens't like (buggy perhaps?) to be "band-steered" Whens ticking to a single band, no issue. Hope it helps someone in my same situation

Hi Kanken, can you link that build please? I (and I imagine lots of others) would be very interested in trying it!

Yea my biggest issue here is getting it to run without having to keep android on it . We have successfully created a duel boot but that takes up mem I also know a project that uses raspberry pi boot loader to install onto the rockchip . Your right it seems its a free for all

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

@SteeMan Yes i did it that way. Inserted the SD with the fix for boot. It booted, then I powered of and removed SD. After that I Inserted the Armbian SD card but then is when the boot loop appears. So there was no way to boot form any SD card anymore. But still works on Android TV when no SD card is present. Please let me know if I'm doing something wrong. Thank you.

While I managed to land support for two extensions, implementing control flow re-convergence in NVK did not go as planned. This is the story of what went wrong and how we fixed it. View the full article

Thanks @Igor for your help, yes, I did, but now found out, that installed headers are: /usr/src/linux-headers-6.6.16-current-rockchip64 while kernel still was Linux odroidm1 6.1.12-rk3568-odroid #23.02.2 SMP PREEMPT Sat Feb 18 00:05:38 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux I got my Frozen kernel in armbian-config somehow solved by updating firmware and rebooting several times. Now kernel and headers are in sync again and zfs-module gets loaded! I will need to reanimate my odroidc2, which I use as a standby for the odroidm1, since that device doesn't boot any more after reinstall latest kernel, but that's another story ... Thanks!

Greetings Armbian Community, We’re thrilled to share our latest strides in enhancing partnerships, expanding support, and advancing innovations within the Armbian ecosystem. Here’s a roundup of recent developments: 1. Strengthening Partnerships in Shenzhen: We’ve embarked on a mission to fortify our collaborations with partners in Shenzhen, aimed at fostering better support for our community. During our visit, we engaged with both existing and potential partners to deepen our ties and enhance the services we offer to you. Read more 2. Platinum Support and Giveaway for Bananapi M7: We’re excited to announce the launch of platinum support and a special giveaway for the latest Bananapi M7, a collaborative effort between Bananapi and ARMSOM. This initiative aims to provide unparalleled assistance and rewards to our valued users. Learn more 3. Expansion of Community Build Framework: Our community interaction has led to the integration of several new boards, including SakuraPi and H96 TV box, into our build framework. Additionally, we’ve upgraded u-boot on 32-bit Rockchip devices and successfully ported Khadas Edge 2 to kernel 6.1. Moreover, FriendlyElec NAS now runs on mainline-based kernels, enriching our ecosystem with more versatile options. 4. Ongoing Upgrades and Future Ventures: In the pipeline, we have several exciting upgrades underway. We’re working on upgrading the Odroid XU kernel to version 6.6 and adding support for Orangepi 5 PRO. Furthermore, we’re introducing mainline kernel support for Orangepi Zero 2W, and our team is eagerly diving into the development of the new Radxa Rock 5 ITX board and Rock 5C. Stay tuned for more updates as we continue to elevate the Armbian experience! Best regards, The Armbian Team View the full article

You are probably going to need a share name after the IP address smb://10.10.2.101/sharename Running smbclient from the command line will give you more feedback and allow you to search for shares.

Seems this issue has been fixed, I am able to use the new kernel now with video playback. I did not do anything different...just update/upgrade.

This comment describes a recovery method without shorting the pins. I haven't tried this method.

Hello, I need to create images for multiple boards (rpi4b, rpi5b, rock3a, rock5b, orangepi5, orangepi-plus, nanopct6 and khadas-vim4) for a Kubernetes cluster running ceph and cilium, hence I need some new modules and parameters in the kernel. I created a simple playbook that changes the parameters in build/config/kernel/linux-* which works. What does not work is calling compile.sh with the required parameters. The task gives an error and stops after 5 minutes or so. If I run the commands from the prompt, everything is fine...but not convenient. The Ubuntu VM used for the compilation is created on a Fedora 40, with Vagrant, and I gave it 30 cores and 30GB of RAM with plenty of disk to run. vars: board_build: rpi4b: "BOARD=rpi4b BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm" rpi5b: "BOARD=rpi5b BRANCH=edge BUILD_DESKTOP=yes BUILD_MINIMAL=no \ DESKTOP_APPGROUPS_SELECTED='browsers desktop_tools internet multimedia remote_desktop' DESKTOP_ENVIRONMENT=xfce \ DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=jammy" rock3a: "BOARD=rock-3a BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm" rock5b: "BOARD=rock-5b BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm" opi5: "BOARD=orangepi5 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm" opi5p: "BOARD=orangepi5-plus BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm" nanopct6_edge: "BOARD=nanopct6 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm" nanopct6_legacy: "BOARD=nanopct6 BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm" vim4: "BOARD=khadas-vim4 BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=yes CLI_TARGET=bullseye KERNEL_CONFIGURE=no RELEASE=bookworm" [...] - name: Compile images ignore_errors: true ansible.builtin.shell: | ./compile.sh {{ board_build[item] }} args: executable: /bin/bash chdir: build register: compile_output changed_when: true loop: "{{ board_build.keys() }}" loop_control: label: "{{ item }}" Thank you, Stefanita Vilcu

Bookworm is latest stable. You can only upgrade to unstable ... which is not recommended for production. You could upgrade kernels, but we don't provide them anymore for bullseye. That is correct. This is the list of packages per distribution: https://fi.mirror.armbian.de/apt/content.html Bullseye only has some files, probably by mistake. It should be just empty as its not supported anymore. Change tags in armbian.list from bullseye to bookworm and update. Should be fine .... at least as far as from Armbian perspective. We can't vouch for packages that are coming from Debian repository as they might come into some conflicts between each other. This is the problem we observe on older releases and have no capacity nor wish to address.

@Ikesankom I did a quick test jiggling with bootloader to try and test multiple cases with both sdcard and emmc. I found a little "bug": there is no "alias" for the mmc devices in the device tree, so sometimes at boot the emmc is mmcblk0 and sdcard il mmcblk2, sometimes they get swapped. Anyway, despite this bug, the installer never broke the existing bootloader, at most it could miss the right device (I should check the logic behind, as it is not so easy guess what is the booting device) if you have both emmc and sdcard plugged. It's not a big deal though: the bootloader has got no real updates in a while since it works fine and the important thing is that the script does not destroy anymore the existing bootloader 😁 Anyway, if the board is remotely installed and controls something important, and you want extra-safety, you can do apt-mark hold linux-u-boot-tinkerboard-current and prevent bootloader upgrades

Thank you so much Micsa! This config really "just" worked for me. Now Banana Pi detects either my DS3231 or DS1307 clock.

Directly no as it doesn't have any software that would allow this. This way (via SD or eMMC): https://docs.armbian.com/User-Guide_Getting-Started/#how-to-install-to-emmc-sata-nvme-usb

@royk thanks for the build, still i didn't test it but i performed some new tests, using the dist from Joshua Riek as Ubuntu is ready, with GPU, and the Kernel is already patched And same problem with Nexus, but i was able to build Omega and is working fine if in System -> Video i select my TV on not the default option (dunno why), after that i can change the resolution to 1080p and everything is working fine, HDR10, x265, x264, 4k.. all good although when i start a video the change of resolution is a bit slow and in the Kodi logs i can see an issue with the EDID: 2024-04-22 10:53:53.119 T:2038 error <general>: [display-info] Error parsing EDID: 2024-04-22 10:53:53.119 T:2038 error <general>: [display-info] ---------------------------------------------- 2024-04-22 10:53:53.119 T:2038 error <general>: [display-info] Block 1, CTA-861 Extension Block: 2024-04-22 10:53:53.119 T:2038 error <general>: [display-info] Colorimetry Data Block: Reserved bits MD0-MD3 must be 0. 2024-04-22 10:53:53.119 T:2038 error <general>: [display-info] 2024-04-22 10:53:53.119 T:2038 error <general>: [display-info] ---------------------------------------------- after these messages in can see in the Kodi log that is able to load all the resolutions profiles Don't know if there is a fix for the EDID After installing Omega it create automatically the GBM profile, using that Kodi works, meanwhile if I'm using yours with the FFMPEG_RKMPP_DEC_OPT="afbc=on" option the video is not showing and Kodi crash cat /usr/local/share/wayland-sessions/kodi-gbm.desktop [Desktop Entry] Name=Kodi on GBM Comment=This session will start Kodi media center Exec=kodi-standalone --windowing=gbm TryExec=kodi-standalone Type=Application Keywords=audio;video;media;center;tv;movies;series;songs;remote; Icon=kodi Also, there was an issue with the python IMP module not found that caused some crashes, and addon probs. finally resolved installing python3-zombie-imp