Jump to content

Search the Community

Showing results for tags 'orangepizero'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. Hello .. I have tested both current release 24.2.1 (jammy and bookworm) on OPiZero, and usb otg not working .. on both .. Kernel is 6.6.20-current-sunxi module g_serial is loaded ttyGS0 exist serial-getty@ttyGS0.service is runing dtc overlays are usbhost0 - 3 ..all looks good on opizero side ... but on "computer side" not.. nothing happened when usb cable is plugged in .. no ttyAMC0 device was created .. no new usb hardware can be found in system log ... ..nothing.. Buster version works well... (my old installation) any advice ..? or it is any "actual kernel problem" .. ?? have somebody the same problem .. ??
  2. Hi I have installed the latest image for Orange Pi Zero v1 https://dl.armbian.com/orangepizero/archive/Armbian_24.2.1_Orangepizero_bookworm_current_6.6.20.img.xz link from https://www.armbian.com/orange-pi-zero/ After the first boot, I see that it is kernel 6.6.20 Welcome to Armbian 24.2.1 Bookworm with Linux 6.6.20-current-sunxi Linux version 6.6.20-current-sunxi (armbian@next) (arm-linux-gnueabihf-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Sat Mar 2 17:23:09 UTC 2024 and when I run apt update& apt upgrade apt list --upgradable Listing... Done armbian-firmware/bookworm,bookworm 24.2.1 all [upgradable from: 24.2.1] linux-image-current-sunxi/bookworm 24.2.1 armhf [upgradable from: 24.2.1] and when running apt upgrade apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: armbian-firmware linux-image-current-sunxi 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 111 MB of archives. After this operation, 42.3 MB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://fi.mirror.armbian.de/apt bookworm/main armhf armbian-firmware all 24.2.1 [75.2 MB] Get:2 http://fi.mirror.armbian.de/apt bookworm/main armhf linux-image-current-sunxi armhf 24.2.1 [35.7 MB] Fetched 111 MB in 1min 6s (1,678 kB/s) (Reading database ... 41412 files and directories currently installed.) Preparing to unpack .../armbian-firmware_24.2.1_all.deb ... Unpacking armbian-firmware (24.2.1) over (24.2.1) ... Preparing to unpack .../linux-image-current-sunxi_24.2.1_armhf.deb ... Armbian 'linux-image-current-sunxi' for '6.6.20-current-sunxi': 'prerm' starting. Armbian 'linux-image-current-sunxi' for '6.6.20-current-sunxi': 'prerm' finishing. Armbian 'linux-image-current-sunxi' for '6.6.16-current-sunxi': 'preinst' starting. Armbian 'linux-image-current-sunxi' for '6.6.16-current-sunxi': 'preinst' finishing. Unpacking linux-image-current-sunxi (24.2.1) over (24.2.1) ... Armbian 'linux-image-current-sunxi' for '6.6.20-current-sunxi': 'postrm' starting. Armbian 'linux-image-current-sunxi' for '6.6.20-current-sunxi': 'postrm' finishing. Setting up linux-image-current-sunxi (24.2.1) ... Armbian 'linux-image-current-sunxi' for '6.6.16-current-sunxi': 'postinst' starting. dkms: autoinstall for kernel 6.6.16-current-sunxi was skipped since the kernel headers for this kernel do not seem to be installed. update-initramfs: Generating /boot/initrd.img-6.6.16-current-sunxi update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.16-current-sunxi Image Name: uInitrd Created: Tue Mar 12 07:11:59 2024 Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 17410594 Bytes = 17002.53 KiB = 16.60 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.16-current-sunxi to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.6.16-current-sunxi' update-initramfs: Armbian: done. Remove unused generated file: /boot/uInitrd-6.6.20-current-sunxi Remove unused generated file: /boot/initrd.img-6.6.20-current-sunxi Armbian: update last-installed kernel symlink to 'zImage'... '/boot/zImage' -> 'vmlinuz-6.6.16-current-sunxi' Armbian: Debian compat: linux-update-symlinks install 6.6.16-current-sunxi boot/vmlinuz-6.6.16-current-sunxi I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.6.16-current-sunxi I: /initrd.img.old is now a symlink to boot/initrd.img-6.6.16-current-sunxi I: /vmlinuz is now a symlink to boot/vmlinuz-6.6.16-current-sunxi I: /initrd.img is now a symlink to boot/initrd.img-6.6.16-current-sunxi Armbian 'linux-image-current-sunxi' for '6.6.16-current-sunxi': 'postinst' finishing. Setting up armbian-firmware (24.2.1) ... After reboot it seems kernel 6.6.20 was replaced by 6.6.16 Welcome to Armbian 24.2.1 Bookworm with Linux 6.6.16-current-sunxi Linux version 6.6.16-current-sunxi (armbian@next) (arm-linux-gnueabihf-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Fri Feb 23 08:25:28 UTC 2024 Is that correct?
  3. Hi guys, I downloaded Armbian 24.2.1 Jammy CLI (Armbian_24.2.1_Orangepizeroplus_jammy_current_6.6.16.img.xz) for the Orange Pi Zero Plus and it's not booting. Boot log below: U-Boot SPL 2024.01-armbian (Feb 09 2024 - 19:21:37 +0000) DRAM: 512 MiB Trying to boot from MMC1 NOTICE: BL31: v2.9(debug):armbian NOTICE: BL31: Built : 19:20:27, Feb 9 2024 NOTICE: BL31: Detected Allwinner H5 SoC (1718) NOTICE: BL31: Found U-Boot DTB at 0x20a4ef0, model: Xunlong Orange Pi Zero Plus INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller NOTICE: PMIC: Assuming H5 reference regulator design INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: cortex_a53: CPU workaround for 1530924 was applied SCP/INF: Crust v0.6.10000 INFO: PSCI: Suspend is available via SCPI INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2024.01-armbian (Feb 09 2024 - 19:21:37 +0000) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: Xunlong Orange Pi Zero Plus DRAM: 512 MiB Core: 67 devices, 20 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 1 Loading Environment from FAT... MMC: no card present ** Bad device specification mmc 0 ** In: serial,usbkbd Out: serial,vidconsole Err: serial,vidconsole Net: eth0: ethernet@1c30000 MMC: no card present ** Bad device specification mmc 0 ** Couldn't find partition mmc 0 MMC: no card present ** Bad device specification mmc 0 ** Couldn't find partition mmc 0 starting USB... Bus usb@1c1a000: sun4i_usb_phy phy@1c19400: External vbus detected, not enabling our own vbus USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop MMC: no card present Device 0: unknown device ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-01-a6-4a-c9-69 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/00000000 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/0000000 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/000000 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/00000 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/0000 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/000 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/00 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/0 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/default-arm-sunxi ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/default-arm ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/default ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Config file not found ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! => %
  4. I have followed this guide and I can boot my Orange Pi Zero from SSD without the need for an SD card inserted. I want to keep a bootable backup for my system in case the SSD gets corrupted. I was thinking to clone my system in a USB stick (just like I did to clone from SD to SSD) and then use rsync once a week to keep everything up to date with a script like that. If I go in armbian-config > system > install I can see only one option: "Install/Update the bootloader on SD/eMMC". How could I clone from SSD to a USB stick? Is there a command like `sudo nand-sata-install`?
  5. Hey everyone, I am attempting to update my Orange Pi Zero from Armbian 22.0.2.1 to the latest 23.11 version however I am running into the issue that I am stuck on how to perform this update, I have tried it using the sudo apt dist-upgrade command and tried regular sudo apt update and upgrade commands but everytime it says there are no new updates available (also no errors), when there is clearly a new version 23.11 available here: https://www.armbian.com/orange-pi-zero/ What am I doing wrong? Is it maybe because it says unsupported userspace?
  6. Hello. For some reason, UART1 does not work for transmission, only for reception. The transmitter pin itself is definitely working, I checked by switching this pin to output mode, and then switching it to a high/low logical level, everything works properly, the level on the Pin changes. How I check the UART itself: I installed picocom, shorted the TX and RX pins, and I’m trying to see what I’m sending. For UART2 this method works as it should, but UART1 only works for reception. I realized this when I opened the TX and RX, and was able to receive incoming data sent through the USB-UART converter.
  7. We are trying to compile a modified kernel module for this version of Armbian downloaded in October When running it reports: $cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=orangepizero BOARD_NAME="Orange Pi Zero" BOARDFAMILY=sun8i BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=ba704f4740 LINUXFAMILY=sunxi ARCH=arm IMAGE_TYPE=stable BOARD_TYPE=csc INITRD_ARCH=arm KERNEL_IMAGE_TYPE=zImage FORCE_BOOTSCRIPT_UPDATE= VENDOR=Armbian BOOTSCRIPT_FORCE_UPDATE="no" BOOTSCRIPT_DST="boot.cmd" VERSION=23.8.3 REVISION=23.8.3 BRANCH=current uname -a Linux orangepizero 6.1.53-current-sunxi #3 SMP Wed Sep 13 07:43:05 UTC 2023 armv7l GNU/Linux cat /boot/config-6.1.53-current-sunxi | grep -i MODULE_FORCE # CONFIG_MODULE_FORCE_LOAD is not set We assume that if CONFIG_MODULE_FORCE_LOAD is not set that modprobe --force will not work and we will have to compile with the exact headers. Note that we've also tried compiling on the target but : sudo apt-get install linux-headers-$(uname -r) Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package linux-headers-6.1.53-current-sunxi E: Couldn't find any package by glob 'linux-headers-6.1.53-current-sunxi' E: Couldn't find any package by regex 'linux-headers-6.1.53-current-sunxi' For cross-compiling, what branch/tag do we checkout from https://github.com/armbian/build that will result in the correct headers? Alternately how do we modify the .ko from a near-similar build to overcome CONFIG_MODULE_FORCE_LOAD not set? Thank you in advance!
  8. I’m trying to use a 3.5 LCD (waveshare clone) with ILI9486 + XPT2046 with my orange pi zero. My display is like this. I installed both Debian_buster_next_4.19.59 and Ubuntu_bionic_next_4.19.57 and I followed many guides in here with no success. I edited armbianEnv.txt and added these: overlays=spi-spidev spi-add-cs1 param_spidev_spi_bus=1 param_spidev_spi_cs=1 After that I ran this sudo modprobe fbtft_device custom name=fb_ili9486 gpios=dc:18,reset:2 speed=16000000 busnum=1 rotate=90 and didn’t get any error. I figured that the reset & DC pins on orange pi zero are pin22(GPIO2) and pin18(GPIO18) but I’m not 100% sure about these. With dmesg I see these: [ 179.174013] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 179.181645] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [ 179.183696] spidev spi1.1: spidev spi1.1 1000kHz 8 bits mode=0x00 [ 179.184295] fbtft_device: GPIOS used by 'fb_ili9486': [ 179.184307] fbtft_device: 'dc' = GPIO18 [ 179.184314] fbtft_device: 'reset' = GPIO2 [ 179.184331] spidev spi1.1: spidev spi1.1 1000kHz 8 bits mode=0x00 [ 179.184347] spi spi1.0: fb_ili9486 spi1.0 16000kHz 8 bits mode=0x00 [ 179.202576] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned. [ 179.749873] Console: switching to colour frame buffer device 60x40 [ 179.751385] graphics fb0: fb_ili9486 frame buffer, 480x320, 300 KiB video memory, 4 KiB buffer memory, fps=20, spi1.0 at 16 MHz I tried con2fbmap 1 0 but the screen remains white What else could I try? How could I debug the issue?
  9. Hi everyone, Very green here. Basically I setup 1 of my orange pi a few months back with "Armbian_23.02.3_Orangepizero2_jammy_legacy_4.9.318". I recently bought another pi and wanted to set it up with a newer version. I see bookworm is now the latest. I have tried both CLI and Minimal but whenever I flash those into my micro SD the orange pi never boots up. My router doesnt see the connection, so it cant hand off an IP. I thought maybe it was a bad mini SD or a bad pi. But when I flashed the old jammy image into the same SD, the pi immediately picked up the connection, my router gave it an IP and I was able to log in as a root to the pi. I read the documentation, and even saw the beginner videos to see that I wasnt doing something wrong. I had the SD connected before I powered on the PI, ensured I was the usb c for power. And that the SD has enough memory (8gb). Does anyone have an idea of what could be happening here with the bookworm armbian?
  10. after installing wireguard (kernel upgrade + headers) the pi would no longer boot and fail with crc error. Looking at the boot partition the uinitrd file was linked to the old version. Changed the uinitrd link to the newest one and it booted again.
  11. The topic is no longer new, but I have not found the reason and its solution! If you turn off the power (just pull out the wire) then you can get a non-working system. As I noticed, the files opened at the time of launch are broken. And some files such as /etc/boot/armbianEnv.txt in general, they are recorded with some kind of garbage!!! Because of this, your settings fly off! For example, I use ttys1 and this option is registered armbianEnv.txt , but after the power loss, there is just terrible garbage in this file, as if the memory dump fell there!!! For example, I still use dotnet, so it also breaks down and does not start anymore!! When you try to run dotnet from the command line, you get a bus error! Of course, deleting and reinstalling it solves the problem. You may also get problems with apt! I certainly expected this from windows. But for linux to be somewhat unreliable is a tin and a disappointment!! Why does this happen and how to treat it??? Now I have made a sh script to check the integrity of files and restore them. But these are crutches and a shame for linux!!! Maybe arabian is crooked and unreliable? or is it a disease of all systems??? I must say right away that the SD card is normal! This has been tested on 10 minicomputers. It's the same problem everywhere!
  12. Hi all, I need to add some packages to Armbian in the build phase. I tried two ways, both failed: 1. Had run through docs (https://docs.armbian.com/Developer-Guide_User-Configurations/), and the suggestion is to add a var PACKAGE_LIST_ADDITIONAL in userpatches/lib.config PACKAGE_LIST_ADDITIONAL="$PACKAGE_LIST_ADDITIONAL watchdog modemmanager iptables iptables-persistent dnsmasq bridge-utils iproute2 openvpn" Building the image I get the following error: [🌱] Using user configuration override [ /home/andrea/armbian/build/userpatches/lib.config ] /home/andrea/armbian/build/userpatches/lib.config: line 1: PACKAGE_LIST_ADDITIONAL: readonly variable [💥] Exiting with error 1 [ at /home/andrea/armbian/build/userpatches/lib.config:1 source() --> userpatches/lib.config:1 do_extra_configuration() --> lib/functions/configuration/main-config.sh:352 do_with_logging() --> lib/functions/logging/section-logging.sh:81 do_with_conditional_logging() --> lib/functions/logging/section-logging.sh:111 prep_conf_main_build_single() --> lib/functions/main/config-prepare.sh:34 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:22 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176 main() --> compile.sh:50 ] [💥] Cleaning up [ please wait for cleanups to finish ] 2. Customizing userpatches/customize-image.sh: Added the following lines to the aforementioned file: CUST_PACKAGES="watchdog modemmanager iptables iptables-persistent dnsmasq bridge-utils iproute2 openvpn" apt-get install -yy $CUST_PACKAGES |& tee -a $DEST/${LOG_SUBPATH}/custom.log The build completes, but packages aren't added as the logging prevents the build to fail. Anyway the following info messages are displayed during the build: [🔨] Reading package lists... [🔨] Building dependency tree... [🔨] Reading state information... [🔨] Package modemmanager is not available, but is referred to by another package. [🔨] This may mean that the package is missing, has been obsoleted, or [🔨] is only available from another source [🔨] [🔨] Package iptables is not available, but is referred to by another package. [🔨] This may mean that the package is missing, has been obsoleted, or [🔨] is only available from another source [🔨] However the following packages replace it: [🔨] libxtables12 [🔨] [🔨] E: Unable to locate package watchdog [🔨] E: Package 'modemmanager' has no installation candidate [🔨] E: Package 'iptables' has no installation candidate [🔨] E: Unable to locate package iptables-persistent [🔨] E: Unable to locate package dnsmasq [🔨] E: Unable to locate package openvpn Can you suggest a suitable way to add packages to the build? Thanks very much in advance, kind regards Andrea
  13. Hi, I use an OrangePi Zero as a race timer for a car. It is powered from the car. So when the car starts the OrangePi gets power and boots and when the car is turned off the OrangePi loses power and "turns off". This isn't ideal but I don't have a lot of options. I feel like this is a fairly common use case for electronics in cars especially ones like race timers etc. Unless I have a battery as well. I was wondering what are the best things to do to protect against the sudden power loss so that I don't corrupt anything? Is it possible to make parts of the file system read only maybe? All I do with the OrangePi is run a C++ application, it uses two serial ports and runs a server on port 80. The application does read and write its own configuration files and log files. But these are not OS files, only files that the application created itself. I have noticed that after writing or appending to a file from C++, if the power is pulled and then plugged back in the change to the file does not persist. I can ssh on before the power is pulled and `cat` the file and see that it is updated. Seems that the file data is held in RAM for a little while before actually writing. Is there anyway to force file writes to actually be flushed and written straight away?
  14. Hi all, I'm trying to put my orange pi zero to talk with a CAN BUS via mcp2515 chip. The chip is SPI controlled. The actual image does not have support for SocketCAN enabled, so I'm compiling the kernel with SocketCan following the kernel configuration shown here https://developer.ridgerun.com/wiki/index.php/How_to_configure_and_use_CAN_bus I'm using the cross-compiler tool from the armian website. After the image is burned to the sdcard and the orange pi zero is booted, I can see the image has can support enabled, but when I load the mcp251x driver it does nothing. I'm sure I'm missing some detail on spi side in order to have the mcp driver pointing to the proper spi. Any hints? Thanks in advance Amauri
  15. Hi, I have a board Orange Pi Zero with modified PAs for power of WiFi module from PA20 to PA02, by soldering a connection on board. This is done to allow connection of I2C DAC. I see that board definition in 'u-boot/configs/orangepi_zero_defconfig' It uses dts definition of: 'arch/arm/dts/sun8i-h2-plus-orangepi-zero.dts' I need to modify one section of this dts file from: reg_vcc_wifi: reg_vcc_wifi { compatible = "regulator-fixed"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-name = "vcc-wifi"; enable-active-high; gpio = <&pio 0 20 GPIO_ACTIVE_HIGH>; to: reg_vcc_wifi: reg_vcc_wifi { compatible = "regulator-fixed"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-name = "vcc-wifi"; enable-active-high; gpio = <&pio 0 2 GPIO_ACTIVE_HIGH>; How can I do this and use armbian build script: compile.sh Thanks, Michal
  16. Running the command below I have the issue below: I work with armbian-build git repo, tag 23.02.0-trunk.0256 and I run this command to build a armbian .img for my orangepi zero lts. It used to work well in february but now maybe the armbian repositories do not work anymore with this tag version ? ./armbian-build/compile.sh docker USE_MAINLINE_GOOGLE_MIRROR=yes BOARD=orangepizero BRANCH=current BUILD_KSRC=no RELEASE=bullseye BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_ONLY=no KERNEL_CONFIGURE=no ROOTFS_TYPE=ext4 BOOTFS_TYPE=fat COMPRESS_OUTPUTIMAGE=sha,img ' Processing triggers for resolvconf (1.87) ... [ o.k. ] Checking MD5 sum of installed packages [ debsums ] debsums: changed file /usr/share/doc/base-files/changelog.gz (from base-files package) debsums: changed file /etc/os-release (from base-files package) debsums: changed file /etc/issue.net (from base-files package) debsums: changed file /etc/issue (from base-files package) [ error ] ERROR in function create_rootfs_cache [ functions/cli/cli-entrypoint.sh:109 -> functions/main/build-tasks.sh:302 -> functions/main/build-tasks.sh:225 -> functions/main/rootfs-image.sh:66 -> functions/rootfs/create-cache.sh:229 -> functions/logging/traps.sh:0 ] [ error ] MD5 sums check of installed packages failed [ o.k. ] Process terminated [ error ] unmount_on_exit() called! [ functions/cli/cli-entrypoint.sh:109 -> functions/main/build-tasks.sh:302 -> functions/main/build-tasks.sh:225 -> functions/main/rootfs-image.sh:66 -> functions/rootfs/create-cache.sh:229 -> functions/logging/traps.sh:1 -> functions/main/rootfs-image.sh:0 ] [ o.k. ] Unmounting [ /root/armbian/.tmp/rootfs-329b560e-4e99-40c7-bad2-3ddabd8752c8/ ] [ error ] ERROR in function unmount_on_exit [ functions/cli/cli-entrypoint.sh:109 -> functions/main/build-tasks.sh:302 -> functions/main/build-tasks.sh:225 -> functions/main/rootfs-image.sh:66 -> functions/rootfs/create-cache.sh:229 -> functions/logging/traps.sh:1 -> functions/main/rootfs-image.sh:27 -> functions/logging/traps.sh:0 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated Thank you for your help
  17. First, I have installed latest Armbian 23.8 Bookworm CLI, boot works fine, I can login Then, I have installed wireguard. As a dependency, wireguard install linux-image-6.1.0-12-rt-armmp After reboot device is unavailable in network (orange LAN LED blinking while green does not, I assume ethternet broken with this kernel)
  18. Now that xradio has been enabled on kernel 6.x, I'm ready to upgrade my Orange Pi Zero that I've been keeping on 23.02 with kernel 5.x. With armbian-config I've unfrozen kernel/firmware updates and after apt upgrade and reboot I am on kernel 6.1.53 and wifi is working! But boot message says I'm still on 23.02, and apt says that armbian-bsp-cli-orangepizero is being kept back. Now trying: $ sudo apt install armbian-bsp-cli-orangepizero [...] Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: armbian-bsp-cli-orangepizero-current : Depends: base-files (>= 23.8.3) but 23.8.1-bullseye is to be installed E: Unable to correct problems, you have held broken packages. Do I just need to wait for something to be updated in the repositories so that armbian-bsp-cli-orangepizero will be made available, or have I messed up something on my system that I need to fix?
  19. Should it be possible to take a working SD card out of one OrangePi Zero and put it in a new one? Same board and amount of RAM and everything.
  20. Help me, my orangepizero wont work. Every time i try to start ssh it say connection refused. Only sometimes it works. I recently installed Armbian 22.5 bullseye and after that it stopped working. Pls help
  21. I am trying to figure out how to compile and load the Xradio drivers onto an orange pi zero LTS. I am having some troubles with the xradio drivers that came with my image and am hoping that https://github.com/fifteenhex/xradio will add some improvements. There does seem to be some code change so I am remaining optimistic. I am able to compile the drivers with the kernel from https://github.com/orangepi-xunlong/orangepi-build but it crashes network manager and a few other modules when I try to modprobe it, I am guessing it is because this kernel is not an armbian kernel. I am trying to get the kernel https://github.com/armbian/build to work, but it doesn't look like that's what I need to do. I am lost as to how to get this compiled and any help would be appreciated.
  22. I have orange pi zero board ..i searched a lot for changing boot splash screen ( currently "armbian universal operating system" which is enabled by adding bootlogo=true in armbianEnv.txt ) I have tried Plymouth it is not working After searching lot i knew about if we can replace bootsplash.armbian , it can help because then neither we need to change uboot packages nor we have to add quiet splash like words etc in armbianEnv.txt. https://github.com/armbian/build/tree/master/packages/blobs/splash. With help of this bootsplash-packer Can anyone list me some steps ( in short ) How to run this script and create bootsplash.armbian and replace it
  23. My OrangePi Zero is on 23.02 and I intend to stay with it (unless/until xradio wifi works on kernel 6.x). Just ran apt update and it shows these available packages: armbian-config/bullseye,bullseye 23.08.0-trunk--1-SA9048-Baeda all [upgradable from: 23.02.2] armbian-firmware/bullseye,bullseye 23.08.0-trunk--1-SA1251-B226d all [upgradable from: 23.02.2] armbian-zsh/bullseye,bullseye 23.08.0-trunk--1-SAbfee-Baf88 all [upgradable from: 23.02.2] I'm surprised to see anything related to 23.08 seeing as that version hasn't been released yet, so obviously I don't really understand what it means to be seeing this. Should I go ahead and install these even though I don't intend to upgrade to 23.08? Maybe this should be in the "beginners" area; mods please feel free to move if appropriate.
  24. Hello, I would like to know how they reduce the size of the images and then, when the microSD cards are inserted into a card, they expand to fill the entire space. In other words, the same thing that Armbian images do when we use them for the first time: they are small, and then they occupy all the storage space.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines