Search the Community

I started seeing this happen "now and then" a couple of months ago, but over the last month it has gone to "multiple times a day". It's not always the same mirror. Frequently it's the airframes.io mirrors, this morning it was lv.auroradev.org The pattern is usually like this: Err:1 https://armbian.lv.auroradev.org/apt bookworm/main arm64 linux-libc-dev arm64 23.02.2 404 Not Found [IP: 23.186.113.5 443] E: Failed to fetch https://armbian.lv.auroradev.org/apt/pool/main/l/linux-6.1.11-sunxi64/linux-libc-dev_23.02.2_arm64.deb 404 Not Found [IP: 23.186.113.5 443] Is there a place to report these issues to get those mirrors fixed?

I can't seem to get apt-get update to work, this is a fresh install anyone know the fix? mango@nezha:~$ sudo apt-get update Hit:3 http://ports.ubuntu.com jammy InRelease Hit:4 http://ports.ubuntu.com jammy-security InRelease Hit:5 http://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu jammy InRelease Hit:6 http://ports.ubuntu.com jammy-updates InRelease Hit:7 http://ports.ubuntu.com jammy-backports InRelease Hit:1 https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium InRelease Hit:2 https://cli.github.com/packages stable InRelease Err:2 https://cli.github.com/packages stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 Reading package lists... Done N: Skipping acquire of configured file 'main/binary-riscv64/Packages' as repository 'http://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium InRelease' doesn't support architecture 'riscv64' W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://cli.github.com/packages stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 W: Failed to fetch http://cli.github.com/packages/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 W: Some index files failed to download. They have been ignored, or old ones used instead.

Hi all, I need to customize the /etc/fstab during the build to mount a mtd partition and also to override some mountpoints with tmpfs in order to reduce wearing on mmc. So, have added the following lines to customize-image.sh: cat <<EOT >> /etc/fstab # Reduce SD wearing by storing log files into ram (no need as overlayroot is used to freeze all the rootfs) tmpfs /tmp tmpfs defaults,noatime,nosuid,nodev 0 0 tmpfs /run tmpfs defaults,noatime,nosuid,nodev 0 0 tmpfs /var/tmp tmpfs defaults,noatime,nosuid,nodev 0 0 tmpfs /var/log tmpfs defaults,noatime,nosuid,nodev,noexec 0 0 tmpfs /var/lib/logrotate tmpfs defaults,noatime,nosuid,nodev,noexec,size=1m,mode=0755 0 0 tmpfs /var/lib/sudo tmpfs defaults,noatime,nosuid,nodev,noexec,size=1m,mode=0700 0 0 # MTD EEPROM memory dev/mtdblock0 /mnt/mtd jffs2 ro,relatime 0 0 EOT However changes in /etc/fstab are overridden somewhere over the build process, and this is the resulting /etc/fstab: UUID=c8167755-b557-4288-9109-9108bc48dd94 / btrfs defaults,noatime,commit=600 0 1 UUID=27ac6cc6-eff3-4736-a7bd-5517e3b150c0 /boot ext4 defaults,commit=600,errors=remount-ro 0 2 tmpfs /tmp tmpfs defaults,nosuid 0 0 Is there a way to safely patch the /etc/fstab file? Thanks very much! Andrea

I have a unique hardware setup with an ARMv8 architecture but a 32-bit 'armeabi-v7a' ABI. My goal is to install a 64-bit operating Ambian (or others, even a 64 bit Android Go if possible) system on this hardware, replacing the existing 32-bit setup. The device is a kids tablet ZIDS701 by Trayoo. The current OS is Android Go 10 32-bit. I'm kind of a newbie to firmware, so I'm reaching out to the knowledgeable members of this community for guidance and assistance in achieving this. I'm particularly interested in recommendations for a 64-bit OS that would be compatible with this setup and any steps or considerations I should be aware of during the installation process. Much appreciated thank you.

Armbian 22.05.0-trunk with bleeding edge Linux 5.16.20-rockchip64 my armbian runs on a MKS SKIPR motherboard for a 3d printer. Since I updated the system, I can no longer change any files. I change it but after a restart the file is back as it was.since i have updated the system for example this file nano /etc/resolv.conf After saving and restarting everything is as it was. no matter whether as root or user Is there a setting that prevents or reverses changes?

I don't know if this is the right subforum for this question. Would Armbian be possible for the PineTab2?

I'm trying to get the armbian x86-64 generic image to run in virtualbox. I can successfully convert the *.img file to qcow2 and qemu will run it just fine. However, virtualbox fails to boot it in any format (qcow2, vmdk, vhd, vdi, etc). The grub menu comes up, but when trying to boot Linux then it just sits at a blinking cursor. I've tried converting this a variety of ways, such as using `qemu-img convert`, `vboxmanage convertfromraw` and `vboxmanage convertdd`. None of them yield an image that virtualbox will boot. Has anybody else had success with this, and/or know how to fix it? Thanks.

I just buy the orange pi 3b powered by the Rockchip RK3566. Is there any plan to support this new SBC.

Hello friends, I apologize for such a noob question, but I was not able to find the answer in the forums, nor via duckduckgo. Since the 23.08 upgrades were released (thank you again to team Armbian!), I noticed that the "default" image for the Orange Pi 3 LTS is Armbian 23.8 Bookworm. The minimal CLI image weighs in at 267Mb. My OPi3LTS SBCs are all running Armbian Jammy 23.08. The minimal CLI image weighs in at 195Mb. My understanding is that Jammy is Ubuntu (22.04.3 LTS), and Bookworm is Debian (12.0). But also Ubuntu Jammy is based on Debian Bookworm/sid. My questions are as follows: 1. What goes into the decision to designate one or the other as the default (ie. listed in the hero section - above the "other supported variants")? 2. What constitutes the 72Mb difference between the images? 3. Other than obvious software incompatibility (ie. software requires either Ubuntu or Debian), what does one lose by moving from Jammy to Bookworm? 4. How does one upgrade to Armbian 23.8 Bookworm Minimal CLI from Armbian 23.8 Jammy Minimal CLI - without reformatting? Thank you team Armbian for all of your heroic efforts! Best Regards.

I've set up 23.02 Debian Bullseye CLI on my Orange Pi 5. I believe I read 23.05 is coming out soon. Would I just do an apt update and then apt upgrade to make the change? I'm at the point where I could just re-install and start with 23.05 but what would I do in the future for new updates? Thanks.

I would like to use a CI service to build Armbian images, ideally BitBucket pipelines since that is where most of my projects are. Has anyone had any success doing something similar? I thought it would be easy since docker based builds are supported, but it seems the supported technique is to run a command on the host that starts a separate docker container. Most CI build now are already running in a container and while I think running docker inside docker is possible, I have not been able to get that to work well in the past.

Wondering if it is possible to replace pfsense (freebsd 14) with Armbian on a netgate sg-2100 appliance? https://shop.telappliant.com/product/sg-2100-pfsense-security-gateway-appliance/ I have the version with an additional 32GB M.2 SSD and it looks like the mvebu_armada-37xx board is supported by the generic Armbian, but I struggle to get from u-boot to starting the installer from usb (used the Armbian_23.5.1_Uefi-arm64_bookworm_current_6.1.30_minimal.img), with the usbboot command. Below is the current u-boot environment. I have masked some parts with "xxxxx" and probably won't need half of these variables, as they are very vendor specific, for example netgateid etc. If possible, I would like to flash/replace the boot loader that is not specific for pfsense, but I am a total beginner with arm boards and boot loaders. Not as easy as installing various Linux distros... Marvell>> printenv arch=arm baudrate=115200 board=mvebu_armada-37xx board_name=mvebu_armada-37xx boot_file=efi/boot/bootaa64.efi bootcmd=run setLED; run mmcboot; run scsiboot; run usbboot; run net; bootdelay=2 cpu=armv8 dmi_board_mfg=Silicom dmi_board_name=xxxxxxxx dmi_board_serial=xxxxxxxx dmi_board_ver=R301 dmi_chassis_mfg=Silicom dmi_chassis_serial=xxxxxxxx dmi_chassis_ver=R301 dmi_sys_mfg=Silicom dmi_sys_name=SG-2100 dmi_sys_serial=xxxxxxxx dmi_sys_ver=R301 dtb_name=armada-3720-sg2100.dtb eth1addr=xxxxxxxx ethact=neta@xxxxxxxx ethaddr=xxxxxxxx ethprime=eth0 fdt_addr_r=0xc00000 fdtcontroladdr=7f623360 gatewayip=xxxxxxxx ipaddr=0.0.0.0 kernel_addr_r=0x1000000 load_dev=usb loadaddr=0x1000000 mmcboot=mmc rescan; setenv load_dev mmc; if fatls ${load_dev} 0:2 /; then run pfsenseboot; fi; net=dhcp; tftp ${fdt_addr_r} ${dtb_name}; tftp ${kernel_addr_r} loader.efi; fdt addr ${fdt_addr_r}; fdt set / sn ${dmi_sys_serial}; bootefi ${kernel_addr_r} ${fdt_addr_r}; netgateid=xxxxxxxx netmask=255.255.255.0 pfsenseboot=load ${load_dev} 0:2 ${fdt_addr_r} ${dtb_name}; load ${load_dev} 0:1 ${kernel_addr_r} ${boot_file}; fdt addr ${fdt_addr_r}; fdt set / sn ${dmi_sys_serial}; bootefi ${kernel_addr_r} ${fdt_addr_r}; pxefile_addr_r=0x2000 ramdisk_addr_r=0x2000000 rootpath=/srv/nfs/ scsiboot=scsi reset; setenv load_dev scsi; if fatls ${load_dev} 0:2 /; then run pfsenseboot; fi; serverip=0.0.0.0 setLED=i2c dev 1; i2c reset; i2c mw 67 ff 0; i2c mw 67 0 1; i2c mw 67 f 20; i2c mw 67 3 40; i2c mw 67 26 0; i2c mw 67 10 0; soc=mvebu stderr=serial@12000 stdin=serial@12000 stdout=serial@12000 usb_pgood_delay=4000 usbboot=usb reset; setenv load_dev usb; if fatls ${load_dev} 0:2 /; then run pfsenseboot; fi; usbrecovery=mmc erase 0 400000; run usbboot vendor=Marvell

Hello everyone, I'm new user about SBC and armbian. I recently purchased this SBC - purple-pi-oh (rk3566, Number/type of interfaces similar to Raspberry Pi), It has opened up its linux sdk and more. Because its default image version is older, and does not support k3s, cilium, etc (I'm a k8s ops), so I want to use armbian with it. I first directly downloaded and tried all rk3566/3568 images of other SBCs, such as station m2/station p2/Bananapir2pro, etc., and the most pleasant surprise was that using the station m2 image, purple pi oh almost works (can run through the installation process, mouse/keyboard/hdmi monitor works fine), the only regret is that the network card activation error, can not run properly. (It's so close.) △ The only problem, eth0 failed to activate. I am trying to build a custom image of Armbian for the purple pi oh, but I really don't have any relevant experience in this area. Can any of the experts guide me please? My simple idea is that, based on the station m2 situation, maybe with a few tweaks to the configuration, the rebuilt image will work perfectly fine. Thank you! Finally, English is not my first language, so I'm slower to read/comprehend and reply.

How can I access individual packages that make up the images that are available for download e.g. at https://www.armbian.com/lenovo-x13s/ ? I see only "full image" downloads and no link to information on what was used to build these images. I poked around the dists named "bookworm something" on apt.armbian.com looking for the kernel used, but didn't find any obvious match (no 6.3 kernel version, no kernel that has "x13s" in the package name, ...). Likewise, there is no x13s listed in https://github.com/armbian/build/tree/master/config/sources/families

Not sure if this should go in this section, but since my problem is about non-supported board, then I guess... I found out about Armbian only recently and decided to give it a try for my T113-S3 based board I bought on Aliexpress. It looks like it's some kind of a MangoPi MQ clone, at least judging by schematics. I managed to create a new configuration for my board, together with required U-Boot patches. I built two images, for "current" and "edge" kernel. For some time I was under impression that Linux doesn't boot at all (serial console output was stuck at "Starting kernel ..."), until I added earlycon=on to armbianEnv.txt. Then I finally saw some output from kernel being booted. But at some point it looks like it's stuck, or just doesn't show login prompt? It's hard to say. Logs from the "current" image look like this: Logs from "edge" image don't even come to that point: What could be wrong, or what could I be forgetting to set? I'd be grateful for any help, especially knowing that this board is not either officially nor unofficially supported. EDIT: I might have not been precise enough, I'm trying to login through serial console since I can't connect any screen to my board at the moment. I guess the lack of login prompt might be connected to this: "Warning: unable to open an initial console". It is connected with /dev/console device file, which might be needed for the serial console to work in userspace. I tried to track the warning down by adding some debug logs into kernel code and what I confirmed: - /dev/console device is created successfully - at the same time, while opening it (from within the kernel), open operation fails with ENODEV error What's going on?

i have already install pihole + unbound on this device now i want to reset everything so i can make a new project on it because of the limitation on storage.. can i know how to do that? and without change any kernel/firmware i'm beginner on linux ecosystem...

I found what a likely duplicate out-of-tree driver after investigating a warning from the kernel build: CC [M] drivers/gpu/drm/panel/panel-simple-dsi.o drivers/gpu/drm/panel/panel-simple-dsi.c: In function 'panel_simple_get_modes': drivers/gpu/drm/panel/panel-simple-dsi.c:310:73: warning: passing argument 3 of 'of_get_drm_display_mode' makes pointer from integer without a cast [-Wint-conversion] 310 | ret = of_get_drm_display_mode(panel->dev->of_node, mode, p->desc->bus_format, | ~~~~~~~^~~~~~~~of_get_drm_display_mode~~~~ | | | u32 {aka unsigned int} In file included from ./include/drm/drm_crtc.h:32, from drivers/gpu/drm/panel/panel-simple-dsi.c:13: ./include/drm/drm_modes.h:509:66: note: expected 'u32 *' {aka 'unsigned int *'} but argument is of type 'u32' {aka 'unsigned int'} 509 | struct drm_display_mode *dmode, u32 *bus_flags, | ~~~~~^~~~~~~~~ This code cannot work as is and a fix would be to add the missing ampersand before the p->desc->bus_format. Still other warning surface when this is fixed. This driver calls of_get_drm_display_mode against bus_format while panel-simple does against bus_flags (it also has bus_format but it passes it as an argument to drm_display_info_set_bus_formats). So it might well be that the driver would pass the wrong arguments. It has no documentation for its DTS parameters so it is hard to tell if bus_format should be set as bus_flags from the panel-simple documentation or if its user will end up sending bus_format as a bus_flags. There is already a dsi driver in upstream drivers/gpu/drm/panel/panel-simple.c (panel-dsi-simple while this one is panel-simple-dsi). So I wonder if there is a use in shipping two drivers for the same purpose. And there are no dts users of this out-of-tree driver panel-simple-dsi. The discussion about its introduction is in: https://github.com/armbian/build/pull/3140 It is told in the commit log to be a port of a rockchip kernel 4.4 driver, but panel-simple has dsi probe since v3.14. I am puzzled rockchip forked panel-simple instead of expanding it. Rockchip.DRM.Panel.Porting.Guide.pdf has no mention of the bus_format dts parameter so maybe this code path was never used and the buggy code affects no users. (a few dts parameters in the rockchip code are also not documented in this PDF). @iamdrq you are the author of this driver. Was there code missing in the dis support of panel-simple.c for dsi support, ie is panel-simple-dsi necessary? Was the aim to have a version of the panel dsi code that is bit-to-bit compatible with the rockchip kernel, so no porting was necessary? If features were missing could we bake them into the panel-simple.c driver (so they could be tested and one day be upstreamed)?

SMART AM40 iQ Appliance P/N: 1031572 Model: UGK-AM40-EDU | EWY1-AM40-EDU | EWY2-AM40-EDU Processor RK3399, Dual-core A72+Quad-core A53, 64 bits, 2GHz Memory 4 GB DDR3L SDRAM Storage 32 GB eMMC 5.1 Wireless technology Bluetooth 4.1 802.11A/B/G/N/Ac Capture options Establish a Bluetooth wireless connection with a supported mobile device Connectors HDMI 1.4 (1920 × 1080) output for external monitor USB 3.0 Type-A (×2) RJ45 Gigabit Ethernet --Update-- For device tear-down and technical sheets included in package - SEE SECOND POST Reference links posted at bottom are sourced as I dig up more details that may be useful . It looks like the power will have to be supplied via gpio as far as I can tell.. The official documentation and fccid technical orders refer to the Headless SBC / Module what have you; as an "IQ Appliance". Tagged 'grep' for control/command function searching through fccid or other official documentation) Otherwise found simply as AM40 rk3399 or AM40 iq on google/other engines --AM40 iQ - Anyone seen or attempted armbian on something similar?-- Figured this forum may be one of the few places that might appreciate and see what I first saw. So if anyone might have an idea where to proceed with a possible hidden gem like this.. I picked it up for reasonable price a quite a bit LESS than current nanopi m4 cost the other night. Can't say quite yet if it will be a useless paperweight, or a diamond in the rockchip. heh. As soon as it arrives I intend on seeing what kind of hac.. err educational research can be done to place Armbian on it eventually over its intended OS. There seems to be a service switch that is used on other models to allow intel modules and windows OS. The form factor seems to be carrier board size, so here's hoping for that switch to be more open to source than intended for this particular model. It's just something about the specs on it raised an eyebrow, yea? And the case it comes with is pretty solid compared to the shit, err, other case and fan combos you normally see.. That alone.. I didn't see any tear-down from the ffcid schematics available to the public, possibly because it sold as an education exclusive device to school system. If anyone here shows interest, I'd be glad to do a tear-down (bubba do like destroy) and share it with the RK3399 community. -Follow up- Regarding cost. I paid somewhere under $50. If anyone else considers it, I suggest you be firm with the seller, and make an offer that is well under what they're going to be asking. Reason to be a cheapskate on these things? Well.. 1. Likely these were paid for by government tax funds for schools. Or written off as a privately owned business cost anyhow, which means someone like us already helped pay for them.. In the form of tax or tax return budget allotted to business owners. 2. Considering I'm not even sure if its possible to power on so simply without gpio testing or a breakout wizard beard 3. Cause we can build this things ourselves already for under $100 easily. So yea don't pay something more than that, even brand new for sure! Open Power Specification and 2 pins in the back is all I see so far. Ebay: https://www.ebay.com/itm/SMART-Model-AM40-Part-Number-1029788-Rev-07-No-Antennae-Very-Good-Condition/174156468137?hash=item288c88cfa9:g:DvwAAOSwCRVdcQyW https://www.ebay.com/itm/NEW-SMART-iQ-Appliance-AM40-Education-Digital-Signage-Player-Rockchip-RK3399/173853101572?hash=item287a73ce04:g:AccAAOSwaAlccc2l Manufacturer Reference: https://support.smarttech.com/docs/software/iq/en/about/specifications/am40.cshtml https://support.smarttech.com/docs/software/iq/en/about/iq-appliance-connectors.cshtml FCCID Technical Orders: doesn't seem to have its own nomenclature listing however, it is referenced in great detail its carrier device (an over priced touch screen) sourced for IMPORTANT notes before any reversing or mod attempt at introducing hardware compatible touch screen, PSU, OPS (serial) etc user manual control/command function search 'grep AM40' FCC ID QCIIDS665P1 QCI-IDS665P1, QCI IDS665P1, QCIIDS665P1, QCIIDS665PI, QCI1DS665P1, QCIID5665P1, QCIIDS66SP1, QC11DS665P1, OCIIDS665P1, 0CIIDS665P1 SMART Technologies Inc. SMART Board 6000S and 6000S Pro Series Interactive Displays IDS665P1 SMART LCD Monitor SBID-6065S, IDS665-1 Smartboard Interactive Display 6000S / Pro SBID-6265S, SBID-6275S, SBID-6265S-PW, SBID-6275S-PW https://fccid.io/QCIIDS675P1 https://fccid.io/QCIIDS675P1/Users-Manual/User-Manual-4554712 FCC ID QCI7086 QCI-7086, QCI 7086, QCI7086, QCI7O86, QC17086, OCI7086, 0CI7086 SMART Technologies Inc. Interactive Display 7086 https://fccid.io/QCI7086 https://fccid.io/QCI7086/User-Manual/Users-Manual-3626573 https://fccid.io/QCI7086/Internal-Photos/Internal-Photos-3626563 user manual control/command function search 'grep iQ appliance' FCC ID QCI7000 QCI-7000, QCI 7000, QCI7000, QCI7OOO, QC17000, OCI7000, 0CI7000 SMART Technologies Inc. Interactive Display 7000 https://fccid.io/QCI7000 https://fccid.io/QCI7000/Users-Manual/user-manual-3417295 https://fccid.io/QCI7086/Internal-Photos/Internal-Photos-3417295 OPS: Open Plug-gable Specification Serial (40 pin) Seria(40 pin) = OPS (80 pin *note, not sure exactly if this is the way to go, but closest I could find for now to adapt the OPS interface manufacturers "support" forum search regarding ops https://community.smarttech.com/s/global-search/OPS?language=en_US A Challenger Appears https://hackaday.io/project/20193-open-pluggable-specification-breakout-board https://www.digikey.com.au/products/en/connectors-interconnects/rectangular-board-to-board-connectors-arrays-edge-type-mezzanine/308?k=tx24&k=&pkeyword=tx24&s=54162&pv1989=0&FV=ffe00134&mnonly=0&newproducts=0&ColumnSort=0&page=1&quantity=0&ptm=0&fid=0&pageSize=25 OPS: Open Plug-gable Specification potentially an inconvenient convenience. (hdmi,usb,rj45 and etc..) to make the platform a module. imagine your favorite usb to serial, or whatever favorite debugging i/o. Now, chop off the USB part, and replace it with this. heres hoping those 2 pins are simple logic level voltage and ground Service Switch: Possibly switches between EMMC and SD Boot? May be interesting TLDR; possibly epic fail or epic win used condition: metal case / fan / rk3399 / 4GBDDR3 / 32GB EMMC vs NanoPi M4 Metal Case w/ Cooling Fan $30 to $45 Metal Case with Cooling Fan and RK3399/4GBDDR3/32GB eMMC $35 to $100

Hi guys, which is the Armbian recommended way to jump to a newer Userspace version? A fresh install ? A regular system upgrade ? Thanks in advance, 🙏 F.

On X86 and AMD64 systems they all have either the UEFI bios or the old bios. I don't know what the Raspberry Pi uses but I don't think it's UEFI. Do any of the ARM systems use UEFI? How does Armbian boot on the non-UEFI systems?

Hi, i've a tablet that has an Allwinner A20 socs. Can i install armbian? Which are installation steps? Thank You Luigi

I have a development board, model eaidk-310, with soc rk3228h (which is said to be the same as rk3328). The official website of the board has been closed, so I cannot obtain more related information. However, I found the official firmware and can use rockchip's official tool for burning. The file structure is as follows. 190798 Jun 8 2020 MiniLoaderAll.bin 33554432 Jun 8 2020 boot_linux.img 374 Jun 8 2020 parameter-linux.txt 6815744000 Jun 8 2020 rootfs.img 4194304 Jun 8 2020 trust.img 4194304 Jun 8 2020 uboot.img parameter-linux.txt is: FIRMWARE_VER:8.1 MACHINE_MODEL:RK3328 MACHINE_ID:007 MANUFACTURER:Rockchip MAGIC: 0x5041524B ATAG: 0x00200800 MACHINE: 3328 CHECK_MASK: 0x80 PWR_HLD: 0,0,A,0,1 TYPE: GPT CMDLINE:mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(trust),0x00010000@0x00006000(boot_linux:bootable),-@0x00016000(rootfs:grow) uuid:rootfs=614e0000-0000-4b53-8000-1d28000054a9 I tried to install armbian's image based on rk3328, which is officially supported. Some of them can boot up but neither network nor Bluetooth works properly. Therefore, I want to compile my own version to support these peripherals. My question is whether I can use the pre-compiled .img files in these official images to compile my own armbian? If possible, how should I configure ./compile.sh? Thank you all. Translated from:

Hi all, I try to use SPI on the BananaPi M2 Berry. The devices are activated in the configfile and the devices spidev0,0 and spidev1.0 are shown in the /dev .directory but the spi-bus did not work. DMESG shows the following error - messages : [ 0.944871] sun6i-spi 1c05000.spi: Failed to request TX DMA channel [ 0.944893] sun6i-spi 1c05000.spi: Failed to request RX DMA channel [ 0.945987] sun6i-spi 1c06000.spi: Failed to request TX DMA channel [ 0.946006] sun6i-spi 1c06000.spi: Failed to request RX DMA channel OS version is 6.2.12-sunxi Any idea what's wrong ?

I'd like to run usbdux usb hardware with armbian but have no experience so far in building modules. I compiled the current armbian branch form github. But I could not figure out how to compile the comedi drivers and include it in the kernel. help appreciated Thomas

Hello everyone, Would like to ask for some guidance regarding how to install armbian on a t507 processor. as written here in this post allwinner 507 processor it says For this reason I have tried to burn an image for orangepi zero 2 but it doesn't boot, it just get frozen and I can't get any logs because the serial console do not prints anything all black. Does someone could maybe have some suggestion of what I could try? anything is more than welcome. Thank you in advance