Magnets
-
Posts
54 -
Joined
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Magnets
-
-
I just updated my system and it failed to boot, see here:
I assume I have the same cause as you guys? What can I do to recover my install and get it booting?
-
I am running a old buster image and ran apt-get upgrade, now it won't boot.
Armbian 21.02.3 Buster with Linux 5.15.93-sunxi64
Get:8 http://netcup.armbian.com/apt buster/main arm64 linux-u-boot-orangepipc2-current arm64 25.2.3 [336 kB] ... Unpacking armbian-firmware (25.2.3) over (23.08.0-trunk--1-SA1251-B226d) ... dpkg: error processing archive /tmp/apt-dpkg-install-RjldFI/034-armbian-firmware_25.2.3_all.deb (--unpack): trying to overwrite '/lib/firmware/ath10k/QCA9377/hw1.0/board-2.bin', which is also in package firmware-atheros 20190114+really20220913-0+deb10u2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) ... Preparing to unpack .../089-linux-dtb-current-sunxi64_25.2.3_arm64.deb ... Armbian 'linux-dtb-current-sunxi64' for '6.6.75-current-sunxi64': 'preinst' starting. Armbian 'linux-dtb-current-sunxi64' for '6.6.75-current-sunxi64': 'preinst' finishing. Unpacking linux-dtb-current-sunxi64 (25.2.3) over (23.02.2) ... dpkg: warning: unable to delete old directory '/boot/dtb-5.15.93-sunxi64/allwinner': Directory not empty dpkg: warning: unable to delete old directory '/boot/dtb-5.15.93-sunxi64': Directory not empty Preparing to unpack .../090-linux-image-current-sunxi64_25.2.3_arm64.deb ... Armbian 'linux-image-current-sunxi64' for '6.6.75-current-sunxi64': 'preinst' starting. update-initramfs: Deleting /boot/initrd.img-5.15.93-sunxi64 Removing obsolete file uInitrd-5.15.93-sunxi64 Armbian 'linux-image-current-sunxi64' for '6.6.75-current-sunxi64': 'preinst' finishing. Unpacking linux-image-current-sunxi64 (25.2.3) over (23.02.2) ... Preparing to unpack .../091-linux-u-boot-orangepipc2-current_25.2.3_arm64.deb ... Unpacking linux-u-boot-orangepipc2-current (25.2.3) over (23.02.2) ... ... Errors were encountered while processing: /tmp/apt-dpkg-install-RjldFI/034-armbian-firmware_25.2.3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ... Preparing to unpack .../armbian-firmware_25.2.3_all.deb ... Unpacking armbian-firmware (25.2.3) over (23.08.0-trunk--1-SA1251-B226d) ... dpkg: error processing archive /var/cache/apt/archives/armbian-firmware_25.2.3_all.deb (--unpack): trying to overwrite '/lib/firmware/ath10k/QCA9377/hw1.0/board-2.bin', which is also in package firmware-atheros 20190114+really20220913-0+d eb10u2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/armbian-firmware_25.2.3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1)after rebooting
U-Boot SPL 2019.10-armbian (Feb 17 2020 - 08:45:21 +0100) DRAM: 1024 MiB Trying to boot from MMC1 NOTICE: BL31: v2.2(debug):572fcdd-dirty NOTICE: BL31: Built : 08:45:08, Feb 17 2020 NOTICE: BL31: Detected Allwinner H5 SoC (1718) NOTICE: BL31: Found U-Boot DTB at 0x40a1650, model: Xunlong Orange Pi PC 2 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: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2019.10-armbian (Feb 17 2020 - 08:45:21 +0100) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: Xunlong Orange Pi PC 2 DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial Out: serial Err: serial Allwinner mUSB OTG (Peripheral) Net: phy interface7 eth0: ethernet@1c30000 Warning: usb_ether using MAC address from ROM , eth1: usb_ether 230454 bytes read in 18 ms (12.2 MiB/s) starting USB... Bus usb@1c1a000: 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 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: 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 bus usb@1c1c000 for devices... 2 USB Device(s) found scanning bus usb@1c1c400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 2 USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found scanning usb for storage devices... 2 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3069 bytes read in 6 ms (499 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 165 bytes read in 2 ms (80.1 KiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Bad Linux ARM64 Image magic! SCRIPT FAILED: continuing... Device 0: Vendor: ACASIS Rev: 0508 Prod: Type: Hard Disk Capacity: 228936.5 MB = 223.5 GB (468862128 x 512) ... is now current device ** Unrecognized filesystem type ** ethernet@1c30000 Waiting for PHY auto negotiation to complete....... done BOOTP broadcast 1 DHCP client bound to address 10.0.0.126 (7 ms) *** Warning: no boot file name; using '0A00007E.img' Using ethernet@1c30000 device TFTP from server 10.0.0.136; our IP address is 10.0.0.126 Filename '0A00007E.img'. Load address: 0x42000000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-02-01-1a-9a-1c-cb Using ethernet@1c30000 device TFTP from server 10.0.0.136; our IP address is 10.0.0.126 Filename 'pxelinux.cfg/01-02-01-1a-9a-1c-cb'. Load address: 0x4fd00000 Loading: T T T T T T T T T T
armbianEnv.txt
verbosity=1 console=both overlay_prefix=sun50i-h5 rootdev=UUID=5d4a9712-49dd-4566-8f99-28aba89a7816 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:uboot.cmd
mw.l 0x01C20020 0x80101810 # DO NOT EDIT THIS FILE # # Please edit /boot/armbianEnv.txt to set supported parameters # # default values setenv load_addr "0x44000000" setenv rootdev "/dev/mmcblk0p1" setenv verbosity "1" setenv rootfstype "ext4" setenv console "both" setenv docker_optimizations "on" # Print boot source itest.b *0x10028 == 0x00 && echo "U-boot loaded from SD" itest.b *0x10028 == 0x02 && echo "U-boot loaded from eMMC or secondary SD" itest.b *0x10028 == 0x03 && echo "U-boot loaded from SPI" echo "Boot script loaded from ${devtype}" if test -e ${devtype} ${devnum} ${prefix}armbianEnv.txt; then load ${devtype} ${devnum} ${load_addr} ${prefix}armbianEnv.txt env import -t ${load_addr} ${filesize} fi if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=ttyS0,115200 console=tty1"; fi if test "${console}" = "serial"; then setenv consoleargs "console=ttyS0,115200"; fi # get PARTUUID of first partition on SD/eMMC it was loaded from # mmc 0 is always mapped to device u-boot (2016.09+) was loaded from if test "${devtype}" = "mmc"; then part uuid mmc 0:1 partuuid; fi setenv bootargs "root=${rootdev} rootwait rootfstype=${rootfstype} ${consoleargs} panic=10 consoleblank=0 loglevel=${verbosity} ubootpart=${partuuid} usb-storage.quirks=${usbstoragequirks} ${extraargs} ${extraboardargs}" if test "${docker_optimizations}" = "on"; then setenv bootargs "${bootargs} cgroup_enable=memory swapaccount=1"; fi load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile} fdt addr ${fdt_addr_r} fdt resize 65536 for overlay_file in ${overlays}; do if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/allwinner/overlay/${overlay_prefix}-${overlay_file}.dtbo; then echo "Applying kernel provided DT overlay ${overlay_prefix}-${overlay_file}.dtbo" fdt apply ${load_addr} || setenv overlay_error "true" fi done for overlay_file in ${user_overlays}; do if load ${devtype} ${devnum} ${load_addr} ${prefix}overlay-user/${overlay_file}.dtbo; then echo "Applying user provided DT overlay ${overlay_file}.dtbo" fdt apply ${load_addr} || setenv overlay_error "true" fi done if test "${overlay_error}" = "true"; then echo "Error applying DT overlays, restoring original DT" load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile} else if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/allwinner/overlay/${overlay_prefix}-fixup.scr; then echo "Applying kernel provided DT fixup script (${overlay_prefix}-fixup.scr)" source ${load_addr} fi if test -e ${devtype} ${devnum} ${prefix}fixup.scr; then load ${devtype} ${devnum} ${load_addr} ${prefix}fixup.scr echo "Applying user provided fixup script (fixup.scr)" source ${load_addr} fi fi load ${devtype} ${devnum} ${ramdisk_addr_r} ${prefix}uInitrd load ${devtype} ${devnum} ${kernel_addr_r} ${prefix}Image booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} # Recompile with: # mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr/boot dir
-rw-r--r-- 1 root root 263 Mar 18 2019 armbianEnv.bad.bak -rw-r--r-- 1 root root 165 Mar 1 13:17 armbianEnv.txt -rw-r--r-- 1 root root 165 Mar 18 2019 armbianEnv.txt.fresh -rw-r--r-- 1 root root 165 Jul 6 2024 armbianEnv.txt.good -rw-r--r-- 1 root root 0 Jan 14 2019 armbianEnv.txt.out -rw-r--r-- 1 root root 1536 Jan 9 2019 armbian_first_run.txt.template -rw-r--r-- 1 root root 230454 Jan 9 2019 boot.bmp -rw-r--r-- 1 root root 2997 Jan 11 2019 boot.cmd -rw-r--r-- 1 root root 4882 Jan 9 2019 boot-desktop.png -rw-rw-r-- 1 root root 3069 Jan 11 2019 boot.scr -rw-r--r-- 1 root root 223045 Feb 26 15:06 config-6.6.75-current-sunxi64 drwxr-xr-x 3 root root 4096 Mar 9 2020 dtb-4.19.104-sunxi64 drwxr-xr-x 2 root root 4096 Feb 1 2019 dtb-4.19.13-sunxi64 drwxr-xr-x 3 root root 4096 Feb 12 2019 dtb-4.19.20-sunxi64 drwxr-xr-x 3 root root 4096 Apr 16 2019 dtb-4.19.25-sunxi64 drwxr-xr-x 3 root root 4096 May 14 2019 dtb-4.19.38-sunxi64 drwxr-xr-x 3 root root 4096 Jul 6 2019 dtb-4.19.57-sunxi64 drwxr-xr-x 3 root root 4096 Aug 3 2019 dtb-4.19.63-sunxi64 drwxr-xr-x 3 root root 4096 Feb 11 2021 dtb-5.10.12-sunxi64 drwxr-xr-x 3 root root 4096 Feb 18 2021 dtb-5.10.16-sunxi64 drwxr-xr-x 3 root root 4096 Mar 29 2021 dtb-5.10.21-sunxi64 drwxr-xr-x 3 root root 4096 May 14 2021 dtb-5.10.34-sunxi64 drwxr-xr-x 3 root root 4096 Jan 10 2021 dtb-5.10.4-sunxi64 drwxr-xr-x 3 root root 4096 Sep 25 2021 dtb-5.10.60-sunxi64 drwxr-xr-x 3 root root 4096 Mar 10 2022 dtb-5.15.25-sunxi64 drwxr-xr-x 3 root root 4096 Aug 3 2022 dtb-5.15.48-sunxi64 drwxr-xr-x 3 root root 4096 Nov 5 2022 dtb-5.15.74-sunxi64 drwxr-xr-x 3 root root 4096 Mar 1 2023 dtb-5.15.93-sunxi64 drwxr-xr-x 3 root root 4096 May 10 2020 dtb-5.4.28-sunxi64 drwxr-xr-x 3 root root 4096 Jun 6 2020 dtb-5.4.43-sunxi64 drwxr-xr-x 3 root root 4096 Aug 23 2020 dtb-5.7.15-sunxi64 drwxr-xr-x 3 root root 4096 Sep 24 2020 dtb-5.8.10-sunxi64 drwxr-xr-x 3 root root 4096 Sep 26 2020 dtb-5.8.11-sunxi64 drwxr-xr-x 3 root root 4096 Oct 9 2020 dtb-5.8.13-sunxi64 drwxr-xr-x 3 root root 4096 Oct 18 2020 dtb-5.8.14-sunxi64 drwxr-xr-x 3 root root 4096 Oct 27 2020 dtb-5.8.16-sunxi64 drwxr-xr-x 3 root root 4096 Sep 8 2020 dtb-5.8.6-sunxi64 drwxr-xr-x 3 root root 4096 Dec 17 2020 dtb-5.9.14-sunxi64 drwxr-xr-x 3 root root 4096 Mar 21 15:49 dtb-6.6.75-current-sunxi64 lrwxrwxrwx 1 root root 20 Mar 9 2020 dtb.old -> dtb-4.19.104-sunxi64 lrwxrwxrwx 1 root root 23 Mar 1 2023 Image -> vmlinuz-5.15.93-sunxi64 -rw-r--r-- 1 root root 3584829 Feb 26 15:06 System.map-6.6.75-current-sunxi64 lrwxrwxrwx 1 root root 23 Aug 2 2023 uInitrd -> uInitrd-5.15.93-sunxi64 -
Spotted this "Orange pi robot" board inside a commercial R2 D2 DIY kit. Start around 20:00
The guy made a pervious video here showing what the toy does:
-
On 11/14/2020 at 5:25 PM, Werner said:
All kernel and header packages for the sunxi family are built from https://github.com/megous/linux/tree/orange-pi-5.9
I'm running 5.10.12 on opi PC2 and gettin the same problem with V4L2_PIX_FMT_SUNXI_TILED_NV12 which is not defined in /usr/include/linux/videodev2.h
It is defined in that source tree
https://github.com/megous/linux/blob/orange-pi-5.10/include/uapi/linux/videodev2.h
How is it getting lost in the armbian build process?
-
I have NFS running on opi PC2 5.4.43-sunxi64 working fine
-
I had a problem with ext4 and data being committed every 30 seconds and changing commit interval in fstab made no difference to fix it I modified:
/proc/sys/vm/dirty_expire_centisecs
to 500 (5 seconds). 30 seconds is default
You can monitor it with:
cat /proc/meminfo | grep "Dirty" -A1
-
The latest update on my OPI pc2 has reduced the max cpu freq from 1.3ghz to 1.01ghz.
I believe the old minfreq was 120mhz?
linux-stretch-root-next-orangepipc2_5.85_arm64.deb
/etc/default/cpufrequtils
# WARNING: this file will be replaced on board support package (linux-root-...) upgrade ENABLE=true MIN_SPEED=480000 MAX_SPEED=1010000 GOVERNOR=ondemand
-
I have a similar issue on opi PC2 with 4.19.25-sunxi64 and a DVB-T2 USB dongle. The problem is solved by locking the frequency scaling.
E.g. I have
# WARNING: this file will be replaced on board support package (linux-root-...) upgrade ENABLE=true MIN_SPEED=120000 MAX_SPEED=1400000 #MAX_SPEED=500000 GOVERNOR=conservativeIf MIN_SPEED and MAX_SPEED are the same you don't get any problems.
Performance gov works OK (it locks to max freq)
ondemand or interactive don't fix it unless you lock frequency
I can lock frequency at 420mhz and it works fine so it's not related to actual frequency
If I set MIN=800 and max=1300 it still gives problems
my error:
[ 6382.756348] rcu: INFO: rcu_sched self-detected stall on CPU [ 6382.756892] rcu: 1-....: (5601 ticks this GP) idle=d8a/1/0x4000000000000004 softirq=227944/227947 fqs=2034 [ 6382.756957] rcu: (t=5250 jiffies g=486985 q=1835) [ 6382.757208] Task dump for CPU 1: [ 6382.757310] kworker/1:2 R running task 0 4002 2 0x0000002a [ 6382.757904] Workqueue: events dbs_work_handler [ 6382.758057] Call trace: [ 6382.758316] dump_backtrace+0x0/0x1c0 [ 6382.758526] show_stack+0x14/0x20 [ 6382.758703] sched_show_task+0x160/0x198 [ 6382.758900] dump_cpu_task+0x40/0x50 [ 6382.759103] rcu_dump_cpu_stacks+0xc0/0x100 [ 6382.759281] rcu_check_callbacks+0x594/0x780 [ 6382.759455] update_process_times+0x2c/0x58 [ 6382.759664] tick_sched_handle.isra.5+0x30/0x48 [ 6382.759844] tick_sched_timer+0x48/0x98 [ 6382.760013] __hrtimer_run_queues+0xe4/0x1f8 [ 6382.760172] hrtimer_interrupt+0xf4/0x2b0 [ 6382.760378] arch_timer_handler_phys+0x28/0x40 [ 6382.760563] handle_percpu_devid_irq+0x80/0x138 [ 6382.760765] generic_handle_irq+0x24/0x38 [ 6382.760960] __handle_domain_irq+0x5c/0xb0 [ 6382.761107] gic_handle_irq+0x58/0xa8 [ 6382.761249] el1_irq+0xb0/0x140 [ 6382.761466] __usb_hcd_giveback_urb+0x98/0x148 [ 6382.761649] usb_giveback_urb_bh+0xdc/0x170 [ 6382.761821] tasklet_action_common.isra.3+0x7c/0x168 [ 6382.761961] tasklet_action+0x24/0x30 [ 6382.762107] __do_softirq+0x10c/0x200 [ 6382.762238] irq_exit+0xac/0xc0 [ 6382.762431] __handle_domain_irq+0x60/0xb0 [ 6382.762567] gic_handle_irq+0x58/0xa8 [ 6382.762706] el1_irq+0xb0/0x140 [ 6382.762915] clk_propagate_rate_change+0x30/0xe0 [ 6382.763088] clk_propagate_rate_change+0x90/0xe0 [ 6382.763262] clk_propagate_rate_change+0x90/0xe0 [ 6382.763465] clk_core_set_rate_nolock+0x1c0/0x1f8 [ 6382.763649] clk_set_rate+0x38/0xa8 [ 6382.763807] dev_pm_opp_set_rate+0x1f0/0x540 [ 6382.764083] set_target+0x40/0x70 [cpufreq_dt] [ 6382.764276] __cpufreq_driver_target+0x184/0x5b0 [ 6382.764463] od_dbs_update+0x140/0x1a0 [ 6382.764660] dbs_work_handler+0x3c/0x70 [ 6382.764858] process_one_work+0x1e4/0x360 [ 6382.765042] worker_thread+0x48/0x4b0 [ 6382.765195] kthread+0x128/0x130 [ 6382.765367] ret_from_fork+0x10/0x1csome others with the issue:
-
On the PC2 I found the default governor (ondemand?) makes the freq spike too much, conservative prevents it from just hitting max freq every time you load it.
I run conservative with an up_threshold of 50 (I think default is 25%)
IIRC the parameter that allows it to consider IO as part of the load is not available on conservative so you lose a small amount of performance at the top end. If you're using USB wifi dongles it also doesn't want to increase freq in a hurry when running conservative.
-
I have just noticed the same issue when trying to use armbian-config on pi pc2, as have others here:
https://github.com/armbian/config/issues/33
My armbianEnv.txt looks like this
/var/log.hdd/aptitude { rotate 6 monthly compress missingok notifempty } ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:uHow can I regenerate armbianEnv.txt without doing a reinstall?
edit: pulled it from the .img
-
I thought I'd share some links to JMS578 based enclosures I've found:
ACASIS FA-08US - cheapest on ebay but also on ali https://www.aliexpress.com/item/Acasis-fa08us-2-5-inch-usb3-0-aluminum-external-hard-drive-disk-SATA-SSD-mechanical-solid/32818921168.html
Metal enclosure with plastic tray, has 4 mounting holes to secure the drive to the tray. Firmware Version: v0.5.0.8
CHIPAL clear enclosure - Firmware Version: v133.2.0.2. This enclosure gave me errors after running fstrim with an ADATA SU650 but not with another SSD I have. It works fine with discard. The SU650 + fstrim works fine in the ACASIS enclosure.
JZYuan adapter - according the pictures on aliexpress it has JMS578 but I've not personally tested it
-
Mt76 based dongles should work. A6210 works OK for me. I get around 160mbit/250mbit on 5ghz AC
110mbit on 2.4ghz
Around £15 on ebay. Argos sell them for £30 but reduce to £20 on occasion
https://wireless.wiki.kernel.org/en/users/drivers/mediatek
The drivers are under active development https://github.com/openwrt/mt76/commits/master
some of the RTL8812AU yellow dongles from china come with RTL8812CU now. RTL8812AU perform bad even under windows so likely have poor design
-
On 12/17/2018 at 5:35 AM, svts said:
So the problem was solved!
sed -i -e '1imw.l 0x01C20020 0x80101810\' /boot/boot.cmd mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scrThe reason of crashes was DRAM PLL value which seems too high for the boards I have.
Default DRAM_PLL value set by u-boot 2017.05+ is 624MHz. It seems not all board support this value.
I changed it to 600MHz by setting 0x01c20020 register to 0x1810 value (instead of 0x1910 set by u-boot) and there's no any crash anymore.
The script adds "mw.l 0x01C20020 0x80101810" line to boot.cmd and then compiles boot.scr.
After that u-boot will change DRAM_PLL value to a bit lower one to avoid crashes.
Thanks everybody who helped me to find a solution.
Special thanks to @znoxx for testing and logging
Great work! I have the same problem with a PC 2 which came direct from the manufacturer
Your script has some unicode characters so I removed them:
sed -i -e '1imw.l 0x01C20020 0x80101810\' /boot/boot.cmd mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr -
15 hours ago, guidol said:
Not for $20 shipped, but with the -for me - cheap NAS case the NanoPi Neo2 LTS is a option.
The Neo2 is available with 512MB or 1GB of Ram and works fine inside the NAS-Case
(I got 2 of these combinations running over a year).armbian-support for the Neo2 (H5-CPU) is fine. HDMI isnt included, but with the NAS-case he has 2 USB 2.0-Ports, GBE,
a power-switch AND a proper Power-connector for a normal 12V power-supply
Neo2 LTS:
https://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=180
NAS-case:
https://www.friendlyarm.com/index.php?route=product/product&path=85&product_id=222
That looks neat and essentially gives me 3 USB ports as I would be using USB-SATA adapter anyway but it's $55 USD including shipping to the UK
7 hours ago, manuti said:OPi PC 2 is around 23€ including ship cost to my country. But for my is a huge upgrade from OPi PC Gigabit and cpu extensions made the difference.
sound good
-
I have an orange pi PC that I use as a simple NAS (NFS, smb, iscsi) and for openVPN occasionally but want something new with GbE.
What is the best upgrade that will give me 2 or more usb ports, GbE and a faster processor? With decent software support (
)? I don't need HDMI or wifi but it would be a plus
512MB-1GB RAM
opi zero plus?
opi PC 2?
Around $20 shipped ideally
-
Using performance gov on opi PC with Sandisk 16GB A1 on a usb card reader
Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Output is in kBytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 kBytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 3546 3573 5092 5086 4412 2948 102400 16 4588 8634 15272 15273 13885 7955 102400 512 21594 30277 36395 36542 35605 27344 102400 1024 28300 32080 36932 37035 36661 26242 102400 16384 30036 32860 37809 37933 37894 28773 iozone test complete.Purchased from aliexpress ($5) but the scratch & verify sticker says it's genuine
My samsung evo 64gb went read-only recently (20 months old) and then would not boot. I copied to another card and ran fsck and all seems OK. I think the later evos were not as well made as the earlier batches.
-
I'd use this to get the HDMI output of your DSLR encoded (720p only)
https://blog.danman.eu/new-version-of-lenkeng-hdmi-over-ip-extender-lkv373a/
Then a raspberry pi or pi0 to do the hw h264 re-encoding
-
Not sure, but I don't think so. AFAIK you can only wake from IR or GPIO
You can buy RTC modules based on the DS3231 which have built in wakeup alarms that you can set and trigger a GPIO on the opi to wake it
-
If you want hardware accelerated decoding you need to use mpv or mplayer. I'm not sure if you can run multiple instances and all use VDPAU
edit: mpv segfaults if you open 2 instances
-
I have VDPAU working on TVout on the opi zero.
VDPAU only works on screen0. opizero is set to use screen1 by default, but both are configured to PAL/TVOUT. setting VDPAU_SCREEN=1 had no effect so I just changed the fex to: disp_mode=0
-
On 12/30/2017 at 7:47 AM, pbezza said:
Assuming different versions are just around the corner, I'll wait and see all the variations of specs before purchasing.
Lite2
-
On 11/23/2017 at 10:36 AM, Moklev said:
Thank you!
I'll try with "extraargs=cma=96M".Did you have any success?
-
I updated to head and recompiled and still have a black screen.
Do I need to edit the kernel config? CONFIG_CMA_SIZE_MBYTES is set to 16
edit: appears not, this is from dmesg
cma: CMA: reserved 128 MiB at 58000000 Kernal Command Line: ... cma=96M -
Thanks.
Desktop works but HW video decoding doesn't, I just get a black window - the same video works on my OpiPC.
Does VDPAU support TV out/CVBS?
Using: Armbian_5.35_Orangepizero_Debian_jessie_default_3.4.113_desktop
Orange Pi PC2 failed to boot after update
in Allwinner sunxi
Posted · Edited by Magnets
I tried copying dtb and initrd for 6.6.75 but it wouldn't boot.
I managed to mount the system using chroot on x64 machine using binfmt-support and qemu-user-static, downgraded kernel using what I had available in apt-cache
5.15.93-sunxi64 #23.02.2
i also had to downgrade dtb package as suggested here
No FDT memory address configured. Please configure ERROR: Did not find a cmdline Flattened Device Treeall working