Jump to content

Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates

  1. Past hour
  2. You can use the raspberrypi iso burner software to write to an SD card or thumb drive etc.... there are a number of image burning/writing softwares. for different OS's What OS are you using and or have you solved your problem yet?
  3. sgjava

    Odroid C1

    OK, I got it to build. The secret is REPOSITORY_INSTALL= REPOSITORY_INSTALL (comma-separated list): list of core packages which will be installed from repository Available options: u-boot, kernel, bsp, armbian-bsp-cli,armbian-bsp-desktop,armbian-desktop,armbian-config, armbian-firmware Set to “” to use packages one from local output or build if not available I'll do it from scratch and post final instructions.
  4. Today
  5. I have recently managed to get SPI boot to USB SSD working on my Odroid N2+. However, to get there, I had to manually set setenv rootdev "/dev/sda1" in my /boot/boot.cmd With that set, SPI boot works. However, obviously I should not set it manually there, and the setting gets overwritten by armbian-config. My understanding is, that I should let boot.cmd unchanged (rootdev "/dev/mmcblk0p1") and armbianEnv.txt should do its magic, but the rootdev setting in armbianEnv.txt is simply ignored upon SPI boot and it fails to boot, as it tries to load the root fs from SD card... Any pointers, what might go wrong here or how to persist the boot.cmd change?
  6. From second driver very similar error: root@orangepione:~/build/rtl8821CU# make make ARCH=arm CROSS_COMPILE= -C /lib/modules/5.15.80-sunxi/build M=/root/build/rtl8821CU modules make[1]: Entering directory '/usr/src/linux-headers-5.15.80-sunxi' ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it. make[1]: *** [Makefile:749: include/config/auto.conf] Error 1 make[1]: Leaving directory '/usr/src/linux-headers-5.15.80-sunxi' make: *** [Makefile:2217: modules] Error 2
  7. Yesterday
  8. Description update renegade device tree patches How Has This Been Tested? build passes Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
  9. My board is an Helios4 rev 1.1. If only early revisions of the board are affected, that could explain why not everybody is experiencing this issue.
  10. Hello everyone! After my Helios4 had been laying in a cardboard box for a long time after moving houses, I decided it was time to once again set it up as an NAS. I was previously running Open Media Vault (OMV) with 4 disks in xfs and using MergerFS for unionizing three of them at a single mount point and then using Snapraid for the fourth disk. OMV worked pretty well for me but I go somewhat irritated from time to times because how it decides to thing in it's own way. But now I when I re-installed it (after getting a new PSU) I went with Armbian instead to keep it closer to "standard" linux. I think I will still go with MerverFS and Snapraid this time also but I also wonder what you guys and gals are using! For example: - What filesystem are you using? xfs, btrfs or maybe zfs? - Are you running raid, mergerfs or something else? - How are making the storage avalible to other hosts? NFS, SSHFS? - Are you running some kind of admin UI to manage your Helios?
  11. Ok I just spend hours poring over the CAD drawings. I have discovered the source of my measurements error and have now corrected it. All effected cad files have been updated with corrections. I thought I was having lost steps on my cnc machine when I made the steel heatsink brackets. It would not surprised me considering my cnc machine is not made to cut steel. When I cut the first attempt of the back plane for mounting the OPI5 the holes didn't match up at all. Oh sh!t we have a problem. I have had no comments to me with issues which leads me to believe no one has built (fully) the design yet including me.
  12. @Artem Komissarov Thank you for your reply, Artem. I did try to run armbian-config several times with ext4 and all other available install options but it stalled after the initial booting with the u-boot logo and before the armbian ubuntu logo appeared. During the installation phase, it did not recognize the eMMC nor any mmcblk2 partition, but only the mmcblk1 partition where armbian-ubuntu was installed from the sd card which I flashed it to. Although I surely must have missed some basic command somewhere during installation, it nonetheless seems that with the factory pre-installed manjaro on Pinebook Pro any attempt at installing another OS might make the eMMC unreacheable. No resetting of the PBP will have any effect, leaving booting from the sd card as the only choice. Any further hint or advice on how to solve this issue would be very much appreciated.
  13. Description USB3 has been enabled in mainline since 2021 View the full article
  14. Since you are posting in the TV Box sub-forum, I'm assuming you are talking about a TV Box. But you have't provided any informaion about your setup. What TV Box do you have, what version of Armbian do you have (by version I mean the name of the image you downloaded, and where downloaded from).
  15. i am use MXQ Pro+ 4K 2/16G s905x, i am facing reset button not function too already try 1 week 😭 ..... just boot up the system, the new version armbian no aml_autoscript.zip, try use adb tool i sort the emmc 5 & 6 pin then plug the usb cable success for connect and flash to stock rom then PC install adb tool adb connect 192.168.x.x (TV Box IP address) adb reboot update <==this command can boot up the usb
  16. Hi, i just received my Rock 4 Se and a 32GB eMMC module today, and i'm currently not sure if the Image is incompatible, or if my storage modules are broken. I tried emmc standalone and SD for boot with nvme (from an dell notebook) for rootfs When i use the emmc, the filesystem goes into read only as soon as i do some apt upgrade. On reboot i often end up in initramfs nd have to fsck. I could gether some dmesg output: After this trace i get a lot of I/O Errors: Im not sure if this is an os or an emmc module issue. Any guess whats going wrong here? after that i coppied the current image ( Armbian_22.11.1_Rockpi-4b_bullseye_current_5.15.80.img.xz) onto a micro SD card, addedthe nvme drive, bootet that and made an armbian-install to migrate the rootfs to the nvme. After a reboot, i could actually start to instlall software. But after a while i still had some freeze of the whole system, so i had to power the board off and turn it on again. Sadly i do not have any more output from this situation. i'm also going to try a version with older kernel, will reportlater if that worked
  17. I finally found an official source code on the download page of OrangePI that has a version of wiring pi with support for the Orange PI 5 - unfortunately that code is not on the github of orangepi yet. What would be the best way to get this code and the gpio tool into armbian? Build a PPA and package for that one? I don't mind forking their repo and adding the mods but I'm not familiar with generating debian packages.
  18. Do you guys know how reliable the chrome://gpu is? Mine says that hardware video decoding is enabled - I don't get the great 14% cpu usage that @royk gets but the machine plays 4k videos without any hickup with ~ 60% cpu which is imo already fast.
  19. In fact, most of the reports I have read speak of Samsung. However, Samsung is also the market leader. So I am cautious about blaming the issue on Samsung. This one speaks of Kingston. Anyway, the problem seems to be accumulating.
  20. Ver 20230128-EDK2-EFI for Quartz64-B Added EDK2-EFI support for Quartz64-B,
  21. Hi Guys, My Orange Pi Zero LTS H5 had a short circuit and no longer power up. worst that it seems that i cannot find any replacement for it as market is full of H2 & H3 variants but non is H5. Perhaps its time to upgrade Armbian & Hardware by inserting the SD card in one of the below boards: - Orange Pi Zero 2 1GB RAM with Allwinner H616 - Orange Pi R1 Plus LTS 1GB RAM RK3328 -Nanopi NEO3 Mini RK3328 (though not Orange pi but seems very similar) Though i'm not sure OS would boot on different CPU / board, (i remember doing such upgrade from h3 to 5h or zero 2 to lts) I would like to avoid re-building the OS with my programs and configurations. Would it be possible to make such upgrade? and what i will need to do in such case. Many thanks
  22. Adding more info here, would be glad if anyone more knowledgeable than me could point me in the right direction. I just updated to the latest Armbian 22.11.4 Bullseye with Linux 6.0.13-meson64 and enabled uartA and uartC overlays via armbian-config (and confirmed they are set in armbianEnv.txt). Still I don't get the uartA to show up, dmesg has only ff803000.serial: ttyAML0 at MMIO 0xff803000 (irq = 14, base_baud = 1500000) is a meson_uart which is uartC. Anything I might have missed or is this a bug? Is anyone around who could give me hint what to look for? I'm new to the topic, haven't used overlays before.. Maybe @martinayotte, I saw that you could help another user in an older thread for the Odroid C2 with a serial port issues, any ideas? Highly appreciate any help 🙂
  23. Hi SoSie, Thanks for your message, that is what I did in the end - I went back to: Armbian_22.08.7_Bananapim5_bullseye_edge_5.19.16_gnome_desktop.img and is booting into the desktop now, but I'm sure I still had those errors in dmesg 🤔 I thought it was due to a permissions problem, but didn't know where to look..
  24. Description These patches are are needed for panfork "go-faster". Using env PAN_MESA_DEBUG=gofaster we can get better glmark performance. Here are some infos from icecream95 copied on discord: "go-faster" patches for Mesa on RK3588 are almost ready, but need some kernel patches to get the full advantage: https://gitlab.com/panfork/rk3588-implicit-sync That repo has backports of a couple of patches from Linux v6.0, a fix to rockchip-drm, and also a patch to kbase fixing a bug that I hit accidentally… but could probably be used in an exploit. On that note, kbase vulnerabilities are found quite often: https://developer.arm.com/Arm Security Center/Mali GPU Driver Vulnerabilities … but don't expect patched versions to make their way to BSP kernels any time soon I tried using a newer kbase version with the Rockchip kernel… but with all of Rockchip's often broken changes, it's quite a hassle. I guess that is why the "patch gap" exists: https://googleprojectzero.blogspot.com/2022/11/mind-the-gap.html The kernel patches are important for performance as they allow applications to pipeline rendering without the windowing system needing to know about it (only Android has the necessary plumbing to work well without the patches) How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Build rock5b kernel with no error [x] test glmark2-es2-wayland with env PAN_MESA_DEBUG=gofaster Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
  25. After many tries I managed to make it work, I don't know how I did it but one of the steps was to uninstall ufw and use firewalld
  26. I was successful to boot uBoot over SPI-FLASH and continue to boot over network (PXE+NFS), and my few comments: uboot (orangepi) - https://github.com/orangepi-xunlong/u-boot-orangepi.git (v2021.10-sunxi) does not support SPI-FLASH boot upstream uboot hungs, but it has patch to support SPI boot (since v2023.01-rc1) - https://patchwork.ozlabs.org/project/uboot/list/?series=252044&state=* - https://github.com/u-boot/u-boot/commit/e50ee3a8d7328142eb24741305f751e5c0952380 so I extend 1. with 2. (attached) and rebuild uBoot flash uboot, in linux ` nandwrite /dev/mtd0 u-boot-sunxi-with-spl.bin ` (erase: ` flash_eraseall /dev/mtd0 `) install jumper between PC5 and GND (13-14 pinheader) ... and boot U-Boot SPL 2021.10-g0b91e222-dirty (Jan 09 2023 - 02:10:12 +0100) DRAM: 1024 MiB Trying to boot from sunxi SPI NOTICE: BL31: v2.8(debug):f4d8ed5 NOTICE: BL31: Built : 23:43:55, Jan 7 2023 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a087b80, model: OrangePi Zero2 INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: PMIC: Probing AXP305 on RSB INFO: PMIC: aldo1 voltage: 3.300V INFO: PMIC: aldo2 voltage: 3.300V INFO: PMIC: aldo3 voltage: 3.300V INFO: PMIC: bldo1 voltage: 1.800V INFO: PMIC: bldo2 voltage: 1.800V INFO: PMIC: dcdcd voltage: 1.500V INFO: PMIC: dcdce voltage: 3.300V 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 INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. U-Boot 2021.10-g0b91e222-dirty (Jan 09 2023 - 02:10:12 +0100) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: OrangePi Zero2 I2C: ready DRAM: 1 GiB MMC: mmc@4020000: 0 Loading Environment from SPIFlash... SF: Detected mx25l1606e with page size 256 Bytes, erase size 4 KiB, total 2 MiB OK In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: phy interface7 eth0: ethernet@5020000 Autoboot in 2 seconds, press <Space> to stop MMC: no card present ethernet@5020000 Waiting for PHY auto negotiation to complete.. done BOOTP broadcast 1 *** Unhandled DHCP Option in OFFER/ACK: 2 *** Unhandled DHCP Option in OFFER/ACK: 42 *** Unhandled DHCP Option in OFFER/ACK: 4 *** Unhandled DHCP Option in OFFER/ACK: 252 *** Unhandled DHCP Option in OFFER/ACK: 2 *** Unhandled DHCP Option in OFFER/ACK: 42 *** Unhandled DHCP Option in OFFER/ACK: 4 *** Unhandled DHCP Option in OFFER/ACK: 252 DHCP client bound to address 192.168.1.242 (45 ms) *** Warning: no boot file name; using 'C0A801F2.img' Using ethernet@5020000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.242 Filename 'C0A801F2.img'. Load address: 0x42000000 Loading: * TFTP error: 'Access violation' (2) Not retrying... missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-02-00-d2-c3-32-42 Using ethernet@5020000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.242 Filename 'pxelinux.cfg/01-02-00-d2-c3-32-42'. Load address: 0x4fd00000 Loading: * TFTP error: 'Access violation' (2) Not retrying... missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A801F2 Using ethernet@5020000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.242 Filename 'pxelinux.cfg/C0A801F2'. Load address: 0x4fd00000 Loading: # 11.7 KiB/s done Bytes transferred = 126 (7e hex) Config file found 1: linux missing environment variable: bootfile Retrieving file: uInitrd Using ethernet@5020000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.242 Filename 'uInitrd'. Load address: 0x4ff00000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ######################### 9.2 MiB/s done Bytes transferred = 15625901 (ee6ead hex) missing environment variable: bootfile Retrieving file: Image Using ethernet@5020000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.242 Filename 'Image'. Load address: 0x40080000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ###################### 9.8 MiB/s done Bytes transferred = 22259720 (153a808 hex) append: root=/dev/nfs nfsroot=192.168.1.1:/sunxi/ ip=dhcp rw missing environment variable: bootfile Retrieving file: dtb/allwinner/sun50i-h616-orangepi-zero2.dtb Using ethernet@5020000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.242 Filename 'dtb/allwinner/sun50i-h616-orangepi-zero2.dtb'. Load address: 0x4fa00000 Loading: ### 706.1 KiB/s done Bytes transferred = 38323 (95b3 hex) Moving Image from 0x40080000 to 0x40200000, end=417a0000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15625837 Bytes = 14.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 49119000, end 49fffe6d ... OK Loading Device Tree to 000000004910c000, end 00000000491185b2 ... OK Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 5.16.17-sun50iw9 (martin@martin-v15) (aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 9.2.1 20191025, GNU ld (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 2.33.1.20191209) #3 SMP Wed Jan 11 14:07:16 CET 2023 [ 0.000000] Machine model: OrangePi Zero2 [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x000000007fffffff] [ 0.000000] NUMA: NODE_DATA [mem 0x7fdca040-0x7fdcbfff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000040000000-0x000000007fffffff] [ 0.000000] DMA32 empty [ 0.000000] Normal empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000040000000-0x000000004007ffff] [ 0.000000] node 0: [mem 0x0000000040080000-0x000000007fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000007fffffff] [ 0.000000] cma: Reserved 128 MiB at 0x0000000076c00000 [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs spiboot.patch
  27. Thanks. I cannot find your work under H616 and Allwinner is too generic. Can you navigate me to the right patch (maybe WIP repo outside patch queue) ? h616 patchwork allwinner patchwork
  1. Load more activity
×
×
  • Create New...