Search the Community

Showing results for tags 'solved'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Allwinner H6
    • Rockchip 3399
    • Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 122 results

  1. Espressobin V7 1G 800MHz DDR4 RAM 1GHz cpu purchased last week. The board starts up reliably and gets to the boot prompt ok (using minicom). I downloaded and unpacked Armbian_5.91_Espressobin_Debian_buster_next_4.19.59.img. Ran shasum and got "Ok". I dd'd it to a new Samsung SD card, dd'd it back, and ran shasum again, getting "Ok". I put the card in the board and powered it up. It finds the card and tries to boot but fails, saying: Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Bad Linux ARM64 Image magic! I'm guessing that the problem is that I did not update uboot. I copied flash-image-ddr4-1g-1cs-1000_800.bin to a FAT formatted USB key, but this: Updated u-boot needs new default boot environment and new boot script (overwrite the one on your /boot media – needed only if you upgrade from < v5.59). This is what you need to copy/paste into u-boot prompt: is unclear. This: Copy this flash-image-ddr4-1g-1cs-1000_800.bin to your FAT formatted USB key, plug it into USB3.0 port and execute from u-boot prompt: bubt flash-image-ddr4-1g-1cs-1000_800.bin spi usb Seems clear enough. I assume that I am then to paste the list of commands that follows in at the boot prompt but the part about the "new boot script" is unclear. [Edit] I updated uboot and inserted the setenv commands (but ignored the unclear part about the "new boot script"). I'm getting U-Boot 2018.03-devel-18.12.3-gc9aa92c-armbian (Feb 20 2019 - 09:45:04 +0100) so that evidently worked. However, when it tries to boot from the SD card I get Marvell>> run bootcmd_mmc0 / ** Unrecognized filesystem type ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ ** Unrecognized filesystem type ** ## Executing script at 06d00000 Wrong image format for "source" command Marvell>> [Edit] The SD card is the same one that I used to flash the Uboot update. Is it necessary to prepare the card in any way other than to dd the image to it? [Edit] I loop mounted the image and found that it has an ext4 filesystem with an 8192 block offset. Used dd to make a copy with no offset. That copy boots. -- John Hasler
  2. Hello, Recently I bought a nanopi fire 3 and installed armbian without any issue (Armbian_5.91_Nanopifire3_Debian_buster_next_4.14.133). The first thing I did was to connect the nanopi to my ADSL router in order to complete the basic configuration. Everything worked fine. Then I connected the nanopi to an Edimax gigabit ethernet switch and here is where the network problems appeared. The ethernet connection was too slow, with ping times of more than 1000ms, and an unstable behavior that made it almost impossible to connect via ssh. 64 bytes from icmp_seq=1 ttl=64 time=1004 ms 64 bytes from icmp_seq=2 ttl=64 time=1025 ms 64 bytes from icmp_seq=3 ttl=64 time=1001 ms 64 bytes from icmp_seq=4 ttl=64 time=1002 ms After many reconfigurations and reinstalls, I tried forcing the ethernet interface to work at 100Mbps, and it solved the network slugginess and unstability. ethtool -s eth0 speed 100 autoneg off Other devices connected to the same switch work fine at 1Gbps. Although with this workaround I can work for now, I still want to use my nanopi at full speed if possible. Anybody has any idea of how can I solve it?
  3. first i was able to boot my nanopi from SD card and i was able to access it through SSH. then i was trying to boot my nanopi from EMMC but it was not booting. I already installed a different OS which is specialized for Eflasher (nanopi-neo-core_eflasher_friendlycore-xenial_4.14_armhf_20190522 ) . then i followed the steps carefully: ... i_NEO_Core note : i was using commands since there is no HDMI. I typed : eflasher then i choose 1 and typed yes and waited until the OS was installed successfully and finally i powered off the nanopi, removed the SD card as mentioned, tried to power it on but i could not access it again through SSH anymore. I would if someone could help find the problem. or if someone would post the detailed steps to boot the nanopi NEO CORE from emmc using commands lines not HDMI. thanks in advance
  4. I know Lamobo-r1 has many problems and that the support ended, but it works fine for me. Everything works fine with kernel 4.14.84-sunxi, however, when I update the kernel, the b53 switch does not work anymore. I need to update the kernel to add another wifi usb dongle that seems to work only with newer kernels ( Anybody experiencing the same problem? Any ideas for a workaround?
  5. Hi, I can't make usb otg works on orange pi pc armbian stretch. Linux orangepipc 4.19.38-sunxi #5.83 SMP Fri May 3 23:33:25 CEST 2019 armv7l GNU/Linux At boot there is the following message in dmesg: [ 2.252841] usb0-vbus: disabling I tried to enable usbhost0 with armbianconfig overlays, but it doesn't make a difference. Any suggestions ? thanks
  6. Hi! short question: Best way to create a bootable clone of sd card? I did some reading and found ">>create image on windows >> shrink image via gparted" doesn't work for me since I dont have a second computer running linux (will the linux subsystem on windows 10 help?). In the past, I used the rpi-clone on a raspberry, but reading in this forum has taught me that hotcloning an armbian sd card via script is not necessarily safe. Computers availabel to me are: 1) odroid hc2 running armbian 2) acer laptop running windows 10
  7. TRYING TO create an ad-hoc network using wireless adapter( lb-link model: wn155a) on NANOPI NEO (Linux nanopim1 3.4.113-sun8i #28 SMP PREEMPT Thu Feb 2 02:01:28 CET 2017 armv7l GNU/Linux). we used this link BUT ad-hoc WAS NOT CREATED. running iwconfig looks like: lo no wireless extensions. tunl0 no wireless extensions. ra0 Ralink STA ESSID:"11n-AP" Nickname:"MT7601STA" Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated Bit Rate:1 Mb/s RTS thr:off Fragment thr:off Encryption key:off Link Quality=10/100 Signal level:0 dBm Noise level:0 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 eth0 no wireless extensions. running ifconfig looks like : eth0 .....(not important) lo ... (not important) ra0 Link encap:Ethernet HWaddr 0c:8c:24:b7:d7:dc UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:17365 errors:0 dropped:0 overruns:0 frame:0 TX packets:156 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3718930 (3.5 MiB) TX bytes:16224 (15.8 KiB) Can I use the steps of creating an Access Point to create an ad-hoc mode network? or I am in the wrong way?
  8. After connecting the wireless adapter we run the following command: lsusb the output is Bus 004 Device 003: ID 148f:7601 Ralink Technology, Corp. Trying to install armbian driver (Linux nanopim1 3.4.113-sun8i #18 SMP PREEMPT armv7l GNU/Linux) for lb-link model: wn155a "MTK7601 chipset" wireless adapter (150Mbps) using the following commands: sudo apt-get install linux-headers-generic build-essential git sudo apt-get install git git clone cd mt7601 make clean make sudo make install sudo mkdir -p /etc/Wireless/RT2870STA/ sudo cp RT2870STA.dat /etc/Wireless/RT2870STA/ sudo modprobe mt7601Usta the output of the last command is modprobe: ERROR: could not insert 'mt7601Usta': Exec format error what should we do? is MT7601U the same as MTK7601? or do we need another driver?
  9. Hello, I want to read data from UART3 on OrangePi One. I want to use UART3 (pin 8 & 10), so I enabled uart3 overlay at /boot/armbianEnv.txt. Now I expect to read data via minicom -b 115200 -D /dev/ttyS3 but I read nothing unfortunately. What am I missing? Any help is appreciated. I'm using Linux orangepione 4.19.38-sunxi (sorry, armbianmonitor doesn't generate link) Thank you, Regards
  10. So I did the following today: Everything went fine except at the end where it complained about busybox not being there and it failed the update of initramfs... This was no issue. I installed busybox, rebooted, ran apt-get autoremove and then autoclean and everything worked fine. I was still on kernel 3.x, so I ran armbian-config but I did not see the latest kernel present in the switch kernel option. I ran apt-get install (or something similar) and it installed, so I then rebooted. Now it's bricked. I'm attaching the serial console output. Please help. Here is the result of 'printenv': Thank you.
  11. I am having problems with the NanoPi R1. I loaded the latest Armbian for R1 on flash. All works good. I went to armbian-config to load into eMMC. The last step of the process had weird text on the dialog, I clicked "OK" anyway, and the process seemed to be working. But after removing uSD card and rebooting, the board does not work. The red led stays on solid. Did anyone successfully burn the image from uSD to eMMC using the tool in armbian-config?
  12. Hi everyone, What I want to do is to use a DS18B20 through 1-Wire to read temperature on an OPi Zero. The sensor seems to be detected by the board (I see the file under /sys/bus/w1/devices/28-something), and then it disappears randomly after a reboot or a power cycle. (file goes away and obviously I can't get any readings). Then it starts working randomly again after an indefinite amount of reboots. I'm having this problem for a while now, and it's driving me absolutely crazy. This one here on the picture is the sensor I'm using. I have attached a 4.7K Ohm resistor between the VCC and Digital cables, and attached to OPi Zero as follows: VCC -> BCM pin 2 (5V, I've also tried with 3.3V) Digital -> BCM pin 26 (PA10) Ground -> BCM pin 25 After that, I've edited my /boot/armbianEnv.txt and it looks like this now: verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost2 usbhost3 i2c0 i2c1 w1-gpio param_w1_pin=PA10 param_w1_pin_int_pullup=0 rootdev=UUID=374d182b-7b9e-4570-b7c5-519a1eb837a7 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u0x2537:0x1066:u,0x2537:0x1068:u0x2537:0x1066:u,0x2537:0x1068:u Also adapted the /etc/default/cpufrequtils file as follows: # WARNING: this file will be replaced on board support package (linux-root-...) upgrade ENABLE=true MIN_SPEED=480000 MAX_SPEED=1200000 GOVERNOR=interactive And the /etc/modules-load.d/modules.conf: g_serial i2c-dev w1-gpio w1-therm So, after all these modifications, I do a reboot and I can see the w1_gpio and w1_therm modules loaded in the output from lsmod, and I can see the device in /sys/bus/w1/devices/28-something I can get my readings and everything works properly. Then, I do a reboot. Here is where I get super confused, because it seems like there's no systematic error in the wiring or the kernel modules being loaded as far as I can see. But, the device disappears after the reboot. Sometimes it will get detected again, without me doing any changes in the configuration. I've already tried two of the same sensor, but it doesn't seem to make any difference, same problem still. I've also put the armbianmonitor output to the post. Looking desparately for some ideas to help me debug this problem. Thanks!
  13. I use the Armbian_5.45_Orangepizeroplus2-h5_Debian_stretch_next_4.14.44.img. I want to use a sensor based on the spi protocol. In armbian-config i enable the spi ,the armbianEnv.txt like this: verbosity=1 console=both overlay_prefix=sun50i-h5 overlays=i2c0 i2c1 spdif-out spi-add-cs1 spi-jedec-nor spi-spidev uart1 uart2 usbhost2 usbhost3 rootdev=UUID=bb48b498-7bd1-4018-b77d-ba00fa61a33d rootfstype=ext4 param_uart1_rtscts=1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u But in /dev on spi-dev root@H5:~# ls /dev/s shm/ snd/ stderr stdin stdout Is it because there is no code adaptation spi-dev? if not ,I want to try to transplant the spi-dev code,Can give me some guiding advice?
  14. Hello, I'm running a OPI Lite with debian jessie, All works fine until i have to reboot, and that happens quiet often while testing software. AFTER the boot i'm not able to reach the OPI via SSH, because the eth0 is activated ...and has a 169.x.x.x ip adress... On the OPI Lite i can ONLY discover WIFI and no eth0 connector...So i go into the "nmtui" tool and "disactivate" the eth0... Than i have access again via the wifi to my OPI lite. How can i completely disable the eth0, that only WIFI connects to my network? I didn't find about this behavior on the web, anyone else have that problem? Kind regards from Hans F4VSJ
  15. I use a Beelink X2 Android TV box with Armbian Stretch mainline kernel 4.19.y Image on a SD Card. If I plug in my SD Card and then the power supply, the LED is purple and after some seconds blue. No picture over hdmi but the num-lock on the keyboard works. The box also don't get an IP over DHCP. No matter how long (1h+) I wait, nothing happens... When I plug in the power supply without the SD Card, the LED is red. The normal standby mode of the box. I can now plug in the SD Card and then power the system on. The LED switches to purple and after sone seconds to blue and Armbian is running fine, no problems. If the system reboots it will run into the boot problem described above. Armbian is great but as long as I can't find a solution it sucks to plug out/in the SD Card all the time the system starts... Tryed different SD-Cards, Etcher and Rufus, other power supply - allways the same problem. The Image SHA256 hash is ok. I wanna boot direct from the SD Card and leave the android on the onboard emmc as it is. I hope someone can give me some hints, but be kind - I have only some basic knowledge of linux. ^^ Thanks
  16. Hi Guys ! I bought a new WD Blue 3D NAND SSD (1TB). It is not detected by the USB 3.0 port but by the USB 2.0 port (tested with lsblk). What can I do to be recognized on the fast 3.0 port? I am using Armbian_5.73.190128_Rockpi-4b_Debian_stretch_dev_4.20.0 Best thanks in advance ... !
  17. Hi, Recently I have installed "Armbian_5.75_Orangepizero_Debian_stretch_next_4.19.20" on my OrangePi Zero . I configured both Ethernet and wifi connection but I had a problem with the wifi, my board does have an IP address but I can not connect through ssh nor pinging that IP. The connection is Ok and I can get access to internet but I can not ping from any other devices on the network (error Destination host unreachable), But I noticed that if I ping (from the orangepi board ) the host machine then I will be able to connect through ssh to that IP. I dont know if its a problem with arp last thing that I tried was to disable the network manager but I still have the same issue.
  18. Dear Armbian friends, I have question about add DS18B20 temp sensor at RPi-Monitor (web based interface). Can somebody paste working config of this sensor? On internet I found many tutorials but with DHT sensors. On this page (Xavier is an author of RPi-Monitor I think) is described DS18B20 but in status "Working in progress". I tried this but without luck. Cheers, Lucas
  19. hello everyone my Orange Pi A20 does not detect any USB device with the current versions of Stretch or Bionic, but works fine with Wheezy I had try with a printer, a scanner, or USB stick. When something is connected, nothing appears in dmesg or lsusb. Yes...yes...I've been reading the troubleshooting FAQs and Google it for an answer. Change power supply and SD card, etc. But a printer or scanner doesn't consume too much power from the USB, does it? in a last effort I went back to the old Debian Wheezy (downloaded from and everything works fine. Any help with that? Could it be a kernel parameter or module?
  20. Requirements: (for Raspberry Pi) (for Orange Pi PC) sudo armbian-config System --> Hardware --> select "spi-spidev" --> Confirm --> reboot when reboot finish: sudo vim /boot/armbianEnv.txt under "overlays=spi-spidev",add this: "param_spidev_spi_bus=0" save & reboot again. then you can see spi enable in "/dev/spidev0.0". cd ./SPI_Python sudo python3 install cd ../RC522 sudo python3 you can test IC card like this: Welcome to the MFRC522 data read example Press Ctrl-C to stop. Card detected Card read UID: 53,101,232,169 Size: 8 Sector 8 [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Card detected Card read UID: 53,101,232,169 Size: 8 Sector 8 [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
  21. I installed Armbian_5.75_Orangepizeroplus2-h3_Debian_stretch_next_4.19.20. But it can't boot up. These image can boot up. Armbian_5.65_Orangepizeroplus2-h3_Debian_stretch_next_4.14.78 Armbian_5.69_Orangepizeroplus2-h3_Debian_stretch_next_4.19.13
  22. Hi, I am running Debian Strech on a headless server with armbian (since 2014 on wheezy), on a Cubox-i 4 Pro. My system is on /dev/sda1 After an upgrade, few minutes ago, my device is no more reachable by ssh neither answering to ping. It seems to boot the kernel but I am not even sure of that (as nothing appears in the console after "booting the kernel"). Here is the full console log: U-Boot SPL 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42) Boot Device: SD1 spl: error reading image u-boot.img, err - -1 Load image from RAW... U-Boot 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42) CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: MX6-CuBox-i DRAM: 2 GiB MMC: FSL_SDHC: 0 *** Warning - bad CRC, using default environment In: serial Out: vga Err: vga Net: FEC [PRIME] (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found Hit any key to stop autoboot: 0 mmc0 is current device ** File not found /boot.scr ** ** File not found /uEnv.txt ** ** File not found /zImage ** ** File not found /uImage ** 1816 bytes read in 127 ms (13.7 KiB/s) Running bootscript from mmc ... ## Executing script at 10800000 ** File not found .next ** 48 bytes read in 114 ms (0 Bytes/s) 36853 bytes read in 826 ms (43 KiB/s) 4636514 bytes read in 411 ms (10.8 MiB/s) 5839840 bytes read in 482 ms (11.6 MiB/s) Kernel image @ 0x10800000 [ 0x000000 - 0x591be0 ] ## Loading init Ramdisk from Legacy Image at 14800000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4636450 Bytes = 4.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800bff4 Starting kernel ... Uncompressing Linux... done, booting the kernel. Files located in /boot on the SDCard (same files list in sda/boot): -rw-r--r-- 1 root root 48 janv. 30 18:28 armbianEnv.txt -rw-r--r-- 1 root root 79 janv. 30 18:28 armbianEnv.txte -rw-r--r-- 1 root root 1,8K sept. 20 22:33 boot.cmd -rw-r--r-- 1 root root 1,8K sept. 20 22:33 boot.scr -rw-r--r-- 1 root root 360 déc. 27 2015 boot.txt -rw-r--r-- 1 root root 160K févr. 8 09:33 config-4.14.98-cubox -rw-r--r-- 1 root root 162K févr. 8 09:38 config-4.19.20-cubox lrwxrwxrwx 1 root root 17 févr. 16 17:47 dtb -> dtb-4.19.20-cubox drwxr-xr-x 2 root root 12K févr. 16 17:42 dtb-4.14.98-cubox drwxr-xr-x 2 root root 12K févr. 16 17:31 dtb-4.19.20-cubox -rw-r--r-- 1 root root 4,2M févr. 16 17:09 initrd.img-4.14.98-cubox -rw-r--r-- 1 root root 4,5M févr. 16 17:09 initrd.img-4.19.20-cubox -rw-r--r-- 1 root root 2,5M févr. 8 09:33 -rw-r--r-- 1 root root 2,6M févr. 8 09:38 lrwxrwxrwx 1 root root 21 févr. 16 17:47 uInitrd -> uInitrd-4.19.20-cubox -rw-r--r-- 1 root root 4,2M févr. 16 17:09 uInitrd-4.14.98-cubox -rw-r--r-- 1 root root 4,5M févr. 16 17:09 uInitrd-4.19.20-cubox -rwxr-xr-x 1 root root 5,4M févr. 8 09:33 vmlinuz-4.14.98-cubox -rwxr-xr-x 1 root root 5,6M févr. 8 09:38 vmlinuz-4.19.20-cubox lrwxrwxrwx 1 root root 21 févr. 16 17:48 zImage -> vmlinuz-4.19.20-cubox $ more boot.txt setenv bootargs root=/dev/sda1 rootfstype=ext4 rootwait console=tty1 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 rd.luks=0 rd.lvm=0 raid=noautodetect pci=nomsi ahci_imx.hotplug=1 consoleblank=0 vt .global_cursor_default=0 quiet ext2load mmc 0 0x18000000 /boot/dtb/${fdt_file} ext2load mmc 0 0x12000000 /boot/zImage bootz 0x12000000 - 0x18000000 $ more armbianEnv.txt verbosity=1 rootdev=/dev/sda1 usbstoragequirks= What else could I provide as information to get help? Thanks a lot to anybody that could give me some support...
  23. Hello, since I upraded from Armbian Strech 5.60 (kernel 4.14.84-sunxi) to Armbian Stretch 5.70 (kernel 4.19.13-sunxi), I can't get hostapd to work on my Cubietruck. When I modprobe the brcmfmac module, I get the following lines with dmesg: [134591.243266] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43362-sdio for chip BCM43362/1 [134591.523515] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43362-sdio for chip BCM43362/1 [134591.523658] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43362-sdio.clm_blob failed with error -2 [134591.523665] brcmfmac mmc1:0001:1: Falling back to syfs fallback for: brcm/brcmfmac43362-sdio.clm_blob [134591.532943] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-11), device may have limited channels available [134591.535517] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43362/1 wl0: Oct 23 2017 10:33:17 version 5.90.240 FWID 01-0 Also, the result of "ip a" returns "state DOWN" for interface wlan0. Did I miss something ? Thanks in advance for your suggestions, Romain
  24. Dear Armbian Friends, My temperature sensor is not detected by board. Can somebody give me some advice what should I chceck / change / test now? Cheers! Lucas I tried: - another sample of DHT11 - changed cables to different ones - changed - both tested sensors were connected with 4.7k resistor between positive and data cable - tried different system versions like bionic, stretch and now jessie - tried to load modules via /etc/modules-load.d/modules.conf g_serial w1-sunxi w1-gpio w1-therm - or with /boot/armbianEnv.txt (disabling loading with modules.conf) wverbosity=1 logo=disabled console=serial disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost2 usbhost3 w1-gpio param_w1_pin=PA10 param_w1_pin_int_pullup=1 rootdev=UUID=9cecf84e-027e-40ad-b711-ae5d323d9043 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u - tried to change data pin from GPIO10 (number 26) to GPIO 15 MOSI (number 19) Below some info about my system. sysadm@orangepizero:~$ ls /sys/bus/w1/devices/ w1_bus_master1 sysadm@orangepizero:~$ cat /sys/devices/w1_bus_master1/w1_master_slave_count 0 sysadm@orangepizero:~$ dmesg | grep wire [ 7.802453] Driver for 1-wire Dallas network protocol. [ 7.807173] gpio-10 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file sysadm@orangepizero:~$ sudo cat /sys/kernel/debug/gpio [sudo] password for sysadm: gpiochip0: GPIOs 0-223, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-10 ( |onewire@0 ) in lo gpio-17 ( |orangepi:red:status ) out lo gpio-20 ( |vcc-wifi ) out hi gpio-166 ( |cd ) in lo 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 gpio-362 ( |orangepi:green:pwr ) out hi sysadm@orangepizero:~$ uname -a Linux orangepizero 4.19.17-sunxi #5.73 SMP Mon Jan 28 21:06:40 CET 2019 armv7l GNU/Linux sysadm@orangepizero:~$ cat /etc/issue Debian GNU/Linux 9
  25. Hi, I just got an Orange Pi R1. It has an Allwinner quad core CPU, but I wonder what of the H2, H3 etc. type it is. hwinfo says: ... processor : 3 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 100.80 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 Hardware : Allwinner sun8i Family Revision : 0000 Thx