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. Dear forum, When looking at the Orange Pi Zero schematic V1.1, the OSC-RTC box is empty. Does this mean that there is no crystal for the internal RTC? The internal RTC cannot be used at all? When just checking the time register, the RTC is running too fast. Thanks, Arjan
  2. hardware: Orange Pi Zero H2 Kernel: 5.9.14-sunxi Armbian 20.11.3 Buster ethtool version 5.9 get error on cable-test option. full log: http://ix.io/2Icy sudo ethtool --cable-test eth0 netlink error: PHY driver does not support cable testing netlink error: Operation not supported
  3. Hardware: Orange Pi Zero 512MB LTS (several different devices), bench power supply, good SD card - everything working good at all clock speeds from 480MHz upwards (all the way up to 1.4GHz even, with a heatsink). ffmpeg encode, stress-ng etc. are all fine. Specifically, the board is rock solid at 960MHz. What I want to achieve: take the U-boot for OPi Zero, and rebuild with an adjusted config to achieve a faster boot time, by replacing CONFIG_SYS_CLK_FREQ=480000000 with CONFIG_SYS_CLK_FREQ=960000000. (Does anyone know why the standard Armbian build is set to boot at such a low clock speed?) Starting point: I can successfully build U-boot from the Armbian sources (using Armbian's orangepi_zero_defconfig), write to SSD using nand-sata-install, and boot. It works fine. So there is nothing wrong with my build process, or my ability to reproduce the base configuration. What goes wrong: when I adjust CONFIG_SYS_CLK_FREQ=960000000, the board fails to boot. It freezes a few seconds into booting the kernel, with the UART output normally just stopping around here: [ OK ] Started Armbian memory supported logging. Starting Journal Service... [ OK ] Started Raise network interfaces. Occasionally I will get some kind of error: [ 6.871890] BUG: Bad page state in process sed pfn:546e2 So it appears that, in addition to adjusting the CPU frequency, I need to adjust something else to make it all work. Does anyone know what needs to be done? Thanks!
  4. Good evening, I ran into some problems with sbc-bench on a couple of Allwinner boards Orange Pi Zero, Orange Pi Zero+, Orange Pi One and Nanopi Neo 2 spcifically. The 7 Zip benchmark causes the following error: ./sbc-bench.sh: Zeile 611: 4206 Bus-Zugriffsfehler "${SevenZip}" b >> ${TempLog} Most likely due to a problem with the ZRam: zram: Decompression failed! err=-22 This happens on all boards under Debian and focal with different SD cards and power supplies. The benchmark ran previously on this setups without any issues – unfortunately I don’t know when it stopped working and hence cannot narrow down the change that caused the problem. The benchmark results and armbianmonitor output from the Orange Pi one as an example: http://ix.io/2EPZ http://ix.io/2ES2 Is this a known issue? Is there a solution? Daniel
  5. Hi, I've been using Armbian for three years on some work's project and this is the first time I see this issue. Basically I have an image of the operative system and all the programs and scripts already saved in it, so when I have to prepare a new SD card I just use the command "dd" and then I modify some registry stuff specific for the object I'm creating. It has always worked without problem, but now we bought a new batch of SD cards and I'm facing this issue: the dd command goes succesfully and if I mount the partitions after it has finished I can see all my data, but when I boot the system sometimes I get some errors. Here is the last part of the boot log: [ 12.866043] systemd[1]: Mounted Kernel Configuration File System. [ 13.948285] thermal thermal_zone0: binding zone cpu_thermal with cdev thermal-cpufreq-0 failed:-22 [ 93.570475] mmc0: Card stuck in programming state! mmc_do_erase [ 94.342442] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 95.110441] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 95.870438] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 95.877698] blk_update_request: I/O error, dev mmcblk0, sector 1863688 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0 [ 95.889014] blk_update_request: I/O error, dev mmcblk0, sector 1281568 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 95.889652] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #13767: comm fstrim: reading directory lblock 0 [ 95.900257] EXT4-fs error (device mmcblk0p2): __ext4_get_inode_loc:4699: inode #135743: block 524611: comm rc.local: unable to read itable block [ 95.911460] EXT4-fs (mmcblk0p1): I/O error while writing superblock [ 95.924553] EXT4-fs (mmcblk0p2): I/O error while writing superblock [ 95.937750] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #13767: comm fstrim: reading directory lblock 0 [ 95.938429] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #13767: comm find: reading directory lblock 0 [ 95.949147] EXT4-fs (mmcblk0p1): I/O error while writing superblock [ 95.950615] EXT4-fs error (device mmcblk0p2): __ext4_get_inode_loc:4699: inode #135743: block 524611: comm rc.local: unable to read itable block [ 95.950697] EXT4-fs (mmcblk0p2): I/O error while writing superblock [ 95.960128] EXT4-fs (mmcblk0p1): previous I/O error to superblock detected [ 95.967624] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #13767: comm fstrim: reading directory lblock 0 [ 95.979752] EXT4-fs (mmcblk0p1): I/O error while writing superblock [ 95.985982] EXT4-fs (mmcblk0p1): previous I/O error to superblock detected [ 95.993275] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #13767: comm find: reading directory lblock 0 [ 96.004308] EXT4-fs (mmcblk0p1): I/O error while writing superblock [ 96.010602] EXT4-fs (mmcblk0p1): previous I/O error to superblock detected [ 96.010702] EXT4-fs (mmcblk0p1): I/O error while writing superblock [ 96.018166] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #13767: comm fstrim: reading directory lblock 0 [ 96.029509] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #13767: comm find: reading directory lblock 0 [ 96.032375] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #99: comm systemd-udevd: reading directory lblock 0 [ 96.032420] EXT4-fs (mmcblk0p1): I/O error while writing superblock [ 96.035115] EXT4-fs (mmcblk0p1): I/O error while writing superblock [ 96.094862] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #13767: comm find: reading directory lblock 0 [ 96.094899] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #13767: comm fstrim: reading directory lblock 0 [ 96.918443] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 97.674443] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 98.442444] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 99.210440] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 99.974443] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 100.730444] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 100.810651] debugfs: Directory 'mmcblk0' with parent 'block' already present! [ 125.415973] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #7779: comm cron: reading directory lblock 0 [ 125.427247] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #7779: comm cron: reading directory lblock 0 [ 125.438653] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #46845: comm cron: reading directory lblock 0 [ 125.450113] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #7779: comm cron: reading directory lblock 0 [ 125.461370] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #7779: comm cron: reading directory lblock 0 [ 125.472605] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #7779: comm cron: reading directory lblock 0 [ 125.483833] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1532: inode #46845: comm cron: reading directory lblock 0 Sometimes it manages to exit from the error state, other times it keeps logging the same error message. We have tested the SD cards using some broken sectors detector software, and none of them found any problems. The source image is working because if I use an old SD card, I don't see any errors. I tried dd-ing a vanilla version of Armbian into one of the SD cards that is giving me problems and it is working nicely. I tried the same "broken-OS SD cards" into differents OrangePI and none of them worked. The problem happens sometimes at boot, sometimes after a couple of minutes (I saw some kernel panic). This is the output of "uname -a": Linux smartbit 5.4.45-sunxi #20.05.3 SMP Wed Jun 10 12:09:20 CEST 2020 armv7l armv7l armv7l GNU/Linux The "dd" command (which is working on old SD cards) is the following: dd if=./latest.img of=/dev/sdd bs=1M conv=fsync So if the problem is in the source image, why is it working on the old SD cards batch? Otherwise, if the problem is in the SD card, why an Armbian vanilla image isn't giving any problems? Thanks a lot in advance for any help. Mattia
  6. Is it possible that there have been some image changes that broke the XR819 wifi completely? The available images for download on the Armbian page (5.3 server, and 5.4 minimal) as well as a custom built "legacy" branch linux-4.19 image all show the same behavior, The wlan0 interface is not active and it's not possible to bring it up. And dmesg shows that module has been initialized but not much more. Armbianmonitor support info: 5.3.9 official buster server image: http://ix.io/240Y 4.19.88 self-built, two days ago, legacy branch: http://ix.io/240U Everything below is from the official image, but the 4.19 image shows the exact same It is definitely not a hardware issue, I have a SD card with a an older 4.19.72 image (when the branch was still called "next") that works just fine. ifconfig -a ifconfig root@orangepizero:~# ifconfig wlan0 up SIOCSIFFLAGS: Invalid argument root@orangepizero:~# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no root@orangepizero:~# journalctl -b | grep xradio Nov 19 08:08:00 orangepizero kernel: xradio_wlan mmc1:0001:1: Input buffers: 30 x 1632 bytes Nov 19 08:08:00 orangepizero kernel: xradio_wlan mmc1:0001:1: Firmware Label:XR_C01.08.0043 Jun 6 2016 20:41:04 Nov 19 08:08:28 orangepizero NetworkManager[1057]: <info> [1574150908.3204] rfkill0: found WiFi radio killswitch (at /sys/devices/platform/soc/1c10000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy0/rfkill0) (driver xradio_wlan) root@orangepizero:~# uname -a Linux orangepizero 5.3.9-sunxi #19.11.3 SMP Mon Nov 18 18:49:43 CET 2019 armv7l GNU/Linux
  7. I have a raspi hat (rak2245) that has 2 versions: a pi-hat version that has a 40 pin-header on it for raspberry pi's , but also a smaller stamp edition. It uses spi and uart to communicate with the pi. I have it running without issues on my orange pi zero, even though the pinheader is a little too large. And via a breadboard I can access all pins just fine. But since I am making my own PCB anyway, I am interested in using the stamp version. The only difference between the stamp and the pi-hat version (aside from the form-factor and pin-out) is that the pi-hat version has an additional eeprom chip to tell the rapsberry pi about the function of the pins apparently. Now I wonder if that chip is just a convenience or if I can actually do without it. I am comfortable making my own device tree overlay files to indicate pin functions. I've done it with spi before to add additional CS pins on the orange pi zero. So my question is, would that likely be enough to get the stamp version running, or would leaving out the eeprom chip likely make it not work (without serious driver development work)? Cheers.
  8. I have the same problem like other users here, the 1-wire doesn't run correctly, I added 1-wire to armbianEnv.txt, 1-wire drivers are loaded, but I cannot access the data of DS18B20 attached to PA06. L. ___ ____ _ _____ / _ \| _ \(_) |__ /___ _ __ ___ | | | | |_) | | / // _ \ '__/ _ \ | |_| | __/| | / /| __/ | | (_) | \___/|_| |_| /____\___|_| \___/ Welcome to Armbian 20.08.17 Bionic with Linux 5.8.16-sunxi System load: 26% Up time: 0 min Memory usage: 14% of 491M IP: 192.168.3.163 CPU temp: 45°C Usage of /: 4% of 29G Last login: Tue Nov 17 15:06:39 2020 from 192.168.3.31 pi@orangepizero:~$ cat /boot/armbianEnv.txt verbosity=7 logo=disabled console=serial disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 rootdev=UUID=4618846b-19e6-421b-8872-767a46ed5e1e rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u overlays=w1-gpio param_w1_pin=PA06 # desired pin param_w1_pin_int_pullup=1 # internal pullup-resistor: 1=on, 0=off pi@orangepizero:~$ ls -l /sys/bus/w1/devices/ total 0 lrwxrwxrwx 1 root root 0 Nov 17 15:09 w1_bus_master1 -> ../../../devices/w1_bus_master1 pi@orangepizero:~$ sudo cat /sys/kernel/debug/gpio [sudo] password for pi: gpiochip0: GPIOs 0-223, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-11 ( |sysfs ) out lo gpio-17 ( |orangepi:red:status ) out lo gpio-20 ( |reg_vcc_wifi ) out hi gpio-110 ( |onewire@0 ) out lo <-------------------- gpio-166 ( |cd ) in lo ACTIVE LOW gpio-204 ( |usb0_id_det ) in hi IRQ gpiochip1: GPIOs 352-383, parent: platform/1f02c00.pinctrl, 1f02c00.pinctrl: gpio-358 ( |vdd-cpux ) out hi gpio-359 ( |reset ) out hi ACTIVE LOW gpio-362 ( |orangepi:green:pwr ) out hi pi@orangepizero:~$ lsmod Module Size Used by aes_arm_bs 20480 2 crypto_simd 16384 1 aes_arm_bs ccm 20480 6 xradio_wlan 114688 1 mac80211 516096 1 xradio_wlan cfg80211 471040 2 mac80211,xradio_wlan lima 45056 0 rfkill 20480 3 cfg80211 gpu_sched 28672 1 lima libarc4 16384 1 mac80211 sun4i_gpadc_iio 16384 0 industrialio 53248 1 sun4i_gpadc_iio sun8i_thermal 16384 0 sun8i_ce 24576 0 crypto_engine 16384 1 sun8i_ce sun8i_di 20480 0 sunxi_cedrus 32768 0 w1_gpio 16384 0 <------------- zram 24576 2 wire 32768 1 w1_gpio cn 16384 1 wire uio_pdrv_genirq 16384 0 uio 16384 1 uio_pdrv_genirq cpufreq_dt 20480 0 sch_fq_codel 20480 6 usb_f_acm 20480 1 u_serial 24576 3 usb_f_acm g_serial 16384 0 libcomposite 45056 2 g_serial,usb_f_acm ip_tables 24576 0 x_tables 24576 1 ip_tables autofs4 36864 2 pwrseq_simple 16384 1 sunxi 20480 0 phy_generic 20480 2 sunxi pi@orangepizero:~$ ls -l /boot/dtb/overlay/ total 384 -rw-r--r-- 1 root root 5448 Oct 20 22:15 README.sun4i-a10-overlays -rw-r--r-- 1 root root 3262 Oct 20 22:15 README.sun5i-a13-overlays -rw-r--r-- 1 root root 6817 Oct 20 22:15 README.sun7i-a20-overlays -rw-r--r-- 1 root root 4736 Oct 20 22:15 README.sun8i-h3-overlays -rw-r--r-- 1 root root 267 Oct 20 22:15 sun4i-a10-analog-codec.dtbo -rw-r--r-- 1 root root 387 Oct 20 22:15 sun4i-a10-can.dtbo -rw-r--r-- 1 root root 4832 Oct 20 22:15 sun4i-a10-fixup.scr -rw-r--r-- 1 root root 500 Oct 20 22:15 sun4i-a10-i2c1.dtbo -rw-r--r-- 1 root root 500 Oct 20 22:15 sun4i-a10-i2c2.dtbo -rw-r--r-- 1 root root 2301 Oct 20 22:15 sun4i-a10-nand.dtbo -rw-r--r-- 1 root root 778 Oct 20 22:15 sun4i-a10-pps-gpio.dtbo -rw-r--r-- 1 root root 443 Oct 20 22:15 sun4i-a10-pwm.dtbo -rw-r--r-- 1 root root 1040 Oct 20 22:15 sun4i-a10-spdif-out.dtbo -rw-r--r-- 1 root root 1093 Oct 20 22:15 sun4i-a10-spi-jedec-nor.dtbo -rw-r--r-- 1 root root 1069 Oct 20 22:15 sun4i-a10-spi-spidev.dtbo -rw-r--r-- 1 root root 949 Oct 20 22:15 sun4i-a10-uart2.dtbo -rw-r--r-- 1 root root 1205 Oct 20 22:15 sun4i-a10-uart3.dtbo -rw-r--r-- 1 root root 935 Oct 20 22:15 sun4i-a10-uart4.dtbo -rw-r--r-- 1 root root 802 Oct 20 22:15 sun4i-a10-uart5.dtbo -rw-r--r-- 1 root root 806 Oct 20 22:15 sun4i-a10-uart6.dtbo -rw-r--r-- 1 root root 806 Oct 20 22:15 sun4i-a10-uart7.dtbo -rw-r--r-- 1 root root 777 Oct 20 22:15 sun4i-a10-w1-gpio.dtbo -rw-r--r-- 1 root root 267 Oct 20 22:15 sun5i-a13-analog-codec.dtbo -rw-r--r-- 1 root root 2146 Oct 20 22:15 sun5i-a13-fixup.scr -rw-r--r-- 1 root root 500 Oct 20 22:15 sun5i-a13-i2c1.dtbo -rw-r--r-- 1 root root 500 Oct 20 22:15 sun5i-a13-i2c2.dtbo -rw-r--r-- 1 root root 1239 Oct 20 22:15 sun5i-a13-nand.dtbo -rw-r--r-- 1 root root 382 Oct 20 22:15 sun5i-a13-pwm.dtbo -rw-r--r-- 1 root root 1069 Oct 20 22:15 sun5i-a13-spi-jedec-nor.dtbo -rw-r--r-- 1 root root 1045 Oct 20 22:15 sun5i-a13-spi-spidev.dtbo -rw-r--r-- 1 root root 974 Oct 20 22:15 sun5i-a13-spi0.dtbo -rw-r--r-- 1 root root 936 Oct 20 22:15 sun5i-a13-spi1.dtbo -rw-r--r-- 1 root root 563 Oct 20 22:15 sun5i-a13-spi2.dtbo -rw-r--r-- 1 root root 795 Oct 20 22:15 sun5i-a13-uart0.dtbo -rw-r--r-- 1 root root 505 Oct 20 22:15 sun5i-a13-uart1.dtbo -rw-r--r-- 1 root root 505 Oct 20 22:15 sun5i-a13-uart2.dtbo -rw-r--r-- 1 root root 505 Oct 20 22:15 sun5i-a13-uart3.dtbo -rw-r--r-- 1 root root 267 Oct 20 22:15 sun7i-a20-analog-codec.dtbo -rw-r--r-- 1 root root 386 Oct 20 22:15 sun7i-a20-can.dtbo -rw-r--r-- 1 root root 5532 Oct 20 22:15 sun7i-a20-fixup.scr -rw-r--r-- 1 root root 500 Oct 20 22:15 sun7i-a20-i2c1.dtbo -rw-r--r-- 1 root root 500 Oct 20 22:15 sun7i-a20-i2c2.dtbo -rw-r--r-- 1 root root 500 Oct 20 22:15 sun7i-a20-i2c3.dtbo -rw-r--r-- 1 root root 766 Oct 20 22:15 sun7i-a20-i2c4.dtbo -rw-r--r-- 1 root root 590 Oct 20 22:15 sun7i-a20-mmc2.dtbo -rw-r--r-- 1 root root 2301 Oct 20 22:15 sun7i-a20-nand.dtbo -rw-r--r-- 1 root root 778 Oct 20 22:15 sun7i-a20-pps-gpio.dtbo -rw-r--r-- 1 root root 443 Oct 20 22:15 sun7i-a20-pwm.dtbo -rw-r--r-- 1 root root 1040 Oct 20 22:15 sun7i-a20-spdif-out.dtbo -rw-r--r-- 1 root root 556 Oct 20 22:15 sun7i-a20-spi-add-cs1.dtbo -rw-r--r-- 1 root root 1093 Oct 20 22:15 sun7i-a20-spi-jedec-nor.dtbo -rw-r--r-- 1 root root 1069 Oct 20 22:15 sun7i-a20-spi-spidev.dtbo -rw-r--r-- 1 root root 808 Oct 20 22:15 sun7i-a20-uart2.dtbo -rw-r--r-- 1 root root 1078 Oct 20 22:15 sun7i-a20-uart3.dtbo -rw-r--r-- 1 root root 513 Oct 20 22:15 sun7i-a20-uart4.dtbo -rw-r--r-- 1 root root 513 Oct 20 22:15 sun7i-a20-uart5.dtbo -rw-r--r-- 1 root root 513 Oct 20 22:15 sun7i-a20-uart6.dtbo -rw-r--r-- 1 root root 513 Oct 20 22:15 sun7i-a20-uart7.dtbo -rw-r--r-- 1 root root 777 Oct 20 22:15 sun7i-a20-w1-gpio.dtbo -rw-r--r-- 1 root root 339 Oct 20 22:15 sun8i-h3-analog-codec.dtbo -rw-r--r-- 1 root root 384 Oct 20 22:15 sun8i-h3-cir.dtbo -rw-r--r-- 1 root root 478 Oct 20 22:15 sun8i-h3-cpu-clock-1.2GHz-1.3v.dtbo -rw-r--r-- 1 root root 982 Oct 20 22:15 sun8i-h3-cpu-clock-1.368GHz-1.3v.dtbo -rw-r--r-- 1 root root 898 Oct 20 22:15 sun8i-h3-cpu-clock-1.3GHz-1.3v.dtbo -rw-r--r-- 1 root root 4185 Oct 20 22:15 sun8i-h3-fixup.scr -rw-r--r-- 1 root root 374 Oct 20 22:15 sun8i-h3-i2c0.dtbo -rw-r--r-- 1 root root 374 Oct 20 22:15 sun8i-h3-i2c1.dtbo -rw-r--r-- 1 root root 374 Oct 20 22:15 sun8i-h3-i2c2.dtbo -rw-r--r-- 1 root root 778 Oct 20 22:15 sun8i-h3-pps-gpio.dtbo -rw-r--r-- 1 root root 862 Oct 20 22:15 sun8i-h3-pwm.dtbo -rw-r--r-- 1 root root 1040 Oct 20 22:15 sun8i-h3-spdif-out.dtbo -rw-r--r-- 1 root root 1177 Oct 20 22:15 sun8i-h3-spi-add-cs1.dtbo -rw-r--r-- 1 root root 804 Oct 20 22:15 sun8i-h3-spi-jedec-nor.dtbo -rw-r--r-- 1 root root 788 Oct 20 22:15 sun8i-h3-spi-spidev.dtbo -rw-r--r-- 1 root root 502 Oct 20 22:15 sun8i-h3-uart1.dtbo -rw-r--r-- 1 root root 502 Oct 20 22:15 sun8i-h3-uart2.dtbo -rw-r--r-- 1 root root 502 Oct 20 22:15 sun8i-h3-uart3.dtbo -rw-r--r-- 1 root root 504 Oct 20 22:15 sun8i-h3-usbhost0.dtbo -rw-r--r-- 1 root root 504 Oct 20 22:15 sun8i-h3-usbhost1.dtbo -rw-r--r-- 1 root root 504 Oct 20 22:15 sun8i-h3-usbhost2.dtbo -rw-r--r-- 1 root root 504 Oct 20 22:15 sun8i-h3-usbhost3.dtbo -rw-r--r-- 1 root root 777 Oct 20 22:15 sun8i-h3-w1-gpio.dtbo <----------- -rw-r--r-- 1 root root 374 Oct 20 22:15 sun8i-r40-i2c2.dtbo -rw-r--r-- 1 root root 374 Oct 20 22:15 sun8i-r40-i2c3.dtbo -rw-r--r-- 1 root root 547 Oct 20 22:15 sun8i-r40-spi-spidev0.dtbo -rw-r--r-- 1 root root 547 Oct 20 22:15 sun8i-r40-spi-spidev1.dtbo -rw-r--r-- 1 root root 505 Oct 20 22:15 sun8i-r40-uart2.dtbo -rw-r--r-- 1 root root 505 Oct 20 22:15 sun8i-r40-uart4.dtbo -rw-r--r-- 1 root root 505 Oct 20 22:15 sun8i-r40-uart5.dtbo -rw-r--r-- 1 root root 505 Oct 20 22:15 sun8i-r40-uart7.dtbo pi@orangepizero:~$ ls -l /sys/bus/w1/devices/ total 0 lrwxrwxrwx 1 root root 0 Nov 17 15:21 00-300000000000 -> ../../../devices/w1_bus_master1/00-300000000000 lrwxrwxrwx 1 root root 0 Nov 17 15:21 00-700000000000 -> ../../../devices/w1_bus_master1/00-700000000000 lrwxrwxrwx 1 root root 0 Nov 17 15:21 00-b00000000000 -> ../../../devices/w1_bus_master1/00-b00000000000 lrwxrwxrwx 1 root root 0 Nov 17 15:09 w1_bus_master1 -> ../../../devices/w1_bus_master1 pi@orangepizero:~$ ls -l /sys/bus/w1/devices/ total 0 lrwxrwxrwx 1 root root 0 Nov 17 15:21 00-700000000000 -> ../../../devices/w1_bus_master1/00-700000000000 lrwxrwxrwx 1 root root 0 Nov 17 15:21 00-b00000000000 -> ../../../devices/w1_bus_master1/00-b00000000000 lrwxrwxrwx 1 root root 0 Nov 17 15:09 w1_bus_master1 -> ../../../devices/w1_bus_master1 pi@orangepizero:~$ ls -l /sys/bus/w1/devices/ total 0 lrwxrwxrwx 1 root root 0 Nov 17 15:21 00-700000000000 -> ../../../devices/w1_bus_master1/00-700000000000 lrwxrwxrwx 1 root root 0 Nov 17 15:21 00-b00000000000 -> ../../../devices/w1_bus_master1/00-b00000000000 lrwxrwxrwx 1 root root 0 Nov 17 15:21 00-f00000000000 -> ../../../devices/w1_bus_master1/00-f00000000000 lrwxrwxrwx 1 root root 0 Nov 17 15:09 w1_bus_master1 -> ../../../devices/w1_bus_master1 pi@orangepizero:~$ ls -l /sys/bus/w1/devices total 0 lrwxrwxrwx 1 root root 0 Nov 17 15:22 00-080000000000 -> ../../../devices/w1_bus_master1/00-080000000000 lrwxrwxrwx 1 root root 0 Nov 17 15:21 00-700000000000 -> ../../../devices/w1_bus_master1/00-700000000000 lrwxrwxrwx 1 root root 0 Nov 17 15:21 00-f00000000000 -> ../../../devices/w1_bus_master1/00-f00000000000 lrwxrwxrwx 1 root root 0 Nov 17 15:09 w1_bus_master1 -> ../../../devices/w1_bus_master1 pi@orangepizero:~$ ls -l /sys/bus/w1/devices/00-700000000000/ ls: cannot access '/sys/bus/w1/devices/00-700000000000/': No such file or directory pi@orangepizero:~$ ls -l /sys/bus/w1/devices/00-080000000000/ total 0 lrwxrwxrwx 1 root root 0 Nov 17 15:23 driver -> ../../../bus/w1/drivers/w1_slave_driver -r--r--r-- 1 root root 4096 Nov 17 15:23 id -r--r--r-- 1 root root 4096 Nov 17 15:23 name drwxr-xr-x 2 root root 0 Nov 17 15:23 power -rw-r--r-- 1 root root 4096 Nov 17 15:23 rw lrwxrwxrwx 1 root root 0 Nov 17 15:23 subsystem -> ../../../bus/w1 -rw-r--r-- 1 root root 4096 Nov 17 15:22 uevent pi@orangepizero:~$ ls -l /sys/bus/w1/devices/00-f00000000000/ ls: cannot access '/sys/bus/w1/devices/00-f00000000000/': No such file or directory
  9. Hi, Please help to setup W5500 Ethernet board on Armbian (Orange PI Zero). My config: $ cat /boot/armbianEnv.txt verbosity=1 logo=disabled console=serial disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost2 usbhost3 spi-spidev param_spidev_spi_bus=1 rootdev=UUID=4a65461e-d8ac-4d8f-94c0-05ecd12f6d58 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u I can see spi: $ sudo ls -l /dev/spi* crw------- 1 root root 153, 0 Nov 3 22:32 /dev/spidev1.0 But no eth1... Maybe I need to install some "user_overlays"? I was trying to use "anyspi" and "w5500" overlays from Raspberry Pi but failed...
  10. Hello ! I have a problem with an OrangePi Zero under Armbian Buster with mainline kernel (5.8). I need to put the module snd-aloop as primary soundcard (index=0), and the integrated soundcard sun4i-codec as index=1. It worked very well with kernel 5.4 and before. I just had to load the snd-aloop module by adding it to /etc/modules and add "options snd-aloop index=0" to /etc/modprobe.d/alsa.conf. But now this is impossible, snd-aloop doesn't load. I had this message when I try to load it manually : modprobe: ERROR: could not insert 'snd_aloop': No such device After reading configuration file of the kernel, I saw that the module sun4i-codec (integrated soundcard) was directly integrated into the kernel, not as an external module, which is confirmed by the lsmod command, it no longer returns the name of the module. I think this is the reason of this issue, because this is the main change between the two versions. I have the impression that the index of the integrated sound card is no longer editable, unless you provide me a solution. I tried to invert indexes, but my software is too complicated to modify (experimental analog-to-digital gateway for HAM radio communications), so I need to keep the original configuration. I have also tried configuring indexes manually in kernel arguments, with no success. Can you help me please, because I can't downgrade to 5.4 to ensure the sustainability of the project. Thanks in advance -- MAX
  11. Hi, I've been trying to get the next IMU sensor to work: Fusion_IMU_BNO055, on my OPi zero with Armbian Bionic 20.08.10 with the linux kernel 5.8.14-sunxi. I have installed everything from the official Adafruit guide but I still get the same error. I have followed all the steps of this guide for beginners: OPi_r1_guide, executing all the commands successfully. However, I still have the same error in Python that is related to the "board" module. root@orangepizero:/home/Test# python Python 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import board Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python3.6/dist-packages/board.py", line 82, in <module> from adafruit_blinka.board.orangepi.orangepizero import * File "/usr/local/lib/python3.6/dist-packages/adafruit_blinka/board/orangepi/orangepizero.py", line 5, in <module> from adafruit_blinka.microcontroller.allwinner.h3 import pin File "/usr/local/lib/python3.6/dist-packages/adafruit_blinka/microcontroller/allwinner/h3/pin.py", line 4, in <module> PA0 = Pin(0) File "/usr/local/lib/python3.6/dist-packages/adafruit_blinka/microcontroller/generic_linux/libgpiod_pin.py", line 34, in __init__ self._chip = gpiod.Chip("gpiochip0", gpiod.Chip.OPEN_BY_NAME) AttributeError: module 'gpiod' has no attribute 'Chip' >>> exit() The python code that I try to execute is the following: import board import digitalio import busio print("Hello blinka!") # Try to great a Digital input pin = digitalio.DigitalInOut(board.PA6) print("Digital IO ok!") # Try to create an I2C device i2c = busio.I2C(board.SCL, board.SDA) print("I2C ok!") # Try to create an SPI device spi = busio.SPI(board.SCLK, board.MOSI, board.MISO) print("SPI ok!") print("done!") If you need more details I will gladly give them to you. Thank you.
  12. Hi! I recently upgraded the OS of my OpiZeroLTS, from the Debian Stretch Server 5.3.5 (available distro on Sunxi website) to Debian Buster 5.8.5 (downloaded from armbian webpage). Everything went well, except when I plug my USB webcam several video devices are assigned. I made a script with fswebcam to acquire still pictures from all /dev/video* and these "ghost" cameras are causing errors when the software try to open them as regular webcams. My script: for vid in /dev/video*; do output=$(basename $vid) fswebcam -d $vid -r 1920x1080 -D 10 -S 5 -F 1 --jpeg -1 --no-banner --no-timestamp --no-info /opt/images/$output mv /opt/images/$output /opt/images/$output.jpg done ____ This is the error message I get running the script: # ./capture.sh --- Opening /dev/video0... Trying source module v4l2... /dev/video0 opened. No input was specified, using the first. Unable to query input 0. VIDIOC_ENUMINPUT: Inappropriate ioctl for device mv: cannot stat '/opt/images/video0': No such file or directory --- Opening /dev/video1... Trying source module v4l2... /dev/video1 opened. No input was specified, using the first. Unable to query input 0. VIDIOC_ENUMINPUT: Inappropriate ioctl for device mv: cannot stat '/opt/images/video1': No such file or directory --- Opening /dev/video2... Trying source module v4l2... /dev/video2 opened. No input was specified, using the first. Adjusting resolution from 1920x1080 to 1280x800. Delaying 10 seconds. --- Capturing frame... Skipping 5 frames... Capturing 1 frames... Captured 6 frames in 0.17 seconds. (35 fps) --- Processing captured image... Setting output format to JPEG, quality -1 Disabling banner. Clearing timestamp. Clearing info text. Writing JPEG image to '/opt/images/video2'. --- Opening /dev/video3... Trying source module v4l2... /dev/video3 opened. No input was specified, using the first. Unable to query input 0. VIDIOC_ENUMINPUT: Inappropriate ioctl for device mv: cannot stat '/opt/images/video3': No such file or directory ____ Here is my lsusb output: Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 004: ID 04f2:b351 Chicony Electronics Co., Ltd Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub _____ typing v4l2-ctl --list-devices I get: cedrus (platform:cedrus): /dev/video1 sun8i-di (platform:sun8i-di): /dev/video0 HD Webcam: HD Webcam (usb-1c1b000.usb-1): /dev/video2 /dev/video3 The only physical device is the /dev/video2 I got some clue reading this post: https://unix.stackexchange.com/questions/512759/multiple-dev-video-for-one-physical-device but I don´t know much (i.e. nothing) about kernel compiling, drivers and etc. Does anyone know what to stop assigning video nodes to these memory-to-memory devices? Is there a way to filter the virtual devices on my fswebcam script? Thank you!
  13. Hello, I have OPI0 with Ubuntu 20.04.1 LTS with Linux 5.8.6-sunxi and I would like to set 240 MHz as minimum frequency. cpufreq-info shows that available steps starts at 480 MHz but on older kernel 240 MHz and 120 MHz were available too. I also tried to "force" 240 and 120 by editing /etc/default/cpufrequtils but no go. Lower reachable frequency is 480 MHz and what I see are a bit CPU higher temperatures. cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 5.44 ms. hardware limits: 480 MHz - 1.01 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "conservative" may decide which speed to use within this range. current CPU frequency is 480 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:98.26%, 648 MHz:1.28%, 816 MHz:0.12%, 960 MHz:0.35%, 1.01 GHz:0.01% (12233) analyzing CPU 1: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 5.44 ms. hardware limits: 480 MHz - 1.01 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "conservative" may decide which speed to use within this range. current CPU frequency is 480 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:98.26%, 648 MHz:1.28%, 816 MHz:0.12%, 960 MHz:0.35%, 1.01 GHz:0.01% (12233) analyzing CPU 2: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 5.44 ms. hardware limits: 480 MHz - 1.01 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "conservative" may decide which speed to use within this range. current CPU frequency is 480 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:98.26%, 648 MHz:1.28%, 816 MHz:0.12%, 960 MHz:0.35%, 1.01 GHz:0.01% (12233) analyzing CPU 3: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 5.44 ms. hardware limits: 480 MHz - 1.01 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "conservative" may decide which speed to use within this range. current CPU frequency is 480 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:98.26%, 648 MHz:1.28%, 816 MHz:0.12%, 960 MHz:0.35%, 1.01 GHz:0.01% (12233) thank you
  14. On a fresh install of Armbian 20.08.1/Linux 5.8.5-sunxi on an OPi Zero (256MB version), total memory is 238MB according to "free -m": root@orangepizero:~# free -m total used free shared buff/cache available Mem: 238 74 78 1 85 154 Swap: 119 0 119 238MB is not 256MB. :-) I assume the discrepancy is due to reserved framebuffer memory, but after a bit of testing I've found that the "sunxi_fb_mem_reserve" parameter (set to "16" in /boot/boot.cmd by default) has no apparent effect. Here's a boot with the Armbian default "sunxi_fb_mem_reserve=16": root@orangepizero:~# dmesg | grep "command line" && free -m [ 0.000000] Kernel command line: root=UUID=442e3394-ebc5-4a14-82f8-235d74d6b2e5 rootwait rootfstype=ext4 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 consoleblank=0 loglevel=1 ubootpart=7d536c8c-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 total used free shared buff/cache available Mem: 238 73 82 1 81 155 Swap: 119 0 119 A boot with "sunxi_fb_mem_reserve=0": root@orangepizero:~# dmesg | grep "command line" && free -m [ 0.000000] Kernel command line: root=UUID=442e3394-ebc5-4a14-82f8-235d74d6b2e5 rootwait rootfstype=ext4 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 consoleblank=0 loglevel=1 ubootpart=7d536c8c-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=0 cgroup_enable=memory swapaccount=1 total used free shared buff/cache available Mem: 238 74 82 1 81 154 Swap: 119 0 119 A boot with "sunxi_fb_mem_reserve=32" (the kernel default according to https://linux-sunxi.org/Kernel_arguments): root@orangepizero:~# dmesg | grep "command line" && free -m [ 0.000000] Kernel command line: root=UUID=442e3394-ebc5-4a14-82f8-235d74d6b2e5 rootwait rootfstype=ext4 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 consoleblank=0 loglevel=1 ubootpart=7d536c8c-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=32 cgroup_enable=memory swapaccount=1 total used free shared buff/cache available Mem: 238 74 82 1 81 154 Swap: 119 0 119 Now, since I'm building a headless server and have no actual use for a framebuffer and "sunxi_fb_mem_reserve=0" doesn't appear to work, is there any other way to recover the framebuffer memory? Or am I completely off track and the memory is taken by something else entirely? ;-)
  15. When I try to read the input on PA19 immediately goes to "1" even though there is no voltage being sent to the pin. Example: #!/usr/local/bin/python from pyA20.gpio import gpio from pyA20.gpio import port pin_to_circuit = port.PA19 gpio.init() gpio.setcfg(pin_to_circuit, gpio.OUTPUT) gpio.output(pin_to_circuit, 0) gpio.setcfg(pin_to_circuit, gpio.INPUT) print(gpio.input(pin_to_circuit)) I don't understand why this would put "1" with nothing even connected to the PA19 pin? Are there some settings I need to change to get PA19 working as a normal GPIO pin?
  16. I use orange pi zero with armbian xenial 5.38 with update kernal via apt-get upgrade the issue is that sometime the device get hang at boot before the start of the kernal, and then we have to unplug it and plug it again i want to start watchdog at boot itselft, so if this happen the device reboot automatically i already sold 1000 devices, but now the sales stop due to this issue please help Thanks
  17. Trival endevour, though fun and easy to do. Text and diagram taken from zip file attached. Orange Pi Zero fan self adapting to temperature, inside Shenzhen Xunlong Software CO.,Limited manufacturered low profile (non-expansion board version) case. Probably can be used with other SBC's. FanDaemon source provided. Comes with no warranty of any sort. Use at your own risk. The software included works with Mainline Kernel 4.13 Armbian image. Run armbian-config - system - hardware, use arrow keys to highlight "pwm" and press spacebar to [*] enable it. Select save and reboot. Install the fan how you wish. I used a 5volt 3cm wide (bigger will not fit), 1cm thick blower fan from ebay (sucks air in from below, blows from side) glued to the ceiling of the case against the top vents. Could also cut holes into the roof and mount a regular fan to blow air out the top, or on top of the sbc and leave vents unaltered. Use sticky tape to cover the extra vent slits and round the blower fan if there is a gap, to stop leakage. I filed the power cable hole in the case wider, to allow more air flow. Mosfet I used was "FQP30N06L/FQP30N06" very common and cheap if you can wait several weeks for shipping from ebay. 10kohm resistor between outer pins using wires with 2.54 header plugs. Tight fit but doable. You can use either the +3.3v power rails (pin 1 or 9 on 26 pin header) or +5v for faster fan speed, or for fans that do not handle the lower voltage. For some reason when using +5v, I only got a very narrow range of operation or 2 effective speeds whereas with 3.3v, duty cycles 20% to 100% worked. For +5v, pin 1 on the 13 pin header can be used, however the wire tends to hand right on top of fan and risks it being sucked into the blades. Put the fand executable where ever you want and do... chown root fand chmod u+x fand (I used midnight commander and used in its File menu, set owner can execute and chown adding file to root user and root group) fand software needs root priviledges for manipulating the pwm interface in /sys folder. Maybe another user in wheel group would do? run sudo crontab -e and below "# m h dom mon dow command" add (#how to customise below) @reboot sleep 10 && nohup /root/fand/./fand 48000 5 1 65 10 100 & Remember to press enter after "&" as the crontab requires a new empty line after declaring the last cronjob. Sleep is added as I found if the daemon was started too early, there was a chance the fand would fail to start for whatever reason. * e.g. above for FanD executable located in /root/fand/ sets Duty Cycle freqency to 48000Hz (or something or rather), temperature check at 5 second intervals temperature/DT% 1c(10%DT) to 65c(100%DT) #fand command line is as below /(path to execultable)/./fand duty cycle (Duty Cycle (DT) frequency) (polling interval in seconds) (min temperature, lowest DT% => 1) (temp for max DT%) (& to fork into background) FanD shows Duty Cycle % in its process name when using the "top" command, scroll down using down arrow if you cannot see it at first. To compile included fand.c source, if you edit it or do not trust the included binary. gcc -std=gnu99 fand.c -o fand Daemon has negligible memory and cpu usage. You can also set a fixed speed with console commands in a script as root. You may need to experiment with values. echo 0 > /sys/class/pwm/pwmchip0/unexport echo 0 > /sys/class/pwm/pwmchip0/export echo normal > /sys/class/pwm/pwmchip0/pwm0/polarity # set the DT period to 30000 ns echo 30000 > /sys/class/pwm/pwmchip0/pwm0/period # e.g. set the duty cycle to 15000 ns (50%DT?) echo 15000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable to disable pwm (and the fan), as root enter... echo 0 > /sys/class/pwm/pwmchip0/pwm0/enable Longer DT periods/lower DT frequency, if used, produces a humming sound from the motor. Credits to FanD software to Andrea Cioni. Forked by me from github version for better compatibility with Orange Pi Zero. Did not comment changes I made, on account of being too lazy. DT polarity corrected and device in unready state (preventing daemon start) bug improved. I have ceramic heatsinks on both the ram and soc chip bonded using Artic Silver. Dries and cements the heatsinks to surface rather well. With cpu governor set to performance (constant 1200mhz), ambient air about 22celcius at idle the cpu temperature is 40-45celcius using the cronjob given above. OrangePiZero-FanDaemon-and-wiringdiagram-src&binary.zip
  18. Hi, I'm facing a problem with my Orange Pi Zero with the latest Armbian version. I noticed that when I provide an internet connection type that is not valid (wrong psk, ethernet but no cable plugged in, etc.) and I reboot the system, it hangs just before asking the username and password. Sometimes it takes up to 10 minutes before keeping going. These are the last boot logs that I see: [ 11.209226] systemd[1]: Starting Create list of static device nodes for the current kernel... [ 11.219428] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped. [ 11.244988] systemd[1]: Started Nameserver information manager. [ 11.254315] systemd[1]: Reached target Network (Pre). [ 11.264815] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. [ 11.274833] systemd[1]: Condition check resulted in File System Check on Root Device being skipped. [ 11.293312] systemd[1]: Starting Load Kernel Modules... [ 11.317312] systemd[1]: Starting Remount Root and Kernel File Systems... [ 11.343632] systemd[1]: Starting udev Coldplug all Devices... [ 11.376556] systemd[1]: Mounted POSIX Message Queue File System. [ 11.386689] systemd[1]: Mounted Kernel Debug File System. [ 11.396501] systemd[1]: Mounted Kernel Trace File System. [ 11.413706] systemd[1]: Finished Create list of static device nodes for the current kernel. [ 11.416094] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro [ 11.458472] systemd[1]: Finished Remount Root and Kernel File Systems. [ 11.472062] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. [ 11.481213] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. [ 11.505488] systemd[1]: Starting Load/Save Random Seed... [ 11.514898] systemd[1]: Condition check resulted in Create System Users being skipped. [ 11.553531] systemd[1]: Starting Create Static Device Nodes in /dev... [ 11.583442] g_serial gadget: Gadget Serial v2.4 [ 11.588174] g_serial gadget: g_serial ready [ 11.610410] systemd[1]: Finished Load Kernel Modules. [ 11.626029] systemd[1]: Finished Load/Save Random Seed. [ 11.650175] systemd[1]: Mounting FUSE Control File System... [ 11.671958] systemd[1]: Mounting Kernel Configuration File System... [ 11.694089] systemd[1]: Starting Apply Kernel Variables... [ 11.724736] systemd[1]: Mounted FUSE Control File System. [ 11.741343] systemd[1]: Finished Create Static Device Nodes in /dev. [ 11.751604] systemd[1]: Mounted Kernel Configuration File System. [ 11.776484] systemd[1]: Starting udev Kernel Device Manager... [ 12.843290] thermal thermal_zone0: binding zone cpu_thermal with cdev thermal-cpufreq-0 failed:-22 **Usually here after a couple of seconds I'm asked to provide the username and password** After that the system hangs for a very long time. I stopped and disabled NetworkManager-wait-online.service but nothing changed. Is there something else that prevents the boot phase to finish before having established the connection? Thanks a lot Mattia
  19. Hi - I have been using Armbian buster stable on Orange Pi Zero for the past 12 months, starting with 5.92 last August and going up to 20.05.7 today. In all of these versions, clock speeds above 1.008GHz are unavailable, despite the board supporting 1.104GHz, 1.2GHz, 1.296GHz and 1.368GHz. They are not listed in armbian-config, cpufreq-set is unable to set them, and dmesg includes lines like: [ 10.030991] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 10.031017] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000) [ 10.031305] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 10.031322] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000) [ 10.031589] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 10.031610] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000) [ 10.031883] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 10.031902] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000) Then: /sys/devices/system/cpu/cpufreq/policy0# cat scaling_available_frequencies 480000 648000 816000 960000 1008000 My understanding is OPi Zero has only two regulator settings: 1.1V and 1.3V. So, not surprising if the DTB is trying to set the regulator to 1.32V or 1.4V things don't work. But why is this happening? What am I missing? How do I use these frequencies on Armbian buster stable? Thank you so much! -Adrian
  20. Hi. I've upgraded Buinic to Eoan and encountered an error with apt-get. Decided to have a fresh install of Disco from https://dl.armbian.com/orangepizero/ and got exact same error. I did nothing with the installation except that I've configured WiFi with ntmui-connect command. So I guess this is some issue with Ubuntu releases 19.xx root@orangepizero:~# apt-get update && apt-get upgrade Hit:1 http://ports.ubuntu.com disco InRelease Hit:2 http://ports.ubuntu.com disco-security InRelease Hit:3 http://ports.ubuntu.com disco-updates InRelease Hit:5 http://ports.ubuntu.com disco-backports InRelease Hit:4 https://apt.armbian.com disco InRelease Traceback (most recent call last): File "/usr/lib/cnf-update-db", line 26, in <module> col.create(db) File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 93, in create self._fill_commands(con) File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 127, in _fill_commands self._parse_single_commands_file(con, fp) File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 165, in _parse_single_commands_file suite=tagf.section["suite"] KeyError: 'suite' Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then /usr/lib/cnf-update-db > /dev/null; fi' E: Sub-process returned an error code
  21. Armbian_20.05.3_Orangepizero_buster_current_5.4.45.img apt install cryptsetup lvm2 thin-provisioning-tools All ok if install any two, size problem?
  22. Hi everyone, I'm facing a problem with logrotate on my OrangePi Zero with Armbian Focal mainline. Basically I have a process that is always running with a `tee` command that outputs the stdout to a log file in the /var/log/ directory. My logrotate configuration file looks like the following: /var/log/smartbit/gocpp.log { rotate 10 daily compress missingok notifempty copytruncate dateext } It's all working correctly except the copytruncate part: logs are daily rotated and gzipped but the gocpp.log is not truncated to 0 bytes, so it gets bigger and bigger. I noticed that in this new Armbian version logrotate is not triggered by a cron but by systemd logrotate.service. If I run /usr/sbin/logrotate /etc/logrotate.conf, everything works included the copytruncate line, but with `systemctl start logrotate.service` the copytruncate line is not considered. Does anyone know why? Thanks in advance Mattia
  23. Hello. I have an Orange Pi Zero board with Armbian on it. I want to use its serial pins for flashing arduinos. Right now I only have 1x3 serial pins and 1x13 media (?) pins soldered, the 2x13 GPIO doesn't have any pins and I don't have any spare ones to solder (alright, I might have some, but I'm too lazy for that). That means I only have access to UART0 pins which are currently reserved for Linux console. With RPi Zero and Raspbian the same problem was solved by simply removing "console=ttyAMA0,115200" from kernel options. However, Armbian seems to generate kernel options entirely from armbianEnv.txt, making it impossible to manually remove serial console stuff. I tried setting "console=none" or just deleting this line from armbianEnv, but it just sets console to "both" in boot.cmd and nothing changes. Any other options?
  24. Symptoms: Board does not boot Armbian from inserted SD card, but may boot other distributions (based on old/legacy u-boot). Following or similar output can be grabbed from the serial console: U-Boot SPL 2017.01-armbian (Feb 02 2017 - 03:04:04) DRAM: 2048 MiB Trying to boot from MMC1MMC: no card present spl: mmc init failed with error: -123 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### The key message here is "MMC: no card present" Most likely cause: Malfunctioning microSD slot card detect switch. It can be verified either visually (with a magnifying glass) or electronically (with a multimeter) - at least in the slots used on Orange Pi boards and on Pine64 the pin near the switch should be shorted to the ground (i.e. SD slot casing) when card is inserted. Illustration (example) of a working switch: Verification (with a multimeter): Probe 1 - slot pin near the switch (may be different for different slot types, but at least true for Oranges and Pine64) Probe 2 - microSD slot casing or other parts connected to GND (not shown on the photo) No card - circuit is open Card inserted - circuit is shorted Photos - card is not inseted on the left and is fully inserted on the right: Orange Pi Pine64 (switch is more visible) Can it be fixed? Yes if the switch is not broken completely, by carefully adjusting (bending) the stationary contact (left on the pictures and photos, it usually is a part of the SD slot casing) i.e using a needle so it touches the moving contact (mostly hidden inside the slot on the photos) when card is inserted and not touching it when it is not inserted.
  25. HI, guys. i need help, with my orange pi zero + mpc2515. My connect, is the same as this image. Int connect to PA7. mcp-2515.dtbo: /dts-v1/; /plugin/; / { compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { target-path = "/clocks"; __overlay__ { #address-cells = <1>; #size-cells = <1>; can0_osc_fixed: can0_osc_fixed { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <8000000>; }; }; }; fragment@1 { target = <&pio>; __overlay__ { can0_pin_irq: can0_pin_irq { pins = "PA7"; function = "irq"; bias-pull-up; }; }; }; fragment@2 { target = <&spi0>; __overlay__ { #address-cells = <1>; #size-cells = <0>; status = "okay"; mcp2515 { reg = <0>; compatible = "microchip,mcp2515"; pinctrl-names = "default"; pinctrl-0 = <&can0_pin_irq>; spi-max-frequency = <10000000>; interrupt-parent = <&pio>; interrupts = <0 7 2>; /* PA7 IRQ_TYPE_EDGE_FALLING */ clocks = <&can0_osc_fixed>; status = "okay"; }; }; }; }; dmesg | grep spi [ 3.311923] sun6i-spi 1c68000.spi: chipselect 0 already in use [ 3.311943] spi_master spi0: spi_device register error /soc/spi@1c68000/flash@0 [ 3.311964] spi_master spi0: Failed to create SPI device for /soc/spi@1c68000/flash@0 [ 12.137229] mcp251x spi0.0: MCP251x didn't enter in conf mode after reset [ 12.139207] mcp251x spi0.0: Probe failed, err=16 [ 12.139292] mcp251x: probe of spi0.0 failed with error -16 I try change this is solution not work. Thank you in advance for your help.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines