Jump to content

Search the Community

Showing results for tags 'orangepizeroplus'.

  • 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

Categories

  • Volunteering opportunities
  • Part time jobs

Categories

  • Official giveaways
  • Community giveaways
  • Raffles

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

Found 6 results

  1. My Armbian paste is at https://paste.armbian.com/yamakinoce This is an OrangePi Zero Plus, with an H3, not an H5 or an H2. I see all kinds of problems here but don't know how to fix them. It seems the DTB is just wrong for this board. For one, there are interrupts showing up in /proc/interrupts for HDMI and LCD, but this physical board has *neither* of those. It has an Ethernet PHY but neither the kernel nor uboot see it. It also has a Wifi but the kernel does not see that either. Does a correct DTB exist for this board? What is its name? I vaguely remember a couple ways to force the kernel and uboot to use a different DTB than what it calculates, but I would need to know if such a DTB exists in the first place. Thanks!
  2. Is it a way to reduce the amount of reserved memory on sunxi64 devices? Trying to remove all useless for my case features (video/audio/wireless) to free up memory/resources for other tasks. The amount of total (413M) vs real (512M) memory is quite low: # grep -e Mem -e Cma /proc/meminfo MemTotal: 422416 kB MemFree: 49620 kB MemAvailable: 314396 kB CmaTotal: 0 kB CmaFree: 0 kB # dmesg | grep Memory: [ 0.000000] Memory: 407924K/524288K available (14144K kernel code, 1456K rwdata, 8700K rodata, 3072K init, 521K bss, 116364K reserved, 0K cma-reserved) # grep extraargs /boot/armbianEnv.txt extraargs=cma=0 sunxi_no_mali_mem_reserve sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 # uname -a Linux pi160 6.6.65-current-sunxi64 #1 SMP Wed Dec 11 19:13:43 +04 2024 aarch64 GNU/Linux The tricks which works for `sunxi` (e.g. `orangepizero`) does not work for `sunxi64` boards: https://linux-sunxi.org/Kernel_arguments Attempt to specify that extraargs in /boot/armbianEnv.txt have no effect (also their defaults are absent in /boot/boot.cmd, while present in orangepizero's version), except for `cma=0` with is not directly related to total available memory. Custom kernel with `CONFIG_CMA=n` also changes nothing.
  3. I had to freeze my device on Kernel 6.1.92 & Bullseye to remain operational. Now trying to update/upgrade to Kernel 6.6.nn I run into following probs: 1) Using Armbian-config defreeze and subsequently switch to kernel 6.6.nn works OK 4me, but subsequent apt-get update/upgrade throws me back to kernel 6.1.104. Armbian-config has changed significantly w/ No other Kernel available. 2) Using Armbian-config defreeze, only and going directly to apt-get update/upgrade throws me back to kernel 6.1.104 as well and from Bullseye back to Buster! Its a mess! Will this eventually be corrected and when? RGDS
  4. 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
  5. 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 ! => %
  6. Hello, Like it happened to @Grogorio in 2016, I need to introduce a boot delay on my OrangePi Zero Plus (Armbian 23.02.2 Focal) to allow time for other network elements in my setup to boot. As per what I have read somewhere, this can done by adding a 'boot_delay=n' line in /boot/config.txt, however I don't see this file in Armbian; I've also tried to add the line, but it does not seems to be working. Furthermore, the max delay that can be setup there is 10 seconds, but I need a longer delay. Can someone help? TIA
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines