All Activity

just did another upgrade, 128 pkgs. no errors now but only 3 of the 5 drives show, but drives possibly too warm.drives are warm, need additional cooling. have 5" fan in front of enclosier but which pins do I connect it to? Or should I connect that big a fan direct to psu?

The drives are gigastones, made in Taiwan. Sata to usb3 Adaptor cables are latest StarTech's. I have had zero failures with that brand in over a decade of use here.

I am one of your monthly contributors. I too seem to be subjected recently, noted after doing an apt upgrade. -y. I have a 5 volt 5 amp supply for the bpi-m5 psu plugged into the C port. booting is now both intermittent and several mintes to get started. I have a usb3 hub with 7 usb3 ports plugged into one of the usb3 ports on the bpi-m5. The last of many attempts to boot it worked after the long delay so I plugged the hubs src cable back in to see if something has failed in the 5, 4T drives currently plugged in for amanda's use. But that now gets me an error msg, something about config #1 is returning an error 110, which it did NOT do a couple months ago. And dmesg is only reporting 4 drives. All intended to be one logical volume. Any idea how to determine which of hose 5 drives has gone toes up? Thank you. Gene Heskett, CET.

Hello Jock, thank you for all the work bringing this video acceleration to our boards. Can you give an updated comment about what to download or how to build Armbian OS, and get the needed requirements, before we apply the ffmpeg repository? I haven't been able to get video acceleration for many months. Can you tell us what new kernel modules are needed also?

I am trying to install box86 and possibly box64 on my Orange pi zero 2w. I tried using armbian-gaming as well as following the instructions found here, and attempting to build box86 with both resulted in a gcc error unrecognized command line option '-marm' Upon attempting to build box64 with the instructions, I get a make error 2, and the topmost error is a ccl error unknown value 'loongarch64' for '-march' This seems to be cross-compilation errors, but IDK what steps to take to fix it. Thanks in advance! QuowLord

vendor branch is based on latest rockchip bsp which is 6.1.115 atm. You can use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-config to switch.

I have the same issue with my tv box (RK3228A, the same one @Benedito Portela uses, only wireless lan works, the wired ethernet port does not work. It is present, the kernel sees the interface (end0), it detects the cable being plugged in, it even requests an IP address from DHCP, but it never takes it. I've tried to force it with a static IP, but I get no connectivity with that.

Good evening, I managed to complete the installation of my R29 without any problems, but it simply isn't recognized by my gigabit router. It works on my other secondary router, but I need it on my main one. I can also connect directly through my Ethernet notebook. I saw that it could be a problem with the router not accepting 10 Mbps, but ethtool says the TV Box is working at 100 Mbps. I don't know what else to try.

Are there any linux build config options needed to get the v4l2 functions? Can I assume that the improvements in 6.13.11 would be also in 6.15.4? No, the patches in pull/8086 are not in 6.14, 6.15 build/patch/kernel/archive/sunxi-6.13/patches.media vs the 6.14,6.15 folders Right now, linux-current is 6.12 and linux-edge is 6.15... I want to compile a Linux 6.13 Armbian OS... what specific linux version would I need to enter inside userpatches/lib.config ? KERNELBRANCH="tag:v6.13.xx" I tried building armbian 25.5.1 so I could get linux 6.14.x... but in the image file, there aren't the ko files mentioned in the pull/8086. For example: roberto@orangepizero3:~$ ls /lib/modules/6.14.5-edge-sunxi64/kernel/drivers/media/v4l2-core/ tuner.ko v4l2-cci.ko v4l2-fwnode.ko v4l2-jpeg.ko v4l2-vp9.ko v4l2-async.ko v4l2-dv-timings.ko v4l2-h264.ko v4l2-mem2mem.ko videodev.ko roberto@orangepizero3:~$ ls /lib/modules/6.14.5-edge-sunxi64/kernel/drivers/media/v4l2-core/v4l2-io* ls: cannot access '/lib/modules/6.14.5-edge-sunxi64/kernel/drivers/media/v4l2-core/v4l2-io*': No such file or directory

Hello Mark, Sorry, I think I solved the problem by creating a readme file. Now you can create a fork of the github projet: https://github.com/GuillaumeLopere/Armbian-TX95Max-AllwinnerH618/fork - Then you can add documents with "+" and "Upload files" - "Choose your files" and Check the box "Create a new branch for this commit and start a pull request" I think this is the easiest way to do it. Best regards, Guillaume

https://bugs.launchpad.net/ubuntu/+source/postgresql/+bug/2116789

Ok thanks there. Mind you their kernel is the older 5.x branch, so I'm kinda in two minds about that. ljones

OK I've actually found the crux of the issue, though I haven't tried to figure out specifically what causes it yet. I ordered another Dumb TypeC->DP adapter cuz I figured there might be a bridge in my last one that was messing things up. It did the same thing with the messed up colors and shifted image. Then I remembered I have a typeC dock that's smart and has a DP port and it works fine. Checking Dmesg I noticed the dock sets up link training for 2 lanes @ 8.1Ghz. The dumb adapters with the bad color train 4 lanes at 2.7Ghz because that's what my display advertises. The Orange Pi5 Plus manual states: 1 x Type-C (DP 1.4A) output, up to 4K@60FPS To meet that bandwidth it needs to supply either 4 DP lanes @ HBR2 or 2 DP lanes @ HBR3. I reprogrammed My display's bridge (it's custom) to advertise only 2 DP lanes at 2.7Ghz. Now that's what the Opi does and the image is perfectly fine. So I think what happens here is the Orange Pi 5 may not actually have 4 lanes to supply over type C but it's configured so that it will try if requested. The 2 lanes of DP it can supply are incomplete as they are expecting to be merged with the other 2. When using a smart typeC dock, it intercepts the display's DPCD report and says "I only have 2 lanes at HBR3 so that's what I want". On a Type C dock with USB ports it's not possible to pull 4 lanes out of the host connection because the other 2 lanes have to be used for USB3.x. So basically the Opi has to be told the sink only has 2 lanes or it will screw up when it delivers 4 lanes and can't. I assume that's the correct assessment cuz I can plug this thing into any other PC with a real DP or type C alt and the color is fine, reporting 4 lanes over DPCD. I assume this is probably a device tree thing, I'll update the git issue on Opi's kernel repo, just figured it'd be good to let anyone trying to use it what might be going on.

Hello, I have a MXQ Pro 5G 4K TV Box with Allwinner H616 and the motherboard IK316-EMCP_V4.1. I am looking for a server (CLI only) version of the Armbian image for this device. The previously shared Google Drive links in this topic are no longer working. Could someone please provide a new download link (Google Drive, MEGA, etc.) for the latest server image compatible with my device? If there are any specific instructions for booting or the correct DTB file, please let me know. Thank you very much! Best regards, Luska1331 BTW: I generated this message with the help of Copilot because I don't speak English very well.

Difficult to say how to fix without further logs. What I am looking into and what it could possibly be related to is the simpledrm module loading alongside sun4i-drm. I wonder if you remove simpledrm then does the cursor become less erratic? Without diverging to far off topic, I suspect this related to sun4i-gpadc and how the temperature sensor is polled is carried out. The 6.12 Hdmi patches are a backport of the changes found in 6.15.

Ok, maybe @jock has some suggestions to this issue.

@Werner - When the Armbian Official Nobel upgrades it has the same issue. Will look at going back to Debian tomorrow.

I modified the armbianEnv.txt file : verbosity=1 extraargs=coherent_pool=2M bootlogo=false overlay_prefix=rk322x fdtfile=rk322x-box.dtb rootdev=UUID=87d2bf72-4b91-4d33-8f77-284fa91fc3a7 rootfstype=ext4 extraargs=drm_kms_helper.edid_firmware=HDMI-A-1:edid/1920x1080.bin video=HDMI-A-1:1920x1080@60 drm.debug=0x4 overlays= usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u This is apparently preventing the tv box from booting, I lost access. I will have to flash it again with the multitool to get back in, and this will have to wait on monday, since I was remoting into it at the office. Thanks for your help!

Can you check if you can pass drm.debug=0x4 to the kernel command line and see if you get more info ? If yes, paste here the boot log.

Thanks for the hint Sirmalinton. Today, I could solve the problem. Here is a short summary that might be of use for people running into similar issues. Running lspci -k shows the "Non-Volatile memory controller" but it does not show the line "Kernel driver in use: nvme". Hence, I ran echo nvme > /sys/bus/pci/devices/0002\:01\:00.0/driver_override echo 0002:01:00.0 > /sys/bus/pci/drivers_probe where 0002:01:00.0 is from the output of lspci -k. That worked and made the disk appear as files /dev/nvme0*. To have a solution that works after reboot, I created a udev rule /etc/udev/rules.d/99-nvme-override.rules with the content: ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x144d", ATTR{device}=="0xa80d", ATTR{driver_override}="nvme" The vendor and device IDs are from lspci -nn. To trigger the probe, I created a systemd service /etc/systemd/system/nvme-rebind.service with the content: [Unit] Description=Rebind NVME controller to driver after override After=udev.service [Service] Type=oneshot ExecStart=/bin/sh -c "echo 0002:01:00.0 > /sys/bus/pci/drivers_probe" [Install] WantedBy=multi-user.target The service can be enabled via systemctl enable nvme-rebind.service. Maybe one reason it does not work in the first place is because /lib/systemd/system/nvmefc-boot-connections.service is not started. The reason is that the condition ConditionPathExists=/sys/class/fc/fc_udev_device/nvme_discovery is not met. Another reason, I can imagine is that the vendor/device ID combination is not registered to the nvme driver in the current kernel. As I mentioned before, it did work out of the box when I installed Armbian at first.

Well, since this same edid file I use on the Libre Renegade board works perfectly fine with this same monitor, I think the file is ok. This link you provide is the one I followed, I tried most of the things in there, as well as a bunch of stuff I found from other users. Again, since this works on U-Boot, this points at something defective on Armbian and how the edid communication happens. This Armbian kernel that came with the armbian image I downloaded it from the armbian github as a part of the image I use on my device. I did not build it. I would think it was the Armbian team, correct?

More like a kernel issue than Armbian. The Armbian supplied edid bin file probably does not match your monitor's. Take a look here on how to get the actual edid and force it: https://wiki.archlinux.org/title/Kernel_mode_setting#Forcing_modes_and_EDID

Yes, The 1920x1080.bin file comes with Armbian. I use the multitool to flash https://github.com/armbian/community/releases/download/25.8.0-trunk.309/Armbian_community_25.8.0-trunk.309_Rk322x-box_bookworm_current_6.12.35_minimal.img.xz , this is the latesst build. On a Libre Renegade board I have (rk3328 CPU instead of rk3228 for this TV box), I have the same issue where it reverts to 1024x768, and adding the line extraargs=drm.edid_firmware=edid/1920x1080.bin to armbianEnv.txt fixes the issue, with the Armbian provided 1920x1080.bin file. To me, since it works fine under U-Boot, this hints at an Armbian bug.

@Igor thank you for fixing overlay-prefix problem in current armbin-config now on OZPI V1 and V3 overlays in armbianEnv.txt are without prefix

Do you actually have this edid file : edid/1920x1080.bin ? How did you generate it?